TWRP unable to wipe or format `Failed to mount '/system' (Device or resource busy)` - Google Pixel Questions & Answers

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?

Related

Not able to flash Stock image with custom Recovery (TWRP 3.1.1.1.)

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

TWRP ADB Sideload and File Install Problems on Nexus 5

Hello everyone,
I have a LG Nexus 5 and I want to install Lineage OS.
I was successfully (official) TWRP and (official) Lineage OS with GAPPs installed and used and many times OTA updated in past.
Few days ago I want wipe all old datas and fresh install Lineage OS and first download latest versions of (official) TWRP and (official) Lineage OS 14.1.
I downloaded TWRP via https://eu.dl.twrp.me/hammerhead/ and Lineage OS via https://web.archive.org/web/20190223223750/https://download.lineageos.org/hammerhead
I verified hashes before use this files.
Second I pressed "Volume Down + Power" buttons but old (version) TWRP not started. Nexus 5's screen look like factory image. After this "adb reboot bootloader", "fastboot devices", "fastboot flash recovery twrp-3.3.1-0-hammerhead.img".
I powered off Nexus 5 and press "Volume Down + Power" buttons but Nexus 5's screen look like factory image even move down by using Volume Down button and selected "Recovery mode" after press power button latest TWRP started. (I don't know is this normal? Old time I pressed "Volume Down + Power" buttons, directly TWRP started.)
Third I selected "Wipe", "Format Data", "Advanced Wipe", choosed "Cache and System" and they are wiped.
Fourth I backed to main page and selected “Advanced”, “ADB Sideload” and swiped. On my computer "adb sideload lineage-14.1-20190126-nightly-hammerhead-signed.zip". Process succesfully completed. But I navigated to "Install" via main page I didn't see "lineage-14.1-20190126-nightly-hammerhead-signed.zip". My "sdcard" directory look like only within TWRP directory. Even so I turned main page and selected "Reboot", "System" swiped and after reboot Lineage OS 14.1 normally started and I was succesfully set up it.
Fifth I just wondered Lineage OS 16 on Nexus 5 and I downloaded in here (unofficial) LineageOS 16 for Nexus 5.
https://forum.xda-developers.com/google-nexus-5/orig-development/rom-lineageos-16-0-nexus-5-t3921162
And verified hash for 20190719. (It was latest version in time I downloaded.)
Sixth start TWRP and wipe necessary locations. (Format Data, System, Cache)
Go to ADB Sideload and (on computer) "adb sideload lineage-16.0-20190719-UNOFFİCİAL-hammerhead.zip"
Terminal printed (only): "Total xfer: 0.01x"
---------------------------TWRP Screen Start--------------------------
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Formatting Data using make_ext4fs...
You may need to reboot recovery to be able to use /
data again.
Updating partition details...
...done
Formatting System using make_ext4fs...
Formatting Cache using make_ext4fs...
Updating partition details...
...done
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'
Warning: No file_contexts
Target: google/hammerhead/hammerhead:6.0.1/M4B30Z/
3437181:user/release-keys
detected filesystem ext4 for /dev/block/bootdevice/
by-name/system
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
---------------------------TWRP Screen End---------------------------
Seventh I want reflash (official) Lineage OS 14.1 because of Lineage OS 16 flash failed and I wiped old installed Lineage OS 14.1 but ADB Sideload again same error. (This file before successfully transferred and installed.)
Eight I downloaded factory image (6.0.1 (M4B30Z, Dec 2016)) for Nexus 5. in here https://developers.google.com/android/images#hammerhead
It was completely installed without any error and started. I set up it. (I don't lock bootloader.)
I used "flash-all.sh".
Nineth I re-installed TWRP and retry same installation. Again fail with same error.
I tried some solutions for solve this problem but they aren't solve my problem.
1) Install different versions of TWRP. (3.3.1-0, 3.3.0-0, 3.2.1-1)
2) Delete "assert line" in "updater-script" explained this video https://www.youtube.com/watch?v=VCqROwIGLLE
3) Lineage OS file transfere to external USB drive and connect the Nexus 5 via USB OTG cable. (Error or not detect USB drive for different results depend versions of TWRP.)
4) Repair "data" partition. (Ext4 file system.)
How to solve this problem and install Lineage OS?
Note: I am using Manjaro. https://manjaro.org/
I am not a native english speaker. Sorry for my wrongs.
The official Lineage 14.1 with the unofficial Lineage 14.1, 16.0 have differences with their keys, the unofficial is not signed with lineage private key.
You may see the razoloves' post #2994
and cvxda post #2
sant514 said:
The official Lineage 14.1 with the unofficial Lineage 14.1, 16.0 have differences with their keys, the unofficial is not signed with lineage private key.
You may see the razoloves' post #2994
and cvxda post #2
Click to expand...
Click to collapse
Hello,
I know their keys different but I try clean install. I wiped System, Cache, Dalvik / ART Cache and Format Data.
I can't transfer any zip file via ADB Sideload. I always face same problem on TWRP.
"E1001: Failed to update system image.
Updater process ended with ERROR: 7"
I installed succesfully official Lineage OS with same method in past but now I can't transfer/install same old official or different unofficial any zip file.
What I don't understand is Google's factory image transferring and installing without any problem.
I am not a native english speaker. Sorry for my wrongs.
earthling2019 said:
Hello,
I know their keys different but I try clean install. I wiped System, Cache, Dalvik / ART Cache and Format Data.
I can't transfer any zip file via ADB Sideload. I always face same problem on TWRP.
"E1001: Failed to update system image.
Updater process ended with ERROR: 7"
I installed succesfully official Lineage OS with same method in past but now I can't transfer/install same old official or different unofficial any zip file.
What I don't understand is Google's factory image transferring and installing without any problem.
I am not a native english speaker. Sorry for my wrongs.
Click to expand...
Click to collapse
You get this error in TWRP during installation of unofficial LOS16 because from 20190719 build and beyond you have to do repartition procedure in order to increase system partition.
Just look here https://forum.xda-developers.com/showpost.php?p=79928889&postcount=190
If you've never done repartition before you're good to go with post i've provided.
Otherwise you have to return stock partition layout.You have to look at the following post in order to do this procedure https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
Actually i don't know your current O.S. Manjaro,but if you follow carefully these posts you'll be able to flash and enjoy LOS16 perfectly.
srepole said:
You get this error in TWRP during installation of unofficial LOS16 because from 20190719 build and beyond you have to do repartition procedure in order to increase system partition.
Just look here https://forum.xda-developers.com/showpost.php?p=79928889&postcount=190
If you've never done repartition before you're good to go with post i've provided.
Otherwise you have to return stock partition layout.You have to look at the following post in order to do this procedure https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
Actually i don't know your current O.S. Manjaro,but if you follow carefully these posts you'll be able to flash and enjoy LOS16 perfectly.
Click to expand...
Click to collapse
Hello,
When I started this topic, can't transfer any official or unofficial Lineage OS zip file. (Include official/unofficial 14.1)
I found a solution for this problem few days ago and succesfully installed unofficial Lineage OS 16 and then 14.1. (I used before July 19 Lineage OS 16 build for not to require repartitioning.)
DISCLAIMER:
I am NOT responsible for any damage. This solution at your own risk.
I found this solution:
DISCLAIMER:
I am NOT responsible for any damage. This solution at your own risk.
You make sure battery charged.
1st start TWRP and go to "Wipe", "Format Data", "yes"
2nd go to "Advanced Wipe", select "Dalvik /ART Cache, System, Data, Internal Storage, Cache" and "Swipe to Wipe"
3rd go to TWRP home screen "Reboot", "Power Off"
Wait for 10 minutes.
4th start TWRP and go to "Advanced", "ADB Sideload", "Swipe to Start Sideload", transfer Lineage OS zip to smart phone from computer.
DISCLAIMER:
I am NOT responsible for any damage. This solution at your own risk.
I am not a native english speaker. Sorry for my wrongs.

Gapps installation problem - LineageOS 16 + Oneplus 7 Pro

I'm trying to install the OpenGapps package for LineageOS 16 on my new Oneplus 7 Pro, but have a problem installing it.
First I tried the "open_gapps-arm64-9.0-micro-20190827.zip" package, but it told me its the wrong platform. Is it not arm64?
Second I tried to install the "open_gapps-arm-9.0-micro-20190827.zip", but gives me an error 70, saying I do not have enough space.
Maybe someone have a solution for this?
Thanks
Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
oryanh said:
Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Click to expand...
Click to collapse
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...
cbadk said:
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...
Click to expand...
Click to collapse
Format data in twrp then try boot again should work
liam_davenport said:
Format data in twrp then try boot again should work
Click to expand...
Click to collapse
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....
cbadk said:
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....
Click to expand...
Click to collapse
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.
liam_davenport said:
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.
Click to expand...
Click to collapse
Have not wiped the System and Vendor partition after I installed Lineage... It boots just fine... just not if I install Open GApps....
Tried MindTheGapps latest version, but still no luck.
Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.
cbadk said:
Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.
Click to expand...
Click to collapse
I am facing the same A/B slot problem with my Moto Z2.
After setp 5), did you let the lineage OS fist then reboot into recovery, or did you go straight to the lineage recovery?
Thank you so much for this. I finally fot it sorted. I did find that sometimes you have to ubplug the USB cable and plug it in again to be recognised, but I got it going. Goodby Google!!!!
I am using Gentoo Linux with adb to do this.

Question LineageOS: "Can't load Android System" on first boot.

My new Xiaomi Poco X3 Pro is showing an error screen after some time, like in this post:
https://forum.xda-developers.com/t/cant-load-android-system-lineageos.4314035/
It reads "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device"
This happened so far:
I just unlocked the boot loader of my new phone after week of waiting.
I followed the official lineage instructions to install the OS: https://wiki.lineageos.org/devices/vayu/install
Everything worked including the sideloading via db.
I downloaded those two files for the LineageOS-Site:
- Recovery via fastboot: lineage-18.1-20211203-recovery-vayu.img (recovery works, I can still boot into recovery)
- System via adb: lineage-18.1-20211203-nightly-vayu-signed.zip
I also added Gapps via adb: "open_gapps-arm64-11.0-nano-20211204.zip"
Both adb transfers exited successfully.
After the first error screen
- I tapped Try again,
- When the error occurred again, I tapped "Factory data reset," but the error still occurred. The phone is new, no user data is on the phone.
- I booted into recovery and reset all the data I could. When I tap "Format system partition" it throws an error "E: Failed to open /dev/block/dm-0: No such file or directory. System wipe failed."
- Then I repeated the adb sideload. The error occurs again.
- I removed the SIM card, as someone in the forum suggested this could be a problem source. The error still occurs.
What can I do now?
----
Update [2021-12-05 Sun 20:09]
It seems to be a Problem with the GApps Version.
What I did Try so far is:
- Install 03-12-LOS and latest GApps via LOS recovery (didn't work)
- Install 03-12-LOS and latest GApps via TWRP recovery (didn't work)
- install LOS Build from 26-11-2021 without GApps (works)
- Install LOS Build from 26-11-2021 with latest GApps (didn't work)
- Install LOS Build form 26-11-2021 with GApps from 25-11-2021 (works)
Just use TWRP, flash ROM and AFTER flashing ROM Format Data where you have to type "yes". (Format, not Wipe)
Xiaomi Poco X3 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Thanks for the Idea. At the moment it has not solved the problem.
This is what I did:
- Flash TWRP
Code:
fastboot flash recovery TWRP-3.5.2-vayu-Nebrassy-2.img
- copy lineage-18.1-20211203-nightly-vayu-signed.zip and "open_gapps-arm64-11.0-nano-20211204.zip" to the Poco device
- install via "install" option, wipe cache at the end of installation
- Format files (via "Wipe" -> "Format Data" -> type "yes")
- Reboot
After some time of the animated Lineage OS logo, the phone reboots into TWRP.
To me this seems very similar to the Lineage recovery before.
Any ideas what could be wrong?
You probably wiped System or Vendor partition or something, you are not supposed to do that.
Most likely you have to reflash MIUI now first. Make sure it's atleast version 12.5.X.X.
Flashing instructions are really simple, this apply to all ROM's.
FIRST INSTALL?:
Remove any fingerprint, PIN, or password in MIUI
Unlock the bootloader
Transfer ROM to internal storage
Install any suitable recovery
Flash ROM zip file
Do a data wipe in recovery (format data)
Reboot to the system, wait and enjoy
FLASHING UPDATES?:
Download via OTA Updater and let it automatically install; OR
Download an update, transfer to internal/external storage (always check file sha256)
Flash ROM zip and reboot.
Do not wipe anything else or add any additional steps. (maybe except Gapps if ROM doesn't have them included)
ps.
In first post there is no mention if you did Format Data or not and when you did it. Like i said before - you have to Formata DATA AFTER flashing ROM . Not before.
This happened so far:
I just unlocked the boot loader of my new phone after week of waiting.
I followed the official lineage instructions to install the OS: https://wiki.lineageos.org/devices/vayu/install
Everything worked including the sideloading via db.
I downloaded those two files for the LineageOS-Site:
- Recovery via fastboot: lineage-18.1-20211203-recovery-vayu.img (recovery works, I can still boot into recovery)
- System via adb: lineage-18.1-20211203-nightly-vayu-signed.zip
I also added Gapps via adb: "open_gapps-arm64-11.0-nano-20211204.zip"
Both adb transfers exited successfully.
Click to expand...
Click to collapse
k3lcior said:
In first post there is no mention if you did Format Data or not and when you did it. Like i said before - you have to Formata DATA AFTER flashing ROM . Not before.
Click to expand...
Click to collapse
I followed the LOS Install Guide: https://wiki.lineageos.org/devices/vayu/install But this procedure does not seem to bee the cause (see below).
Download the LineageOS installation package that you would like to install or build the package yourself.
Optionally, download an application package add-on such as Google Apps (use the arm64 architecture).
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. When Xiaomi/POCO/Redmi splash appears, release Power and keep pressed Volume Up until recovery appears.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Click to expand...
Click to collapse
Okay so this is what I did (the part that works):
- I downloaded the latest possible stock ROM from https://www.xda-developers.com/down...ut-several-xiaomi-redmi-mi-poco-devices/#vayu The fastboot ROM is more than 5GB.
- Extract the file "vayu_eea_global_images_V12.5.3.0.RJUEUXM_20211015.0000.00_11.0_eea_05cc38de43.tgz"
- then connect the phone via USB cable in fastboot mode and:
Bash:
cd ~/Downloads/vayu_eea_global_images_V12.5.3.0.RJUEUXM_20211015.0000.00_11.0_eea
/bin/bash ./flash_all.sh
- The default MIUI starts flawless, as it dit the first time I turned on the phone. So far so good.
What didn't work:
1. I installed the LOS Recovery again and flashed the OS and Gapps. Only after that I did step 3 - formating. The result ist the same bootloop as in the beginning.
2. I flashed the stock MIUI ROM again (which woks fine). Then I flashed TWRP, transfered the OS and GApps file and installed. I did not wipe anything, just used "format data" like above.
In both cases the OS does not start. After a while displaying the LOS-logo the phone reboots to recovery.
What did work:
I downloaded lineage-18.1-20211126-nightly-vayu-signed.zip, one version before the latest verion and the corresponding recovery lineage-18.1-20211126-recovery-vayu.img
I flashed only the OS, and no GApps -- and it launched successfully. Installing with the latest GApps failed again.
Install older gapp, not all gapp is compatible

Cannot install GAPPS

Hello all - hope everyone's doing OK? I have a OnePlus One lying in the drawer for years and decided to flash it to the latest Lineage OS18.1 so I can take it as a backup phone abroad. I was able to successfully install the OS but when I attempted to install GAPPS (the smallest pico version) I got an error 70 saying there was insufficient space to install it. Doing some Googling a workaround seems to be to re-size the partition using TWRP. However when I tried that (Wipe-Advance Wipe-Check System-Repair or Change File System-Resize File System) I get another error message:
/sbin/e2fsck -fp /dev/block/platform/msm_sdcc.1/by-name/system process ended with ERROR: 1
Unable to repair System
Anyone have any idea how I can fix this? For completeness in my system_root file system it is showing as Size: 1303Mb Used: 1063MB Free: 239Mb
Thanks!
Use a lower size gapps or aroma gapps so that you can choose required apps to install. Also, flash the rom+gapps together because of changes from some custom android versions you can't reboot to system and then flash gapps, that will give you force closes error.
Or maybe try to do full reset with original operating system and start all over again.
If the problem still persist, change the recovery to another available versions.
LineageOS only recommends MindTheGapps for 18.1

Categories

Resources