OnePlus X brick - OnePlus X Q&A, Help & Troubleshooting

Hello, I need help with my OPX.
I cannot enter Android or recovery, only Fastboot. Also, Fastboot on my PC can detect my device, but ADB cannot.
I had CM 13 and TWRP 3.0.2.0 installed on it, and now I was going to install LineageOS 14.1. I was first going to update TWRP to 3.0.3.0 because I thougt why not. I installed the new version with TWRPs image flashing and then it rebooted itself to Android. Then I was going to enter recovery again to install Lineage, the problem was that I couldn't even start the recovery. So now I tried to install TWRP with Fastboot, but it told me that the bootloader was locked which I thought was strange since I had unlocked it before.
So I tried to unlock the bootloader with Fastboot using "fastboot oem unlock" which it reported that it did and now I couldn't even enter Android.
But when I use "fastboot oem device-info", it says false to both unlocked and tampered and I still couldn't flash or boot into a recovery with Fastboot.
So now I can only boot into Fastboot Mode.
EDIT 2: Never mind, I fixed it with https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Can I remove this thread somehow?

You needed to flash OOS3 ROM or system partion before flashing 3.0.3 and Lineage

Yepp, I noticed. Found out later that it was because of the older bootloader. I had no idea about that before.

Related

Softbrick with no custom recovery

I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
xavier55 said:
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
Click to expand...
Click to collapse
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
thanks you saved me
baymon said:
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
Click to expand...
Click to collapse
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
soltheman said:
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the follow up! No the phone would not boot at all and kept stuck at boot loop. I ended up just doing the OEM Lock and call it a day, the old device just won't boot to anything at this point.
I tried fastboot flash recovery recovery.img but it's giving some kinda kernel panic message and I was never able to get into recovery. This reminds me of the time when my Note 3 eMMC was fried, it wouldn't give a device ID to adb.
I think I am in the same boat too. I've been OEM unlocked yet recently my phone won't keep the TWRP recovery and keeps putting me into bootloop. I can't install a ROM and only thing I can do is fastboot mode. What did you do OEM lock the device? I am hoping that solution will get rid of that message bootloader unlocked during the bootloop and then I can try and get it serviced.

Please Help! I have soft bricked my OnePlus X!!

Hi. I have had the OnePlus X for a very long time, and I have recently bricked .
Ok, here it goes :fingers-crossed:. I had a OnePlus X running CM13 with TWRP but a locked bootloader. I decided to try cyanogenmod recovery but soon realized it was terrible.
I was unable to flash img. files and the UI was unappealing to me. However at that point I was able to reboot into my ROM (CM13) with no issues. Knowing this, I thought that the only way I could get TWRP back was through a fastboot command (fastboot flash recovery recovery.img).
For me to execute that command, I needed to unlock my bootloader first, so I took all the necessary steps in the developer options settings menu. I then booted into fastboot mode and executed this command: fastboot oem unlock. This was my big mistake, as I read up after that you should not unlock bootloader on a custom recovery.
After executing this command, it booted me into recovery. I tried many times without success to wipe data and flash a rom zip via external sd card but they never worked. To make things worse, I was unable to boot up the device. Whenever I tried to power on the device, it booted straight into recovery. I am able to boot into fasboot and recovery, but that is pretty much it. Can someone please help me? I am willing to donate.
If you were able to flash the Cyanogen recovery with a locked bootloader you should be able to flash the official OPX recovery as well. You can download that from this link: https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
Then you should be able to unlock the bootloader!
Or if @Tanner1294's doesn't help, flashing stock rom via fastboot will surely help..
PS: Don't ever flash anything on a locked bootloader.

Unable to enter Recovery Mode even though officially unlocked

Hi,
I have unlocked my bootloader officially through the unlock tool and wanted to flash a custom recovery and also root my device (Redmi Note 3 - Snapdragon).
I was on Global Dev (6.5.19) before I even started to unlock my bootloader.
After unlock, I was succesffuly able to flash Cofface TWRP recovery through fastboot (well the command prompt didn't throw up any errors and had a success message).
However, when i reboot into recovery (either through button combination or "adb reboot recovery", I just get a screen that shows an image of a phone and USB cable" (similar to the image on the official bootloader unlock tool.
I checked whether the bootloader was unlocked (fastboot oem device-info) and it was indeed unlocked.
I have factory reset and reflashed 6.5.19 (Global dev rom) with MiFlash and this hasn't made any difference.
I also relocked the bootloader with MiFlash Beta and then unlocked successfully with the official unlock tool.
All of these steps still haven't made a difference.
Can someone please advise on the next step to do (as unlocked bootloader is pretty useless if I can't install a custom recovery).
P.S. I also get the same phone and usb cable image when booting into stock recovery
find it weird problem
if you dont,then first just boot the recovery
code:- fastboot boot xxxrecovery.img where xxxrecovery replace your own recovery img name in fastboot folder.
you must success and see twrp recovery
then again transfer img to sdcard and to flash from recovery.
then flash it from recovery and when you reboot ,just swipe to diseable rom to replace it with stock one.
find it really weird ,i did it hundredths of time in my offi unlocked and every time goes fine flashing recovery from fastboot
Hit thanks if i helped
please follow this... it does help for me.
http://forum.xda-developers.com/showpost.php?p=67636917&postcount=32
Thanks very much! These instructions solved my issue
mra1n1 said:
Thanks very much! These instructions solved my issue
Click to expand...
Click to collapse
I have the same problem .How u solved your problem?
You can easily flash this one ZCX Twrp. Is the best i didn`t encountered any issue until now. I`ve flashed custom roms and miui roms as well.. The install process is very simple, follow this one https://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448

[HELP][CRITICAL] stuck with no recovery, no root and locked bootloader on Sultan CM13

Hello Guys,
I was trying to install OxygenOS 3.1.0 when I was on Sultanxda's CM13 but instead bricked the device.
What I did:-
1. Rebooted to TWRP and flashed stock OOS recovery and then clicked reboot into recovery.
2. Instead of rebooting in recovery my phone got stuck at the OnePlus logo.
3. I booted into fastboot to flash twrp.img but it says 'writing 'recovery'...
FAILED (remote: device is locked. Cannot erase)'
4. I repeated the same with stock recovery but no success and was not even able to boot to CM13 now.
Hence I was stuck on the OnePlus logo without any booting ROM or recovery and a locked bootloader (according to fastboot)
What I have already tried but failed:-
1. Tried to root with kingroot etc. (Before bricking)
2. Tried to unlock bootloader but failed because it has no recovery.
3. Tried to flash stock OOS 2.1.3-x
4. For now I used fastboot continue to boot back into CM13
Please help, I'm now stuck with cm13 without root and without any recovery installed.
P.S. I'm not even sure that if I clicked reboot then the phone will boot.
Thanks.
Okay, calm down.
Go to developer options and see if "OEM Unlocking" is enabled. If not, enable it.
Cool. Now enable USB Debugging, connect the phone to PC, open CMD and type
Code:
adb reboot bootloader
then
Code:
fastboot oem unlock
Download TWRP from the official website, rename it to recovery.img and then
Code:
fastboot flash recovery recovery.img
Now you have a recovery and an unlocked bootloader. Profit?
I hope this helps.
Thunderbottom said:
Okay, calm down.
Go to developer options and see if "OEM Unlocking" is enabled. If not, enable it.
Cool. Now enable USB Debugging, connect the phone to PC, open CMD and type
then
Download TWRP from the official website, rename it to recovery.img and then
Now you have a recovery and an unlocked bootloader. Profit?
I hope this helps.
Click to expand...
Click to collapse
Thanks for your help,
But if you read my post then you'll understand that due to absence of a recovery I can't unlock the bootloader and hence cannot flash twrp
gavisharora said:
Thanks for your help,
But if you read my post then you'll understand that due to absence of a recovery I can't unlock the bootloader and hence cannot flash twrp
Click to expand...
Click to collapse
You don't need recovery to unlock bootloader, you need fastboot.
Thunderbottom said:
You don't need recovery to unlock bootloader, you need fastboot.
Click to expand...
Click to collapse
But in OnePlus devices the phone asks a confirmation through recovery recovery to wipe data and unlock
gavisharora said:
But in OnePlus devices the phone asks a confirmation through recovery recovery to wipe data and unlock
Click to expand...
Click to collapse
Try the Mega Unbrick Guide then.
Deleted
Same problem. But i dont have pc with windows and can't use mega unbrick guide(
Any news with solution?

Tried flashing TWRP, but stays stuck on/replace by stock recovery no matter what Itry

No matter how I try to flash the TWRP recovery image to the recovery partition, TWRP gets replaced by the crappy stock recovery!! This is absolutely maddening!
Specifically, it seems that no matter what method to use to flash the TWRP recovery, it gets overriden by the stock loader when the phone reboots.
My bootloader is UNLOCKED and I've installed a custom rom just fine by using the command fastboot boot twrp.img to boot into the twrp image. This is the only way I'm able to use TWRP at all.
I've tried:
fastboot flash recovery twrp.img
Booting into TWRP, and flashing the image over the recovery partition
Flashify to flash the TWRP over the recovery partition from within the rom
Trying to flash cyangenmod's recovery from within the rom (was pretty desperate at this point..)
I've also tried many different versions of TWRP, I can boot into them just fine but none of them stick when I flash them to the recovery partition.
It always says it's successful when I try to flash it, I reboot into recovery, and it boots into the piece of crap EmUI stock recovery screen every time
Anyone have any pointers here? It's not the end of the world but it's pretty aggravating having a completely useless recovery if I'm not near a computer,.
Try using Flashify or Flashfire.
Sadly didn't work. It doesn't seem to matter how I flash the recovery, the bootloader replaces it with the stock recovery when it boots. I'll update the OP to clarify, but thank you
I am having same issue have you found a fix
Have you tried starting completely over? Like, downloading the official MM build (b331, C564D003) from Huawei (Assuming you're on L24)?
On the new, freshly installed ROM, make sure that USB Debugging is and enable OEM Unlock are on in the developer settings.
Then, try flashing this build of TWRP again.
Before rebooting, do a Cache/Dalvik Wipe.
Boot up into the stock rom, then use 'adb reboot recovery' to see what happens next. It should work...
Hi mate,
It'd be easier to help you if you could post a screenshot of your FASTBOOT screen. There will be a line that will say FRP=LOCKED/UNLOCKED something like this.
if it is locked,
you have to install stock rom & enable OEM unlock from setting.
Then relock the boot loader. Then again unlock the boot loader.
For myself, I unlocked my BL unofficially, & this problem occurred . I solved it this way...
Hope it helps.
Cheers!

Categories

Resources