Develop Bugs

[Q] Stuck in Recovery, can't flash ROMs

Decided to resurrect my old Verizon GNex, and found that it will only boot to TWRP recovery. Was able to successfully sideload a ROM zip, but attempt to flash produces the following result (copied from phone screen, site won't let me link screenshot):
Formatting /system
Extracting /system
Symlinking
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/sideload.zip'
Updating partition details...
Failed
Any ideas on how to proceed?

First copy ROM on sdcard, then wipe all except sdcard, and then try.

[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.

[solved] TWRP - could not mount /data and unable to find crypto footer

Hi,
Nice to be here after so much years of reading !
My LG G3s (d722) was fine with Cyanogenmod 13 and encryption enabled. I've made a Titanium backup for my apps (& cie...) on the SD card, and reboot in TWRP 3.0.2-0, enter my password to mount storage, and I've wiped all partitions exept the SD card.
Then I've flashed the CM14 zip file, and get these error in the process :
"could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4 mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Unkown error 200 unmount of /data failed; no such volume"
"Failed to mount '/data' (No such device)"
Since then :
- if I reboot into recovery, TWRP doesn't ask me the password to decryp the partition
- if I reboot in CyanogenMod ask me the password, but the tells me :
Decryption unsuccessful
The password you entered is correct but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.​Then it reboot into TWRP
Any ideas ?
How could I mount ext4 partition in TWRP ? Or restore stock recovery ?
Thanks a lot for your advices

resolving !
Hi myself and everyone from another time,
I've resolved this mess by :
- installing LG drivers
- downloading kitkat stock-rom D72210d_00.kdz
- open LG Flash Tool 2014 and load D72210d_00.kdz, and start a CSE Flash
Then stard android 4, root it... etc
Best

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.

[solved] Recovery: "Unable to mount storage"

I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.

Fabian R�ling said:
I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.
Click to expand...
Click to collapse
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.

SubwayChamp said:
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.
Click to expand...
Click to collapse
I have never heard of a "super partition". How do I do that?

Fabian R�ling said:
I have never heard of a "super partition". How do I do that?
Click to expand...
Click to collapse
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.

SubwayChamp said:
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.
Click to expand...
Click to collapse
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.

Fabian R�ling said:
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.
Click to expand...
Click to collapse
Super partition is where some logical partitions are grouped like system, vendor, odm, product, etc.; it depends on the device we're talking about.
As you got a used device, it seems that the last owner did some stuff with it, probably unlocked bootloader (then relocked it) and mess with some custom ROMs (maybe). You can totally fix it by flashing the stock ROM and starting from there, being sure first that you can log in without issues in Google Play (that your account is authorized).
To have this partition readable, you may read this https://forum.xda-developers.com/t/...-mount-system-rw-super-rw-read-write.4247311/ in case this doesn't solve flashing the super partition it is a part of the process to flash the stock ROM.

SubwayChamp said:
flashing the super partition it is a part of the process to flash the stock ROM
Click to expand...
Click to collapse
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.

Fabian R�ling said:
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.
Click to expand...
Click to collapse
You can update through the stock recovery in case your TWRP have actually some issues, flash the stock recovery through fastboot (get it from your stock ROM) and then do the sideload through stock recovery, it's probable that the stock recovery can mount super partition and made readable again the system files that´s within, or you can simply flash this or that partition using fastboot commands, for this you need an unlocked bootloader, nothing more.
BTW did you try formatting data?.
And this tool should work for you https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4217855/

That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.

Fabian R�ling said:
That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.
Click to expand...
Click to collapse
The ROM to be flashed through recovery contains a payload.bin file within others one, this file can be unpacked, not sure if it contains a recovery image though, but you should get it from the full ROM that in some variant comes in oplus format and can be decrypted too, this full ROM contains all the images, it's useful to unbrick a OP device.
Linux doesn't have a counterpart of the Windows applications for smartphones and vice versa in regard to Android development, this is one of the reasons why I have a dual boot machine.
As per the last part it could be an issue from your browser, I didn't have this kind of behaviors from the XDA site.

For "boot.img" and "recovery.img" in the "EU" and the "global" section I get "fastboot: error: boot partition is smaller than boot image". The Magisk version can be installed, but then I get a Qualcomm crash screen when I try to actually start it.

Apparently I have a "OnePlus 7 Pro", not a "OnePlus 7T Pro". I bought that accidentally, but the specs are fine. Actually following the instructions for the correct device worked, who would have thought…