Stuck at Oneplus logo when trying to boot into TWRP - OnePlus X Q&A, Help & Troubleshooting

Hi, I have tryed everything I could find in this forum now but nothing worked.
I'm installing TWRP on a Oneplus X via Fastboot as I did with an other OPX before without problems.
Now when I flash TWRP via Fastboot and reboot (holding power + volume down) TWRP doesn't boot.
The phone is stuck at the OP logo with the "powered by android" logo. I can restart it by holding down the power button for a while but then TWRP gets obviously overwritten by stock recovery.
The only thing I recognized is the output of
Code:
fastboot oem device-info
is different from the device I flashed before:
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.018s
Shouldn't the tempered flag be on true? Could this be the problem?
I really would appreciate your help! Thank you!

obermeier said:
Hi, I have tryed everything I could find in this forum now but nothing worked.
I'm installing TWRP on a Oneplus X via Fastboot as I did with an other OPX before without problems.
Now when I flash TWRP via Fastboot and reboot (holding power + volume down) TWRP doesn't boot.
The phone is stuck at the OP logo with the "powered by android" logo. I can restart it by holding down the power button for a while but then TWRP gets obviously overwritten by stock recovery.
The only thing I recognized is the output of
Code:
fastboot oem device-info
is different from the device I flashed before:
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.018s
Shouldn't the tempered flag be on true? Could this be the problem?
I really would appreciate your help! Thank you!
Click to expand...
Click to collapse
But u still able to boot into stock recovery right? If u r on oos 3.1.3 flashing official twrp will not work, u need to use oos3 twrp... After flashing it by fast boot, boot into it directly by giving cmd "fastboot boot nameofrecovery.img"

Thank you for your reply!
Just in this second I made a TWRP boot on my phone. I took the one from blu_spark. I guess this is kind of a oos3 twrp.
For people looking for it in the future: I took the twrp file from here: http://forum.xda-developers.com/devdb/project/?id=12587#downloads
Is there an official oos3 twrp? Because I took the most recent from the twrp.me download site and it didn't worked...

obermeier said:
Thank you for your reply!
Just in this second I made a TWRP boot on my phone. I took the one from blu_spark. I guess this is kind of a oos3 twrp.
For people looking for it in the future: I took the twrp file from here: http://forum.xda-developers.com/devdb/project/?id=12587#downloads
Is there an official oos3 twrp? Because I took the most recent from the twrp.me download site and it didn't worked...
Click to expand...
Click to collapse
Till now der is no official twrp for mm bootloader.. But dis one is unofficial like bluespark https://www.androidfilehost.com/?fid=529152257862676606 by NachiketNamjoshi

Related

Unable to unlock bootloader

Hi,
This morning i had the very bad idea of changing my recovery, and now I'm stuck!
I'm running CM13 and i wanted to update to the latest release, but I got errors, so I said "well, maybe they need their recovery and TWRP is not good anymore for some reasons.
I downloaded the new recovery from CM website (yes, it is the correct version of the phone) and installed it. Well, i don't know what happened, but now I'm stuck into the bootloader (fastboot mode detects my device in cmd)
I decided to flash TWRP again, but now my bootloader is locked (for some mysterious reason, as it was unlock by both the dev option toggle and by a previous OEM unlock command).
I've been trying to unlock it again, but nothing. I lunch
Code:
fastboot oem unlock
and all it does is coming up with this message:
Code:
OKAY [ 0.015s]
finished. total time: 0.016s
The phone reboots and it's stuck as I have access to neither recovery or OS. It just stays there and i have to go back into the bootloader.
the device info from fastboot is:
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.010s]
finished. total time: 0.010s
I also tried with
Code:
fastboot flashing unlock
but it stays stuck with the 3 dots without doing anything.
Is there anything i can do or i have to trough my device into the bin?
thanks
nickimola said:
Hi,
This morning i had the very bad idea of changing my recovery, and now I'm stuck!
I'm running CM13 and i wanted to update to the latest release, but I got errors, so I said "well, maybe they need their recovery and TWRP is not good anymore for some reasons.
I downloaded the new recovery from CM website (yes, it is the correct version of the phone) and installed it. Well, i don't know what happened, but now I'm stuck into the bootloader (fastboot mode detects my device in cmd)
I decided to flash TWRP again, but now my bootloader is locked (for some mysterious reason, as it was unlock by both the dev option toggle and by a previous OEM unlock command).
I've been trying to unlock it again, but nothing. I lunch and all it does is coming up with this message:
The phone reboots and it's stuck as I have access to neither recovery or OS. It just stays there and i have to go back into the bootloader.
the device info from fastboot is:
I also tried with but it stays stuck with the 3 dots without doing anything.
Is there anything i can do or i have to trough my device into the bin?
thanks
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page18
shravanv3 said:
Try this
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page18
Click to expand...
Click to collapse
Yes, this worked!
Thanks a lot.

Can't Boot Into Recovery, Bootloader locked

So my Bootloader is currently locked and I can't boot into recovery, it just shows the OnePlus Logo when I try to boot into it.
So currently, I have ParanoidAndroid w/root, can boot into it, can get to FastBoot, can't get into recovery, Bootloader locked, can't unlock it because the Bootloader Unlock option isn't present in this ROM, since it's not the stock ROM,
How It happened
I had the MultiROM Recovery installed, with the Stock ROM installed as the main ROM. I guess through experimenting with it the Bootloader got relocked somehow.
I eventually installed Paranoid Android, and wanted to switch back to regular TWRP, so I flashed it from recovery, that's when I lost access to it, so I booted into PA, used the TWRP app to flash the recovery, still nothing. finally tired to flash with FastBoot, that's when I found out the Bootloader was locked again.
Did "fastboot oem device-info" got this
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0​
I tried this Unbrick Guide, didn't work, here's the comment I made over there
Not too sure what to do at this point,
https://forum.xda-developers.com/nexus-5x/help/tp-link-android-phone-adb-device-t3440471 maybe inbox the OP of this thread and see if he found a solution
I figured it out, in the end it's the Mega unbrick guide, but with a step I didn't see mentioned anywhere.
if you can't get your phone to show up as QHUSB_BULK:
Turn off your phone.
Hold Volume Up and plug your phone into you computer,
this will force the phone to show up as QHUSB_BULK.
Then you can use the driver provided in that guide and follow the rest of the steps as stated.
Thanks to this guide I found, https://www.gizmochina.com/2016/07/30/oneplus-series-mega-unbrick-guide-twrp-flashing/

Oem locked, bootloop, touchscreen isn't working

Hi all,
I messed up my onyx pretty good this time. It gets stuck after oneplus powered by android logo, if it is connected to my computer i see about 7 partitions come and go. I can enter fastboot, original oneplus recovery.
In fastboot everything is locked,
[email protected]:/home/ivo# fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.005s
[email protected]:/home/ivo# fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
So fastboot isn't working for me.
I tried enter the original recovery, adb sideload original OOS, it says all ok nothing failed, once i reboot nothing changed.
In original recovery my touchscreen isn't responding to touches, with volume up an down and powerbutton i can control it. I wiped everything multiple times.
I tried https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
With this method i locked my device, and still it doesn't change anything.
What else could i try?
thanks for your help
vanderveen.ivo said:
Hi all,
I messed up my onyx pretty good this time. It gets stuck after oneplus powered by android logo, if it is connected to my computer i see about 7 partitions come and go. I can enter fastboot, original oneplus recovery.
In fastboot everything is locked,
[email protected]:/home/ivo# fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.005s
[email protected]:/home/ivo# fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
So fastboot isn't working for me.
I tried enter the original recovery, adb sideload original OOS, it says all ok nothing failed, once i reboot nothing changed.
In original recovery my touchscreen isn't responding to touches, with volume up an down and powerbutton i can control it. I wiped everything multiple times.
I tried https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
With this method i locked my device, and still it doesn't change anything.
What else could i try?
thanks for your help
Click to expand...
Click to collapse
Does this work:
1. Boot into oxygen recovery.
2. Wipe data and cache.
3. Wipe data and cahce again.
4. Then sideload the latest version of OxygenOS.
5. Then boot.
aryan.arora180 said:
Does this work:
1. Boot into oxygen recovery.
2. Wipe data and cache.
3. Wipe data and cahce again.
4. Then sideload the latest version of OxygenOS.
5. Then boot.
Click to expand...
Click to collapse
I tried it, but noticed my terminal says:
serving: 'OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip' (~94Total xfer: 2.00x
It looks like it stops at 94% and then stopped, while my onyx says download succes.
but is still not booting
vanderveen.ivo said:
I tried it, but noticed my terminal says:
serving: 'OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip' (~94Total xfer: 2.00x
It looks like it stops at 94% and then stopped, while my onyx says download succes.
but is still not booting
Click to expand...
Click to collapse
Use this OOS zip file instead: http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_2.2.3/
The one you're downloading is for OOS 3 which has to use the new bootloader and since the mega unbrick guide will put you on the old bootloader I would try the old OOS first. If it boots immediately open the developer settings and tick off OEM unlock.
---------- Post added at 01:34 AM ---------- Previous post was at 01:27 AM ----------
Also I'll say when mine became locked with a custom rom installed I just had to keep following the guide over and over until it finally worked. A lot of it was just trying to get the device to be recognized and having to download files from other sites.
vanderveen.ivo said:
I tried it, but noticed my terminal says:
serving: 'OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip' (~94Total xfer: 2.00x
It looks like it stops at 94% and then stopped, while my onyx says download succes.
but is still not booting
Click to expand...
Click to collapse
When u say booting, do you mean that it gets stuck at the OnePlus logo along with Powered by Android or do you mean it passes that and shows the bootscreen animation and is stuck there?
---------- Post added at 11:19 AM ---------- Previous post was at 11:17 AM ----------
Tanner1294 said:
Use this OOS zip file instead: http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_2.2.3/
The one you're downloading is for OOS 3 which has to use the new bootloader and since the mega unbrick guide will put you on the old bootloader I would try the old OOS first. If it boots immediately open the developer settings and tick off OEM unlock.
Click to expand...
Click to collapse
If you flash the newer OxygenOS, it will automatically install the newer bootloader so old/new bootloader will not make a difference.
aryan.arora180 said:
When u say booting, do you mean that it gets stuck at the OnePlus logo along with Powered by Android or do you mean it passes that and shows the bootscreen animation and is stuck there?
---------- Post added at 11:19 AM ---------- Previous post was at 11:17 AM ----------
If you flash the newer OxygenOS, it will automatically install the newer bootloader so old/new bootloader will not make a difference.
Click to expand...
Click to collapse
Well, i tried oos 2, it changed my boot behavior. I now tries to boot, gets stuck at OnePlus logo along with Powered by Android and then it disapeers and it tries again. It is new that she wants to try again. And the partitions are not visible anymore. Before oos3 it showed about 7 partitions.

[Kate] Phone stuck on bootloop after flash

Hello guys. I write another post because I found what is the real problem on my phone.
Here is my old post : https://forum.xda-developers.com/redmi-note-3/help/kenzo-black-screen-red-dot-blinking-t3891141.
So, my phone is stuck on bootloop when I try to boot it. It doesn't stop rebooting forever.
Here is a video showing the bootloop http://youtu.be/pi2-fnSNGGA.
What I've already done :
Deep cable to unbrick my phone and it was successful (phone now detected as Qualcomm HS-USB QDLoader 9008)
Flash stable or dev rom in EDL mode with MiFlash (I tried a lot of version...)
Flashing a TWRP rom in EDL mode with MiFlash
eveything
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.029s]
finished. total time: 0.031s
Click to expand...
Click to collapse
I really need help guys... :crying: I've no phone anymore for the moment xD
Are you flashed lazy flasher??
ketan7731 said:
Are you flashed lazy flasher??
Click to expand...
Click to collapse
I used lazy flasher before to get my phone rooted but i didn't used it when i bricked my phone
There is something weird in my phone, i can't boot with power button anymore... I'm forced to boot with USB cable.
Here is a video showing my problem : https://youtu.be/3uZceq1mqys
Rtxx said:
There is something weird in my phone, i can't boot with power button anymore... I'm forced to boot with USB cable.
Here is a video showing my problem :
Click to expand...
Click to collapse
Did u try unofficial unlock again?
https://forum.xda-developers.com/redmi-note-3/how-to/guide-rn3-pro-se-t3565172
I've done this one and now my phone is unlocked but still in bootloop
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.013s]
finished. total time: 0.014s
Click to expand...
Click to collapse
I have tried to flash in fastboot TWRP official but i cant access to recovery after the flash.
fastboot flash recovery twrp-3.2.3-0-kenzo.img
target reported max download size of 536870912 bytes
sending 'recovery' (18580 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 0.131s]
finished. total time: 0.734s
Click to expand...
Click to collapse
Rtxx said:
https://forum.xda-developers.com/redmi-note-3/how-to/guide-rn3-pro-se-t3565172
I've done this one and now my phone is unlocked but still in bootloop
I have tried to flash in fastboot TWRP official but i cant access to recovery after the flash.
Click to expand...
Click to collapse
U e official unlocked. But u cant boot into recovery .
Connect phone to pc in fastboot mode.
And use command.
fastboot reboot recovery
I have similar problem with my kate and locked bootloader. It started when my phone needed about 10-15 seconds to turn on and it started freeze. After freeze it rebooted itself. After rebooted it worked normal about 1 hour and again freezed. Untill the moment when it didin't start. I couldn't go into fastboot mode or edl mode (vol + and power). But I found solution to switch into edl mode by disconnect the buttery. And it worked. So i had in device manager qualcomm hs-usb qdloader 9008. I flashed phone with miui 10 and it was successful. But now I have black screen, no fastboot mode only red light blinking. And now I have strange situation. When I connect phone to computer, in device manager I see 900E device. When I disconnect phone from computer and disconnect battery for a moment and connect again to computer, in device manager I have 9008 device. When I try flash I have error ping target failed XiaoMiFlas.code.bl.SerialPortDevice.ping(). I also made and used deep flash cable but it didin't help. Only thing I didin't try is test point but i think it's doing the same as deep flash cable. What am I doing wrong? Or maybe it is hardware issue? (broken emmc or something)

Flashing Recovery Issue

I have a weird condition. First of all I was using Android 9 with twrp. Everything was fine. Today I decided to install Lineage 17.1 and first of all I needed the A10 stock rom. So I decided to use Official Fastboot rom. Installed and booted. I turn the dev options on.
Used Adb reboot fastboot to get into fastboot mode. Used the commands that I used to use.
fastboot getvar current-slot (it says A)
fastboot set_active b
fastboot erase boot
fastboot flash boot twrp.img (everything was fine. no errors so far.)
fastboot reboot recovery (I press vol+ button)
Phone boots to fastboot mode. when I try fastboot continue it changes slots and boot OS. I tried to flash twrp or orange fox or different versions of recovery to both slot but nothing works. I always end up with fastboot screen.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
It seems OK?
I cannot install A9 it gives error (rollback protection maybe?)
How can I flash recovery now? Please help.
Edit: I will try to gain root access patching boot.img with magisk. Maybe somehow I gain access to recovery again. -> Got root access but no recovery
Solved. Tried thousands of recoveries and one worked.

Categories

Resources