Hi guys, today I tried to install the nightly cm-13.0-20160301-NIGHTLY-hammerhead.zip of Cyanogenmod 13 for my nexus 5 (OTA update). I downloaded it and I have rebooted my phone for finishing installation. It didn't reboot in recovery, but there was a black screen (the lcd screen was turned on). I didn't touch my phone for about 15 min. to see what happen. I decided to reboot my phone because was stuck here, but there was the google logo (yes, it appears), and then the black screen. I can go to bootloader mode, but not in recovery mode (black screen in this mode). Adb isn't working (I have the last version from the SDK, and it always worked for me): if I am in bootloader mode my pc don't see my nexus 5. If I try to boot in "black screen mode" my pc see it but says unauthorized (before the brick debug mode was enabled). If I connect my phone to a power source, for one second show me the start of the "battery animation", then boot "normally".
I can't go to recovery; I can't reset from external or re-install the recovery. What can I do????
Thanks in advance..
Sorry for my bad english
Hi,
Try posting your question here:
Nexus 5 Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!
I solved
I solved by installing the adb and fastboot naked drivers andò flashing the factory image. Thank you anyway.
Related
Hello,
I am desperately looking for help with my daughters Moto G (first generation) being stuck in a boot loop with black backlit screen. The device is unrooted, the bootloader is locked, usb debugging is off, I tried fastboot mode with recovery and factory reset many times. The phone just keeps looping or gets stuck with the blue M. Adb recovery via cmd also does not work, the device is not listed. Do I waste my time or is there any other method I could try? I am very thankful for advice, please forgive my poor English...
regards
smallwood
P.S.: I also opened the phone and disconnected the battery before I retried to fastboot and recover - did not work.
Hi there,
I changed my broken screen on nexus 5 but after that unable to boot.
I can boot in recovery mode, actually I did a factory reset and also a fresh ROM installation via ADB.
The problem is still the same: the device seems to start normally, I see google logo etc but when I have to put pin to unlock SIM I see the screen for half second and then the screen go black.
Please help me!
Thanks,
Sandra
Hi, people. I hope you can help me.
My problem is that my rooted Nexus 7 (2012) with 3G and kitkat Stock Android suddenly turned into so called brick state. Only Google logo was appearing during the boot, and that will last forever. Then, just for interest, I tried to enter into the recovery mode (Clockwork Recovery v6.0.4.3 for tilapia), but the device did not go into it. The logo of CWM appeared in the middle of the screen and then the device reboots automatically showing the Google logo screen for several seconds and then going into recovery mode with the CWM logo appearing on the centre of the screen, and then reboot again. This recovery bootloop lasts forever or till the battery runs out. I tried to use
Code:
adb devices
and
Code:
fastboot devices
on my nexus 4, everythings works fine (meaning drivers are installed correclty). But
Code:
fastboot devices
for the nexus 7 outputs into
Code:
- waiting for device -
I tried to force the battery to run out and then tried to go into fastboot, but that did not help, the recovery bootloop appeared on its own again. Please, help me, I don't know what to do.
EDIT. I tried to pull out the battery for a half day (disconnect battery connectors) in hope that this will somehow reset the boot options, but this did not help.
Any thoughts?
Also, if the thread is not in the appropriate branch of the forum, please, let me know, probably at correct location I will find more help. Thanks.
EDIT2. I solved the problem by trying to enter the bootloader mode via adb. But to enter bootloader required a liitle bit of humoristic approach. I was pressing UP then ENTER to enter fastboot mode via termianl (#adb reboot-bootloader) for 5 to 10 minutes. When I managed to enter the fastboot, I flashed TWRP recovery for tilapia and the latest 5.1 Lopllipop But it seems there is a bug in the stock recovery because it does not work with NEXUS 7, the last two updates of Kitkat and Lollipop required to flash custom recovery, because the stock one did the bootloop on either Google logo or the animation of "beautiful" circles.
Thanks for reading, hope this might help someone.
from danik
Hi,
Glad to hear it solved
Good Luck!
Thread Closed.
So today after a doctors appointment i checked my phone to see the time. when i got home my phone was stuck in the google screen. i waited for about one hour as i had to go some place else. when i came home the phone was still in the google screen. at this point i could still go in to recovery mode. i searched a bit on the internet and then flash+unroot from the nexus toolkit from the stock 5.0.1 that i had to the stock 5.1.1 . it still didn't open. i searched some more and I found that i needed to enter recovery mode and wipe everything off. i tried making a backup with the toolkit but it didn't work. then i tried going to recovery mode and it also didn't work. next i tried to flash a 4.4.4 version as i saw it worked from someone but it is stuck at the point "waiting for device" .
i don't know what to do. please help me fast , i need to leave town in 4 days and i don't have time to take it to service and i don't have a back up phone either.
your help would be much appreciated
edit: when i try to enter recovery now the phone shuts completely down
edit2: my nexus toolkit apparently didn't flash properly so atm i have no os on my phone. (it is confimed by a twrp recovey i booted with the nexus toolkit) i am currently struggling to find out how to install and os without recovery mode or toolkit, help would be appreciated
edit 3 : if anyone is reading this, i manage to boot a recovery image but it only shows an android robot with a red exclamation mark, i cant use adb commands, it says device not found, still don't know what to do
if i try to install os with a flash-all.bat it says failed remote flash write failure, same as with the nexus toolkit
if i try to wipe cache from the trwp recovery it says taht i cant mount any partition so i think my memory drive is busted
Hello, thank you for using XDA Assist.
Try asking for help HERE and the Nexus 5 experts will help you there.
My guess is that you need to unlock the bootloader to use the flashall.bat
Have Fun!
Hi There,
Firstly I do apologize if this has already been posted, but I have searched through the forums and have not been able to find any specific information about this particular problem.
I have a Galaxy S3 (purchased in 2012) and a few weeks ago, the phone started to automatically switch off (when I locked it) and I would have to hold the power button for about 15-30 seconds for it to switch back on.
I checked the power button(to see if it was broken and pressing down all the time) but it seemed to be fine as whenever I pulled the battery (and put it back in after 1 minute) the phone would NOT come on unless I held the power button.
Also tried replacing the battery, but that did not seem to work.
About 1 week ago when i tried to turn my phone on, with the power button, but it would get stuck on the samsung logo screen (it was frozen, not looping).
I was still able to enter both recovery and download mode. So I tried wiping the cache but it did nothing.
Then I tired flashing the ROM with ODIN and it passed but it also did nothing (tried flashing multiple times all with "PASS" as well as wiping the data cache in conjuction with the flashing but to no avail).
Tried flashing it again with BL and it also passed, but now whenever I try to enter Recovery Mode or Turn the phone ON it would display a White Scrambled Screen which probably means eMMC failure.
Now for the problem:
How do I retrieve the information on the phone ?
N.B;
- I do not care about fixing the phone, only want the information
-I cannot enter Recovery Mode, BUT I can enter download mode.
-When I connect S3 to PC it is detected (In Device Manager it states "Samsung Mobile USB CDC Composite Device")
-I did have my phone password protected before this happened using the Pattern Password (you have a 3x3 Dot grid in which you can use to draw a line(s) which will function as a password)
-My phone is an S3 GT-I9300
-Never interfered with the ROM or software on the phone before this (was running the official android software from Samsung which I believe was Android Version 4.3).
-Have Tried EaseUs, but it does not detect the phone.
bossman111 said:
Hi There,
Firstly I do apologize if this has already been posted, but I have searched through the forums and have not been able to find any specific information about this particular problem.
I have a Galaxy S3 (purchased in 2012) and a few weeks ago, the phone started to automatically switch off (when I locked it) and I would have to hold the power button for about 15-30 seconds for it to switch back on.
I checked the power button(to see if it was broken and pressing down all the time) but it seemed to be fine as whenever I pulled the battery (and put it back in after 1 minute) the phone would NOT come on unless I held the power button.
Also tried replacing the battery, but that did not seem to work.
About 1 week ago when i tried to turn my phone on, with the power button, but it would get stuck on the samsung logo screen (it was frozen, not looping).
I was still able to enter both recovery and download mode. So I tried wiping the cache but it did nothing.
Then I tired flashing the ROM with ODIN and it passed but it also did nothing (tried flashing multiple times all with "PASS" as well as wiping the data cache in conjuction with the flashing but to no avail).
Tried flashing it again with BL and it also passed, but now whenever I try to enter Recovery Mode or Turn the phone ON it would display a White Scrambled Screen which probably means eMMC failure.
Now for the problem:
How do I retrieve the information on the phone ?
N.B;
- I do not care about fixing the phone, only want the information
-I cannot enter Recovery Mode, BUT I can enter download mode.
-When I connect S3 to PC it is detected (In Device Manager it states "Samsung Mobile USB CDC Composite Device")
-I did have my phone password protected before this happened using the Pattern Password (you have a 3x3 Dot grid in which you can use to draw a line(s) which will function as a password)
-My phone is an S3 GT-I9300
-Never interfered with the ROM or software on the phone before this (was running the official android software from Samsung which I believe was Android Version 4.3).
-Have Tried EaseUs, but it does not detect the phone.
Click to expand...
Click to collapse
Hello, the best solution will be to ask here Galaxy S III Q&A, Help & Troubleshooting since that guys know more about mentioned device.
Thank you
Paget96 said:
Hello, the best solution will be to ask here Galaxy S III Q&A, Help & Troubleshooting since that guys know more about mentioned device.
Thank you
Click to expand...
Click to collapse
Hi There Krusevac,
Thanks for the reply.
I will check it out.
Kind Regards,
B
bossman111 said:
Hi There Krusevac,
Thanks for the reply.
I will check it out.
Kind Regards,
B
Click to expand...
Click to collapse
No problem
Sent from my Nexus 5 using Tapatalk