Bootloop after installing Layers & unable to find /system/vendor/overlay/ with TWRP
Hi,
I've installed Layers and messed with various themes for the past few weeks without encountering any issue, until this morning. Indeed, I tried to apply a new theme (Evolve UI, if you'd like to know) which caused my Pixel C to go into bootloops.
Now, having some experience with Layers on my phone, I know you're supposed to boot into TWRP, then go to Advanced > File manager and remove the bad overlay apk from /system/vendor/overlay/ to fix the bootloops. But, here's the problem : the TWRP File manager shows my /system/ folder empty, thus I am unable to delete the faulty apk ...
Does anyone know where the overlays are installed on the Pixel C, and how to recover from an incompatible layer ?
Thanks in advance !
Did you mount the system partition while in TWRP? ?
Sent from my Pixel C using Tapatalk
Just ran into this myself, you only need to mount Vendor and the location is /vendor/overlay, just rename the overlay folder and you're good to go!
Sent from my Nexus 6 using Tapatalk
Aaand now I feel dumb. I ended up reflashing the factory system.img, which took me way longer than expected
But can confirm, the /overlay/ folder shows up in /vendor/ when mounted ... It'll save me the trouble next time ! Thank you mate
hahaha you're welcome!
Related
SystemUI keeps crashing when it tries to restart, making my phone completely unusable. I'm not able to flash another ROM at the moment so what I'd like to try is deleting the app data for SystemUI (wiping cache and dalvik didn't work). I have Team Win Recovery so I'm able to access the filesystem to delete files.
Can anyone suggest which file(s) I should look for?
restore a backup
beekay201 said:
restore a backup
Click to expand...
Click to collapse
I want to keep my most recent files. I took some photos today and they didn't get a chance to instant upload. I can wait a few days until I get to a computer I can use ADB on to push a ROM.
Sounds like you don't need a working device.
a maguro wrote this.
Use adb to remove /data/data/com.android.systemui/ folder
Hey guys! Big news!
I've fixed the problem, well.. sort of.
I will edit the post If I had something else to test.
1. Uninstalled Android System Webview and installed the one that is present in the Play Store (I can't select it for Webview Implementation though)
2. Launched YouTube app and showed a green screen no matter what the quality is.
3. Tried Chrome and the video works well without any freezes.
Anybody having trouble mounting /System in 5.0.1? es explorer can't write to it and when I use terminal emulator to mount it's still no go. ?
I use ScriptManager. It has the auto mount system partition as needed feature working for Samsung SELinux but it occasionally has an issue mounting as ro after writing. Just reboot. The prompt will keep popping up with "Not recommended" and something else like continue or default or recommended, can't recall. But with stock kernel, the only choice is "Not recommended" and reboot when done. No problem writing. Can't even use advanced mode to mount system as ro when it fails. Just reboot.
I just sent an update to the developer yesterday. He had sent me a development apk last Christmas to get the icon sizing issue corrected; mismatched to text on the Note 4, resizing the text makes the icons tiny. He fixed that in development but hasn't released it yet.
Are you talking about mounting system in a root file browser app? If so, use root explorer. It never fails.
tx_dbs_tx said:
Are you talking about mounting system in a root file browser app? If so, use root explorer. It never fails.
Click to expand...
Click to collapse
Yes. Got file Explorer going but still can't get any of the reboot menu apps to go with your stock L roms. Stock tar yes... I dunno.
jhill110 said:
Yes. Got file Explorer going but still can't get any of the reboot menu apps to go with your stock L roms. Stock tar yes... I dunno.
Click to expand...
Click to collapse
Do u want me to upload the 4 way reboot mod for my deodexed rom? I have that done already.
Edit: Here you go. Pushh this android.policy.jar to system/framework. You might get a freeze & reboot but once you hot swap it if the system freezes then recovers, just copy & paste it one more time then set permissions & reboot again.
tx_dbs_tx said:
Do u want me to upload the 4 way reboot mod for my deodexed rom? I have that done already.
Edit: Here you go. Pushh this android.policy.jar to system/framework. You might get a freeze & reboot but once you hot swap it if the system freezes then recovers, just copy & paste it one more time then set permissions & reboot again.
Click to expand...
Click to collapse
Thanks tx, your my hero! Still scratching my head tho... Running your rom completely from scratch... Total wipe of everything. Thanks again.
Edit: Awesome menu. Took one reboot and went through the "android is upgrading" for 15 minutes but it's working great.
Thanks again! :thumbup:
samep said:
I use ScriptManager. It has the auto mount system partition as needed feature working for Samsung SELinux but it occasionally has an issue mounting as ro after writing. Just reboot. The prompt will keep popping up with "Not recommended" and something else like continue or default or recommended, can't recall. But with stock kernel, the only choice is "Not recommended" and reboot when done. No problem writing. Can't even use advanced mode to mount system as ro when it fails. Just reboot.
I just sent an update to the developer yesterday. He had sent me a development apk last Christmas to get the icon sizing issue corrected; mismatched to text on the Note 4, resizing the text makes the icons tiny. He fixed that in development but hasn't released it yet.
Click to expand...
Click to collapse
May be off topic but I wanted to update the status of this app. The developer is focusing on lollipop issues and updated the application a couple of times recently. I appreciate the fact he's responded to the issues that were present with Samsung stock kernel and icon to text proportionality with Note 4. It keeps getting better; squashing bugs and adding features. I have the pro version so long term support is a wonderful thing regarding a purchase.
So I installed miui 10 days ago to try it. Now I'm on jaguar with the last Magisk release. I was searching where slim Theme engine stored apks when I saw a folder named miui at this place : /storage/emulated/miui. So I tried to remove it but I can't. Total commander has all root rights. See attachment to see the error message. Could you help me finding a solution to remove it please? I'm scared that it can be a scam or something like that.
Thanks in advance
PS : I did a full wipe and only restored my data backup taken before installing miui
**** forgot screenshot ahaha
Have you tried booting into TWRP and deleting the MIUI folder using the built-in file manager?
Up
Same problem.
Twrp dont see nothing inside emulated folder so inpossible to remove MIUI folder
Guys, I'm having a tough time deleting a file or two that were recently installed in the root's /product folder and I guess I don't understand what I am doing wrong, or what security is in place to prevent me from doing this. I would greatly appreciate any help or suggestions here. I cannot change permissions to make the folder recursively rw. I first started with Root Explorer and Solid Explorer. Both are capable of changing permissions but failed saying it was a "system folder". I used terminal to setenforce to 0, and tried with su from terminal and could not manually change folder permissions using chmod either. I thought maybe TWRP would be the answer, so I booted recovery and tried mounting the data partition (I think it's on data) and used file manager to browse to the folder, but I cannot see the contents of the folder nor can I delete it. What am I missing here? Is the TWRP mount function busted atm? Last night I reflashed November's update with the -w thinking it might "overwrite" the folder, but there was no joy there either. I do have a couple of TWRP backups of the data folder and that is my next step. Before I apply the December image tonight, I'm going to restore the most recent /data partition backup. There has to be a way to get control of that folder and it's contents but so far it has eluded me.
Cheers and TIA.
As far as I'm aware, the only way currently to write to the product partition is to fastboot flash it. I've went as far as to modify TWRP fstab to mount it in recovery and use the file manager to replace the bootanimation only to have it either never write properly or for it to "correct" itself. Not sure which happened.
Sent from my Pixel 3 XL using Tapatalk
I appreciate the response... anything helps. Product is a folder in root also and that is what I am trying to access. Unless there is some kind of symlink linking that product folder to the product partition. I don't know. When I flashed the full image yesterday I would have thought that partition.img (nested in the zipfile) would have been flashed, too. Maybe I can try fastboot formating the product partition. Can't hurt. Thanks again!
Edit: Just found this thread where you also contributed. I'll try to flash that partition with the partition.img and see what happens. I just want to reset it to stock.
superchilpil said:
As far as I'm aware, the only way currently to write to the product partition is to fastboot flash it. I've went as far as to modify TWRP fstab to mount it in recovery and use the file manager to replace the bootanimation only to have it either never write properly or for it to "correct" itself. Not sure which happened.
Click to expand...
Click to collapse
I flashed product.img first and it rendered the phone unbootable... corrupt. I then went back into TWRP and wiped system and ran the flash-all script in fastboot and re-rooted. The net result is the product folder is unchanged. Everything is up and running just fine. That folder is just untouchable for me so far. Next I will format data and re-flash. I didn't fully understand what you meant about the custom kernel being the solution but so far EX is not working. May reach out to flar2 and see if he can make some kind of change to his kernel to support mounting this partition? Thanks again.
v12xke said:
I flashed product.img first and it rendered the phone unbootable... corrupt. I then went back into TWRP and wiped system and ran the flash-all script in fastboot and re-rooted. The net result is the product folder is unchanged. Everything is up and running just fine. That folder is just untouchable for me so far. Next I will format data and re-flash. I didn't fully understand what you meant about the custom kernel being the solution but so far EX is not working. May reach out to flar2 and see if he can make some kind of change to his kernel to support mounting this partition? Thanks again.
Click to expand...
Click to collapse
Yeah I have yet to be able to mount the product image to modify it, but I haven't tried all that much lately. I'm pretty sure it's fixable with a kernel edit but that's beyond my ability, and even if I could I have a 8 year old laptop that wouldn't be able to build it.
What are you trying to accomplish? The bootanimation?
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
Yeah I have yet to be able to mount the product image to modify it, but I haven't tried all that much lately. I'm pretty sure it's fixable with a kernel edit but that's beyond my ability, and even if I could I have a 8 year old laptop that wouldn't be able to build it. What are you trying to accomplish? The bootanimation?
Click to expand...
Click to collapse
No, I see boot animation in that folder, and yes we all used to use it, but this time it's just an apk from apkmirror that wrote to that system partition (don't ask me how) and now I can't uninstall or update it. com. breel.wallpapers18. I tried to uninstall it using pm uninstall, but it uninstalled it for user 0 so it remains as a system app, and not available to me. I can't uninstall it completely or upgrade... or even use it! It's just a fk'in set of Google live wallpapers I like, but now want to re-set. Waay too much time spent on this so I'm (just about) ready to flush and start over. Every year Google makes it harder for us (fans) to customize our own phones. wtf? Pissed.
I have Magisk rooted global 10.0.15 rom on my OnePlus 7T.
While looking around I found the following apk - please reference attached screenshot.
I can't delete these apks and mount r/w does nothing; nor changing permissions either.
So, is thier any way to delete these apks?
Will deleting these apks have any side effects?
Haven't determined if a Magisk module could exist to deal with this (r/w permissions)?
Will I have to figure out abd commands on Windows 10 or live Linux CD/USB drive? It's it any easier using Linux?
Thanks
Use ADB or magisk debloat module, otherwise no way.
Just freeze them.. I'm guessing it's not a storage issue but a personal bloat-ware issue that you don't want those apks running at all... So the easiest way for that to happen is to just put them on ice.
Sorry to revive a most likely dead issue....
But...
I've only used TWRP on my OnePlus once... Lost TWRP with OTA update - so I really didn't get much of a chance to familiarize myself with TWRP on any OnePlus - like I've previously done with all my prior Samsung's.
Having said all that: I think I remember TWRP has a storage/file manager?
If that's correct... Then can I drill down into the OOS and delete whatever I like as opposed to the previously provided solutions (and yeah I've used both solutions with thanks
For freezing apps I'm loving SD Maid and enjoy the additional features of that app and worth much more than I paid for it and it's wonderful that it's still seems to be maintained over the years....