Thanks for the instruction.
However, after following the instructions above (by clean flashing), my device only boots to TWRP. My TWRP version is 3.3.1 by YumeMichi.
I have the seamen problem. The problem happened after installing de TWRP 3.3.1 in Boot. How can we solve the problem?
I have wiped cache, data, Dalvik, system. After that I have installed the latest Lineage 17.1 again, then a system restart. That worked fine for me. After that I installed OpenGaps with no problems and no restarts in TWRP anymore.
So, we have already a fancy name for that ... "seamen problem" .
If i got it right, you're installing twrp into boot-partition, reboot and wonder why you're system won't start but just enters twrp?
Then, after clean reflashing the ROM, you're able to boot into LOS again and now you're wondering why?
Because the reflashing restored the boot-partition you've overwritten with twrp, i'd guess .
twrp has to be flashed to recovery-partition, not to boot-partition.
Hello everyone, my OnePlus X screen froze and it turned off after its battery got depleted. Unfortunately its power button is broken. However, I tried to boot into TWRP by using the Volume up/down buttons but that did not work as well (don't know why).
As my phone's USB Debugging option is turned on, I tried connecting the phone to the pc but the "adb devices" command does not show my device (it returns a blank list of connected devices).
Any ideas/methods on how I can switch on my phone? Thanks in advance!!
Reinstall USB drivers, try a different USB cable / USB port?
You can also boot into bootloader and choose recovery from there I believe.
Thanks for the advice. I have tried different USB ports and tried connecting my phone to a different PC as well, but the device folders don't show up after I connect it to a PC (I think the PC does not treat it as a portable storage device because its switched off and the phone might have been set to "Charge only" mode by default).
The "adb devices" command is not recognizing the phone even though the USB debugging is turned on (I tick marked the option when the phone was working), any thoughts on how to reboot my phone using "adb" commands? Do these commands work if the device is switched off? Thank you!!
UPDATE: The PC recognizes the phone as Model: Android and as a MTP USB Portable under the category "Unspecified" (I found it under Windows Control Panel -> Devices & Printers), but I cannot access the file/storage system of the phone as it does not show up in the windows explorer. I can also access the read-only properties of the phone, if that helps somehow.
First question, in what state is your phone, LOS booted or TWRP booted? If both is not the case, there is nothing adb can connect to. Or is it in FASTBOOT-mode? Then you can try to reboot it with "fastboot reboot" and push volume-down to get it into recovery.
If both is not the case, you should search for "unbrick onyx" .
I'm currently on AOSP Extended Pie Stable rom. It's bug free and awesomely smooth. It is my primary device and daily driver. But still i wanted to try out Android 10. As Yumemichi's rom is the most frequently updated and well maintained i'm hoping it will be wise to flash this. From previous comments i'm not getting a clear view of the rom. Actually I wanted to know, How is the overall performance, battery life, and any heating/lagging/forced close issues compare with Pie roms. if possible please mention the best build of this rom.
My phone was LOS booted (and was running some applications) when it froze. It then switched off after its battery got depleted. It seems my power and volume buttons are broken and I am unable to turn on my device using any of these hardware buttons. As the USB debugging feature is enabled on my phone, I was wondering if I could power on the device by connecting it to a PC and running some "adb" commands.
When I charge my phone it shows the 1+ splash screen and the charging battery animation so the device is working fine, its just that I am unable to switch on the device due to the broken hardware buttons.
I really doubt that.
Should have plugged it in when it froze if you knew your buttons are broken lol, at least then you might have been able to run some ADB commands to reboot it.
Hope its not your daily driver.
#include <std_disclaimer.h> /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. Hard. A lot. */