Related
Hey fellas,
so I rooted my phone and tried to install some Magisk modules, but after rebooting it got stuck in the TWRP bootloop. So I flashed the Nandroid backup and it got stuck in the OOS boot animation. After that I tried reflashing OOS, but it didn't change anything, so I tried Lineage OS and now it won't even get past the Oneplus logo at the beginning and keeps restarting.
Thanks in advance
EDIT: when I flash the stock ROM through TWRP it installs normally, but then when I try to reboot it says there is no OS. So I flashed the stock OS to try adb sideload, but my pc says it cannot read the zip.
I also decrypted my phone through the OP5 Decrypt App, before the bootloop it worked for some time.
Of course I wiped everything before every action.
if you can bootup into recovery, try go into advanced and format data and system.
if you can't your last chance is using adb - flash a default rom.
Is it any different than wiping everything? Because it didn't do anything. I can access both twrp and fastboot so I guess it's not that bad
sounds like you went from unencrypted to an encrypted rom and your data is encrypted, or visa versa.
yep, it's vice versa, I used the OP5 Decrypt App after rooting. Is OP5 encrypted by default?
If you've tried the Android 8.0 Rom, just go to the official OP5 support site and download stock rom, flash it via ADB sideload if you can. (Don't forget to format data etc etc..) and restart from scratch.
Unlock BL if it's relock, then flash TWRP and go for a custom ROM. That's what I did, happened to me 2 days ago.f
EDIT : Oh you just flashed Magisk.. Well, try this anyway.
I tried flashing Lineage, but I can't install Oxygen
Ok, so apparently OOS boots up only after relocking the bootloader. And I had to make adb use more RAM to get sideload to work.
Hey guys,
I recently flashed Omnirom and after doing so, noticed I had no signal. After flash, reboot, or resetting Network/Data settings, I'll have data for about 20-30 seconds. I can browse the web, but I can't send or receive calls or messages. Then it goes away completely. It sporadically returns, but drops again quickly.
Carrier is Verizon. My Sim card is still being read so the issue doesn't seem to be there. I've put it back in my Pixel 2 and it's working fine.
At a high level, this is what I've done over the past 12 hours:
1. My bootloader is unlocked. I flashed a new ROM and then it wouldn't boot.
2. I did a Factory reset through Recovery and then it booted into the ROM, where I noticed I had no signal
--Possibly an issue here? This factory reset wasn't done thru TWRP, but the stock(?) recovery. I noticed that after doing this, it wiped everything on my phone, including my Nandroid backups
3. I did another factory reset, still no service
4. I moved sim card from Sim Slot 2 to Sim slot 1, temporarily restored service. Then dropped.
5. I flashed OOS 9.0.12 back, service came back temporarily, then dropped
6. I did a network reset, restored service temporarily, then dropped
7. I reflashed modem, system, and vendor images
Anyone have any thoughts or suggestions? Otherwise, I'm probably going to send my phone back to OnePlus for repair.
Try restoring through the msm tool.
TheRemyx said:
Hey guys,
I recently flashed Omnirom and after doing so, noticed I had no signal. After flash, reboot, or resetting Network/Data settings, I'll have data for about 20-30 seconds. I can browse the web, but I can't send or receive calls or messages. Then it goes away completely. It sporadically returns, but drops again quickly.
Carrier is Verizon. My Sim card is still being read so the issue doesn't seem to be there. I've put it back in my Pixel 2 and it's working fine.
At a high level, this is what I've done over the past 12 hours:
1. My bootloader is unlocked. I flashed a new ROM and then it wouldn't boot.
2. I did a Factory reset through Recovery and then it booted into the ROM, where I noticed I had no signal
--Possibly an issue here? This factory reset wasn't done thru TWRP, but the stock(?) recovery. I noticed that after doing this, it wiped everything on my phone, including my Nandroid backups
3. I did another factory reset, still no service
4. I moved sim card from Sim Slot 2 to Sim slot 1, temporarily restored service. Then dropped.
5. I flashed OOS 9.0.12 back, service came back temporarily, then dropped
6. I did a network reset, restored service temporarily, then dropped
7. I reflashed modem, system, and vendor images
Anyone have any thoughts or suggestions? Otherwise, I'm probably going to send my phone back to OnePlus for repair.
Click to expand...
Click to collapse
Have you wiped the cache?
It's not a hardware issue.
rickysidhu_ said:
Try restoring through the msm tool.
Click to expand...
Click to collapse
I would also try the MSM tool to restore back to stock. Then reflash what you want for a ROM.
rickysidhu_ said:
Try restoring through the msm tool.
Click to expand...
Click to collapse
Scott said:
I would also try the MSM tool to restore back to stock. Then reflash what you want for a ROM.
Click to expand...
Click to collapse
Thanks guys. Using MSM worked.
For those who may have the same issue, I used MSM to go back to 9.0.11 since a few people said they had issues with 9.0.12 such as not being able to unlock it. I restored 9.0.11, unlocked my device, then flashed the 9.0.12 OTA. Issue stayed resolved.
I did try to flash Omnirom again and the issue came back, so I'm curious as to what's happening. I'm going to try another Rom.
Just an update, this seems to happen with any rom I flash now. I tried Omnirom, Pixel Experience, and Syberia OS. They boot up but with no 4g connection. When I use MSM to go back to 9.0.11 or 9.0.12 everything works properly. Not sure what I may be missing?
Out of curiosity, how are you installing your custom ROMs. I have installed quite a few custom ROMs in the last week or so and have not encountered any issues. I use a USB pendrive with an OTG adapter to install my stuff as the phone normally ends up in an encrypted state so the internal storage will not be accessible when booting into TWRP. Here are the steps I use when installing a custom ROM:
01. Boot into TWRP
02. Wipe, then swipe. You can choose to Format Data if you want, but this will erase your internal storage so you will lose your recent pictures and other media.
03. Install full OOS 9.0.11/9.0.12 depending on which version is required for the custom ROM and install TWRP also.
04. Reboot recovery.
05. Install full OOS 9.0.11/9.0.12 and TWRP again to ensure both slots have OOS install on it. Use the same version you installed in step 3.
06. Reboot recovery.
07. Install your custom ROM and TWRP.
08. Reboot recovery.
09. Wipe, then swipe (Do not format; unsure if this makes a difference).
10. Install GApps if needed (ROM dependent) and optionally install Magisk and a custom kernel.
11. Reboot system and then wait to setup the phone.
As stated, this has worked flawlessly for me and I have not run into any issues. Admittedly, I have not tried Omnirom directly, but I have tried Omnirom Treskmod (not available on XDA) and SkyDragon which are both based on Omnirom and did not have issues with either. I have tried maybe 10 different custom ROMs in the last week on so and have not had any problems. Still trying to find the best ROM for me. You could say that I'm a flashaholic.
I hope this helps.
Ooms
dj_ooms said:
Out of curiosity, how are you installing your custom ROMs. I have installed quite a few custom ROMs in the last week or so and have not encountered any issues. I use a USB pendrive with an OTG adapter to install my stuff as the phone normally ends up in an encrypted state so the internal storage will not be accessible when booting into TWRP. Here are the steps I use when installing a custom ROM:
01. Boot into TWRP
02. Wipe, then swipe. You can choose to Format Data if you want, but this will erase your internal storage so you will lose your recent pictures and other media.
03. Install full OOS 9.0.11/9.0.12 depending on which version is required for the custom ROM and install TWRP also.
04. Reboot recovery.
05. Install full OOS 9.0.11/9.0.12 and TWRP again to ensure both slots have OOS install on it. Use the same version you installed in step 3.
06. Reboot recovery.
07. Install your custom ROM and TWRP.
08. Reboot recovery.
09. Wipe, then swipe (Do not format; unsure if this makes a difference).
10. Install GApps if needed (ROM dependent) and optionally install Magisk and a custom kernel.
11. Reboot system and then wait to setup the phone.
As stated, this has worked flawlessly for me and I have not run into any issues. Admittedly, I have not tried Omnirom directly, but I have tried Omnirom Treskmod (not available on XDA) and SkyDragon which are both based on Omnirom and did not have issues with either. I have tried maybe 10 different custom ROMs in the last week on so and have not had any problems. Still trying to find the best ROM for me. You could say that I'm a flashaholic.
I hope this helps.
Ooms
Click to expand...
Click to collapse
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
TheRemyx said:
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
Click to expand...
Click to collapse
I didn't notice any popups when setting up my device. The only thing I can say is that VoLTE never used to work properly for me on OOS. I had to edit a setting in serial mode to get VoLTE working on my network in the UK. Not sure if it is related at all. I highly doubt it. I noticed in your steps, you have not flashed GApps. I believe most custom ROMs don't contain GApps, only a select few. Is there a reason you are not flashing GApps? I know there are individuals who want to stay away from Google and use Micro-G as an alternative. I believe the minimum is to flash Pico or Nano GApps. I am not sure if there is possibly something in GApps that is related to data and telephony. The notification popup you are getting may also be related to not having GApps. I install the Nano GApps so I can get face unlock working. Maybe try that and then try installing Magisk after if you still have the same issues. You are rebooting the system in your Step 12. Maybe try and reboot recovery first, then reboot system to keep TWRP intact. You could try the steps that I posted. I use a USB pendrive but if you Format Data to clear your internal storage, it should not be encrypted after unless you reboot into OOS beforehand. You should be able to push files directly to internal storage through ADB in TWRP or you can maybe mount the phone on the computer and copy the files across. These are only suggestions. I haven't had the issues you are having but the steps I listed seem to have worked consistently for my. As a note, I have never had to use the MSMTool to get my phone back up and running again. I have used fastboot mode before though.
I hope this helps.
Ooms
TheRemyx said:
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
Click to expand...
Click to collapse
Not sure if it helps, but you are doing too many repeated steps. Skip 4 & 5, Format Data before installing 9.0.12. Skip 11. Why are you installing TWRP so many times?
dj_ooms said:
I didn't notice any popups when setting up my device. The only thing I can say is that VoLTE never used to work properly for me on OOS. I had to edit a setting in serial mode to get VoLTE working on my network in the UK. Not sure if it is related at all. I highly doubt it. I noticed in your steps, you have not flashed GApps. I believe most custom ROMs don't contain GApps, only a select few. Is there a reason you are not flashing GApps? I know there are individuals who want to stay away from Google and use Micro-G as an alternative. I believe the minimum is to flash Pico or Nano GApps. I am not sure if there is possibly something in GApps that is related to data and telephony. The notification popup you are getting may also be related to not having GApps. I install the Nano GApps so I can get face unlock working. Maybe try that and then try installing Magisk after if you still have the same issues. You are rebooting the system in your Step 12. Maybe try and reboot recovery first, then reboot system to keep TWRP intact. You could try the steps that I posted. I use a USB pendrive but if you Format Data to clear your internal storage, it should not be encrypted after unless you reboot into OOS beforehand. You should be able to push files directly to internal storage through ADB in TWRP or you can maybe mount the phone on the computer and copy the files across. These are only suggestions. I haven't had the issues you are having but the steps I listed seem to have worked consistently for my. As a note, I have never had to use the MSMTool to get my phone back up and running again. I have used fastboot mode before though.
I hope this helps.
Ooms
Click to expand...
Click to collapse
I had tried flashing GAPPs (ARM64-Nano) and it didn't seem to make a difference. I was skipping that and flashing Magisk just to confirm if I had service first. But would service/signal be dependent on something in GAPPs? I may try your way. I hadn't run into any issues with encrypted storage lately. The last few times I was able to get around it by booting to system first, then rebooting back to recovery.
schmeggy929 said:
Not sure if it helps, but you are doing too many repeated steps. Skip 4 & 5, Format Data before installing 9.0.12. Skip 11. Why are you installing TWRP so many times?
Click to expand...
Click to collapse
I was installing TWRP because every time I restored or flashed, I was losing my custom recovery.
So, I decided to upgrade my OP6T with Renovate on it. Booted into TWRP (official from their website), did a Nandroid Backup. Now, I did remove my fingerprint and other security before starting. Flashed the full 9.0.14, reflashed TWRP, rebooted into TWRP, flashed Magisk, and then trid to boot into system. Got a bootloop where the phone was jumping in and out of the bootloader message. I tried to stop it by pressing power and volume down and it ended up booting into safe mode. I didn't like that so I booted into TWRP and restored my Nandroid. And that's when the fight started.
It won't boot into anything but TWRP now and everything is encrypted. I have been here before but last time, I got the device totally corrupt message and used MSM to recover. But that was within two weeks of owning the phone. Now it's been three months or so and I do not relish loosing all the pictures and other setting/changes I've made to my apps etc. I am NOT liking this decryption stuff.
So, is there something, anything I can do short of a fastboot rom and/or MSM tool that we all know will wipe out all data. What if I used the unofficial TWRP? Sideload the ROM again?
Any help is appreciated. I hope I didn't make this too long, but long enough to give enough detail of how I got here and that I somewhat know what I'm doing. Been doing this since the OG Motorola Droid almost 10 years ago.
That's usually why backup is always a good idea and in some case, mandatory.
It usually depends on what TWRP version you are using, the recent unofficial TWRP can decrypt the whole /data directory no problem. However, it's possible to brick a slot, and be able to salvage your files in other slot. I have this problem, so I will have to figure out how to remove the encryption keys after backing up my stuff off the phone so I can have both slots functional (Slot A in my OnePlus 6T is bricked, so right now I'm on Slot B, with AOSiP, FrancoKernel and TWRP 3.3.1-6 on it). Dual-boot setup can be both your friend and enemy.
Nevertheless, I would give TWRP 3.3.1-6 bootable image via fastboot a try, and see if you could be able to recover your files from thereon.
Sent from my ONEPLUS 6T using Tapatalk
I tried asking about this in the twrp thread no replies as of yet.... man I miss the days of epic4g touch (s2) days I could flash a rom , brick my phone and just restore my twrp or clockwork mod recovery back ups...I used to show off all the roms I had from back ups....I tried making a back up when we first got root and twrp for this phone and I definitely had to use msm tool to get my phone back up and running
mlock420 said:
I tried asking about this in the twrp thread no replies as of yet.... man I miss the days of epic4g touch (s2) days I could flash a rom , brick my phone and just restore my twrp or clockwork mod recovery back ups...I used to show off all the roms I had from back ups....I tried making a back up when we first got root and twrp for this phone and I definitely had to use msm tool to get my phone back up and running
Click to expand...
Click to collapse
Me too. This a/b partition crap and force decryption takes all the fun out of trying new roms. So far it seems to be pointless taking a Nandroid if restoring it just soft bricks your phone. And from what I'm reading, flashing even a updated ROM almost always has to be done very clean, heck it seems like wiping your 'sdcard' is also mandatory. I'm just hoping the above suggestion of trying the different TWRP will allow me to at least get some stuff off my 'sdcard' but I secretly hope I can get into system once just to take a titanium.
Then it's wipe and trade for the oneplus 7 pro, root it and rom it once and call it a day.
I can back up and restore nandroid no issue although I remove any pin code/face unlock/fingerprint prior to backing up. No issues.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
ozzmanj1 said:
I can back up and restore nandroid no issue although I remove any pin code/face unlock/fingerprint prior to backing up. No issues.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Just curious, what TWRP version are you on? I checked the TWRP website and they only have 3.2.?.? available there while mauronofrio (who is named as maintainer at TWRP) has 3.3.1.6 available in the thread here at XDA:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
So. Today I tried to get this thing up and running. I went to the TWRP thread mentioned above and downloaded the latest files. Booted into bootloader, ran flashboot boot xxx.img and it booted into 3.3.1.6 just fine. The 'sdcard' was still encrypted so I couldn't copy the .img file and flash it via the newst instructions, , so I did an adb sideload of the installer file. That flashed just fine and I used TWRP to reboot recovery. Check. 'sdcard' still encrypted. Since this encryption issue seems to happen if you upgrade to a newer security patch and I had tried to do an nandroid restore of an earlier version, at the end I tried this (I did try those steps with 9.0.12 full ROM first, the version of my nandroid):
adb sideload of the full 9.0.14 rom (the upgrade that got me into this dang fix). Then adb sideload of the TWRP installer. Then adb sideload of Magisk since I have read that this needs to be done after TWRP to make your phone boot. Still no good. Won't boot into anything but recovery. Tried the 3.3.1.6 advanced 'fix recovery reboot' or whatever it is, still to no avail.
At least I still have the yellow exclamation point and not the red one. And TWRP 3.3.1.6 stuck, so I am at the latest TWRP there is, at least from what I know.
Any more help or ideas so I can at least boot into my system one last time so I can do some Titanium or even the OnePlus backup? I just have some data that to backup correctly, I need to be able to boot system without wiping my data.
Please?
teddyearp said:
So. Today I tried to get this thing up and running. I went to the TWRP thread mentioned above and downloaded the latest files. Booted into bootloader, ran flashboot boot xxx.img and it booted into 3.3.1.6 just fine. The 'sdcard' was still encrypted so I couldn't copy the .img file and flash it via the newst instructions, , so I did an adb sideload of the installer file. That flashed just fine and I used TWRP to reboot recovery. Check. 'sdcard' still encrypted. Since this encryption issue seems to happen if you upgrade to a newer security patch and I had tried to do an nandroid restore of an earlier version, at the end I tried this (I did try those steps with 9.0.12 full ROM first, the version of my nandroid):
adb sideload of the full 9.0.14 rom (the upgrade that got me into this dang fix). Then adb sideload of the TWRP installer. Then adb sideload of Magisk since I have read that this needs to be done after TWRP to make your phone boot. Still no good. Won't boot into anything but recovery. Tried the 3.3.1.6 advanced 'fix recovery reboot' or whatever it is, still to no avail.
At least I still have the yellow exclamation point and not the red one. And TWRP 3.3.1.6 stuck, so I am at the latest TWRP there is, at least from what I know.
Any more help or ideas so I can at least boot into my system one last time so I can do some Titanium or even the OnePlus backup? I just have some data that to backup correctly, I need to be able to boot system without wiping my data.
Please?
Click to expand...
Click to collapse
This is the actual way to install or upgrade an OS
Boot to TWRP
ADB sideload oos 9.0.14
ADB sideload TWRP installer
Reboot system (Yes boot to system not TWRP..don't flash Magisk too now)
Let the phone boot
Go back to TWRP
Install Magisk
teddyearp said:
So, I decided to upgrade my OP6T with Renovate on it. Booted into TWRP (official from their website), did a Nandroid Backup. Now, I did remove my fingerprint and other security before starting. Flashed the full 9.0.14, reflashed TWRP, rebooted into TWRP, flashed Magisk, and then trid to boot into system. Got a bootloop where the phone was jumping in and out of the bootloader message. I tried to stop it by pressing power and volume down and it ended up booting into safe mode. I didn't like that so I booted into TWRP and restored my Nandroid. And that's when the fight started.
It won't boot into anything but TWRP now and everything is encrypted. I have been here before but last time, I got the device totally corrupt message and used MSM to recover. But that was within two weeks of owning the phone. Now it's been three months or so and I do not relish loosing all the pictures and other setting/changes I've made to my apps etc. I am NOT liking this decryption stuff.
So, is there something, anything I can do short of a fastboot rom and/or MSM tool that we all know will wipe out all data. What if I used the unofficial TWRP? Sideload the ROM again?
Any help is appreciated. I hope I didn't make this too long, but long enough to give enough detail of how I got here and that I somewhat know what I'm doing. Been doing this since the OG Motorola Droid almost 10 years ago.
Click to expand...
Click to collapse
What you should have done is not flashed magisk, but booted back to recovery, flashed oos again so you have it on both slots. Flashed TWRP again, booted back to recovery then flashed magisk and then to system.
If you had encountered encryption, you could either start fresh with MSM and have to re-root. Or you could have wiped data and sideloaded OOS & TWRP from an OTG or PC so you wouldn't have to go through the process of using adb and re-rooting.
Well, thank you two very much, but . . . . crud. Here's what I've done now:
per sanjeev7 I did this:
Code:
boot to TWRP (it won't boot to anything else, lol)
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot system
It didn't boot to system, but booted back into TWRP so the additional step to sideload Magisk was moot.
So, then I went with what ebproject said above which on the surface looked more promising(?):
Code:
Boot TWRP
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot to TWRP via phone
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot TWRP via phone
adb sideload Magisk-v19.3.zip
Reboot System
Still would not boot into system, but just back to recovery (TWRP).
I know I could probably do a data wipe after sideload TWRP installer, but I'm being stubborn. I have an app called Fuel Log that I track all my vehicle expenses on. I can make a backup within the software that I can then copy from the 'sdcard'. And I also have pdf maps which I would like to be able to access my 'sdcard' to get the most recent maps from, but it would be easy enough to get the two or six newest maps since my last backup of the files from my 'sdcard'. And then there's my stock tracking app which I don't think I can backup my current stuff without doing a Titanium. Still could be done manually. So at the end of the day, I really wish I could get into system just once to backup fuel log.
None of it is the end of the world, as I am going to receive a Oneplus 7 Pro tomorrow. I just wish I could make as seamless a transition as possible. I do have Titanium backups from a few months ago for all these above named apps, but like I said, if anyone has any ideas, please let me know.
What if I did the second set using OOS 9.0.12 instead of 9.0.14 since that is the version of the Nandroid backup that I restored? Or, and this is a long shot I know, what if I flashed a different ROM altogether? I do know that dirty flashing a different ROM is almost impossible, but maybe?
That's a classic symptoms of the loss of encryption keys for the /data directory (for some reasons, despite the dual-boot setup sharing the same /data directory, but uses two separate different keys for each slots - a definite bad idea).
Sent from my ONEPLUS 6T using Tapatalk
teddyearp said:
Well, thank you two very much, but . . . . crud. Here's what I've done now:
per sanjeev7 I did this:
Code:
boot to TWRP (it won't boot to anything else, lol)
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot system
It didn't boot to system, but booted back into TWRP so the additional step to sideload Magisk was moot.
So, then I went with what ebproject said above which on the surface looked more promising(?):
Code:
Boot TWRP
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot to TWRP via phone
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot TWRP via phone
adb sideload Magisk-v19.3.zip
Reboot System
Still would not boot into system, but just back to recovery (TWRP).
I know I could probably do a data wipe after sideload TWRP installer, but I'm being stubborn. I have an app called Fuel Log that I track all my vehicle expenses on. I can make a backup within the software that I can then copy from the 'sdcard'. And I also have pdf maps which I would like to be able to access my 'sdcard' to get the most recent maps from, but it would be easy enough to get the two or six newest maps since my last backup of the files from my 'sdcard'. And then there's my stock tracking app which I don't think I can backup my current stuff without doing a Titanium. Still could be done manually. So at the end of the day, I really wish I could get into system just once to backup fuel log.
None of it is the end of the world, as I am going to receive a Oneplus 7 Pro tomorrow. I just wish I could make as seamless a transition as possible. I do have Titanium backups from a few months ago for all these above named apps, but like I said, if anyone has any ideas, please let me know.
What if I did the second set using OOS 9.0.12 instead of 9.0.14 since that is the version of the Nandroid backup that I restored? Or, and this is a long shot I know, what if I flashed a different ROM altogether? I do know that dirty flashing a different ROM is almost impossible, but maybe?
Click to expand...
Click to collapse
Okay, to start off, before you started any of this what was you OS were you running?
That's what you need to try and sideload to try get the encryption back to normal because of the mismatch in security patches.
teddyearp said:
Well, thank you two very much, but . . . . crud. Here's what I've done now:
per sanjeev7 I did this:
Code:
boot to TWRP (it won't boot to anything else, lol)
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot system
It didn't boot to system, but booted back into TWRP so the additional step to sideload Magisk was moot.
So, then I went with what ebproject said above which on the surface looked more promising(?):
Code:
Boot TWRP
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot to TWRP via phone
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot TWRP via phone
adb sideload Magisk-v19.3.zip
Reboot System
Still would not boot into system, but just back to recovery (TWRP).
I know I could probably do a data wipe after sideload TWRP installer, but I'm being stubborn. I have an app called Fuel Log that I track all my vehicle expenses on. I can make a backup within the software that I can then copy from the 'sdcard'. And I also have pdf maps which I would like to be able to access my 'sdcard' to get the most recent maps from, but it would be easy enough to get the two or six newest maps since my last backup of the files from my 'sdcard'. And then there's my stock tracking app which I don't think I can backup my current stuff without doing a Titanium. Still could be done manually. So at the end of the day, I really wish I could get into system just once to backup fuel log.
None of it is the end of the world, as I am going to receive a Oneplus 7 Pro tomorrow. I just wish I could make as seamless a transition as possible. I do have Titanium backups from a few months ago for all these above named apps, but like I said, if anyone has any ideas, please let me know.
What if I did the second set using OOS 9.0.12 instead of 9.0.14 since that is the version of the Nandroid backup that I restored? Or, and this is a long shot I know, what if I flashed a different ROM altogether? I do know that dirty flashing a different ROM is almost impossible, but maybe?
Click to expand...
Click to collapse
I replicated ur situation...and I have one cheat code for u
Boot into SLOT B if u r in SLOT A or vice versa!
The other SLOT is taking backup of current system before flashing successfully!! Try this!
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
sanjeev7 said:
I replicated ur situation...and I have one cheat code for u
Boot into SLOT B if u r in SLOT A or vice versa!
The other SLOT is taking backup of current system before flashing successfully!! Try this!
Click to expand...
Click to collapse
U can WhatsApp me on +918898340211
I would like to help u coming out! I have some experience in this!
If you are not sure how to boot into either slots in Fastboot, here's the slot switch command;
fastboot --set-active=a
(Set to Slot A, substitute with B if you want to boot into Slot B.)
Afterwards, reboot (you can alternatively reboot into the bootloader by typing into "fastboot reboot-bootloader" so you can retry the data salvation via fastbooted TWRP).
Sent from my ONEPLUS 6T using Tapatalk
ebproject said:
Okay, to start off, before you started any of this what was you OS were you running?
That's what you need to try and sideload to try get the encryption back to normal because of the mismatch in security patches.
Click to expand...
Click to collapse
I was on 9.0.12. I did already sideload the 9.0.12 app then sideload TWRP (version I mentioned above) then sideload Magisk. I obviously took a bit of a break, rec'd my OnePlus 7 Pro last night. And of course, like any good Andoird'er I had to get it all rooted and stuff, you know, first things first, lol. So tonight I will probably try some more.
As in I'll sideload 9.0.12, sideload TWRP, reboot system and if it works I'll not really worry about magisk since I will be in.
Thank you very much.
sanjeev7 said:
I replicated ur situation...and I have one cheat code for u
Boot into SLOT B if u r in SLOT A or vice versa!
The other SLOT is taking backup of current system before flashing successfully!! Try this!
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
U can WhatsApp me on +918898340211
I would like to help u coming out! I have some experience in this!
Click to expand...
Click to collapse
Wow, thanks. I don't have Whatsapp and as my signature says, I usually try to read read read, then after doing some steps with fail, I give up and post, lol. So I was done by the time I posted.
Like I said in my previous post, I rec'd my 7 Pro last night and got it ready to be set the rest of the way up, so tonight I will try this new method. Just curious, should I do the slot switch within TWRP or should I do it as Dr. Mario said and use fastboot to switch?
Thanks a bunch everyone.
teddyearp said:
Wow, thanks. I don't have Whatsapp and as my signature says, I usually try to read read read, then after doing some steps with fail, I give up and post, lol. So I was done by the time I posted.
Like I said in my previous post, I rec'd my 7 Pro last night and got it ready to be set the rest of the way up, so tonight I will try this new method. Just curious, should I do the slot switch within TWRP or should I do it as Dr. Mario said and use fastboot to switch?
Thanks a bunch everyone.
Click to expand...
Click to collapse
U can simply go to TWRP and click on REBOOT...u will get option...SLOT A....SLOT B....try both the slots...one one time...I hope u boot!!
I was able to!
Either fastboot or TWRP, you can use either methods of switching the active slots. TWRP is much easier though.
Sent from my ONEPLUS 6T using Tapatalk
Well boys, I can't say I/we didn't give it the old college try. Dang it!
So, I'm not going to put out as much detail as I did before since by now you know what I'm doing step by step. I'll point out that the 9.0.12 file (yes I used that one) I used is this one: OnePlus6TOxygen_34_OTA_019_all_1901231347_fb09dd2d4.zip
So:
Boot into TWRP
sideload ROM
sideload TWRP
Went to reboot menu (in TWRP) saw that I was on slot a, but just used the Recovery reboot button. Once back into TWRP, I went again to the Reboot menu and saw that I was already now on slot b. Repeated above and then sideloaded Magisk. Reboot. Back to TWRP only. Ugh! Tried it again, but instead of rebooting TWRP after the one slot, just changed slots without rebooting TWRP and repeated. Did not sideload Magisk. Still a fail.
I'm about done here, but there was one message on my computer within the command window that was shown after the second flash of the ROM on both tries:
ADB: Failed to read command: no error.
What a journey! Thanks guys. And/or girls if any of you are girls, hehe.
ozzmanj1 said:
I can back up and restore nandroid no issue although I remove any pin code/face unlock/fingerprint prior to backing up. No issues.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
Click to expand...
Click to collapse
teddyearp said:
<snip> Now, I did remove my fingerprint and other security before starting. <snip>
Click to expand...
Click to collapse
Thank you, but I do believe that I did do that.
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.
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