Hi!
I need help.
I had a cataclysm rom, with super su 2.66 and layers manager.
I installed layers theme, but then can not remove.
Full wipe, installed pure nexus rom, but the layers remain.
how do I fix this?
jcpq said:
Hi!
I need help.
I had a cataclysm rom, with super su 2.66 and layers manager.
I installed layers theme, but then can not remove.
Full wipe, installed pure nexus rom, but the layers remain.
how do I fix this?
Click to expand...
Click to collapse
they are stored in vendor/overlay folder. delete the apks there or just reflash vendor in the pure nexus OP
Related
I flashed cm 10.1 and then gapps, gapps writes over the gallery.apk so it changes the camera. I've noticed this with a few roms. I tried removing the apk from the gapps zip but for whatever reason the install fails. Any way I should go about this differently
IAIRgallery91456 said:
I flashed cm 10.1 and then gapps, gapps writes over the gallery.apk so it changes the camera. I've noticed this with a few roms. I tried removing the apk from the gapps zip but for whatever reason the install fails. Any way I should go about this differently
Click to expand...
Click to collapse
delete the gallery apk in /system/app/ using a root file exlporer, replace it with the gallery apk you want to use(in /system/app/), then reboot. itll install itself upon booting up.
Xposed for Samsung Lollipop is out. But I am having trouble installing apps since I installed xposed so I decided to remove it. I restored the system partitioned with a backup I've made before the installation but looks like xposed isn't removed. I still getting "Optimising app" at every start up and I cannot install apps from Play Store. Many of users that installed xposed reported these.
I even tried to wipe system (not data) and flashing the rom I'm using on it again but xposed is still there. (Stil getting "optimising apps" and error "-504" from play store. ) What can I do to totally remove xposed without wiping data or restoring data partition?
ImjuzCY said:
Xposed for Samsung Lollipop is out. But I am having trouble installing apps since I installed xposed so I decided to remove it. I restored the system partitioned with a backup I've made before the installation but looks like xposed isn't removed. I still getting "Optimising app" at every start up and I cannot install apps from Play Store. Many of users that installed xposed reported these.
I even tried to wipe system (not data) and flashing the rom I'm using on it again but xposed is still there. (Stil getting "optimising apps" and error "-504" from play store. ) What can I do to totally remove xposed without wiping data or restoring data partition?
Click to expand...
Click to collapse
have you tried to clear the data from the playstore and let it rebuild the services ??
krazierokz said:
have you tried to clear the data from the playstore and let it rebuild the services ??
Click to expand...
Click to collapse
I did, for many times
ImjuzCY said:
I did, for many times
Click to expand...
Click to collapse
How about this?? thanks to @craigcrawford1988
Did you try this ?Simply boot into TWRP, and mount system, then Advanced -> File Manager then do the following:1.Go into /system/bin/ and delete app_process32 and app_process32_xposed
2.Rename app_process32_original to app_process32
3.Delete dex2oat and rename dex2oat.orig to dex2oat
4.Repeat the above step for oatdump and patchoat
5.Go up a directory and then into the lib directory
6.Delete libart.so and rename libart.so.orig to libart.so
7.Repeat the above step for libart-compiler.so, libart-disassembler.so and libsigchain.so
8.Delete libxposed_art.so
9.Go up a directory and delete xposed.prop
10.Go into framework directory and delete XposedBridge.jar
11.Reboot your device.
krazierokz said:
How about this?? thanks to @craigcrawford1988
Did you try this ?Simply boot into TWRP, and mount system, then Advanced -> File Manager then do the following:1.Go into /system/bin/ and delete app_process32 and app_process32_xposed
2.Rename app_process32_original to app_process32
3.Delete dex2oat and rename dex2oat.orig to dex2oat
4.Repeat the above step for oatdump and patchoat
5.Go up a directory and then into the lib directory
6.Delete libart.so and rename libart.so.orig to libart.so
7.Repeat the above step for libart-compiler.so, libart-disassembler.so and libsigchain.so
8.Delete libxposed_art.so
9.Go up a directory and delete xposed.prop
10.Go into framework directory and delete XposedBridge.jar
11.Reboot your device.
Click to expand...
Click to collapse
Tried that too but that was for the "normal" official xposed alpha. The way the devs set xposed on samsung touchwiz is different. We flash a different version of xposed framework.
Many of the original files you listed I don't find it (almost all). I think the only way to totally remove it is a full wipe
well good luck with your problem bud , i tried Sorry we could not determine the issue.... Long weekend !
Do u still need help?
From my s4 Powered by
Prism barebone v15
shiruuu.samad said:
Do u still need help?
From my s4 Powered by
Prism barebone v15
Click to expand...
Click to collapse
I already did a clean install. But help is still welcomed to help those who needs help
ImjuzCY said:
I already did a clean install. But help is still welcomed to help those who needs help
Click to expand...
Click to collapse
I had issues of FC with xposed i used this guide to disable it.https://plus.google.com/app/basic/stream/z13ecnpjtpirgbyn023sdjagnpmrzjarm04Check the last comment of google+ post it should disable it.Hope it works
From my s4 Powered by
Prism barebone v15
shiruuu.samad said:
I had issues of FC with xposed i used this guide to disable it.https://plus.google.com/app/basic/stream/z13ecnpjtpirgbyn023sdjagnpmrzjarm04Check the last comment of google+ post it should disable it.Hope it works
From my s4 Powered by
Prism barebone v15
Click to expand...
Click to collapse
I tried this but I still can't install apps larger than 1mb. Apps that are smaller than 1mb installed perfectly. I don't get fc BTW. I got error -504 from play store. I Googled about it and the error is due to lack of space in /cache partition. I checked the partitions and proved it. Only 800kb free in cache partition but play store needs to download apks to cache before installing. Even restoring titanium backups made during xposed is installed to a clean installed rom can cause that. So I did a clean install without any backups restored.
I tried clearing cache before, it's emptied when I cleared it, but it fills up when optimising app and I don't think I can skip optimising app after clearing cache.
Try formatting system, data, cache then restore system and after first boot, restore data
If didnt work (this is impossible) that means you did the backup after installing xposed
Goodluck
RubbaBand said:
Try formatting system, data, cache then restore system and after first boot, restore data
If didnt work (this is impossible) that means you did the backup after installing xposed
Goodluck
Click to expand...
Click to collapse
Yes I was lazy I backed up after installing the apk before flashing the zip. So that backup is somehow unusable. I already did a fresh install .
I have a Moto X Pure running Andriod 6.0 Marshmallow, that I flashed from here. It was the XT1575 Stock 6.0 Deodexed from Sabissimo. I rooted using SuperSU beta, and I have xposed running. I have tried everything to remove the layers that I downloaded, I tried "uninstalling" them from Layers Manager, I tried uninstalling Layers Manager, I tried going into /system/vendor/overlay and manually deleting the files (which it won't let me do). I am pulling my hair out trying to figure this out, and google doesn't seem to be any help. Thank you.
jfreaks25 said:
going into /system/vendor/overlay and manually deleting the files (which it won't let me do).
Click to expand...
Click to collapse
That's the correct way to manually do it. If you're attempting to delete from an app, such as some file explorer, then make sure you granted root privileges and whatever else it asked for. Otherwise, you can do it from TWRP, which you might need to mount /system to complete.
Reboot
Sent from my XT1575 using Tapatalk
I was looking at how close my Nexus 5 really is to my R1 HD, and besides the obvious Qualcomm MTK thing they are amazingly similar.
I took the official Hammerhead NetHunter 3.0 Marshmallow zip and put it on my external and card.
I then did a factory reset including dalvik and cache in TWRP.
Installed SuperSU and booted my phone. I then installed Busybox Pro and rebooted back into TWRP.
Once in TWRP I clicked install and chose my saved nethunter-hammerhead-marshmallow-3.0.zip
It will open the Aroma installer. On the first screen click everything except the RF Analyzer, MAKE SURE YOU HAVE THE OLDER VERSION OF SUPERSU CHECKED TO INSTALL AS WELL.
On the next screen click everything but custom boot screen and custom wallpaper.
Click next and be patient while it installs everything, extracts the chroot image, and verifies the extract. Took about 10-12min till it completed to 100%.
A funny side note.....when running this on My Nexus 5 it would always freeze between 90-93? and after about an hour of being frozen I would do a hard reboot. On a Nexus 6 I would install it on, same thing but if I didn't wait 90+min I couldn't later manually install chroot or any metapackages.
After install finishes reboot your phone. Once rebooted I opened up From Toolbox Pro and used Root Browser to open the Hammerhead install zip. Once opened I extracted bootanimation.zip from system/media and Hammerheadwallpaper from wallpaper.
Go to Boot Animations in Rom Toolbox Pro, choose local and you can either install bootanimation.zip as it is, or choose resize and change the framerate up to 40.
Then open wallpaper chooser from your desktop and choose Hammerheadwallpaper from your extracted folder.
Finally open the NetHunter app and click install chroot. Once it verifies it already is then choose install metapackage. I always choose the forensics package.
Once that is installed go ahead and reboot your newly modded phone with a working Kali Linux install on it.
So does this mean that other ROMs meant for the Nexus 5 could more or less function on the R1?
wh00p said:
So does this mean that other ROMs meant for the Nexus 5 could more or less function on the R1?
Click to expand...
Click to collapse
I'm not a kernel person and that's the only thing that didn't work, was Kali dirty kernel changing.
I honestly can't answer that but seems plausible to me if someone can figure out the kernel thing.
Sent from my BLU R1 HD using XDA Labs
wh00p said:
So does this mean that other ROMs meant for the Nexus 5 could more or less function on the R1?
Click to expand...
Click to collapse
this isnt a rom it's a linux system you flash ON TOP of the n5 stock rom, so no
This is incredible, thank you for sharing!
I had my hopes up at first, but now I'm getting skeptical. If a kernel port wouldn't work, how can this boot considering the differences between mediatek and Qualcomm?
Unless that just doesn't even matter at all, considering its like a virtual machine computer-inside-a-computer
jasonmerc said:
I had my hopes up at first, but now I'm getting skeptical. If a kernel port wouldn't work, how can this boot considering the differences between mediatek and Qualcomm?
Unless that just doesn't even matter at all, considering its like a virtual machine computer-inside-a-computer
Click to expand...
Click to collapse
There is a universal kernel option in setup. Like I said though it didn't flash the kernel to kalidirty kernel. Everything else worked though. With the views I'm sure someone else can verify they got it working as well.
blu kernel source, binaries available?
Are the blu kernel source, binaries available to try and create a custom ROM?
That's a nice option!
I was actually looking at https://www.pwnieexpress.com/products/pentesting-community-editions yesterday which may be another cool alternative to this one, to see if there was a way to build this for the Blu.
I don't think the Nexus 5 image will work out of the box but there are detailed instructions on how to build a custom rom too, maybe when the device-tree etc is working for CM we will be able to give it a try.
(also the lack of USB OTG will be very detrimental)
emc2cube said:
That's a nice option!
I was actually looking at https://www.pwnieexpress.com/products/pentesting-community-editions yesterday which may be another cool alternative to this one, to see if there was a way to build this for the Blu.
I don't think the Nexus 5 image will work out of the box but there are detailed instructions on how to build a custom rom too, maybe when the device-tree etc is working for CM we will be able to give it a try.
(also the lack of USB OTG will be very detrimental)
Click to expand...
Click to collapse
have you done anymore looking into the AOPP ?
wfandreas said:
have you done anymore looking into the AOPP ?
Click to expand...
Click to collapse
Yes, but no success so far.
HeeyMaan said:
I was looking at how close my Nexus 5 really is to my R1 HD, and besides the obvious Qualcomm MTK thing they are amazingly similar.
I took the official Hammerhead NetHunter 3.0 Marshmallow zip and put it on my external and card.
I then did a factory reset including dalvik and cache in TWRP.
Installed SuperSU and booted my phone. I then installed Busybox Pro and rebooted back into TWRP.
Once in TWRP I clicked install and chose my saved nethunter-hammerhead-marshmallow-3.0.zip
It will open the Aroma installer. On the first screen click everything except the RF Analyzer, MAKE SURE YOU HAVE THE OLDER VERSION OF SUPERSU CHECKED TO INSTALL AS WELL.
On the next screen click everything but custom boot screen and custom wallpaper.
Click next and be patient while it installs everything, extracts the chroot image, and verifies the extract. Took about 10-12min till it completed to 100%.
A funny side note.....when running this on My Nexus 5 it would always freeze between 90-93? and after about an hour of being frozen I would do a hard reboot. On a Nexus 6 I would install it on, same thing but if I didn't wait 90+min I couldn't later manually install chroot or any metapackages.
After install finishes reboot your phone. Once rebooted I opened up From Toolbox Pro and used Root Browser to open the Hammerhead install zip. Once opened I extracted bootanimation.zip from system/media and Hammerheadwallpaper from wallpaper.
Go to Boot Animations in Rom Toolbox Pro, choose local and you can either install bootanimation.zip as it is, or choose resize and change the framerate up to 40.
Then open wallpaper chooser from your desktop and choose Hammerheadwallpaper from your extracted folder.
Finally open the NetHunter app and click install chroot. Once it verifies it already is then choose install metapackage. I always choose the forensics package.
Once that is installed go ahead and reboot your newly modded phone with a working Kali Linux install on it.
Click to expand...
Click to collapse
Which supersu did you install ?
HeeyMaan said:
I was looking at how close my Nexus 5 really is to my R1 HD, and besides the obvious Qualcomm MTK thing they are amazingly similar.
I took the official Hammerhead NetHunter 3.0 Marshmallow zip and put it on my external and card.
I then did a factory reset including dalvik and cache in TWRP.
Installed SuperSU and booted my phone. I then installed Busybox Pro and rebooted back into TWRP.
Once in TWRP I clicked install and chose my saved nethunter-hammerhead-marshmallow-3.0.zip
It will open the Aroma installer. On the first screen click everything except the RF Analyzer, MAKE SURE YOU HAVE THE OLDER VERSION OF SUPERSU CHECKED TO INSTALL AS WELL.
On the next screen click everything but custom boot screen and custom wallpaper.
Click next and be patient while it installs everything, extracts the chroot image, and verifies the extract. Took about 10-12min till it completed to 100%.
A funny side note.....when running this on My Nexus 5 it would always freeze between 90-93? and after about an hour of being frozen I would do a hard reboot. On a Nexus 6 I would install it on, same thing but if I didn't wait 90+min I couldn't later manually install chroot or any metapackages.
After install finishes reboot your phone. Once rebooted I opened up From Toolbox Pro and used Root Browser to open the Hammerhead install zip. Once opened I extracted bootanimation.zip from system/media and Hammerheadwallpaper from wallpaper.
Go to Boot Animations in Rom Toolbox Pro, choose local and you can either install bootanimation.zip as it is, or choose resize and change the framerate up to 40.
Then open wallpaper chooser from your desktop and choose Hammerheadwallpaper from your extracted folder.
Finally open the NetHunter app and click install chroot. Once it verifies it already is then choose install metapackage. I always choose the forensics package.
Once that is installed go ahead and reboot your newly modded phone with a working Kali Linux install on it.
Click to expand...
Click to collapse
what command it that last pic?
wfandreas said:
Which supersu did you install ?
Click to expand...
Click to collapse
Originally I installed the one off the Google play store and then pro off the store as well.
Once installing nethunter I used the older supersu that comes in the zip.
wfandreas said:
what command it that last pic?
Click to expand...
Click to collapse
That's the bootup from vnc. You have to go set your passwords and boot into it.
HeeyMaan said:
That's the bootup from vnc. You have to go set your passwords and boot into it.
Click to expand...
Click to collapse
thank you, I did the same install, works well.
noticing that flashing font files as I did on my OP3 using TWRP-seems ineffective.
I also tried the Midnight Magisk module and installing via terminal, this was also ineffective.
Are the fonts handled differently on Android 9?
Could this be because flashing to A/B slots?
I would think the slots are not the issue as the install from Midnight is done while in the OS via terminal
and no, I am not using the slate font and wondering why flashing over roboto is not changing my system font.
I am using roboto...
naxalite971 said:
noticing that flashing font files as I did on my OP3 using TWRP-seems ineffective.
I also tried the Midnight Magisk module and installing via terminal, this was also ineffective.
Are the fonts handled differently on Android 9?
Could this be because flashing to A/B slots?
I would think the slots are not the issue as the install from Midnight is done while in the OS via terminal
and no, I am not using the slate font and wondering why flashing over roboto is not changing my system font.
I am using roboto...
Click to expand...
Click to collapse
Try one of the font magisk modules from the magisk download in magisk app.(ex ubuntu font) I made one for myself by editing one I downloaded using 7 zip on my computer. Only issue with Android 9 is you cannot change Google app that use their new font bc the new Google sans is built into Google apps now