I'm failed on installing LineageOS again - Google Pixel Questions & Answers

base1:
pixel 32G, factory image version: 9.0.0 (PPR2.181005.003, Oct 2018)
downloaded:
lineageos nightly 15.1-1118 , opengapps arm64 1119 nano/aroma, mindthegapps 0808
commands:
adb reboot fastboot
fastboot boot twrp*****.img
twrp: ***format data -> wipe system -> install lineageos via sideload/adb push -> remember slot a
by this step , I tried lineageos recovery and twrp recovery
***reboot into recovery: opengapps aroma( I chose 4~5 apps, finally error , seems like no enough space), nano(failed without reason)
mindthegapps (twrp : fail to mount system/ lineageos recovery: flash show proceed and back)
by this step, I tried reboot to bootloader and then recovery to install addition-su from lineageos, or not to install.
***-> reboot. -> bootloader lock warn -> google logo -> flash a black screen then self reboot -> bootloader. all failed.
base2:
pixel 32G, factory image version: 8.1.0 (OPM4.171019.021.P1, Jul 2018)
downloaded:
lineageos nightly 15.1-1118 , opengapps arm64 1119 nano/aroma, mindthegapps 0808
commands:
tried as above.
-> reboot. -> bootloader lock warn -> google logo -> loooooong black screen without response
-> long press power button : not work
-> long press vol down + power, I don't remember if bootloader or lineageos recovery. Then I used google factory image script.
I always choose a same slot , a or b, if bootloader show a different, I use fastboot --set-active=a/b ,even flash both all. failed.
I post a earlier steps on reddit. Nobody tell me why.
https://www.reddit.com/r/LineageOS/comments/9mwzut/failed_to_install_lineageos_on_sailfish/

why the forum eaten all the formatting spaces.

Fixed.
Follow this installation guide:
https://forum.xda-developers.com/pi...ageos-15-1-pixel-xl-marlin-t3725985?nocache=1
Anyone if face on media library missing issue, delete /storage/emulated/0/DCIM/.thumbnails and clear 'media storage' app data then reboot.

Related

Update firmware on custom ROM

I am currently on LineageOS 17.1 on both slots, which I flashed over OOS 10.0.4. As I am coming from a OnePlus One, I am still unfamiliar with the A/B slots and I didn't found detailed instructions. Now I want to update the vendor image to 10.0.5 and stay with LineageOS. Is the following procedure correct if I want to keep my data (<- important)?
1. Download 10.0.5 from here: https://forum.xda-developers.com/on...ygen-os-10-0-5-live-oxygen-os-10-0-5-t4080943 (full: https://otafsg1.h2os.com/patch/amaz....25_OTA_025_all_2003270113_4588ebe57af551.zip)
2. Deactivate Magisk modules
3. Open sideload in LineageOS recovery
4. Flash 10.0.5 via adb sideload
5. Flash TWRP via adb sideload (https://sourceforge.net/projects/ma...le-unified-installer-mauronofrio.zip/download)
6. Reboot to TWRP
7. Open sideload in TWRP
8. Flash 10.0.5 via adb sideload
9. Flash TWRP via adb sideload
10. Reboot to TWRP
11. Repeat Steps 3 to 9 , but with newest LineageOS nightly
12. Reboot to LineageOS, reactivate Magisk modules
Is this correct? Am I missing something? I would be happy about improvements.
Bump
I think you will break your data partition if you do this. You can try it, but I think it won't work.
I would backup the phone phone (apps + internal storage) and do the procedure, most likely it will fail.
BTW, its illegal on the internet to pretend to be another (real) person
Just use another username and profile picture (I think you don't have the copyright?)
Thanks for your answer! Hmmm... I don't wanna break my data partition. If I understand you correctly, there's no way to avoid this? Or is there a way and my approach is wrong?
Right about the picture, I'm deleting that.
Edit: New profile picture
my usual update round
- reboot into recovery (assume TWRP already flashed)
- data backup and get current slot
twrp -> settings -> timezone (for nicer local datestamp)
twrp -> backup data (compress) -> /sdcard/TWRP/BACKUPS/
twrp -> enter reboot menu -> show current slot
- upload archives to virtual sdcard
host # adb shell mkdir /sdcard/TWRP/image/
host # adb push oos/OB12-OnePlus7ProOxygen_13.W.31_OTA_031_all_2004111755_397ef15c84.zip /sdcard/TWRP/image/
host # adb push los/lineage-17.1-20200420-nightly-guacamole-signed.zip /sdcard/TWRP/image/
host # adb push twrp/twrp-3.3.1-79-guacamole-unified-installer-mauronofrio.zip /sdcard/TWRP/image/
host # adb push magisk/Magisk-v20.4.zip /sdcard/TWRP/image/
- install/sideload archives via TWRP (every install will usually go into inactive slot)
twrp -> install OOS zip (for vendor/baseband firmware update)
twrp -> install LOS zip (for fun)
twrp -> install TWRP zip (for override LOS recovery) [will patch both slots - against A/B logic]
- switch slot
twrp -> reboot menu -> select other slot
twrp -> reboot into recovery
- rebooted into recovery (verify TWRP version, current slot, correct /data decryption)
twrp -> install Magisk (for LOS17 with SU/root support) [will install into current slot - against A/B logic]
- reboot into new flashed system (verify current slot, LOS version, baseband version)

Install android 11, and Gapps

Hello,
I trying to install (Lineage 18 / Android 11) in my device.
Here is my steps:
1. TWRP-> Wipe -> Swipe to factory reset
2. TWRP -> Install -> find Lineage / system.img
3. wait for the phone to start.
4. reboot into TWRP
5. TWRP -> Install -> find Gapps -> wait for install
6. after done error (mount system structure needs cleaning)
I got this error here:
Code:
mount system structure needs cleaning
What i expected is isntall google apps on Lineage 18
See my photo added
Thanks for your time

How to install LineageOS with MicroG

Hi,
Phone : Realme 5 Pro EU version 4GB/128GB.
As the title says, I am trying to install LineageOS then MicroG on my Realme 5 Pro. So far... I've been at this for a couple of days and I've learned a lot, but that was worth it. Still have to see after a couple of days if this install is stable enough.
Usual disclaimer that this is not because it worked for me that it'd work for you etc...
What files are necessary to follow this post?
-> vbmeta.img & twrp.img here : https://drive.google.com/drive/folders/1MUEJkl25gL7zUPXNKFx_I5HLHyfCAzz7 as posted in this guide : https://forum.xda-developers.com/t/...install-twrp-and-install-custom-roms.4177511/
-> C12 Stock ROM from realme : https://download.c.realme.com/osupdate/RMX1971EX_11_OTA_1120_all_s0mRvUGlCJAI.ozip
-> the Lineage 17.1 ROM provided by @kemo12533 here : https://sourceforge.net/projects/myholly****/files/ROMs/RMX1971/LineageOS/
-> the NikGApps Core for Android 10 ARM64 : https://sourceforge.net/projects/ni...ps-core-arm64-10-20210130-signed.zip/download
-> Magisk : https://github.com/topjohnwu/Magisk/releases/download/v22.1/Magisk-v22.1.apk
-> NanoDroid-patcher : https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-23.1.2.20210117.zip
-> NanoDroid-MicroG : https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-microG-23.1.2.20210117.zip
What I have done so far that works (after tons of FAIL)?
-> Unlocked the device
I managed to unlock the device without too much issue following the guide (link to the guide on this forum is provided above).
-> Installed TWRP
rebooted into bootloader.
"fastboot flash recovery twrp.img"
then proceeded in recovery to TWRP.
Lesson Learned: when "fastboot flash ..." behaves funky (as in not the expected result which is OK), change cable/usb port/computer and don't bother trying to troubleshoot it (I spend a day on this for no result). I have to go on my parents windows computer to fastboot flash but hey it works.
-> Installed latest version of RealmeUI OS (C12 from late march 2021)
TWRP wiped (Dalvik, Cache, System, Vendor, Data)
TWRP format data.
TWRP installed RealmeUI OS C12 without issue
(I did boot it without problem and enabled debugging but I don't think it is required)
-> reinstalled TWRP that had just been overwritten by C12 install.
rebooted in bootloader
"fastboot flash recovery twrp.img"
"fastboot flash vbmeta vbmeta.img"
then booted in recovery to TWRP.
-> Installed LineageOS 17.1 with NikGApps.
TWRP wiped (Dalvik, Cache, System, Vendor, Data) and then formatted data.
TWRP installed LineageOS 17.1
TWRP Install NikGApps.
TWRP installed magisk (which roots the OS).
Rebooted and LineageOS booted without issue.
Note 1 : I tried to install this LineageOS on its own to do a clean MicroG install but on its own it wouldn't boot (same with OpenGApps pico). BitGApps and NikGapps Core both make Lineage Boot, but I settled on NikGApps because it seems automatically 'removed' afterwards when installing MicroG, see later.
Note 2 : The magisk app says that the realme5pro does not have ramdisk. It seems that this is wrong: Magisk does say that phones from 2019 & 2020 are a mess to detect and that the RAMDISK test (Yes or No) is unreliable for those. I followed the manual for No Ramdisk and it corrupted my recovery partition. I followed the manual for yes and it works without issue since.
-> Installing MicroG.
I am now in LineageOS
Magisk Installed Magisk from the same apk and follow instructions to install Magisk properly.
Magisk Installed NanoDroid-patcher & rebooted
Magisk Installed NanoDroid-MicroG & rebooted
at this point the play store icon and app have disappeared (most probably removed by the NanoDroid-MicroG install) and the MicroG Settings app is installed. You still have some permissions to give MicroG and configure it properly, but the following video does a good job of that so I'll leave is at that.
Learned along the way :
It seems to be really hard to brick that phone (good stuff). As long as you can still boot in fastboot you can recover, even if system and recovery don't work.
when "fastboot flash ..." commands don't work when "fastboot devices" lists your device, find another computer, don't waste your time trying to fix this with no result.
write down what works for future reference. I am now documenting every step that works.
Edit 1 : Added Magisk bit. Reorganised post and added details.
Edit 2 : Added MicroG bit. Reorganised post and added details. I guess it's a sort of a guide now...
Hi there!
Does anyone know if it is currently possible to install LineageOS+MicroG on a Samsung Galaxy S20FE Exynos with OneUI 4.1 and Android 12 (SM-G780F/DS)?
Or is there another OS that would allow me to have a degoogled and privacy-friendly smartphone?
Thank you all for your help!
Search for "Lineageos with microg". LineageOS with microgn and f-droid already installed

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

OP7Pro not recognized by Windows in FastBoot mode

Phone OS: OxygenOS 11 EU
PC OS: Windows 11 x64
I'm trying to unlock the bootloader so that I could debloat my phone, install some magisk modules, and GCam.
While ADB normally sees my phone without issues, it's not recognized in Fastboot mode. In the Devices Manager window, the phone is shown as a generic Android device with the yellow warning sign (only during Fastboot, correctly detected as OP7Pro otherwise).
I tried installing ADB from multiple sources, and even used mauronofrio's Tool All In One to no avail. The guides to unlock bootloader don't make any mentions of this issue, and online I've only managed to find very old unsolved threads for other phones.
So, your system doesn't recognize the phone in fastboot mode ?
Did you tried to uninstall the device in the device manager, then plug it back ?
draentor said:
So, your system doesn't recognize the phone in fastboot mode ?
Did you tried to uninstall the device in the device manager, then plug it back ?
Click to expand...
Click to collapse
Good news, not sure why but today it was recognized, and installing TWRP and Magisk seemed to go smoothly.
I now have another question: this post (from 2019) mentions that I should've not installed Magisk the way I did.
I did the following:
1. unlock bootloader via Tool All In One
2. update OxygenOS via the notification I received, then reboot
3. install TWRP via Tool All In One
4. install Magisk via the TWRP menu and app (using the recommended choice)
What instead the guide says is: after TWRP and Magisk installed, update without rebooting, then install TWRP A/B Retention Script, then install Magisk to Inactive Slot and not the recommended Direct Install.
Could I have issues of any kinds, maybe update related, with these premises? If yes, what can I do to fix them?
Nevermind, phone's dead now. I will open another thread about it.
I think this guide is outdated.
That's what worked for me (Read everything before beginning) :
Unlock the bootloader
Update to the last OxygenOS version
Use Oxygen Updater app to be really up-to-date
Install TWRP
To do so, get the latest TWRP .img file here : https://twrp.me/oneplus/oneplus7pro.html
Get the latest twrp-installer.zip file too
It's ready for Android 11, maybe Android 12, I didn't tried
Don't forget to check "Developer options" in system settings
With your phone plugged in your computer, use adb commands and reboot to fastboot with "adb reboot bootloader"
Then, load TWRP with "fastboot boot twrp.img". Of course, you need to put the latest TWRP image file previously downloaded in the same folder and rename it "twrp.img"
In TWRP, go to Advanced then press "Flash Current TWRP"
Done !
Then, follow those instructions :
Wipe -> Factory Reset + : Wipe Data, System, Cache and Dalvik Cache
Install -> Flash ROM : Use the install function and install the ROM
Install -> Flash TWRP Installer : Don't reboot, go back and install as the previous step
Reboot -> Recovery : Reboot TWRP and it automatically load the other slot
Wipe -> Format Data : Click and type yes
Reboot -> System : Just reboot and it should load the installed ROM
Reboot to recovery
Install -> Magisk
Reboot -> System
Install -> Whathever you want
Reboot -> System
draentor said:
I think this guide is outdated.
That's what worked for me (Read everything before beginning) :
Unlock the bootloader
Update to the last OxygenOS version
Use Oxygen Updater app to be really up-to-date
Install TWRP
To do so, get the latest TWRP .img file here : https://twrp.me/oneplus/oneplus7pro.html
Get the latest twrp-installer.zip file too
It's ready for Android 11, maybe Android 12, I didn't tried
Don't forget to check "Developer options" in system settings
With your phone plugged in your computer, use adb commands and reboot to fastboot with "adb reboot bootloader"
Then, load TWRP with "fastboot boot twrp.img". Of course, you need to put the latest TWRP image file previously downloaded in the same folder and rename it "twrp.img"
In TWRP, go to Advanced then press "Flash Current TWRP"
Done !
Then, follow those instructions :
Wipe -> Factory Reset + : Wipe Data, System, Cache and Dalvik Cache
Install -> Flash ROM : Use the install function and install the ROM
Install -> Flash TWRP Installer : Don't reboot, go back and install as the previous step
Reboot -> Recovery : Reboot TWRP and it automatically load the other slot
Wipe -> Format Data : Click and type yes
Reboot -> System : Just reboot and it should load the installed ROM
Reboot to recovery
Install -> Magisk
Reboot -> System
Install -> Whathever you want
Reboot -> System
Click to expand...
Click to collapse
Thanks, I'll save it for next time. Unfortunately the phone's dead and I'm not sure how I got there, nor how or if I can recover it. I made a thread here https://forum.xda-developers.com/t/op7pro-dead-black-screen-wont-turn-on.4387537/

Categories

Resources