So as I just said, by mistake, I installed an image to the firmware partition and suddenly I couldn't install roms anymore, have tried factory resetting, deleting data, some commands that never worked for my device, its shows me the following message: Failed to mount /firmware (invalid argument), what I am thinking to do is flashing the device again starting from zero but how do I do it from the TWRP? Is it really needed or can I do something else to fix my problem?
which partition did you flash? QPST to stock and unlock bootloader
Related
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. Today I flashed the factory image of Marshmallow without much problem. But when I installed MultiRom, problems started to arise. When I tried booting to the primary rom, it took me to recovery. I thought a reflash of the factory image would remove MultiRom. Apparantly I thought wrong. I kept trying to flash system and userdata, but to no avail. Now the system bootloops at Google, and I cant mount /data. I still have access to recovery and bootloader, but TWRP displays Internal Storage as 0MB. Does anyone know how to solve this? It would be very, very appreciated.
EDIT: Fixed, formatted data as ext2, ran e2fsck, then formatted as ext4 again, then flashed userdata.img, system.img, and boot.img in fastboot.
CraftedAndroid said:
Hello. Today I flashed the factory image of Marshmallow without much problem. But when I installed MultiRom, problems started to arise. When I tried booting to the primary rom, it took me to recovery. I thought a reflash of the factory image would remove MultiRom. Apparantly I thought wrong. I kept trying to flash system and userdata, but to no avail. Now the system bootloops at Google, and I cant mount /data. I still have access to recovery and bootloader, but TWRP displays Internal Storage as 0MB. Does anyone know how to solve this? It would be very, very appreciated.
Click to expand...
Click to collapse
Try using the Nexus Root Toolkit by Wugfresh to unbrick.
It will automatically install the latest stock firmware, making your device as good as new.
Just boot into bootloader mode, plug the device into a computer, open up the program, click "flash Stock", and watch as the magic happens.
Having a similar problem - powering on the tablet either leads me to TWRP (with all sorts of error messages like below) or it simply sits at the google screen, in excess of 30min.
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/misc'
E: Primary block device '/dev/block/platform/msm.sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to find mount '/data/'
E:Unable to recreate /data/media folder.
E: Unable to find partition size for '/sbl1'
E: Unable to find partition size for '/sbl2'
E: Unable to find partition size for '/sbl3'
E: Unable to find partition size for '/tz'
E: Unable to find partition size for '/rpm'
E: Unable to find partition size for '/aboot'
E: Unable to find partition size for '/sbl2b'
E: Unable to find partition size for '/sbl3b'
E: Unable to find partition size for '/tzb'
E: Unable to find partition size for '/rpmb'
E: Unable to find partition size for '/aboobtb
E: Unable to find mount '/system'
E: Unable to find mount '/data'
E: Unable to find mount '/cache'
....
E: Unable to find mount '/data/media/TWRP/.twrps' when trying to read settings file
Attempts to wipe in TWRP fail. Attempts to use Nexus Toolkit to
Attempted using Nexus Toolkit to do stock un-root/flash (of 4.4 - 6.0), flash other recoveries, or anything besides /boot and bootloader all fail.
I am still unlocked, was previously rooted (and happy) before this trouble started when attempting to flash the stock recovery, which has never been successful.
Bootloader is flo-4.05, I have also seen 4.02.
Now I'm staring at a bricked device. Is this similar to what you see, CraftedAndroid? Any help would be much much appreciated!!
alexfone said:
Having a similar problem - powering on the tablet either leads me to TWRP (with all sorts of error messages like below) or it simply sits at the google screen, in excess of 30min.
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/misc'
E: Primary block device '/dev/block/platform/msm.sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to find mount '/data/'
E:Unable to recreate /data/media folder.
E: Unable to find partition size for '/sbl1'
E: Unable to find partition size for '/sbl2'
E: Unable to find partition size for '/sbl3'
E: Unable to find partition size for '/tz'
E: Unable to find partition size for '/rpm'
E: Unable to find partition size for '/aboot'
E: Unable to find partition size for '/sbl2b'
E: Unable to find partition size for '/sbl3b'
E: Unable to find partition size for '/tzb'
E: Unable to find partition size for '/rpmb'
E: Unable to find partition size for '/aboobtb
E: Unable to find mount '/system'
E: Unable to find mount '/data'
E: Unable to find mount '/cache'
....
E: Unable to find mount '/data/media/TWRP/.twrps' when trying to read settings file
Attempts to wipe in TWRP fail. Attempts to use Nexus Toolkit to
Attempted using Nexus Toolkit to do stock un-root/flash (of 4.4 - 6.0), flash other recoveries, or anything besides /boot and bootloader all fail.
I am still unlocked, was previously rooted (and happy) before this trouble started when attempting to flash the stock recovery, which has never been successful.
Bootloader is flo-4.05, I have also seen 4.02.
Now I'm staring at a bricked device. Is this similar to what you see, CraftedAndroid? Any help would be much much appreciated!!
Click to expand...
Click to collapse
I'm looking much better than you. I only cannot mount /data and anything under it, like /data/media. Yours looks a bit irreversible if I've ever seen irreversible.
Fixed, updating OP
hello,
i'm having similar problem . I upgraded to 6.0 manually from 5.1.1 via the flash-all method and stucked in bootloop.
it wont boot even after a data wipe.
so
i tried the method fastboot erase boot, recovery, system etc
after a restart it wont boot to anything else but the bootloader.
tried reflashing through various methods it just wont work
here is where its stuck
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.05
Baseband Version.....: DEB-Z00_2.44.0_0213
Serial Number........: 09e4b977
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (7448 KB)...
Click to expand...
Click to collapse
some attempts from fastboot flash also ends up with failure
any ideas?
fr3ker said:
hello,
i'm having similar problem . I upgraded to 6.0 manually from 5.1.1 via the flash-all method and stucked in bootloop.
it wont boot even after a data wipe.
so
i tried the method fastboot erase boot, recovery, system etc
after a restart it wont boot to anything else but the bootloader.
tried reflashing through various methods it just wont work
here is where its stuck
some attempts from fastboot flash also ends up with failure
any ideas?
Click to expand...
Click to collapse
Try doing fastboot flash userdata userdata.img, fastboot flash system system.img, and fastboot flash boot boot.img in that order.
i did that too, I tried flashing tru a lot of method ... it just wont boot at all
does it have anything to do with the partitions? i cant find how to repair a partition for Nexus devices ...
^ So what's it say when you flash each .img individually? You get the "OKAY"?
You say some end in failure which ones? Throw in a fastboot format cache for the hell of it. Your bootloader and baseband are correct?
If you're getting the okay on all images and wiped everything in stock recovery.. I don't know man I might be stuck.
If you figure it out let us know. We can erase and format the partitions, usually you don't even need to use those. Hmm.. I clean flashed flo with just boot system and userdata (bootloader stayed the same as 5.1.1). Worked perfect.
Seems that we're stuck ... I've flashed a custom ROM and works perfect but when I flash any stock firmware it'll stuck at the bootani ... Flashing process were cleared until end ... I get everything as expected. I did everything founded on google and it's still fcuked up ..
Sent from my Z1 using Tapatalk
Well, I decided to flash my phone and forgot that it was encrypted.
Went to TWRP, and wiped everything that it could, but it was stuck in '/data'. This means that my phone got pretty much reseted but the 'data' partition didn't.
The problem now is that I cannot install any ROM. I tried a lot of methods to remove the encryption and some worked, for example:
mke2fs -t ext4 /dev/block/mmcblk0p19
Click to expand...
Click to collapse
This meant that I could restart TWRP without having to put the PIN to decrypt it. But still, It kept failing on me, when trying to install a new rom, with the error:
unable to wipe 'data' -- unknown filesystem 'auto'
unable to format to remove encryption
Click to expand...
Click to collapse
I have no idea of what to do. I tried with DD also, to rewrite the blocks, but it just brought my encryption back.
Can anyone please help me ?
try to flash raw file with asus flashtool
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
Help! I flashed the Android Oreo Pixel 2 Mod over Android Oreo 8.1.0 with my apps and data on it, and then the phone wouldn’t boot. So I went back into the recovery (TWRP 3.2) and tried to wipe the phone. TWRP wiped everything except for /vendor, returning the error “Failed to mount /vendor (invalid argument),” and "Failed to mount /system (invalid argument)". In TWRP I also tried mounting /system and /vendor, but it wouldn't let me check the box. So tried installing the stock android from the google page, and while sending sparse file ‘system’, It says FAILED (data transfer failure(Unknown Error)). Please Help, I’m a pretty much a noob at this kind of stuff.
EDIT: SOLVED
After browsing online, I wiped the phone one more time, re-flashed TWRP, tried a few commands, I tried repairing the file system of /system, re-installed the vendor.img(probably this), then It worked!
I'm just thankful it works now.