Recently all of a sudden my phone(Realme X2) got stuck in bootloop. It happened all by itself, phone got drained out and I connected it to the charger after 15mins and in no time it was in bootloop.
Now I'm trying to access the fastboot but I'm unable to unlock it as my phone is stuck in this bootloop.
I tried using adb commands but its not reading, and in my device manager the port section driver also keep on looping. I tried to access the stock recovery which is really of no use.I tried all the ways out by my side none is working.
Any idea how I can flash my device and get it back to usable?
Hint: Add Realme X2 to this thread's title thus mainly owners of such phone get addressed.
will do
Related
Hi all new here,
Just got my OnePlus One and updated to cyanaogen 12, while simply using the phone it crashed forcing me to reboot the device, after this the phone would not turn on (asssuming it was hard bricked), luckily following some guides on this forum I was able to get it back up and running again.
I reflashed 12 after and exactly the same thing has happened this time, unfortunately I am unable to unbrick it using the ColorOS method like before, the phone just remains dead and I cannot get it into fast boot mode to rectify the problem.
I am out of luck already? OnePlus seem absolutely useless over support and just plain rude.
EDIT:
I am now able to get into fastboot, but still cannot see it on screen, but fastboot is appearing in device manager as windows ADB, what can I do from here?
Hey guys, I've got a Kyocera Brigadier and I decided to change the runtime from Dalvik to ART. Now the phone is stuck on loadscreen and I don't know how to fix it. The phone is rooted using the KingRoot app, but I don't know if that would help in any way.
Please help me guys!
Similar Issue
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Ornias Abezethibou said:
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Click to expand...
Click to collapse
I have the same problem. I bought a new a Brigadier that was on 4.4.2. I rooted with Kingroot ran update and now my phone will not boot past Kyocera screen. It goes black with the back light on. Did factory wipe and still nothing. I am shocked that KK has killed yet another phone of mine. I very much dislike KK ROM. What did you find out?
Hello.
First of all, i'm sorry if this question have been asked before. Believe me, i've tried searching even through Google's 2nd page but still no luck in finding answer.
I had a OPO 64GB version. It was working fine until i decided to do ROM update. My previous working ROM is "CM13-20160812-somethingsomething-SNAPSHOT.zip". It is rooted with Xposed installed
I tried to update it using TWRP. the update is "CM13-20161216-somethingsomething-SNAPSHOT.zip". It got stuck at "Patching system image unconditianally"(probably wrong spelling there) for more than one hour. So, i decided to force reboot it and it is now stuck at boot logo(not bootanimation)
Thing is, i cant get it into fastboot, nor recovery. it just stuck there and i've tried to Power Cycle but still no result. I tried to plug it into my computer and it does detect it in "Device Manager" under "Portable Devices" with name "A0001".
I wonder if it soft brick or hard brick. I'm asking brilliant mind in here, if there's a way to restore it. I just revived it from broken screen since 2016(talk about bad luck) and i don't want to completely replace as the device is still in good condition.
Also, if there's no other choice then i had no other way than to follow this guide here, which completely unbrick my phone(also losing me 30+ apps)
http://www.androidbrick.com/unbrick-oneplus-one-two-3-3t-qualcomm-hs-usb-qdloader-9008/
or
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Nevermind. i got it to work by installing QPST driver. for some reason it enable adb at boot logo(yes at boot logo). got into recovery and recover my system partition(which is broken).
I ask the mod to delete this thread. Thank you
Guys, my Yureka got hardbricked.
I updated to CM12 by downloading zip file and flashing from stock recovery. But the update sucked big time, lags, battery heating, etc. so i thought of reverting back to CM11 by fastboot method and now phone is not booting up, not able to go in recovery mode, not able to go in fastboot mode, not charging, i mean nothing! after searching internet, i came to know that u cannot downgrade from 64bit(CM12) to 32bit(CM11). I tried to recover by following this "https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040" but device is not getting detected in device manager, so couldnt proceed further. tried calling Yu customer care, but they wont even pick up the call. please help!
Recently all of a sudden my phone(Realme X2) got stuck in bootloop. It happened all by itself, phone got drained out and I connected it to the charger after 15mins and in no time it was in bootloop.
Now I'm trying to access the fastboot but I'm unable to unlock it as my phone is stuck in this bootloop.
I tried using adb commands but its not reading, and in my device manager the port section driver also keep on looping. I tried to access the stock recovery which is really of no use.I tried all the ways out by my side none is working.
Any idea how I can flash my device and get it back to usable?