Develop Bugs

HTC One X stuck in bootloop /bricked/

Hi,
last time I flashed FlexOS and now I wanted to go abck to HD Revolution. I flashed kernel and then accidentally rebooted the phone. It got stuck in bootloop and I can't even enter fastboot menu. I don't know if I broken volume key somehow (it was working I guess, last time I got to recovery via menu). My computer doesn't see any ADB or fastboot devices, neither I can go to fastboot on the phone. What can I do?

Renioo said:
Hi,
last time I flashed FlexOS and now I wanted to go abck to HD Revolution. I flashed kernel and then accidentally rebooted the phone. It got stuck in bootloop and I can't even enter fastboot menu. I don't know if I broken volume key somehow (it was working I guess, last time I got to recovery via menu). My computer doesn't see any ADB or fastboot devices, neither I can go to fastboot on the phone. What can I do?
Click to expand...
Click to collapse
Nothing if you can't go in fastboot to flash the boot.img or the rom from recovery

No options to force the device to enter fastboot? It is recognized by computer, just not by fastboot.

Renioo said:
No options to force the device to enter fastboot? It is recognized by computer, just not by fastboot.
Click to expand...
Click to collapse
If you have enable debuging you can use adb reboot bootloader

When I reboot into recovery TWRP gets stuck in a splash screen loop.

Hello, ever since I flashed the 14.1 nightly CM ROM, TWRP has no longer worked. I have tried reflashing the compatible MM BL and also tried a normal TWRP using fastboot, and nothing seems to fix it. Whenever I reboot into recovery mode, it just flashes a gray screen and never gets out of the loop. My phone can start up into normal mode fine, its just recovery that does not work.

https://drive.google.com/open?id=0B72QQTXqZSRweG5sYW0taFoycFE
download above files and extract files. go to MM bootloader folder. now reboot your phone into fastboot mode and connect to PC. now run upgrade.bat... once it finishes transfer file. and phone reboots the bootloader. now run twrp.bat. now as transfer finishes. now very important do not boot your phone to normal os.. find option for recovery mode and reboot into recovery. you will get into recovery..

sukhwant717 said:
https://drive.google.com/open?id=0B72QQTXqZSRweG5sYW0taFoycFE
download above files and extract files. go to MM bootloader folder. now reboot your phone into fastboot mode and connect to PC. now run upgrade.bat... once it finishes transfer file. and phone reboots the bootloader. now run twrp.bat. now as transfer finishes. now very important do not boot your phone to normal os.. find option for recovery mode and reboot into recovery. you will get into recovery..
Click to expand...
Click to collapse
are you have bootloader for z008 sir ? thanks

sandycogan said:
are you have bootloader for z008 sir ? thanks
Click to expand...
Click to collapse
i will try to post soon

lineage 14.1 sumire on xperia z5 dual nightmares. No root. Recovery mode inaccessible

After flashing the z5 dual with lineage-14.1-20180223-nightly-sumire-signed there is apparently no way to get root access back or even enter recovery mode. The advanced restart features do NOT work it boots back into the OS. AFAIK the hold volume-down and power button method does not work, though I was never able to get that trick to work on the dual, period. adb reboot recovery boots to the OS. Nothing works. Fastboot boot twrp.img boots to OS nothing works. I can't even remove lineage because flashtool is denied root access despite adb root access being turned on.
EDIT: I managed to root the device again, however the lineage recovery and bootloader power button options still do not work. This is good enough I guess.

Try fastboot flash twrp.img

kurtn said:
Try fastboot flash twrp.img
Click to expand...
Click to collapse
Thanks for the reply, did you mean fastboot flash recovery twrp.img? I retried that again just now followed by fastboot reboot and it boots to the OS like normal. There was one small difference however, normally there is only a white experia screen while booting but that time it had the animated blue lineage(?) logo.

No OS is installed. Moreover recovery cannot be accessed. Nor can flash it via adb.

Previously I was using Ressurection Remix treble rom which is based on android 9 pie. I went to TWRP and wiped the OS. Then I tried to install a new rom called Dot OS. But it showed error 7. So I flashed Vendortofactory zip within twrp and without rebooting again into TWRP I flashed a new TWRP image within TWRP by selecting Recovery mode. After that I cant boot into TWRP and as already my OS is gone I also cannot boot into any system. Moreover my device is not getting detected in my PC. I cannot install TWRP by writing commands in cmd, while the phone is in fastboot mode as the device is not getting detected in my pc. Really it is urgent. I will be glad if someone helps me. Thanks in advance.

What is the present booted state of your device? Are you in twrp, or bootloader. Most of the time you can keep on pressing the power button. When it boots into a message about unlocked bootloader, press volume button to select recovery and it will boot into twrp

You should be able to boot in fastboot mode without recovery nor os, maybe your drivers are not working on windows? Try different usb ports, check if the display says "bootloader" or something. If nothing works try the usb shunt, this device is literally 'unbrickable' if it's working properly.

Watch this video(https://www.youtube.com/watch?v=DexLELi04XY) and then you will be able to detect your phone in your pc in qcom 9008 mode , then use qfil to flash ZUI firmware ,there are plenty of tutorials on the internet for that ,then follow the proper procedure mentioned in DotOs thread for flashing the new rom .
Hope it helped .

If you don't want to flash the firmware and all long process just follow the following steps
Enter in to the boot loader make sure you installed all the drivers in to pc then open cmd windows in adb fastboot folder and enters the following cmd into the cmd
Fastboot -i 0x2b4c devices this will detect your device
After that enter
Fastboot -i0x2b4c flash recovery recovery name.img
And boom you are good to go flash the rom of your choice and enjoy
For this process you need following files
Adb and fastboot devices
Drivers of zuk z2
Latest recovery and place revovery image file into the adb and fastboot folder if you are confused about anything pm me i am not the expert but i faced simillar problem and solved by this method

yashpatel1221 said:
If you don't want to flash the firmware and all long process just follow the following steps
Enter in to the boot loader make sure you installed all the drivers in to pc then open cmd windows in adb fastboot folder and enters the following cmd into the cmd
Fastboot -i 0x2b4c devices this will detect your device
After that enter
Fastboot -i0x2b4c flash recovery recovery name.img
And boom you are good to go flash the rom of your choice and enjoy
For this process you need following files
Adb and fastboot devices
Drivers of zuk z2
Latest recovery and place revovery image file into the adb and fastboot folder if you are confused about anything pm me i am not the expert but i faced simillar problem and solved by this method
Click to expand...
Click to collapse
This assumes u have upgraded bootloader to 4.4 kernal.
U can still boot into twrp.. When the phone is booting up press vol up key and select recovery.. From there boot into twrp. There select f2v or v2f .. Then flash twrp which u want to flash.. Reboot to recovery.. U will get promp no os installed.. Ignore and reboot to recovery . Then again d9 f2v or v2f depending on what rom to install.. Again reboot to recovery... Then flash rom of ur choice.
This procedure is needed when changing from vendor to factory and vice versa.

sanjay.2704 said:
This assumes u have upgraded bootloader to 4.4 kernal.
U can still boot into twrp.. When the phone is booting up press vol up key and select recovery.. From there boot into twrp. There select f2v or v2f .. Then flash twrp which u want to flash.. Reboot to recovery.. U will get promp no os installed.. Ignore and reboot to recovery . Then again d9 f2v or v2f depending on what rom to install.. Again reboot to recovery... Then flash rom of ur choice.
This procedure is needed when changing from vendor to factory and vice versa.
Click to expand...
Click to collapse
I don't understand what you are talking about as i say i am not some kind of technical expert i am here help regarding this i faced similar situation where i am not able to enter into recovery and also not able to enter into the os and when i restart the phone it automatically boot into fast boot mode what ever option i select and i solved my problem by this method

Lenovo TB3-730X keeps rebooting and can't enter recovery mode nor connected to PC

Hi all,
I have a Lenovo TB3-730X tablet.
Recently I wanted to flash a custom ROM but it turned out it was not compatible and the tablet was messed up.
What I did before reaching at this messed up state was:
1) Flash TWRP recovery
2) Copied the custom ROM into SD card and installed it, the installation failed and boot failed. The tablet stuck in the logo screen forever
3) I tried to install the stock ROM back using PC and SP Flash Tool but the latter never managed to connect to my tablet.
4) I manually copied the system.img and boot.img from stock ROM into SD card and tried to install them manually using TWRP by selecting "System Image" and "Boot" partitions respectively. After this and before rebooted the tablet, TWRP reported that "No OS is installed". I went ahead and rebooted the tablet anyway and now it keeps restarting. It shows the logo screen for few seconds and then restarts over and over again. I cannot connect to TWRP recovery mode anymore as the Volume-UP / Volume-DOWN + Power button are being ignored. I am not sure if the TWRP was gone after flashing the boot with boot.img. Also the tablet cannot be connected to the PC at all because it keeps restarting and it doesn't get stable to the logo screen as before so that the USB connection cannot be established. This means I cannot use "adb" from PC to connect to recovery mode using "adb reboot recovery" command
I really stuck here and would appreciate any help.
Thanks in advance!