yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Starting to think that the repair centre (Device was sent for RMA in Germany, Gießen at Saturn Elektromarkt) flashed a non-relockable bootloader onto it. Seriously, I think I literally tried everything on the internet.

Here is a chronological summary:

First encounter of unlocked bootloader.

Noticed screen burn in. Prepare for RMA starts here.

Noticed earpiece not working.

First attempt to locking bootloader after succesfull manual factory image flash.

-Results in:

M:\SHAMU\FACTORY IMAGE\shamu-lmy47z>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 0.012s

Try "fastboot oem lock begin" method.

-Results in:

M:\SHAMU\FACTORY IMAGE\shamu-lmy47z>[COLOR="Red"]fastboot oem lock begin[/COLOR]
...
[COLOR="red"](bootloader) Ready to flash signed images[/COLOR]

OKAY [ 0.121s]
finished. total time: 0.123s
M:\SHAMU\FACTORY IMAGE\shamu-lmy47z>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (7731 KB)...
OKAY [ 0.252s]
writing 'boot'...
[COLOR="red"](bootloader) Preflash validation failed
FAILED (remote failure)[/COLOR]
finished. total time: 0.271s

M:\SHAMU\FACTORY IMAGE\shamu-lmy47z>

Notice messages in "Bootloader Logs" within bootloader menu.

cmd: oem lock
hab check failed for boot
failed to validate boot image

A bad download is assumed. Kind members upload their boot.img for testing purposes if downloads are actually corrupt.

-Results in same error.

Try everything again on Mac.

-Results in same error.

Try everything on Linux Ubuntu.

-Results in same error.

Try everything with Factory Image provided by MotoFirmware.

-Results in same error.

Panic.

Open thread on MototFirmware.

Assume conspiracy.

Wait for answers...

-Still waiting...

Please tell me I'm doing something wrong or overlooking something.
[Nexus 6 Q&A, Help & Troubleshooting] :
Please, just verify for me. After flashing factory image, did you boot to android and enter developer options and enable OEM unlock? In all my time with nexus, I have never seen this error or the need for the fastboot commands you've used.

I feel things have become way more complicated than they need to be. Download the factory image from the Google nexus development page. Unzip twice to extract all the images. Flash the images individually with fastboot. No need to fastboot erase before flashing. Boot to android, skip all set up, enable developer options, and enable OEM unlock.

Boot back to bootloader and fastboot oem lock.
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Did. See the video I just recorded (making a point here). Same error =(

I don't know. How is this even possible....I dealt with so many Nexus devices (S, Galaxy Nexus, 4, 5, 7. 9) but never had something like this. At the end of the video, the screen of the N6 kinda flickers. That's what happens when I hit enter after fastboot oem lock command.

[YOUTUBE]watch?v=CDBGUBQOxG8[/YOUTUBE]
[Nexus 6 Q&A, Help & Troubleshooting] randras83:
I saw preflash validation failed error on my Moto G. It was caused by a wrong flash. Nothing helped I tried everything, it was a piece of brick. I made a hard brick then send to RMA. Somehow Motorola's bl can corrupted, so I ll never buy a Moto again. I wish you the best!
[Nexus 6 Q&A, Help & Troubleshooting] karandpr:
Advisory :

Refrain from using boot images & bootloader images by Teamkang.

This member has passed off Nexus Q boot images as Nexus 6.

The bootloader is far from Nexus 6 bootloader as shown by member @rbox

http://xdaforums.com/showpost.php?p=61817885&postcount=18

-karandpr

XDA Staff
[Nexus 6 Q&A, Help & Troubleshooting] nhizzat:
An unlocked bootloader shouldn't affect your RMA for burn-in and a broken ear piece. Just send it in.
[Nexus 6 Q&A, Help & Troubleshooting] Ltdrev:
That's what anyone think, unless it's bricked.

I'd take that option over playing with emmc & partition deeper since it's under warranty and not bricked, pretty sure this issue as the thread owner suggested on G+ himself it probably qualify as a "defect".
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
That depends. Samsung for example refused RMA on my previous Galaxy Note 3 because it was rooted (Knox 0x1) which, according to the repair centre, caused the proximity sensor to malfunction. It also depends on location.

My second conspiracy theory is that I'm not the only one. I think there are many more like me that go unnoticed since there's no real reason for many N6 users to lock, or unlock their bootloaders. I'd try to initiate a "lock your bootloader" campaign....maybe not....

Got that!
[Nexus 6 Q&A, Help & Troubleshooting] tflogic:
curious...how have you installed ADB and fastboot? did you download them from the Minimal ADB and Fastboot package? i was having issues earlier with my Nexus 6 on my Macbook trying to flash bootloader images via fastboot and received the same error you did (bootloader) Preflash validation failed. FAILED (remote failure).

i thought that my downloaded image was corrupt but it turned out that ANY image i chose to flash wouldn't work so i started looking at my own system configuration. i downloaded the Android SDK and installed fastboot+adb via the platform-tools in the SDK application. then, i placed the bootloader image i was trying to flash in the same folder as adb and fastboot binaries. then to flash the boot image, i used "./fastboot flash boot boot.img" with the backflash included (if you're on Windows, this might not be necessary). as it turns out, it worked. i think it was because the Minimal ADB and Fastboot package was using an outdated version of the platform-tools.

tl;dr: 1) manually download adb and fastboot via the Android SDK from Google. 2) move the images you want to flash to the same folder as the adb and fastboot binaries (i.e. android-sdk/platform-tools/. 3) flash images using the the binaries in that same folder, not the globally recognized adb and fastboot that you linked via environmental profiles on your system.
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
I did. I tried Google Fastboot and ADB package I took from the SDK. Also Minimal ADB and Fastboot, something called "mfastboot" (Moto G users reported that with mfastboot the (...)system.img missing error would be solved) and the Fastboot and ADB packages provided by motofirmware.com. All of these fastboot packages were also tested on Mac and Linux Ubuntu, on Windows 8.1 Pro N Update 1 and Windows 7 Professional N SP2 (all x64). Resulted in the same errors.

Can we make it, that I add a Poll to this thread asking you guys how locking the bootloader on your N6's worked out? Wait, I already did...

Feel free to comment. In fact, I'm asking you to comment on your experience with locking the bl of your N6.

---------------UPDATE----------------

If the partition table is of any help, here it is.

127|root@shamu:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name

179 0 61079552 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 58351488 mmcblk0p42
179 32 4096 mmcblk0rpmb
254 0 58351488 dm-0
[Nexus 6 Q&A, Help & Troubleshooting] npjohnson:
First off, I like how you organized the OP. I'm gonna have to steal that format, lol.

Here is the issue: Google released a factory image in which the flash-all script fails due to incorrect headers in the factory .zip they provide. This seems like no big deal until your situation. You are unable to OEM lock (potentially due to your kernel, have you tried flashing just the boot.IMG?) And this is easily remidiable by running fastboot OEM lock begin (which is used to fully return the device to stock and re-lock in one command. Unfortunately... Due to the fact that the factory .zip google provided had those messed up headers (headers is the wrong word, but you get the meaning, if I remember the correct term, I'll edit it in), the begin argument causes fastboot to rely on the factory .zip (which is broken).

This is easily fixable as I said above. Unfortunately, Googles oversight makes it much harder/impossible. Send it in for RMA with the device unlocked. I have sent multiple phones in rocking unlocked Bootloaders (in the US), Motorola being one I have sent several devices back into for warranty repair. They didn't complain at all about the bootloader state.
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Yes, one of the many things I've learned during my long odyssee is the issue with Google's semi-broken factory image's. Unfortunately I have no time to test your suggestion as I heavily rely on my phone during the week and need it working. I did the exact same with only flashing the boot.img but while using the "fastboot oem lock begin" command. Of course, didn't work. I'll be back on it this "projec" this weekend.

I live in Europe and things are a bit different here. I never had to return a device, except my Galaxy Note 3 which had that Knox 0x1 stuff and it was refused, despite many people on XDA saying the Knox counter has no impact on warranty. But I've hear from many people here in the EU that returned Nexus' don't have to have a locked bootloader. Many people got their Nexi in an unlocked state back and some even sent theirs in locked state and got it back unlocked. Retailers and manufacturers have a clear statement here. They say unless a device is not in "delivery condition" no warranty/guarantee claims shall be accepted from retailers.

I'm definitely going to RMA either way, though.

----------Update--------

And here's something interesting a kind User on G+ sent me

http://www.androidpolice.com/2015/0...nds-and-cleaner-syntax-for-reboot-bootloader/
[Nexus 6 Q&A, Help & Troubleshooting] npjohnson:
Do Not Go Up to the M Bootloader! That will make successful RMA much less likely.
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Been there already since I knew M bootloader (71.11) is downgradeable. Fastboot OEM lock won't work on M bl. It'll return an error saying a "signed boot.img" is needed to perform the action.
[Nexus 6 Q&A, Help & Troubleshooting] efrant:
First of all, make sure you are using a new version of fastboot. Download this one and extract the files to where your images are (or to where your path points to). Use that version of fastboot, not an older one, not mfastboot.

Next point (related to your question about reduced storage): You should never flash the userdata image contained in the factory image. It's pointless, let alone that it is a 32GB image. Rather than using the command "fastboot flash userdata userdata.img", use "fastboot format userdata". It does the same thing, and you avoid having the lost storage space issue.

Thirdly, try the steps again (using the fastboot I linked to, and not the one currently in your PATH, and using one of the shamu 5.1.1 images found here):

fastboot flash bootloader nameofbootloaderimage.img

fastboot reboot-bootloader

fastboot flash radio nameofradioimage.img

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash recovery recovery.img

fastboot format userdata

fastboot format cache

fastboot reboot

Then boot into Android and make sure that it does NOT ask you for a Google account and password. Then reboot back into the bootloader and execute: fastboot oem lock
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Thank you, but still getting the same error messages. And why shouldn't it be asking for the Google account?

Sidenote; is it normal that I can downgrade from 71.10 bootloader to 7.08?

Also, can you guys tell me what these two files are for? http://motofirmware.center/files/category/98-blankflash-51/

-----Update-----

Got in touch with the guy I bought the N6 from. The device's battery blew up so he returned it in "locked" state. Since he's familiar with Android modding and stuff (Had a long chat with him about Custom ROMs and Kernels) I belive him. The last factory image he flashed onto before returning it was LMY47i after which he locked it. As soon as he got it back from RMA service he checked whether it was charging correctly and then never used it again until I came to buy it. So, whatever happened to it, it happened at the repair centre I think.

-----Update-----

Ok, I should be more precise; I downloaded the ADB and Fastboot files you provided. I replaced my fastboot and adb files with yours. Then, I made a factory reset, flahed a factory image I downloaded previously from Google (LMY47z). Set it up and checked "allow OEM unlock" from within developer options. At this point I started following the third part of your instructions. Did everything exactly as described but unfortunately ended up with the same error messages when trying to lock the bootloader again.

Another Sidenote: The message "(...) fastboot oem lock begin first!" is only known on non-Nexus Motorola devices! I've never seen any reports on the internet of a Nexus 6 returning this fastboot message o.O.

------Update------

Question: If I "fastboot erase system"' and accidentally type "fastboot oem lock" in fastboot mode, will this command be performed immediately or with a Yes/No prompt just like while unlocking?
[Nexus 6 Q&A, Help & Troubleshooting] npjohnson:
Answer to question: Yes. Don't do that.

Make sure you are on stock, and that the ROM boots before relocking, othereize you can't check the allow in lock into check box to unlock :/
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Ok, Guys. Just requested an RMA inquiry. Got accepted. Device will hopefully be repaired at Datrepair. Not Motorola, as in Germany (Europe?) manufacturers have service partners for warranty/guarantee cases. I don't feel confident though. These guys more than once rejected my warranty inquiries. The last one was my Note 3 with a defective proximity sensor. They literally told me that me rooting it would have caused the damage.... Anyway. Described the known defects and also that I'm not able to relock the bootloader. To be precise, I wrote them I had received the device with the bootloader unlocked after the first repair. That's what the actual case is, according to the first owner. I'll let you updated. Wish me luck.

---------UPDATE-------2015/08/10----------

Ok. Since last Friday , the device is being checked for malfunctions and defects. I'm still not sure though. I just expect to get a mail from these guys saying the device is unlocked and thus not covered by warranty.

---------UPDATE-------2015/08/14----------

Man, this guys are really, really slow on updating status. Should've known better. 1,7 Stars on Google Reviews with a total of 23 reviews. Most of them complain about extreme slow progress and non-existent support. How are these guys still in business?

---------UPDATE-------2015/08/17----------

The support team just mailed me, saying the device has been repaired under warranty. No mentioning of what exactly has been repaired. As long as I get rid of the burned in screen I'm fine.

---------UPDATE-------2015/08/27----------

The odyssey just came to an abrupt end. Make sure to read the first few lines in OP.
[Nexus 6 Q&A, Help & Troubleshooting] lilfuzzybunny:
Oh wow that's rough there should be a way to verify a devices history like they have for automobiles. Sorry it took me a bit to get back to you on the g+ post my back flared up. If your curious to what happened I think it has to do with the verification keys pretty much the data gets corrupted so the safety checks fail. Here are some example of what could be the issue here regardless it has to do with coding on their end and thus their responsibility.
[Nexus 6 Q&A, Help & Troubleshooting] Mr_S:
Hope you get another 6 mate!
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Thanks mate. Just got a new white one. Not some used, second hand crap. But guess what? The backcover doesn't adhere properly. FML big time!
[Nexus 6 Q&A, Help & Troubleshooting] chrisram88:
Like they say "if it isn't one thing, it's another" Best of luck.

Sent from my Sexy Nexy 6 with Pure
[Android Q&A, Help & Troubleshooting] Feliine:
So, I flashed my GS3 with CM12 last night and I'm in love. Completely They've done a really clean job there. But the only issues I'm facing are my screen flashes. My Screen flashes black when I'm having an incoming call. I guess the proximity sensor is acting up or something. Is there a way to fix it? It is really annoying

P.S. New to this forum. If my thread isn't in a section it's supposed to be please pardon me.

Thank you.
[G2 Q&A, Help & Troubleshooting] Cinderella17:
Hello, today I just saw I have a problem with my screen, some area don't respond at all, what can I do? This is some hardware problem or software?

I attached a screenshot

Help please

Enviado desde mi LG-D800 usando Tapatalk 2
[G2 Q&A, Help & Troubleshooting] Mashed_Potatoes:
time to change screen or digitizer..... had same problem
[G2 Q&A, Help & Troubleshooting] Cinderella17:
Wow is a hardware problem... That sucks

Enviado desde mi LG-D800 usando Tapatalk 2
[G2 Q&A, Help & Troubleshooting] Mashed_Potatoes:
:( i had left and right vertical line dead from top to bottom of screen...**** happens, but the seller paid for fix. still not good, replacement screen not as good and there is bezel light leak at max brightness in dark
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jaaard:
Im trying to unlock my phone but im on stock I337UCUGOC3(5.0.1 Cannot be rooted yet) and cannot unlock phone unless i downgrade my modem to the 4.2.2 modem as stated in method 2 here: http://xdaforums.com/showthread.php?t=2595457. Although i haven't tried to install the modem given in that link, I have already tried it with another file because i'm afraid i wont be able to go back to my original baseband which OP hasn't uploaded.

P.S. i flashed the modem.bin from this link http://xdaforums.com/showthread.php?t=2496517&page=66#post61639532 tried MDL and MF3 both didn't work

P.P.S. whenever i try to flash in odin it fails with this log:

*******************************************************

ID:0/014> Now Writing.. Please wait about 2 minutes

<ID:0/014> FAIL! (Auth)

<ID:0/014>

<ID:0/014> Receive Response from boot-loader

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/014> Removed!!

*******************************************************

Please help me. I'm happy to give more information if you need it.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
First, you can root oc3, although it takes some gyrations. Read thorough this, http://xdaforums.com/showthread.php?t=2616221

I haven't done this but here is what I'd try:

Odin to nb1

Root phone

Install safestrap

Flash mf3 modem

Run regionlockaway

If it works, once the sim is unlocked it'll remain unlocked even with future Odin flashes. I'd then Odin nb1 again to get the newer modem back and then work your way back to oc3 using the information in the link above. The information is all there, it'll just take a fair amount of reading and planning.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jaaard:
I'm trying it now as I type. Thanks dude :)
[8525, TyTN, MDA Vario II, JasJam General] system366:
Anyway to get free FM Radio reception on my SPV M3100??? If so how might i go about setting this up?

Thanks in advance

Your friendly neighbourhoob

|-|4X0|2 //\\//[][]8
[8525, TyTN, MDA Vario II, JasJam General] Malik05:
hermes doesnt have an FM module...the closest you can come is getting a program...such as Resco Music player or something like that, i forgot what it was called, but Resco has a music player that offers online music
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Zanny1540:
EDIT: I went ahead and ordered a replacement as it was under warranty, so an Admin can delete this if they see it (I looked and couldn't find that ability to do it myself).

I, like many other TURBO owners, started the Lollipop update today, but unlike many others, my phone seems to have been bricked by the update.

I am, unfortunately, not exactly sure at what point the update killed my phone, but I'll explain what lead up to it.

I jumped on my company's wifi to download the update, and it said it would take about an hour to do so, so I went back to work. About half an hour later I wanted to check the download progress, so I waved my hand over the screen and it did not light up. I tapped the phone's screen and it did not light up. I tapped the Lock button and the screen did not light up. I tried holding the Lock button to power the phone up, nothing. I tried holding Lock and Volume Up to reset the phone, nothing. I've tried plugging my phone into wall outlets and a computer to charge, nothing.

I did not have my phone plugged in before starting the update, which I now regret not doing, but I charge my phone every night and only lightly use it during the day, and it wasn't below 80% before starting the update, so I highly doubt it ran out of power after half an hour of downloading, and even if it id, plugging it in would have woken it up. Unless somehow the power did run out, and the download took less time than it should have and the phone started the update process and then died due to running out of power, I have no idea what is wrong.

I fear the phone is bricked and I'll have to take it into a Verizon store, but if anyone has any information on what might have caused this, I'd greatly appreciate it.

~Zanny
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] kinglove1211:
Use the unbrick method posted in general, install all the drivers and it'll bring your phone back to life.
[Android Apps and Games] theonlyanil:
Check out my latest app in Play Store. hCamera. It’s a nifty tool to take pictures and videos discreetly. No preview, no sound. Minimal to the core. Beautiful UI. I hope you like the app. Please shoot your feedback :)

Checkout screenshots in attachments.
[Android Apps and Games] Ragnoraks:
I cant find it)
[Android Apps and Games] theonlyanil:
Here's the link to the app: https://play.google.com/store/apps/details?id=com.widefide.hCamera
[ZenFone 2 Q&A, Help & Troubleshooting] mattfreyer45:
I simply want to get the performing compatible micro-sd for the zenfone 2. If any one has links to compatible micro-sd cards please post them here.
[ZenFone 2 Q&A, Help & Troubleshooting] glock24:
I have a SanDisk Ultra 64GB, its a class 10 or UHS-I. Here's the link:

http://www.amazon.com/gp/aw/d/B00M55C1I2/

I also tried the PNY Turbo 32GB, had better read performance, but slower writes :

https://www.amazon.com/dp/B00N2ROHA2/
[ZenFone 2 Q&A, Help & Troubleshooting] Asus_USA:
Zenfone 2 supports up to 128GB microSD, microSDHC, and microSDXC, with speed class up to Class 10

Sincerely

ASUS_USA
[ZenFone 2 Q&A, Help & Troubleshooting] cmendonc2:
So now it does support 128 GB officially. Everywhere else it is only 64GB.