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
[Q] [q] sm-n930f boot loops and error messages after hydra rom install & stock flash
Hello,
I've incurred ENDLESS boot loops after trying to install Hydra Rom. I've been getting very strange error messages also. In light of this, I've tried to flash back to stock through ODIN multiple times, but I've only been successful after I change the partition files to FAT through TWRP RECOVERY beforehand. It gets stalled up, I reset, then only Download mode is accessible, at this point I can get a success message through ODIN when I flash stock.
Interesting enough, the files seem to have reset after the stock flash through ODIN is successful... well, halfway successful. Everything seems to look good but then the screen pictured below shows. I reboot and NOTHING but boot loops. I have to go through obstacles to reflash TWRP and get it working again too, which is how I found the files go from FAT, back to 4.
I'm not sure what's going on, and I wish I had more information, but I'm terribly confused at this point. Anyone have any ideas??????
No Support SINGLE-SKU
Supported API: 3
E: failed to mount /efs (invalid argument)
E: failed to mount /efs (invalid argument)
E: failed to mount /efs (invalid argument)
dm-verity verification failed...
try to install newest twrp and format all or repair partitions ... then try to flash hydra 1.3.5 with hydra kernel 1.2.5 select in aroma .... after this flash csc selection be sure to select your csc and then reboot hope it comes back hehe
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
TWRP won't start after updating from 3.3.. to 3.4.0-0 using fastboot. Output includes "Failed to mount '/data'" - see following post.
I guess because I accidentally ran fastboot unlock although it was already unlocked. (The TWRP website fastboot update procedure starts right back with installing the tools and I jumped in at the wrong place)
Tried installing previous TWRP version but no dice.
Any ideas?
I did a TWRP backup before all this. Not exactly sure where it's located but would like to recover it if possible. Will a factory reset likely overwrite it?
Lenovo P2 LineageOS 17.1 Kuntao
Output when booting to recovery:
Code:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Unable to mount storage
Failed to mount '/data' (Invalid argument)
fs_mgr_mount_all
Full SELimux support is present.
Unable to mount /data/media/TWRP/.twrps
Running recovery commands
Failed to mount '/data' (Invalid argument)
Formatting cache using mke2fs...
Done.
Done processing script file
Renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP.
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…