Database Info

Possible Brick after attempting to install Xposed

Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.

jimburke57 said:
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
Click to expand...
Click to collapse
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?

Zepius said:
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Click to expand...
Click to collapse
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.

jimburke57 said:
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
Click to expand...
Click to collapse
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.

Zepius said:
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Click to expand...
Click to collapse
I have followed it already. The images on the first post are my result.

It is showing as unlocked at the booloader and on fastboot oem device-info.

follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701

Zepius said:
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Same thing as before. All of the erase commands get processed, but when it gets the the system.img it fails to write it.

I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.

jd1639 said:
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
Click to expand...
Click to collapse
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.

jimburke57 said:
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
Click to expand...
Click to collapse
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.

orangekid said:
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
Click to expand...
Click to collapse
Are you talking about these drivers?

jimburke57 said:
Are you talking about these drivers?
Click to expand...
Click to collapse
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.

orangekid said:
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
Click to expand...
Click to collapse
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.

jimburke57 said:
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
Click to expand...
Click to collapse
Have you tried flashing stock kitkat (from google) via fastboot?

orangekid said:
Have you tried flashing stock kitkat (from google) via fastboot?
Click to expand...
Click to collapse
yes, many times

So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.

pantlessjim said:
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
Click to expand...
Click to collapse
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.

Here is some additional information. When I perform a factory reset in recovery it freezes while formatting /data. And when flashing the stock images, I am able to flash everything successfully except for the system.img

jimburke57 said:
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Click to expand...
Click to collapse
Have you tried just dirty flashing stock / rooted thru recovery?
edit: or restoring a backup?

[Q] Reset tamper, flash stock, oem lock

I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?

You could read the guide in general (sticky thread) which answers all these questions
Sent from my Nexus 5 using Tapatalk

rootSU said:
You could read the guide in general (sticky thread) which answers all these questions
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, however the guide seems to use a separate flash step to reset tamper, I was specifically interested in using the app instead if possible.

Android.Addiction said:
Thanks, however the guide seems to use a separate flash step to reset tamper, I was specifically interested in using the app instead if possible.
Click to expand...
Click to collapse
Your steps look good to me. There are a couple ways to flash the stock firmware, make sure your userdata gets wiped. You could also go into stock recovery when you're finished and factory reset.

Aerowinder said:
Your steps look good to me. There are a couple ways to flash the stock firmware, make sure your userdata gets wiped. You could also go into stock recovery when you're finished and factory reset.
Click to expand...
Click to collapse
So far I've just been running the steps inside ./flash-all.sh manually:
Code:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-hammerhead-kot49h.zip
I can add this extra step before the above commands if needed:
fastboot erase userdata
Thanks man!

Android.Addiction said:
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
Click to expand...
Click to collapse
for the record: don't do this! it DANGEROUS to oem-lock without a working stock recovery corresponding to your bootloader version! its not mentioned often, but fastboot oem unlock uses the stock recovery to do the wipe plus unlock. this means: no stock recovery, no unlock!
yes, you can manually unlock THIS DEVICE because we know how to, IF YOU CAN BOOT AND BE ROOT. if you cant get root from android or recovery (say, recovery doesnt boot and android is not rooted) then you CANT UNLOCK EVER AGAIN.

Lanchon said:
for the record: don't do this! it DANGEROUS to oem-lock without a working stock recovery corresponding to your bootloader version! its not mentioned often, but fastboot oem unlock uses the stock recovery to do the wipe plus unlock. this means: no stock recovery, no unlock!
yes, you can manually unlock THIS DEVICE because we know how to, IF YOU CAN BOOT AND BE ROOT. if you cant get root from android or recovery (say, recovery doesnt boot and android is not rooted) then you CANT UNLOCK EVER AGAIN.
Click to expand...
Click to collapse
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app

EddyOS said:
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
Click to expand...
Click to collapse
The steps the last guy quoted did flash factory images before locking.

rootSU said:
The steps the last guy quoted did flash factory images before locking.
Click to expand...
Click to collapse
Yeah, but the guy I was quoting was on about the issues present in the OPO where there are issues with the bootloader getting stuck locked if not using a stock recovery

rootSU said:
The steps the last guy quoted did flash factory images before locking.
Click to expand...
Click to collapse
lol yes he did, sorry! i thought he run the toggle-lock/reset-tamper script. my bad.

EddyOS said:
Yeah, but the guy I was quoting was on about the issues present in the OPO where there are issues with the bootloader getting stuck locked if not using a stock recovery
Click to expand...
Click to collapse
Sorry, to clarify -
Poster 1 - Outlines correct steps
Poster 2 - Don't do this this it's dangerous
You - yeah but its not dangerous. You're thinking of opo
Me - Actually the steps highlighted originally are correct and would work even on Opo!

rootSU said:
Sorry, to clarify -
Poster 1 - Outlines correct steps
Poster 2 - Don't do this this it's dangerous
You - yeah but its not dangerous. You're thinking of opo
Me - Actually the steps highlighted originally are correct and would work even on Opo!
Click to expand...
Click to collapse
In a nutshell, although the guide in my signature covers all bases with the OPO as I wrote it when I had one!

EddyOS said:
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
Click to expand...
Click to collapse
what makes you think its not the same? any source to that info? i have a nexus 5 with me here, and i remember that fastboot oem unlock ran something that looked liked a recovery. do you mean to tell me that the bootloader has its own independent recovery image built into part of its partition to boot to and do the unlocking? because otherwise i dont see how it would do it. please explain.

Android.Addiction said:
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
Click to expand...
Click to collapse
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.

Lanchon said:
what makes you think its not the same? any source to that info? i have a nexus 5 with me here, and i remember that fastboot oem unlock ran something that looked liked a recovery. do you mean to tell me that the bootloader has its own independent recovery image built into part of its partition to boot to and do the unlocking? because otherwise i dont see how it would do it. please explain.
Click to expand...
Click to collapse
What I mean is there's an issue with the OPO where you relock the bootloader without the stock recovery and you then can't unlock it again. It's not been documented that the same fault happens in the Nexus range, but if the OP follows the guides available on here it'll all be OK

gee2012 said:
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Click to expand...
Click to collapse
all N5 have tamper flag. it was introduced mid life of the N4 via a bootloader upgrade. i had an N4 at the time and thought that move was sh*tty.

gee2012 said:
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Click to expand...
Click to collapse
Yes it does

EddyOS said:
Yes it does
Click to expand...
Click to collapse
Where can you see it? Not in the bootloader menu as i see. So its reset tampered flag (BootUnlocker), flash the factory image and afterwards lock the bootloader in fastbooot?

EddyOS said:
What I mean is there's an issue with the OPO where you relock the bootloader without the stock recovery and you then can't unlock it again. It's not been documented that the same fault happens in the Nexus range, but if the OP follows the guides available on here it'll all be OK
Click to expand...
Click to collapse
yes, we've established the steps are ok and it was my misreading.
but regarding my warning about locking with non working stock recovery: its not been documented, but im sure it happens all the same! the bootloader uses a recovery (presumably the one recovery we know and not an image embedded in the bootloader itself) to wipe data. and it would be a mistake to unlock before wiping. so the bootloader does the wipe-then-unlock by delegating everything to the recovery. no recovery, no unlock.

gee2012 said:
Where can you see it? Not in the bootloader menu as i see. So its reset tampered flag (BootUnlocker), flash the factory image and afterwards lock the bootloader in fastbooot?
Click to expand...
Click to collapse
When connected in fastboot, type
fastboot oem device-info
And it'll show device tampered true or false
To get it all back to stock, flash the factory image completely then boot TWRP (don't flash it) and run the bootunlocker script found in the Nexus 5 unroot thread

[Q] about root

are the modaco's rooting method still viable ? I'm seeing people saying it not work.
and can we root without having to flash other recovery, just using the default one (fastboot).

Nope, no rooting methods without unlocking bootloader yet. Most reliable method is to use custom recovery to root, and also some other fastboot (which will need unlocked bootloader)

hemanthmahesh said:
Nope, no rooting methods without unlocking bootloader yet. Most reliable method is to use custom recovery to root, and also some other fastboot (which will need unlocked bootloader)
Click to expand...
Click to collapse
root with unlocking bootloader is fine, my question is can we root without flashing other recovery (eg. cwm) ?

Recovery is not working in Moto g sometimes.. It's a known issue.. So better flash cwm to avoid bricking
Sent from my XT1033 using XDA Premium 4 mobile app

padhu1989 said:
Recovery is not working in Moto g sometimes.. It's a known issue.. So better flash cwm to avoid bricking
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
oh thank you for the info, then I root with cwm :good:

Stock recovery is pretty useless now, I hardly have any idea what it can even be used for other than those ota updates. Do you not want to move away from stock recovery cause you might not install firmware updates? You can install alternate recovery just for rooting and revert back to stock if you really want to.

hemanthmahesh said:
Stock recovery is pretty useless now, I hardly have any idea what it can even be used for other than those ota updates. Do you not want to move away from stock recovery cause you might not install firmware updates? You can install alternate recovery just for rooting and revert back to stock if you really want to.
Click to expand...
Click to collapse
I just being careful if not how to send warranty

Well, if you are unlocking the bootloader, you won't be able to claim warranty anyway.

hemanthmahesh said:
Well, if you are unlocking the bootloader, you won't be able to claim warranty anyway.
Click to expand...
Click to collapse
oh yeah forgot about that, but what if after root, I lock back the bootloader ?
is the root still there ?

To lock bootloader you have flash your stock firmware, which in a way would be a complete reset, so no root left. Also, whatever you do after with the phone, once you request the unlock code from the moto website, they will consider your phone unlocked, hence no warranty. You can relock to try your luck and they just might not care if you are lucky.
Be very careful with locking bootloader though, locking your bootloader in a wrong way (wrong firmware, not flashing all files, downgrading) will create a big mess. In my opinion, stay away from locking bootloader!

hemanthmahesh said:
To lock bootloader you have flash your stock firmware, which in a way would be a complete reset, so no root left. Also, whatever you do after with the phone, once you request the unlock code from the moto website, they will consider your phone unlocked, hence no warranty. You can relock to try your luck and they just might not care if you are lucky.
Be very careful with locking bootloader though, locking your bootloader in a wrong way (wrong firmware, not flashing all files, downgrading) will create a big mess. In my opinion, stay away from locking bootloader!
Click to expand...
Click to collapse
thank you man, btw can you help me with rooting by flashing cwm ?

You need working adb and fastboot drivers.
Download here:
http://www.mymotocast.com/download/MDM?platform=windows (drivers)
https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc (minimal adb and fastboot files)
http://forum.xda-developers.com/showthread.php?t=2563599 (cwm download)
Guide:
1. http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6 (For unlocking bootloader)
2. After unlocking (which will be equal to a complete reset, no files left in your "sd card"), boot into fastboot mode again and use this command:
fastboot flash recovery recovery-clockwork-6.0.4.7-falcon.img (or whatever is the name of recovery image file)
or use this tool:
http://forum.xda-developers.com/showthread.php?t=2635706
You can also use that too to push supersu to sd card or manually place it. Reboot to recovery (adb reboot recovery) and flash that zip file.

hemanthmahesh said:
You need working adb and fastboot drivers.
Download here:
http://www.mymotocast.com/download/MDM?platform=windows (drivers)
https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc (minimal adb and fastboot files)
http://forum.xda-developers.com/showthread.php?t=2563599 (cwm download)
Guide:
1. http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6 (For unlocking bootloader)
2. After unlocking (which will be equal to a complete reset, no files left in your "sd card"), boot into fastboot mode again and use this command:
fastboot flash recovery recovery-clockwork-6.0.4.7-falcon.img (or whatever is the name of recovery image file)
or use this tool:
http://forum.xda-developers.com/showthread.php?t=2635706
You can also use that too to push supersu to sd card or manually place it. Reboot to recovery (adb reboot recovery) and flash that zip file.
Click to expand...
Click to collapse
thanks man, seriously million of thanks

[Q] Root in the past - Warranty

Hi guys,
I have a question for u. If I have rooted my N5 in the past and now I went back to stock, is it possible to check it?
And is it a reason to cancel my warranty?

If you returned to stock properly, no it cannot be traced.
Google won't reject warranty by apparently LG might
Sent from my Nexus 5 using Tapatalk

Did you reset the tamper flag? That's the only way Google/LG would know you modded.

How
BirchBarlow said:
Did you reset the tamper flag? That's the only way Google/LG would know you modded.
Click to expand...
Click to collapse
Is it a way to reset temper flag without working screen? I watched this video - How to Unbrick or Unroot the Nexus 5 (incl. Tamper Flag Reset) on YT and I can't flash cwm-Nexus.BootUnlocker.zip because I don't have working screen and TWRP isn't help for me. Is there any other way to install cwm-Nexus.BootUnlocker.zip without TWRP?

AdamDubas said:
Is it a way to reset temper flag without working screen? I watched this video - How to Unbrick or Unroot the Nexus 5 (incl. Tamper Flag Reset) on YT and I can't flash cwm-Nexus.BootUnlocker.zip because I don't have working screen and TWRP isn't help for me. Is there any other way to install cwm-Nexus.BootUnlocker.zip without TWRP?
Click to expand...
Click to collapse
If you're rooted and you have a video out, you can use BootUnlocker from play

rootSU said:
If you're rooted and you have a video out, you can use BootUnlocker from play
Click to expand...
Click to collapse
I am not rooted, but I can get root via NRT. But I don't want to unlock my bootloader, only to reset temper flag.

AdamDubas said:
I am not rooted, but I can get root via NRT. But I don't want to unlock my bootloader, only to reset temper flag.
Click to expand...
Click to collapse
You cant. ...and you should never use toolkits

rootSU said:
You cant. ...and you should never use toolkits
Click to expand...
Click to collapse
OK, I know now, but I didn't in the past.
Will it work if I simply flash cwm-Nexus.BootUnlock.zip via fastboot using "fastboot flash cwm-Nexus.BootUnlock.zip"?

AdamDubas said:
OK, I know now, but I didn't in the past.
Will it work if I simply flash cwm-Nexus.BootUnlock.zip via fastboot using "fastboot flash cwm-Nexus.BootUnlock.zip"?
Click to expand...
Click to collapse
No. You cannot fastboot flash zips. You can either have root and use an application to do it, or you can have a custom recovery and flash a zip. These are the only 2 ways and both involve you needing video/ screen to do it. If it is not done, there is nothing you can do.

rootSU said:
No. You cannot fastboot flash zips. You can either have root and use an application to do it, or you can have a custom recovery and flash a zip. These are the only 2 ways and both involve you needing video/ screen to do it. If it is not done, there is nothing you can do.
Click to expand...
Click to collapse
Thanks guys. You're awesome!
I hope LG won't check Temper flag. Rest of my phone is stock.

One more question. If I've flashed all stock files, my recovery is stock too? There was recovery.img file, but I want to be sure. And if not - Does the custom recovery void warranty?

Yes it does.

[Q] Error message while installing android lollipop on Nexus 5

Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!

eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
Do you have a custom recovery or flashed a kernel? You must be 100% stock
Sent from my Nexus 5 using XDA Free mobile app

I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5

eatcyanide said:
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
Click to expand...
Click to collapse
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.

eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
rahul9five said:
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
Click to expand...
Click to collapse
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.

wantabe said:
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
Click to expand...
Click to collapse
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet

rahul9five said:
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
Click to expand...
Click to collapse
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.

wantabe said:
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
Click to expand...
Click to collapse
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?

rahul9five said:
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
Click to expand...
Click to collapse
Flashing the factory image or a system image will always unroot your device. Lock the bootloader using the sdk. The command is fastboot oem lock.

Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?

beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Yea, you can't flash the ota through a custom recovery anymore
Sent from my Nexus 9 using XDA Free mobile app

beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.

rahul9five said:
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
Click to expand...
Click to collapse
Err... I didn't suggest that you flash a custom ROM. Read what I said.