Develop Bugs

[Q] Lost. SD partition? Can't install ROMs, soft brick

So i'm a noobie. I mean i have some experience (rooted and installed many ROMS like my Nexus One device, i know, ancient) but i got all that information and knowledge on here! So my mom is using this HTC ONE X that she just received and i want to be nice and root it and remove all the bloatware on it and what not. After so many struggles of unlocking the bootloader and all things that fall under rooting the device i was able to FINALLY gain root permission but for some reason i couldn't permanently delete the apps on there like i have in the past with other phones. So, i decided to try flashing a ROM. So i Google'd, YouTube'd and tried to come across the best one i could find. Found a Lollipop Rom somewhere (probably made a mistake on which phone it was for), followed the instructions but didn't backup anything (i know, i know, noob move #1) but it would get stuck on then HTC Quietly Briliant screen (oh and before that, i had a HUGE amount of trouble with the phone using ADB and it being recognized, flashing recoveries and booting into them, it was just a hassle!). I also flashed Clockworkmod at one poit to try and fix things but i was able to get back on TWRP V2.5.0 (tried a higher version but it did not work) so now my phone connects easily to my pc and i pretty much know how to use adb fastboot commands and get into recovery and sideload ROMs but, after many, many attempts at trying to install different ROMs, none work. It'll either stay on the HTC Quietly Briliant screen or won't install and i'll get a message in ADB Sideload:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
script succeeded: result was [0.200000]
Updating partitio details...
E:Unable to mount '/cache'
Formatting Cache using mke2fs...
Done .
Updating partition details...
Wiping Dalvik and Cache Directories....
--Dalvik Cache Directories Wipe Complete!
Also, came across this on a different site:
Here's the solution.
The problem was that I managed to screw up the partitions on my internal storage card, so basically nothing would work properly. I could still get into recovery, though. That's key.
Here's what you'll need:
1 Working recovery, basic knowledge of adb & the shell
2 Parted (download here)
3 stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse
So i thought this may be my problem but then as i get to the parted /dev/block/mmcblk0 mkfs ext2 part of the steps I get stuck because it says something like i can't overlap partitions?
So here i am, desperate for help, trying to fix my mothers phone. Sorry, if i'm not clear enough, i tried my best to recall everything i did (kind of hard after hours and hours of trying multiple things for multiple problems) and all that i've come across without being too specific on things that may not matter (hopefully?). So can anyone help? Please, guide me!

babymatrix said:
So i'm a noobie. I mean i have some experience (rooted and installed many ROMS like my Nexus One device, i know, ancient) but i got all that information and knowledge on here! So my mom is using this HTC ONE X that she just received and i want to be nice and root it and remove all the bloatware on it and what not. After so many struggles of unlocking the bootloader and all things that fall under rooting the device i was able to FINALLY gain root permission but for some reason i couldn't permanently delete the apps on there like i have in the past with other phones. So, i decided to try flashing a ROM. So i Google'd, YouTube'd and tried to come across the best one i could find. Found a Lollipop Rom somewhere (probably made a mistake on which phone it was for), followed the instructions but didn't backup anything (i know, i know, noob move #1) but it would get stuck on then HTC Quietly Briliant screen (oh and before that, i had a HUGE amount of trouble with the phone using ADB and it being recognized, flashing recoveries and booting into them, it was just a hassle!). I also flashed Clockworkmod at one poit to try and fix things but i was able to get back on TWRP V2.5.0 (tried a higher version but it did not work) so now my phone connects easily to my pc and i pretty much know how to use adb fastboot commands and get into recovery and sideload ROMs but, after many, many attempts at trying to install different ROMs, none work. It'll either stay on the HTC Quietly Briliant screen or won't install and i'll get a message in ADB Sideload:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
script succeeded: result was [0.200000]
Updating partitio details...
E:Unable to mount '/cache'
Formatting Cache using mke2fs...
Done .
Updating partition details...
Wiping Dalvik and Cache Directories....
--Dalvik Cache Directories Wipe Complete!
Also, came across this on a different site:
So i thought this may be my problem but then as i get to the parted /dev/block/mmcblk0 mkfs ext2 part of the steps I get stuck because it says something like i can't overlap partitions?
So here i am, desperate for help, trying to fix my mothers phone. Sorry, if i'm not clear enough, i tried my best to recall everything i did (kind of hard after hours and hours of trying multiple things for multiple problems) and all that i've come across without being too specific on things that may not matter (hopefully?). So can anyone help? Please, guide me!
Click to expand...
Click to collapse
When you install some rom are you flash the boot.img with the command fastboot flash boot boot.img where the boot.img is taken from rom archive where you install and puted in your fastboot folder

Thant said:
When you install some rom are you flash the boot.img with the command fastboot flash boot boot.img where the boot.img is taken from rom archive where you install and puted in your fastboot folder
Click to expand...
Click to collapse
Initially on the first rom i remember doing so (still didn't work), but after that i did fail to do it for the other roms.

babymatrix said:
So i'm a noobie. I mean i have some experience (rooted and installed many ROMS like my Nexus One device, i know, ancient) but i got all that information and knowledge on here! So my mom is using this HTC ONE X that she just received and i want to be nice and root it and remove all the bloatware on it and what not. After so many struggles of unlocking the bootloader and all things that fall under rooting the device i was able to FINALLY gain root permission but for some reason i couldn't permanently delete the apps on there like i have in the past with other phones. So, i decided to try flashing a ROM. So i Google'd, YouTube'd and tried to come across the best one i could find. Found a Lollipop Rom somewhere (probably made a mistake on which phone it was for), followed the instructions but didn't backup anything (i know, i know, noob move #1) but it would get stuck on then HTC Quietly Briliant screen (oh and before that, i had a HUGE amount of trouble with the phone using ADB and it being recognized, flashing recoveries and booting into them, it was just a hassle!). I also flashed Clockworkmod at one poit to try and fix things but i was able to get back on TWRP V2.5.0 (tried a higher version but it did not work) so now my phone connects easily to my pc and i pretty much know how to use adb fastboot commands and get into recovery and sideload ROMs but, after many, many attempts at trying to install different ROMs, none work. It'll either stay on the HTC Quietly Briliant screen or won't install and i'll get a message in ADB Sideload:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/s
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at
unmountof system failed; no such volume
script succeeded: result was [0.200000]
Updating partitio details...
E:Unable to mount '/cache'
Formatting Cache using mke2fs...
Done .
Updating partition details...
Wiping Dalvik and Cache Directories....
--Dalvik Cache Directories Wipe Complete!
Also, came across this on a different site:
So i thought this may be my problem but then as i get to the parted /dev/block/mmcblk0 mkfs ext2 part of the steps I get stuck because it says something like i can't overlap partitions?
So here i am, desperate for help, trying to fix my mothers phone. Sorry, if i'm not clear enough, i tried my best to recall everything i did (kind of hard after hours and hours of trying multiple things for multiple problems) and all that i've come across without being too specific on things that may not matter (hopefully?). So can anyone help? Please, guide me!
Click to expand...
Click to collapse
hello babymatrix, i'm wondering if you were able to solve or find a solution to your issue. The reason i'm asking is because i'm on the same boat right now and looking for way to fix a similar issue as yours.
basically, i got a phone with a broken partition like yours. I can still go to recovery but you'll see this message and cannot mount system. I also cannot go into fastboot mode (it hangs when i do a power+vol down)
E: failed to mount block devices /dev/block/mmcblk1p1
E: remount block devices /dev/block/mmcblk1
E: failed to mount /sdcard (No such file or directory)
From searching the net, i figured there's something wrong with the partitioning of the phone. I managed to do adb shell and i could see there's a folder sdcard.
nway, if you've managed to find a solution for your issues, i hope if you could share. thanks.

[Q] help installing ucyan cm 12

yesterday . i downloaded this ucyan cm 12 for my xperia s . and every time when i try to install this rom through CMW and TWRP i get this error
warning: no file_contexts detected filesystem ext4 for /dev/block/mmcblk0p12
and cmw freezes after this error ....
please help .... how to fix this error ?????????????????????????????
P.S : english is not my native language so ignore my mistakes

I have ALMOST the same issue:
I get:
detected filesystem ext4 for /dev/block/mmcb1k0p12
And it's here forever.
Update: After waiting a LOOONG time, I got this:
"ApplyParsedPerms: 1setfilecon of /system/lost+found to ubject_r: system_file: s0 failed: Operation not supported on transport endpoint set_metadata_recursive: some changes failed"
Error executing updater binary in zip ...
Click to expand...
Click to collapse

Re
Maybe first of all you two write the steps performed for flashing Lollipop Roms? I've tried all the Lollipop Roms compiled for SXS and nor,ally I used to do this way:
1. TWRP recovery (but CWM also worked)
Install TWRP recovery in FOTA partition using Terminal apk provided your phone is running on 4.1.2. kernel supporting TWRP recovery. Flash kernel from ROM zip file prior entering TWRP (this step helps avoiding an error like "update binary...").
2. In TWRP recovery - Advanced - wipe everything but sdcard. In Mount section unmount everything but sdcard.
3. Flash the ROM and wipe Cashe&Dalvik
4. Flash appropriate GAPPS, wipe Cashe&Dalvik and reboot.
that's all

I messed up the /data partition. "Partition table doesn't exist".

Hi people,
Today I decided to do a fresh start on my Redmi 1S. I erased all partitions (excluding the bootloader) with fastboot to then install CyanogenMod 12.1. For some whatever reason TWRP can't detect my SD card, so I can't flash any .zip from there (this is a problem I had before I had this idea of a fresh start, so it's not related). And, it says error mounting every partition I have erased with fastboot (edit: now it's only /data), so I couldn't store the .zip to flash in internal storage. I attempted to fix the /data partition using TWRP (Repair file system) and an error occurred and completely destroyed my /data partition. I'm glad I didn't do the same for the other partitions (I was testing it first with the /data).
Then I heard about "ADB Sideloading", which would easily solve my problems I guess, since I could flash the original MIUI and it would bring my partitions back (I think). Well, here's what happened:
Code:
Installing '/sideload/package.zip'
Writing image emmc_appsboot.mbn...
[I]blah blah blah[/I]
E:Unable to mount '/data'
With fastboot I can for example erase /system, but I can't erase /data, fastboot gives this error:
Code:
remote: partition table doesn't exist
How can I fix the /data partition? Am I screwed?
Thanks in advance!
Edit: I just fixed the SD card problem not being recognized. I had to use the tool SDFormatter instead of the built-in Windows Formatting Tool.
Edit 2: I tried to restore a nandroid backup, it stops with "Unable to mount /data" too... The other partitions work fine.

Nixtren said:
Hi people,
Today I decided to do a fresh start on my Redmi 1S. I erased all partitions (excluding the bootloader) with fastboot to then install CyanogenMod 12.1. For some whatever reason TWRP can't detect my SD card, so I can't flash any .zip from there (this is a problem I had before I had this idea of a fresh start, so it's not related). And, it says error mounting every partition I have erased with fastboot (edit: now it's only /data), so I couldn't store the .zip to flash in internal storage. I attempted to fix the /data partition using TWRP (Repair file system) and an error occurred and completely destroyed my /data partition. I'm glad I didn't do the same for the other partitions (I was testing it first with the /data).
Then I heard about "ADB Sideloading", which would easily solve my problems I guess, since I could flash the original MIUI and it would bring my partitions back (I think). Well, here's what happened:
Code:
Installing '/sideload/package.zip'
Writing image emmc_appsboot.mbn...
[I]blah blah blah[/I]
E:Unable to mount '/data'
With fastboot I can for example erase /system, but I can't erase /data, fastboot gives this error:
Code:
remote: partition table doesn't exist
How can I fix the /data partition? Am I screwed?
Thanks in advance!
Edit: I just fixed the SD card problem not being recognized. I had to use the tool SDFormatter instead of the built-in Windows Formatting Tool.
Edit 2: I tried to restore a nandroid backup, it stops with "Unable to mount /data" too... The other partitions work fine.
Click to expand...
Click to collapse
try to flash miui v5 or v6 rom via fastboot

unkown rockstar said:
try to flash miui v5 or v6 rom via fastboot
Click to expand...
Click to collapse
I have MIUI here in a .zip file. Can you tell me the command to flash via fastboot? I tried "fastboot update" but it says that there's no android-info.txt in the .zip file.
To sum up, so far I have tried to ADB Sideload, I have tried to flash that MIUI .zip from TWRP and everything fails with "Unable to mount /data".
I probably need to recreate the /data partition. Any ideas?

Nixtren said:
I have MIUI here in a .zip file. Can you tell me the command to flash via fastboot? I tried "fastboot update" but it says that there's no android-info.txt in the .zip file.
To sum up, so far I have tried to ADB Sideload, I have tried to flash that MIUI .zip from TWRP and everything fails with "Unable to mount /data".
I probably need to recreate the /data partition. Any ideas?
Click to expand...
Click to collapse
there is a seperate rom for fastboot..your can check on miui downloads page for links and step by step guide.

unkown rockstar said:
there is a seperate rom for fastboot..your can check on miui downloads page for links and step by step guide.
Click to expand...
Click to collapse
It worked! Thanks, I didn't know there was a separate ROM for fastboot.

Nixtren said:
It worked! Thanks, I didn't know there was a separate ROM for fastboot.
Click to expand...
Click to collapse
glad to know it worked..now follow all steps correctly

Fatal Error - Cant flash roms

Hello,
I was getting an error after flashing exposed framework that would not let me use my device at all. Something along the lines of com.android.something has stopped/crashed/shutdown and stopped the phone from working and prompted to send report to HTC.
I am on an unlocked htc 10 s-on w/ unlocked bootloader FYI. While flashing a new rom in twrp I'm getting 'zip file is corrupt!' or 'Invalid zip file format!' I have flashed this particular rom before. Happens with viper, profusion, stock deodex, elementalx, and so on.
log when flashing a rom:
Updating partition details...
...done
Full SElinux support is present.
MTP EnabledInstalling zip file '/sdcard/HTC10_DEV.zip'
Checking for MD5 file
Zip file is corrupt!
or
Invalid zip file format!
Error installing zip file '/sdcard/HTC10_DEV.zip'
Updating partition details...
...done
If you have any idea how to solve this please, then you can roast me after. I've been bricked for nearly 2 weeks. I seriously need help here

notsurprised said:
Please see my most recent thread: https://forum.xda-developers.com/htc-10/help/unable-to-mount-repair-wipe-micro-ext-t3716101
I repaired the /system partition. Now I am able to mount everything but 'Micro SDCard' + 'usb_otg' partitions, and cannot repair anything but cache. Still unable to flash rom. Error - 'Zip file is corrupted'
Click to expand...
Click to collapse
.............

??

notsurprised said:
??
Click to expand...
Click to collapse
So you created a thread to point to your recent created thread. Seriously ...... read the forum rules again. This one will be reported to be closed, 1 thread on a subject is enough.

This was a thread I made previously. I didn't make it just to point at my other post.

notsurprised said:
Hello,
e:I got /system to mount after repair.
I am on an unlocked htc 10 s-on w/ unlocked bootloader FYI. After wiping all of my data(I know) while flashing a new rom in twrp I'm unable to do anything to 'MicroSDCard' or 'usb _otg' partitions and am getting 'zip file corrupted' when flashing any files/roms. Initially I was not able to mount /system either, but I was able to repair+mount it. This is the log now when flashing a rom:
Installing zip file '/sdcard/HTC10_DEV.zip'
Checking for MD5 file
Zip file is corrupt!
Error installing zip file '/sdcard/HTC10_DEV.zip'
Updating partition details...
...done
I tried to wipe, repair, and change file system for microsd + usb_otg - some of the logs:
mkfs.fat process ended with ERROR: 1
Unable to wipe usb_otg.
Unable to wipe /usb_otg
mkfs.fat process ended with ERROR: 1
Unable to wipe microsdcard.
Unable to wipe /external_sd
/sbin/fsck.fat -y process ending with ERROR: 2
Unable to repair Micro SDCard
Unable to repair usb_otg.
Error Changing File System
If you have any idea how to solve this please, then you can roast me after. I've been bricked for a few days. I seriously need help here
Click to expand...
Click to collapse
Can you provide a link to the HTC10_DEV.zip you tried to flash?

https://androidfilehost.com/?fid=817906626617945469 from this thread: https://forum.xda-developers.com/htc-10/development/htc10-stock-deodexed-nougat-wwe-2-41-t3556908
Its not the rom - it does this for all of them, I have already flashed these roms previously. viper, profusion, even stock rom. I think it has to sd card but I'm not positive. tysm for responding.... really

So I failed to mention the reason I was re-flashing my rom. I was getting an error after flashing exposed framework that would not let me use apps at all. com.android.something has stopped/crashed/shutdown and stopped the phone from working and prompted to send report to HTC. I didn't think much of it because I was still able to boot. But I don't think wiping 'data' partition is harmful and I'm thinking this has to be it.

[GUIDE]Failed OTA update installation with root/TWRP

As this questions pops up every single month, I'm putting this information into a separate topic. It is for everyone who followed the Magisk A/B OTA update guide and OTA update still fails to install. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The usual culprit is TWRP - if you booted into TWRP and allowed system modifications (even once), OTA update won't install. The second common suspect is one of apps with root access, which might have tampered the system partition (AdAway or some other old apps).
Use these commands as root from ADB shell or terminal emulator on the phone and look for mount count (has to be 0) and last mount time (must be n/a). Anything else means that system partition has been mounted as R/W and you MUST reflash stock system.img manually.
Code:
[I][B]tune2fs -l /dev/block/sda12
tune2fs -l /dev/block/sda13[/B][/I]
sda12 is system_a, sda13 is system_b
Example of untouched system:
Code:
Filesystem created: Wed Dec 31 17:00:00 2008
Last mount time: n/a
Last write time: Wed Dec 31 17:00:00 2008
Mount count: 0
Maximum mount count: -1
Last checked: Wed Dec 31 17:00:00 2008
How to fix - reflash system.img with the same version as currently running (or reflash everything with newer ROM):
Option #1
- download full OTA zip (not the incremental one, size must be above 1gb)
- and this Windows tool https://androidfilehost.com/?fid=818070582850510260
- extract both and put payload.bin into payload_input folder. Then run payload_dumper.exe. Once it completes the job, you'll find all images which can be flashed via fastboot.
- flash system.img to the active partition
- install OTA update
Option #2
- set A as active partition
- download, extract and run flash_all_except_data_storage.bat from stock Fastboot ROM
- root with Magisk patched boot.img and apply OTA with the usual Magisk A/B OTA procedure
Before flashing, backup your important data, one can be never sure enough.

flash_all_except_storage.bat = flash_all_except_data_storage.bat

I have a few questions about this method of yours.
1) I downloaded the fastboot rom from this thread but I can't find the payload.bin mentioned in the first method. Did I download the right thing? All I can see are *.img files and system.img is there too. Can I flash that one?
2) I have both TWRP and magisk installed currently. Will I lose them if I follow your method? How should I go if I wanted to keep them?
3) Of course you advice us to make a backup beforehand. Can you tell me or link me a guide about how to backup and restore properly with the new A/B partion in the way?
I'm sorry for asking this much, but all the guides I'm following are either confusing or with conflicting info.
Thank you for the help, I just can't wrap my head around this dual partion thing :s

SirAugustin said:
I have a few questions about this method of yours.
1) I downloaded the fastboot rom from this thread but I can't find the payload.bin mentioned in the first method. Did I download the right thing? All I can see are *.img files and system.img is there too. Can I flash that one?
2) I have both TWRP and magisk installed currently. Will I lose them if I follow your method? How should I go if I wanted to keep them?
3) Of course you advice us to make a backup beforehand. Can you tell me or link me a guide about how to backup and restore properly with the new A/B partion in the way?
I'm sorry for asking this much, but all the guides I'm following are either confusing or with conflicting info.
Thank you for the help, I just can't wrap my head around this dual partion thing :s
Click to expand...
Click to collapse
1. Fastboot ROM can be used straight away (Option #2).
2. Well, the point of this guide is to restore phone to stock images, so you can install OTA update. TWRP can't be kept. You can flash Magisk without TWRP though.
3. Titanium backup pro is my #1 backup tool for years, except very few exceptions it can backup and restore all apps and their settings. Data partition is only one, so you might have luck using TWRP backup - I haven't tried it.

Thank you kindly for all the info. These days I will try the method you described. ?

_mysiak_ said:
As this questions pops up every single month, I'm putting this information into a separate topic. It is for everyone who followed the Magisk A/B OTA update guide and OTA update still fails to install. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The usual culprit is TWRP - if you booted into TWRP and allowed system modifications (even once), OTA update won't install. The second common suspect is one of apps with root access, which might have tampered the system partition (AdAway or some other old apps).
Use these commands as root from ADB shell or terminal emulator on the phone and look for mount count (has to be 0) and last mount time (must be n/a). Anything else means that system partition has been mounted as R/W and you MUST reflash stock system.img manually.
Code:
[I][B]tune2fs -l /dev/block/sda12
tune2fs -l /dev/block/sda13[/B][/I]
sda12 is system_a, sda13 is system_b
Example of untouched system:
Code:
Filesystem created: Wed Dec 31 17:00:00 2008
Last mount time: n/a
Last write time: Wed Dec 31 17:00:00 2008
Mount count: 0
Maximum mount count: -1
Last checked: Wed Dec 31 17:00:00 2008
How to fix - reflash system.img with the same version as currently running (or reflash everything with newer ROM):
Option #1
- download full OTA zip (not the incremental one, size must be above 1gb)
- and this Windows tool https://androidfilehost.com/?fid=818070582850510260
- extract both and put payload.bin into payload_input folder. Then run payload_dumper.exe. Once it completes the job, you'll find all images which can be flashed via fastboot.
- flash system.img to the active partition
- install OTA update
Option #2
- set A as active partition
- download, extract and run flash_all_except_data_storage.bat from stock Fastboot ROM
- root with Magisk patched boot.img and apply OTA with the usual Magisk A/B OTA procedure
Before flashing, backup your important data, one can be never sure enough.
Click to expand...
Click to collapse
I tried method 1, OTA installation still shows Error message
What next?

oseraphaels said:
I tried method 1, OTA installation still shows Error message
What next?
Click to expand...
Click to collapse
If you are running custom kernel, flash the stock boot.img to boot partition as well.

oseraphaels said:
I tried method 1, OTA installation still shows Error message
What next?
Click to expand...
Click to collapse
Was your system partition mounted as RW in the first place? Is it still untouched? Some apps with root access can still mount it as RW, even if you reflash system.img.

Frank.G said:
If you are running custom kernel, flash the stock boot.img to boot partition as well.
Click to expand...
Click to collapse
I have stock boot img running, still ota install failed
---------- Post added at 10:25 AM ---------- Previous post was at 10:22 AM ----------
_mysiak_ said:
Was your system partition mounted as RW in the first place? Is it still untouched? Some apps with root access can still mount it as RW, even if you reflash system.img.
Click to expand...
Click to collapse
I fastboot flash_all.bat , I think this should mount all ROM segments, including system partitions

I fast boot flashed the latest ROM v11.0.15 and it works perfectly.
_mysiak_ said:
Was your system partition mounted as RW in the first place? Is it still untouched? Some apps with root access can still mount it as RW, even if you reflash system.img.
Click to expand...
Click to collapse
I can't find any apps that may be mounting system partition.
Is there a way to find out?

oseraphaels said:
I can't find any apps that may be mounting system partition.
Is there a way to find out?
Click to expand...
Click to collapse
Yes, compare the last mount timestamp and Magisk log. You will see which app used root access at that time.

oseraphaels said:
As this questions pops up every single month, I'm putting this information into a separate topic. It is for everyone who followed the Magisk A/B OTA update guide and OTA update still fails to install. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The usual culprit is TWRP - if you booted into TWRP and allowed system modifications (even once), OTA update won't install. The second common suspect is one of apps with root access, which might have tampered the system partition (AdAway or some other old apps).
Use these commands as root from ADB shell or terminal emulator on the phone and look for mount count (has to be 0) and last mount time (must be n/a). Anything else means that system partition has been mounted as R/W and you MUST reflash stock system.img manually.
sda12 is system_a, sda13 is system_b
Example of untouched system:
I tried method 1, OTA installation still shows Error message
What next?
Click to expand...
Click to collapse
Flash ota ROM in recovery

Rajendran Rasa said:
Flash ota ROM in recovery
Click to expand...
Click to collapse
Thank you very much
I fastboot flashed the latest ROM and my device works perfectly

Hi,
I have similar issue. My current version is V11.0.1.0.QFQEUXM. The system update show can't install update.
I get the stock version of V11.0.1.0.QFQEUXM fastboot room, and get the system.img. Then I flash it into my current active slot - b. After reboot, I still get can't install update.
The specific error is W update_engine: [0615/084826.432657:WARNING:mount_history.cc(66)] Device was remounted R/W 1 times. Last remount happened on 2020-05-15 10:30:34.000 UTC.
The remount is cause by TWRP.
Is there other suggestion?
Flash ota ROM in recovery
Click to expand...
Click to collapse
Tried to sideload V11.0.2.0.QFQEUXM OTA.zip, but error also.
Thanks.

JackVoo said:
Hi,
I have similar issue. My current version is V11.0.1.0.QFQEUXM. The system update show can't install update.
I get the stock version of V11.0.1.0.QFQEUXM fastboot room, and get the system.img. Then I flash it into my current active slot - b. After reboot, I still get can't install update.
The specific error is W update_engine: [0615/084826.432657:WARNING:mount_history.cc(66)] Device was remounted R/W 1 times. Last remount happened on 2020-05-15 10:30:34.000 UTC.
The remount is cause by TWRP.
Is there other suggestion?
Tried to sideload V11.0.2.0.QFQEUXM OTA.zip, but error also.
Thanks.
Click to expand...
Click to collapse
You've found the culprit already.. Do NOT use TWRP to flash images, it must be done via fastboot.

_mysiak_ said:
You've found the culprit already.. Do NOT use TWRP to flash images, it must be done via fastboot.
Click to expand...
Click to collapse
Hi, the remount is at 15-May. Which I try to fix this issue.
I use fastboot to flash the system.img, but it still mentioned about "remount R/W".
After that, I boot into stock recovery and sideload the OTA.zip, still fail
Thanks

JackVoo said:
Hi, the remount is at 15-May. Which I try to fix this issue.
I use fastboot to flash the system.img, but it still mentioned about "remount R/W".
After that, I boot into stock recovery and sideload the OTA.zip, still fail
Thanks
Click to expand...
Click to collapse
You probably forgot to flash something (or used incorrect image). Just download the latest fastboot image, switch to slot A and flash it all (except storage).

Try flashing with V11.0.1.0.QFQEUXM boot.img and system.img at slot A and B, still couldn't update.
Will try to flash all with the V11.0.2.0.QFQEUXM.
Update status:
I finally solve this issue.
I flash the new fastboot ROM into slot A, my current active is slot B.
Thanks for help.

help please
doing these steps will erase my data like factory reset?
if yes, then how can i install ota without losinig any data

_mysiak_ said:
As this questions pops up every single month, I'm putting this information into a separate topic. It is for everyone who followed the Magisk A/B OTA update guide and OTA update still fails to install. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The usual culprit is TWRP - if you booted into TWRP and allowed system modifications (even once), OTA update won't install. The second common suspect is one of apps with root access, which might have tampered the system partition (AdAway or some other old apps).
Use these commands as root from ADB shell or terminal emulator on the phone and look for mount count (has to be 0) and last mount time (must be n/a). Anything else means that system partition has been mounted as R/W and you MUST reflash stock system.img manually.
Code:
[I][B]tune2fs -l /dev/block/sda12
tune2fs -l /dev/block/sda13[/B][/I]
sda12 is system_a, sda13 is system_b
Example of untouched system:
Code:
Filesystem created: Wed Dec 31 17:00:00 2008
Last mount time: n/a
Last write time: Wed Dec 31 17:00:00 2008
Mount count: 0
Maximum mount count: -1
Last checked: Wed Dec 31 17:00:00 2008
How to fix - reflash system.img with the same version as currently running (or reflash everything with newer ROM):
Option #1
- download full OTA zip (not the incremental one, size must be above 1gb)
- and this Windows tool https://androidfilehost.com/?fid=818070582850510260
- extract both and put payload.bin into payload_input folder. Then run payload_dumper.exe. Once it completes the job, you'll find all images which can be flashed via fastboot.
- flash system.img to the active partition
- install OTA update
Option #2
- set A as active partition
- download, extract and run flash_all_except_data_storage.bat from stock Fastboot ROM
- root with Magisk patched boot.img and apply OTA with the usual Magisk A/B OTA procedure
Before flashing, backup your important data, one can be never sure enough.
Click to expand...
Click to collapse
Thanks for the post.
When i ran flash system.img is says partition unknown!