Flashed Recovery and OS from OP5T on OP5 - OnePlus 5 Questions & Answers

Hi,
i've made a big mistake, i have flashed TWRP and LineageOS/Stock-Roms from Oneplus 5T on my Oneplus 5. There was only a few things that don't work. Now when i boot into Recovery i can't install LineageOS for the OnePlus 5 because of Error 7. Is there a special TWRP for Oneplus 5T and Oneplus 5 or is it the same for both devices? At the moment there is no OS installed. I have flashed this Recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 and tried to flash LineageOS for OnePlus 5 but it failed with
zip treble compatibility error!
invalid zip file format
Click to expand...
Click to collapse
I have the same error when i try LineageOS and LineageOS microG. What is wrong here? Is there any way to start again with a new fresh stock rom for the oneplus 5?

gene2 said:
Hi,
i've made a big mistake, i have flashed TWRP and LineageOS/Stock-Roms from Oneplus 5T on my Oneplus 5. There was only a few things that don't work. Now when i boot into Recovery i can't install LineageOS for the OnePlus 5 because of Error 7. Is there a special TWRP for Oneplus 5T and Oneplus 5 or is it the same for both devices? At the moment there is no OS installed. I have flashed this Recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 and tried to flash LineageOS for OnePlus 5 but it failed with
I have the same error when i try LineageOS and LineageOS microG. What is wrong here? Is there any way to start again with a new fresh stock rom for the oneplus 5?
Click to expand...
Click to collapse
Yes, there are 2 ways.
1. Flash OOS from bootloader, or via adb sideload. Else use MSM Tool to flash OOS. Then lock bootloader, and unlock again to flash the TWRP. After that all back to normal.
2. Lock the bootloader and unlock, then flash CodeworkX Force Encrypt TWRP from the same link. Format data and try.
#1 will make it all clean with no need of vendor again.
#2 will have the need to flash vendor image again.

is it stable? did u have navigation gestures hahaha just wondering
what didnt work?

Most works. Microphone didn't work and sometimes bluetooth.

Related

[FIX][DM-Verity][Oneplus3/3T]DM-Verity/Force Encryption Patched Boot Image

I am creating this thread keeping in my mind the several posts in various threads mentioning that they have accidentally triggered the DM-Verity flag and have an annoying message during startup or due to force encryption in the boot image the phone went back to encrypted state after flashing a new Stock Oxygen OS zip file in TWRP recovery.
So I decided to start a thread where I will post the links to the OFFICIAL BOOT IMAGES of Oxygen OS ROMs for both OnePlus3 and OnePlus3T which have been patched to disable the DM-Verity Flag and to disable the Force encryption that is present in the Stock Oxygen OS ROM.
NB: This thread is only for Nougat Based OOS ROMs. For disabling Dm-Verity and force Encryption in PIE OOS ROMs refer to my thread here: https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324. For Disabling DM-Verity in Oreo Based OOS ROMs visit my thread here: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
THIS IS FOR BOTH ONEPLUS 3 and 3T and read the instructions carefully and apply the file specific for your model
Disclaimer: I am not responsible for any damage to your phone by using this...
Nothing has been changed....
It is 100% stock boot image except that the DM-Verity Flag and Force Encryption has been patched...
Links:
For ONEPLUS 3T
STABLE OOS Boot Images
Patched Boot Image Stable OOS 4.5.1
http://www.mediafire.com/file/vm2k81s3pregdiv/boot-patched-4.5.1-OP3T.img
Patched Boot Image Stable OOS 4.5.0
http://www.mediafire.com/file/m8e3nu4ak4u1zkz/boot-patched-4.5.0-OP3T.img
Patched Boot Image Stable OOS 4.1.7
http://www.mediafire.com/file/g5rk4284lzyvqnu/boot-patched-4.1.7-OP3T.img
Patched Boot Image Stable OOS 4.1.6
[url]http://www.mediafire.com/file/j3802c259gea6f2/boot-patched-4.1.6-OP3T.img[/URL]
Patched Boot Image Stable OOS 4.1.5
[url]http://www.mediafire.com/file/78ej52gmthok212/boot-patched-OOS4.1.5.img[/URL]
BETA OOS Boot Images
Patched Boot Image OOS Beta 15
http://www.mediafire.com/file/a436larx3ddx00l/boot-patched-Beta15-OP3T.img
Patched Boot Image OOS Beta 14
http://www.mediafire.com/file/brlvdth86lxi0yl/boot-patched-Beta14-OP3T.img
Patched Boot Image OOS Beta 13
http://www.mediafire.com/file/2clnhl0x4vu8bu8/boot-patched-Beta13-OP3T.img
Patched Boot Image OOS Beta 12
http://www.mediafire.com/file/2214mr1adpdwlx4/boot-patched-Beta12-OP3T.img
Patched Boot Image OOS Beta 11
http://www.mediafire.com/file/hywcwmv0a993ah5/boot-patched-Beta11-OP3T.img
Patched Boot Image OOS Beta 10
http://www.mediafire.com/file/n7nu0wj266e8fhh/boot-patched-Beta10-OP3T.img
Patched Boot Image OOS Beta 9
[url]http://www.mediafire.com/file/5lkp6fi33u9lkpt/boot-patched-Beta9-OP3T.img[/URL]
Patched Boot Image OOS Beta 8
[url]http://www.mediafire.com/file/4d5zrpff4jakjgk/boot-patched-OOS_Beta_8.img[/URL]
For OnePlus 3
STABLE OOS Boot Images
Patched Boot Image Stable OOS 4.5.1
http://www.mediafire.com/file/srdurw9pg4f614f/boot-patched-4.5.1-OP3.img
Patched Boot Image Stable OOS 4.5.0
http://www.mediafire.com/file/nrbuddj0652bf4u/boot-patched-4.5.0-OP3.img
Patched Boot Image Stable OOS 4.1.7
http://www.mediafire.com/file/2cb3jrqckb4suxw/boot-patched-4.1.7-OP3.img
Patched Boot Image Stable OOS 4.1.6
[url]http://www.mediafire.com/file/ytax9vfa9lyhd6d/boot-patched-4.1.6-OP3.img[/URL]
BETA OOS Boot Images
Patched Boot Image OOS Beta 24
http://www.mediafire.com/file/8fcbeiduhiewc9v/boot-patched-Beta24-OP3.img
Patched Boot Image OOS Beta 23
http://www.mediafire.com/file/9i3snrmmsinczct/boot-patched-Beta23-OP3.img
Patched Boot Image OOS Beta 22
http://www.mediafire.com/file/bauq66z2s6o2k1q/boot-patched-Beta22-OP3.img
Patched Boot Image OOS Beta 21
http://www.mediafire.com/file/r31feak94y3cm5z/boot-patched-Beta21-OP3.img
Patched Boot Image OOS Beta 20
http://www.mediafire.com/file/5h32hzw5ot1gbba/boot-patched-Beta20-OP3.img
Patched Boot Image OOS Beta 19
http://www.mediafire.com/file/y6446j7sxiw9jwx/boot-patched-Beta19-OP3.img
Patched Boot Image OOS Beta 18
http://www.mediafire.com/file/zfsji9mjjds7a6n/boot-patched-Beta18-OP3.img
Patched Boot Image OOS Beta 17
[url]http://www.mediafire.com/file/mrqhkq7igt7x4na/boot-patched-Beta17-OP3.img[/URL]
USAGE FOR STOCK OOS:
# Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip in TWRP before doing anything (even before restarting or applying any patches, root, kernels, etc.)
# Restart back to TWRP Recovery.
# Done.
# Now do whatever you want like usual.. Flash root, kernel, mods or anything as usual
# You dont have to worry about triggering DM-Verity or Getting Force Encrypted again...
VERY IMPORTANT: FOR PEOPLE WHO HAVE ALREADY TRIGGERED DM-VERITY ON THEIR OOS OR CUSTOM ROM AND NEEDS TO GET RID OF THE DM-VERITY MESSAGE PERMANENTLY, READ MY POST 2. AFTER GETTING RID OF DM-VERITY BY FOLLOWING THE STEPS IN POST 2, NEXT TIME ONWARDS WHILE UPDATING YOUR OOS OR CUSTOM ROM FOLLOW THE INSTRUCTIONS IN THIS OP TO KEEP YOUR OOS AND PHONE FREE FROM THE TROUBLE OF DM-VERITY AND FORCE ENCRYPTION...
FAQs:
Q: Is the boot.img file altered in anyway?
A: As mentioned above its 100% stock boot image except that the DM-Verity Flag and Force Encryption has been patched...
Q: My phone is already encrypted, will I lose encryption?
A: No. It only disables force encryption. That means if you have already disabled encryption in your phone it will prevent the phone from getting encrypted when you flash a stock OOS ROM..
Q: I happen to lose TWRP and revert to stock recovery every time I update OOS, I happen to lose data/apps accidentally while updating OOS after I lose TWRP ...Can this be corrected by using this method?
A: Definitely. Follow the steps correctly. Each time while updating the OOS, after flashing the Full OOS ROM.zip, immediately flash the patched boot.img of the corresponding OOS given in this thread and then restart back to TWRP recovery. Done. You will never lose TWRP again..
Q: I am Rooting my phone using Magisk/Supersu then why do i need this?
A: Its optional.. If you are rooting phone using Magisk/Supersu it patches the stock boot.img. But in case you have problems flashing Magisk/Supersu after flashing the STOCK ROM zip this can come in handy or as an insurance policy just flash this patched boot.img before doing anything. But is very helpful to those people out there who doesn't root their phone but has unlocked their phone or installed TWRP for other purposes..
Q: How to flash the patched boot.img in TWRP?
A: Default flash option is for zip files in TWRP. Select the flash image option in TWRP. Then select the downloaded patched boot.img file and among from the partition option (boot, recovery and system) select the boot option and then flash it.
Q: Can I use it for CUSTOM ROMs? / What to do while updating CUSTOM ROMs?
A: For hassle free and the best results whenever you update CUSTOM ROMs always do it this way...
The below steps are for CUSTOM ROMs only. (For STOCK ROMs follow the main step mentioned above in the section USAGE)...
1.Go to TWRP
2.Flash the required firmware zip file
3.Flash the corresponding patched boot IMG
4.Flash the ROM whether LINEAGE, RR, ASOP, etc.
5.Flash gapps
6.Flash root (magisk /su)
7.Flash kernel
8.At last Reboot...
There will not be any problem ever...
You can reboot after step 5
Steps 6,7 are optional
Q: What is "-Xn" seen after the OOS Version in the settings menu?
A: That's just my signature -Xn that I had put there to make sure that you have correctly done the procedure and the boot image that is currently in use is my patched boot image and to ensure you that you are 100% safe from DM verity and forced encryption..
Hope you find it useful...
Will update as newer OOS versions come....
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...
THIS IS FOR PEOPLE WHO HAVE TRIGGERED DM-VERITY AND NEEDS TO GET RID OF THE DM-VERITY MESSAGE PERMANENTLY ON OOS OR OPEN BETA OR CUSTOM ROM. CONFIRMED WORKING EVEN IN THE LATEST OOS 4.5.1/BETA Nougat Roms...
THIS IS FOR ONEPLUS 3T AND FOR ONEPLUS 3 but be careful in using the correct files corresponding to the OOS version and your MODEL
FOLLOW THE STEPS EXACTLY AND 100% THE DM-VERITY MESSAGE WILL BE GONE WITHOUT ANY DATA LOSS OR ANY OTHER HARM!!!
Prerequisite : Install ADB for windows from here: [url]https://forum.xda-developers.com/showthread.php?t=2588979[/URL]
1)
Download 4.0.2 Firmware for Oneplus 3T from here: [url]http://www.mediafire.com/file/cx568em66025p5b/4.0.2_firmware_OnePlus_3T.zip[/URL]
Download 4.0.2 Firmware for Oneplus 3 from here: [url]http://www.mediafire.com/file/8tt5x4xxy4m488t/4.0.2_firmware_OnePlus3.zip[/URL]
2) Flash the downloaded 4.0.2 firmware OnePlus 3.zip or 4.0.2 firmware OnePlus 3T.zip file in TWRP.
3) DONT REBOOT TO SYSTEM. REBOOT TO BOOTLOADER FROM OPTION IN TWRP.
4) Connect your phone to the pc
5) Press windows button + X
6) Open Command prompt
7) Type "fastboot oem disable_dm_verity" without quotes and press enter
8) Type "fastboot oem enable_dm_verity" without quotes and press enter
9) DONT REBOOT TO SYSTEM. REBOOT TO TWRP RECOVERY.
10)
In case of Oneplus3T, Flash the required firmware files for Stable or Open Beta OOS corresponding to your current OOS (current OOS is the version of OOS which you are using now on your phone) in TWRP from this post: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166(Courtesy: @kamilmirza)
In case of Oneplus3, Flash the required firmware files for Stable or Open Beta OOS corresponding to your current OOS (current OOS is the version of OOS which you are using now on your phone) in TWRP from this post: [url]https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628[/URL] (Courtesy: @jamal2367)
11) DONT REBOOT!!!!
10) VERY IMPORTANT: WITHOUT REBOOTING, Flash the downloaded boot-patched.img file corresponding to the OOS version and phone model(either stable or beta) in TWRP from post 1...
11) Reboot..The DM-verity message is gone forever...
VERY IMPORTANT: If you are attempting this method on a a CUSTOM ROM then after Step 10 flash the full CUSTOM ROM zip file + latest gapps again without doing any sort of wipes in TWRP immediately and then only reboot....
Enjoy!!!
FAQs...
Q: Will I lose any data after I do these steps?
A: Never. There will be no data loss or any untoward effects of the procedure. Your data and phone will be in the exact same state as it was a before except for the fact that the damn dirty Dm-Verity message will be gone forever!!!
Q: Will this work on CUSTOM ROMs?
A: Of course. It has been tested to be perfectly working on even CUSTOM ROMs. Just follow the instructions in this post carefully where specific steps for CUSTOM ROMs are mentioned.
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...
Thanks mate..... You made my day..... Working perfectly.
Nice to see this thread on the day of release of oos 4.1.5 itself.
Deleted..
So well explained and working perfectly
One if the most detail step by step explanation
Thanks dev.
Hi,
I have already done the second method on 4.1.4 but without reflashing the firmware so will I have to do it again when Install 4.1.5?
MohamedRaafat said:
Hi,
I have already done the second method on 4.1.4 but without reflashing the firmware so will I have to do it again when Install 4.1.5?
Click to expand...
Click to collapse
Do the second method only if you trigger DM Verity while installing 4.1.5
To be sure you don't trigger DM Verity while installing 4.1.5 follow the instructions in the OP...
Hi,
would it be too bold to ask if something similar could be prepared also for OP3?
I have exactly the same problem with DM-Verity triggered on my OP3. I have seen several guides how to get rid of it but they are sometimes contradictory and the whole process seems to be a bit overwhelming.
This solution seems to be the cleanest of all I have seen but I am not so lucky to own OP3T.
Would you be so kind to prepare this also for us, OP3 owners, if possible?
Of course, there can be many valid reason why not and I can perfectly understand that. But I decided to ask, just in case...
prorokrak said:
Hi,
would it be too bold to ask if something similar could be prepared also for OP3?
I have exactly the same problem with DM-Verity triggered on my OP3. I have seen several guides how to get rid of it but they are sometimes contradictory and the whole process seems to be a bit overwhelming.
This solution seems to be the cleanest of all I have seen but I am not so lucky to own OP3T.
Would you be so kind to prepare this also for us, OP3 owners, if possible?
Of course, there can be many valid reason why not and I can perfectly understand that. But I decided to ask, just in case...
Click to expand...
Click to collapse
I have been thinking about it for the past few days...
Anyways I thought as no one asked they were not interested in getting the patched boot images for op3...
Ok.. they have released OOS 4.1.6..
So will push the links for the patched boot images for both op3 and op3T tomorrow after I test and get hands on the flashable ROMs.
The OP has been updated to accomodate both ONEPLUS 3T and ONEPLUS 3
Now this thread can be used for both models and will be updated as new OOS version come..
Enjoy!!!
NEW UPDATE RELEASED!!!
Links in OP...
Oxygen OOS 4.1.6 patched boot images for ONEPLUS 3T and ONEPLUS 3...
Thenks for this!
sparky vicky said:
How did you flashed the bootimg? through twrp? it's asking for 3 options like boot, recovery,system? im confused
Click to expand...
Click to collapse
Just flash the patched boot.img and select boot in the twrp option..
It's the boot image so boot option...
Xennet said:
Just flash the patched boot.img and select boot in the twrp option..
It's the boot image so boot option...
Click to expand...
Click to collapse
Yes i choose boot but still the warning showing on boot
sparky vicky said:
Yes i choose boot but still the warning showing on boot
Click to expand...
Click to collapse
Which phone are you using op3 or 3t..
Did you flash 4.0.2 zip and type the commands
Tell the steps you did.
Which is the warning being shown?
DM Verity warning or the the phone is unlocked warning??
Im on OP3T, OOS 4.1.6
sparky vicky said:
Im on OP3T, OOS 4.1.6
Click to expand...
Click to collapse
Which is the warning being shown and explain the steps you did
Xennet said:
Which phone are you using op3 or 3t..
Did you flash 4.0.2 zip and type the commands
Tell the steps you did.
Which is the warning being shown?
DM Verity warning or the the phone is unlocked warning??
Click to expand...
Click to collapse
Dm verity warning showing and asusal the unlocked warning also. Im on 3T with OOS 4.1.6. I need to flash 4.0.2 zip before this? Those are not mentioned in OP?
---------- Post added at 05:28 PM ---------- Previous post was at 05:26 PM ----------
Xennet said:
Which is the warning being shown and explain the steps you did
Click to expand...
Click to collapse
Flashed 4.1.6 with twrp at same time without reboot flashed bootpatch and rebooted to system and still the dm verity showung
Did i collapsed the procedure?:silly:
sparky vicky said:
Dm verity warning showing and asusal the unlocked warning also. Im on 3T with OOS 4.1.6. I need to flash 4.0.2 zip before this? Those are not mentioned in OP?
Click to expand...
Click to collapse
Mate do read the second post in the OP...
For getting rid of the DM-Verity message..
The first OP post is only for those who have no DM Verity warning on their phone..
If you already have DM Verity warning on your phone you have to follow the second post..it is clearly mentioned in the OP.. AND WRITTEN IN BOLD LETTERS..
Once you get rid of the DM Verity warning from next time onwards you have to follow only the instructions in the first OP post..

Upgrading blu_spark TWRP to official for decryption

I have blu_spark TWRP and working root on my international 6T. I would like to upgrade the recovery to the official TWRP now, as file decryption is working now in the official.
Is this the correct process to go from blu_spark to official?
Download the fajita TWRP .img and .zip files (from https://forum.xda-developers.com/oneplus-6t/development/recovery-unofficial-twrp-touch-recovery-t3861482
Connect phone to PC and enter fastboot mode
Boot the .img file
Once in recovery, flash the new .zip file
My plan is to then flash the new Oxygen OS released from OnePlus and then flash Magisk.
Looks okay
However, the flash of the OS in TWRP is not clearly defined. Everyone is waiting for new update to try it in the TWRP... So, basically if you wanna flash it that way, you'll probably be the first.... This could put you in the risk of bricking the device though.
I have just done this. Yes you can boot the unofficial 6T recovery and then flash the installer no problem. However if you were running a OP6 ROM the 6T will not decrypt it, unless Im soing something wrong. On my phone once Im on a OP6 rom like LOS16 I can only use the Blu TWRP, if I go back to stock 6T OOS I have to use the 6T TWRP to decrypt. On either system I can bounce between TWRP versions without issue doing as you said, boot the img, then flash the zip, but I cant view anything. Going back to thr correct TWRP restores data access, no bricking worries that Ive run into personally.
There is no official TWRP yet...
Sent from my OnePlus 6T using Tapatalk
celtic426 said:
I have blu_spark TWRP and working root on my international 6T. I would like to upgrade the recovery to the official TWRP now, as file decryption is working now in the official.
Is this the correct process to go from blu_spark to official?
Download the fajita TWRP .img and .zip files (from https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Connect phone to PC and enter fastboot mode
Boot the .img file
Once in recovery, flash the new .zip file
My plan is to then flash the new Oxygen OS released from OnePlus and then flash Magisk.
Click to expand...
Click to collapse
I did a post below for the update to Unofficial version with decryption working
https://forum.xda-developers.com/showpost.php?p=78267079&postcount=299
Sent from my OnePlus6T using XDA Labs
Thanks for the replies.
I successfully went from blu_spark TWRP to the newer faijta TWRP which has the option for decrypting.
That allowed me to use the recovery to flash the new OTA OxeygenOS update which I downloaded from oneplus.com.

Android 10/11 GSI setup for Oneplus 5

Can anyone guide or gimme any link for the steps for flash Generic Phh GSI or ErfanGSI on Oneplus 5
I've tried every method but every time device rebooted to Recovery...
Thanks
zaibansari20 said:
Can anyone guide or gimme any link for the steps for flash Generic Phh GSI or ErfanGSI on Oneplus 5
I've tried every method but every time device rebooted to Recovery...
Thanks
Click to expand...
Click to collapse
use pie vendor (lineage 16)
all Q vendor from custom rom didnt boot
install lineage and noverity (i'm on decrypted)
reboot into twrp and factory reset
install MakeMeSAR file (before install gsi system image) always
https://www.androidfilehost.com/?fid=4349826312261728344
now install gsi image system (Q/R) and noverity
https://sourceforge.net/projects/my-builds/files/Misc. Files/No Verity Treble 4.0.zip/download
reboot system.
jahidinbedod said:
use pie vendor (lineage 16)
all Q vendor from custom rom didnt boot
install lineage and noverity (i'm on decrypted)
reboot into twrp and factory reset
install MakeMeSAR file (before install gsi system image) always
https://www.androidfilehost.com/?fid=4349826312261728344
now install gsi image system (Q/R) and noverity
https://sourceforge.net/projects/my-builds/files/Misc. Files/No Verity Treble 4.0.zip/download
reboot system.
Click to expand...
Click to collapse
I'll give it a shot and let you know
Thanks
great!it works
billsz said:
great!it works
Click to expand...
Click to collapse
I've been busy in my exams, I'll try this as soon as get free
Which GSI you flashed??
Is it stable enough??

Problems with installing LineageOS 17.1

Good morrning everyone!
i am a little bit helpless with my plan to flash LineageOS 17.1 onto my OP 6T. I started from LineageOS 16, which was rooted with Magisk.
With my first attempt I followed the instructions from https://wiki.lineageos.org/devices/fajita/install. I used the latest files from 20200903 of LineageOS. But after flashing temporarily the recovery, I ended up with a stuck in oem-unlock-screen. To fix it i used the MSMtool 4.0.59.
I flashed only boot and not boot_a or boot_b. So I tried it with that now. But I only got the same results. I was unable to boot into recovery. So again MSM Tool and unlocking the bootloader.
Then I tried to install it via TWRP. OOS 9.0.13:
1. booted into fastboot mode
2. booted TWRP 3.3.1.0
3. Wiped Data and rebooted into fastboot mode
4. booted again TWRP 3.3.1.0
5. installed LineageOS lineage-17.1-20200903-nightly-fajita-signed.zip
6. installed TWRP 3.4.0
7. rebooted into recovery
8. repeated 5. and 6.
9. rebooted into recovery
10. installed open gapps-nano
11. installed Magisk 20.4
12. rebooted the system
Result: Qualcomm CrashDump Mode......
I do not understand what I did wrong. In June I installed Lineage OS on another OP 6T and it worked fine with flashing the recovery to boot_a. But I do not know which OOS was installed. No I am trying it since hours and only end up in the above mentioned results.
What do I have to do? Thanks for your help in advance!
Greetings
Thawu
My LOS Install Guide
- Don't use TWRP 3.4.x. Use 3.3.1-32 (The latest 3.3.1 version.) 3.4.x will give you issues.
Thank you lot. Lineage ist booting =)
Thawu said:
Thank you lot. Lineage ist booting =)
Click to expand...
Click to collapse
I also just noticed you are trying to use a very old version of OOS (which also means old firmware). Why are you using 9.0.13? Perhaps this could be your issue.
I need to update my guide, but 10.3.5, and the latest weekly 9-3 work fine. One warning, I never did get the 10.3.5 fastboot ROM to work on either of my 6Ts. The 10.3.4 Fastboot ROM works fine, then I had to update to 10.3.5 using TWRP.
I asked if anyone else had problems with the 10.3.5 fastboot ROM in the fastboot thread but didnt get any replies...
I started at first wit OOS 9 because of the latest (?) msm tool. I regocnized later, that it is crucial to update OOS to Android 10 what I did after I posted my question. I installed OOS 10.3.5 from oneplus.com via TWRP.
So all I had to do yesterday was to reinstall TWRP 3.3.1-32.
Your guide for installing LineageOS was by far the best I got. All the little explenations were the things I needed to understand, why the steps had to be done. So again thank you for your help and your guide which is really really good.
Greetings
Thawu
Thawu said:
I started at first wit OOS 9 because of the latest (?) msm tool. I regocnized later, that it is crucial to update OOS to Android 10 what I did after I posted my question. I installed OOS 10.3.5 from oneplus.com via TWRP.
So all I had to do yesterday was to reinstall TWRP 3.3.1-32.
Your guide for installing LineageOS was by far the best I got. All the little explenations were the things I needed to understand, why the steps had to be done. So again thank you for your help and your guide which is really really good.
Greetings
Thawu
Click to expand...
Click to collapse
Also if you like themed TWRP @acuicultor and @ morphine1e1 have a really nice creation for OP6/6t here: https://forum.xda-developers.com/on...covery-theme-blacked-twrp-acuicultor-t3847752
It's latest twrp but I've been using it for months without any issues and I flash much more than a regular user. Installed LOS twice and all good.
或许你应该先升级到安卓10 再去安装lineage os 17
Thawu said:
Good morrning everyone!
i am a little bit helpless with my plan to flash LineageOS 17.1 onto my OP 6T. I started from LineageOS 16, which was rooted with Magisk.
With my first attempt I followed the instructions from https://wiki.lineageos.org/devices/fajita/install. I used the latest files from 20200903 of LineageOS. But after flashing temporarily the recovery, I ended up with a stuck in oem-unlock-screen. To fix it i used the MSMtool 4.0.59.
I flashed only boot and not boot_a or boot_b. So I tried it with that now. But I only got the same results. I was unable to boot into recovery. So again MSM Tool and unlocking the bootloader.
Then I tried to install it via TWRP. OOS 9.0.13:
1. booted into fastboot mode
2. booted TWRP 3.3.1.0
3. Wiped Data and rebooted into fastboot mode
4. booted again TWRP 3.3.1.0
5. installed LineageOS lineage-17.1-20200903-nightly-fajita-signed.zip
6. installed TWRP 3.4.0
7. rebooted into recovery
8. repeated 5. and 6.
9. rebooted into recovery
10. installed open gapps-nano
11. installed Magisk 20.4
12. rebooted the system
Result: Qualcomm CrashDump Mode......
I do not understand what I did wrong. In June I installed Lineage OS on another OP 6T and it worked fine with flashing the recovery to boot_a. But I do not know which OOS was installed. No I am trying it since hours and only end up in the above mentioned results.
What do I have to do? Thanks for your help in advance!
Greetings
Thawu
Click to expand...
Click to collapse
I install it on HTC u11.. but voice call speaker not working and Bluetooth voice speaker not working .

POCO M3 convert to EU rom and root

Hello, I want to know if I can convert my POCO M3 from global rom to EU rom and then root it after converting and also what are the necessary steps. Thank you. (my bootloader will be unlocked in 6 days.)
Yes, it is possible. Do you mean the official EEA rom or xiaomi.eu custom rom?
For EEA rom you need to flash the fastboot version with MiFlash tool. For xiaomi.eu you can follow the guide from this forum.
For root you need to patch the stock boot.img (you can extract it from the fastboot rom) with Magisk Manager, copy to your computer and flash it with fastboot, because there is no TWRP recovery yet.
When you are going to flash, make shure to keep the bootloader unlocked. This is very important because you will brick your phone if you relock your phone with an other rom than the original one.
mierlo420 said:
Yes, it is possible. Do you mean the official EEA rom or xiaomi.eu custom rom?
For EEA rom you need to flash the fastboot version with MiFlash tool. For xiaomi.eu you can follow the guide from this forum.
For root you need to patch the stock boot.img (you can extract it from the fastboot rom) with Magisk Manager, copy to your computer and flash it with fastboot, because there is no TWRP recovery yet.
When you are going to flash, make shure to keep the bootloader unlocked. This is very important because you will brick your phone if you relock your phone with an other rom than the original one.
Click to expand...
Click to collapse
I'd like to try the xiaomi.eu rom. Thank you, I'll look into it.
Hi Friends. i found a link by Havoc Rom Developer how to Flash Havoc 3.12 GSI on Poco M3 with a Super Gsi Flasher tool. unfortunately it did not work for me. But i tried the same tool with the following GSI and every one of them worked on my Poco M3. i am now currently using Pixel Experience Plus on my Poco M3.
1) Lineage 18.1 ( Android 11 )
2) Pixel Experience Plus ( Android 10 )
3) CR Droid ( Android 10 )
4) Resurrection Remix ( Android 10 )
Procedure.....
1) I Flashed TWRP Recovery in fastboot mode.
2) Then i flashed EU MIUI Rom on Poco M3 with TWRP Recovery.
3) Then I Flashed a Patched VBMETA image in fastboot mode.
4) Then restarted Poco M3 on EU Rom.
5) I did not register any Google or other account on EU Rom and i did not connect it to the net.
6) I copied SUPER GSI FLASHER on the Phone Memory partition.
7) I copied GSI Image that i wanted to flash .... into the Phone Memory Partition.
8) Rename the GSI image copied above as system.img
9) Then rebooted into recovery.
10) Clicked on Install and selected SUPER GSI FLASHER.
11) In about 2 minutes it said to reboot..........I Rebooted.....Rom running perfectly on POCO M3
12) Due Credit goes only to The Link Provided below for Havoc 3.12 and the developer who posted the link. Thanks a lot friend .....You made my day.....and i am passing on your good work to others like me who wish to flash POCO M3 with custom Rom.
LINK WHICH HELPED ME TO DO THE ABOVE
How to Install Havoc OS 3.12 custom ROM on Poco M3 - ROM-Provider
Download & Install havoc os 3.12 custom ROM on xiaomi Poco M3, this article will also guide you how to Install custom rom on Poco M3
romprovider.com
You can download SUPER GSI INSTALLER from above link and go through the instructions on the above link also. Download the GSI from GSI GITHUB WEBSITE.
The GSI should be arm64 ab version only.
ENJOY Friends

Categories

Resources