Hey guys, got a nexus 6p today and first time powering up and charge was OK... Then connected to pc to unlock and root, but forgot to toggle the device unlock under developer settings. So bootloader unlocking failed. I rebooted to system to toggle the settings but the screen won't light up now, but the phone will boot up all the way.
The screen will not light up when I charge it, boot into bootloader, no Google splash screen, or Google bootani. So nothing I do will light up the screen... The phone boots up and connects because I hear notification alerts for email and texts..
II tried factory reset, but fastboot format failed because I need to unlock bootloader first, but can't. I can't get into recovery to wipe because I can't see anything to navigate to recovery. So I either have a dead screen, or something else... I'm open to suggestions before returning...
Thanks
chewy74 said:
Hey guys, got a nexus 6p today and first time powering up and charge was OK... Then connected to pc to unlock and root, but forgot to toggle the device unlock under developer settings. So bootloader unlocking failed. I rebooted to system to toggle the settings but the screen won't light up now, but the phone will boot up all the way.
The screen will not light up when I charge it, boot into bootloader, no Google splash screen, or Google bootani. So nothing I do will light up the screen... The phone boots up and connects because I hear notification alerts for email and texts..
II tried factory reset, but fastboot format failed because I need to unlock bootloader first, but can't. I can't get into recovery to wipe because I can't see anything to navigate to recovery. So I either have a dead screen, or something else... I'm open to suggestions before returning...
Thanks
Click to expand...
Click to collapse
Sounds to me like a hardware failure, almost definitely completely unrelated to what you were doing at the time. You'll have to have it replaced.
Yea, I was hoping it was something else... I just returned it... Now I have to wait for them to send another one.
Thanks for the reply :good:
Heisenberg said:
Sounds to me like a hardware failure, almost definitely completely unrelated to what you were doing at the time. You'll have to have it replaced.
Click to expand...
Click to collapse
Related
Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
possibly?
Did you just update and it got stuck at the booting up????
opeller said:
Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
Click to expand...
Click to collapse
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
ChainFires Son said:
Did you just update and it got stuck at the booting up????
Click to expand...
Click to collapse
No, it did not occur after an update.
theminikiller said:
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
Click to expand...
Click to collapse
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Follow this guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
You can download factory images from here https://developers.google.com/android/nexus/images
opeller said:
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Click to expand...
Click to collapse
First we should check if you can boot into the bootloader at all. First turn the device off. Then hold down both the volume buttons and then press and hold the power key. Keep holding all the buttons until you see some different colored text. If that happens we should be able to install a factory image, if it still gets stuck on the Google logo I unfortunately don't have any more ideas.
Tried pressing both volume keys and power button. Google logo show for a second, then black for 2 second, thank flashing red notification light every 1/2 second until I let go of the buttons.
When I release the buttons, the phone goes back to charging battery screen.
I see people suggesting that the red light flashing means a battery problem, but the device keeps trying to boot up while it is not plugged to the charger, unlike what happened to them
Any Ideas why this is happening or what the red light means in this case?
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
harishmenace said:
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
Click to expand...
Click to collapse
Oh it was just volume down, not both. Heh, sorry.
Use the Nexus Root Toolkit (NRT), it's the easiest way to unlock, root, flash and manage your SuperUser needs!
http://www.wugfresh.com/nrt/
Not sure, but maybe?
You can try using the nexus root kit & unlock your bootloader and see if a factory reset can work. If it does you can always relock it again ☺..Flashing a factory image can work too also ...
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
I'm you can't get into the bootloader then I am unfortunately not aware of any way to help you. If you can't even get into the bootloader I think it is a high probability that it is a hardware problem.
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
opeller said:
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
Click to expand...
Click to collapse
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
Bus 001 Device 005: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode),
Click to expand...
Click to collapse
on windows (XP/Vista/7)
Qualcomm something QDL Mode or something like this on "device manager"
Click to expand...
Click to collapse
there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
x1123 said:
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
on windows (XP/Vista/7) there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
Click to expand...
Click to collapse
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
opeller said:
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
Click to expand...
Click to collapse
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
That sounds like the battery is completely empty. Put the device on charger over a night and try then to boot into the bootloader.
Once I had these symptoms (red light flashing) on my N4, it was enough to charge the battery for one hour. Then it booted properly. It's worth trying.
x1123 said:
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
Click to expand...
Click to collapse
How do I do that?
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
redbay1 said:
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
Click to expand...
Click to collapse
That is the norm for fastboot, it doesn't go past that screen.
It may not make a difference, did you try to boot to recovery via Power+Volume Down buttons?
Greetings Khaos64,
Yes, I've tried booting with Vol-Down+Power but the phone does not start.
With volume-up+power, I get the Fastboot splash screen but the phone does not respond to any input.
I tried selecting "bootloader" from the reboot menu but I get the same thing: Reboots and after a second, the phone reboots again normaly and into OxygenOS.
Is there a way to verify if the bootloader or recovery is corrupt and maybe reflash the stock recovery onto the phone?
Thanks for your input!
You may just want to go straight to oneplus support since everything is stock and only 2 weeks they should be able to get you updated or replace it.
If you'd like to be more hands on... maybe something below can help.
So your phone isn't recognized/no commands acceptred from your computer when booted to fastboot?
Such as unlocking your bootloader and booting into twrp... "fastboot boot yourfilename.img" or maybe flashing it.
Make sure OEM unlocking is selected in Developer options.
If you can't do that then this may not work but is worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
These may also be something to look into:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
I did try to contact Oneplus for support but I am not the one who purchased the phone. Long story short, it was a gift from my girlfriend that she bought off of someone. The phone was new in box and was a warranty replacement. I would have to contact the seller and go trough him for support unfortunately.
Thanks for the different suggestions!, I will fiddle around with it this afternoon while the kids are having their mid-day nap and I'll get back with the results
Thanks again for the help, it's greatly appreciated!
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Congratulations hope you enjoy the phone
Sent from my ONE A2005 using Tapatalk
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
Glad one was able to help you do it. :good:
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
HI there,
I am having the exact same issue with my oneplus 2. Unfortunately i know almost nothing regarding these android thingy. I know it has been almost 2 years, would you mind guide me through the steps? I would appreciate it so much.
Thanks.
Help: G4 Plus won't start after accidentally hitting "Open" on icon pack install.
I got this phone literally yesterday, it's unrooted, worked perfectly fine until my hand slipped when installing an icon pack from the play store and I hit "Open" - the phone immediately crashed, and now will not boot. I've tried using standard power on, powering on through the recovery bootloader, and entering recovery mode through said bootloader, in every instance it displays the Motorola startup screen, plays through its sequence of animations, then as soon as the Lenovo brand icon shows on screen emits one long pulse of vibrate and then turns off again.
I can't pull the battery because I don't have the required micro-hex screwdriver. Can anyone help?
Yodhrin said:
I got this phone literally yesterday, it's unrooted, worked perfectly fine until my hand slipped when installing an icon pack from the play store and I hit "Open" - the phone immediately crashed, and now will not boot. I've tried using standard power on, powering on through the recovery bootloader, and entering recovery mode through said bootloader, in every instance it displays the Motorola startup screen, plays through its sequence of animations, then as soon as the Lenovo brand icon shows on screen emits one long pulse of vibrate and then turns off again.
I can't pull the battery because I don't have the required micro-hex screwdriver. Can anyone help?
Click to expand...
Click to collapse
can you reboot to bootloader and start recovery? Then clear cache and see if it helps to boot your device? Or if not make a factory reset if it won't help. Maybe the icon pack screwed up something.
Report back. After that, if nothing worked, you can try this:
Is your device recognized by fastboot? If yes, try "fastboot devices" and see if it shows serial number.
Then try to flash the latest stock in the following guide rom if you have one of this devices https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
strongst said:
can you reboot to bootloader and start recovery? Then clear cache and see if it helps to boot your device? Or if not make a factory reset if it won't help. Maybe the icon pack screwed up something.
Report back. After that, if nothing worked, you can try this:
Is your device recognized by fastboot? If yes, try "fastboot devices" and see if it shows serial number.
Then try to flash the latest stock in the following guide rom if you have one of this devices https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
Hi, thanks for responding. After four or five attempts to boot into recovery it succeeded; wiping the cache did nothing so I did a factory reset, which worked and now the phone will boot to the setup stage. Unfortunately now I'm getting "The device was reset. To continue, sign in with a Google Account that was previously synced on this device.", which after googling seems to be a security feature - the problem is it doesn't accept the google account credentials, every time I enter them it just cycles back to the "This device was reset..." screen again.
I know I'm not getting the details wrong since I made the account specifically for the phone and have the details written down. Any suggestions on how to proceed?
EDIT: Actually nevermind, I managed to follow along with a tutorial on how to bypass it using MotoService & ADB. Thanks again for replying.
Anyone get bricked from the last update (I assume January/December security updates). I tried to update my phone yesterday 1/7/2018. My phone basically downloaded everything, told me to restart, loaded into the bootloader 3 times - after i selected normal Boot, and then stopped and charging.
Pretty glad that I had 2 phones.. because I have a video of it bricking in front of my eyes. not sure if I can post links yet.
Any help would be reallly appreciated as I haven't modified anything on it...
Can you still boot into recovery?
neokwlx said:
Anyone get bricked from the last update (I assume January/December security updates). I tried to update my phone yesterday 1/7/2018. My phone basically downloaded everything, told me to restart, loaded into the bootloader 3 times - after i selected normal Boot, and then stopped and charging.
Pretty glad that I had 2 phones.. because I have a video of it bricking in front of my eyes. not sure if I can post links yet.
Any help would be reallly appreciated as I haven't modified anything on it...
Click to expand...
Click to collapse
try to wipe your data fastboot -w or with stock recovery
This video is the last time I could get the phone to turn on. The only signs of life I (saw) on the phone was the LED light when I tried to charge the phone -
after it ran out of battery.
https://photos.app.goo.gl/XaD1W5CUmMpV9U9w2
The screen won't turn on or off. It's like the power button's broken even though it's still pressable. It should have battery though because I've been trying to turn it on with it plugged in.
neokwlx said:
The screen won't turn on or off. It's like the power button's broken even though it's still pressable. It should have battery though because I've been trying to turn it on with it plugged in.
Click to expand...
Click to collapse
ok maybe try power on with volume down
nicoconepala said:
ok maybe try power on with volume down
Click to expand...
Click to collapse
None of these combinations worked. (Held them for at least 3 seconds each)
Power+Up
Power + Down
Power+UP+DOWN
Up+down
neokwlx said:
None of these combinations worked. (Held them for at least 3 seconds each)
Power+Up
Power + Down
Power+UP+DOWN
Up+down
Click to expand...
Click to collapse
Try them for 45 seconds.
Sent from my PH-1 using XDA Labs
avd said:
Try them for 45 seconds.
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Thanks! It turned on after Vol Down+Power (10 seconds).
Unfortunately every menu option from FastBoot Mode proceeds to black screen
-Start
-Recovery Mode
-Restart bootloader
-Power Off
Got it to work with flash unlock in the bootloader menu! Thanks for the advice everyone!
neokwlx said:
Got it to work with flash unlock in the bootloader menu! Thanks for the advice everyone!
Click to expand...
Click to collapse
glad for you ?
How?
neokwlx said:
Got it to work with flash unlock in the bootloader menu! Thanks for the advice everyone!
Click to expand...
Click to collapse
Can you please tell me how exactly you did this? via command line fastboot?
I can't select anything in the boot loader menu, just like you all options show a black screen. Can't do anything.
Please help!
Essential Phone stuck in Start up screen with Locked Boot loader
Essential Phone stuck in Start up screen with Locked Boot loader, need help to get it back on. Is there a way around to unlock the boot loader from Fast Boot ?
[email protected] said:
Essential Phone stuck in Start up screen with Locked Boot loader, need help to get it back on. Is there a way around to unlock the boot loader from Fast Boot ?
Click to expand...
Click to collapse
You will need to side load the OTA.
You cannot unlock the boot loader unless you check OEM unlock in the developer menu.
Or, at least I have not seen it done.
tech_head said:
You will need to side load the OTA.
You cannot unlock the boot loader unless you check OEM unlock in the developer menu.
Or, at least I have not seen it done.
Click to expand...
Click to collapse
OEM unlocking is ticked off. That's the issue. I've seen in some videos or posts like Chris Paton. Advising to relocate the bootloader after sideloading the beta OTA's... I followed it and now I'm in a soup.
[email protected] said:
Essential Phone stuck in Start up screen with Locked Boot loader, need help to get it back on. Is there a way around to unlock the boot loader from Fast Boot ?
Click to expand...
Click to collapse
try to wipe all user data and reflash the stock ROM through command line..i don 't know if you want to keep your data or just make the phone work
panossd said:
try to wipe all user data and reflash the stock ROM through command line..i don 't know if you want to keep your data or just make the phone work
Click to expand...
Click to collapse
I don't min wiping it off... But I'm unable to access those commands as my Boot loader is locked and OEM Unlocking is not toggled on. Let me know of there is anything I can do in such case.
[email protected] said:
I don't min wiping it off... But I'm unable to access those commands as my Boot loader is locked and OEM Unlocking is not toggled on. Let me know of there is anything I can do in such case.
Click to expand...
Click to collapse
Can u get the phone in fastboot mode??? Try to install lineage os (twrp etc. )
panossd said:
Can u get the phone in fastboot mode??? Try to install lineage os (twrp etc. )
Click to expand...
Click to collapse
Fastboot Mode - YES. But it isn't accepting any commands from there.
[email protected] said:
Fastboot Mode - YES. But it isn't accepting any commands from there.
Click to expand...
Click to collapse
Does your PC sees the phone when in fastboot mode?
So, pretty much what the title says...I got the prompt to update to Oreo. Clicked install and left it. It does whatever it needs to do and after 2 hours of leaving it there it was just stuck on the boot screen. Tried to boot into recovery and no luck, it just remains on boot screen. I can access fastboot mode though.
Because the boot loader is locked, I can't install a custom recovery or anything. I tried everything I could in my own power before resorting to here. Any suggestions?
Did you hold the power button down until your phone completely powered off? I'm assuming you did. What you described isn't supposed to happen on a dual partition phone. If an update goes bad the phone is supposed to recover by booting from the other partition. If powering the phone down completely and then turning it back on doesn't allow you to boot I would honestly go straight to Essential Support since you didn't mod your phone or unlock the bootloader. I dealt with support via email and if nothing else they are definitely very responsive. They answer emails so promptly it was almost like being in a chat.
devon4786 said:
So, pretty much what the title says...I got the prompt to update to Oreo. Clicked install and left it. It does whatever it needs to do and after 2 hours of leaving it there it was just stuck on the boot screen. Tried to boot into recovery and no luck, it just remains on boot screen. I can access fastboot mode though.
Because the boot loader is locked, I can't install a custom recovery or anything. I tried everything I could in my own power before resorting to here. Any suggestions?
Click to expand...
Click to collapse
Hello
Tell us the status of your phone Did you solve the problem? Tell us the way I'm stuck in the same problem