Database Users

[Q] Nexus 7 stuck at the google logo

Hello,
I've got a problem. On monday my Nexus 7 2012 (with lastest stock Android) froze and I had to reboot it. But then it got in a bootloop where it would boot to the boot-animation (the four moving dots) and then restart after half a minute. Then I went into the bootloader to switch it off. When I switched in back on it just got stuck at the google logo.
I tried to reflash the stock rom, but I haven't unlocked the bootloader yet and everytime I try to do unlock it, it fails with "unknown error code".
At first I used Wug's Toolkit. When that didn't work I used cmd, but that doesn't work either.
I would really appreciate some ideas to solve that

You dont have to unlock the bootloader to flash factory images.
You can flash it with fastboot or a toolkit.

Did you try to get into recovery?
Maybe you can wipe some thing like cache, dalvik cache and system,
And then install the firmware again.
I once installed a firmware without properly wiping and also got stuck in thjis animation logo.
After wiping in recovery and re-flashing the firmware it worked again.

Erovia said:
You dont have to unlock the bootloader to flash factory images.
You can flash it with fastboot or a toolkit.
Click to expand...
Click to collapse
As far as I know, you need to unlock the bootloader. Anyway, I tried a toolkit as well as fastboot via cmd but none worked.
See here: http://forum.xda-developers.com/showthread.php?t=1907796
In order to do anything useful in fastboot, the bootloader must be unlocked
Click to expand...
Click to collapse
Amlan90 said:
Did you try to get into recovery?
Maybe you can wipe some thing like cache, dalvik cache and system,
And then install the firmware again.
I once installed a firmware without properly wiping and also got stuck in thjis animation logo.
After wiping in recovery and re-flashing the firmware it worked again.
Click to expand...
Click to collapse
I dont't have any custom recovery installed. When I am trying to access the stock recovery mode via the bootloader then I get to the Google logo and "booting failed" is written in the upper left corner.
My guess is that the emmc is broken

Google search android factory images, download the appropriate one for your device
Then extract contents and double click the flashall.bat
If this fails then chances are your emmc has been severely corrupted, I've seen a few get to that point with the booting failed and its 50/50 if they resurrect their device
Best of luck
(Oh and don't use toolkits)
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Google search android factory images, download the appropriate one for your device
Then extract contents and double click the flashall.bat
If this fails then chances are your emmc has been severely corrupted, I've seen a few get to that point with the booting failed and its 50/50 if they resurrect their device
Best of luck
(Oh and don't use toolkits)
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried that again the way you described it and sadly it didn't work. I have to accept that the emmc is corupted.
Thanks guys for your help anyway

Nexus 10 Boot Loop after OTA 4.4.3 Update

I have a Nexus 10, rooted but still running stock. I clicked the 4.4.3 OTA update, it updated, and restarted in a boot loop. No idea what went wrong with the update.
I went to Recovery Mode and did a factory/data reset, but after that completed, it was still in a boot loop. I noticed the system recovery says "K0T49H", which is 4.4.3 that didn't install correctly, so I'm thinking maybe factory reset is out as an option.
I also tried entering Recovery Mode and applying the update via adb, but it says "Fastboot device was not found".
Any ideas on how to get it running again?

Giraffeteria said:
I have a Nexus 10, rooted but still running stock. I clicked the 4.4.3 OTA update, it updated, and restarted in a boot loop. No idea what went wrong with the update.
I went to Recovery Mode and did a factory/data reset, but after that completed, it was still in a boot loop. I noticed the system recovery says "K0T49H", which is 4.4.3 that didn't install correctly, so I'm thinking maybe factory reset is out as an option.
I also tried entering Recovery Mode and applying the update via adb, but it says "Fastboot device was not found".
Any ideas on how to get it running again?
Click to expand...
Click to collapse
It says "fastboot device was not found" because Fastboot is only for when you are in the Bootloader. ADB is for when you are in Recovery, or booted into the Android OS. Since you already did a factory data reset, I would assume you don't mind losing data. If that's the case, just boot into the bootloader and flash the entire factory image for 4.4.3.

charesa39 said:
It says "fastboot device was not found" because Fastboot is only for when you are in the Bootloader. ADB is for when you are in Recovery, or booted into the Android OS. Since you already did a factory data reset, I would assume you don't mind losing data. If that's the case, just boot into the bootloader and flash the entire factory image for 4.4.3.
Click to expand...
Click to collapse
When I go to bootloader, NRT doesn't find the device any more. Is there something else I need to do?

Giraffeteria said:
When I go to bootloader, NRT doesn't find the device any more. Is there something else I need to do?
Click to expand...
Click to collapse
Oh. You're using a toolkit... Sorry, can't help you much then. I'm not a big fan of toolkits for this very reason. It's much easier to figure out what went wrong, and where, when you flash everything manually. However, it sounds like there's a driver issue. Make sure you still have the correct drivers installed. That's all I can think of.

Giraffeteria said:
When I go to bootloader, NRT doesn't find the device any more. Is there something else I need to do?
Click to expand...
Click to collapse
I followed this guide: http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/ and flashed through the bootloader. Wouldn't have gotten there without your help, though! Thanks!

Giraffeteria said:
I followed this guide: http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/ and flashed through the bootloader. Wouldn't have gotten there without your help, though! Thanks!
Click to expand...
Click to collapse
NICE! Glad I could help. These Nexus devices are so easy to flash manually, so I don't really see the need for toolkits for this device. I can understand other locked down devices though. After I picked up my Gnex, doing everything manually was how I learned the basics of ADB and Fastboot.

Hi,
Glad to see that you solved your issue, could you please add a [SOLVED] tag to the title now?
~Lord

[Q] Need help! Did OTA update to 5.0, stuck in bootloop!

I need some major help
My N7 2012 was stock, never rooted. I had only installed OTA updates. Yesterday, the OTA update for Lollipop appeared, and I installed it.
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
I've also tried getting it into fastboot, and I can issue fastboot commands. However, I've never unlocked the bootloader. And when I try to unlock it now, I get the screen that says "This will void your warranty are you sure?" But when I select Yes, fastboot's console says "Failed", and it remains locked.
If I go into Recovery, it just says "No commmand"
I need some help from the geniuses on this forum. To me it seems like an app running at startup is causing the crash, so if I could just get it to Safe Mode, I could figure it out and uninstall it. Hell, I'd be fine w/ a total wipe at this point. Just something to get it working again!
Thanks in advance!

Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.

Didn't work
bubba949 said:
Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.
Click to expand...
Click to collapse
I tried using the Nexus toolkit, using Flash to Stock/Unroot in Bootloop mode, and it didn't work. A few sections succeeded, but most of the sections said "FAILED". Even after performing this, it still wants to boot to my normal desktop, so I know it's not re-flashing a thing.
I wish I knew more about this. I can get into fastboot by going to Power+VOL- but because it won't stay on the desktop, adb commands are a no-go. Is there something in the Advanced section of the Nexus Toolkit that will let me do a reflash? I'm afraid of just poking and trying things for fear of truly bricking it.
Thanks.

Sorry just re-read your last reply didn't realise you can't do adb commands, if you get to a point when you can then below may help...
I had a similiar issue caused differently what i did was to go to this link
http://forum.xda-developers.com/showthread.php?t=1907796
Downloaded the bootloader from JWR66V the guy mentions in his thread he mentions the same issue that i had which is when i tried to flash a stock or custom rom i kept getting messages about invalidstate on bootloader then the system and userdata images would fail when i tried to install...
In the end i downloaded the stock JWR66Y rom, replaced the bootloader image with the one mentioned above, i had to flash the seperate parts of the rom as the Nexus Root Toolkit wouldn't accept the MD5 after i replaced the bootloader so make sure the recovery, the modified bootloader, system and userdata are in your SDK tools folder then i did the following in cmd...
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
Fastboot reboot
And voila it booted up and then upgraded its self and is now stock running 5.0 but its working for 2days it wasn't lol

alastria1 said:
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
Click to expand...
Click to collapse
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
bftb0 said:
[size=+1]Safe Mode Boot[/size]
From a cold start boot (press & release Power button), wait 2 seconds after the B&W Google (bootloader) splash screen appears, then press and hold Vol-Down button until the normal OS boot is fully completed (lock screen or home screen appears)
Click to expand...
Click to collapse
Sounds like something is draining the RAM. Try using the stock launcher as default.

Still crashed
dtg7 said:
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
Sounds like something is draining the RAM. Try using the stock launcher as default.
Click to expand...
Click to collapse
I didn't know that. I tried it, and I was able to boot it into safe mode doing this ... and then it crashed in 15 seconds and rebooted...
At this point, I'm considering just emailing Google, since its their update that did this.

They'll probably tell you to wipe cache partition. And by the way,
alastria1 said:
If I go into Recovery, it just says "No commmand"
Click to expand...
Click to collapse
that is a normal operation, it's supposed to say that. What you need to do to get the actual recovery menu is, with screen saying No Command, hold the power button, then click the volume Up button, them let go of power.
This will get you the recovery options, where you should scroll down to wipe Cache partition (last one I think) and select it by hitting power. Reboot into Android and see if that helped.
If not in the same recovery menu there's an option to wipe everything, factory reset. that might cure your device but it will wipe your data.
There is an adb command to pull your sdcard data off your device, but I've never tried it in stock recovery. it might work, but of course it will probably require you had turned On USB debugging.
adb pull /storage/sdcard0/ yourcomputerfolder
yourcomputerfolder being a location on your laptop, like a folder on the desktop.
try this command when in recovery, I don't think it works in bootloader. also, if it works it will only backup your regular files, not your installed apps.
if not then just do the wipe from recovery.
good luck.

Still a no go...
So, I got into the recovery menu, and did a full factory reset. After it rebooted, it went right back to Nova Launcher (with my usual wallpaper on there), and crashed as before. Getting into safe mode confirmed that it no apps were wiped. Factory reset didn't reset a thing.
Its almost like the flash memory is stuck on read-only mode. No matter what I do, nothing changes the contents of memory.

That is weird. And I suppose you can't do what 'wakers' suggested and flash the individual partitions since it probably requires an unlocked bootloader, which you already tried to unlock unsuccessfully. I'd say you were up sh-- creek without a paddle, but... Google searching, maybe there's still a tiny bit of hope:
See this discussion: http://android.stackexchange.com/qu...p-after-lollipop-flash-no-adb-and-no-fastboot
to summarize the suggestions:
- try holding the power button for over ten seconds to kind of reset... something
- try sending the command: fastboot oem lock
yes I know you never unlocked but try it anyway, it might go thru where unlock failed.
speaking of fastboot oem unlock, I know it failed but maybe you can just keep sending the command a few times, one of them might go thru.
I'd add another suggestion: carefully remove the back and carefully unplug the battery and let it sit for a while. then put it back together and try booting up.
may the force be with you.

Finally resolved
Thanks to the posters for the help. I contacted Google customer support and they're overnighting a refurb replacement for free.

Soft Bricked Nexus 6P With Locked Bootloader (Need Help)

My Nexus 6P is stuck on the Android boot animation after installing the Android Beta OTA that came out today. I waited like 30 Minutes and nothing was happening so I tried Clearing Cache which did nothing then factory resetting, Clearing Cache & Even sideloading the OTA using ADB to no avail. My huge mistake was not having OEM Unlocking enabled so now I can't even flash stock android.. I know this is my fault for being so stupid but is there anything at all I can do to save my phone?

AlfexOmega said:
My Nexus 6P is stuck on the Android boot animation after installing the Android Beta OTA that came out today. I waited like 30 Minutes and nothing was happening so I tried Clearing Cache which did nothing then factory resetting, Clearing Cache & Even sideloading the OTA using ADB to no avail. My huge mistake was not having OEM Unlocking enabled so now I can't even flash stock android.. I know this is my fault for being so stupid but is there anything at all I can do to save my phone?
Click to expand...
Click to collapse
I'm in the exact same boat...hopefully something can be done, but I'm afraid we're idiots for not having checked OEM Unlocking. I've tried adb sideloading the OTA image, but as you said, with a locked bootloader, we've got nothing. Anybody have any ideas?

You might be able to use ADB to modify the OEM Unlock setting while booting.
Also, if you ever plan to mess with your OS, especially alpha/beta versions, always have your bootloader unlocked to prevent issues like this.

Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.

imatts said:
Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.
Click to expand...
Click to collapse
Live booting TWRP works on the 6P even with the bootloader is locked?
Sent from my Nexus 5X using Tapatalk

imatts said:
Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.
Click to expand...
Click to collapse
Can't boot twrp.img because the device is locked. Anything else I can do?

I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try

spookytay said:
I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try
Click to expand...
Click to collapse
No luck for me, unfortunately. Keep in mind that I tried to sideload the OTA.zip with a locked bootloader before doing this, so that may have made this process not work. For those who haven't tried to "fix" their failed installation like I did, give the cache clear a try first.

Apparently some people can use the fastboot format command while their bootloader is locked. You can try booting into the bootloader and issuing these commands. (THIS WILL WIPE YOUR ENTIRE DEVICE INCLUDING SDCARD/INTERNAL STORAGE. Of course, your device is now bricked, so I'm sure this is fine for you.)
Code:
fastboot format cache
fastboot format userdata

My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip

AlfexOmega said:
My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
Glad you got it working! Hopefully it works for the other guy too. Probably best to use the factory image if you wanna update to N, with OEM Unlocking enabled

lightmastertech said:
Glad you got it working! Hopefully it works for the other guy too. Probably best to use the factory image if you wanna update to N, with OEM Unlocking enabled
Click to expand...
Click to collapse
This method will work 100% just adb sideload the package and done. My idea worked thanks to the guy who posted the ota zip

Ame123 said:
This method will work 100% just adb sideload the package and done. My idea worked thanks to the guy who posted the ota zip
Click to expand...
Click to collapse
Hello guys. I'm having the same problem here: installed the update last Thursday, apparently didn't have usb debugging checked on and I can't get past the boot animation.
Tried everything: format several times, cleared cache, sideload, etc. I've tried to sideload this package you guys are talking about but unfortunately this doesn't work either... In cmd it says <waiting for devices>. Tried different usb ports and everything - still nothing

silviuardelean said:
Hello guys. I'm having the same problem here: installed the update last Thursday, apparently didn't have usb debugging checked on and I can't get past the boot animation.
Tried everything: format several times, cleared cache, sideload, etc. I've tried to sideload this package you guys are talking about but unfortunately this doesn't work either... In cmd it says <waiting for devices>. Tried different usb ports and everything - still nothing
Click to expand...
Click to collapse
Seems like it could be a driver issue. If you run adb devices does your device show up?

freezerbite said:
Seems like it could be a driver issue. If you run adb devices does your device show up?
Click to expand...
Click to collapse
Yes, the device was showing up in cmd but couldn't get over <waiting for devices>... I've tried to install TWRP and failed again. After trying to sideload the image a dozen times and clearing cache, formatting data, etc several times, it somehow worked in the end. Thank you very much!

It might sound like a dumb question, but how do i Side load through ADB? can you please point me in the right direction. I'd really appreciate it! @silviuardelean @Ame123 @AlfexOmega Actually, I don't think I ever enabled usb debugging

GeorgeOSbeta said:
It might sound like a dumb question, but how do i Side load through ADB? can you please point me in the right direction. I'd really appreciate it! @silviuardelean @Ame123 @AlfexOmega Actually, I don't think I ever enabled usb debugging
Click to expand...
Click to collapse
I was able to get mine to work without having it enabled you could try using Nexus Root Toolkit it guides you through how to do everything
https://www.youtube.com/watch?v=LfDSZsr6230

Locked bootloader 7.1.1 ota preview help!
I have the latest preview build directly installed ota from Google. The phone just started bootlooping the other day for no apparent reason. I didn't have the developer options on or oem unlock enabled.
I can get to bootloader mode and recovery mode. I have wiped and reset from recovery with no help. I can access adb and fastboot on the pc but it won't let me write any files because of the locked bootloader. Anything I try to sideload so far gives an error. Any further suggestions?

AlfexOmega said:
My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
I'm full stock with locked bootloader. How do I install this package? Flashing through recovery or with adb (and in this case, which commands should I use)?

solefero69 said:
I'm full stock with locked bootloader. How do I install this package? Flashing through recovery or with adb (and in this case, which commands should I use)?
Click to expand...
Click to collapse
You use recovery to sideload it via adb. If you are unsure how to do so you can download and use Nexus Root Toolkit it does everything for you, it's really useful This video will help
https://www.youtube.com/watch?v=LfDSZsr6230

Bootloop With locked bootloader 7.0

My 6p is stuck in a bootloop. nbd90x build my bootloader is locked is there anyway to unlock from adb. I have already tried sideloading ndb90x through adb wipping chache and user data and still no luck. Help me Xda youre my only hope..

So you previously enabled USB debugging, how about OEM unlocking? If so, use 'fastboot flashing unlock' to unlock the bootloader. Note that internal storage will be completely wiped. Everything. Though with USB debugging enabled, you should be able to adb pull the contents of you SD card first. If you can unlock the bootloader you can try flashing factory images with fastboot. Otherwise, not much else besides RMA it with Google. There's been a few reports of stock N6Ps bootlooping. Haven't seen anyone post that Google denied the claim.

no bootloader is locked so cant flash using flashboot but debugging is enabled so I am able to use adb .

I know. What I'm asking is if you enabled allow OEM unlocking in developer settings? That doesn't unlock your bootloader in itself. You still need to use fastboot to do it. However if that setting IS enabled what you can do is... Use ADB to pull your internal storage to PC. Then use fastboot to unlock the bootloader and flash factory images. If the setting is not enabled, and wiping data and flashing an OTA don't work, I'm not sure what else can be done.
You can try downloading the 7.1 dev preview OTA and seeing if it updates whatever is causing it to fail. Other than those, RMA would be your best bet.
https://developer.android.com/preview/download.html#device-preview

After sideloading a ton of times between 7.0 and 7.1, one time i got it to boot up then i immediately enabled oem unlock then it crashed again... so now I am able to flash through fastboot although I havent been able to get it to boot again. Is it normal for bootloops to not get fixed by flashing?

Hijacking your post to report what is happening to me. I posted the same thing on the Android Beta program community on G+.
Have been using the latest beta since it came out on completely stock 6P (locked bootloader, unrooted). Everything working normally when yesterday around 10 or 11AM, phone starts to bootloop OUT OF NOWHERE, it was just sitting there on the table while I was working. I could still get to bootloader/recovery, so that was a bit of a relief. First thing I tried: clear cache, nothing. Then proceed to wipe/factory reset the device, to no avail. Immediately downloaded the latest factory image from Google's page, tried flashing it but couldn't since the bootloader was locked (OEM unlock option also disabled). Then downloaded the beta OTA and sideloaded it, process went through OK but device still bootloops. Tried sideloading the latest stable OTA but didn't work since it was from a previous build. Ran out of ideas. So there I was creating a thread on XDA for help while the device was still on its bootloop rush, about to hit the Submit button when again OUT OF THE BLUE SKY the device decides to boot itself back up. First thing I did was unlock the bootloader. Phone worked normally for 6 or 7 hours, when I'm doing something on it and then again, screen froze and bootloop starts again. This time I only reset the device and left the it bootlooping, after about 30 minutes it boots up again. I unenrolled from the beta and installed the latest 7.0 build. Everything working fine for the last 12 hours. Anyone have any idea on what can cause the device to bootloop like that? Never seen anything like it.

Yea I signed up for the beta program too do you have the link to unenroll? So you just reset and let it sit?

Here you go
google.com/android/beta

do you remember what you did to get it to boot?

noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
Well, that's the thing. Everything I tried didn't seem to work. I couldn't flash the factory image since the bootloader was locked. I was able to sideload the beta OTA but the device still bootlooped after that. So I just left it bootlooping and after around 20 or 30 minutes the device booted normally. I have no idea what caused it and what I did to make it work again.
P.S: device restarted 2 times while I was typing this.

noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
If your boot loader is locked you are screwed, sorry to say, I would RMA it. Unbelievable an update can mess a phone up...that's why I always unlock the bootloader first thing and never lock it. I need complete control of my phone.
Edit: Only thing I can think of is delete the partitions with fastboot or adb and reflash factory image.

boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot

noetre said:
boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot
Click to expand...
Click to collapse
As a last resort, flash all of the images manually with fastboot. This will wipe all userdata and completely format the SDcard. Nothing will be left. Extract the bootloader and radio images from the factory images zip. Flash them in fastboot. Reboot to fastboot again. Extract the next zip in the same folder as BL & radio images and flash the vendor, system, boot, recovery & userdata image files. Just for good measure, boot to recovery (stock Android recovery) and perform a factory reset & cache wipe. If the phone still fails to boot, your only option would be to RMA it at this point.
Note: As per Heisenberg's sticky thread, do NOT flash userdata.img if you have anything besides the 32gb model as you will only have the ~32gb storage available. If you're using a model with more storage, just use fastboot to format userdata but don't flash the image.

Ill try that.. but isnt the warranty voided because the bootloader is unlocked?

noetre said:
Ill try that.. but isnt the warranty voided because the bootloader is unlocked?
Click to expand...
Click to collapse
Not on a Nexus, no.
Added: I had to RMA mine after the phone got its first update. I unlocked the bootloader and stayed stock for a long time (until N came out). I took the OTA in About Phone and it applied with no problems but the phone would not boot. Factory images also couldn't get it running. Stock recovery and all. RMA'd without issues. I didn't tell them, just sent it in. If they tried to boot it they would've seen the unlock symbol. There's also a thread somewhere buried in the general section where someone called Google and asked and they confirmed to them that unlocking does not void warranty. I'll try to find it for you.
Found it: http://forum.xda-developers.com/nexus-6p/general/unlocking-bootloader-warranty-google-t3229804/page1
I also returned 4 faulty Nexus 5's (mostly screen artifacts) all unlocked with no problems.