Related
Again I'm not the dev of these custom recovery. Just that I pack them together and modified a theme to work with our ZR phone.
Installation procedure:
1. Just unzip lockeddualrecovery2.6.0-RELEASE.windows.zip in your PC and run either supersu.bat or superuser.bat.
2. After all files are installed, your phone should reboot automatically into CWM.
3. If you're unable to see CWM and your phone just reboot normally to Android, then you might be suffering from remount-reboot issue. Just run the fix for remount-reboot first.
How to enter CWM/TWRP:
1. During a reboot, when the LED turns green, press VOL-UP for CWM or VOL-DOWN for TWRP. The LED will then turn purple before entering the selected custom recovery.
How to apply the proper theme in TWRP to fix UI issue:
1. Copy the TWRP_theme_720_play.zip into /sdcard/TWRP/theme and rename it as ui.zip
How to restore stock recovery
1. Delete the following files:
/system/bin/recovery.twrp.cpio.lzma (or .tar)
/system/bin/recovery.cwm.cpio.lzma (or .tar)
/system/bin/charger
/system/bin/ric
/system/bin/chargemon
/system/bin/dualrecovery.sh
2. Inside /system/bin/ rename chargemon.stock to chargemon
3. Change permission for chargemon (chmod 755 chargemon)
Credits:
- Team Win for TWRP
- ClockWorkMod for CWM
- z31s1g for the beautiful Holofied theme. I only rescaled some images and edit the xml for 720p display.
excuse me for my ignorance noobish question, but why do we need a dual boot recovery? whats special about twrp if we already have a fine working cwm? or perhaps if one prefers twrp why whould be need both?
shteren said:
excuse me for my ignorance noobish question, but why do we need a dual boot recovery? whats special about twrp if we already have a fine working cwm? or perhaps if one prefers twrp why whould be need both?
Click to expand...
Click to collapse
This is actually a valid question. Personally, I prefer to use TWRP since it's touch based and support more functions. Maybe someone does need CWM for some reasons.
Working fine on Xperia ZR C5502 67 Firmware & able to use TWRP recovery
anthonythangaraj said:
Working fine on Xperia ZR C5502 67 Firmware & able to use TWRP recovery
Click to expand...
Click to collapse
CWM part is working fine but fail to fix ui issue on TWRP part.
Copying the ui.zip to sdcard/TWRP/theme not solved the problem.
Can someone help me to fix this.
:crying::crying:
PS. Xperia ZR C5502 with C5503 10.1.1.A.1.310 firmware.
njsdante said:
CWM part is working fine but fail to fix ui issue on TWRP part.
Copying the ui.zip to sdcard/TWRP/theme not solved the problem.
Can someone help me to fix this.
:crying::crying:
PS. Xperia ZR C5502 with C5503 10.1.1.A.1.310 firmware.
Click to expand...
Click to collapse
Are you using the INTERNAL SD card to store the ui.zip?
What do you see in TWRP? Similar to the Holofied them in this link?
itandy said:
Are you using the INTERNAL SD card to store the ui.zip?
What do you see in TWRP? Similar to the Holofied them in this link?
Click to expand...
Click to collapse
TWRP folder is on internal sd card so i copy the ui.zip into internal sd/TWRP/theme.
But when i entering into TWRP mode, i can only see the partial screen which contain install, wipe and backup buttons in big icon.
And no way to get out of recovery mode except removing the battery.
njsdante said:
TWRP folder is on internal sd card so i copy the ui.zip into internal sd/TWRP/theme.
But when i entering into TWRP mode, i can only see the partial screen which contain install, wipe and backup buttons in big icon.
And no way to get out of recovery mode except removing the battery.
Click to expand...
Click to collapse
So it seems TWRP is unable to read the theme file. Can you check if your ui.zip file is corrupted?
MD5 checksum is: 20B934657DB6E7F19E9D603DA7529B35
FXP compatible?
Does this work with FXP?
gmengass said:
Does this work with FXP?
Click to expand...
Click to collapse
Actually I don't know. Please report back if you have answer.
itandy said:
So it seems TWRP is unable to read the theme file. Can you check if your ui.zip file is corrupted?
MD5 checksum is: 20B934657DB6E7F19E9D603DA7529B35
Click to expand...
Click to collapse
I don't really know how to check the theme file is corrupted or not.( sorry for my noobness)
Can you please tell me how to do it.
njsdante said:
I don't really know how to check the theme file is corrupted or not.( sorry for my noobness)
Can you please tell me how to do it.
Click to expand...
Click to collapse
I guess the easiest way is to use something like 7zip in PC and use the Test function.
Working on my device flalessly
Sent from my C5502 using XDA Premium 4 mobile app
Shh I want to modify this package in order to compile my own flasher package with twrp only. But that cpio archive is making me crazy since I can't repack it in this format.
Sent from my LG-P970 using xda app-developers app
word of advice.dont update busy box after installing this.it will make this to stop working
TWRP is working perfectly. Thanks very much
i tried with TWRP manager .it didnt work.but when in recovery it works well
both are working great , thanks a lot .
i have a question, where does CWM save the nandroid backups? i can't seem to find the backup i just made.
single said:
both are working great , thanks a lot .
i have a question, where does CWM save the nandroid backups? i can't seem to find the backup i just made.
Click to expand...
Click to collapse
ClockworkMod stores its NANDroid backup folders at this location:
/mnt/shell/emulated/clockworkmod/backup
su1979 said:
ClockworkMod stores its NANDroid backup folders at this location:
/mnt/shell/emulated/clockworkmod/backup
Click to expand...
Click to collapse
any idea how to change that path to be in SDcard instead?
Hi everyone
I'm trying to get the infamous GPS Location Spoofer installed as a system app on my rooted HTC phone, but so far no luck, so I figured I would try to ask for help here, in case anyone went through a similar situation, or knows what I've been doing wrong. This is what I tried so far:
Installed the app from Google App store, and using File Explorer with root , tried to move the app folder to /system/app or /system/priv-app, , but pasting the folder there would result in an instant reboot and the app would not be there.
So I installed lucky patcher , and using apk downloader, downloaded the apk file from the App Store, copied it over to the phone, and used the "Rebuild and Install" option, choosing the option to install it as a system app , and it would process it and say that the installation was sucessfull, needs to reboot to complete, but after the reboot the app would not be there (not only not showing on the apps list, but navigating to the /system folder with File Explorer and checking app and priv-app I could verify that it was not installed).
SO I tried to use adb shell to do the work , and this is what I did:
mount -o remount /dev/block/mmcblk0p35 /system
to mount the /system filesystem as read write , and it did
cp /sdcard/Download/com.incorporateapps.fakegps.fre-55.apk /system/app
to copy the file under /system/app
chmod 644 com.incorporateapps.fakegps.fre-55.apk
to set the permissions as required
and reboot the phone, but after the reboot, the file would not be there. I tried also to create a folder under /system/app named com.incorporateapps.fakegps.fre-55, move the apk inside; installing normally , changing the mount point to read-write and moving it from /data/app to /system/app or /system/priv-app using the shell and chaning ownership / permissions , but the app will not stick , either rebooting or just re-mounting the filesystem as read-only again will cause everything that was done to be lost; and after trying any of the above one time, doing it for a second time would cause the phone to reboot.
I figure that there must be an image of the /system mount point somewhere , which gets installed every time there is a remount to read-only or reboot , or something of that nature, that will cause any changes made under /system to be lost. Maybe I'm wrong but it seems to be related to HTC phones, since there's load of people doing it on other models without issues, or maybe I'm doing something wrong, since I'm no android expert
Does anyone knows what could be the issue, or what can I do ? I searched the net quite a bit for a solution to no avail (here as well), any help is appreciated
Thanks
sasteck said:
Hi everyone
I'm trying to get the infamous GPS Location Spoofer installed as a system app on my rooted HTC phone, but so far no luck, so I figured I would try to ask for help here, in case anyone went through a similar situation, or knows what I've been doing wrong. This is what I tried so far:
Installed the app from Google App store, and using File Explorer with root , tried to move the app folder to /system/app or /system/priv-app, , but pasting the folder there would result in an instant reboot and the app would not be there.
So I installed lucky patcher , and using apk downloader, downloaded the apk file from the App Store, copied it over to the phone, and used the "Rebuild and Install" option, choosing the option to install it as a system app , and it would process it and say that the installation was sucessfull, needs to reboot to complete, but after the reboot the app would not be there (not only not showing on the apps list, but navigating to the /system folder with File Explorer and checking app and priv-app I could verify that it was not installed).
SO I tried to use adb shell to do the work , and this is what I did:
mount -o remount /dev/block/mmcblk0p35 /system
to mount the /system filesystem as read write , and it did
cp /sdcard/Download/com.incorporateapps.fakegps.fre-55.apk /system/app
to copy the file under /system/app
chmod 644 com.incorporateapps.fakegps.fre-55.apk
to set the permissions as required
and reboot the phone, but after the reboot, the file would not be there. I tried also to create a folder under /system/app named com.incorporateapps.fakegps.fre-55, move the apk inside; installing normally , changing the mount point to read-write and moving it from /data/app to /system/app or /system/priv-app using the shell and chaning ownership / permissions , but the app will not stick , either rebooting or just re-mounting the filesystem as read-only again will cause everything that was done to be lost; and after trying any of the above one time, doing it for a second time would cause the phone to reboot.
I figure that there must be an image of the /system mount point somewhere , which gets installed every time there is a remount to read-only or reboot , or something of that nature, that will cause any changes made under /system to be lost. Maybe I'm wrong but it seems to be related to HTC phones, since there's load of people doing it on other models without issues, or maybe I'm doing something wrong, since I'm no android expert
Does anyone knows what could be the issue, or what can I do ? I searched the net quite a bit for a solution to no avail (here as well), any help is appreciated
Thanks
Click to expand...
Click to collapse
Are you using stock kernel?
donkeykong1 said:
Are you using stock kernel?
Click to expand...
Click to collapse
Yes, kernel is the default that comes with the phone (3.4.10.g96cae32 , android 5.0.2)
sasteck said:
Yes, kernel is the default that comes with the phone (3.4.10.g96cae32 , android 5.0.2)
Click to expand...
Click to collapse
And there's your problem. Stock kernel has system write protection, so you can't mount system as writeable. You can, but after reboot, it comes back to read only, and nothing will stick into system partition. You have 2 choices now - disable system write protection on stock kernel, or flash a custom kernel
donkeykong1 said:
And there's your problem. Stock kernel has system write protection, so you can't mount system as writeable. You can, but after reboot, it comes back to read only, and nothing will stick into system partition. You have 2 choices now - disable system write protection on stock kernel, or flash a custom kernel
Click to expand...
Click to collapse
oh I see.. didn't know about that , thanks! I'll check about disabling system write protection , otherwise look for a custom kernel, never did it before but will give it a try
donkeykong1 said:
And there's your problem. Stock kernel has system write protection, so you can't mount system as writeable. You can, but after reboot, it comes back to read only, and nothing will stick into system partition. You have 2 choices now - disable system write protection on stock kernel, or flash a custom kernel
Click to expand...
Click to collapse
Shhhhhh, don't help him, he's going to steal everyone's pokemons
Sent from my HTC One using XDA Labs
alray said:
Shhhhhh, don't help him, he's going to steal everyone's pokemons
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Ooooohhh... That's why he's trying the spoofer.... If I knew, I wouldn't help at all [emoji6]
donkeykong1 said:
Ooooohhh... That's why he's trying the spoofer.... If I knew, I wouldn't help at all [emoji6]
Click to expand...
Click to collapse
Sorry you feel that way, but I appreciate the help anyway. This is something that I never tampered with before, so I still had some doubts about the process, but I am liking the whole thing and will install a custom rom on my own phone, been reading about the Ressurection rom and it looks very nice, will try it as soon as I'm better informed
sasteck said:
Sorry you feel that way, but I appreciate the help anyway. This is something that I never tampered with before, so I still had some doubts about the process, but I am liking the whole thing and will install a custom rom on my own phone, been reading about the Ressurection rom and it looks very nice, will try it as soon as I'm better informed
Click to expand...
Click to collapse
That was a joke mate. I don't care what you do with your phone, but I'm here to help if I can [emoji6]
This is an extension of my Android Oreo Pixel Mod thread, found here https://forum.xda-developers.com/nexus-6p/themes-apps/zip-android-oreo-pixel-mod-t3661388
This thread is for the users who want the Pixel Mod but also the ability to use Substratum. Why does my original mod break substratum? It modifies the framework-res.apk. The pixel no longer gets it's features from a modified framework-res.apk. It gets it from a theme. Making a pixel mod work with Substratum now requires making the 6P do the same thing as the Pixel. However, to simplify the mod I mimiced the features by modifying the framework-res.apk. This breaks Substratum. Following this walkthrough will enable the Pixel Theme on your 6P without modifying your framework-res.apk. Exactly how Google does it with the Pixel. (Exciting right?) This will allow the use of Substratum. This is what I am using and I can verify that substratum works.
Here'es the first thing: The files that you will need.
1)My original Pixel mod (flashable) -- https://www.androidfilehost.com/?fid=961840155545590555
2)Stock framework (flashable) -- https://www.androidfilehost.com/?fid=673368273298981491
3)Pixel Theme files (NOT flashable) -- https://www.androidfilehost.com/?fid=889764386195925591
4)You need to be ROOTED
5)You need a file manager that has root functions and can edit file permissions. (I.E.: Amaze File Manager, EX File Explorer, MT Manager)
Here are the steps. This is as simple as I can make it at the moment. It's not too complicated, but if you are a beginner with this stuff make sure to make a back up. Even if you're not. Make a backup. You are responsible for anything that happens to your device and making a backup will save everybody.
Step 1) Download all files onto your internal storage
Step 2) Extract the contents of "NO FLASH Pixel Mod + Substratum.zip". You should have a build.prop file and a folder called "overlay"
Step 3) Move that folder in your Vendor folder. Leave behind the "build.prop" If you go to your root directory you should see the folder "Vendor". Along with folders like "sys" and "system". But you don't want those. You want "Vendor".
Step 4) Make sure the permissions are accurate. The 2 apk files that you will find inside the "overlay" folder (the framework file and the pixel.apk file you'll find in the "pixel" folder inside the "overlay" folder) are set to 644. The folders "overlay" and "pixel" ("pixel" is found within the "overlay" folder) needs to be set to 755.
Step 5) Edit the build.prop file found within your vendor to include the lines that are found in the included build.prop (See footer)
Step 6) Reboot into TWRP
Step 7) In this order flash "Android OPR6 Pixel Mod 6P.zip" and then "Stock Framework.zip"
Step 8) Reboot
Step 9) If you don't see Round Icons you may need to clear Pixel Launcher Data
If SystemUI is crashing after reboot, reboot into TWRP and mount the vendor partition. Then delete the overlay folder and that'll solve the issue
If you followed those correctly you should have now have a Pixel Theme (Accent color, Night Mode, and Round icons) with compatibility with Substratum.
*footer*
ro.opa.eligible_device=true
ro.com.google.ima.theme=5
ro.boot.vendor.overlay.theme=com.google.android.theme.pixel
Followed each step as explained. Changed permissions from 644 to 755. Blue accent gone and stock teal is back. Default round icons gone and the ever so stupid square ones back. And Substratum's still broken. Wonder where I went wrong!!!
Edit : Additional to that, there are 'n' number of folders namely ".." with today's date as modified date. Each ".." folder contains multiple ".." folders and it just keeps going on and on....
Never faced this earlier. Have I screwed up something???
Suhas_JS said:
Followed each step as explained. Changed permissions from 644 to 755. Blue accent gone and stock teal is back. Default round icons gone and the ever so stupid square ones back. And Substratum's still broken. Wonder where I went wrong!!!
Edit : Additional to that, there are 'n' number of folders namely ".." with today's date as modified date. Each ".." folder contains multiple ".." folders and it just keeps going on and on....
Never faced this earlier. Have I screwed up something???
Click to expand...
Click to collapse
That is interesting. The folder thing is weird. Did you set the files "build.prop", "framework_generated.......apk", and "Pixel.apk" to 644? The files needed to be 644 and the folders needed to be 755
krisyarno said:
That is interesting. The folder thing is weird. Did you set the files "build.prop", "framework_generated.......apk", and "Pixel.apk" to 644? The files needed to be 644 and the folders needed to be 755
Click to expand...
Click to collapse
Should I be reflashing Vendor image to set the folders right???
May be I can retry the whole stuff again?
I am ready to be the specimen for experiments :laugh:
Is there any change Pixel Theme alone can be enabled on Nexus using ADB overlay service commands that were explained recently on main XDA page?
Suhas_JS said:
Should I be reflashing Vendor image to set the folders right???
May be I can retry the whole stuff again?
I am ready to be the specimen for experiments :laugh:
Click to expand...
Click to collapse
Definitely. I'm redoing the steps myself and I'm running into a weird bump. I'm going to revise it a little maybe. Definitely a good idea to reflash the vendor and take another shot though!
Suhas_JS said:
Should I be reflashing Vendor image to set the folders right???
May be I can retry the whole stuff again?
I am ready to be the specimen for experiments :laugh:
Click to expand...
Click to collapse
Try setting build.prop to 600 instead of 644
revanmj said:
Is there any change Pixel Theme alone can be enabled on Nexus using ADB overlay service commands that were explained recently on main XDA page?
Click to expand...
Click to collapse
I believe so. Placing the overlay folder found from Pixel's vendor to the same place on the 6P should give the 6p the ability to use all the overlay service commands
krisyarno said:
Try setting build.prop to 600 instead of 644
Click to expand...
Click to collapse
Downloading the latest vendor image. Will keep you updated....
Suhas_JS said:
Downloading the latest vendor image. Will keep you updated....
Click to expand...
Click to collapse
Thanks!
Suhas_JS said:
Downloading the latest vendor image. Will keep you updated....
Click to expand...
Click to collapse
I appreciate your help throughout all of these releases
krisyarno said:
I appreciate your help throughout all of these releases
Click to expand...
Click to collapse
Pleasure's all mine. When we can not do something on our own, the least we could do is to assist someone who is more capable.
Coming back to the point, I am using Amaze & EX Explorer to replace the said files.
Strangely, I am getting various error messages, like "Insufficient space".
Also, everytime I try and copy a folder, it wont show up until I restart the device.
I know this is little too much for you to imagine. I'll may be post a short GIF in some time for you to get a gist of the issue.
Thanks and apologies for the story.
Worked out fine with your instructions, only had to clear data and cache of pixel launcher to get round icons. Thanks!
Tested, substratum works but no night light
syfo said:
Worked out fine with your instructions, only had to clear data and cache of pixel launcher to get round icons. Thanks!
Click to expand...
Click to collapse
Wich permission did you use for the build prop? 600 or 644?
Sent from my Nexus 6P using XDA-Developers Legacy app
Congratulations to me... I think I screwed up my phone. All of a sudden Substratum started working (may be I had done everything alright???). Applied a couple of overlays and voila!!! The phone does a factory reset by itself and get stuck at the Google animation. Interestingly, it's the new animation that came with the OPR6 mod. Don't know where I went wrong. I have currently switched my cell off. Maybe I need to reflash everything again???
bigcelo75 said:
Wich permission did you use for the build prop? 600 or 644?
Click to expand...
Click to collapse
600
Suhas_JS said:
Congratulations to me... I think I screwed up my phone. All of a sudden Substratum started working (may be I had done everything alright???). Applied a couple of overlays and voila!!! The phone does a factory reset by itself and get stuck at the Google animation. Interestingly, it's the new animation that came with the OPR6 mod. Don't know where I went wrong. I have currently switched my cell off. Maybe I need to reflash everything again???
Click to expand...
Click to collapse
I don't believe there is a need to wipe if your phone factory reset itself. There may be a chance that it didn't successfully factory reset. I would reflash stock system.img and stock vendor.img. That should undo everything and let you boot up
noooooo said:
Tested, substratum works but no night light
Click to expand...
Click to collapse
Same here. Is there a fix for that yet @krisyarno?
Sent from my Nexus 6P using XDA-Developers Legacy app[/QUOTE]
Sent from my Nexus 6P using XDA-Developers Legacy app
Not to contradict OP but I used 644 for files (.prop and apk's) and 755 for folders. Also I don't know if it helps but at first I didn't have night light and installed the "pixel" apk (inside the overlay folder), rebooted the device and voila! After that just cleared pixel launcher cache and that took care of the round icons.
Exist an easy way to export magisk module list? Export and import?
Clarifications needed... Which list are you talking about? The entire Magisk repo or just the ones you've installed (I'm gonna guess the latter)? And for what purpose?
Didgeridoohan said:
Clarifications needed... Which list are you talking about? The entire Magisk repo or just the ones you've installed (I'm gonna guess the latter)? And for what purpose?
Click to expand...
Click to collapse
only the one i have installed. full list for backup / reinstall purpose. installed and not active. xposed ha a function to export /import list. I like it.
If you just need a backup, make a backup of the Magisk image (/data/adb/magisk.img). That's where all modules are kept (for now, this might change in a future version of Magisk).
Didgeridoohan said:
If you just need a backup, make a backup of the Magisk image (/data/adb/magisk.img). That's where all modules are kept (for now, this might change in a future version of Magisk).
Click to expand...
Click to collapse
oh. perfect. no problem. can i restore? like in a rom change to a new rom? what is status for enabled disabled module?
simona70 said:
oh. perfect. no problem. can i restore? like in a rom change to a new rom? what is status for enabled disabled module?
Click to expand...
Click to collapse
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
73sydney said:
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
Click to expand...
Click to collapse
Thanks. Providential.
73sydney said:
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
Click to expand...
Click to collapse
Where are the ZIP files located, in case I just want to backup those rather than the img?
oroboros74 said:
Where are the ZIP files located, in case I just want to backup those rather than the img?
Click to expand...
Click to collapse
Zip files are not saved. It gets extracted in to the location as mentioned in this thread. But each time you flash a module the zip file is downloaded in to Download folder of your internal storage. Save it for future use.
Now /data/adb/magisk.img is no more used... What folder must I backup?
Didgeridoohan said:
If you just need a backup, make a backup of the Magisk image (/data/adb/magisk.img). That's where all modules are kept (for now, this might change in a future version of Magisk).
Click to expand...
Click to collapse
Hi how can i find data/adb/magisk/img
Sk7007 said:
Hi how can i find data/adb/magisk/img
Click to expand...
Click to collapse
That's an old post you're quoting, and the last part of it has come true...
All modules are currently stored in /data/adb/modules.
Didgeridoohan said:
That's an old post you're quoting, and the last part of it has come true...
All modules are currently stored in /data/adb/modules.
Click to expand...
Click to collapse
How to backup now then?
Sent from my motorola one power using Tapatalk
Always wondered the same..
73sydney said:
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
Click to expand...
Click to collapse
All modules are currently stored in /data/adb/modules. Would the concept of copying the files back to the correct location still work after a reboot?
rodken said:
All modules are currently stored in /data/adb/modules. Would the concept of copying the files back to the correct location still work after a reboot?
Click to expand...
Click to collapse
I actually havent tried it since the change from the img method
I can tell you i do backup and restore the magisk.db file....i have a Galaxy Active2 Watch, and if it even sniffs root i have to reset the watch and start over to get Samsung Pay working. So i flash the ROM/GApps, then Magisk, reboot and setup the ROM and Magisk, set my Android ID back to the previous one (to avoid having to reset the Watch, and have it connectable in Gear app) then copy the magisk.db to /data/adb, then reboot. Then enable MagiskHide, and hide Magisk Manager. When i restore my apps the Samsung ones are already in the MagiskHide list and Samsung Pay works as before, once i reconnect the watch.
Next time i flash ill try copying back the /data/adb/modules and let you know
rodken
Just a quick update
I was about to flash a new ROM for testing, and thought about doing the test...copy the modules folder from /data/adb, and restore on new ROM and then realised that not all modules im using are going to like that, as some set symbolic links during install and some now use filesystem overlays as well (thinking busybox and Vanced Youtube)
Ive just decided rather than copying im going to stick with what works 100%, and install them by hand one by one
73sydney said:
rodken
Just a quick update
I was about to flash a new ROM for testing, and thought about doing the test...copy the modules folder from /data/adb, and restore on new ROM and then realised that not all modules im using are going to like that, as some set symbolic links during install and some now use filesystem overlays as well (thinking busybox and Vanced Youtube)
Ive just decided rather than copying im going to stick with what works 100%, and install them by hand one by one
Click to expand...
Click to collapse
Thanks for the update.
It seems my android\OBB folder is write protected. I can't install certain apps that need to write to this folder. I can't seem to unlock it and have been trawling Google for solutions.
I can delete the folder, then create a new OBB folder, but I still can't copy a folder into it. I'm using a rooted EU rom if this helps. Thanks
It is rooted device with EU rom on it
Can someone check on their phone if they can copy a file or folder into the obb folder? I'm getting very desperate for a fix
perryano said:
It seems my android\OBB folder is write protected. I can't install certain apps that need to write to this folder. I can't seem to unlock it and have been trawling Google for solutions.
I can delete the folder, then create a new OBB folder, but I still can't copy a folder into it. I'm using a rooted EU rom if this helps. Thanks
It is rooted device with EU rom on it
Click to expand...
Click to collapse
no problem at all..
any magisk modules installed? maybe disable and check
perryano said:
Can someone check on their phone if they can copy a file or folder into the obb folder? I'm getting very desperate for a fix
Click to expand...
Click to collapse
Yes, it works.
I can read/copy/delete every file/folder inside /Android/Obb directory.
Stock MIUI 10 Global.
matchung said:
no problem at all..
any magisk modules installed? maybe disable and check
Click to expand...
Click to collapse
No magisk modules installed. Thank you
I have faced this exact problem a few weeks ago. It started after I flashed a ROM, MiRum if I'm not mistaken. Tried deleting it via TWRP and make a new folder, changing the folder permission, no luck. I don't know how exactly I got my issue resolved, but I think wiping your data (storage) will do. Just backup your data, wipe your device clean, reflash your ROM, restore everything, and you'll be good to go...I guess.
I'm sorry if I can't be of more help to you in this regard.
Enthunk said:
I have faced this exact problem a few weeks ago. It started after I flashed a ROM, MiRum if I'm not mistaken. Tried deleting it via TWRP and make a new folder, changing the folder permission, no luck. I don't know how exactly I got my issue resolved, but I think wiping your data (storage) will do. Just backup your data, wipe your device clean, reflash your ROM, restore everything, and you'll be good to go...I guess.
I'm sorry if I can't be of more help to you in this regard.
Click to expand...
Click to collapse
Thanks for the suggestion. I guess this might have to be the last resort as I can't seem to find any other fix. I have tried the permission stuff in twrp file explorer also and this doesn't help. Cheers
hope this may help: -> http://en.miui.com/thread-2950541-1-1.html
matchung said:
hope this may help: -> http://en.miui.com/thread-2950541-1-1.html
Click to expand...
Click to collapse
Thank you for this. I have seen this and unfortunately on miui 10 this option is not there. The only option for mock sd card is to formal it. There is nowhere to enable/disable it. Not that I can find with developer options also enabled.
have you ever try to toggle "MIUI Optimization"？ will it help?
or you may check the group/permission of the folder, here is mine
6815767 drwxrwx--x 72 root sdcard_rw 4.0K 2019-06-13 10:12 data
6815746 drwxrwx--x 4 root sdcard_rw 4.0K 2019-06-06 18:10 obb
Click to expand...
Click to collapse
matchung said:
have you ever try to toggle "MIUI Optimization"？ will it help?
or you may check the group/permission of the folder, here is mine
Click to expand...
Click to collapse
I will check that now. Where can I check the group/permissions for the holder?
Thank you
I am going with a wipe and reinstall of everything. Hope this works
And a fresh wipe and install fixed it