Related
Hi everyone, my name is Mirko and I am an italian student and first of all sorry for my bad english, fiddle with ROMS and Kernels is an hobby for me and i really enjoy it.
I would make a tutorial for anyone who can not unencrypt OnePlus3 with any ROM. READ EVERYTHING BEFORE START.
I AM NOT RESPONSIBLE FOR WHAT COULD HAPPEN TO YOUR DEVICE. PAY ATTENTION.
DOWNLOAD
VIRUSTOTAL
Open and extract the zip file where you want.
Install USB drivers
Install ADB drivers by open adb-setup-1.3.exe, Y, Y ,Y and close.
Copy fastboot adb drivers 1.0.36 to C:\adb and overwrite.
Open CMD in the same file folder by pressing Shift+right click and type "adb", if it say nothing match reboot your pc.
Plug your phone to PC and allow adb access, then type "adb devices" and you should see your phone id.
We have to unlock bootloader, THIS ACTION PERFORM A FULL, FULL (EVEN INTERNAL MEMORY) OF YOUR PHONE, BACKUP EVERYTHING. Tick on OEM Unlock in developer option (nothing here will happen). Type "adb reboot fastboot" and your phone will reboot in fastboot mode. Use now "fastboot devices" for recognize your phone and "fastboot oem unlock" for unlock bootloader.
Do not restore backup cause we are gonna wipe again, back into fastboot mode (AFTER OEM UNLOCK FROM DEV OPTIONS) and flash twrp using fastboot flash recovery multiboot....img.
If phone reboot back again into fastboot and type fastboot format userdata. Reboot into recovery.
Now on recovery start MTP and copy OOS/HOS and supersu zips into your phone, flash the ROM, DO NOT REBOOT, flash supersu. Your device is now unencrypted.
Type adb shell chown -R media_rw:media_rw /data/media on CMD for avoid problems after flash.
You can now flash multiboot.zip and you have to inject boot sector every time you will install/update ROMS. OOS/HOS OTA ARE NOT COMPATIBLE WITH TWRP, YOU HAVE TO FLASH THE ENTIRE ZIP FILE FOR UPDATE IT.
You will see a slide menu on top right side of TWRP and from here you can install new roms on INTERNAL MEMORY. In advanced option select "no-kexec workhound" (important).For gapps go to ROM list, select the interested rom, then flash zip, >gapps.zip. NOT ALL ROMS ARE COMPATIBLE WITH MULTIROM.
Every OTA (i think) except (for sure) stock roms will update without problems.
Reboot your phone and it will boot on multiboot menu, here you select rom you want boot.
YOU ARE DONE.
I tested it on my phone and it works really fine, OOS can be installed as secondary rom BUT FLASH SUPERSU BEFORE REBOOT.
Installing secondary ROMS are slower than primary, cause it will create virtual disks.
If you have problems with pattern after reboot, back into twrp, advance, filemanager, /data/system and delete locksettings.db, locksettings.db-shm, locksettings.db-wal and reboot. Pattern will be deleted.
Installing Kernels wich are not compatible with MULTIROM will softbrick the phone, and you have to wipe.
Installing Kernels on virtual ROMS will softbrick the ROM.
I think my guide is done.
If you have problems
FOR ANY PROBLEMS AND DOUBTS WRITE HERE OR PM ME.
Wow, there's a lot of misinformation in this post.
No "virtual disks" are created. Mount points are changed to point to the secondary ROM.
You don't have to use a multi ROM capable kernel, you should read up on the no kexec workaround before you write up a post like this
Also, you can flash kernels to secondary ROMs. I'm not sure what gives you the impression that you can.
You don't have to flash the multi ROM zip Everytime you write to the system partition. Mutirom is on the "SD card" on the data partition
Aside from the incorrect parts, the rest of the tutorial is poorly written and very difficult to follow
Why don't you leave the tutorials to the people who actually know how things work on the back end.
Sent from my Pixel XL using Tapatalk
slothdabski said:
Wow, there's a lot of misinformation in this post.
No "virtual disks" are created. Mount points are changed to point to the secondary ROM.
You don't have to use a multi ROM capable kernel, you should read up on the no kexec workaround before you write up a post like this
Also, you can flash kernels to secondary ROMs. I'm not sure what gives you the impression that you can.
You don't have to flash the multi ROM zip Everytime you write to the system partition. Mutirom is on the "SD card" on the data partition
Aside from the incorrect parts, the rest of the tutorial is poorly written and very difficult to follow
Why don't you leave the tutorials to the people who actually know how things work on the back end.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
First of all thank you for reply, i totally missed to enable no-kexec workhound function...
I want to clarify that it is my first guide I do, I started in make some because I want to help people like me who have had difficulties in carrying out certain passages. I accept ANY advice and I will try to improve with time. I admit I made a mistake forgetting the previously mentioned feature. I can tell you, however, that the multi-boot every time you install a new ROM is removed. Going blind I specified / system because it is the main partition is rewritten during a flash. But I have a doubt. The Kernel for secondary ROM, should not be predisposed to function properly?
mirko8054 said:
First of all thank you for reply, i totally missed to enable no-kexec workhound function...
I want to clarify that it is my first guide I do, I started in make some because I want to help people like me who have had difficulties in carrying out certain passages. I accept ANY advice and I will try to improve with time. I admit I made a mistake forgetting the previously mentioned feature. I can tell you, however, that the multi-boot every time you install a new ROM is removed. Going blind I specified / system because it is the main partition is rewritten during a flash. But I have a doubt. The Kernel for secondary ROM, should not be predisposed to function properly?
Click to expand...
Click to collapse
I assure you, you do not have to reflash the mutirom zip Everytime. I have flashed dozens of times on my phone and have not had to flash mutirom again. The only exception is if you wipe internal storage, BC it wipes your "sdcard"
Mutirom patches the kernel when you flash to to secondary, hence almost any kernel will work
Sent from my Pixel XL using Tapatalk
slothdabski said:
I assure you, you do not have to reflash the mutirom zip Everytime. I have flashed dozens of times on my phone and have not had to flash mutirom again. The only exception is if you wipe internal storage, BC it wipes your "sdcard"
Mutirom patches the kernel when you flash to to secondary, hence almost any kernel will work
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
When my CM13 (Internal rom) installs OTA, after reboot multiboot menu won't appear, and i can't select secondary roms for boot them, i solve by re-flash multiboot.zip...
What you have to do in that case is go into the mutirom menu from twrp , then hit " inject boot sector"
That patches the new kernel from the OTA. You dont need to reflash the entire mutirom zip
Sent from my Pixel XL using Tapatalk
slothdabski said:
What you have to do in that case is go into the mutirom menu from twrp , then hit " inject boot sector"
That patches the new kernel from the OTA. You dont need to reflash the entire mutirom zip
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Ok thank you, i will update the guide.
I am trying to install TWRP and root my Mi Mix. I have followed the steps below without encountering any error messages.
1. Go into fastboot
2. Flash TWRP recovery
3. Boot into recovery.
But at the end when I boot into recovery I see Mi Recovery 3.0 instead of TWRP. Am I missing anything? My device is unlocked. I am currently running MiUI 9.6.1 Global stable Android 8.0
sofene said:
I am trying to install TWRPA on my Mi Mix. I have followed the steps below without encountering any error messages.
1. Go into fastboot
2. Flash TWRP recovery
3. Boot into recovery.
But at the end when I boot into recovery I see Mi Recovery 3.0 instead of TWRP. Am I missing anything? My device is unlocked. I am currently running MiUI 9.6.1 Global stable Android 8.0
Click to expand...
Click to collapse
Never mind I solved the problem by booting from the pc. But I have a new problem. Two problems really. First of all I can't seem to get the data partition backed up. I get the error unable to mount *\data *. Secondly I cannot install magisk.zip. I cannot find the file in twrp though it is in main storage in the device. Do I need to copy it to any specific location for the twrp to use it?
Same like your firs post. But i not try instal magisk. I using SU. Now not root and not cusum recovery
sofene said:
Never mind I solved the problem by booting from the pc. But I have a new problem. Two problems really. First of all I can't seem to get the data partition backed up. I get the error unable to mount *\data *. Secondly I cannot install magisk.zip. I cannot find the file in twrp though it is in main storage in the device. Do I need to copy it to any specific location for the twrp to use it?
Click to expand...
Click to collapse
You can install it using a usb stick or via sideload.
You cant backup because the twrp's dont let you enter the password for the encryption on the device thus leaving it encrypted.
If u dont want to delete everything then use sideload for the Magisk installer, if u dont mind then u can go ahead and format data and the encryption will be gone untill you go back to system, then the device will encrypt the data again.
sexlord89 said:
You can install it using a usb stick or via sideload.
You cant backup because the twrp's dont let you enter the password for the encryption on the device thus leaving it encrypted.
If u dont want to delete everything then use sideload for the Magisk installer, if u dont mind then u can go ahead and format data and the encryption will be gone untill you go back to system, then the device will encrypt the data again.
Click to expand...
Click to collapse
I tried to install magisk using sideload enabled but still got error unable to mount storage at the end so I deleted data. And then I was able to install magisk without error. However, when I check root status with root checker it says root was not properly installed. When I went back to twrp I was presented with a screen to enter password to mount I guess the storage or partition. Does this mean that ruth has been installed even though root checker says its not.? Secondly which password is being requested because when I entered my screen unlock password it says password failed. Is it asking for the mi account password or with other password? Thanks for your assistance.
Hi, the only thing that worked for me is to install right after the rom the encryption disabler and you'll be able to use trwp. Just follow the steps in the link below. last thing, when you'll make an update you'll loose again the trwp access.
https://forum.xda-developers.com/mi-mix/development/rom-global-miui9-oreo-mi-mix-t3783869
lnt976 said:
Hi, the only thing that worked for me is to install right after the rom the encryption disabler and you'll be able to use trwp. Just follow the steps in the link below. last thing, when you'll make an update you'll loose again the trwp access.
https://forum.xda-developers.com/mi-mix/development/rom-global-miui9-oreo-mi-mix-t3783869
Click to expand...
Click to collapse
Thanks for your reply. One question, though. Would this then allow you to backup data using twrp?
sofene said:
Thanks for your reply. One question, though. Would this then allow you to backup data using twrp?
Click to expand...
Click to collapse
Yes you can make a backup, but in case of update you'll loose the access on your files in trwp.
A couple things :
1. You can't install magisk if your data partition is encrypted, because magisk needs to put the file in the data partition. so you need to disable the encrypt first, and then you can install magisk.
2. If your data partition is encrypted, don't bother to backup from twrp. Boot to system, connect to pc, and backup using regular way (copy and paste files).
3. Backup your data before you do any encrypt/decrypt process.
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
I have tested some unofficial recovery, but none of those worked.
issues :
1. Touch doesn't response.
2. Only in pitchblack recovery touch worked, but doesn't shows internal storage files, just shows unknown inaccessible files which I don't have in internal storage.
So, does anyone know about a recovery with which I can flash gapps?, or any other way to flash gapps without root, like with pc?
Similar problem here. Unoffical TWRP doesn't respond to touch inputs for me, PBRP does. The garbeled letters inside your storage is probably because of the encryption of the phone.
I don't know on which version you are, but I downgraded to MIUI 11, there you can access the files, sometimes I have to enter my phone password, sometimes not.
It's still encrypted with "FBE" (File Based Encryption) though... At least my console is giving me that output. I can reach the files anyways and flash them, a few of them are working, but often I get errors while trying to flash different types of zip files. The errors are often because of this "FBE" encryption, so the recovery can't mount some partitions or can't access some files (Permission denied)...
But by now, I did not find any way or flashable zipfile (LazyFlasher, etc.) in the web that works to turn the decryption off.
the only build where touch works is 0108. https://androidfilehost.com/?fid=17248734326145712658
iReebu said:
Similar problem here. Unoffical TWRP doesn't respond to touch inputs for me, PBRP does. The garbeled letters inside your storage is probably because of the encryption of the phone.
I don't know on which version you are, but I downgraded to MIUI 11, there you can access the files, sometimes I have to enter my phone password, sometimes not.
It's still encrypted with "FBE" (File Based Encryption) though... At least my console is giving me that output. I can reach the files anyways and flash them, a few of them are working, but often I get errors while trying to flash different types of zip files. The errors are often because of this "FBE" encryption, so the recovery can't mount some partitions or can't access some files (Permission denied)...
But by now, I did not find any way or flashable zipfile (LazyFlasher, etc.) in the web that works to turn the decryption off.
Click to expand...
Click to collapse
Thanks for the reply,
All the things are same for me too. But for most of the people unofficial twrp 3.4.2b works fine, i don't know the problem with my device, and i'm in miui 12.0.3
I daily drive a Redmi Note 10 Pro (great phone for anyone having a 250 euro budget if you can get the 8GB version) and decided to swap roms after getting fed up with MIUI's bull****, I ended up installing Pixel OS via ADB Sideload. After a while, I decided to root my phone (mainly to install some mods for the OS such as Dolby Atmos support etc.) and installed TWRP. However TWRP won't mount storage posting "Failed to mount storage" and pressing "Reboot to system" leads to a message saying "No OS detected", before booting back into Pixel OS just fine. Some people are saying that doing a Dalvik Cache and Cache wipe is supposed to fix this issue, however I can't do that if I cant even mount the storage. Another solution people are throwing around is reinstalling your basic recovery, doing a complete factory reset then installing TWRP and your custom OS. All of these solutions are a huge pain in the butt and I would like to avoid resetting my whole phone for the 4th time in 2 months. Has anyone experienced this and can suggest a fix, or is it something I can attribute to Android 12 not being supported by TWRP yet?
imho you have done it in the wrong sequence, because installing a rom, means encrypting storage.
It could be that you have installed the wrong version of Twrp that doesn't support A12 or that encryption is the reason Twrp can't mount storage anymore.
CvGR said:
I daily drive a Redmi Note 10 Pro (great phone for anyone having a 250 euro budget if you can get the 8GB version) and decided to swap roms after getting fed up with MIUI's bull****, I ended up installing Pixel OS via ADB Sideload. After a while, I decided to root my phone (mainly to install some mods for the OS such as Dolby Atmos support etc.) and installed TWRP. However TWRP won't mount storage posting "Failed to mount storage" and pressing "Reboot to system" leads to a message saying "No OS detected", before booting back into Pixel OS just fine. Some people are saying that doing a Dalvik Cache and Cache wipe is supposed to fix this issue, however I can't do that if I cant even mount the storage. Another solution people are throwing around is reinstalling your basic recovery, doing a complete factory reset then installing TWRP and your custom OS. All of these solutions are a huge pain in the butt and I would like to avoid resetting my whole phone for the 4th time in 2 months. Has anyone experienced this and can suggest a fix, or is it something I can attribute to Android 12 not being supported by TWRP yet?
Click to expand...
Click to collapse
Check here and then you'll revise your opinion
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
TWRP is really unclear about wether it supports Android 12 on it's latest release. I've seen many YouTube videos of people daily driving this particular phone, with Pixel OS and TWRP installed so I don't think it has anything to do with the encryption. It may have something to do with me installing my OS via ADB Sideload and installing a custom recovery afterwards
Elinx said:
imho you have done it in the wrong sequence, because installing a rom, means encrypting storage.
It could be that you have installed the wrong version of Twrp that doesn't support A12 or that encryption is the reason Twrp can't mount storage anymore.
Click to expand...
Click to collapse
Laptapper said:
Check here and then you'll revise your opinion
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
Click to expand...
Click to collapse
Will check it out as soon as I'm back on my PC you're a lifesaver!