I have a family member's phone (N7100) that was stuck on a bootloop. This phone was never rooted or had any custom recoveries or roms installed on it. When I go into recovery I see that I'm getting the common "e:failed to mount /efs(invalid argument)". When trying to google the problem I found that common fix for it:
Code:
adb shell
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
So I go ahead and do this but I notice that even though the phone is out of a bootloop and goes into factory mode (I already know how to get out of it), it doesn't connect to the phone network. Going back to recovery I see that EFI is still not able to be mounted but the error is different "failed to mount /efs Operation not supported on transport endpoint".
I can tell that if I ADB into the phone and do "mount -w -t ext4 /dev/block/mmcblk0p3 /efs" it will mount just fine. Anybody knows what is happening? To make everything worse he doesn't have a EFI backup so at this point I'm thinking the phone is dead no matter what. Suggestions?
Thanks
Try flashing stock ROM.
Skull97 said:
Try flashing stock ROM.
Click to expand...
Click to collapse
I already did and it didn't help. Googling the problem doesn't seem to give me any results for that particular error line.
Bump! I hate to do this but I think this is my last chance to fix it. Google is not giving me any good leads for me to latch on.
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.
When I boot my phone I get the message "Device storage corrupt" and it prompts me to reboot into recovery. However TWRP doesnt automatically fix the problem. In TWRP most operations terminate with the message "Unable to mount /data". I cannot wipe /data because it gives me that error.
Is it a problem with the partition table? Should I be trying to flash a PIT file using Heimdal? (I am new to Samsung sorry.) If it is a problem which can be sorted out by manually partitioning, I'm a pretty deft hand with the linux shell and maybe the adb shell isnt too different.
TIA
Oh no ! You have updated your phone to an locked bootloader ! You can't flash now something.
Word to the wise: I was able to fix this problem by reformatting the /data partition. For some reason twrp was not able to do this.
0. Reboot into twrp and if necessary disable MTP in the mount menu.
1. Then I found out the name of the partition block device which holds the /data partition. I found this out by trying to wipe the data partition using TWRP and noting the error message. For me that was mmcblk0p24.
2. Run adb shell mke2fs -T ext4 /dev/block/mmcblk0p24
Problem solved!
Hey folks! I unlocked my FireTV stick and was able to install TWRP following the amazing guide by @k4y0z (https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-tv-stick-2nd-gen-tank.3907002/).
I can boot into TWRP just OK.
I am using adb shell to issue TWRP commands. (I don't have an OTG cable with power input).
I began by flashing stock ROMs by @0815hoffi from here (https://forum.xda-developers.com/t/...-7-ota-zip-launcher-replacement-root.4155489/).
Then I tried installing pre-rooted images by @rbox (https://forum.xda-developers.com/t/fire-tv-stick-2-tank-prerooted-stock-images-5-2-7-3_r1.3912271/) along with magisk.
Here are the general steps I followed while flashing these images :
1. wiping everything. I suspect my first issue here :
Code:
$ adb shell
$ twrp wipe cache
$ twrp wipe data
$ twrp wipe dalvik
$ twrp wipe /system
~ # twrp wipe cache
Formatting Cache using make_ext4fs...
Failed to mount '/cache' (No such device)
Done processing script file
Click to expand...
Click to collapse
~ # twrp wipe /system
Formatting System using make_ext4fs...
Failed to mount '/system' (No such device)
Done processing script file
Click to expand...
Click to collapse
~ # mount /cache
mount: mounting /dev/block/mmcblk0p12 on /cache failed: No such device
Click to expand...
Click to collapse
~ # stat /dev/block/mmcblk0p12
File: '/dev/block/mmcblk0p12'
Size: 0 Blocks: 0 IO Block: 4096 block special file
Device: ch/12d Inode: 5332 Links: 1 Device type: b3,c
Access: (0600/brw-------) Uid: ( 0/ root) Gid: ( 0/ root)
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Access: 2010-01-01 00:17:58.000000000
Modify: 2010-01-01 00:17:57.000000000
Change: 2010-01-01 00:17:57.000000000
Click to expand...
Click to collapse
2. push images to /sdcard
Code:
$ adb push update-kindle-full_tank-288.6.6.4_user_664657620.bin /sdcard/firm.zip
update-kindle-full_tank-288.6.6.4_user... 6.1 MB/s (532252995 bytes in 83.009s)
3. Install image
adb shell
~ # twrp install /sdcard/firm.zip
Installing zip file '/sdcard/firm.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
[amonet] Remove boot patch...
[amonet] OK
Patching system image unconditionally...
Copying preloader_prod.img to boot partition 0 for secure device...
script succeeded: result was [][amonet] Install boot patch...
[amonet] OK
[amonet] Install recovery patch...
[amonet] ALREADY_INSTALLED
Done processing script file
Click to expand...
Click to collapse
4. `adb shell reboot`
They all install just OK. But in all cases, every time I do `reboot` in `adb shell` after `adb install` commands, it boots and gets stuck on 'fireTV Stick' logo.
At first I thought maybe it takes time to boot for first time, but I let it go for as long as half an hour and still no good.
I tried wiping cache and dalvik before rebooting too, no avail (had same could not mount /cache prompt).
I am pretty sure I am doing something stupid, I'd really appreciate any help. I'll be happy if I get it back to a working state, I do not really need root. This all started because the stick went into bootloop outta nowhere. My initial finding pointed at a failed update, see :
https://twitter.com/i/web/status/1393963756426698756
Maybe try with 5.2.7.7
ftvs2k-5.2.7.7
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
0815hoffi said:
Maybe try with 5.2.7.7
ftvs2k-5.2.7.7
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Thanks @0815hoffi , that's actually the very first image I tried with from your thread.
Looking back, I think there's something wrong with my partitions.
If I see logs of other people from these threads, it says
script succeeded: result was [ALL DONE][amonet] Install boot patch...
Click to expand...
Click to collapse
Whereas for me, it says
script succeeded: result was [][amonet] Install boot patch...
Click to expand...
Click to collapse
This may mean that my flash is not successful, right? It's same everytime I flash.
I wonder, is there a way to bring everything to a clean state?
Given your expertise in amonet, @k4y0z from the thread and this comment, do you have a suspicion of what could be going wrong?
It looks like like it indeed were messed up partitions. My initial plan was to flash GPT fix in DL mode (by @k4y0z : link). But I thought might as well play with few things if am anyway going to re-do everything.
I started by going deleting directories manually (e.g. `rm -rf /system`). My plan was to manually flash each partition through fastboot.
Before that I attempted
Code:
fastboot format all
and received a bunch of errors, specifically
Code:
Formatting is not supported for file system with type ''.
Though format didn't work, I decided to wipe anyway
Code:
fastboot -w
It finished with few errors, but looked like it created those directories which I deleted earlier. So I rebooted to TWRP and did
Code:
twrp wipe data
Re-flashed @0815hoffi 's image and luckily it booted into "Optimising storage" screen. Post boot-up it appears to be working OK so far. Had an issue with wifi, but restart fixed it.
tl;dr
Code:
rm -rf /cache
rm -rf /data/dalvik
rm -rf /system
fastboot format userdata # errors
fastboot -w # completed but some errors
twrp wipe data
twrp install <img.zip>
reboot
EDIT : Looks like @Sus_i and @racega went through a similar journey and ended up with a similar fix. Good to know the fix is reproducible. Here's their posts : https://forum.xda-developers.com/t/...ck-2nd-gen-tank.3907002/page-61#post-83031003
saurabhshri said:
It looks like like it indeed were messed up partitions. My initial plan was to flash GPT fix in DL mode (by @k4y0z : link). But I thought might as well play with few things if am anyway going to re-do everything.
I started by going deleting directories manually (e.g. `rm -rf /system`). My plan was to manually flash each partition through fastboot.
Before that I attempted
Code:
fastboot format all
and received a bunch of errors, specifically
Code:
Formatting is not supported for file system with type ''.
Though format didn't work, I decided to wipe anyway
Code:
fastboot -w
It finished with few errors, but looked like it created those directories which I deleted earlier. So I rebooted to TWRP and did
Code:
twrp wipe data
Re-flashed @0815hoffi 's image and luckily it booted into "Optimising storage" screen. Post boot-up it appears to be working OK so far. Had an issue with wifi, but restart fixed it.
tl;dr
Code:
rm -rf /cache
rm -rf /data/dalvik
rm -rf /system
fastboot format userdata # errors
fastboot -w # completed but some errors
twrp wipe data
twrp install <img.zip>
reboot
EDIT : Looks like @Sus_i and @racega went through a similar journey and ended up with a similar fix. Good to know the fix is reproducible. Here's their posts : https://forum.xda-developers.com/t/...ck-2nd-gen-tank.3907002/page-61#post-83031003
Click to expand...
Click to collapse
Usually when this corrupted partitions happen you may try the command:
fastboot format userdata
followed by :
adb shell
(to call twrp#)
Then :
twrp wipe data
twrp wipe system
twrp wipe cache
twrp wipe dalvik
Then adb push the rom, gapps/magisk to /sdcard
twrp install nameofyourrom.zip
twrp install gappsxx.zip
Let it boot once and go back and update magisk via recovery.
(adb reboot recovery once permissions set or use powermenu little vic apk for quickness)
Another method I found which works good with fireos is :
When faced with corrupted/encrypted partition issues and/or unable to mount/format data issues
goto advanced wipe
select change file system
change it to EXT2
it will format data and data should appear become mount
hit back and change to EXT4 Filesystem again.
Then push rom and any other zips etc to /sdcard and install in usual way.
Good you got it working
Regards
Thank you for writing this down @Bertonumber1, I am sure it'll be very helpful to people who will encounter such situation in future.
Bertonumber1 said:
select change file system
change it to EXT2
it will format data and data should appear become mount
hit back and change to EXT4 Filesystem again.
Click to expand...
Click to collapse
I sincerely wish I could have done this. But I don't have an OTG with power input and deliveries are closed due to the pandemic. I was issuing TWRP commands through adb. I'll keep this in mind for future!
Thanks!
saurabhshri said:
Thank you for writing this down @Bertonumber1, I am sure it'll be very helpful to people who will encounter such situation in future.
I sincerely wish I could have done this. But I don't have an OTG with power input and deliveries are closed due to the pandemic. I was issuing TWRP commands through adb. I'll keep this in mind for future!
Thanks!
Click to expand...
Click to collapse
Ah I see, I'm sure the twrp can be commanded to repair change file systems. However, you are correct it is much easier via otg mouse or keyboard.
Regards
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…