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.
I was on beta 3 and decided to flash a new version of OOS. I flashed 9.0.11 -> reflashed TWRP and magisk but when I rebooted, it went straight back to TWRP.
I had to switch to a different slot and the phone booted to OOS beta 3 again. Tried to flash 9.0.11 and reflashed beta 3 again but the same thing happened.
Then i swiped everything except for USB storage and Internal Storage in TWRP and now the phone is without OS.
I rebooted to TWRP and now TWRP lost the encryption and I can't flash anything anymore.
Does anybody know how to recover from this?
I'm using the official TWRP build.
Dont panic just download a fast boot rom for version 9.0.11 and run it from fastboot using terminal. Then you will need to flash Magisk in order to have root access.
devam1995 said:
Dont panic just download a fast boot rom for version 9.0.11 and run it from fastboot using terminal. Then you will need to flash Magisk in order to have root access.
Click to expand...
Click to collapse
How do you do that using the terminal? I tried following this topic https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 but I got this error
https://imgur.com/wy1immW
TWRP still can't flash OOS
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
twistingthai said:
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
Click to expand...
Click to collapse
Flash a patched
Code:
boot.img
when I got the problem, I did that and it worked, booted me to system but if that doesn't work then you have to flash Magisk.
twistingthai said:
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
Click to expand...
Click to collapse
This phone has A/B partitions and is able to store a backup version of the OS so if a new installed version doesn't boot it will revert back to the old one.
When Flashing, you need to flash "BOTH" slots.
If you used the MSM tool to boot, you just booted and not flashed.
The MSM tool will flash your phone, restore the stock recovery and relic the bootloader. It will look like it came out of the box.
I don't know how to get you from wrapped around the axle except to tell you to run the MSM tool and let it wipe the phone and get you back to stock. You can then unlock the BL again and install TWRP, etc if you like.
twistingthai said:
I was on beta 3 and decided to flash a new version of OOS. I flashed 9.0.11 -> reflashed TWRP and magisk but when I rebooted, it went straight back to TWRP.
I had to switch to a different slot and the phone booted to OOS beta 3 again. Tried to flash 9.0.11 and reflashed beta 3 again but the same thing happened.
Then i swiped everything except for USB storage and Internal Storage in TWRP and now the phone is without OS.
I rebooted to TWRP and now TWRP lost the encryption and I can't flash anything anymore.
Does anybody know how to recover from this?
I'm using the official TWRP build.
Click to expand...
Click to collapse
You are booting into TWRP because you did not format your data partition. When flashing OOS, you need to not only wipe data, but also under the Wipe menu, select format data. It should prompt you to type "yes".
parker.stephens said:
You are booting into TWRP because you did not format your data partition. When flashing OOS, you need to not only wipe data, but also under the Wipe menu, select format data. It should prompt you to type "yes".
Click to expand...
Click to collapse
This! Thanks to you I was able to flash OOS again. But do I need to format the data everytime I flash OOS because it will be a pain . This is the first time I had to format data when updating OOS. Thanks alot.
twistingthai said:
This! Thanks to you I was able to flash OOS again. But do I need to format the data everytime I flash OOS because it will be a pain . This is the first time I had to format data when updating OOS. Thanks alot.
Click to expand...
Click to collapse
Glad to help. I was sick of having to put the device into Qualcomm mode just to get it to boot up, then I decided to try reformatting data and it worked.
I attempted to install Lineage OS on my Pixel C. When I attempt to sideload Lineage OS, I get an error that says "Updater process ended with signal: 7" and it acts like I have no system image installed and just keeps boot-looping. I tried to flash back to stock, but I keep getting an error that says "error: Cannot generate image for userdata". I have re-downloaded all of the images, and retried over and over again, to no avail. Any advice is appreciated!
Well, I finally got my tablet to boot again. I extracted the factory image and individually flashed each component (boot, cache, recovery, vendor, system - in that order) and I'm back to a clean install of the stock android. I went back and flashed twrp (successfully), and tried to sideload Lineage again per the instructions on their website, and got the same result. If I can't figure this out, I may be going back to just stock android.
Is it your first attempt at a custom rom?
Have you flashed a recent kernel, bootloader is unlocked etc?
edit: lol, last reply was from May..
Hey, I guess I haven't been on here in a while, and never saw your reply to this. It is not my first attempt at a custom rom. Bootloader is unlocked, and kernel is up to date (or was in May). I ended up staying on stock android since I had no trouble getting it to work. Best I can recall, I think I read that there was a conflict between TWRP and the kernel version I was on. Around the same time, I tried to flash LineageOS to my Essential PH-1, and had similar issues, and ended up just staying with stock android. I've been flashing custom roms since cyanogenmod was available on my Nexus One (I think that was on cupcake), and while I'm not an expert, I'm pretty comfortable with the process, so I went back to my Moto N6, and was able to flash LineageOS to that without a problem. I know that the Pixel C and PH-1 both have the whole A/B slot architecture, and I wonder if I wasn't managing that correctly, but I've gone through a couple of custom roms on my Pixel C over the years without having that problem, so I just don't know. Right now I'm fine with stock (rooted) Android, but the bug is sure to bite me again soon, so we'll see what happens then.
I recently downgraded to Lineage 15.1 (official) from 16 and had some issues.
Short story to make it work was; installed the April version of the official factory/ota image like you did to overcome version conflicts.
(booting to TWRP.img after getting to the correct recovery menu by pressing power+volume up).
In TWRP; As the \data folder was encrypted I had to format that first (advanced wipe) and used adb to push files to \sdcard.
I flashed the Lineage 15.1 zip, gapps and Magisks before rebooting.
As that build enforces encryption of \data at first boot you may need to use "default_password" to load TWRP with access to \data in the future.
Hope this helps
Hi all
I've gotten myself into a bit of an odd spot, i suspect, due to my complete lack of understanding about the Slots.
I was using Pixen and decided to go back to stock this morning.
After doing so, and installing TWRP, magisk and blu_spark, i've found that if the phone boots into slot A, it just loads into TWRP all the time and won't boot the OS. It also shows all my 'sdcard' folders as just garbage text - not usable.
If i switch to slot B in TWRP and reboot, it's all fine, but i'm worried that something is broken somewhere.
Is there a way i can somehow mirror slot b to a, or somehow make slot a actually work properly?
My process specifically was:
was on latest pixen build with TWRP and magisk
booted into fastboot and flashed the 10.3.6 fastboot ROM
got that up and running, and then installed the 10.3.8 update
did a factory reset
booted up again in clean 10.3.8
booted into fastboot and then booted the TWRP 3.4.0-11 image
installed TWRP 3.4.0-11 using mauronofrio installer zip
rebooted into recovery
installed magisk 21.4 and blu_spark kernel
rebooted into system
All was seemingly fine, but then booting back to recovery to flash some magisk modules and i encountered this trouble with slot A seeming not to work.
can anyone help?
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