Database Users

Soft-Bricked, no access to recovery.... HELP!

Hey everyone.
I'm really hoping someone can help me. I just got my Redmi 2 Prime today, and before even properly setting it up I had rooted it. It wasn't long before I decided to try a different ROM. I decided on Resurrection Remix and TWRP recovery, both of which I flashed an ran flawlessly. RR booted up, everything was great.
I then tried flashing SuperSU again, after installing RR. Flashing the .zip file resulted in a boot loop, with no access to recovery, only fastboot.
What I've tried (with no success):
- Re-flashing TWRP (through Fastboot).
- Flashing CWM instead (through Fastboot).
- Flashing stock recovery (through Fastboot).
None of these have proven successful..... Can anyone give any advice on how to get out of this mess? I hardly feel up for having to take my phone into a shop without even having had it for 24 hours.....
TIA!

Fastboot flash Redmi 2 ROM. Download ROM file from MIUI forums and read the instructions there. Go to this link http://en.miui.com/a-234.html

i dont know if this comes at the right time,since fastboot is accesbile ,boot into fastboot, and flash recovery into boot(this may sound foolish but you can do it)
fastboot flash boot recovery_twrp.img
reboot,you will be taken into twrp
you can take a backup here,
now wipe all and flash the ROM.zip
anfd it should all work fine

I had the same problem when I switched from MIUI 8 4.4Kitkat to CM13 6.0
But I was able to solve it without fastboot.
RessurectionRemix and most roms esepecially CM based have "built-in" superSU manager.You just have simply to re-enable it on the developer settings.No need to flash supersu.zip,it would just make things worse.Download Flashify to boot in TWRP manually since flashing different ROMs will temporarily remove the TWRP(doing the button combination wouldn't boot into recovery,instead bootloop like you mentioned).
Then I was able to perform a restore on stock MIUI 8.
You have to download Flashify in order to manually force the phone to boot in recovery mode,since doing to volume up+power wouldn't let you.
I don't know if this is because my TWRP version only supports KitKat....or switching from 4.4-6.0 is a big gap.

Thanks for the responses!
I ended up solving the issue, though there wasn't really an issue to begin with. Turns out the button combination to enter recovery is different than stock (both volume buttons and power), though I did re-flash to the latest version of TWRP.
I'm now running Resurrection Remix without flaws!
But yeah, I realize now that CM based ROMs have a baked-in SU manager, it was foolish of me to flash the file without doing proper reading up beforehand!

Xiaomi Mi A1 Bricked, inifnite loop, I really don't know what's happening :( HELP

Hi, I have owned my Xiaomi Mi A1 like 5 days ago, and after a day I had it in my hands I rooted the device with Magisk 14.1 in TWRP, well, after I day I rooted the phone the update of oreo just realesed and my cellphone was avalible to install it, so I decided to unroot my phone, and there is where the ALL the problem started... Seems like when I flashed Magisk it didin't make a backup of the original boot.img so when I flashed the magisk uninstaller it didn't boot into the phone, it sent me to recovery again, so I tried installing the Magisk installer again and it let me boot.
After watching that I tried to flash the latest ROM in MiFlash but it just didn't do nothing, it flashed in 1 second and nothing happened to the phone.
Yesterday after all of that happened I tried to update the phone manually while rooted with TWRP, I found a backup of oreo of TWRP, so I restored that backup in TWRP and it booted me to oreo finally, after booting it to oreo I decided to go back to TWRP to restore my data backup of Nougat to restore all my apps and that stuff but when I booted into recovery it asked for decrypt my storage (as always), so I tried to decrypt it with the pattern I always used before and it just didn't let me, it just failed I don't know why, I booted into the system again trying to remove that stuff but it just didn't let me, the button to remove it was unavalible, it just let me remove my pattern to unlock the phone, so I removed it to see if it would work and it just make the things worse, I booted into recovery again and it didn't let me again, so I tried to boot into system AGAIN and it just didn't let me, just infinite loop, and recovery just removed, so I booted into recovery with fastboot mode and it didn't ask me for any decryption, it just let me in, but without mounting my internal storage, it just didn't, I tried to wipe the data option and after that it worked again, internal storage appeared again, after it I flashed the recovery into both slots.
Well, the last thing I did is restore the backup of oreo again that I found in XDA, but it just give me infinite loop, it's been like half of hour or more "booting", I'm so frustated and worried about this, tell me that there is a solution for this, the phone is literaly new, just five days with it... That version of magisk literally ruined my phone, lol

Ok mate, I suggest you go back to the last factory fastboot Xiaomi source. You flash this with the MiFlash tool.
The first file you need is the latest fastboot rom. This is in the tgz/tar format.
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
Extract this tgz and the subsequent tar file so that you get a directory (containing .bat files and an image folder).
Download MiFlash2017-7-20-0.zip - it must be this version.
Get your phone into fastboot mode with at least 25% battery charge.
Follow the instructions to use MiFlash here https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548
Good luck!

TWRP install impossible, phone doesn't make it past fastboot splash screen

Hey guys,
I just oem unlocked my new 6T and have access to the bootloader. As I try to install TWRP with
HTML:
fastboot boot imagename.img
my computer says that it pushes the image just fine, but my phone restarts and then never makes it past the fastboot splash screen instead of loading up TWRP.
I was following the fajita (6T) instructions from the lineage OS website.
The first time I did it it worked, but following the instructions on installing lineage and telling me to wipe and format data, both the recovery seems to be gone and i cannot fastboot boot into TWRP.
Can you help?

Seems the same with what i experienced. Have you tried installing a fastboot rom? I had my oneplus 6t bootlooped into fastboot mode even if i try to turn it off, it just boots back automatically to fastboot mode. Last resort was to flash a fastboot rom. That worked for me.

thalesian2020 said:
Hey guys,
I just oem unlocked my new 6T and have access to the bootloader. As I try to install TWRP with
HTML:
fastboot boot imagename.img
my computer says that it pushes the image just fine, but my phone restarts and then never makes it past the fastboot splash screen instead of loading up TWRP.
I was following the fajita (6T) instructions from the lineage OS website.
The first time I did it it worked, but following the instructions on installing lineage and telling me to wipe and format data, both the recovery seems to be gone and i cannot fastboot boot into TWRP.
Can you help?
Click to expand...
Click to collapse
What TWRP version are you trying to install?

jp0469 said:
What TWRP version are you trying to install?
Click to expand...
Click to collapse
I tried 3.3.1.1. and 3.2.3.0.

What you are describing, I'm going to assume you are trying to install Lineage 17. You can't install TWRP if you are going Android 10, at least that's the conclusion I've come to at this point in time. It will fail to boot or end up in crash dump mode every time you try and enter recovery if you are on a custom ROM. If you are on Android 9, it's not an issue. I believe it's OK stock as well, but I don't know haven't tried, haven't been stock in a long time.
For LOS 17, only boot the TWRP image, never boot to recovery, never run the TWRP installer. You will likely still have to format data.
I have a post here, from when I had a similar issue. (instructions)
You'll notice the OmniRom instructions don't mention installing TWRP, only booting it.
Once I was in your spot, I always went back to stock using the fastboot ROM, installed TWRP, updated (still using TWRP), then started over with my install.

Well no, i was actually trying to install Lineage 16, which is Android 9 I believe.
The problem for me is that I do not get to the point where TWRP opens after "fastboot boot"ing it. So I understand, I should use a fastboot stock ROM? Is there such a thing? Where would I find it? Or would it be an OnePlus Oxygen ROM that I can fastboot?

Quickest way to start over:
To get back straight your gonna need to access a Windows PC, and run the MSM tool. Make sure you install both OnePlus and Qualcomm drivers. ( Don't wait for Windows, just pre install the drivers) here are some links. Not my work. Please be sure to thank the developers for creating and hosting these tools ?
MSM Tool:
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
OnePlus Drivers:
https://androidfilehost.com/?fid=11410963190603879743
Qualcomm drivers:
https://androidfilehost.com/?fid=11410963190603879743

thalesian2020 said:
Well no, i was actually trying to install Lineage 16, which is Android 9 I believe.
The problem for me is that I do not get to the point where TWRP opens after "fastboot boot"ing it. So I understand, I should use a fastboot stock ROM? Is there such a thing? Where would I find it? Or would it be an OnePlus Oxygen ROM that I can fastboot?
Click to expand...
Click to collapse
Were you on Android 10 before (OOS)? That will do that. LOS 16 is Android 9 and should have no problems installing TWRP or booting to it.. For LOS 16 I'd go back to 9.0.17, then install LOS 6T.
I posted these LOS install instructions a long time ago for another user.
Remember the MSM Tool will relock your bootloader so if something goes wrong the MSM Tool is your only choice. That is why it is always the last thing I resort to.
Thread to get Fastboot stock Roms if you want to try that route first.

Hey guys,
thank you so much for all your help. I've managed to use mauronofrios workaround here on xda to put my phone in a 9.0.17 state again (no idea what i had originally), and this way i could fastboot the twrp image again. so that worked fine, but so far flashing lineage hasnt worked, for whatever reason it seems to boot into a lineageos kind of recovery only (which i didnt even know existed).
So i guess in terms of this thread the problem is solved. Thank you again!

thalesian2020 said:
Hey guys,
thank you so much for all your help. I've managed to use mauronofrios workaround here on xda to put my phone in a 9.0.17 state again (no idea what i had originally), and this way i could fastboot the twrp image again. so that worked fine, but so far flashing lineage hasnt worked, for whatever reason it seems to boot into a lineageos kind of recovery only (which i didnt even know existed).
So i guess in terms of this thread the problem is solved. Thank you again!
Click to expand...
Click to collapse
Did you see my Lineage install instructions above? LOS installs its on Recovery when you flash the ROM. When om Android 9, boot TWRP, flash the TWRP installer, reboot to Recovery, install LOS 16, flash the TWRP installer again (replaces the LOS recovery that was installed), reboot to Recovery, install gapps / magisk if desired, reboot.
Read my instructions post though, the first time install is different, as you need LOS on both slots. Updating is different as well, its much easier.
It should go smoothly.

OhioYJ said:
Did you see my Lineage install instructions above? LOS installs its on Recovery when you flash the ROM. When om Android 9, boot TWRP, flash the TWRP installer, reboot to Recovery, install LOS 16, flash the TWRP installer again (replaces the LOS recovery that was installed), reboot to Recovery, install gapps / magisk if desired, reboot.
Read my instructions post though, the first time install is different, as you need LOS on both slots. Updating is different as well, its much easier.
It should go smoothly.
Click to expand...
Click to collapse
Do I need to be on Android 9 Stock when I start that process? What I did was boot into TWRP, flash TWRP installer, reboot into recovery, then format and wipe ALL partitions (except USB), then reboot into recovery again and then flash LOS, flash TWRP, reboot into recovery, flash LOS, flash TWRP, reboot system. Still no luck...

thalesian2020 said:
Do I need to be on Android 9 Stock when I start that process? What I did was boot into TWRP, flash TWRP installer, reboot into recovery, then format and wipe ALL partitions (except USB), then reboot into recovery again and then flash LOS, flash TWRP, reboot into recovery, flash LOS, flash TWRP, reboot system. Still no luck...
Click to expand...
Click to collapse
Wiping, Dalvik / ART, System, and Vendor is generally a bad idea. You can do them in certain situations, this isn't one of those situations you should be wiping those though. Factory reset, means the slider on the main page of the wipe screen that says swipe to factory reset, format data is the button that says format data. Don't do anything extra. If you did, yeah I would go back to 9.0.17 using the fastboot rom again, that will put everything back on both slots.

like OhioYJ stated, don't use advanced wipe. re-run the msm tool. Then follow his instuctions. You shouldn't need to preform any manual data wiping. The process of flashing will do everything required. looks like you're almost there

Thanks guys. I will try it out and let you know.
Edit: So I finally managed to properly install LOS - OhioYJ, your instructions worked! I installed 9.0.17 and went from there without wiping any additional partitions.
One questions remains: in your instructions you mention that after installing LOS once, you can update LOS as normal and you mention doing it via the recovery with flashing TWRP or GAPPS later again. Is it possible to do the update via the normal update function of LOS as well? Or will that overwrite TWRP?
You guys are awesome. Thank you so much for your help!

I seem to be stuck on the fastboot screen as well. Being on a MAC, anytime i try to do something in fastboot it goes straight back to the fastboot screen. I Thought I was on Android 10.0 trying to install recovery for that lead to bootloop of fastboot, tried using the Pie recovery and same thing. I am open to suggestions.
Thanks.

OhioYJ said:
What you are describing, I'm going to assume you are trying to install Lineage 17. You can't install TWRP if you are going Android 10, at least that's the conclusion I've come to at this point in time. It will fail to boot or end up in crash dump mode every time you try and enter recovery if you are on a custom ROM. If you are on Android 9, it's not an issue. I believe it's OK stock as well, but I don't know haven't tried, haven't been stock in a long time.
For LOS 17, only boot the TWRP image, never boot to recovery, never run the TWRP installer. You will likely still have to format data.
I have a post here, from when I had a similar issue. (instructions)
You'll notice the OmniRom instructions don't mention installing TWRP, only booting it.
Once I was in your spot, I always went back to stock using the fastboot ROM, installed TWRP, updated (still using TWRP), then started over with my install.
Click to expand...
Click to collapse
Twrp is working fine with Android 10, using mauronofrio version and magisk 20.2

callumbr1 said:
Twrp is working fine with Android 10, using mauronofrio version and magisk 20.2
Click to expand...
Click to collapse
Yeah it starting to seem like it maybe isolated to Lineage. You cant install TWRP with LOS 17. Someone else mentioned in the Omni thread that it worked. This thread is about Lineage, but that should be clarified, or clearer.

Only booting into fastboot (repaired, solution found). I want to know the rootcause.

Hi all,
Since a couple of days I was able to unlock the bootloader on my Mi 9T Pro device. I managed to install TWRP recovery via fastboot and then the vendor, Lineage, other kernel, Magisk as zip via TWRP recovery.
It worked fine, until at one moment I rebooted and suddenly it started only the fastboot. No OS anymore, but also no recovery. Flashing TWRP again via fastboot worked, but recovery was not loading and it kept booting into fastmode.
I repaired it via the Xiaomi Flashtool, by flashing the Global rom again. System flashed, MIUI booted. After I could unlock bootloader again, flash recovery, and TWRP was also loading again.
Suddenly, I still don't know exactly why, it again started booting only to fastboot. Flashing the official ROM via the Xiaomi tool repaired the device again. Then I continued again with TWRP + vendor/LineageOS/Magisk/kernel. Works!
Now my device runs LineageOS 17.1, still has TWRP working, is rooted, has updated kernel and all seems fine. However I am scared that this strange "only booting to fastboot and needs complete wipe/reinstall by installing official Rom via Xiaomi tool" again. (It means, at any moment you will lose your whole device, setup, configuration, applications and data...)
Now I was wondering: can anyone explain me what is the rootcause for this "only booting to fastboot" bug?
Am I doing something wrong?
Is it perhaps caused by a kernel or magisk bug in the version I use?
Did I flash the wrong TWRP? (I tried official and some version for Mi 9T Pro found in this forums).
I don't see it yet, I hope someone knows what causes this issue. Then I know what to be careful for.
What causes this bug?
Thanks in advance!
***EDIT: Oops! I accidentally posted this in the Mi 9T forum instead of the Mi 9T Pro. Perhaps the issue and answer is the same, however perhaps a mod can move this to the Q&A subforum of the Mi 9T Pro? Sorry***

This usually happens if you wipe system and/or vendor partitions and then reboot (at least that's how I got this issue). For some reason if those are empty or invalid, the device gets stuck to fastboot and can't even boot to TWRP (neither directly or using fastboot boot).
To avoid that just never reboot (even reboot to recovery) right after wiping system/vendor, always make sure a ROM is installed first (or just don't wipe them since usually the ROMs take care of it before the install anyways).

Thank you!
Indeed, even TWRP did not load, exactly as you describe.
So that means for some reason the system or vendor partition got wiped or corrupted. Thanks, I will think why that might happened and where to be extra careful for.

[Solved] It's impossible to install LineageOS on my 6T.

Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.

dequadim said:
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
Click to expand...
Click to collapse
Did you get twrp installed? Wipe data by typing yes after flashing?

dequadim said:
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
Click to expand...
Click to collapse
You can follow this. If you want to install lineage os and want Google service make sure follow the "non gapp version" under installation method.
Havoc Flashing Notes for OnePlus 6 /6T from OOS 11 [Using TWRP Recovery]
1. Clean Flash : 2. Dirty Flash 3. Update oos base 1. Clean Flash : 🔊 Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; we're going to format the data partition and you're going to lose everything from internal storage. Basic requirements ○...
telegra.ph

Thanks for replies.
I must add this point: my 6T has OxygenOS v11.1.1.1; maybe this the reason of the problem? Maybe OnePlus did something that screws any modding attempt?
I simply followed the instructions found on YouTube, in the LineageOS' Fajita page and installed TWRP, but my 6T went in "Qualcomm Crashdump" and TWRP was not working → phone bricked.
Then I've tried installing, in the same way via ADB and Fastoot commands the Lineage Recovery, that has worked but when I tried to boot system, keeping OxygenOS, the phone went in bootloop.
So where is the error/fault?
Please, help me with a step-by-step tutorial that lead me to successfully install TWRP and LineageOS on my 6T.

dequadim said:
Thanks for replies.
I must add this point: my 6T has OxygenOS v11.1.1.1; maybe this the reason of the problem? Maybe OnePlus did something that screws any modding attempt?
I simply followed the instructions found on YouTube, in the LineageOS' Fajita page and installed TWRP, but my 6T went in "Qualcomm Crashdump" and TWRP was not working → phone bricked.
Then I've tried installing, in the same way via ADB and Fastoot commands the Lineage Recovery, that has worked but when I tried to boot system, keeping OxygenOS, the phone went in bootloop.
So where is the error/fault?
Please, help me with a step-by-step tutorial that lead me to successfully install TWRP and LineageOS on my
Click to expand...
Click to collapse
OnePlus definitely didn't do anything to make it harder. You need to fastboot boot twrp.img then flash the twrp installer zip. I'll attach both In next post. Reboot to recovery. Then install OOS, twrp installer, reboot to recovery. Install oos again, twrp installer again, reboot to recovery. Now install lineage, twrp installer, reboot to recovery. Install lineage again, twrp installer again, reboot to recovery. Factory reset and wipe data by typing yes. Boot to system

The img is for fastboot boot
The zip is for installing in twrp

Thanks for your reply.
I'm still wondering how to speed up the boot.

dequadim said:
Thanks for your reply.
I'm still wondering how to speed up the boot.
Click to expand...
Click to collapse
If everything is installed correctly it won't take long to boot

Brettroth said:
If everything is installed correctly it won't take long to boot
Click to expand...
Click to collapse
There is clearly something wrong, as my 6T's boot is slow.
Furthermore, the Recovery of the previous message is the one I downloaded three days ago and that made me go to the 6T in Qualcomm Crashdump.
I repeat my request: where can I find a safe and updated guide that explains how to install LineageOS without risk?

If you can't fastboot boot into that twrp on a11 without crash dumping there is something really wrong

If you can't fastboot boot into that twrp on a11 without crash dumping there is something really
dequadim said:
There is clearly something wrong, as my 6T's boot is slow.
Furthermore, the Recovery of the previous message is the one I downloaded three days ago and that made me go to the 6T in Qualcomm Crashdump.
I repeat my request: where can I find a safe and updated guide that explains how to install LineageOS without risk?
Click to expand...
Click to collapse
You sure you didn't try 3.6.0_9?

Clearing your cache might help with current boot. But once you install a new os everything will run smooth like it should

Thank you for the advice.
1) I've downloaded "twrp-3.6.0_9-0-fajita.img" and tried to install it several times, getting errors and then bricking my phone.
2) I have already cleared the cache several times from Recovery, without anything having changed; the two white dots on the boot screen continue to rotate 37 times around the red dot before the phone starts up and then works perfectly.
It occurred to me that the MSM Download Tool program uses a decrypted image of the original firmware; could this possibly be the cause of the long boot?

dequadim said:
Thank you for the advice.
1) I've downloaded "twrp-3.6.0_9-0-fajita.img" and tried to install it several times, getting errors and then bricking my phone.
2) I have already cleared the cache several times from Recovery, without anything having changed; the two white dots on the boot screen continue to rotate 37 times around the red dot before the phone starts up and then works perfectly.
It occurred to me that the MSM Download Tool program uses a decrypted image of the original firmware; could this possibly be the cause of the long boot?
Click to expand...
Click to collapse
That twrp version always will crash dump on a11. Use the one I sent

I followed these steps:
after having managed to make MSM Download Tool detect the phone in EDL mode, I proceeded by reinstalling OOS v9.0.13, after which I reconfigured the phone and restored the apps backup stored in my Google account.
Later, I don't remember the details well, I received the update notification for OOS v10 and later for OOs v11.1.2.2.
I don't remember exactly where the boot started to stretch, however this is more or less the process I followed to bring my 6T back to life.

Brettroth said:
That twrp version always will crash dump on a11. Use the one I sent
Click to expand...
Click to collapse
Are you sure that this TWRP will work without problems?
I've tried also with Lineage Recovery for Fajita, resulting with the 6T in bootloop :-(

dequadim said:
Are you sure that this TWRP will work without problems?
I've tried also with Lineage Recovery for Fajita, resulting with the 6T in bootloop :-(
Click to expand...
Click to collapse
I promise it works. I do t know what happened with your previous updating and msm tool but something sounds messed up. Just get twrp running and ease all your problems. Clean flashing and getting everything fresh

Brettroth said:
I promise it works. I do t know what happened with your previous updating and msm tool but something sounds messed up. Just get twrp running and ease all your problems. Clean flashing and getting everything fresh
Click to expand...
Click to collapse
Keep your finger crossed...

Another question: assuming I can install TWRP and make it working, LineageOS image must be copied in the 6T's internal SD and proceeding to install from TWRP?

dequadim said:
Another question: assuming I can install TWRP and make it working, LineageOS image must be copied in the 6T's internal SD and proceeding to install from TWRP?
Click to expand...
Click to collapse
Or you could use USB OTG. Or a PC and use adb sideload