I was using havoc os with the last beetle kernel, but one day my phone suddendly stopped working. When I try to boot it up, the screen stays black and it vibrates once in a while. Once it stops vibrating i can connect it to my computer and see internal storage, i have access to adb commands but never managed to go fastboot mode. I'm prettry sure this is not hardware problem because absolutely nothing happened before it stopped working. It was just standing in my pocket. Can somebody help?
oh, i managed to access fastboot, can somebody help?
i managed to flash miui rom, now the phone is making sound, but the screen is still not showing anything
Related
Hi Guys,
I have tried to install a CM mod on my Motorola Defy as illustrated here. The problem is that despite the phone had been rooted, I had some problems with ClockWorkMod and rebooted my phone in recovery mode using the application that ships with the phone. I did remove the Cache and Factory settings and ran the zip file.
The problem is that upon restart, the phone kept rebooting itself, that is, I kept seeing the Motorola logo for a couple of minutes, and then, the phone reboots and the process is repeated.
Now, out of the blue, the phone is not even turning on. What I have is a small white light that turns on whenever I connect the phone to a laptop via usb. Any idea on how I can get the phone working? At the moment I do not really care about what OS version, as long as it runs.
Thanks in advance
Edit: There seems to have been an issue with the battery, I have managed to load up the phone to recovery mode. Can anyone show me how can I install a fresh Operating System? I seem to only have access to the phone's boot up screen. Also, the laptop does not seem to be able to connect to the phone via usb.
So I managed to install the adb drivers for my OPO and then used the OPO Toolkit to reboot into fastboot mode. But the phone just shows a black screen. I tried manually booting into fastboot but it doesnt work. Just shows a black screen, windows detects something but seems like it gets disconnected immediately. The cable is working fine, I checked that already.
I unplugged the cable and booted into fastboot manually and it works but as soon as I plug the cable back in, the phone just shuts down I think and returns to the black screen. I tried searching but couldnt find a solution. Any idea where I'm going wrong?
PS: Fixed the issue by rebooting the phone to recovery and wiping everything.
Mods, can you please delete this?
Problem solved. Thread closed.
Hey guys,
I don't know whether you're able to help me.
I was a happy user of a Mi4, 16GB with latest CM13 nightlies installed and TWRP latest version working fine, too. After one of the latest updates of a CM13 nightly, my phone went into keylock and from there did not quite awake. It is in a strange state: The phone is working in principal, for example did I shoot some photos (by double clicking the on/off-button) which from there went up to my Google Photos account. Problem was: The screen stayed black, only the backlight did work. I tried to set up the phone newly, but couldn't manage to get into TWRP. Then I tried to start from scratch by installing a MIUI fastboot rom, still the phone did not awake. Now I followed this instruction:
http://en.miui.com/forum.php?mod=viewthread&tid=226426
Everything which is described under "Part 1" worked like a charm. Now the phone is hanging on the charger, the led is constantly yellow and the backlight is on, sometimes the vibration is going. I tried to boot into fastboot which is actually working (it appears on entering "fastboot devices" in windows cmd), but the screen doesn't show that fastboot image, still backlight is on.
As the phenomenon of working backlight with a dead screen seems to appear in CM13, in fastboot and with Fastboot Rom installed, what could be the reason for this!? Is the phone broken you think?
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
AMpageg2 said:
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Sounds like a Hardware issue? Sorry to say what your saying doesn't add up and or make sense. Fastboot should work no matter what even if you soft brick it and mess up recovery. I suggest letting the power fully drain maybe and google how to fast boot in case you are doing it wrong.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Click to expand...
Click to collapse
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
AMpageg2 said:
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
Click to expand...
Click to collapse
I agree with what @Shinobi_warrior said.Seems like you just have a soft brick,so you should be able to boot into fastboot mode without any issues.Are you sure you're doing it the right way? Did you try draining battery completely and then booting into fastboot(yes,you don't need much battery to boot into fastboot mode)?
Well I was finally able to get the device detected by ADB, but it just shows as offline. I attempted to use the repair kit and nothing seemed to happen. I also attempted a different tool (https://forum.xda-developers.com/on.../oneplus-one-toolkit-manudroid19-gui-t2807418) and then booting into either fastboot or recovery that way, a terminal window pops up and quickly disappears, and then nothing else happens. I still see the TugaPower boot logo and it still goes to the blank black screen after this.
Recently had issues with my G7 Power and it seems to be soft-bricked. I was using an app and the app in question usually has the occasional stutter but then things resume to normal a second later. This is what happened yet this time the phone froze and was completely unresponsive. I held the power button down, turned it off and back on and it seemed fine but for whatever reason it got stuck on the Verizon loading screen which never happens. Turned it off and on again and it got stuck on the Moto animation so I held the power button down again. The phone shut off and refused to turn on again.
Eventually I ended up getting into fast boot (initially tried getting into fast boot many times with no success, no idea why it suddenly worked that time) and reset the phone through there and it would still get stuck on the Verizon loading screen. Kept turning the phone off and returning it to fast boot to repeat the process which was probably a stupid mistake on my part as the phone proceeded to shut off like expected but this time I couldn't get into fast boot anymore at all, even when keeping it on the charger that came with the phone.
LMSA was looking like the perfect solution but my PC isn't recognizing the phone as a drive so I don't think any sort of software made for instances like this are going to work unless there's something I'm doing wrong here. I can't get into the phone to enable USB debugging either.
Any recommendations as to what I should do? It's looking like sending it back to get it fixed is my only option here. Never had any issues with the phone until now.
Re-flash Stock ROM.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP>
jwoegerbauer said:
Re-flash Stock ROM.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP>
Click to expand...
Click to collapse
My PC won't recognize the phone at all, would this still work? Would it also completely wipe the device's memory?