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
Related
I don't think this is a Moto X (XT1096) specific problem, but more so with TWRP. Phone works fine, just can't backup or restore
I'll try to get a log as soon as I can, just need to figure out how
Problem
I can't backup or restore (and maybe can't delete via TWRP?) from TWRP, getting errors at the start (can't access .../data/cmthemes and can't access .../data/motogallery) and then at the end TarFork() process ended with ERROR=255
Tried Solutions
Reflash TWRP (broke, had to use TWRP app to fix)
Upgrade TWRP (says it failed, but worked)
Enable Compression (no real difference that I can tell)
Cause?
I was on CM13 (2/2 ?), upgraded to most recent (2/6), didn't like it so wiped and flashed to original (1/29 ?) then restored backup (2/2). Probably wasn't the best way to do that, oops. Since then I have wiped and reflashed 2/2 and upgraded to 2/7, haven't done anything since (besides mess with TWRP)
Any help or ideas would be appreciated!
Please lock/delete
Solution: Factory reset, only method that worked for me
Be sure to clear cache
Solution: There is a file on the phone that is preventing the backup. Not sure what is creating it. It could be an artifact of a TWRP backup restoration, which is the first time I had the problem.
Look in the TWRP log ([SDCard]/recovery.log) and scroll near the end - you will find the culprit there, almost always in the [root]/SYSTEM folder but sometimes in multiple folders. It has many names. I've seen it called, simply "999". On my Moto G4, it was "d.addon". Delete the folder and you're good to go.
I've been all over the OP3T forums looking for current information about the correct versions of TWRP and (Magisk or SuperSU) to use with stock OOS 4.1.6. I kept my old TWRP 3.0.4-1 and when I tried to apply SuperSU 2.79 SR3 I got an unusable system and had to restore from nandroid backup. I updated to TWRP 3.1.1-2 as per the Official TWRP app and now every time I try to reboot to system from TWRP it warns "No OS installed", but the reboot works fine. I have Magisk 13.2 ready to install but I'm reluctant until I know I have the right combination - the TWRP 3.1.1-2 backup is missing some partitions and I want to make sure I can at least recover my system if Magisk screws things up.
I've been all over the forums and all the relevant threads were closed months ago, or are written about OOS 4.0.3 or 4.1.1, or describes some hideous way someone turned their 3T into a pile of molten lava. Is there any current information about what combination of TWRP and a root zip will work with the latest OOS 4.1.6? Everything is stock except the unlocked bootloader. I don't want to flash a different ROM, I don't care about passing SafetyNet, I just want to root and go on with my life.
A couple of numbers is all I ask. I can't be the only one. Please - I've been without root for a week and it's bugging me.
TWRP 3.1.1-2 has got at least one major bug where it reports the OP3T as a OP3. That'll mess up your OP3T specific installations... Don't know if there are any other bugs, since I'm staying on 3.1.1-0 until they fix that bug. You also have the option of using blu_spark's TWRP. I've never tried it, but many users swears by it.
What works for me:
OOS 4.1.6
Franco Kernel r25
TWRP 3.1.1-0 (official)
Magisk v13.2
Magisk Manager 5.0.6
No issues whatsoever (for me)...
Thanks for that. I'd rather not change kernels, though. How likely is it that the same combination works with the stock kernel? Does anyone have that running?
OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."
So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.
Advice?
OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."
So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.
Advice?
Scratch that request. Things seem to be turning around - su works in terminal emulator, lets me ls privileged directories like /data. Root Explorer is working again. The only thing that isn't is AdAway, which can't write the hosts file. Otherwise the system seems to be rooted and working OK.
I'm still nervous that TWRP can't see that there's an OS on the phone, and I haven't seen any other reports of this.
It looks like Magisk can't mount /system read-write. Adaway won't install, and neither will Busybox. Titanium Backup also reports problems. I tried installing Busybox and the installation failed when it tried to remount system /rw.
Will look for solutions to this problem and report back here.
I've found many solutions to this problem, like installing busybox (Stericson Busybox apparently doesn't work in OOS 4.1.6, tried two others. Problem is, busybox will only install into a partition on /system, which requires that /system be read/write.
When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...
JMB2K said:
When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...
Click to expand...
Click to collapse
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.
mobilityguy said:
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.
Click to expand...
Click to collapse
I seem to remember having that problem once before.... Can't recall what I did, I think it involved something with the terminal... I'm not at my desk right now, I'll look into it shortly and see if I can remember
Problem solved. The more I looked at the symptoms, the more I realized that the OTA I took after unrooting with SuperSU corrupted the system partition somehow. The first time I tried applying the OTA with the stock recovery it failed, but I was able to reboot and apply 4.1.6. That's when the trouble began - I was unable to reapply SuperSU. Fortunately I had done a nandroid backup between the upgrade and the attempt to re-root, and after the SuperSU script failed I was able to restore the backup (made and restored using TWRP 3.0.4-1) and continue working. It was either at that point or earlier, during the OTA itself, that /system was damaged - not badly enough to prevent the phone from working perfectly well, but enough to keep TWRP from mounting /system read/write. From that point on I was doomed. None of my other attempts to fix the problem had a chance as long as TWRP was restricted to mounting /system read-only. Then it got worse.
After a semi-failed attempt to install Magisk (rooted applications worked as long as they didn't try writing to /system) I restored my pre-root 4.1.6 backup one more time. After that, TWRP wouldn't mount /system at all, which prevented me from making any more nandroid backups.
It was time to act. I could keep using the phone unrooted, but the longer I went on the more work would be required to put things completely right. The risk would increase because I couldn't take any more snapshots of the phone to fall back to if I munged the device again. I also had a positive reason to fix things - during the two days the phone was rooted but couldn't access /system, Titanium Backup kicked in and did a full backup of all my software and settings.
With a damaged file system and full backups, there was no reason for halfway measures. I copied all my user data off the phone and used LloydSmallwood's unbrick tool to flash the phone back to its original OOS 3.5.4 state. That took care of rebuilding all file structures. As soon as I rebooted, OOS upgraded to 4.1.6 in one step, taking care of the system upgrade. Unlocked the bootloader, installed TWRP 3.1.1-0 (not 3.1.1-2, which has a serious bug for the 3T as someone posted above). I was able to mount and unmount /system from TWRP's mount screen, no problem. Ran Magisk 13.3 script without a problem, installed Titanium Backup, and tested an app restore. No problem. I'm now in the midst of copying all my stuff back onto the phone, after which I'll restore all missing apps and be back in business (I hope).
It's possible I could have done something tricky like reformatting /system and restoring the partition from my last good nandroid backup. But I always would have been concerned that problems would have popped up later, maybe during the Android O upgrade, when it would be way too late to recover my then-current setup. After seeing virtually every combination of working and non-working features, it just made sense to build from a clean system.
So thanks have been given to LloydSmallwood for his absolutely indispensable unbrick tool (this is the second time it has saved my phone). I should also thank my Galaxy S3, running the current build of LineageOS, which has gotten me through the two days it took to set my OnePlus straight. The Galaxy has performed better than a five year old phone running brand-new software should ever be expected to - if it supported LTE I could consider using it as a daily driver. This has been an education, and a reminder of how important it is to keep good backups at every step throughout an upgrade - and routinely during production use.
Thanks to all who gave advice in this thread.
Hello, I recently bought the Xiaomi MI 6X and I want to install Android to replace the MIUI since I have certain limitations.
I have problems to install the Android image through the TWRP, after passing the image of TWRP to the cell phone with the command "fastboot boot twrp-3.2.3-1-wayne.img" the TWRP screen appears asking for a password, apparently it is encrypted, the strange thing is that I do not have a password on the phone and still ask me for the password, I have the option to swipe and go to the TWRP options, but when I'm in the options to install the image I can not see all the files / folders to find the image of Android that I copy in the internal memory, in addition to this I mark "0 BM Internal Storage" when I am scanning the files.
I really need your help to solve this problem, it is becoming a headache for me, help please!
isaac.nunez said:
Hello, I recently bought the Xiaomi MI 6X and I want to install Android to replace the MIUI since I have certain limitations.
I have problems to install the Android image through the TWRP, after passing the image of TWRP to the cell phone with the command "fastboot boot twrp-3.2.3-1-wayne.img" the TWRP screen appears asking for a password, apparently it is encrypted, the strange thing is that I do not have a password on the phone and still ask me for the password, I have the option to swipe and go to the TWRP options, but when I'm in the options to install the image I can not see all the files / folders to find the image of Android that I copy in the internal memory, in addition to this I mark "0 BM Internal Storage" when I am scanning the files.
I really need your help to solve this problem, it is becoming a headache for me, help please!
Click to expand...
Click to collapse
Happened to me a lot of time, I had to format data (with a twrp with working mtp), but if someone have a better idea wait for a different solution
you have to wipe data thats all i know. thats the way twrp can encrypt the storage.
Oceansoul91 said:
Happened to me a lot of time, I had to format data (with a twrp with working mtp), but if someone have a better idea wait for a different solution
Click to expand...
Click to collapse
Ignore
Hello,
today I did have a strange experience with my ROG 2 and my best guess is that there is some UFS problem, but a second opinion or ideas are welcome.
During a bike ride when I was wifi scanning (apps: "Tower collector", "Radio Beacon"), navigating and listening to an audio book, the phone just went dark. I thought from previous experience on a Note 3 that it might have overheated. Pretty much stress proofed from the previous phone.
Yes - it was warm in its bike pocket but really not overly hot.
The phone is an ebay buy 2 months old and has been ever since with omnirom, stable so far. I only noticed that the RGB LED here has no blue light, but I plainly did not care.
I tried to boot it after some 10 minutes again and the phone would not go past its omnirom boot screen until it reboots after some time, boot loops.
30 Minutes later at home I wondered then what is going on, and I copied off the TWRP backup from the phone I took two days ago, just in case.
I then tried to restore the same backup, but the phone switched off during restore after ~30%. This was reproducible, so I thought this may be something with the backup, maybe I cannot restore a partition. When I restore I had all partitions marked and I tested them one by one. The restore of single partitions worked, one by one, except vendor as it was marked read only and data as it failed unpacking (my recent backup then is dead?).
I then tried formatting the partitions, so "data", originally f2fs. I lack experience with journal recovery on f2fs so went to ext4. System was ext4 and was just wiped. I lost of course other data on the internal storage so tried to restore again with my copied backup. It restores, but it cannot boot and just bootloops. I now formatted all partitions, including vendor.
Finally, I tried downloading omnirom again and installed it. It won't boot, it doesn't even get to the boot animation, but just boot loops.
I reformatted data back to f2fs. But no change here.
Trying more: lineageos won't flash for unknown reasons, it immediately dies as "Error installing zip file". Checksum of the downloaded zip is correct.
I downloaded a stock rom and installed it. This is now the best result so far - It does want to boot.
Here I get a boot animation and this incredibly lame "tching" sound (it is a phone, not a sword...). But it also stops there and never continues. Yes, first boot takes longer, but not 10 minutes.
Any ideas what else to try with this phone?
So far, I can boot twrp via sideload and interact with it fine. But that will be it; ran out of ideas.
Happy for suggestions.
Gaya
Use raw firmware to restore everything.
Install latest firmware zip on both slots.
After installing custom roms go to wipe -> format data by typing yes. Otherwise rom wont boot
thanks for getting back, If by raw firmware you meant the ASUS stock, I did. Not sure why data wipe after installation or double install to a/b partition would make a difference, but in the end I am new to this a/b concept, looks though like standard dual boot to me. Tried it, but no difference.
- installed asus firmware to inactive B
- switched to B partition
- installed asus firmware to inactive A
- wiped data
- started, so far same behaviour after 15 minutes of waiting (boot animation with sound, then it repeats boot animation until ...).
There are Two kind of rom raw firmware (used to restore bricked device) and recovery rom (zip file we use for update)
Raw firmware will flash ROM to both the slots, while recovery rom only flash to one slot. So you need to Only select reboot to recovery after flashing ROM to switch to the updated slot.
No, stock rom is not exactly raw firmware. RAW firmware uses EDL mode (in bootloader) to flash the stock rom. Download A10 raw from here version .90.
when extracting it you will see some files.
Steps To flash Raw:
* enable usb debugging in phone.
*connect the phone via side port to pc
open command prompt and run this command
adb devices
adb reboot bootloader
Now go to the folder where you extracted the raw firmware & run "flashall_AFT.cmd" as admin
wait [there will be no output]. After 15 -20 mins your device should boot. If you have any old version stock rom data the phone will carry the data to new version. If you have any custom rom/ updated version of stock rom data, it will ask to factory reset, so do that.
wiping is not exactly formatting so do it the right way
Why format: the one where you format by typing "yes" .If you switch between Roms ( stock to custom or vice versa) and go back to older versions (v .100 to .60) the old/previous rom data cant be used with new one so you must format data.
when formatting is not necessary : If you want to upgrade both stock images (version .90 to .100) & custom rom (v 1 to 1.2) i.e., flashing stock rom and then custom rom over it, you dont need to format data because you can reuse the data from custom rom to updated custom rom.
A/B device use two partition instead of one. so the upgrade can happen in the background. On restart you will switched to updated slot. So room for error is less.
The wiping here should be the same as formatting, as it is running the mke2fs (as per TWRP settings). But raw rom I do not have (I believe).
The link you have there seems broken, could you repost it again?
I did download the stock ROM earlier from ASUS directly, to not violate policies, HTTP links etc, here is only the path on asus . com
pub/ASUS/ZenFone/ZS660KL/UL-ASUS_I001_1-ASUS-17.0240.2103.75-1.1.229-user.zip
That is the one I installed via recovery. Am not sure what is in your mentioned flashall_AFT.cmd though, but suspect some adb sideload at least.
I eventually succeeded, but of course would liek to know
1) why
2) what happened?
I did follow a video about flashing the stock rom, basically as you explained (factory reset and data wipe), twice to a and b partition. That made the device bootable. Why is this needed?
I tested wiping system again (I am used to doing clean flashes) and installed omnirom again, and it failed booting.
I installed again the a/b with stocks, factory reset and data wipe and installed omnirom as dirty flash. All is well.
Now I was able to restore my backup finally without the device switching off and it did not complain about the data backup. So finally I am with my phone again rom and copy data to my fresh partition.
as to 1) why?
I understand a/b partition as sort of windows/linux dual boot with a more separate bootloader maybe. So I do not see the point in flashing the stock rom twice or in rendering the device unbootable when wiping system.
and as 2) what happened.
I may only guess: I did an omnirom upgrade 2 days earlier that worked fine and was the reason for my nandroid.
During my ride, the phone had some whateverissue and rebooted. I am unsure whether i tested booting but assume that after the upgrade it flashed to the other partition and it was not bootable. It does not make sense as this would make a/B partitions rather hard for custom rom makers, e.g. people complaining all the time.
Other guess: there was a file system issue with f2fs. Problem with data partition seems to cause bigger issues.
When I flash to ext4 after testing the bootable rom with a wiped data, it would not boot anymore. After factory reset again, it mke2fs the data partition again, back to f2fs and the device booted again happily.
Thanks for the help. Happy to know/learn more about this issue, as I would love to prevent or handle them quicker with more of I know what I'm doing.
Android Dual Partition (A/B) is made for seamless updates i.e, Dual system/vendor partition but uses same data partition. Lets say you are currently in slot A when you apply system update the slot B gets updated. As always rebooting the device switches to the B partition after update. & further update flashes the system to the A partition.
Basically there is no need to flash stock rom twice, unless you are coming from stock [one partition might be in higher firmware version than other] or there is new stock version with some minor/major upgrades to firmware files.
Our custom ROMs are not stand alone, Mostly it only replaces the system files and keep the vendor same as stock. (also this keeps the ROM update file size to be minimum)
you might even have different version of Android in A/B partition.
Here is a scenario on How A/B works:
Say you are currently using your device in B-slot and A9 so partition on slot-A will be A9 partition slot-B be A9. After that you are doing system update to A10 from System update (not via TWRP)
now you will have A10 on slot-A and A9 on slot-B.
then you want to go to custom rom, so you flashed say omni on A-slot and rebooted & it will surely work.
After that you are using inbuild system update from custom rom any applied it. now the system update will overwrite the A9's system files but (the device specifically needs A10s vendor to work properly). Now comes the fun part i.e., soft brick, boot looping, and corrupt images
That's why you have to flash latest stock to both A and B slots, and overwrite them all with system files from custom rom (also should be flashed once in slots A and B) to get neat experience from custom ROMs.
If you understand what was written above, then you will know the reason behind soft brick.
stock rom flashed only once (firmware image variation may affect stability)
custom rom only flashed in one slot (switching slot will boot loop device)
Not using Reboot to recovery to flash (you will be flashing to the same slot over and over & thus rebooting will boot loop)
Not formatting data ( Just Maybe, your custom ROM and stock uses different file system for data partition)
For Raw files search "ASUS rog 2 RAW firmware images" those files will be around 3 GB in size.
Would it be possible to backup different images from different GSI ROMs to be able to test and restore each one without losing all the apps, configuration, etc. in the process.
For example:
1. Install "GSI name1" configure it, install apps, my Google account, etc.
2. Somehow, make a backup of the required partitions "backup name1" (At the computer?)
3. Install "GSI name2" configure it, install apps, my Google account, etc. (Not necessarily the same apps than before).
4. Somehow make a backup of the required partitions "backup name2".
5. Continue testing other GSI or restoring one of the previous ones from the backups and be able to use the phone as it was before, including apps, configuration, etc.
I can imagine two ways to face this task:
A. Using a custom recovery to backup partitions to SD card.
B. Using fastboot or mtk_client to backup partitions to the PC.
Would be easy? Possible? Not recommendable for some reason?
I am new on this flashing-bricking-sweating-unbricking thing, so I would appreciate feedback.
Thank you!
Hi
If your goal is to test the GSIs, it's easier to use the DSU-sideloader instead of the backup.
This app enables you to dual boot.
You will be able to move back and forth between images. Even if you get into a boot loop, you can return to the original image just by rebooting.
If you have root, this app will be easier because there will be less operations.
https://github.com/VegaBobo/DSU-Sideloader
I have been taking a look to the DSU concept. It is interesting, but not what I want. Also, it requires the main ROM to be stock ROM (maybe in future is fine to use with custom ROMs).
DSU would be perfect if you want to keep romA and romB working in parallel in your daily life (for example, one for work and business and the other one for gaming and social apps).
What I want to do is to test romA for a while, move to romB for a while, if I prefer romA, reinstall it and forget about romB (literally, delete it). Maybe in few months, backup romA again and check romC for a while...
As I do not want to be swapping from one to another in daily life, it does not make sense to reserve space for having both simultaneously ready to work on the phone.
By now I have been learning about adb and recovery backup options. I need to check more during the next days, but I noticed that from Recovery, I can also use adb (it says not authorized device, but that is for not being rooted yet, I suppose). If it is possible to use adb from recovery after rooting, it would be easy to have a PC software for backing up ROMs easily (system, data and userdata partitions?).
I will keep researching about it...
The DSU does not have to be a stock rom.
It's just desirable.
Currently I have crdroid GSI as the first OS and the second OS is trying several OSs.
If you try it, you'll notice how easy it is.
Currently, TWRP does not support backup or encryption on Android 12. It is the same even if it is the official latest of other models.
I have a 128GB model, so it took too long to back up using mtkclient and I quit halfway through.
The problem is time and encryption, keep them in mind.
Currently, TWRP does not support backup or encryption on Android 12. It is the same even if it is the official latest of other models
Click to expand...
Click to collapse
Well, definitely untrue now as most devices have got it sorted out with decryption, Android 12 being a pain some devices got 13 done before 12, but as of the time you wrote this post my device Motorola stylus 22 5g Qualcomm, we hadn't figured out the decryption yet but you could definitely just patch your fstab in vendor either by hand or with DFE neo, to disable the encryption and TWRP would run fine. You would just have to make that first format reboot back to recovery immediately and while it still stays the data from a fresh format flash the other handy RO2RW re zip and DFE neo. Honestly the boot times are so much better without decryption I don't think I would go back as long as I've got a password on orange fox or whatever.