Related
So today I received a XT 1056. I then proceeded to unlock the bootloader and flash SU.
So I then tried flashing a CM 12 nightly build and all went well. I was able to setup the device until the screen was locked and then the phone instantly starts looping through the "Unfortunately, system UI has stopped." error. I've tried flashing an older version of the ROM, and I've tried numerous other 5.0 ROM's but each one will crash as soon as the screen is locked.
And it would not seem like a great idea to revert to an older version of Android and risk bricking the device.
So if someone could advise me how to get rid of the loop error it would be much appreciated.
I have TWRP 2.8.3 currently flashed if that makes any sort of difference....
Install the gApps...
690sid said:
Install the gApps...
Click to expand...
Click to collapse
I tried a fresh install of this CM12 with the gapps it says to use and once again I can setup the phone and as soon I get to the home screen the system UI loop happens. http://forum.xda-developers.com/moto-x/development/rom-unofficial-nightly-lollipop-5-0-t2960768
I also saw your post in that thread to try flashing with these instructions, but it still has the same error.
1 - Download an earlier version of the ROM that booted on you phone along with the gapps.
2 - Flash the ROM and gapps with a suitable recovery... CWM or TWRP 2.6.
3 - Download the latest release that you want to install.
4 - Flash the latest release over the pre - installed ROM without wiping anything.
Is it possible to just flash 4.4.4 or do I risk bricking the device?
So, I tried everything, flashed the ROM based on OREO like 9.6.1.0 ended in bootlooping the device, also custom rom based on OREO doesnt work too, like pixel experience, LINEAGE, ETC
Other than OREO based, ROM based on NOUGAT works well, like MIUI 8.xxx or RR based on NOUGAT
Any idea why this happens?
codearm2 said:
So, I tried everything, flashed the ROM based on OREO like 9.6.1.0 ended in bootlooping the device, also custom rom based on OREO doesnt work too, like pixel experience, LINEAGE, ETC
Other than OREO based, ROM based on NOUGAT works well, like MIUI 8.xxx or RR based on NOUGAT
Any idea why this happens?
Click to expand...
Click to collapse
-Format data
-wipe
-use otg drive since format data delete everything
-flash firmware newest 8.5.10 minimum requirment for oreo
-flash rom
-flash gapps
-reboot
evanlocked said:
-Format data
-wipe
-use otg drive since format data delete everything
-flash firmware newest 8.5.10 minimum requirment for oreo
-flash rom
-flash gapps
-reboot
Click to expand...
Click to collapse
tried it all, still bootloop
codearm2 said:
tried it all, still bootloop
Click to expand...
Click to collapse
flash any miui dev rom beyond 8.5.10 using miflash
reboot once ...
flash twrp ...
push any oreo rom (ie. LOS 15.1) and gapps while in recovery ...
Install that rom and gapps ...
reboot to twrp ...
format data ...
reboot again to twrp ...
reboot to system ...
3Dota said:
flash any miui dev rom beyond 8.5.10 using miflash
reboot once ...
flash twrp ...
push any oreo rom (ie. LOS 15.1) and gapps while in recovery ...
Install that rom and gapps ...
reboot to twrp ...
format data ...
reboot again to twrp ...
reboot to system ...
Click to expand...
Click to collapse
not working
Flashed 8.5.10 rom, ended in bootloop
flashed the LOS 15.1 and GAPPS, still bootloop
so, any one?
codearm2 said:
so, any one?
Click to expand...
Click to collapse
Your custom recovery needs to be an Oreo version compatible, so you can install oreo based roms on it.
Try to update to early version.
Regards.
codearm2 said:
So, I tried everything, flashed the ROM based on OREO like 9.6.1.0 ended in bootlooping the device, also custom rom based on OREO doesnt work too, like pixel experience, LINEAGE, ETC
Other than OREO based, ROM based on NOUGAT works well, like MIUI 8.xxx or RR based on NOUGAT
Any idea why this happens?
Click to expand...
Click to collapse
try updating firmware and twrp and flash lazy flasher zip after rom instalation hope it fix . *Lazy Flasher zip is must
Steffanom said:
Your custom recovery needs to be an Oreo version compatible, so you can install oreo based roms on it.
Try to update to early version.
Regards.
Click to expand...
Click to collapse
already 3.2.3 version which I believe supports oreo rom
Tsuzan said:
try updating firmware and twrp and flash lazy flasher zip after rom instalation hope it fix . *Lazy Flasher zip is must
Click to expand...
Click to collapse
didnt work, still bootloop
codearm2 said:
so, any one?
Click to expand...
Click to collapse
so ... what last rom boot fine in your Mi5?
3Dota said:
so ... what last rom boot fine in your Mi5?
Click to expand...
Click to collapse
any nougat rom works well
tried flashed 8.5.10 rom, still bootloop
codearm2 said:
any nougat rom works well
tried flashed 8.5.10 rom, still bootloop
Click to expand...
Click to collapse
this is quite weird ... since if you install any nougat ... you'll sure receive OTA update to oreo (dev or stable) ...
why dont you take that OTA?
3Dota said:
this is quite weird ... since if you install any nougat ... you'll sure receive OTA update to oreo (dev or stable) ...
why dont you take that OTA?
Click to expand...
Click to collapse
yes, installing the OTA based on OREO update also cause bootloop happens
basically, anything OREO based, whether it's ota or flashing it manually through TWRP, ZCX TWRP, or Mi Flash cause bootloop
Have you wipe your internal partition?
I think we need to wipe all partition after installing firmware when come from nougat to Oreo, because Oreo have new vendor partition.
At least you should use twrp-3.2.1-1-gemini
Sent from my MI 5 using Tapatalk
codearm2 said:
not working
Flashed 8.5.10 rom, ended in bootloop
flashed the LOS 15.1 and GAPPS, still bootloop
Click to expand...
Click to collapse
Try reflashing latest twrp via fastboot (not from within twrp).
After wiping all partitions (also mount and wipe vendor) and formatting data, reboot to recovery before flashing the ROM to access the data partition correctly again.
Then also try to boot (would go with a custom ROM) without any gapps, mods or root first, to further center the problem.
What happens now?
Have the same problem
Try to install latest build via fastboot --> failed
Try to install miui nougat based work, ota update to oreo based -->bootloop
Also try to flash all included internal storage but the problem still occured
Any miui nougat based and aex mod 5.1 work fine in my phone
Install lazy flasher before installing anything like SuperSU...
masruri03 said:
Have you wipe your internal partition?
I think we need to wipe all partition after installing firmware when come from nougat to Oreo, because Oreo have new vendor partition.
At least you should use twrp-3.2.1-1-gemini
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
already wiped, still not working
Phil_Smith said:
Try reflashing latest twrp via fastboot (not from within twrp).
After wiping all partitions (also mount and wipe vendor) and formatting data, reboot to recovery before flashing the ROM to access the data partition correctly again.
Then also try to boot (would go with a custom ROM) without any gapps, mods or root first, to further center the problem.
What happens now?
Click to expand...
Click to collapse
flashed latest twrp via fastboot, also already wiped all partition included mount and wipe vendor, also formated the data and reboot first before flashing the rom, boot without any gapps, still it doesnt work
reysack said:
Have the same problem
Try to install latest build via fastboot --> failed
Try to install miui nougat based work, ota update to oreo based -->bootloop
Also try to flash all included internal storage but the problem still occured
Any miui nougat based and aex mod 5.1 work fine in my phone
Click to expand...
Click to collapse
yeah, practically the same with mine
brhnahmad05 said:
Install lazy flasher before installing anything like SuperSU...
Click to expand...
Click to collapse
tried, doenst work
codearm2 said:
flashed latest twrp via fastboot, also already wiped all partition included mount and wipe vendor, also formated the data and reboot first before flashing the rom, boot without any gapps, still it doesnt work
Click to expand...
Click to collapse
Puh, don't know.
Do you have an old backup of your efs partition lying around?
If so, try restoring that.
If that also doesn't help, I'm through with my math here, I think...
Flash a Lineage OS 14.1 build without GApps but with a firmware that supports Oreo. Then, go to developer settings, turn on ADB and run adb devices on your computer so that the RSA Fingerprint pops up. There, make sure you tap on remember this computer and click ok.
Now, do an update to Lineage 15.1 without wiping anything. As soon as you reboot your phone, connect it to your PC and try to get a logcat. Paste the logcat here and we'll be able to see what's actually going on.
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Did you tried another recovery? Try Batik Recovery!
Anirudh15 said:
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
Hey there, how about u try to install Pitchblack twrp the latest one and install Pixel experience pie riva, it can be used for rolex also because the developer make the rom to unified for both rolex and riva. Then install the magisk after that. I've been using pixel experience pie for a month and it is so far so good.
Amir_espie said:
Hey there, how about u try to install Pitchblack twrp the latest one and install Pixel experience pie riva, it can be used for rolex also because the developer make the rom to unified for both rolex and riva. Then install the magisk after that. I've been using pixel experience pie for a month and it is so far so good.
Click to expand...
Click to collapse
Sure,will give it a go
An update
I installed Batik recovery.Magisk could be flashed but Im still getting the decryption unsuccessful message when I install Pixys
Solved Magisk Error!
I've been using Pixys OS on my Redmi 4A and it works fine smoothly. I recommended to clean wipe before installing. Android Pie us amazing and I've installed stable version. Do backup before clean wipe.
For Magisk I recommended this: https://freaksterism.blogspot.com/2018/10/solved-cannot-mount-vendor-magisk.html?m=1
It worked for me. Also go through this step before any custom ROM. Do let me know the status
Anirudh15 said:
An update
I installed Batik recovery.Magisk could be flashed but Im still getting the decryption unsuccessful message when I install Pixys
Click to expand...
Click to collapse
to solve decryption unsuccesful message, format data (Wipe>Format Data) after installing the rom, make sure you backup your internal storage coz Format Data will also ERASE the internal storage. This how i got over the decryption unsuccessfull message. hope this helped.
You have two problems.
Anirudh15 said:
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
You need to flash the twrp separated vendor version by my friend Offain https://androidfilehost.com/?fid=962187416754475993
The other problem with the decryption:
You must enter in the twrp press wipe and format data. Type yes and then reboot into twrp again. After that flash the rom and gapps and you will not have the decryption problem again
Anirudh15 said:
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
I had the same problem. Its because your phone is encrypted. The only solution I found is to boot the device into fastboot and using command: [fastboot format userdata] on PC. This will wipe all data off your phone so do backup. It removes encryption and now you can install any custom rom.
Decrypt ur phone first then flash, use twrp vendor
athish said:
to solve decryption unsuccesful message, format data (Wipe>Format Data) after installing the rom, make sure you backup your internal storage coz Format Data will also ERASE the internal storage. This how i got over the decryption unsuccessfull message. hope this helped.
Click to expand...
Click to collapse
Format Data was the only thing that worked for me. First backup everything on your mass storage.
Hi,
tried going from stock OxygenOS (rooted) to LineageOs 16 according to the LineageOS Instructions.
No dice.
After flashing successfully, including nano gapps, TWRP (3.2.3-1) tells me that there is no OS.
Reboot ends in the bootloader.
Tried flashing stock OxygenOS and it only shows me the OxygenOS boot animation.
Any Ideas on how to clean that up?
thx
afx
a.f.x. said:
Hi,
tried going from stock OxygenOS (rooted) to LineageOs 16 according to the LineageOS Instructions.
No dice.
After flashing successfully, including nano gapps, TWRP (3.2.3-1) tells me that there is no OS.
Reboot ends in the bootloader.
Tried flashing stock OxygenOS and it only shows me the OxygenOS boot animation.
Any Ideas on how to clean that up?
thx
afx
Click to expand...
Click to collapse
Please clarify - did you do the following steps from the installation instructions using the latest official TWRP?
4. Go back to return to main menu, then tap Wipe.
5. Now tap Format Data and continue with the formatting process. This will remove encryption as well as delete all files stored on the internal storage.
Sent from my OnePlus 3T using XDA Labs
Dupe
Dupe
BillGoss said:
Please clarify - did you do the following steps from the installation instructions using the latest official TWRP?
4. Go back to return to main menu, then tap Wipe.
5. Now tap Format Data and continue with the formatting process. This will remove encryption as well as delete all files stored on the internal storage.
Click to expand...
Click to collapse
Yes, as this is also part of the Lineage install instructions.
cheers
afx
a.f.x. said:
Yes, as this is also part of the Lineage install instructions.
cheers
afx
Click to expand...
Click to collapse
In that case, I strongly suggest that you use this version of TWRP https://androidfilehost.com/?fid=11410963190603866112
The official version of TWRP has a bug: if you decrypt the phone, you end up with a broken encryption header.
(Lots of discussion about this in https://forum.xda-developers.com/on...covery-official-twrp-touch-recovery-t3742894)
After installing TWRP, tap the Format Data button in the Wipe menu. This will reformat and fix the encryption header. You can then reinstall OOS.
Sent from my OnePlus 3T using XDA Labs
There's a problem with this build, just read the official thread on the forum...
Next build will fix it, you're not alone
BillGoss said:
In that case, I strongly suggest that you use this version of TWRP https://androidfilehost.com/?fid=11410963190603866112
Click to expand...
Click to collapse
This is the one I have installed. I already went on a Google tour before asking here.
After installing TWRP, tap the Format Data button in the Wipe menu. This will reformat and fix the encryption header. You can then reinstall OOS
Click to expand...
Click to collapse
I got OOS installed that way.
But only after I ignored the "No OS Installed" message in TWRP.
This killed TWRP, so flashed that again, then (after the wipe sequence) LOS 16, Gapps and Magisk and I am back to the "No OS installed" message and a reboot ends at the fastboot menu.
thx
afx
fra9090 said:
There's a problem with this build, just read the official thread on the forum...
Next build will fix it, you're not alone
Click to expand...
Click to collapse
Thanks!
So what is the best course of action now.
Stick with OOS until the next build or flash LOS 15.1 and then upgrade (or is this again a complete reflash)?
thx
afx
a.f.x. said:
Thanks!
So what is the best course of action now.
Stick with OOS until the next build or flash LOS 15.1 and then upgrade (or is this again a complete reflash)?
thx
afx
Click to expand...
Click to collapse
It's a major release, so you should do a full wipe anyway while you're installing lineage 16.0, stick with 15.1, or OOS.
Don't waste too much reinstalling everything, wait for lineage release.
Edit: They just release it
fra9090 said:
Edit: They just release it
Click to expand...
Click to collapse
Yup, flashing it already.
Still the TWRP message about no OS installed,
But Lineage boots!!!!
THX!!
afx
Another useful post for Titanium users:
https://forum.xda-developers.com/showpost.php?p=78599004&postcount=4
cheers
afx
a.f.x. said:
Yup, flashing it already.
Still the TWRP message about no OS installed,
But Lineage boots!!!!
THX!!
afx
Click to expand...
Click to collapse
Glad to here you're up and running again.
It's odd that you get the no OS message in TWRP, yet the phone boots.
See if deleting both the .twrps file and the theme folder (if it exists) in the TWRP directory helps .
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
It's odd that you get the no OS message in TWRP, yet the phone boots.
See if deleting both the .twrps file and the theme folder (if it exists) in the TWRP directory helps .
Click to expand...
Click to collapse
A regular reboot in TWRP works fine, it was just after the Install step where I had seen that message.
cheers
afx
BillGoss said:
In that case, I strongly suggest that you use this version of TWRP https://androidfilehost.com/?fid=11410963190603866112
The official version of TWRP has a bug: if you decrypt the phone, you end up with a broken encryption header.
(Lots of discussion about this in https://forum.xda-developers.com/on...covery-official-twrp-touch-recovery-t3742894)
After installing TWRP, tap the Format Data button in the Wipe menu. This will reformat and fix the encryption header. You can then reinstall OOS.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thanks a lot for your hint regarding the TWRP version.
I was stuck with "E1001: Failed to update system image" and "Error 7" on every custom or stock ROM I tried to install with TWRP 3.3.1-0 after my encrypted data partition got corrupted on latest update.
Formating data with TWRP 3.2.1 fixed the issue and I was finally able to reinstall the stock ROM.
a.f.x. said:
Hi,
tried going from stock OxygenOS (rooted) to LineageOs 16 according to the LineageOS Instructions.
No dice.
After flashing successfully, including nano gapps, TWRP (3.2.3-1) tells me that there is no OS.
Reboot ends in the bootloader.
Tried flashing stock OxygenOS and it only shows me the OxygenOS boot animation.
Any Ideas on how to clean that up?
thx
afx
Click to expand...
Click to collapse
Download os karnel + os ( you can find that in xda forum)
Then flash karnel and os
It will work
You should use usb otg
Hi all,
I have got another problem with the nightly updates since modem firmware changed to 9.0.4 in July . This is just the date, don't know if it is related to that.
Since then I get the common hints about "new nightly available".
-> download -> install.
"Preparing update" -> Reboot.
Getting into TWRP 3.3.1.0 -> Patching all fine. -> Reboot
Enter PIN to start Android -> starting Android
Lineage running circles but longer than normal -> Back to reboot and TWRP Main Menu
That's it. This happens at every update since then.
What I do then is
Wiping cache and system, install lineage-os from the lineage update directory, install gapps reboot.
Data and all programs are still there with all of there setting except permissions. So I have got to start more or less every app to grant their permissions and the system is more or less back to normal.
Any idea how to fix that or where to get some more information what is happening during startup that the system cannot settle?
Greez2all
Tweety
Device variant: XT19121-2 James
Chipset: MSM8920
After repeated failed flashes I am on stock firmware using this guide. Phone boots and works normally right now, but I can't seem to flash any Custom ROMs on to my phone. I was using this post to flash Lineage OS 15.1, which worked successfully at first, but the WiFi wasn't working so I reflashed it. It still didn't work so I did it again, wiping Dalvik/Cache too. After the second flash attempt, my phone began to only flicker on and off. I made sure to always clean flash, factory resetting, wiping Cache and Dalvik, even formatting data, but no matter what I do it doesn't work. Also attempted other GSI images (arm, A-only) like AOSP, ResurrectionRemix and phhusson's Lineage OS 15.1 But they all failed too. I am using TWRP for James v 3.3.1 although I did also try other TWRP images like v 3.2.1 . But it makes no difference. Also used Magisk v19 like some guides suggested but whether I have Magisk or not, it doesn't work. Even made sure to push the fstab.qcom file to /vendor. Anytime a Custom ROM is flashed whether zip or GSI img it goes past the initial "bad key" or "N/A" screen and starts flickering on and off. Bootloader and TWRP works fine, but that's about it. Everytime a flash fails I go back to stock firmware (which always works) and try another ROM. I wonder why the first attempt worked but doesn't anymore even if I mirror the exact steps I took from stock. If anyone has any solutions I would be really grateful. Let me know if you need any more information.
have you taken any recent OTA updates?
mikeshutte said:
have you taken any recent OTA updates?
Click to expand...
Click to collapse
Nope. Still on the 8.0.0 version the stock firmware comes in.
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
---------- Post added at 10:09 PM ---------- Previous post was at 09:59 PM ----------
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
I also just noticed you are using the latest version of TWRP 3.3.1. I'm not sure if you originally rooted and installed TWRP with the original patched version by Cody or not, but if so make sure with the new version that you format your data partition to f2fs. As this will ensure correct mounting of the data partition.
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
I am having the same issue
Using XT1921-1
Latest TWRP
Have tried LOS 15, LOS 16, AOSP 8.1, AOSP 9.0
Have tried flashing in fastboot and TWRP
Have tried every combo of wipe/factory reset/format data and magisk flash possible
have tried stock recovery, have tried no verity, have tried stock boot.img
nothing works. only able to produce powered on (black and blank) screen that turns on and off for a minute before returning to bootloader
PLEASE HELP
think i might need a 8.0 GSI but cant find one anywhere
I eventually got RR to boot on the james xt-1921-3 I installed XT1921-3_JAMES_T_MPCS_8.0.0_OCPS27.91-150-5-1-3_cid21 as a base, then used boot and vendor partitions from JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC and it finally worked.
tkhan7916 said:
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
Click to expand...
Click to collapse
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Download the file from this post https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 , then using fastboot, flash the vendor and boot img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
then boot into recovery and flash the file from that post to disable dm-verity and force encrytion, after that flash magisk, then reboot to bootloader, at command prompt-
fastboot erase userdata
fastboot erase cache
fastboot reboot
that should get you booted - profit
mrbox23 said:
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Click to expand...
Click to collapse
Do you still have that back up by any chance and could ypu send it to me?