How do i fix this, i dont know what is wrong. CM12 wont flash, even though it is on te device.
Mention your current recovery (PhilZ/ TWRP) and version.
sharkymyn said:
Mention your current recovery (PhilZ/ TWRP) and version.
Click to expand...
Click to collapse
It is TWRP recovery v. 2.8.5
sharkymyn said:
Mention your current recovery (PhilZ/ TWRP) and version.
Click to expand...
Click to collapse
Thanks for the reply, but i fixed it, I just formatted the data again, then copied cm12 onto the phone, flashed it, then it booted up!
unable to mount system after deleting os accidentally
pliz help
Even I am having the same problem. When I flash it says " E unable to mount "/system" I gather from googling that it is malformed partition issue. But I am not able to find fixes for it. Please help
I think the problem was with the Cm 12.1 zip. I installed another rom.zip file (Blisspop rom) and it is working fine now.
Hi. Just wanted to say that LineageOS 17 is indeed working on my Samsung Galaxy A40.
By wiping everything except internal storage and flashing the A/B image of LineageOS 17, I got it working on my A40. The only problem is that:
1. USB OTG does not work.
2. File transfers does not work.
3. WiFi is a bit slow, but still works.
You just search up online tutorials on how to flash GSI Rom's on phones, then you follow those.
PS: Some apps show you that your system is A only. Those apps are not working. The phone uses A/B.
Same problems at my side. Now im trying some other ROMs
Added:
OTG works fine (tested flashstorage)
View attachment 4973199View attachment 4973201
EMEK said:
Same problems at my side. Now im trying some other ROMs
Added:
OTG works fine (tested flashstorage)
Click to expand...
Click to collapse
How have you gotten OTG to work? MicroSD card works fine, but not an external USB.
Nothing... It works from beginning, my otg cable was faulty.
Wysłane z mojego MI 5 przy użyciu Tapatalka
How did you do it? I keep getting stuck after flashing the GSI rom. It wont boot..
Hey there
On my A40 with LOS17 my Bluetooth Headphones works fine, untill i get a call (or want to make one),
then the Phone switches to the internal speaker.
Does anybody have the same problem?
Hi,
Did anyone manage to fix the rounded corners. For example the battery icon is not visible.
EDIT: Already found it. It is in Phh settings.
LoggyDogDog said:
Hi. Just wanted to say that LineageOS 17 is indeed working on my Samsung Galaxy A40.
By wiping everything except internal storage and flashing the A/B image of LineageOS 17, I got it working on my A40. The only problem is that:
1. USB OTG does not work.
2. File transfers does not work.
3. WiFi is a bit slow, but still works.
You just search up online tutorials on how to flash GSI Rom's on phones, then you follow those.
PS: Some apps show you that your system is A only. Those apps are not working. The phone uses A/B.
Click to expand...
Click to collapse
Hello! Would you possibly provide with documentation or just the procedures on how to get a GSI to work on the Samsung A40? Been trying to get it to work and it just says "No OS installed" in TWRP and boot loops...
zooble said:
Hello! Would you possibly provide with documentation or just the procedures on how to get a GSI to work on the Samsung A40? Been trying to get it to work and it just says "No OS installed" in TWRP and boot loops...
Click to expand...
Click to collapse
Atleast for now, all of the gsi images are not worth effort for this device. I've tried most of them and they are laggy. But here is an instruction
1. Download all attached files and copy them to sd card (Cant post links because im new but i hope that this will not get deleted
ht tps://drive.google.com/drive/folders/1GhcWXGcNir-5fKt25y1D6kgZd7DNVz6e (remove the space in gaps)
2. Boot into twrp
3. wipe
Dalvik/ Art Cache
System
Data
Internal Storage
Cache
4. Flash Disable_Dm-Verity_ForceEncrypt
5. Flash gsi rom as system
6. Reboot to recovery (very important, dont skip this step. There might be information about No OS Installed dont worry about it.)
7. Then click Mount - System. Go to wipe -> Advanced wipe -> Select system -> Click repair or change file system -> resize file system (If there is an error while resizing system just do it one more time.)
8. Flash Magisk
9. Now depends on your gsi. Some have already attached google services. If you are using lineage os i suggest you to use NikGapps (Open gapps didn't worked for me) Flash it
10. If you are having problem with corners in gsi rom, flash A40LOSFIX. It fixes the problem
There is fix for laggy animations in system ui
Open up any root file explorer and go to:
/system/build.prop (remember to change partition from r/w to r/o)
and paste those lines at the bottom of the file
#visual_tweak
debug.sf.hw = 0
debug.egl.hw = 0
debug.enable.sglscale = 1
debug.sf.enable_hwc_vds = 1
debug.gralloc.enable_fb_ubwc = 1
debug.sf.latch_unsignaled = 1
debug.sf.recomputecrop = 0
dev.pm.dyn_samplingrate = 1
Thats all, but as i said i dont think that is worth the effort. Android q navigation gestures are choppy even with the fix and thats problem for me. But maybe someone could fix this or make rom specific for this device.
What is about camera performance in LOS ? As far as I know there are some propriatary part of firmware ...
Whats with the Gapps?
LoggyDogDog said:
Hi. Just wanted to say that LineageOS 17 is indeed working on my Samsung Galaxy A40.
By wiping everything except internal storage and flashing the A/B image of LineageOS 17, I got it working on my A40. The only problem is that:
1. USB OTG does not work.
2. File transfers does not work.
3. WiFi is a bit slow, but still works.
You just search up online tutorials on how to flash GSI Rom's on phones, then you follow those.
PS: Some apps show you that your system is A only. Those apps are not working. The phone uses A/B.
Click to expand...
Click to collapse
Whats with Gapps can i flash it?
Hello, I'm considering installing Lineage OS 17.1 over stock Android. Have the slow WiFi and files not transferring via USB cable been patched yet?
Tsw2 said:
Hello, I'm considering installing Lineage OS 17.1 over stock Android. Have the slow WiFi and files not transferring via USB cable been patched yet?
Click to expand...
Click to collapse
Ive been using it for 2 weeks now. I like it many times more than the Samsung bloatware. But yes, there are still some limitations and broken functionalities there. To name the ones I've noticed so far:
- No USB OTG, nor file transfer via USB.
- Auto brightness not working (even though the light sensor is working)
- Proximity wont change audio messages from playing on speaker
Working:
- Wifi 5Ghz working full speed (30 Mb/s+)
- Playing music over bluetooth
- Battery seems to last the same
Apart from that, I have nothing to complain just yet.
Does Ambient Display work for you?
Elmarigo said:
Does Ambient Display work for you?
Click to expand...
Click to collapse
It does not. I can search it in the settings menu, but the setting is not there. Same for adaptive backlight
I've installed according to Yankezss advice with twrp 3.4 unofficial. I have ARM64 architecture device and I downloaded the A/B version "lineage-17.1-20201114-UNOFFICIAL-treble_arm64_bvS (1).img.xz" extracted it and installed the .img as system in twrp and everything else according to his post. My phone stays in "galaxy" logo, waited for 20-30 minutes and it was still like that. Any advice? I've also tried installing unofficial lineage os 18 from two different sources and could not get those booted either.
norteo fucnciona
So you all talking about general GSI LOS Roms, right. There is no dedicated for A40?
kolja82 said:
Hey there
On my A40 with LOS17 my Bluetooth Headphones works fine, untill i get a call (or want to make one),
then the Phone switches to the internal speaker.
Does anybody have the same problem?
Click to expand...
Click to collapse
Hi, did you solve? I have the same bug
Yankezss said:
4. Flash Disable_Dm-Verity_ForceEncrypt
Click to expand...
Click to collapse
Hello!
Do I need to flash "Disable_Dm-Verity_ForceEncrypt" again anytime?
1. After factory reset?
2. After wiping a specific partition?
3. After resotring the phone using Odin?
4. which partition is this patch stored on?
Many thanks!
Is there any logical reason why many of the modified roms (especially the pixel experience) come to a point where the phone almost hangs up, you end up rebooting with the power button and when you boot up it doesn't start and only fixes itself by flashing the persistent partition?
It's already happened to me like 4 times.
The last time with the last pixel experience, I flashed persist.img and got it to boot, but after 30 seconds it rebooted itself.
In the end with the original miui it goes perfect and never fails.
What's wrong with me?
No root, no magisk... only open bootloader
wrong recovery maybe. Use lr team recovery by wzsx150 if you aren't.
Also https://forum.xda-developers.com/mi-8/help/one-repair-persist-issues-t4036919
What I don't understand is what a recovery has to do with a failure after 1 week of the persist.img partition that is read-only.
kaiseryeahhh said:
What I don't understand is what a recovery has to do with a failure after 1 week of the persist.img partition that is read-only.
Click to expand...
Click to collapse
I wrote an extensive post on this issue. First thank the gods that reflashing a persist works for you, for some it doesn't. I am guessing that you also have a copy of your persist after you have fully setup your phone backed up to your desktop computer? If not do so immediately, just in case you need it one day.
Unfortunately persist is a complex image that handles a lot of responsibility: It contains the calibration data for your sensors: bluetooth, WIFI, Camera, and data signals. It also contains your FRP data such as, google , miCloud, Pay apps etc.
If you want to avoid persist issues permanently go back to stock and don't use root.
I suspect that these issues that people have had with persist are the beginning of the end, when it comes to using root, and maybe eventually impact use of custom roms too?
I have found that I can go for months without experiencing persist issues while keeping root by restoring my phone with a fastboot stock rom. To be clear I am not talking about a recovery rom that can be flashed with TWRP. It must be a fastboot rom, with a full format, it will overwrite TWRP too, so back everything up and start clean.
Unfortunately once you start experiencing persist issues you will get them again and again. I have experienced the best long term results by using the stock rom, and I also use custom recovery and root. My parents Mi8s have never used anything but Xiaomi.EU version of stable or the Stable stock w/root and they have never had the persist issue.
I have been enjoying the new Miui 12 rom. But it has been causing a lot of issues so far. First earlier today my phone stopped connecting to Google apps, and when I rebooted, I could no longer access data. In addition, I have had trouble with phone calls.. Data works but the ability to make a phone call has been sporadic. So I will unfortunately go back to the older stable Xiaomi.EU 11.0.7 rom. Which I like, but miui 12 is such an improvement it's hard to go back.
If you want to stick with Pixel Rom, just do a clean format , and flash a fastboot rom, once setup, You should be able to use it for at least a couple of months before seeing the issue again.
Sometimes you can quickly resolve the issue by simply flashing a root patched boot image that has the the correct system signature. Flash the magisk patched boot, and you may be able to go back to normal without having to reinstall anything. But the issue will return.
Thank you very much for the explanation.
But that's what I'm saying, I don't understand why a partition that in theory is only read and no one touches, gives failures.
I guess it must be a hardware failure, I don't see any other explanation.
I've never used root.
kaiseryeahhh said:
Thank you very much for the explanation.
But that's what I'm saying, I don't understand why a partition that in theory is only read and no one touches, gives failures.
I guess it must be a hardware failure, I don't see any other explanation.
I've never used root.
Click to expand...
Click to collapse
You unlocked the bootloader, maybe this alone contributes to the issue for all of us. Also, this problem occurs on practically on every phone that allows us to unlock the bootloader and use custom Roms.
While, it is possible that it could be a hardware issue, I really don’t think so ( A short would not work without issues for months at a time. For me the issue only appears when I update
You can write to the persist if you are rooted and using a version of TWRP that allows you to write specifically to the persist partition. As I mentioned I made a very extensive thread attempting to figure this issue out myself, and I provided several resolutions.
If you never want to deal with it again then restore your persist backup, return to stock and lock the bootloader. Maybe even sell the phone and buy a onePlus 7T while they are still priced at the low $499…I am considering this myself.
No doubt, Xiaomi contributes to this issue with Mi Cloud restore being available to devices with unlocked bootloaders, I believe that they are recently starting to figure this out for themselves because you can no longer backup and restore every single app.
Also, if I am using a Miui based custom rom. My sim card does not work until I sync my device to Mi-Cloud., and because I switched to a cheaper carrier that does not allow inbound calls from overseas, I have trouble receiving a text from MI Cloud to verify my device. So, I do it manually by going to https://i.mi.com/ on my phone and selecting to find my device.
See the attached image with 2 unknown devices, I believe that this triggers the persist issue. but it can also be triggered by Google. I don’t think it's a hardware issue. Finally, these Roms all seem to use individual variations of FSTAB vendor files, changing this absolutely increases the potential for getting a persist conflict. Keep in mind that your persist partition is NOT really empty when you an issue. It’s is simply encrypted.
tsongming said:
I wrote an extensive post on this issue. First thank the gods that reflashing a persist works for you, for some it doesn't. I am guessing that you also have a copy of your persist after you have fully setup your phone backed up to your desktop computer? If not do so immediately, just in case you need it one day.
Unfortunately persist is a complex image that handles a lot of responsibility: It contains the calibration data for your sensors: bluetooth, WIFI, Camera, and data signals. It also contains your FRP data such as, google , miCloud, Pay apps etc.
If you want to avoid persist issues permanently go back to stock and don't use root.
I suspect that these issues that people have had with persist are the beginning of the end, when it comes to using root, and maybe eventually impact use of custom roms too?
I have found that I can go for months without experiencing persist issues while keeping root by restoring my phone with a fastboot stock rom. To be clear I am not talking about a recovery rom that can be flashed with TWRP. It must be a fastboot rom, with a full format, it will overwrite TWRP too, so back everything up and start clean.
Unfortunately once you start experiencing persist issues you will get them again and again. I have experienced the best long term results by using the stock rom, and I also use custom recovery and root. My parents Mi8s have never used anything but Xiaomi.EU version of stable or the Stable stock w/root and they have never had the persist issue.
I have been enjoying the new Miui 12 rom. But it has been causing a lot of issues so far. First earlier today my phone stopped connecting to Google apps, and when I rebooted, I could no longer access data. In addition, I have had trouble with phone calls.. Data works but the ability to make a phone call has been sporadic. So I will unfortunately go back to the older stable Xiaomi.EU 11.0.7 rom. Which I like, but miui 12 is such an improvement it's hard to go back.
If you want to stick with Pixel Rom, just do a clean format , and flash a fastboot rom, once setup, You should be able to use it for at least a couple of months before seeing the issue again.
Sometimes you can quickly resolve the issue by simply flashing a root patched boot image that has the the correct system signature. Flash the magisk patched boot, and you may be able to go back to normal without having to reinstall anything. But the issue will return.
Click to expand...
Click to collapse
Hm, I had a problem with persist partition on my Mi 8 too, but after 2nd flashing stock persist.img (it was taken from fastboot ROM) via TWRP all seems OK...
But I still have lots of problems with data partition on any ROM (I used xiaomi.eu beta and now I use PE+). The problems can be in files/folders, and I can't simply delete them (on PE+ I can, but the errors from recovery don't disappear...) There's 3 types of errors in data partition I had:
-Operation not permitted
-Structure needs cleaning
-No such file or directory
Now I'm going to explain how I fix these errors on xiaomi.eu:
First error (operation not permitted) can be solved by deleting some app data from system (in system settings of an app)
BUT if the "problem" path isn't app data, I have no idea what I should do... The idea is you should use system standard operations of wiping something.
Second error can be solved by "e2fsck" (fsck operation) from recovery terminal
Third error can be solved by deleting "problem" path/files IN ENCRYPTED STATE. The problem is finding them when they're encrypted. I puted in the first encrypted folder with the problem a lot of files and when I see the folder with a lot of files, I delete it(if the /data/data/*app_data*/cache/*file1* file is problem, then I put a lot of files in /data/data/*app_data* folder (this folder is the first encrypted folder after reboot) and then spend a lot of time to find this folder in encrypted state to delete it)
On PE+ I got only 3 "operation not permitted error", but, as I said, deleting works, but it doesn't "kill" errors
So, obviously, I don't like that from time to time I have errors in my data partitions. Once I didn't fix it, errors "multiplied", I woke app and saw my phone in TWRP with the hundreds errors of different types. So, it's easier to format data... (wiping doesn't give anything, only formatting)
So, does anyone know what I should do? It very looks like hardware error, because I don't see anyone else with the errors...
I guess the problem is watsapp, because always my system UI stucks for a long time (20~30 sec.), which is a signal of appearing another data error, I writed someone in watsapp or has it launched...
Here's an example of the errors (only "operation not permitted" error) on PE+
View attachment 5014159
Plovel said:
Here's an example of the errors (only "operation not permitted" error) on PE+
View attachment 5014159
Click to expand...
Click to collapse
Your log file is not accessible, you reupload it.
You are having the exact issue that I get occasionally.
Try this
The next time you are ready to complete a full format trying changing your user data and cache partition to F2FS format, then install a rom and attempt to to boot to system, some roms will boot and the issue will go away for some people. I have not been able to boot to a miui Rom using this format. However, I helped someone else via PM with this same issue and they told me that changing to F2FS, rebooting to recovery and then changing it back to ext4 work for them, and I never heard about that issue from that person again.
When I installed my recent installation of the Miui 12 5.7 Xiaomi.EU, I followed th3ese steps myself and so far no issues.
In fact, I just found how people with the OnePlus 5T used the exact same solution: https://forum.xda-developers.com/oneplus-5t/help/failed-to-mount-structure-cleaning-t3761674
Hopefully that allows you to run without issues for a while.
Good Luck!
Hi, I'm still having the same problems.
I thought everything I did as an orangefox would solve it, but it doesn't.
After 2 days with pixel experience problems again.
After 2 days with the last miui 12's beta, the mobile becomes very slow, I reboot and lose sensors and even a semi factory reset was done, in which I had lost all the applications but I was still logged in google.
Does this make any sense?
I've seen that there is a persist and a persistbackup partition
Does this come from stock? or is it a twrp add-on?
Is there a way to delete absolutely everything and leave the phone with the original partitions?
Because maybe the problem can come from there.
Also, is the partition still read/write?
I tried flashing the persist image then completely go back to china rom stock and re-lock the bootloader. but now I'm facing the same issue, because my phone got bootloop when I started to reboot due to all apps starts to be unresponsive.
tsongming said:
Your log file is not accessible, you reupload it.
You are having the exact issue that I get occasionally.
Try this
The next time you are ready to complete a full format trying changing your user data and cache partition to F2FS format, then install a rom and attempt to to boot to system, some roms will boot and the issue will go away for some people. I have not been able to boot to a miui Rom using this format. However, I helped someone else via PM with this same issue and they told me that changing to F2FS, rebooting to recovery and then changing it back to ext4 work for them, and I never heard about that issue from that person again.
When I installed my recent installation of the Miui 12 5.7 Xiaomi.EU, I followed th3ese steps myself and so far no issues.
In fact, I just found how people with the OnePlus 5T used the exact same solution: https://forum.xda-developers.com/oneplus-5t/help/failed-to-mount-structure-cleaning-t3761674
Hopefully that allows you to run without issues for a while.
Good Luck!
Click to expand...
Click to collapse
I frarmatted data in F2FS and then back to ext4
Seems good so far
Thank you)
Отправлено с моего Pixel через Tapatalk
tsongming said:
Your log file is not accessible, you reupload it.
You are having the exact issue that I get occasionally.
Try this
The next time you are ready to complete a full format trying changing your user data and cache partition to F2FS format, then install a rom and attempt to to boot to system, some roms will boot and the issue will go away for some people. I have not been able to boot to a miui Rom using this format. However, I helped someone else via PM with this same issue and they told me that changing to F2FS, rebooting to recovery and then changing it back to ext4 work for them, and I never heard about that issue from that person again.
When I installed my recent installation of the Miui 12 5.7 Xiaomi.EU, I followed th3ese steps myself and so far no issues.
In fact, I just found how people with the OnePlus 5T used the exact same solution: https://forum.xda-developers.com/oneplus-5t/help/failed-to-mount-structure-cleaning-t3761674
Hopefully that allows you to run without issues for a while.
Good Luck!
Click to expand...
Click to collapse
Damn...
Now I had "no such file or directory" error (in Chrome data)
I already fixed it, but, I guess, formatting ext4->f2fs->ext4 didn't help(
Отправлено с моего Pixel через Tapatalk
Plovel said:
Damn...
Now I had "no such file or directory" error (in Chrome data)
I already fixed it, but, I guess, formatting ext4->f2fs->ext4 didn't help(
Отправлено с моего Pixel через Tapatalk
Click to expand...
Click to collapse
Did the solution help you?
Plovel said:
Hm, I had a problem with persist partition on my Mi 8 too, but after 2nd flashing stock persist.img (it was taken from fastboot ROM) via TWRP all seems OK...
But I still have lots of problems with data partition on any ROM (I used xiaomi.eu beta and now I use PE+). The problems can be in files/folders, and I can't simply delete them (on PE+ I can, but the errors from recovery don't disappear...) There's 3 types of errors in data partition I had:
-Operation not permitted
-Structure needs cleaning
-No such file or directory
Now I'm going to explain how I fix these errors on xiaomi.eu:
First error (operation not permitted) can be solved by deleting some app data from system (in system settings of an app)
BUT if the "problem" path isn't app data, I have no idea what I should do... The idea is you should use system standard operations of wiping something.
Second error can be solved by "e2fsck" (fsck operation) from recovery terminal
Third error can be solved by deleting "problem" path/files IN ENCRYPTED STATE. The problem is finding them when they're encrypted. I puted in the first encrypted folder with the problem a lot of files and when I see the folder with a lot of files, I delete it(if the /data/data/*app_data*/cache/*file1* file is problem, then I put a lot of files in /data/data/*app_data* folder (this folder is the first encrypted folder after reboot) and then spend a lot of time to find this folder in encrypted state to delete it)
On PE+ I got only 3 "operation not permitted error", but, as I said, deleting works, but it doesn't "kill" errors
So, obviously, I don't like that from time to time I have errors in my data partitions. Once I didn't fix it, errors "multiplied", I woke app and saw my phone in TWRP with the hundreds errors of different types. So, it's easier to format data... (wiping doesn't give anything, only formatting)
So, does anyone know what I should do? It very looks like hardware error, because I don't see anyone else with the errors...
I guess the problem is watsapp, because always my system UI stucks for a long time (20~30 sec.), which is a signal of appearing another data error, I writed someone in watsapp or has it launched...
Here's an example of the errors (only "operation not permitted" error) on PE+
View attachment 5014159
Click to expand...
Click to collapse
I take this topic to comment that I remain the same (not with persist fortunately) with my failures with any custom rom.
Now I'm in stock because it's the only one that works for me in time.
The same thing happened to me as to him, structure failures, data failures, etc...
I've even tried e2fsck with erroneous sectors verification but it doesn't have that function.
This is a example
,android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
at android.database.sqlite.SQLiteConnection.open(Unknown Source:33)
at android.database.sqlite.SQLiteConnection.open(Unknown Source:5)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(Unknown Source:6)
at android.database.sqlite.SQLiteConnectionPool.open(Unknown Source:3)
at android.database.sqlite.SQLiteConnectionPool.open(Unknown Source:7)
at android.database.sqlite.SQLiteDatabase.openInner(Unknown Source:6)
at android.database.sqlite.SQLiteDatabase.open(Unknown Source:2)
at android.database.sqlite.SQLiteDatabase.openDatabase(Unknown Source:49)
at android.database.sqlite.SQLiteDatabase.openDatabase(Unknown Source:4)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(Unknown Source:138)
at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(Unknown Source:2)
at com.android.providers.contacts.aggregation.AbstractContactAggregator.<init>(Unknown Source:62)
at com.android.providers.contacts.aggregation.ContactAggregator.<init>(Unknown Source:0)
at com.android.providers.contacts.aggregation.ProfileAggregator.<init>(Unknown Source:0)
at com.android.providers.contacts.ContactsProvider2.initForDefaultLocale(Unknown Source:155)
at com.android.providers.contacts.ContactsProvider2.performBackgroundTask(Unknown Source:212)
at com.android.providers.contacts.ContactsProvider2$1.onPerformTask(Unknown Source:2)
at com.android.providers.contacts.ContactsTaskScheduler$MyHandler.handleMessage(Unknown Source:62)
at android.os.Handler.dispatchMessage(Unknown Source:19)
at android.os.Looper.loop(Unknown Source:249)
at android.os.HandlerThread.run(Unknown Source:28)
And then in the recovery if I try to repair ext4 gives me a lot of unrecoverable errors.
OjSg said:
Did the solution help you?
Click to expand...
Click to collapse
As I see, it didn't help
Отправлено с моего Pixel через Tapatalk
Hello everyone , I was wandering if someone could help me with this issue.
First My phone State and system :
I got an Unlocked k20 Pro , flashed with MIUI 12.0.2 Global (Mi 9T Pro) , rooted wigh magisk (Twrp of course too v3.4 ) , Encrypted storage too.
I am trying to edit some files in the vendor partition but all the changes I make get reversed back , tried everything , Partition mounted as R/W in root explorer , changing the SE Context , but it seems as if all my work is on memory only, and not commited to disk, and everytime I restart the phone it rolls back on how it was before.
Tried copying my edits through TWRP , same result , restart and changes are gone.
So my question is what is happening exactly ? and what should I do to edit the vendor partiton?.
Thought about DM-Verity , tried disabling it using different methods (flashing Universal Zip amd manual editing ) always end up in a bootloop.
The root seems only to allow editing system partition.
Are the files backed up? and then restored if edited ?
Thank you in advance
urbanmec said:
Hello everyone , I was wandering if someone could help me with this issue.
First My phone State and system :
I got an Unlocked k20 Pro , flashed with MIUI 12.0.2 Global (Mi 9T Pro) , rooted wigh magisk (Twrp of course too v3.4 ) , Encrypted storage too.
I am trying to edit some files in the vendor partition but all the changes I make get reversed back , tried everything , Partition mounted as R/W in root explorer , changing the SE Context , but it seems as if all my work is on memory only, and not commited to disk, and everytime I restart the phone it rolls back on how it was before.
Tried copying my edits through TWRP , same result , restart and changes are gone.
So my question is what is happening exactly ? and what should I do to edit the vendor partiton?.
Thought about DM-Verity , tried disabling it using different methods (flashing Universal Zip amd manual editing ) always end up in a bootloop.
The root seems only to allow editing system partition.
Are the files backed up? and then restored if edited ?
Thank you in advance
Click to expand...
Click to collapse
1.Mount vendor image in ubuntu pc... Edit and flash it.
2.In twrp edit in
/system/vendor
Confirm vendor partition mounted in twrp.
[email protected] said:
1.Mount vendor image in ubuntu pc... Edit and flash it.
2.In twrp edit in
/system/vendor
Confirm vendor partition mounted in twrp.
Click to expand...
Click to collapse
Thank you for the answer, however, and after doing some reading, the situation is much more complex, and might be, at the moment, not possible.
It might have something to do with miui dynamic partitons, and twrp not supporting it.(read only mode).
Also, mounting on linux wont work because the dedup ext4 , and unpacking repacking then flashing wont work because , at the moment, I found no way to disable DM-verity on miui 12.0.2(The phone will not boot).
I solved my problem anyway , via Magisk , I just created a module and done what I wanted.(Thats what magisk is for in the first place )