Database Users

CM 12 5.0 f2fs - looking for assistance

I was able to repack the CM12 rom from the N7 Android Development forum so that it would install to all f2fs partitions... cache, data, AND system. It flashes without error and then I flash m-kernel a72 for f2fs support. The rom boots up and seems fine at first. All the default apps from the rom work except for FILE MANAGER and TERMINAL. I then flashed SuperSu beta 2.27 and root works fine. I installed System App Remover [ROOT] and it also works fine. Then I uninstalled FILE MANAGER and reinstalled it with CM app installer and it still doesn't work.
I'm pretty sure it has something to do with my updater script since I had to whip something up because the original script isn't really usable for this type of install.
If anyone who can work their way around an updater script wants to give it a shot and try to get this to install with everything working properly I can PM you a link to my repacked rom.
TIA for any help with this!
P.S. Not positive if this is the right forum for this. Please move if necessary, and sorry for any inconvenience.

miui 8 v6.6.23 xposed not working

Hey guys can you help me
I tried flashing xposed-v79-sdk22-arm.zip through twrp 3.0.2.0 in miui 8 v6.6.23
for lenovo a6000/plus
But after flashing and installing the apk
It says â??xposed framework version 79 is installed but not activeâ?
What should i do?
And is there any way to change apps files default location to external sd card?

amanu247 said:
I tried flashing xposed-v79-sdk22-arm.zip through twrp 3.0.2.0 in miui 8 v6.6.23. But after flashing and installing the apk, it says “xposed framework version 79 is installed but not active”.
And is there any way to change apps files default location to external sd card?
Click to expand...
Click to collapse
Download the Solwarez' xposed for MIUi from here. First, install the app (as a system or user app, your choice). Then flash the xposed package and after reboot open the xposed installer app and you have to choose install/update for the first time.
And, you may use, app2sd or any such app to store app's data on external sd card.

sasukay said:
Download the Solwarez' xposed for MIUi from here. First, install the app (as a system or user app, your choice). Then flash the xposed package and after reboot open the xposed installer app and you have to choose install/update for the first time.
And, you may use, app2sd or any such app to store app's data on external sd card.
Click to expand...
Click to collapse
I tried this but after flashing all my data lost and miui doesn't support to store apps data on external sd card
Switched to cm 12.1 by ed300

sasukay said:
Download the Solwarez' xposed for MIUi from here. First, install the app (as a system or user app, your choice). Then flash the xposed package and after reboot open the xposed installer app and you have to choose install/update for the first time.
And, you may use, app2sd or any such app to store app's data on external sd card.
Click to expand...
Click to collapse
Thanks bro it worked :good::victory:

you can follow the step here
it might worked, i've tried those step and worked.
good luck.

whitenight22 said:
you can follow the step here
it might worked, i've tried those step and worked.
good luck.
Click to expand...
Click to collapse
It worked for me
Thanks :victory:

[ROM] Evervolv | 7.0.0p1 [AOSP Nougat 7.0.0] [3.4 kernel] [ALPHA] WIFI & 4G

For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Right now the current source we are working on is Nougat(Android 7.0.0).
Current version: 7.0.0p1
Current Items not working/Buggy
Updated 10-27-2016
WIFI MODEL
Camera
Wifi cuts out for some.
4g MODEL
Camera
Wifi cuts out for some.
You tell me what you find.
Click to expand...
Click to collapse
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
Twitter: https://www.twitter.com/wbellavance
IRC: #evervolv
Click to expand...
Click to collapse
[GPL Compliance]
Kernel Source
Click to expand...
Click to collapse
[Download]
[Unoffical TWRP Builds]
3.0.2.0 TWRP recovery with MTP support and F2FS. http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.2.0-09-06-16.zip Updated to 3.0.2.0
3.0.2.0 TWRP recovery with MTP support and F2FS. http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.2.0-09-11-16.zip Made a little smaller then previous 9.2mb
**REQUIRES 1312MB System Partition.
This is very easy to do via JCSullins Toolbox
WIFI MODEL TEST BUILDS
http://evervolv.com/get/ev_tenderloin-7.0-testing-2016.10.05.zip Ok this isn't block style install which allows changing the size of system to what you want and use all of it. Its a slower install time but not much slower then before. Also some BT changes that allow me to use my headset. Test out BT and let me know. I'm still testing myself. Another change is root is disabled by default. You will have to go into Evervolv toolbox to enable root.
http://evervolv.com/get/ev_tenderloin-7.0-testing-2016.10.27.zip Behind the scene updates along with fixing BT speakers HOPEFULLY 8)
4g MODEL TEST BUILDS
http://evervolv.com/get/ev_tenderloin4g-7.0-testing-2016.09.07.zip
http://evervolv.com/get/ev_tenderloin4g-7.0-testing-2016.09.17.zip Includes all above
http://evervolv.com/get/ev_tenderloin4g-7.0-testing-2016.10.27.zip Behind the scene updates along with fixing BT speakers HOPEFULLY 8)
These are the gapps im using. http://opengapps.org/?download=true&arch=arm&api=7.0&variant=pico gapps that seem to work the best with Nougat UPDATED 09-06-16
Click to expand...
Click to collapse
****************************************PLEASE READ**************************************************************
F2FS installs. If you want to try out F2FS you will have to wipe your data parition which includes your internal sd card. Some steps if you want to backup your data. PLEASE NOTE DON'T DO THIS IF YOU DON'T KNOW WHAT YOU ARE DOING CAN CAUSE ISSUES OR LOST DATA. IF YOU DON'T DO THIS IT WILL STILL WORK WITH THE CURRENT FORMAT EXT4.
-- Flash the F2FS compatible TWRP Recovery
-- Boot into Recovery
-- Backup > Data
-- Save your internal SD card by transfering to your PC or if you have room your external_sd
-- Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > F2FS
-- Wipe > Advanced Wipe > Cache > Repair or Change File System > Change File System > F2FS
-- Copy the saved SD card content back to your device
-- Restore > Choose backup > Data (the warning about ext4 backup doesn’t matter)
-- Advanced > Fix Permissions
-- Wipe > Advanced Wipe > Cache & Dalvik Cache
-- Flash the 2-12-15 test build and gapps to ensure you got them
-- Reboot to system
Click to expand...
Click to collapse
[UPGRADE(Dirty Flash)]
I have noticed if you dirty flash on first boot you may experience a little lag or possible reboot. After it settles down no issues. Not sure if its art related on upgrades or what. Its hard to pin point as it only happens once and smooth after that. Recommend after an upgrade let it settle in before playing hard.
Thanks
Click to expand...
Click to collapse
FIrst boot is a little slow but that is due to art. I always recommend a clean install when upgrading but if you feel luck. Backup and try a dirty flash. If you have issues run a clean install and if you still have issues please post with a logcat. You can upload via bugreport in the toolbox under settings. If going from a differnt rom other then evervolv lollipop always clean install. ALWAYS REMEMBER TO BACKUP its important if you don't want to loose anything
Click to expand...
Click to collapse
NOTE: NEED a clean install if moving from a previous version and or another ROM.
Flashing from cm or any other ROM will require a clean install, dirty flashes can cause random reboots and random errors
[Disclaimer]
I am not responsible for bricked devices, lost data, etc, etc. You all know the drill. BACKUP BACKUP BACKUP
Click to expand...
Click to collapse
[Special Thanks]
i would like to thank Flemmard, Jcsullins, Dorregaray, Invisiblek, Milaq, and anyone else that helped to make this happen. More great work to come.
Mitchbaria --for a 4g model to start in on this
EricBlade --for my second 4g model to start in on this for Marshmallow
Colchiro-- For a spare Touchpad WIFI to be able to test on one and develop at the same time
Click to expand...
Click to collapse

Biggest thing is need to update system size and use new recovery.
Alot of features have been turned on yet this is ALPHA its not a daily. I released for all to play with and we will grow on this. 8)

TP Toolbox v0.42 Complete Data Reset Guide with Updated Links
NOTICE: THIS THREAD WAS ABANDONED BY THE OP, BUT I WILL KEEP THE LINKS IN THIS POST UPDATED
This guide is for a complete data reset to start from scratch. You should only need to use TP Toolbox to either adjust partition sizes, or start from scratch if any partitions got corrupted or you get errors while adjusting partitions or installing new ROMs.
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
I recommend keeping those files on your PC hard drive so you can always re-use them in the future if needed.
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files from your PC to the "tpinstall" folder after the TP is mounted
4. When given the option to adjust partition sizes, increase the System partition to at least 1312mb
5. Finish install, and reboot to TWRP
6. While in TWRP, flash the newer 3/24/17 TWRP 3.1.0.0
7. Reboot into the new TWRP that you just flashed
8. In TWRP advanced wipe menu, wipe the System partition
9. While still in TWRP, flash the Wifi model ROM or the 4G model ROM along with some OpenGapps

AlwaysLucky said:
Great work @flintman! Will test out now! Many thanks on your continued attention on the tenderloin!
PS: Your OP says you are working on "Marshmallow(Android 7.0.1)"
Click to expand...
Click to collapse
Missed that one. Remember to upsize your system partition.

Wow.
Thank you flintman for giving our touchpad a treat of fresh nougat.
I increased the system size to 1.5 gb several days ago and waited for your nougat. Now downloading it...
Edit: are we required to use the new twrp recovery in the OP? I have twrp 3.0.2 with an older time stamp.

BIG THANKS @flintman

googlephone said:
Wow.
Thank you flintman for giving our touchpad a treat of fresh nougat.
I increased the system size to 1.5 gb several days ago and waited for your nougat. Now downloading it...
Edit: are we required to use the new twrp recovery in the OP? I have twrp 3.0.2 with an older time stamp.
Click to expand...
Click to collapse
Yes use the one in the op you will get an error (not fatal) on older recoveries.
Sent from my Nexus 6 using XDA-Developers mobile app

flintman said:
Remember to upsize your system partition.
Click to expand...
Click to collapse
I actually enlarged the System partition to 1500mb just to be safe, and am testing the Nano OpenGApps. So far everything works great! I've installed several different apps, and all seem to work just fine with no FCs. I also get to test out the apps I'm developing on the Nougat OS, so that's really nice. I do miss CM theme support and the Evervolv toolbox, but I promise to be very patient; as I know those are out of your hands. :angel: I also flashed AdAway to the system and that is also functioning fine.
EDIT: For those who would like a flashable zip of AdAway to flash it to the System, I attached it to this post.

I dirty flashed over evervolve 6.0.1 and it boots up in about 6 minutes.
It feels much faster than 6.0.1 and the multi window is amazing.
There is no evervolve toolbox tab in setting, so there is no option to change the cpu frequency.
In the OP, it mentioned evervolve toolbox for bug report. Is the toolbox supposed to be absent?
Edit: second question: where do we control root permissions?

googlephone said:
I dirty flashed over evervolve 6.0.1 and it boots up in about 6 minutes.
It feels much faster than 6.0.1 and the multi window is amazing.
There is no evervolve toolbox tab in setting, so there is no option to change the cpu frequency.
In the OP, it mentioned evervolve toolbox for bug report. Is the toolbox supposed to be absent?
Edit: second question: where do we control root permissions?
Click to expand...
Click to collapse
Im surprised a dirty flash worked. As stated above not alot of features have been added but the toolbox access at the moment is only though the launcher you should see toolbox just like any other app. Root permission is controlled though the toolbox as well.

How can we promote this thread to the xda news portal? Flintman deserves a spot there.
Edit: there is no thanks button any more on XDA? I can not find that button.
Edit: now the thanks button shows up. Weird.

AlwaysLucky said:
I actually enlarged the System partition to 1500mb just to be safe, and am testing the Nano OpenGApps. So far everything works great! I've installed several different apps, and all seem to work just fine with no FCs. I also get to test out the apps I'm developing on the Nougat OS, so that's really nice. I do miss CM theme support and the Evervolv toolbox, but I promise to be very patient; as I know those are out of your hands. :angel: I also flashed AdAway to the system and that is also functioning fine.
Click to expand...
Click to collapse
Toolbox is located in the launcher for now. All features will be added back little by little. 8) trying to get a good base and then we move on.

flintman said:
Toolbox is located in the launcher for now.
Click to expand...
Click to collapse
OMG, I'm so blind. Sorry about that. :silly:

@ flintman
how is your general partitionsetup, not just system.

schwatter said:
@ flintman
how is your general partitionsetup, not just system.
Click to expand...
Click to collapse
1312 for system, 1 gig for external and rest in data. I
Sent from my Nexus 6 using XDA-Developers mobile app

flintman said:
1312 for system, 1 gig for external and rest in data. I
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, it looks like my setup. I find in touchpad toolbox the partition "media". So "media is like "external" right?
And about "cm-cache", i think i set it up in the past from 200 to 1000. Is that better? So normally yes because
of more. But i don't know how android handle it. That's why i ask.

Hey gang, using tptb I placed jcs rom and the gapps and used jc twrp recovert. it failed. ant pointers? thanks..

deafasheck said:
Hey gang, using tptb I placed jcs rom and the gapps and used jc twrp recovert. it failed. ant pointers? thanks..
Click to expand...
Click to collapse
If you've switched to f2fs, then that's the reason. TPTB is unfortunately incompatible with it.

Hi didn't switch to f2fs. I downloaded the files and used pc tptb for the installation.. Currently I am trying to get wifi working better. I installed the job new rom and cm 12 going to the WiFi forum. I have just bought a new one that's 16 gig, it has WiFi access but falters..
But on this issue I will try to get it going on the other TouchPad see if it works..

Amazing stuff
Great job as always. Flintman, you have always been the first ou with the new release of Android since i have had a toucpad for the last few years. Congratulations again and thanks for all your work.
And Multi screen works too!

Link2SD can't convert to sys apps

Hi
My devices galaxy s10+ is rooted with magisk (no twrp)
Android 10 one UI 2.0
I'm trying to convert app to system app with link2sd and get failure message:
mount: '/system' not in /proc/mounts
Also when I'm in the app info there is a note:
Second partition not found
How can I fix that problem?

GalZ123 said:
Hi
My devices galaxy s10+ is rooted with magisk (no twrp)
Android 10 one UI 2.0
I'm trying to convert app to system app with link2sd and get failure message:
mount: '/system' not in /proc/mounts
Also when I'm in the app info there is a note:
Second partition not found
How can I fix that problem?
Click to expand...
Click to collapse
Bro, its because of Magisk update. Revert magisk to 19.3, your problem will solve. For more info, check the changelog of magisk after 19.3 update.

test.recharge1 said:
Bro, its because of Magisk update. Revert magisk to 19.3, your problem will solve. For more info, check the changelog of magisk after 19.3 update.
Click to expand...
Click to collapse
Is that possible with android 10 One UI 2?

Video calls not displaying on locked screen
Hi guys .
I need help .
After updating my s10plus to latest android 10 stable build.
Video calls not displaying when screen is locked.
Screen not waking up.
Please help

GalZ123 said:
Is that possible with android 10 One UI 2?
Click to expand...
Click to collapse
I have checked on my OnePlus 6 Android 9 & 10. It was working fine.

GalZ123 said:
Hi
My devices galaxy s10+ is rooted with magisk (no twrp)
Android 10 one UI 2.0
I'm trying to convert app to system app with link2sd and get failure message:
mount: '/system' not in /proc/mounts
Also when I'm in the app info there is a note:
Second partition not found
How can I fix that problem?
Click to expand...
Click to collapse
Hello, did you find any working app for Android 10 that can move apps to system partition?
App2sd?
Also, which apps that you tried, work on Android Pie?
I'm still on Pie so i'd like to know (maybe i ll move in the next months)

test.recharge1 said:
I have checked on my OnePlus 6 Android 9 & 10. It was working fine.
Click to expand...
Click to collapse
S10+ One UI2 , not one plus
The regular method to root this broke my phone, that's why I'm asking here and not doing this

[OnePlus 8T] MicroG on OxygenOS 13 (UPDATE-SUCCESS)

So I just wanted to share my journey with trying to get MicroG on OxygenOS 13 for my OnePlus 8T!
I wouldn't say I have successfully done but it is working as MicroG is doing what it is intended to do but with definite issues.
The first obvious issue is after flashing MicroG revived module via Magisk, I notice a black spot near the camera. I'm assuming that the module made the UI misalign with the actual camera. Please check screenshots!
Second issue is there is no AOD, it is completely gone. I tried downloading the latest AOD for Oneplus via the web browser and it installed and also showed up in settings as it didn't after flashing MIicroG.
On the plus side I don't believe Google to be harvesting my data as much as stock OxygenOS would allow, and the running services has increased ram availibility from 6.4 gigs of ram usage to 7.1 and I haven't started debloating yet!
The steps I produced to get MicroG to work:
1. After having magisk installed flash Lsposed.
2. In Lsposed flash the modules FakeGapps, Corepatch, and Xdowngrader.
3. Flash MicroG Revived via magisk.
FakeGapps allows for the signature spoofing of microG.
CorePatch allows for no signature checking as that is an issue when flashing microg, so corepatch is a workaround.
Xdowngrader allows for downgrading the gsm to microG version from the current one with OxygenOS 13.
Perhaps if we work together we can get everything working accordingly and have a Degoogled OxygenOS rom.
I know why not just use Lineage 20? Lineage is great but I just perfer the UI of OxygenOS but if the issues I presented to you are not resolved eventually I shall return to Lineage. I just figure "Hey this is what we do, we experiment with roms, right?"

This is an update to having microg on OxygenOS 13.
I have good news as it seems all the above issues with microg on OxygenOS 13 have been resolved!
So for those interested I will list my steps in order to achieve a successful microg install. Of course magisk and unlocked bootloader is needed.
Flash Lsposed and the same modules listed in my above post!
Download fdroid and then App management via fdoid repo.
Use app management app to disable and uninstall GmsCore using mixplorer (flash magisk module mixplorer)
GmsCore directory location: ROOT/PRODUCT/PRIV-APP. Use mixplorer to locate and than click on the GmsCore.apk and select App Info, this will open Google Play Services using App management app. Disable and try to uninstall, you may get a failed to uninstall notification at first.
Download this microg package as it differs from microg revived which was the microg installer that created an overlay issue: minmicrog-standard flash via magisk and reboot.
On first boot you may not see microg in your app drawer but if you search for it through setting apps and enable view system apps you should see it but it maybe still useless. Use mixplorer and try to uninstall GmsCore.apk again. It should uninstall and than flash the microg module again via magisk.
Reboot and now you should see microg in your app drawer---enable its permission and location modules---go to each location module and make sure to always allow location.
Use fdroid or microg website to download and update to the latest microg!!!
Those are the steps I took and wrote this post immediately after doing so while the process was fresh in my mind!
Just ONE issue, microg in app drawer doesn't survive reboot- just install the microg.apk again!
UPDATE: It turns out after 2 days of this current microg setup that Google's GmsCore can not be uninstalled but can be disabled due to the fact that the system partition in Android 13 is read-only. Until there is a script to flash in custom recovery or perhaps any other means of obtaining write access to system there will not be a truly google-less Oxygen OS 13. Just a matter of time before or workaround is released I'm sure.
My final thoughts for now: Microg is functioning as intended and I will continue to use this setup as my daily driver. I have not encountered a google services dependable app that's having issues working with MicroG except Meet or formerly Duo. No severe bugs what so ever---phone functions as intended with everything intact including AOD, fingerprint, ram expansion and app cloning. However still issues with MicroG surviving reboot, I guess until we can obtain system write access. I hope someone finds my post helpful!

Thats so great. Please keep updating further about the rest issues. I will be trying the same myself soon.

alp47470 said:
Thats so great. Please keep updating further about the rest issues. I will be trying the same myself soon.
Click to expand...
Click to collapse
How is your microg setup going? The only issue is MicroG not surviving reboot but all yo have to do is remove the microg module from magisk then reboot and flash the module again and reboot then you'll have to setup microg google account and the location modules within microg.
I think the reason is because google GmsCore lives in the system partition and on reboot the GmsCore reclaims permission which prevents MicroG to function correctly. When someone makes a module for magisk or perhaps to flash with a custom recovery that debloats google or at least gives use write access the reboot issue should be resolved.

JedidroidX said:
UPDATE: It turns out after 2 days of this current microg setup that Google's GmsCore can not be uninstalled but can be disabled due to the fact that the system partition in Android 13 is read-only. Until there is a script to flash in custom recovery or perhaps any other means of obtaining write access to system there will not be a truly google-less Oxygen OS 13. Just a matter of time before or workaround is released I'm sure.
Click to expand...
Click to collapse
There is such script. Recently updated.
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com

Rootk1t said:
There is such script. Recently updated.
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Click to expand...
Click to collapse
I believe that script in not available for Android 13 and continued development has been suspended as the thread is closed.

JedidroidX said:
I believe that script in not available for Android 13 and continued development has been suspended as the thread is closed.
Click to expand...
Click to collapse
[MAGISK][TWRP][ARM32/64][A8+]Universal Read Only to Read Write for android (RO2RW) | Auto converting SUPER "system partitions" to read/write mode
Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1 The first truly working script, original and unique in its logic for all devices with a SUPER partition Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by...
forum.xda-developers.com

Rootk1t said:
[MAGISK][TWRP][ARM32/64][A8+]Universal Read Only to Read Write for android (RO2RW) | Auto converting SUPER "system partitions" to read/write mode
Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1 The first truly working script, original and unique in its logic for all devices with a SUPER partition Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, so the script was very helpful, took me a few hours to understand how it works but I got it although with some limitations. It seems the script did not grant me write access to the system partition but I was able to eliminate the GmsCore.apk from the system so MicroG can assume all permissions and now working flawlessly on OxygenOS 13.
The script is very helpful in doing so by allowing me to delete certain apk's from the super image and than from my understanding the script would mount that super image without the apk's that I selected which of course GmsCore was one of them. Google's GmsCore is officially eliminated from my current setup with all of Oneplus's benefits intact and no bugs or any issues have been experienced for now.
I will report an update in a couple of days to post the steps I took and any other relevant user experience with the current setup.
Thanks for posting the script @Rootk1t

How to install microg on stock oos13:
1. Debloat google play services apk using
https://github.com/sunilpaulmathew/De-bloater (it's magisk debloater)
2. Flash lsposed and enable fakegapps module.
3. Flash microg installer revived (minmicrog ci or release not working this time)
4. Done. 10 reboots, 0 issues.
My setup:
Magisk delta with new zygisk loader option enabled and lsposed_mod