Develop Bugs

[TUTORIAL][ROM][CM14.1] OFFICIAL CyanogenMod 14.1 for Android One 2nd Gen on WF Swift

Due to a number of reports of people bricking their devices, I have removed this tutorial.
For instructions to get your device unbricked, please read here.
I'm terribly sorry for the inconvenience.

Hello,
thanks for sharing, but do you also know a way back to wileyfox stock rom? I don't think a twrp backup holds all nand data. When flashing GM4G rom, you also flash ie. modem partition, and I don't think that this is covered by a twrp backup.
bye...DonQ

Seed has a TWRP patched for cm updater. I'm a seed user but I prefer crackling roms

DonQuichotte said:
Hello,
thanks for sharing, but do you also know a way back to wileyfox stock rom? I don't think a twrp backup holds all nand data. When flashing GM4G rom, you also flash ie. modem partition, and I don't think that this is covered by a twrp backup.
bye...DonQ
Click to expand...
Click to collapse
Flash the factory image.

[email protected] said:
Seed has a TWRP patched for cm updater. I'm a seed user but I prefer crackling roms
Click to expand...
Click to collapse
I can't find a link for the Seed TWRP patched for CM Updater. Can you share it?

seb5049 said:
I can't find a link for the Seed TWRP patched for CM Updater. Can you share it?
Click to expand...
Click to collapse
Yeah I would like to know too

VivaLaVent said:
Flash the factory image.
Click to expand...
Click to collapse
I'm not sure this is enough, cause with the GM4G rom some partitions (.img) get flashed, that are not in the swift factory rom...oem.img, devinfo.bin. I think about switching to seed, cause no more nigthlies and seed has official CM14.1 already. But there has to be a bullet-proof way to return to stock...just in case.
bye DonQ

twrp patched by Arvin Quilao
VivaLaVent said:
Yeah I would like to know too
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=457095661767122264 i use this and updated via cm updater twice with no problem....

[email protected] said:
https://www.androidfilehost.com/?fid=457095661767122264 i use this and updated via cm updater twice with no problem....
Click to expand...
Click to collapse
Okay so I'm guessing updating with CM updater does work, but the recovery you linked is not the latest version of TWRP.

Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....

Twrp version status...
VivaLaVent said:
Okay so I'm guessing updating with CM updater does work, but the recovery you linked is not the latest version of TWRP.
Click to expand...
Click to collapse
Yeahhh it isnt the latest i know. The latest is 3.0.2-1 but isnt patched for cm ota updates like that shared by me later. The dev stated the official version patched from twrp website will come later. Using it dnt create any prblm.

piromanneo said:
Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....
Click to expand...
Click to collapse
I'm having the same problem.

seb5049 said:
I'm having the same problem.
Click to expand...
Click to collapse
I'm starting to think I made an error, can anyone confirm they successfully used this method?

VivaLaVent said:
I'm starting to think I made an error, can anyone confirm they successfully used this method?
Click to expand...
Click to collapse
I was unsuccessful with your method. I even tried two times then I gave up and restored my backup with cm-13

How is it running on CM 14? Is there noticeable lag and such?

If you want CM14, try crDroid, it works great. I'm using it for two weeks now, no FC errors, good battery performance, no serious lags.
When I read the bricks of some users trying to flash a ROM that is meant for a clone with ALMOST the same hardware - I won't try this.

I am considering doing this update. But I have an issue. Since Android 6 has integrated sdcards, I had to reformat the sdcard on every update which is a pain in the ass. I using mixed mode. Is there any way to do an update which allows to reintegrate the sdcard without reformatting the sdcard?

piromanneo said:
Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....
Click to expand...
Click to collapse
I seem to have the same problem as you, device doesn't respond, no boot or whatever.
Could you link me to the solution you used to unbrick the device?

Due to a number of reports of people bricking their devices, I have removed this tutorial.
For instructions to get your device unbricked, please read here.
I'm terribly sorry for the inconvenience.

LG G4 keeps booting in recovery mode (TWRP)

Hi,
I made a CM14 update yesterday, but since then, my phone boots in recovery mode. I tried to reinstall TWRP, in current and previous versions, and other roms (I can flash), but nothing works; each time I reboot, TWRP appears...
Any hint ?
Thanks very Much !

gdoucou said:
Hi,
I made a CM14 update yesterday, but since then, my phone boots in recovery mode. I tried to reinstall TWRP, in current and previous versions, and other roms (I can flash), but nothing works; each time I reboot, TWRP appears...
Any hint ?
Thanks very Much !
Click to expand...
Click to collapse
Try to install my latest BETA (check my signature)

steadfasterX said:
Try to install my latest BETA (check my signature)[/QUOT
Hi, thanks for your answer. I tried, but it still reboots on TWRP... (tried to install AICP).
There's an error message when installing :
patching system image unconditionnally
E:unknown command [log]
But it keeps going on with "dectected filesystem ext4 for /dev/boot [...]
Then it reboots in recovery...
Click to expand...
Click to collapse

gdoucou said:
steadfasterX said:
Try to install my latest BETA (check my signature)[/QUOT
Hi, thanks for your answer. I tried, but it still reboots on TWRP... (tried to install AICP).
There's an error message when installing :
patching system image unconditionnally
E:unknown command [log]
But it keeps going on with "dectected filesystem ext4 for /dev/boot [...]
Then it reboots in recovery...
Click to expand...
Click to collapse
Please try build 186
Click to expand...
Click to collapse

dont work for me same Probleme

TooThPicK said:
dont work for me same Probleme
Click to expand...
Click to collapse
Try my latest beta and if that is not working build 186
And which nightly causes that problem?

i think its not the recovery i test the cyanogen and this dont work
test installing stock but dont work
testet both not working
no Rom is working evrytime its boot to recovery

TooThPicK said:
i think its not the recovery i test the cyanogen and this dont work
test installing stock but dont work
testet both not working
no Rom is working evrytime its boot to recovery
Click to expand...
Click to collapse
Which cm version? tell exact build date.
Try to reflash stock kdz

Is there a way to Flash kdz from fastboot or recovery lgup dont find my device
ok i find the download mode now lgup find my device i downloading 20g and test

The issue is due to change in Google code not being compatible with TWRP.
I had the same issue, I flashed stock ROM with LGUP and then flashed CM14.1 after that.
Once your back up and running you can't use the in built updater, you have to download the update, manuay reboot to recovery and then flash.

Lgup dont find my device i only have recovery and fastbood

ceanth said:
The issue is due to change in Google code not being compatible with TWRP.
I had the same issue, I flashed stock ROM with LGUP and then flashed CM14.1 after that.
Once your back up and running you can't use the in built updater, you have to download the update, manuay reboot to recovery and then flash.
Click to expand...
Click to collapse
The change in Google code was the reason for one of the beta series I made. I was able to fix that in twrp even when this is no twrp issue. The internal updater worked fine afterwards when using any build after 15 of dec while using my latest beta.
That's why I ask several times what cm build they used (both do not answered this yet).
This is important so I can reproduce the issue and may can release a new twrp workaround if possible.
.

TooThPicK said:
Lgup dont find my device i only have recovery and fastbood
Click to expand...
Click to collapse
Not sure dude, best to post in the dedicated TWRP or cm14.1 thread.

its fixt thank you for your help the trick is turn off the g4 hold the + button and plugin the cabel now the device comes to downloadmode and now lgup is working
---------- Post added at 02:30 PM ---------- Previous post was at 02:28 PM ----------
steadfasterX said:
That's why I ask several times what cm build they used (both do not answered this yet).
This is important so I can reproduce the issue and may can release a new twrp workaround if possible.
.
Click to expand...
Click to collapse
on my is the nigtly from 23.12

I got the same problem booting permanently in TWRP.
Flashing the build (02.12.) I had before also doesn't work.
Some kind of tips here?

xXfreshXx said:
I got the same problem booting permanently in TWRP.
Flashing the build (02.12.) I had before also doesn't work.
Some kind of tips here?
Click to expand...
Click to collapse
Install my latest beta. I know that this do not solve the problem but then after flashing it try to boot into system. This will fail. Then pull the recovery log and provide it on http://paste.omnirom.org
If you don't know how to get that log it is easy. Check my FAQ #4 A.
http://forum.xda-developers.com/showpost.php?p=68249027&postcount=3
.

steadfasterX said:
Install my latest beta. I know that this do not solve the problem but then after flashing it try to boot into system. This will fail. Then pull the recovery log and provide it on http://paste.omnirom.org
.
Click to expand...
Click to collapse
Thanks for your reply
https://paste.omnirom.org/view/6e5948df

xXfreshXx said:
Thanks for your reply
https://paste.omnirom.org/view/6e5948df
Click to expand...
Click to collapse
Hm . This is really after a boot into system??...
Ok as I cannot see relevant data pls do the same again but with build 186 now. Provide the log again. The reason is that this build handles the bootloader commands in an other way and I may see then what I wanna see.
Thx
.

Hm . This is really after a boot into system??...
Ok as I cannot see relevant data pls do the same again but with build 186 now. Provide the log again. The reason is that this build handles the bootloader commands in an other way and I may see then what I wanna see.
Thx
.
Click to expand...
Click to collapse
Here you are.
https://paste.omnirom.org/view/594df4ce

xXfreshXx said:
Here you are.
https://paste.omnirom.org/view/594df4ce
Click to expand...
Click to collapse
Hm the reason for that reboot lays somewhere else...
Please tell me exactly what you had done to produce that loop:
Which exact version of cm installed before upgrading?
Upgraded with internal cm updater or by flashing new zip in twrp?
The above would help me to reproduce the issue.
Besides the short questions above it would be great if you could test 2 things for me and if not skip to 3 (if you're in hurry):
1. The hw key combo test
2. The force twrp test
3. Last resort LG up
1. The hw key combo test
Flash the latest beta twrp and reboot into this twrp
Create a full backup if not already done so!!!
Power off the device and pull out the battery
Use the hardware key combo to get into factory reset screen (press vol down + power and keep them pressed. plugin battery. Wait until you see the LG logo and then release only the power button for 1 sec then press it again and keep both pressed until you see the factory reset screen)
Follow through this process and twrp will showing up without resetting anything
Grab the recovery log and paste it again
Then try to reboot to system
2. The force twrp test
If the first method hasn't worked it would be great to see the log anyways but then try the the following:
Boot into twrp (doesn't matter how for this test)
Flash again the latest twrp beta with twrp itself (choose img button at the bottom) and now when getting asked flash it to BOOT partition! Yes this is no problem or causes any damages. Just do it.
Then choose reboot into system and twrp will popup again (but now it starts from boot partition)
Now install the cm version of your choice or any other rom
Do NOT reboot yet
before rebooting grab the recovery log again and paste it again
3. LG up
If the above does not work and as I believe you need your device back soon the best bet would be do a full backup with the latest twrp beta version. Then use LG up to flash stock kdz again to get a working device.
.

Stuck with No ROM Installed

FOR SOLUTION READ POST:
[SIZE="5"]https://forum.xda-developers.com/showpost.php?p=71007646&postcount=6[/SIZE]
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
https://forums.*neplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip
OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip
oxygen-os-3.2.5-fastboot-flashable.zip
twrp 3.0.3
https://forum.xda-developers.com/showthread.[/CODE]php?t=2588979
Click to expand...
Click to collapse

applsaus said:
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
Click to expand...
Click to collapse
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom

try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads

Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.

Puddi_Puddin said:
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Click to expand...
Click to collapse
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
abhi0502 said:
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
Click to expand...
Click to collapse
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Good idea, I'll put ur idea for the next try

applsaus said:
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
Good idea, I'll put ur idea for the next try
Click to expand...
Click to collapse
Then it's a twrp issue. I'm currently in Bluspark v16 so

Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.

Puddi_Puddin said:
Then it's a twrp issue. I'm currently in Bluspark v16 so
Click to expand...
Click to collapse
ghostofcain said:
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Click to expand...
Click to collapse
I flash twrp bluspark as @Puddi_Puddin suggested and flashing Freedom OS. After that, I restore my data using my last Nandroid backup, then the bootloop comes again. Tried it several times using TWRP Bluspark with different ROMs, still no luck. So I suggest, there's nothing I can do to restoring my phone's data.
I read across the XDA forums and Oneplus forums that some people had similar issues for me, and they suspected something's wrong about corrupted partition, not because twrp version. And I also had tried flashing a few ROM in the past using the same TWRP 3.03 version without any problems. Strange.
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread

applsaus said:
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
Click to expand...
Click to collapse
And, what was the solution ?

Restarting from Zero I guess.

Donglip said:
And, what was the solution ?
Click to expand...
Click to collapse
This:
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
emuandco said:
Restarting from Zero I guess.
Click to expand...
Click to collapse
Better than not starting at all, at least.

Confused about TWRP

I got the redmi note 8 gingko 4/64 and wanted to ask which TWRP is actually the "best". Installed the "original" and it seems to work fine, but read here and there that the one of mauronofrio is recommended. What would you suggest?

mankokoma said:
I got the redmi note 8 gingko 4/64 and wanted to ask which TWRP is actually the "best". Installed the "original" and it seems to work fine, but read here and there that the one of mauronofrio is recommended. What would you suggest?
Click to expand...
Click to collapse
Follow this guide to see why twrp fails in some cases and the solution to overcome twrp issue.

the_weird_aquarian said:
Follow this guide to see why twrp fails in some cases and the solution to overcome twrp issue.
Click to expand...
Click to collapse
am using orangefox.. does it say why kernel and modules work. but lately i have a flashable zip of ringtones and they dont appear in phone or in folder.
---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------
mankokoma said:
I got the redmi note 8 gingko 4/64 and wanted to ask which TWRP is actually the "best". Installed the "original" and it seems to work fine, but read here and there that the one of mauronofrio is recommended. What would you suggest?
Click to expand...
Click to collapse
i think original or stock from twrp doesnt have other features example convert partition to f2fs. ect. other have all this. oreangefox have alot of features.

raptorddd said:
am using orangefox.. does it say why kernel and modules work. but lately i have a flashable zip of ringtones and they dont appear in phone or in folder.
Click to expand...
Click to collapse
You mean flashable zip is not shown in internal storage in orangefox menu from where we browse files to flash??

the_weird_aquarian said:
You mean flashable zip is not shown in internal storage in orangefox menu from where we browse files to flash??
Click to expand...
Click to collapse
if i flash kernel it works. if i flash magisk for root it works. i mean you boot into OS and kernel is installed and so is magisk. if i flash a zip that has ringtones they dont install they do not show up in phone ringtones or in folder its like its not placing the files to system partition. but if i use official twrp flashable zips do install and show up in phone.. i have tried both oreangefox and pitchblack both wont flash those zips i mentioned.
seems like something got messed up . i was in rn5 whyred using orange fox.. then magisk 20.2 was released anad orangefox got update.. after that update it didnt install those zips.. then another update was released in a day. and still dont flash those zips. at that time i reverted to the old orangefox i had and that one worked.. so last friday i unlocked bootloader and encounter the same as in whyred orangefox doesnt install the zips i mentioned.
strange that no one has reported already.

raptorddd said:
if i flash kernel it works. if i flash magisk for root it works. i mean you boot into OS and kernel is installed and so is magisk. if i flash a zip that has ringtones they dont install they do not show up in phone ringtones or in folder its like its not placing the files to system partition. but if i use official twrp flashable zips do install and show up in phone.. i have tried both oreangefox and pitchblack both wont flash those zips i mentioned.
seems like something got messed up . i was in rn5 whyred using orange fox.. then magisk 20.2 was released anad orangefox got update.. after that update it didnt install those zips.. then another update was released in a day. and still dont flash those zips. at that time i reverted to the old orangefox i had and that one worked.. so last friday i unlocked bootloader and encounter the same as in whyred orangefox doesnt install the zips i mentioned.
strange that no one has reported already.
Click to expand...
Click to collapse
hmm that seems weird. Did you create the zip yourself or downloaded from somewhere?

the_weird_aquarian said:
hmm that seems weird. Did you create the zip yourself or downloaded from somewhere?
Click to expand...
Click to collapse
created myself. been using for long time. and ginkgo official twrp does place the files in the folder and shows in phone ringtones.. weird very weird,

raptorddd said:
created myself. been using for long time. and ginkgo official twrp does place the files in the folder and shows in phone ringtones.. weird very weird,
Click to expand...
Click to collapse
My experience with self-made (and third party updater-zips) is, that you have to mount the system and vendor partitions manually before you install the updater-zip.
Have you tried this already? For me that's the way it works.

the_weird_aquarian said:
Follow this guide to see why twrp fails in some cases and the solution to overcome twrp issue.
Click to expand...
Click to collapse
I have read your guide very carefully and thanks for that! Don't get me wrong, but has nothing to do with my question. My device is encrypted and yet there has not been any problems with the original TWRP and encryption or something similar.
My question was if there are any known problems or issues with the original TWRP and is it for that reason necessary to change to another one like Orangefox or the one of @mauronofrio?

mankokoma said:
I have read your guide very carefully and thanks for that! Don't get me wrong, but has nothing to do with my question. My device is encrypted and yet there has not been any problems with the original TWRP and encryption or something similar.
My question was if there are any known problems or issues with the original TWRP and is it for that reason necessary to change to another one like Orangefox or the one of @mauronofrio?
Click to expand...
Click to collapse
Hi..if you read the guide then you might know by now the problem with official twrp is the bootloop in decrypted devices..you can't flash miui OTA with twrp...if you're on encrypted device with twrp then you have to flash full rom...other than that official twrp works just fine

mankokoma said:
My experience with self-made (and third party updater-zips) is, that you have to mount the system and vendor partitions manually before you install the updater-zip.
Have you tried this already? For me that's the way it works.
Click to expand...
Click to collapse
right i found that out yesterday after manually mountinf system partition it works.. but in many years ive never had to do it like this. it was just flash zip.

raptorddd said:
right i found that out yesterday after manually mountinf system partition it works.. but in many years ive never had to do it like this. it was just flash zip.
Click to expand...
Click to collapse
yeah, had this never before either until redmi note 5 and now 8
Any idea why you can't switch off the light in TWRP?

mankokoma said:
yeah, had this never before either until redmi note 5 and now 8
Any idea why you can't switch off the light in TWRP?
Click to expand...
Click to collapse
well orangefox on whyred happened after the latest 2 new updates.. then happens in ginkgo.
no none that i tried cant turn the screen off..if all are the same then is a problem that will stay or fix later i do not know. also kernels all are alike in kernel kcal is broken.. no sound control... i feel no big differnece with whyred.

raptorddd said:
well orangefox on whyred happened after the latest 2 new updates.. then happens in ginkgo.
no none that i tried cant turn the screen off..if all are the same then is a problem that will stay or fix later i do not know. also kernels all are alike in kernel kcal is broken.. no sound control... i feel no big differnece with whyred.
Click to expand...
Click to collapse
the only differences were the reasons I bought it: much better Camera and two SIMs plus sdcard... that's it and it feels good.

What you have to wipe for flashing this ROM?
Data, System, Vendor, Cache.
All of them, right?

TWRP fails to boot on Android 11, 'Error verifying the received boot.img: Invalid Parameter'

I successfully rooted the phone using Magisk, and looking at how to install LineageOS, I saw I needed TWRP first. I followed all the instructions, but when I use fastboot to boot twrp.img, I get the following error message, "Error verifying the received boot.img: Invalid Parameter". Searching for an answer, I saw there was an old issue with TWRP with the Pixel 3a XL and Android 10, but I found nothing more recent about Android 11.
I thought maybe I shouldn't have rooted the phone first, so I reflashed with the stock boot.img and tried TWRP again, but that doesn't solve it. Any idea how I can boot TWRP? Or is there a way to install LineageOS with TWRP? Thanks!
Build # RQ2A.2100505.002
TWRP image twrp-3.5.2_9-0-bonito.img

Twrp doesn't work currently for android 10+
You don't need it to install lineage, just flash the lineage recovery and follow the wiki install guide.
Install LineageOS on bonito | LineageOS Wiki
wiki.lineageos.org

If TWRP does not work on Android 10+ what are we doing about flashing custom roms? Booting the TWRP and then sideloading the ROM?
I need help. When I try to boot TWRP(assuming its possible) I get an error :invalid parameter, error verifying the boot image. I am on Android 11. Yes, Ive used the search function or else I would not have found this thread.
I do not want to flash lineage, but the instructions are vague in other ROM threads.

I just built a TWRP that works on Android 11. I wasn't sure how much interest there was in it, though, so I didn't bother posting it anywhere. I'll consider it once I clean up the source a bit.

Captain_Throwback said:
I just built a TWRP that works on Android 11. I wasn't sure how much interest there was in it, though, so I didn't bother posting it anywhere. I'll consider it once I clean up the source a bit.
Click to expand...
Click to collapse
Please post it! It would be greatly appreciated!

ncrawler said:
Please post it! It would be greatly appreciated!
Click to expand...
Click to collapse
I posted it on Telegram here: https://t.me/pixel3a/161825

Captain_Throwback said:
I posted it on Telegram here: https://t.me/pixel3a/161825
Click to expand...
Click to collapse
Thank You! I've been waiting for this!

I cant get your twrp and magisk to work together? I can only get one or the other working.

ncrawler said:
I cant get your twrp and magisk to work together? I can only get one or the other working.
Click to expand...
Click to collapse
Boot TWRP, copy image to device, use Install Image -> Install Recovery Ramdisk to install TWRP, then flash Magisk.apk.
I've done it a bunch of times and it works fine. Is that what you're doing?

Captain_Throwback said:
Boot TWRP, copy image to device, use Install Image -> Install Recovery Ramdisk to install TWRP, then flash Magisk.apk.
I've done it a bunch of times and it works fine. Is that what you're doing?
Click to expand...
Click to collapse
Done it about 10 times and never boots again

ncrawler said:
Done it about 10 times and never boots again
Click to expand...
Click to collapse
with or without lmza kernel

ncrawler said:
with or without lmza kernel
Click to expand...
Click to collapse
No idea what to tell you. It works for users in the TG group and it works for me. That's the exact process I'm using. You can alternatively try the Advanced -> Flash Current TWRP option and then flash Magisk and see what happens.

Thanks! I think I got it! Think I was using the wrong Magisk! I Guess I still have to use lmza kernel to pass integrity in magisk?

ncrawler said:
Thanks! I think I got it! Think I was using the wrong Magisk! I Guess I still have to use lmza kernel to pass integrity in magisk?
Click to expand...
Click to collapse
I have no idea about any specific kernel or integrity checks in Magisk. I only build TWRP.