Android not turning on after installing custom recovery. - Android Q&A, Help & Troubleshooting

Hello there
I want to install custom rom on my android (android 5.1 cynogen 12.1) for that i flashed custom recovery on my android but after many tries it was not working only company logo appear. my friend suggested me to flash custom bootloader and i did that. but after that my mobile is neither booting or going into recovery mode. Usb debugging is also turned off.
Any solution??
I can go to flashboot mode but my computer is not recoganising my device. win 10

Related

[Q] XOLO Q500 Bricked. Qualcomm Snapdragon MSM8225Q device.

Hello guys, there is no specific forum for this device, that is why have started this new thread.
My xolo q500 is bricked. It stucks at the logo and doesn't go further. I was trying to install CWM recovery. But niether CWM nor TWRP not available for my device so i tried to flash CWM of some other device from the rom manager. It was of xolo q700. After flashing my device got shut down but stcuked at the boot logo when restarting.
All i wanted to do is to flash a custom rom. I rooted. I tried to flash it via the default recovery but it was not succesfull i dont know why. I googled and came up to know that i need to install custom recovery like CWM or TWRP to successfully flash custom roms. So when i flashed cwm of xolo q700, this happened....... It was all because of that other device's CWM..... and that recovery.img file was placed in the internal memory. So overall, i flashed it from the internal memory.............
Now my phone niether boots up normally nor boots in the recovery menu. It stucks at the xolo logo. I googled but i found unbricking methods for mediatek devices via sp flash tools but my device has Qualcomm Snapdragon chipset , so that didn't worked. Please help me how can i unbrick my device? Is there any method to unbrick qualcomm based devices?
I had that thought of not installing stuff of another device. But i niether found any custom rom nor recovery for this device. So i decided to just use another device's stuff. Yeah i know that totally crazy idea... but.....whatever when i plug it into PC it does not detect anything but when i plug it in pc after removing battery, its LED starts blinking. When this happened first time... Something like 'Qualcomm msm' was installed but nothing thereafter......

Remotely enable USB debugging using PC for stucked phone

hello,
Phone Model: Wing M45
Specification: Android 4.2.2.
MT6572 1.3ghz
256mb RAM
The screen on my phone has stucked on manufacture logo and process can't go further every time i restart it.
The problem is that i can't even install custom ROM. Because phone is not in USB Dubbing mode and not in Developer option.
So when i install ROM manager like CWM it gives error like"partition 'recovery' not support flash".
Now the question is how to root the phone or enable USB Debugging from pc in fastboot mode.
Which recovery please
so you have custom recovery or stock recovery?
i have custom rom
I have custom ROM but not able to install it....
Reason is posted above....
custom rom? -_- I asked recovery not rom
yes i have recovery
yes i have recovery...

Stuck in bootloop and usb debugging off

Hi people,
I have installed TWRP with CF-Autoroot in the Android 5 Lollipop (and everything was ok), then I've replace It with the latest Android 6 Marshmellow and when I've tried to boot into Recovery-Mode through the TWRP application, the phone stuck in boot loop with a red string "recovery is not seandroid enforcing", so.. now I can't back to normal mode and I'm only able to enter the Download-Mode but I forget to enable the USB Debugging in the Developer Area and Odin/Adb are unable to see the attached device, is there any trick to solve my problem?
Edit: Thanks to jcadduono from #xda-devs on freenode network!
The problem is that the TWRP doesn't support the bootloader of Android 6.0, so I've downgrade the BL to Android 5.0, reinstalled TWRP and flash the BL of Android 6.0 again.
Before I enter to Recovery-Mode I must wait the TWRP kernel updates or the phone already stuck in boot-loop.

Does this mean i bricked my device? Help/clarification?

Device:
Lenovo A916. (I don't think that matters for this isue though)
Issue:
Since the one and only firmware lenovo released was kitkat 4.4.1, i wanted to update to 5.1.
Rooted phone, managed to install TWRP, flashed to lollipop 5.1, so far so good. But had some problems with the custom ROM (no SIM detected), so i decided to download a stock ROM recovery and installed it.
When rebooted device i was stuck on CWM and custom rom installations give me errors and can't access USB storage on PC.
When i try to install a custom rom i get a no file_contexts warning and it fails.
Is there a way to fix this (maybe enter again to TWRP so i can flash a rom again? i don't know) or is my phone ruined forever? It was on USB debug mode, if that helps.
For some weird reason, it turns on by itself when connected via USB cable.
Any help would be greatly appreciated!

Is the device dead? No fastboot no twrp

Hello, after installing miui 11, I did not like the root work .... and I installed the rom fastboot. After several procedures, the device stopped responding and did not show fastboot or recovery. Is there a solution to this problem

Categories

Resources