Hello guys,
some days ago my phone was permantly booting up in the recovery mode nothing else was possible. As I was on road and couldn't access internet anywhere I just tried to do some wipes, which then made my phone not show anything. I guess the reason that it didn't boot up anymore was that the battery was fully drained. When I was finally back home I was able to charge my phone but then the following happend:
I can start my OPO, see the android logo and then it turns black, but it fully boots up. I mean I can even click the touchscreen and hear some touch reactions/sounds. Also I'm able to turn up/down the volume and hear my phone. Furthermore I'm also able to do the "V-gesture" to turn on the flashlight. When I boot up into fastboot mode I also see the message "fastboot mode" + the little cyanogen face.
All in all everything seems to work, aside that I dont see anything else than dark after the logo.
I tried flashing new roms, stock reset, like seriously anything, but I can't get my phone to work probably again.
Does that mean that my phone got some hardware problems, maybe the touchscreen?
Help is appreciated, thanks in advance!
btw: English isn't my first language, so please excuse any mistakes.
You'll have to try flashing completely stock CM11 rom or CM12 rom, img by img in fastboot..modem, boot, system etc. I helped a friend who had this kind of problem. Probably not the cleanest way, but at least it works.
Already did that 3times using different methods. Stock CM11, CM12 and colorOS
I have a similar problem, did you manage to fix it? And if so, how?
Thanks,
Capelare.
Related
Hi,
I recently rooted my htc vivid and i tried to flash a rom. However, the rom didnt work and my phone isnt working. The phone's bottom touch-buttons vibrate when touched, but the screen remains off no matter what i do. What's wrong with it?
EDIT: I got it to boot, however, its stuck on booting, the boot logo just keeps on popping up. What should I do?
any luck?
sounds like you need to try and flash the rom again. this may or may not be a know issue with the rom. check the thread where you got the rom. I had to flash twice with the same rom the last time i did it (unrelated device)
May have to hold the buttons in a specific sequence to get back to the debug mode.
also have a look through this thread:
http://forum.xda-developers.com/showthread.php?t=1433149&page=2
Hello I am searching for help. The problem is that my galaxy s2 i9100 stopped working properly. It started like this maybe I took out the battery or something I don't remember and then I turned it on the phone wouldn't boot. I thought maybe my android operation system got bricked so I decided to re flash it but as I can remember the phone wouldn't go in to download mode but some how I managed to reflash the firmware but then phone booted it just froze and then I pressed lock button the phone screen would go black and reboot. After installing cyanogen mode 11 the phone would boot and it could be used again until pressed the lock button it would go black and reboot so I have been reading forums and found problems like boot loop corrupted mmc or something else corrupted and I don't know what the real problem is because the symptoms are like boot loop or corrupted mmc or soft brick. I have already tried other kernels other android versions clock work mode
migimantas said:
Hello I am searching for help. The problem is that my galaxy s2 i9100 stopped working properly. It started like this maybe I took out the battery or something I don't remember and then I turned it on the phone wouldn't boot. I thought maybe my android operation system got bricked so I decided to re flash it but as I can remember the phone wouldn't go in to download mode but some how I managed to reflash the firmware but then phone booted it just froze and then I pressed lock button the phone screen would go black and reboot. After installing cyanogen mode 11 the phone would boot and it could be used again until pressed the lock button it would go black and reboot so I have been reading forums and found problems like boot loop corrupted mmc or something else corrupted and I don't know what the real problem is because the symptoms are like boot loop or corrupted mmc or soft brick. I have already tried other kernels other android versions clock work mode
Click to expand...
Click to collapse
I have found that my emmc has the insane chip bug. The phone boots normally with cyanogen mode 11 but then it goes to sleep mode or I press the power button the screen goes black and the phone restarts. I have tried siyah kernel to try dual boot but then I flash siyah I cant get into recovery.
I think you should flash latest STOCK ROM with Odin, and then follow available custom rom instructions on xda...
Test if the stock rom will work for you, boot your phone etc... Try to use it a few days. If everything is OK, proceed with
further procedures...
twinsen.net said:
I think you should flash latest STOCK ROM with Odin, and then follow available custom rom instructions on xda...
Test if the stock rom will work for you, boot your phone etc... Try to use it a few days. If everything is OK, proceed with
further procedures...
Click to expand...
Click to collapse
I have already tried this but with the stock rom phone boots but at the section where I have to chose language I jus freezes stops working
So I think it is a hardware problem. Phone on stock rom shouldn't freeze on language selection. Something is wrong. If you are on warranty, let them fix it for you, if you are not, try to fix it in some phone repair point. I'm sure you can stop your attempts. It will not be better for now.
twinsen.net said:
So I think it is a hardware problem. Phone on stock rom shouldn't freeze on language selection. Something is wrong. If you are on warranty, let them fix it for you, if you are not, try to fix it in some phone repair point. I'm sure you can stop your attempts. It will not be better for now.
Click to expand...
Click to collapse
Take it straight away to the official service centre
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
with wugfresh nexus root toolkit click on the button "soft-bricked"(flash stock + unroot) or something like that to restore the phone. After that try another time to unlock and root with a custom recovery (for example twrp).
When nexus root toolkit installing the original lollipop rom, look the "dos window" to see if the software shows errors, because sometimes the process ends without a real restore.
If you have other problems, please post a screenshot.
Fenix46 said:
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
Click to expand...
Click to collapse
Yes I was using a custom rom, but I not even reached the step where a was supposed to use the rom, I was steel still cleaning the divece.
Here is a photo from the screen I'm stuck in:
eeee.... I'll find a wint to send the photo to this forum ^^" wait
Moto G XT1032 Bricked (?)
Hey! I'm gonna start off by saying I'm pretty much completely clueless when it comes to rooting, flashing, or doing pretty much anything with phones, so if this is a well known problem with an obvious solution and everything I dont know about it, I've been searching for ages to try and find something.
Anyway, the other week I was using my phone as normal, and it stopped responding to anything, so I held the power button to reboot it. Now, the phone won't boot beyond the blue Motorola boot logo no matter what I do. I've tried booting into recovery mode in order to wipe the partition cache and format it, but neither options seem to do anything after waiting about 45 minutes each for something to happen. Any tutorial I've found on the internet ends up not working for some reason or another half way through the steps. If anyone knows how I can sort this out it would be awesome.
I was on Lollipop 5.0.2 (i think), but I took it to a shop and I think they tried to flash the stock software on it but it still didn't fix it, but now I don't know what version of android my phone is running at the minute. I know that the bootloader menu is on version 41.18 if that means anything.
Cheers!
Hello!
I recently flashed my Moto G with the unofficial LineageOS 16 rom by allstargaurav. Kudos to him for his work.
I unlocked my bootloader, got TWRP, flashed the rom, flashed Gapps,Magisk and started using it normally.
One night, after using it with the battery at 30%, I left it as it was and did not charge it.
The next day, I saw that it was not booting up at all. I plugged it in and the white led light started and did not go off.
The light was constantly on. I searched on google to no avail.
Nothing works and I have pressed the power button and power+volume down for more than 5 minutes.
I cant get to the fastboot menu or the TWRP, the phone doesnt power on at all so I cant do anything or get a logcat.
Please help!!!!
I also got the watchdogs boot animation. That is all I have modified.
Please tell me what is wrong and how to rectify it.
Please help quickly.
I am at wit's end and helpless. I should also mention that this was my first time flashing a rom on any device, but I followed the instructions very carefully.Before this the phone was on stock Lollipop rom, stock recovery and locked bootloader.
Thanking anyone who helps or even replies in advance.
:crying::crying::crying::fingers-crossed::fingers-crossed:
Also
Alphacube111 said:
Hello!
I recently flashed my Moto G with the unofficial LineageOS 16 rom by allstargaurav. Kudos to him for his work.
I unlocked my bootloader, got TWRP, flashed the rom, flashed Gapps,Magisk and started using it normally.
One night, after using it with the battery at 30%, I left it as it was and did not charge it.
The next day, I saw that it was not booting up at all. I plugged it in and the white led light started and did not go off.
The light was constantly on. I searched on google to no avail.
Nothing works and I have pressed the power button and power+volume down for more than 5 minutes.
I cant get to the fastboot menu or the TWRP, the phone doesnt power on at all so I cant do anything or get a logcat.
Please help!!!!
I also got the watchdogs boot animation. That is all I have modified.
Please tell me what is wrong and how to rectify it.
Please help quickly.
I am at wit's end and helpless. I should also mention that this was my first time flashing a rom on any device, but I followed the instructions very carefully.Before this the phone was on stock Lollipop rom, stock recovery and locked bootloader.
Thanking anyone who helps or even replies in advance.
:crying::crying::crying::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Being unsure what the problem is, I also followed FabioSan's guide on unbricking the phone, but I got stuck on the part where we go to the device manager console as my PC would not recognise the phone no matter what I did.
Also, the warranty has expired long ago as the phone was bought in 2014 and it was only a 1year warranty.
Therefore, I am considering giving the phone to the moto support centre. I will also try replacing the battery as it may be a battery problem considering my symptom of the white light does not fit any hardbricked phone's symptoms. Will notify if it works.
Till then, please help and suggest what the problem might be.