I recently been trying to Install the latest version of MIUI for Nexus 5 being MRA58K onto my device but i have been running into alot of problems
Previous i was running KTU84P stock as a base. Prior to attempting to flash the latest version of MIUI i updated the base partitions to MRA58K using the Nexus Factory Image Packages
When trying to install the zip file under any custom recovery, it gives me
mount: no partition named "/dev/block/platform/msm_sdcc.1/by-name/userdata"
Target: Android/aosp_hammerhead_fp/hammerhead:6.0/MRA58K/6.5.26:user/release_keys
and then after while it gives me Error 7. Within mounted Partitions i have /data ticked
Try to mount system after factory reset in TWRP.Factory reset then go to Mount and check system and swap to mount.Hope it will work.It's been discussed in another MIUI 7 forum here about installation error.Please try to search it.
Related
Facing error"error executing updater binary in zip" ( 12.1.1 YOG7DAS2K1) Oneplus one
I tried wiping Data, Cache, System and then after flashing above update it says flashing failed.
Following are the details of my Oneplus one
TWRP : 2.8.7.0
CyanogenMod Version: 12.1-YOG4PAS3JL
Build Number: LMY48B
Device model- A0001
need a solution.
yeah same with me. Weird thing is it just says Error! nothing else is printed on the screen
I have found a solution for this problem.
You can follow this step:
1) Instead of downloading 65.8 MB incremental file go to cyanogen -support website( Sorry couldn't paste the link as i am new user) search for your device and you will find a link which will download the latest complete rom. This rom is of around 700mb.
2) Copy this downloaded rom mentioned above to ur device.
3) Take a Backup
4) Wipe Data, Cache,System or Simply just do factory reset with the help of TWRP
5) Install the Rom using TWRP
6) Reboot and finally your device will be updated and there will be no error.
it worked for me.
Hello guys,
Today I wanted to update my Honor 8 (FDR-L09) because it was showing me, that there is a new update ready to install (FRD-L09C432B405) and I was on a very old firmware (something from mid 2017). So it was time for me to update.
I downloaded the latest update (FRD-L09C432B405) and tried to wipe the cache, dalvik, and Data, but for some reason it "couldn't mount /data" and the wipe failed.
After an advanced wipe it worked and I tried to flash the stock image (the update which was shown to me (FRD-L09C432B405) with TWRP (3.1.1.1.)).
Now my hassle starts:
1. The Rom couldn't get flashed because of "Error: 7" --> I fixed it with the common "Error 7 fix --> editing the update-script and removing the assert line. (And yes, I'm 100% sure that it was the right ROM.
2. Now TWRP seemingly starts to flash the rom but inbetween the lines there is "mountencrypt: failed to mount /data: no such file or directory and it ends with "unknown command [[]" and it takes just two seconds, so the flash obviously isn't succsessfull.
I tried the "failed to mount /data" fix, where I change the data system to ext3 and then back to f2fs and change it back, but it won't work.
In my frustration I did another pretty bad thing and made another advanced wipe and wiped the system too, so now I don't have an OS on my system.
Maybe it's also important to note that there was a window showing up for a very short amount of time, with something like "encryption/encrypted" showed up.
What should I do now? Is there a way to fix the "/data couldn't be mounted" problem? Or am I missing a vital step in flashing the stock rom?
Thanks for your kind help!
You can not flash an update with twrp unless you use hurupdater. You essentially bricked your phone. Look for hurupdater here on xda and follow the instructions and you'll be fine
I'm trying to install LineageOS and then GAPPS on my Pixel XL from TWRP recovery. I'll try to `Advance Wipe` the `/systems` directory and `Format Data`, but I continue to get multiple errors:
Code:
Failed to mount '/system' (Device or resource busy)
Code:
Failed to mount '/vendor' (Device or resource busy)
And
Code:
Unable to wipe 'System'
Code:
Unable to wipe '/system'
If I just continue with `adb sideload lineageos.zip` most of the time it stops about halfway (PowerShell shows `47%`) through and then TWRP shell shows:
Code:
Installing zip file '/sideload/package.zip'
Step 1/2
Step 2/2
I then try to `sideload` the `gapps.zip` file and get another error saying `/system` doesn't have enough space. I've tried sideloading several different gapps versions including their smallest `pico` zip fie of `91.39 MiB`.
I am able to then boot into LineageOS, but no GAPPS show and I'm not able to run any new apps installed via APK without them crashing.
My assumption is that I need to fully wipe `system` and format it, but I've been trying for two days now and still get the above `(Device or resource busy)` errors. Any help would be much appreciated!
Make sure you have the latest tools.
Latest TWRP for marlin is 3.3.0-0
Latest platform-tools is 29.0.1
Not sure what's the cause of this, but if you want to wipe and start fresh I think the best option is reflash the stock factory image that completely wipes everything and restores everything stock.
Then, you can retry wiping the device using the latest TWRP (currently, marlin is 3.3.1-0, the zip is 3.3.0-0, try just boot it and don't flash the zip), flash LOS and then gapps.
Also, as pointed by @post-mortem, make sure you are using the latest adb version when flashing the factory image, just to avoid any potential issue.
Don't use 3.3.1-0. Try 3.3.0-0. I had the same issue.
Why doesn't TWRP Team provide an answer as to why this happens? It appears to affect everyone with the latest official Pixel ROM.
Twrp is for Android pie and has trouble mounting stock Android 10. They have announced this on their website. This shouldn't matter since you're installing lineage. You don't need to wipe system before installing lineage because it installs into the inactive slot. You need to sideload lineage then reboot into recovery to switch slot's. The instructions are on the lineage website.
Did OP manage to solve this issue?
Hi,
I have updated TWRP to 3.3.0-2 using Odin3 v3.13.1 before proceeding to the installation of the rom version lineage-13.0_espressowifi-6.0.1-20190729-1933 but I am unable to install a gapps package. I have made an attempt using an old version (gapps-base-arm-6.0.1-20170902-1-signed) which failed. So I went to Open GApps project to obtain a newer version (open_gapps-arm-6.0-nano-20191116) but it failed again with an error code of 40.
This code tells me that I must wipe the system partition if I want to install their new version of GApps. I went to recovery mode and searched for such an option but it does not exist. The only option available is wiping the cache partition. In fact this new version of TWRP does not look the same as my previous version (3.2.0) in terms of options and features.
I have made an attempt at going back to my previous version of TWRP using Odin3 but it did work; no failure, the version was not changed.
If I can't go back to a previous version of TWRP and the current version does not provide an option for wiping the system partition, what can I do to install GApps?
Regards
did you wipe it under advanced wipe? and I recommend open gapps 6 arm pico.
as stated before, I can wipe cache only under the Advanced option of this version of TWRP.
Now regarding your suggestion of using the pico version of gapps, it doesn't matter. Whatever version I use, it triggers an error code of 40, which translates into something like: the Open Gapps package can only be installed on top of an existing installation of Open Gapps or a clean AOSP.... You must wipe your system partition and flash your rom before installing Open Gapps. Again, the problem is that the actual version of TWRP does not provide the option of wiping the system partition.
I have replaced an old 2018 version of LineageOS 13 with version lineage-13.0_espressowifi-6.0.1-20190729-1933 and as I was trying to install a Gapps package, it failed with an error code of 40.
yaudette said:
as stated before, I can wipe cache only under the Advanced option of this version of TWRP.
Now regarding your suggestion of using the pico version of gapps, it doesn't matter. Whatever version I use, it triggers an error code of 40, which translates into something like: the Open Gapps package can only be installed on top of an existing installation of Open Gapps or a clean AOSP.... You must wipe your system partition and flash your rom before installing Open Gapps. Again, the problem is that the actual version of TWRP does not provide the option of wiping the system partition.
I have replaced an old 2018 version of LineageOS 13 with version lineage-13.0_espressowifi-6.0.1-20190729-1933 and as I was trying to install a Gapps package, it failed with an error code of 40.
Click to expand...
Click to collapse
Try a different version of TWRP.
as I was looking for a solution to my problems, I have discovered there are various "flavors" of Odin3 matching with hardware and software. Unlike what I have read on different sites, it is not always a good idea to use the most recent version of a piece of software. So, I have replaced my version of Odin3 by an older version more in line with my hardware and my operating system and I have managed to install successfully a very old version of TWRP (3.0.0). Then I have upgraded to version 3.3.0-2 and all options that I was used to became available. From this point, I will be able to clean flash my tablet.
Thanks secretwolf98 for your attempts to help me solve my problem.
Case closed.
HI,
I have 2 Samsung devices with TWRP installed, and I can access the TWRP recovery menu. When I install the flash ROM and try to boot, devices are stuck in system boot forever.
Device 1: SM-T800, with LineageOS 14.1 previously. I opened an email and the device got hacked, so I did a factory reset (which failed), then re-flashed the latest TWRP and recovered rescue mode. Now when I flash the Lineage ROM (from TWRP) the device does not boot to system but keeps showing the splash screen. I think the hack might have placed immutable files under system. could I format this partition to zero it out via ADB? What other choices are there?
<EDITED>
Device 2: Galaxy S3 GT-I9300 - I solved this so i removed this section.
Thank you for any help.
Beeblebrox-BSD said:
HI,
I have 2 Samsung devices with TWRP installed, and I can access the TWRP recovery menu. When I install the flash ROM and try to boot, devices are stuck in system boot forever.
Device 1: SM-T800, with LineageOS 14.1 previously. I opened an email and the device got hacked, so I did a factory reset (which failed), then re-flashed the latest TWRP and recovered rescue mode. Now when I flash the Lineage ROM (from TWRP) the device does not boot to system but keeps showing the splash screen. I think the hack might have placed immutable files under system. could I format this partition to zero it out via ADB? What other choices are there?
Device 2: Galaxy S3 GT-I9300, with working TWRP. This device is giving a "Failed to mount /efs (Invalid argument)" error. The previous setup was shared storage with sdcard and encryption on both internal and sdcard. The sdcard got corrupted, hence the error. This post suggests running
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
but the device does not have identifiable boot device under /dev/block. I think this might work if I can identify the boot partition name?
Thank you for any help.
Click to expand...
Click to collapse
Flash a custom ROM for i9300 via TWRP. Download a custom ROM for i9300 and the appropriate Gapps to go with the ROM, store them on external sdcard. When you are in TWRP, before you flash your ROM, select the "Wipe" option, then select "advanced wipes", on the next menu, choose the system partition, data partition, cache partition and dalvik cache partition then swipe the slider to wipe. Then go back to home screen in TWRP and choose the "Install" option, then choose your ROM file and your Gapps file then swipe to flash. When the flash is finished, select the "Reboot system" option and see if it boots into system.
If that doesn't work, we will take some steps further back and try starting from the beginning.
Keep in mind that some of the custom ROMs for i9300 may have a different partition structure and partition sizes than the stock firmware for i9300 has and may require resizing certain partitions such as the system partition by flashing a custom PIT file like the Galaxy S2 had to do before it flashed certain custom ROMs.
Hi, thanks for the input.
* I had already solved the GT-I9300 issue before your post (I should have added to thread rather than edit the original post). I solved issue with that device by including system partition in the wipe.
* For the SM-T800, I used a LineageOS-14.1 that I had stored somewhere. That also did not work, until I only flashed Lineage and did not include any GApps. If I really need it, I can always flash later. I assume the latest GApps 7.1 build conflicts with older ROMs.
An unexpected problem was the lack of current ROMs for the 2 devices. SM-T800 has nothing other than last build Lineage-14-1-20190205. The I9300 has several unofficial ROMs floating around for newer Android versions, but they are all debug/dev builds with enabled options that drain the battery very quickly.
If anyone comes across a decent ROM for either of these devices please LMK. Thanks.