Just openned my N5X.
First boot to enable OEM unlock and ADB debugging.
Used sudo ./fastboot flashing unlock
Then I wanted to upgrade from 6.0.0 to 6.0.1, so I downloaded the factory image
I flashed twrp-2.8.7.2-bullhead.img
Booted to TWRP to ADB push some files and did not flash anyting from TWRP
After first boot it showed Google with the unlock symbol for several minutes, so I powered it down.
Now, if I boot to bootloader it shows a blank black backlight (I know it is in bootloader because sudo ./fastboot devices produces a s/n)
If booted normally, a mess of rainbow pixels is usually displayed (see pics).
Since it does get to the bootloader, I have tried revert to 6.0.0 with a couple different builds but the same screen issues persist.
I tried a bit more force with the following:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
I also have tried flashing using the update script, but still have the same results.
I find it strange on the first stock boot that the display was fine, but after flashing 6.0.1 and then TWRP this started happening. Is it possible the LCD is actually just defective?
edit: can't post link to pics of screen because I'm under 10 posts
I don't know why you used fastboot flashing unlock. This device requires fastboot OEM unlock. I don't know of that is your problem though.
Sent from my Nexus 5X using Tapatalk
Did you try flashing using the flash-all.bat?
Maybe that wil completely revert the phone to stock.
If not start from scratch using fastboot OEM unlock (see the root guide on this forum) and reflash the entire phone using flash-all script.
peltus said:
Did you try flashing using the flash-all.bat?
Maybe that wil completely revert the phone to stock.
If not start from scratch using fastboot OEM unlock (see the root guide on this forum) and reflash the entire phone using flash-all script.
Click to expand...
Click to collapse
Yes, I have tried using flash-all.sh on every build of 6.0.0 as well as the 6.0.1. Still rainbow pixels and when booted to bootloader shows blank, black, backlit screen
PiousInquisitor said:
I don't know why you used fastboot flashing unlock. This device requires fastboot OEM unlock. I don't know of that is your problem though.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Agreed. Not sure what that command is for. Haven't seen that in any of the rooting guides. Flash all the files from the stock image to return to stock and try again would be my suggestion as pious stated as well
hopesrequiem said:
Agreed. Not sure what that command is for. Haven't seen that in any of the rooting guides. Flash all the files from the stock image to return to stock and try again would be my suggestion as pious stated as well
Click to expand...
Click to collapse
Apparently that's how you OEM unlock the 6P.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Apparently that's how you OEM unlock the 6P.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
****ing huawei lol glad I got the 5x
PiousInquisitor said:
Apparently that's how you OEM unlock the 6P.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I stupidly relocked the bootloader to see if it would do anything. Now OEM unlock and USB debugging is disabled and the screen is too unrecognizable to navigate through the initial setup and enable it.
tehNYAZ said:
I stupidly relocked the bootloader to see if it would do anything. Now OEM unlock and USB debugging is disabled and the screen is too unrecognizable to navigate through the initial setup and enable it.
Click to expand...
Click to collapse
PM me the link. I'm curious to see what your phone looks like when booted
Edit: Does anything happen when you issue this command in fastboot: reboot recovery
Sent from my Nexus 5X using Tapatalk
tehNYAZ said:
I stupidly relocked the bootloader to see if it would do anything. Now OEM unlock and USB debugging is disabled and the screen is too unrecognizable to navigate through the initial setup and enable it.
Click to expand...
Click to collapse
You relocked the bootloader in fastboot mode right? You can just fastboot oem unlock again from fastboot. Once unlocked, flash twrp, push and flash a rom. See what you get.
Sent from my Nexus 5X using Tapatalk
Here's the link for anyone with ideas if @PiousInquisitor suggestion does not work.
PiousInquisitor said:
You relocked the bootloader in fastboot mode right? You can just fastboot oem unlock again from fastboot. Once unlocked, flash twrp, push and flash a rom. See what you get.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have successfully flashed twrp (at according to cmd). When I boot to recovery using volume up + power, I get a blank screen. Tring to slide where the twrp screen lock should be does nothing. ADB does not see any devices. I have also tried booting to recovery from the bootloader with two volume down presses and one power button press-- same result.
I have also succesfully unlocked the bootloader again. I have updated my SDK/fastboot/adb/drivers/etc and have run every flash-all script from every build downloaded from the Google Dev site. I have tried all the flash-all.bat/sh on booth Linux and Windows. I have tried using different USB ports on my machine. I have tried using the USB-C to A cable ordered from the Google store and also the USB-C to A cable that came with the Nexus 6P. I used the same procedure to unlock, root, etc my 6P and did not have any issues.
Every time I get the same result that @SlimSnoopOS linked the screenshot to. I get the rainbow screen when booting to Android, a blank backlight when booting to bootloader, and a blank unlight screen when booting into recovery (although adb can't see the device from cmd or terminal).
Based on the amount of time I have spent on this, it may just be time to lock the bootloader and hope the Google Store accepts a return.
tehNYAZ said:
I have successfully flashed twrp (at according to cmd). When I boot to recovery using volume up + power, I get a blank screen. Tring to slide where the twrp screen lock should be does nothing. ADB does not see any devices. I have also tried booting to recovery from the bootloader with two volume down presses and one power button press-- same result.
I have also succesfully unlocked the bootloader again. I have updated my SDK/fastboot/adb/drivers/etc and have run every flash-all script from every build downloaded from the Google Dev site. I have tried all the flash-all.bat/sh on booth Linux and Windows. I have tried using different USB ports on my machine. I have tried using the USB-C to A cable ordered from the Google store and also the USB-C to A cable that came with the Nexus 6P. I used the same procedure to unlock, root, etc my 6P and did not have any issues.
Every time I get the same result that @SlimSnoopOS linked the screenshot to. I get the rainbow screen when booting to Android, a blank backlight when booting to bootloader, and a blank unlight screen when booting into recovery (although adb can't see the device from cmd or terminal).
Based on the amount of time I have spent on this, it may just be time to lock the bootloader and hope the Google Store accepts a return.
Click to expand...
Click to collapse
Seems like a display issue to me.
Sent from my Nexus 5X using Tapatalk
I had the same issue once with my lg g2. Turned out that I the issue was with the display. Sent in to the service center where they said the problem was damaged display connectors due to moisture.
Skickat från min Nexus 5X via Tapatalk
I had a similar issue with my first 5x. I was trying to flash the update, I think, but may have been doing other things at the same time. My display all of a sudden showed a pixelated vertical line running down the left hand side of the screen. The line was about 1/2 inch wide. It was visible in the boot loader, recovery and when normally running system. All attempts to fix the issue by re-flashing were useless. I finally sent it back and got a new one. No issues, rooted and running perfectly. To this day I don't know if was something I did, or if the display was just defective.
Related
been looking around on here. im stuck now
Ok iv unlocked and have root and can load into Clockwork 5.5.0.2
But when in Clockwork i get
E:can't mount /sdcard/
When i reboot the nexus now all i get is the Google Logo with the unlock Padlock.
Once it did load back into OS and then rebooted it self now stuck on Google logo and Unlock padlock... i Didnt copy over my ROM too the SDCard....
How do i get back into the OS
Flash the factory Google images via fastboot. Search the forum. There a quite a few threads with step by step instructions.
Sent from my Galaxy Nexus using xda premium
Try pressing the volume down button and power button until you reach recovery. When you a red triangle, press Vol+/Vol-/Power at the same time, you will now see a menu, select factory data reset.
I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.
??
throwbot said:
I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.
Click to expand...
Click to collapse
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it
NxsLS said:
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it
Click to expand...
Click to collapse
Have you tried flashing via fastboot? I would assume if fastboot oem unlock/lock works, then flashing using fastboot/android sdk should work.
...though, as a non dev, i have been wrong before
what do you mean by "pushing the files"? What are you trying to push?
Sent from my Galaxy Nexus using XDA App
Good, make sure you boot loader has been unlocked. You can use a program like the root toolkit (I don't think I can put a link to a different website) but he root toolkit for the nexus should help you push the stock image to your phone. Go to droid-life (.com, cough cough) and there is a set of instructions for returning back to stock. You can also use those same instructions to try and get her back up and running. Try the root toolkit they have on there, too. The only problem you might run into is having your phone set to USB debugging after unlocking the boot loader, bit it should still accept fast boot commands while I'm the bootloader
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
sorry, by pushing the files I mean pushing the stock image file (the stock software, including the stock operating system, stock bootloader, and stock radios). A rom is a custom tweaked version of the stock software. When you unlock the bootloader, if you don't have stock software on there (which you wont if you were running a rom when it crashed) then it might erase everything, including the from you were running. You will have to push that stock software (stock image file) back to your phone using commands from your computer
no worrys o2 just sending me a new nexus :x
report lost n stolen :x only £30 ex
NxsLS said:
report lost n stolen :x only £30 ex
Click to expand...
Click to collapse
I hate that.. because you didn't know what you were doing and screwed up your phone someone is supposed to provide you with a new one? As a few posters have already said, it should be a fairly easy fix. You didn't even acknowledge that you tried any of the suggested fixes. If you're going to mess around with your phone make sure you know what you're doing, or at the very least exhaust all potential options to get yourself out of a soft brick. I'm sure an experienced Android user could have you up and running in 10 minutes. It's no wonder providers don't want to unlock bootloaders on some phones.. Jesus...
i tryed all i got it too boot back into the OS but reset itself and locked in google with unlocked padlock. so gave up and will not make the same mistake of not copying over the rom after the root n unlock.. i have flashed/unlocked my samsung s2 with ODIN which was easy but the Nexus i used Galaxy Nexus ToolKit
My volume keys aren't working, and my phone is bootlooping after I tried to unroot it. The volume keys not working is a hardware issue. Is there anything I can do on the computer end to boot into the bootloader?
Thanks
Alec
Try to get adb to work for you.
If the system bootloops after adb service is brought up, you can try using 'adb reboot recovery' or 'adb reboot bootloader'.
If you made it, get back to stock and turn it in for the killing.
alec534 said:
My volume keys aren't working, and my phone is bootlooping after I tried to unroot it. The volume keys not working is a hardware issue. Is there anything I can do on the computer end to boot into the bootloader?
Thanks
Alec
Click to expand...
Click to collapse
bk201doesntexist said:
Try to get adb to work for you.
If the system bootloops after adb service is brought up, you can try using 'adb reboot recovery' or 'adb reboot bootloader'.
If you made it, get back to stock and turn it in for the killing.
Click to expand...
Click to collapse
It's bootlooping at the Google logo, and so adb isn't recognizing it. Frown. Thanks for your idea though.
alec534 said:
My volume keys aren't working, and my phone is bootlooping after I tried to unroot it. The volume keys not working is a hardware issue. Is there anything I can do on the computer end to boot into the bootloader?
Thanks
Alec
Click to expand...
Click to collapse
You can type adb reboot-bootloader in a command prompt. You can also download Quick Boot from the market, and you can reboot into the bootloader from your device.
EDIT: Oops, I took to long in replying... didn't see that it was already suggested.
EDIT 2: Mis-read your post. Think you are out of luck.
Sent from my Galaxy Nexus using Tapatalk
efrant said:
You can type adb reboot-bootloader in a command prompt. You can also download Quick Boot from the market, and you can reboot into the bootloader from your device.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
All I get is a "device not found" error. Adb doesn't seem to recognize the phone while it's bootlooping.
You can buy a jig for it to force it into boot loader. I also used it on mine to force it into boot loader download. Purchased one just in case something bad happened.
http://www.amazon.com/gp/aw/d/B0053...ile?redirect=true&ref_=oh_o00_s00_i00_details
Sent from my Galaxy Nexus using Tapatalk
purelife82 said:
You can buy a jig for it to force it into boot loader. I also used it on mine to force it into boot loader download. Purchased one just in case something bad happened.
http://www.amazon.com/gp/aw/d/B0053...ile?redirect=true&ref_=oh_o00_s00_i00_details
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
You are a life-saver if this works on the Nexus too. Thanks so much.
its works on my nexus.
Sent from my Galaxy Nexus using Tapatalk
I flashed a ROM called Chameleon and it really seems to have messed up my phone, a Verizon Galaxy Nexus.
All I have is the screen with the green guy on his back, panel up displaying cyan colored guts.
When I click to Recovery Mode, it flashes briefly and comes back. It says: FASTBOOT MODE - NO BOOT OR RECOVERY IMG
The rest says:
PRODUCT NAME - tuna (?!)
VARIANT - Toro 32GB
HD VERSION - 10
BOOTLOGGER VERSION - PRIMELC03
etc.
Oh, LOCK STATE - UNLOCKED
Is there any way to get a recovery on here or am I actually bricked?
PS Restart Bootloader does nothing.
Fastboot flash.........
Sent from my Galaxy Nexus using xda premium
You can use galaxy nexus toolkit - you boot into fastboot mode, flash a recovery from the toolkit, then just switch to recovery mode using your volume keys ...
Don't use a toolkit, if you want to know your stuff.
This is dead easy, like thedudejdog highlighted, just use fastboot, read efrant's "return to stock" thread stickied on General.
Sent from my Nexus
Green man on his back, seems deaf
I'm not getting any indication that there's a connection. e.g. I send "fastboot reboot" and nothing happens. Fastboot devices returns empty.
Fastboot flash? As suggested? Flash what? Into where? I've never ruined my phone quite this thoroughly so I don't know 1) what exactly I'm trying to flash (although I'm guessing a custom recovery would help and 2) how to get my phone to communicate with my computer.
The cable is fine, just checked it on another phone
fakecharles said:
I'm not getting any indication that there's a connection. e.g. I send "fastboot reboot" and nothing happens. Fastboot devices returns empty.
Fastboot flash? As suggested? Flash what? Into where? I've never ruined my phone quite this thoroughly so I don't know 1) what exactly I'm trying to flash (although I'm guessing a custom recovery would help and 2) how to get my phone to communicate with my computer.
The cable is fine, just checked it on another phone
Click to expand...
Click to collapse
you need the proper drivers.
please uninstall all drivers that you installed for the phone and follow this only:
http://forum.xda-developers.com/showthread.php?t=1626895
Hi guys,
So, I used to have some touchscreen issues, like, device going into standby, when waking up touchscreen wasn't working. After a forced shutdown usually solves it, sometimes i have to do it 2 or 3 times... but today.. after a forced shutdown, my tablet refused to boot.
So, following tutorials all around, I used fastboot to flash the original nexus image for 4.4.2, went fine, no errors (after a few retries), also flashed recovery (tried twrp and cwm), but the result is the same, google logo.
I tried flashing just fastboot flash system system.img, same for boot.img, still stuck at google logo. I got fastboot, but even selecting recovery, stays at google logo. I don't know what else to do. I know similar issues happen but usually they get sorted flashing either recovery or the image itself, but in this case, the tablet refuses to boot after a sucessfull image write.
Any tips? Thanks a lot guys, would mean a lot because I cant sent to warranty right away. Im not in my country (holidays) and I kinda need to use the tablet (ended up bringing it instead of my laptop, wasnt expecting this).
Any help is highly appreciated.
cheers!
MidnightDevil said:
Any help is highly appreciated.
cheers!
Click to expand...
Click to collapse
Did you confirm that adb recognized your tablet while in fastboot? Open a command and type adb devices. What is the response? Do you have adb.exe and fastboot.exe downloaded so you can flash the zips?
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
Did you confirm that adb recognized your tablet while in fastboot? Open a command and type adb devices. What is the response? Do you have adb.exe and fastboot.exe downloaded so you can flash the zips?
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
adb nothing cause it stays in bootloader, its recognized in fastboot, thats how i was able to put the official google image.
I got it to boot now, randomly, out of nothing, did nothing at all and its okay.
I dont know why it happens but its the third time it does this after touchscreen stops working.
Anyway, until the next time.
I know touchscreen issues happen, but this random thing is driving me nuts.
Hi All,
Request all to provide any suggestions related to the below issue:
I rolled back from android n preview 2 to android m after which my display is scrambled.I am not able to view any thing on it.
But I am getting calls and able to pick them when I roughly expect the place where I can swipe the dialer right to pick the call.
Few things that I want to highlight is :
1)I had unstable wifi connection while downloading the android m OTA.
2)I removed the unlock bootloader check before rolling back in the developer options.
3)I can also sense that i am able to take screen shots when I am holding the power button and the volume down button based on the sound it normally makes (while capturing screenshots)
I am not able to come to conclusion whether this a hardware issue?(may be i need the replacement of the screen) or can it be due to corrupt ota file update?
Any suggestions would be much appreciated.
thanks
I would first see if flashing the m factory image solves the issue. Then look at hardware.
k.s.deviate said:
I would first see if flashing the m factory image solves the issue. Then look at hardware.
Click to expand...
Click to collapse
thank you but the problem is I am not able to see the screen at all and hence I am not able to go to the fastboot mode or recovery mode.
NeverBackDown said:
thank you but the problem is I am not able to see the screen at all and hence I am not able to go to the fastboot mode or recovery mode.
Click to expand...
Click to collapse
use "adb reboot bootloader" from command prompt to enter bootloader or if you know the device is off, press power + vol up + vol down for roughly 5sec, thatll get into bootloader. than flash factory image.
or last case scenario use wug fresh toolkit to force flash the image, make sure you select the device fails to boot box (I think that's what its called, the only other one states "device on/normal" <-- so NOT that one)
k.s.deviate said:
use "adb reboot bootloader" from command prompt to enter bootloader or if you know the device is off, press power + vol up + vol down for roughly 5sec, thatll get into bootloader. than flash factory image.
or last case scenario use wug fresh toolkit to force flash the image, make sure you select the device fails to boot box (I think that's what its called, the only other one states "device on/normal" <-- so NOT that one)
Click to expand...
Click to collapse
Thanks I am first looking for type c to usb to connect it to my computer,I will try for it tomorrow and also the first option you provided will work only if usb debugging is already enabled on my phone ,right?
NeverBackDown said:
Thanks I am first looking for type c to usb to connect it to my computer,I will try for it tomorrow and also the first option you provided will work only if usb debugging is already enabled on my phone ,right?
Click to expand...
Click to collapse
yes, the adb command will only work if debugging is on. Once in bootlader, use fastboot commands, debugging doesn't matter at that point.
k.s.deviate said:
yes, the adb command will only work if debugging is on. Once in bootlader, use fastboot commands, debugging doesn't matter at that point.
Click to expand...
Click to collapse
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
NeverBackDown said:
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
Click to expand...
Click to collapse
Not that I'm aware of. Sorry, there is a thread on here that may prove useful that deals with bricked phones with OEM unlocked off. The info there might help you at least get back to stock.
k.s.deviate said:
Not that I'm aware of. Sorry, there is a thread on here that may prove useful that deals with bricked phones with OEM unlocked off. The info there might help you at least get back to stock.
Click to expand...
Click to collapse
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
NeverBackDown said:
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
Click to expand...
Click to collapse
Possibly, I have no experience dealing with a service center unfortunately.
NeverBackDown said:
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
Click to expand...
Click to collapse
I also want to highlight that,I am getting a black screen on the fastboot mode too,i cant see nothing there..Only way i am able to identify that my device is in fastboot mode is by giving fastboot devices command.
So can this be a software issue?
NeverBackDown said:
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
Click to expand...
Click to collapse
You might want to look into android screencast.
I don't know if it still works with the latest android releases, but back in kitkat days if I had a screen that wouldn't display I could use screencast and I'd get the framebuffer displaying on the PC. While viewing on PC I could then do touchscreen "guesses" more accurately and presumably you'd be able to enable OEM unlocked bootloader so you can flash factory images.