Database Users

One plus stuck at boot loop

OP2 is stuck at OP logo after the latest OTA. What do I need to do to have it restored it back ..

sguy156 said:
OP2 is stuck at OP logo after the latest OTA. What do I need to do to have it restored it back ..
Click to expand...
Click to collapse
If you have twrp you can flash a full oxygen rom to restore it if you dont you need to Download latest full rom on your pc go in recovery mode connect phone to pc and put the zip in your storage and after that flash it via recovery mode

No it doesn't go into recovery mode it only goes into fastboot mode ..

sguy156 said:
No it doesn't go into recovery mode it only goes into fastboot mode ..
Click to expand...
Click to collapse
Try this zip on your pc while phone connected and on fastboot mode It auto flashes twrp on your phone so you can try to flash oxygen os via it
https://forum.xda-developers.com/devdb/project/?id=13708#downloads

that worked so do I need to flash modified SU 2.79 to root this phone or stay with the TWRP which came with the first aid script

sguy156 said:
that worked so do I need to flash modified SU 2.79 to root this phone or stay with the TWRP which came with the first aid script
Click to expand...
Click to collapse
If you want to root your phone use this file and Flash it via twrp
https://www.androidfilehost.com/?fid=24591000424939898

modified SU is not going to work and have to use seemless SU . Thanks for your help which version of TWRP works without any issues with the newest Oxygen OS..

sguy156 said:
modified SU is not going to work and have to use seemless SU . Thanks for your help which version of TWRP works without any issues with the newest Oxygen OS..
Click to expand...
Click to collapse
Go to Playstore and download twrp app en flash the latest compiatble version

What is needed to re-root OOS 3.5.6 if you did like me and let the OTA update your phone.
TWRP 3.0.2-2 link
OOS3 SuperSu 2.78 link
You can get latest TWRP flashable OOS packages from here.
For future reference.

Oneplus two Rooted stuck on Boot Loop Mode
Hi Guys I need your Help Can anyone Help me as soon as possible
I was Using Resurrection Remix 5.8.5 Nougat 7.1.2 and in Twrp recovery
I was using Resurrection Remix 5.8.5 Nougat 7.1.2 and in Twrp recovery apk a small mistake was done by me
I tick marked as
Allow Flashing to boot partition after that it got stuck in Boot Loop Mode How fix that guys
But Fastboot Mode only Working

Hi it's done with me but not in your way I was realising why it is not boot loading then I came to know maybe TWRP recovery is not installed so I just wanted to flash TWRP recovery in fastboot mode there are so many people trying in different different way to switch on the mobile which got stuck and boot loop mode I found a simple way with all in one tool for Android I am giving you a description or a link below just to flash TWRP recovery and don't forget to select after flash reboot you have to select tick mark it's the best way you can boot load your phone very very simple way to do that
Download Link
https://basketbuild.com/devs/mauronofrio/TOOL

HELP No recovery, usb not recognized

Its a shame.
7 years unlocking bootloaders, installing CWM or TWRP or Philz recovery, flashing rom after rom, not even one device bricked, and today, i messed up, i hope its not bad.
So the short version of what i did is that i flashed twrp.img trough and older version of twrp and now it wont boot into twrp, it says that it failed to verify the recovery image or something like that, and my laptop wont recognize the cellphone, the cellphone boots into the latest Havoc rom but without Gapps and without root because i did not install it beforehand, when in bootloader mode it just says that it could not recognize the device.
The long version is that i had Resurrection Remix, obviously an unlock bootloader, magisk etc... everything was fine until today that i tried to install Havoc, the installation went well but i found out that ambient display was not working, someone told me that the previous version of Havoc did not had that problem so i tried to flash it but it bootlooped for like 1hr, so i read that the version of TWRP provided by the OP was the way to get it to work, i downloaded the .img file and flashed it trough TWRP and tried to install Havoc again but i was stuck in a bootloop, so i flashed the latest Havoc build so i could download the latest version of twrp, i did not flash Gapps or Magisk because i was going to re flash the rom and then flash Gapps and magisk, so i downloaded TWRP and flashed trough TWRP and thats when the sh$& hit the fan, now it wont boot into TRWP and my laptop wont recognize the device, neither on android nor in bootloader mode.
So, thank you guys in advance for your help, tomorrow im going to try on a computer at my work and see if its my computer and if not, well, ill have to se what you geniuses come up with. thank you so much again.
Info:
Rom build number: opm6.171017.030.h1 or 20180811 android 8.1.0
TWRP: i started with 3.2.2-0 then i downgraded to 3.2.1-0 and the one that messed up everything was 3.2.3-0
By the way, I have a full twrp backup of when my phone was stock, (but no way to use it) T_T

Unlocking bootloader on Orea update?

I've read around that unlocking the bootloader on the axon 7 with the orea update (B04 on A2017G) isn't gonna work and that I need to roll back to nougat (7.1) and then unlock the bootloader that way and then install TWRP.
I'm a noob and I need some help. All I want is android pie and lineage os 16 on top. So could you guys link me to some easy to follow guides on how to get pie and LOS16?
But first I need to understand why I can't just use ADB right now on the oreo axon 7 and get an unlocked bootloader. Why do I have to roll back to nougat?

B1lal545 said:
I've read around that unlocking the bootloader on the axon 7 with the orea update (B04 on A2017G) isn't gonna work and that I need to roll back to nougat (7.1) and then unlock the bootloader that way and then install TWRP.
I'm a noob and I need some help. All I want is android pie and lineage os 16 on top. So could you guys link me to some easy to follow guides on how to get pie and LOS16?
But first I need to understand why I can't just use ADB right now on the oreo axon 7 and get an unlocked bootloader. Why do I have to roll back to nougat?
Click to expand...
Click to collapse
You're correct on that statement.
You can't unlock the bootloader on Oreo because there is no fastboot support with the Oreo updates. ZTE basically broke another thing. You'll need to EDL flash Nougat 7.1 and then use the EDL Tool or the A7 Toolkit to unlock the bootloader. Afterwards, you can follow the instructions in the LineageOS 16 thread, and flash in this order:
• Flash universal bootstack (Los15.1v2Universal)
• Flash the A2017G Modem
• Flash LOS16 zip
• Flash GApps and/or Magisk
• Reboot to system.
If you get an error whilst trying to flash LOS16 zip, just try flashing it again.
All the guides in the Guides section are outdated.

runninghamster said:
You're correct on that statement.
You can't unlock the bootloader on Oreo because there is no fastboot support with the Oreo updates. ZTE basically broke another thing. You'll need to EDL flash Nougat 7.1 and then use the EDL Tool or the A7 Toolkit to unlock the bootloader. Afterwards, you can follow the instructions in the LineageOS 16 thread, and flash in this order:
• Flash universal bootstack (Los15.1v2Universal)
• Flash the A2017G Modem
• Flash LOS16 zip
• Flash GApps and/or Magisk
• Reboot to system.
If you get an error whilst trying to flash LOS16 zip, just try flashing it again.
All the guides in the Guides section are outdated.
Click to expand...
Click to collapse
Thanks for replying when nobody else did. Since this post was a bit old I went ahead and unlocked the bootloader and installed TWRP with magisk, thinking that I could install Lineage later and first I should obtain root. So I installed magisk through TWRP but now whenever I reboot it just goes straight to TWRP and I don't know how to boot into the phone. Any idea about how I can exit twrp?

B1lal545 said:
Thanks for replying when nobody else did. Since this post was a bit old I went ahead and unlocked the bootloader and installed TWRP with magisk, thinking that I could install Lineage later and first I should obtain root. So I installed magisk through TWRP but now whenever I reboot it just goes straight to TWRP and I don't know how to boot into the phone. Any idea about how I can exit twrp?
Click to expand...
Click to collapse
Magisk doesn't work at all on stock roms unless you use a work-around. The phone not booting is because of that.
For the work-around, check out this thread:
https://forum.xda-developers.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809
BTW, I'm not sure if this works, I've never tried it. The thread is also a bit old.

runninghamster said:
Magisk doesn't work at all on stock roms unless you use a work-around. The phone not booting is because of that.
For the work-around, check out this thread:
https://forum.xda-developers.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809
BTW, I'm not sure if this works, I've never tried it. The thread is also a bit old.
Click to expand...
Click to collapse
could it be a possibility that if I reinstall nougat 7.1 on the phone through TWRP, I'd be able to boot? Or does rooting with magisk completely disable us from installing stock roms without some sort of workaround?
My reasoning is that if the rom installs successfully then I would have booted with magisk in magisk manager and root. Maybe my rom got deleted during this process.

B1lal545 said:
could it be a possibility that if I reinstall nougat 7.1 on the phone through TWRP, I'd be able to boot? Or does rooting with magisk completely disable us from installing stock roms without some sort of workaround?
My reasoning is that if the rom installs successfully then I would have booted with magisk in magisk manager and root. Maybe my rom got deleted during this process.
Click to expand...
Click to collapse
Magisk just prevents the phone from booting. It doesn't delete the rom. If you look in topjohnwu's GitHub page for Magisk, you'll find Magisk Uninstaller right next to where you download Magisk from. Download the Magisk Installer zip, move it over to your phone, and then flash it in TWRP. It'll remove Magisk and you'll be able to boot into your rom again.

runninghamster said:
Magisk just prevents the phone from booting. It doesn't delete the rom. If you look in topjohnwu's GitHub page for Magisk, you'll find Magisk Uninstaller right next to where you download Magisk from. Download the Magisk Installer zip, move it over to your phone, and then flash it in TWRP. It'll remove Magisk and you'll be able to boot into your rom again.
Click to expand...
Click to collapse
Ok I've uninstalled magisk with the latest uninstaller. But now when booting up, the phone is stuck on the "please lock bootloader page" and is not proceeding further. Given that I can still use TWRP, should I just follow the LOS 16 pie instructions and install the bootstack, modem, Gapps and the zip file?
I could root the phone by flashing magisk once I'm done flashing these things right?

B1lal545 said:
Ok I've uninstalled magisk with the latest uninstaller. But now when booting up, the phone is stuck on the "please lock bootloader page" and is not proceeding further. Given that I can still use TWRP, should I just follow the LOS 16 pie instructions and install the bootstack, modem, Gapps and the zip file?
I could root the phone by flashing magisk once I'm done flashing these things right?
Click to expand...
Click to collapse
Yeah, go ahead and flash Los 16.
Flash your bootstack and modem, and reboot to recovery from TWRP. The TWRP version will have changed. You need to flash latest TWRP image again, use Orden 3.2.3-0 TWRP from LOS 15/16 thread. After that, reboot to recovery and continue with the rest of the steps.
You can flash Magisk whenever you'd like, hell you could even flash it 1 year after running Los 16 haha.

runninghamster said:
Yeah, go ahead and flash Los 16.
Flash your bootstack and modem, and reboot to recovery from TWRP. The TWRP version will have changed. You need to flash latest TWRP image again, use Orden 3.2.3-0 TWRP from LOS 15/16 thread. After that, reboot to recovery and continue with the rest of the steps.
You can flash Magisk whenever you'd like, hell you could even flash it 1 year after running Los 16 haha.
Click to expand...
Click to collapse
You are my saviour. You've helped me so much. But I'm scared of bricking so please don't be annoyed by me when I ask for confirmation.
So basically I installed the vendor partition using party from @Oki like the LOS 16 guide required.
But now as to the things you told me to do.
First I'll install the universal bootstack for LOS and my model specific modem from https://androidfilehost.com/?w=files&flid=270519
Once both are flashed my TWRP version will have changed so I will flash the latest version of TWRP again using fastboot
Then I'll go on ahead and install LOS 16 and GApps
THANK YOU SO MUCH IN ADVANCE.

B1lal545 said:
You are my saviour. You've helped me so much. But I'm scared of bricking so please don't be annoyed by me when I ask for confirmation.
So basically I installed the vendor partition using party from @Oki like the LOS 16 guide required.
But now as to the things you told me to do.
First I'll install the universal bootstack for LOS and my model specific modem from https://androidfilehost.com/?w=files&flid=270519
Once both are flashed my TWRP version will have changed so I will flash the latest version of TWRP again using fastboot
Then I'll go on ahead and install LOS 16 and GApps
THANK YOU SO MUCH IN ADVANCE.
Click to expand...
Click to collapse
That's correct. Go ahead with the flash, you're welcome for the help

runninghamster said:
That's correct. Go ahead with the flash, you're welcome for the help
Click to expand...
Click to collapse
YAAAAAAAAAYYYY!!!
I just installed LOS 16 and everything seems to be working fine.
But the thing is I downloaded and flashed magisk through TWRP, and the installation went fine. When I booted into LOS even the magisk manager was installed.
But when I installed the root verification app from playstore, it said that the device was not rooted. Any advice? Other than that it feels so good to finally be on a custom ROM. Thanks for your help.
I wish you success and happiness from the bottom of my heart.

runninghamster said:
That's correct. Go ahead with the flash, you're welcome for the help
Click to expand...
Click to collapse
Nevermind hahahahah. I checked another app. I'm rooted, forgot to grant Superuser permissions the first time.
Again thank you so much and I apologize if I was overbearing or annoying. You really helped me out and made this process much less painful than it could've been.

Problems with installing LineageOS 17.1

Good morrning everyone!
i am a little bit helpless with my plan to flash LineageOS 17.1 onto my OP 6T. I started from LineageOS 16, which was rooted with Magisk.
With my first attempt I followed the instructions from https://wiki.lineageos.org/devices/fajita/install. I used the latest files from 20200903 of LineageOS. But after flashing temporarily the recovery, I ended up with a stuck in oem-unlock-screen. To fix it i used the MSMtool 4.0.59.
I flashed only boot and not boot_a or boot_b. So I tried it with that now. But I only got the same results. I was unable to boot into recovery. So again MSM Tool and unlocking the bootloader.
Then I tried to install it via TWRP. OOS 9.0.13:
1. booted into fastboot mode
2. booted TWRP 3.3.1.0
3. Wiped Data and rebooted into fastboot mode
4. booted again TWRP 3.3.1.0
5. installed LineageOS lineage-17.1-20200903-nightly-fajita-signed.zip
6. installed TWRP 3.4.0
7. rebooted into recovery
8. repeated 5. and 6.
9. rebooted into recovery
10. installed open gapps-nano
11. installed Magisk 20.4
12. rebooted the system
Result: Qualcomm CrashDump Mode......
I do not understand what I did wrong. In June I installed Lineage OS on another OP 6T and it worked fine with flashing the recovery to boot_a. But I do not know which OOS was installed. No I am trying it since hours and only end up in the above mentioned results.
What do I have to do? Thanks for your help in advance!
Greetings
Thawu

My LOS Install Guide
- Don't use TWRP 3.4.x. Use 3.3.1-32 (The latest 3.3.1 version.) 3.4.x will give you issues.

Thank you lot. Lineage ist booting =)

Thawu said:
Thank you lot. Lineage ist booting =)
Click to expand...
Click to collapse
I also just noticed you are trying to use a very old version of OOS (which also means old firmware). Why are you using 9.0.13? Perhaps this could be your issue.
I need to update my guide, but 10.3.5, and the latest weekly 9-3 work fine. One warning, I never did get the 10.3.5 fastboot ROM to work on either of my 6Ts. The 10.3.4 Fastboot ROM works fine, then I had to update to 10.3.5 using TWRP.
I asked if anyone else had problems with the 10.3.5 fastboot ROM in the fastboot thread but didnt get any replies...

I started at first wit OOS 9 because of the latest (?) msm tool. I regocnized later, that it is crucial to update OOS to Android 10 what I did after I posted my question. I installed OOS 10.3.5 from oneplus.com via TWRP.
So all I had to do yesterday was to reinstall TWRP 3.3.1-32.
Your guide for installing LineageOS was by far the best I got. All the little explenations were the things I needed to understand, why the steps had to be done. So again thank you for your help and your guide which is really really good.
Greetings
Thawu

Thawu said:
I started at first wit OOS 9 because of the latest (?) msm tool. I regocnized later, that it is crucial to update OOS to Android 10 what I did after I posted my question. I installed OOS 10.3.5 from oneplus.com via TWRP.
So all I had to do yesterday was to reinstall TWRP 3.3.1-32.
Your guide for installing LineageOS was by far the best I got. All the little explenations were the things I needed to understand, why the steps had to be done. So again thank you for your help and your guide which is really really good.
Greetings
Thawu
Click to expand...
Click to collapse
Also if you like themed TWRP @acuicultor and @ morphine1e1 have a really nice creation for OP6/6t here: https://forum.xda-developers.com/on...covery-theme-blacked-twrp-acuicultor-t3847752
It's latest twrp but I've been using it for months without any issues and I flash much more than a regular user. Installed LOS twice and all good.

或许你应该先升级到安卓10 再去安装lineage os 17

Thawu said:
Good morrning everyone!
i am a little bit helpless with my plan to flash LineageOS 17.1 onto my OP 6T. I started from LineageOS 16, which was rooted with Magisk.
With my first attempt I followed the instructions from https://wiki.lineageos.org/devices/fajita/install. I used the latest files from 20200903 of LineageOS. But after flashing temporarily the recovery, I ended up with a stuck in oem-unlock-screen. To fix it i used the MSMtool 4.0.59.
I flashed only boot and not boot_a or boot_b. So I tried it with that now. But I only got the same results. I was unable to boot into recovery. So again MSM Tool and unlocking the bootloader.
Then I tried to install it via TWRP. OOS 9.0.13:
1. booted into fastboot mode
2. booted TWRP 3.3.1.0
3. Wiped Data and rebooted into fastboot mode
4. booted again TWRP 3.3.1.0
5. installed LineageOS lineage-17.1-20200903-nightly-fajita-signed.zip
6. installed TWRP 3.4.0
7. rebooted into recovery
8. repeated 5. and 6.
9. rebooted into recovery
10. installed open gapps-nano
11. installed Magisk 20.4
12. rebooted the system
Result: Qualcomm CrashDump Mode......
I do not understand what I did wrong. In June I installed Lineage OS on another OP 6T and it worked fine with flashing the recovery to boot_a. But I do not know which OOS was installed. No I am trying it since hours and only end up in the above mentioned results.
What do I have to do? Thanks for your help in advance!
Greetings
Thawu
Click to expand...
Click to collapse
I install it on HTC u11.. but voice call speaker not working and Bluetooth voice speaker not working .

Samsung fastboot confirmed

I have successfully used fastboot to flash TWRP to my Tab S5e. Android 10 moved fastboot to userspace as fastbootd and if you have the right recovery it works on Samsung. I used Lineage recovery from local 17.1 build on my machine. Got curious about fastboot options in recovery and it works. Check this to better understand https://source.android.com/devices/bootloader/fastbootd Yep that is source.android link no joke. Device codename can be seen in screenshots.

Does this mean we can flash TWRP Recovery and then just root it with flashing Magisk via TWRP recovery? Thanks.

IngoPan said:
Does this mean we can flash TWRP Recovery and then just root it with flashing Magisk via TWRP recovery? Thanks.
Click to expand...
Click to collapse
Sort of, if you already have LineageOS or another custom ROM that supports it. Stock samsung does not support fastbootd. AOSP based roms should have it as of android 10. It also requires the recovery be compatable. Lineage recovery provides access current TWRP did not. It is explained here https://source.android.com/devices/bootloader/fastbootd . It's a neat trick but not for initial root or custom recovery, still same as always you have to have it before you can get it. It does not replace Odin and the same steps are required as always to root or install twrp on stock Samsung. But once you have access it works to flash magisk_patched.img on LOS which can be good since Lineage 17.1 does not have official su support.