(Be aware that I am a big newbie at this)
I'm using TWRP v2.1.1
Every time I try to flash a ROM it immediately says Failed! in red.
Right now I'm trying to unroot my kindle to fix the problem, but when I go to flash update.zip it does the same thing, it fails.
Here's the error right when I flash update.zip, There's no hesitation, just instantly failed. No loading bar or anything.
Code:
From top to bottom
* Verifying filesystems...
* Verifying partition sizes...
-- Verify md5 for /sdcard/update.zip
-- md5 file not found
-- aborting install
Error flashing zip '/sdcard/update.zip
Formatting /sdcard...
Using rm -rf on '/dev/block/mmcblk0p12'
-- Verify md5 for /sdcard/update.zip
-- md5 file not found
-- aborting install
Error flashing zip '/sdcard/update.zip'
(Same thing, As it does a factory reset and wipe Dalvik cache,
No need to write all that)
Aborting install
Error flashing zip '/sdcard/update.zip'
I appreciate any help anyone can give me.
Thanks in advance.
Edit: Disabled Force MD5 check on all zips, Flash is still failing.
You need to disable md5 checking
[Edit:] I should have paid more attention to the post. Don't choose "install update.zip from sdcard", only "install...". Unless you're installing an update.
Disabled it in settings, Still failing.
Edit: Don't know what you mean by choosing only install ...
What recovery is this? Why is it trying to delete the /sdcard partition when installing a ROM? That doesn't make any sense.
I'm using TWRP v.2.1.1, if that's what your asking. And I know, this is weird seeing as I've researched the problem and no one has seem to had it.
iKrotos said:
I'm using TWRP v.2.1.1, if that's what your asking. And I know, this is weird seeing as I've researched the problem and no one has seem to had it.
Click to expand...
Click to collapse
I hope you edited that post to include the big bold letters at the top... or my eyes are worse than I thought.
This...
Formatting /sdcard...
Using rm -rf on '/dev/block/mmcblk0p12'
is what's troubling to me...
What ROM is this? Have you played around with your partition table? Can you use parted to get a look at your partition table?
While booted into TWRP...
Code:
adb shell parted /dev/block/mmcblk0 unit B print
Got the Update.zip (Unroot) to Flash. (All I did was uncheck the 2 boxes, signature one and MD5 one and it worked)
Now I'm going to re-root my kindle and try to install another ROM and if it keeps failing I'll get back to you. Let's hope it works ...
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.
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
Hello all,
EDIT: I am unable to repair any of my partitions except cache
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
If you have ANY idea please reply. I will most likely not get this fixed as I have been troubleshooting this for a week. I am active on here so I will get back to you asap.
5. Create a thread or post a message only once.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
Thread closed.
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…