Step by Step Installation of/Upgrade to Android Pie Custom Roms
Following this guide, you will lose all your data if haven't backed it up yet!!
Also NO USING GSI PIE!!!
Requirements:
- Twrp is already installed.
What you need:
- LineageosTWRP (Attached to thread)
- Custom Rom (can be found here)
- Open Gapps (Pico or Nano)
Only if Root is wanted: Chose either of them
Magisk(Recommended) or SuperSU
- A brain and a body
- The Knowledge that you will wipe your phone by doing this. Be Warned.
Installation:
1. Backup all the files that you have either by copying them to a usb drive ,a micro SD or your computer.
2. Check that all files are copied successfully and can be opened or viewed.
( Some apps have a cloud synchonisation feature, use it if you have it as an option since it is really helpful!)
3. Now, get your preferred rom, gapps and if wanted, your root method ready, also unzip the twrp file aswell.
Copy them to your micro SD.
4. Boot into twrp via adb or by using some app(root needed).
In Twrp, go into wipe option, then select change file system. Change file System to ext4.
4.1 Now use Twrp Reboot-Menu Option to reboot into recovery(twrp) again.
4.2 Wipe system, data, cache and dalvik-cache partitions using the Wipe option
5. Go into Install Option and Press on "Install IMG" , select pietwrp image and flash it. (The name should be lineagerecovery.img or something if downloaded via telegram)
(If you don't have it yet and are in the Lenovo P2 Telegram group, type #pietwrp in chat and make sure to safe it to your download folder. Otherwise it's also attached to this thread.)
6. Reboot back to recovery like you did in step 4.1.
7. Now install your rom and gapps.
8. Wipe cache and then reboot .
9. Setup your phone and Enjoy.
( For Root, reboot to recovery. Flash your Root Method, wipe cache and reboot)
Enjoy and thank your Devs
FAQ
Q: Instructions unclear, phone stuck in bootloop
A: Either do this:
Download this folder and use one of the two ".bat" files. Boot into Bootloader via Volume Down and Power Button. --
It will flash S048 Firmware of our Lenovo P2, after the flash-process is finished it will boot up on its own. Recommended: Do all the ota updates via ota app.
Or: Boot into bootloader, via adb cmd prompt use: fastboot boot lineagerecovery.img , then use reboot menu to reboot into twrp. Clean Wipe phone(Wipe system,data, cache and dalvik-cache Partitions) and try flashing your Rom etc. again.
Q: Instructions unclear, hardbricked my phone!!
A: Thaat shouldn't have happened. Did you screw up somewhere?...
Luckily you backed up your most important files!
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Introduction
This thread is dedicated to newbies and rooting, so if you're familiar with the whole procedure, you're done
Just ask questions about every step and you'll receive help!
Downloads
TWRP Installer ZIP and TWRP IMG for Android 9/10: https://forum.xda-developers.com/oneplus-7/development/recovery-unofficial-twrp-recovery-t3932943
TWRP for Android 11(including instructions, thank's to @Nebrassy ): https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
TWRP Installer ZIP = For example twrp-3.4.0-10-guacamole-unified-installer-mauronofrio.zip
TWRP IMG = For example twrp-3.4.0-10--guacamole-unified-Q-mauronofrio.img
Check for Pie or Q TWRP IMG! If you have Android Pie, choose Pie TWRP IMG, if you have Android Q, choose Q TWRP IMG.
The TWRP Installer ZIP works on Android Pie(9)/Q(10)
Magisk ZIP: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hints
If you need to update TWRP or Magisk, always keep older versions of both in hand(Magisk canary or beta may have issues)
Remove your lockscreen protection which also removes encryption to prebvent mounting issues within TWRP
Before proceeding
Your Windows PC should already recognized your device with the USB cable
Use an USB cable provided with the phone
Make sure your Windows Explorer is set up to have file extensions enabled to avoid file name issues
This process will FORMAT/WIPE/DELETE your internal storage and every file of your phone, so please back it off your device at first!
Also keep a boot.img from your current system in place if anything went wrong so you can flash it via fastboot, see "Rooting without TWRP" for how to get it.
Rooting with TWRP (Android 9/10)
Steps for unlocked bootloader with TWRP AND Root(Magisk)
1. Follow this guide to unlock your Oneplus 7 bootloader(wipes everything on your device, works for OP7 pro and OP7): https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2.
2. Your phones bootloader is now unlocked, leave the phone plugged to your PC
3. Make sure you have enabled USB-Debugging and Advanced Reboot under developer options(see step 1 how to enable it all) again after the first boot of the wiped device, since this gets reset
4. Copy the latest "TWRP installer ZIP" and "Magisk ZIP" to the phones internal storage.
5. Copy the "TWRP IMG" to the "platform-tools" folder from step 1.
6. Open command window or PowerShell window again if you did not closed it before within the "platform-tools" folder from step 1
7. Type
Code:
adb devices
to see if your device is connected and recognized sucessfully by your PC.
8. Type
Code:
adb reboot bootloader
to reboot to fastboot mode.
9. Type
Code:
fastboot boot recoveryimgfilename.img
to temporary boot TWRP, where recoveryimgfilename.img is the name of your downloaded TWRP *.img file, so watch your file name!.
10. Enter your screen lock PIN within TWRP if you have set it up before.
11. Allow modifications.
12. Now you have temporary booted twrp recovery. To make it stick permanently you need to flash the "TWRP installer ZIP" from your phones storage from step 4.
13. Hit "install" and navigate to the "TWRP installer ZIP" file and select it for installation(dont boot the system now!).
14. Go back and flash "Magisk ZIP" the same way as for TWRP Zip otherwise your device will not boot!
15. Thats all, you can unplug the USB cable and boot the device to your system. Your device is now bootloader unlocked with TWRP and Magisk:highfive:
Steps for unlocked bootloader with TWRP WITHOUT Root(Magisk)
1. Follow this guide to unlock your Oneplus 7 bootloader(wipes everything on your device, works for OP7 pro and OP7): https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2.
2. Your phones bootloader is now unlocked, leave the phone plugged to your PC
3. Make sure you have enabled USB-Debugging and Advanced Reboot under developer options(see step 1 how to enable it all) again after the first boot of the wiped device, since this gets reset
4. Copy the latest "TWRP IMG" to the phones internal storage.
5. Copy the latest "TWRP IMG" to the "platform-tools" folder from step 1.
6. Open command window or PowerShell window again if you did not closed it before within the "platform-tools" folder from step 1
7. Type
Code:
adb devices
to see if your device is connected and recognized sucessfully by your PC.
8. Type
Code:
adb reboot bootloader
to reboot to fastboot mode.
9. Type
Code:
fastboot boot recoveryimgfilename.img
to temporary boot TWRP, where recoveryimgfilename.img is the name of your downloaded TWRP *.img file, so watch your file name!.
10. Enter your screen lock PIN within TWRP if you have set it up before.
11. Allow modifications.
12. Now you have temporary booted twrp recovery. To make it stick permanently you need to flash the "TWRP IMG" from your phones storage from step 4
13. Navigate to advanced menu within TWRP, click on "Install Recovery Ramdisk" and select the "TWRP IMG". This will patch the boot image which does Magisk otherwise.
14. Thats all, you can unplug the USB cable and boot the device to your system. Your device is now bootloader unlocked with TWRP:highfive:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting without TWRP (Android 9/10/11)
Also useful to get stock recovery and kernel --> Recovery is within boot.img on A/B devices like OP7
Refer here for unlocking the bootloader.
1. Download the payload dumper tool to your PC from here and extract it
2. Download the FULL OxygenOS Rom zip(The version your phone is running) and extract the payload.bin
3. Put payload.bin to "payload_input" folder o the extracted tool
4. Run payload_dumper.exe from the tool's folder
5. Extracted img files are in "payload_output" folder
6. Now you have your own boot.img for your Rom
7. Copy it to your phone
8. Patch the boot.img with Magisk directly on your device: Magisk Manager App -> hit install after your Magisk version -> hit "Select and Patch a file"
9. Copy the patched boot.img (it should be in the Download folder of your device named something like "magisk_patched-22100_bjjRn.img") back to your PC
10. Reboot your device to fastboot
11. Flash the patched magisk_patched-22100_bjjRn.img
Code:
fastboot flash boot_a magisk_patched-22100_bjjRn.img
fastboot flash boot_b magisk_patched-22100_bjjRn.img
12. Reboot your device. Now you have your phone rooted without the need of TWRP (Check with Magisk Manager App)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update your rooted OxygenOS (Android 9/10)Steps for UPDATE OxygenOS via OTA and keep unlocked bootloader, TWRP, Root(Magisk)
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Go to Magisk Manager App and uninstall all modules
2.1 [Optional]: For some modules(read those instructions) you should do an reboot now, then proceed
3. Go to Android settings -> system -> system update and hit "Download & Install Now", don't reboot yet!
4. (not for Android 11)Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
5. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit "install to inactive slot"
6. Reboot your device
7. Reinstall your Magisk Modules(maybe a reboot is necessary)
Your device is now updated via OTA and you keep TWRP and Root:highfive:
Steps for UPDATE OxygenOS via local upgrade and keep unlocked bootloader, TWRP, Root(Magisk)
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Download the full rom zip file and place it into the root folder of your storage(/storage/emulated/0)
3. Go to Magisk Manager App and uninstall all modules
2.1 [Optional]: For some modules(read those instructions) you should do an reboot now, then proceed
4. Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, don't reboot yet!
5. (not for Android 11)Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
6. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version ->hit "install to inactive slot"
7. Reboot your device
8. Reinstall your Magisk Modules(maybe a reboot is necessary)
Your device is now updated via local upgrade and you keep TWRP and Root:highfive:
If you have any issues, just feel free to ask!
@strongst you should maybe write in your guide that magisk flash is a must! Without phone won't boot if it's stock.
There are a lot of people who wanna flash TWRP without magisk. I don't know why they do that it makes no sense for me.
Kollachi said:
@strongst you should maybe write in your guide that magisk flash is a must! Without phone won't boot if it's stock.
There are a lot of people who wanna flash TWRP without magisk. I don't know why they do that it makes no sense for me.
Click to expand...
Click to collapse
I made it a little bit more clear, thanks, that's an common issue across several devices and requested often enough
Thank you for the quick tutorial. For me it looks very similar to the procedure with the OnePlus 5, am I right?
Does this indicate, that an EFS Backup is also to create the same way? https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
BR
Axel
AxelM said:
Thank you for the quick tutorial. For me it looks very similar to the procedure with the OnePlus 5, am I right?
Does this indicate, that an EFS Backup is also to create the same way? https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
BR
Axel
Click to expand...
Click to collapse
There's something different after unlocking the bootloader(which is the same). Twrp and magisk installation is different due to treble.
For EFS you can backup with twrp or local terminal
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=512
Thanks for the guide, my OnePlus 7 came with 9.5.5 and I want to clean flash to the latest 9.5.8. I have already unlocked the bootloader, boot into TWRP and installed TWRP, are these the correct steps to flash 9.5.8 as I'm confused with the A/B partition?
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip
3. Flash kernel and Magisk or the other way round?
Camack said:
Thanks for the guide, my OnePlus 7 came with 9.5.5 and I want to clean flash to the latest 9.5.8. I have already unlocked the bootloader, boot into TWRP and installed TWRP, are these the correct steps to flash 9.5.8 as I'm confused with the A/B partition?
1. Wipe data, cache, system
2. Flash 9.5.8 signed flashable zip
3. Flash kernel and Magisk or the other way round?
Click to expand...
Click to collapse
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip with current twrp
3. Flash twrp installer zip with current twrp
4. Flash magisk zip with current twrp
5. Reboot
Make sure not to FORMAT internal data, otherwise you wipe the files you want to flash as it formats sdcard
strongst said:
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip with current twrp
3. Flash twrp installer zip with current twrp
4. Flash magisk zip with current twrp
5. Reboot
Make sure not to FORMAT internal data, otherwise you wipe the files you want to flash as it formats sdcard
Click to expand...
Click to collapse
Thanks, so I boot into TWRP first and then do step 1 and 2? Also, which step should I flash custom kernel?
Camack said:
Thanks, so I boot into TWRP first and then do step 1 and 2? Also, which step should I flash custom kernel?
Click to expand...
Click to collapse
You need to do all steps. I recommend to flash the custom kernel when you've sucessfully booted the device at first.
Hi, a new OP7 User here. I wanted to know how can i keep my data decrypted? i have installed TWRP but i want to decrypt my data and also keep it the same after updated newer updates. Is it possible? I was able to do it on my OP3T, so wanted to know if its possible on OP7 as well
murti52 said:
Hi, a new OP7 User here. I wanted to know how can i keep my data decrypted? i have installed TWRP but i want to decrypt my data and also keep it the same after updated newer updates. Is it possible? I was able to do it on my OP3T, so wanted to know if its possible on OP7 as well
Click to expand...
Click to collapse
This should work https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
strongst said:
This should work https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
I think i messed up real bad, now when iam booting the phone, a message comes, your device is corrupt. It can't be trusted and will not boot.
murti52 said:
I think i messed up real bad, now when iam booting the phone, a message comes, your device is corrupt. It can't be trusted and will not boot.
Click to expand...
Click to collapse
That message is the bootloader unlocked warning and comes every time as soon as you unlocked the bootloader.
Flashing DM verity patch can only be done when you format internal storage which wipes everything of your internal storage. You can't "decrypt" your existing data permanently with this.
strongst said:
That message is the bootloader unlocked warning and comes every time as soon as you unlocked the bootloader.
Flashing DM verity patch can only be done when you format internal storage which wipes everything of your internal storage. You can't "decrypt" your existing data permanently with this.
Click to expand...
Click to collapse
No, this is not the same, i can't even go to fastboot or anything, it's hardbricked.
murti52 said:
No, this is not the same, i can't even go to fastboot or anything, it's hardbricked.
Click to expand...
Click to collapse
If you have really bricked it: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
strongst said:
If you have really bricked it: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
Click to expand...
Click to collapse
Sadly it didn't worked, as phone doesn't gets detected on pc, keeps on rebooting. Gave it to service center and they are also not able to solve it ??. So a replacement for me ?
Edit : i think the force decryption was the culprit. When i rebooted, system was crashing. Op3t had its specific force decrypt file, not a general one, So i think as the development moves forward, op7 will also get it's own. Hoping the best ?
murti52 said:
Sadly it didn't worked, as phone doesn't gets detected on pc, keeps on rebooting. Gave it to service center and they are also not able to solve it ??. So a replacement for me ?
Edit : i think the force decryption was the culprit. When i rebooted, system was crashing. Op3t had its specific force decrypt file, not a general one, So i think as the development moves forward, op7 will also get it's own. Hoping the best ?
Click to expand...
Click to collapse
This file also works on OP7 pro, so it should also work on normal op7. I think the issue comes from something other.
strongst said:
This file also works on OP7 pro, so it should also work on normal op7. I think the issue comes from something other.
Click to expand...
Click to collapse
Then there must be some issue with my flashing sequence. Btw, The service centre repaired the issue and i have rooted it and using bluespark with stock rom. I'll give the zip another try later on when a new update comes. Thanks for the help
I believe the default file system is ext4, is there any benefits changing it to f2fs?
Jacckz said:
I believe the default file system is ext4, is there any benefits changing it to f2fs?
Click to expand...
Click to collapse
A good and quick overview and comparison with oneplus 7 pro https://sparrowsnews.com/2019/08/13/difference-between-f2fs-and-ext4-file-system/
Hi, I am new to custom ROM's and Rooting my device. And i hope you can help me with my Problem. I have a OnePlus A6003
What i tried so far:
Before i tried installing CustomROM's my device was on OOS 10.3.0
Then i needed to use the "twrp-3.3.1-16-enchilada-Q-mauronofrio.img" to get into TWRP
in TWRP i followed the Instructions from the LinageOS site:
Now tap Wipe.
Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
Return to the previous menu and tap Advanced Wipe, then select the System partition and then Swipe to Wipe.
Sideload the LineageOS .zip package:
On the device, select “Advanced”, “ADB Sideload”, then swipe to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip
(Optionally): If you want to install any additional add-ons, run adb reboot sideload, then adb sideload filename.zip those packages in sequence.
info_outline
Note: If you want Google Apps on your device, you must follow this step before booting into LineageOS for the first time!
(Optional): Root your device by installing LineageOS’ AddonSU, (use the arm64 package) or by using any other method you prefer.
Once you have installed everything successfully, run ‘adb reboot’.
Click to expand...
Click to collapse
I was sure this wasn't the right way cause after i rebooted the device i couldn't get to LinageOS.
After that i could get the "twrp-installer-3.3.1-2-enchilada.zip" (The official version from the TWRP site to work)
Flashed LinageOS the proper way (that's what i thought, lol) through install in TWRP
after that i had the same problem i could boot one time into LinageOS and that was it.
Current State of the Phone:
Bootloader unlocked (check)
Recovery Mode starts LinageOS Recovery
Fastboot is working fine
TWRP is not installed
What i am basically trying to do is:
Install a Privacy Focused ROM (open for Suggestions but i think LinageOS is good)
Root with Magisk
Flash NanoDroid Packages
Flash AFWall+
Flash AdAway
Some questions that i have
Do i need the customized TWRP because my phone did originally run OOS 10.3.0?
Whats the proper way to install a ROM on this device and Root it afterwards with Magisk?
Hello, my goal is to flash TWRP onto both Slot A and Slot B.
I've flashed TWRP into Slot A, while Slot B is flashed with LineageOS recovery, currently.
I'm pretty sure I then flashed the OS/ROM with TWRP into Slot A but afterward I had a warning that read, "No OS Installed" - I thought it was a fluke, I rebooted System and it went back to TWRP with Slot A active.
I manually switched to Slot B and rebooted System and LineageOS loaded. Rebooted into recovery and discovered Slot B is still using LineageOS recovery.
From there, in the recovery interface, there's no option to manually change back to Slot A. Rebooted into fastboot and connected phone to PC and ran command:
fastboot set_active other
This switched back to Slot A
I rebooted the device which loaded TWRP on Slot A.
At this point what do I need to do to install TWRP onto Slot B and flash LineageOS onto Slot A and Slot B?
I assume through TWRP on Slot A - I can flash TWRP onto Slot B. Then manually change to Slot B - reboot into recovery and verify TWRP is installed on Slot B?
Doing this of course, will break (assumption again) the LineageOS installation and will have to re-install LineageOS.
Once verified, flash LineageOS onto both Slot A and Slot B.
I feel like I missed something but honestly I'm using multiple guides and I feel I'm going to end up breaking something since not all guides align well.
I know this is a noob question, so I apologize, but I am trying to follow guides, none of which are instructing from A-Z the processes to achieve this goal. I have no issues following instructions, if I did, I'd have broken linux boxes, including a linux server.
I'm willing to start from scratch if I have to, I just want to get it right once and for all.
This should be posted in the Q/A section.
Anyways, you can simply flash the twrp img to both slots using:
Code:
fastboot flash recovery_a name_of_twrp.img
fastboot flash recovery_b name_of_twrp.img
Then, once TWRP is flashed, just flash the installer zip after flashing a rom to keep twrp flashed to both slots.
azoller1 said:
This should be posted in the Q/A section.
Anyways, you can simply flash the twrp img to both slots using:
Code:
fastboot flash recovery_a name_of_twrp.img
fastboot flash recovery_b name_of_twrp.img
Then, once TWRP is flashed, just flash the installer zip after flashing a rom to keep twrp flashed to both slots.
Click to expand...
Click to collapse
This is in Slot A
Completed commands without error. Instead of installer zip, I have the twrp.img
Advanced > Install Recovery Ramdisk > select twrp.img
Swipe to install
Then instead of reboot, the instructions I'm following says to go Back into Advanced and then select Fix Recovery Bootloop then Swipe to confirm.
Here I receive an error related to magisk (Error 1) - Error patching kernel
The error message is: cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel ...
If I reboot system - I'm thrown back into TWRP recovery interface.
This indicates that I need to install the boot.img
Install > Tap Install Image > Select boot.img > select Boot partition > Swipe ton confirm
[IMAGE FLASH COMPLETE]
Reboot System is selected and LineageOS loads.
Open Magisk > Install > Patch boot.img
However, when I first installed LineageOS and set it up with Magisk and TWRP - I had already patched the boot.img - literally this happened yesterday.
Would I need to do it again? I would assume not.
So I go back into TWRP > Install > Image > select the Magisk patched boot.img > check the box to install on both Slots A and B > Swipe to confirm
LineageOS loads.
Now back to TWRP to complete the process of permanently installing TWRP Recovery:
Advanced > Install Recovery Ramdisk > select twrp.img
Tap Back into Advanced > Fix Recovery Bootloop > Swipe to confirm
This time no error - SUCCESS!
Reboot System, but boots into TWRP. No access to LineageOS.
In TWRP I go to Reboot > Select System Partition with Slot A active and it once again reboots into TWRP.
I repeat the process this time selecting Slot B and again reboots into TWRP.
I go back into TWRP, Install > Image > Magisk patched Boot.img > Reboot
LineageOS loads.
Is this the correct process? If so, I imagine that after flashing TWRP onto both Slot A and Slot B, I need to repeat this process on Slot B now?
Also another assumption - is the magisk patched boot.img an actual nandroid backup? Because it flashed the exact image (apps/settings etc..) that I had patched with magisk.
However, if it is, for whatever reason a good portion of my apps are broken. When I open them - they crash. I have to uninstall the app and then re-install it from Aurora Store.
It's not a big deal but I would love for the image to be 100% complete without the apps or even settings being broken/different. But maybe I'm getting ahead of myself here.
Fumetsu_Guritto said:
This is in Slot A
Completed commands without error. Instead of installer zip, I have the twrp.img
Advanced > Install Recovery Ramdisk > select twrp.img
Swipe to install
Then instead of reboot, the instructions I'm following says to go Back into Advanced and then select Fix Recovery Bootloop then Swipe to confirm.
Here I receive an error related to magisk (Error 1) - Error patching kernel
The error message is: cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel ...
If I reboot system - I'm thrown back into TWRP recovery interface.
This indicates that I need to install the boot.img
Install > Tap Install Image > Select boot.img > select Boot partition > Swipe ton confirm
[IMAGE FLASH COMPLETE]
Reboot System is selected and LineageOS loads.
Open Magisk > Install > Patch boot.img
However, when I first installed LineageOS and set it up with Magisk and TWRP - I had already patched the boot.img - literally this happened yesterday.
Would I need to do it again? I would assume not.
So I go back into TWRP > Install > Image > select the Magisk patched boot.img > check the box to install on both Slots A and B > Swipe to confirm
LineageOS loads.
Now back to TWRP to complete the process of permanently installing TWRP Recovery:
Advanced > Install Recovery Ramdisk > select twrp.img
Tap Back into Advanced > Fix Recovery Bootloop > Swipe to confirm
This time no error - SUCCESS!
Reboot System, but boots into TWRP. No access to LineageOS.
In TWRP I go to Reboot > Select System Partition with Slot A active and it once again reboots into TWRP.
I repeat the process this time selecting Slot B and again reboots into TWRP.
I go back into TWRP, Install > Image > Magisk patched Boot.img > Reboot
LineageOS loads.
Is this the correct process? If so, I imagine that after flashing TWRP onto both Slot A and Slot B, I need to repeat this process on Slot B now?
Click to expand...
Click to collapse
I am not sure where you are seeing Advanced > Install recovery ramdisk in twrp. You should never have to used the advanced menu in twrp, unless for very specific reasons.
Ok, lets assume you are running the latest stock OOS.
1. First, you unlock the bootloader and can now use fastboot.
2. Reboot to bootloader
3. At this point you flash the twrp.img file to both recovery slots like i mentioned in my other post.
4. At this point you have twrp forever until something else overwrites the recovery partitions (flashing rom, flashing other custom recovery, etc).
5. Now, you need to factory reset, go to reboot then switch to the inactive slot, dont reboot, go back to install, then flash the rom zip file.
6. After flashing the rom zip file, flash the twrp installer zip file to overwrite the rom recovery.img so you can retain twrp.
7. Then you can reboot system and you will boot to the other slot where the rom was just flashed and everything should be ok.
Since twrp for the 8T is still not fully stable, but works very well, I dont think its good to flash .imgs directly in twrp, im sure it works but I usually just flash compatible zip files in twrp and use fastboot manually to flash a specific img if desired.
For magisk, the dev states in the instructions that flashing in twrp is not recommended (for the 8t in this case) and is better to boot the patched img from fastboot then go into magisk and direct install. Flashing using fastboot should work 100% of the time without issues. I have always just flashed the patched boot.img directly in fastboot and reboot with no issues.
However, if you prefer to flash in twrp, you must reboot back into recovery (reboot then press recovery) after flashing the rom and the twrp installer, so your device is updated to the other slot where the rom was flashed. Now you can flash magisk and it will flash to the correct boot.img slot.
Fumetsu_Guritto said:
Also another assumption - is the magisk patched boot.img an actual nandroid backup? Because it flashed the exact image (apps/settings etc..) that I had patched with magisk.
However, if it is, for whatever reason a good portion of my apps are broken. When I open them - they crash. I have to uninstall the app and then re-install it from Aurora Store.
It's not a big deal but I would love for the image to be 100% complete without the apps or even settings being broken/different. But maybe I'm getting ahead of myself here.
Click to expand...
Click to collapse
A magisk patched img is a boot.img unpacked and magisk is then injected and repacked. The size is 96mb.
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