Database Develop

[Q] 'No OS installed! Are you sure you want to boot?' How to reinstall android os?

I dont know much about this stuff (def not tech savvy), but I decided to take my bad esn Sprint HTC One (running 4.3) and try to unlock it myself. I was successful in unlocking the bootloader, and I even rooted the device on my own (woo!!!). I was on the last stage of finally unlocking the phone, so I decided to go for it.
I tried to follow these steps to finally unlock my HTC One, but I did not know how to go to /system/app to replace the files (The 'Root Reader' app didn't show /system/app in my phone).
://forum.xda-developers.com/showthread.php?t=2491840
The files were:
HtcOMADM_SettingsPlugin_SPCS.apk
HtcOMADM_SPCS.apk
As a result, I tried to flash the copy files mentioned previously using this video as a guide
http://www.youtube.com/watch?v=JhR4Je4I8yw
I dragged and dropped the copies into the 'system storage' (not into a specific file) and started wiping data in TWRP 2.6 (Im assuming I wiped something that I shouldnt have). However, now whenever I try to boot my HTC One out of TWRP, I get the 'No OS installed..." message and it just just keeps showing the white screen with the HTC logo when I do boot anyways. When I connect my HTC One to my PC via usb cable, it doesnt even show up. I decided to take a screen shot of my files/drives/etc that I used. When I click on the 'instal' button in TWRP, it no longer shows the 'android' folder while scrolling through the list of things. My phone also automatically shuts off when leaving it on idle (TWRP running) for a bit, it doesnt connect to my PC anymore too
What should I do to get the phone working again? Could I unlock it from here or do I have to backtrack or something? I have very little knowledge about this stuff so please try to explain things easily for me lol

You need to relock your phone and run a ruu and to reroot your phone with the latest version of twrp 2.6 .3.0 and supersu 1.9.1 I think but you can check that when you run the ruu in the app store real quick to see if it is the latest version.

On the PC download the RUU
http://dl3.htc.com/application/RUU_..._NV_SPCS_4.38_003_release_348053_signed_2.exe
Connect USB cable to the phone to the PC (keep the phone connected until you are done)
1. Boot your phone to the bootloader (volume down and power on). Go to fastboot option on the phone menu.
2. Now using fastboot on your PC type fastboot oem lock
3. Boot your phone to the bootloader (volume down and power on). Go to fastboot option on the phone menu.
4. Now using fastboot on your PC type fastboot oem rebootRUU
5. Run the RUU that you downloaded. That will put your phone back to stock.
---------------------------------------
To unlock the bootloader:
1. Goto http://www.htcdev.com/ follow the steps.
Install custom recovery
2. Install TWRP. Download http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img put in in the same folder on your PC as your fastboot.exe command.
3. fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
4. reboot phone.
Install root:
download http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip?retrieve_file=1
copy UPDATE-SuperSU-v1.65.zip to the phone
Boot your phone to the bootloader (volume down and power on). Go to recovery option on the phone menu. That will boot into TWRP. Use the install and install the zip UPDATE-SuperSU-v1.65.zip.

Just sideload a rom.zip
Sent from my HTC One using Tapatalk

elvisypi said:
Just sideload a rom.zip
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
How would I do that? I just installed the HTC 4.2.001 driver to my pc as well

help please. stuck in boot loader screen

What's up guys. I recently bought a 2014 moto x us cellular. Turns out it was stuck asking for the last Google sign in. I decided to flash back to stock using fastboot. Used motofastboot and entered all the commands correctly, but now it says failed to boot or boot up failed after flashing the m Motorola screen for a split second. It also says failed to validate system image in pink. I tried both the 5.0 and 5.1 factory firmware. Fastboot didn't say any errors. I can't get rsd to see it. Any suggestions? Do I need to flash all 9 of the system.img_sparsechunk files?

If RSD Lite cannot see your phone it might have to do with no drivers installed or improperly installed.
You'll have to deinstall any drivers related to Motorola and/or ADB cleanly using USBDeview http://www.majorgeeks.com/files/details/usbdeview.html and DriverStore Explorer [RAPR.exe] https://driverstoreexplorer.codeplex.com/releases/view/99694 .
1.) In USBDeview you'll want to highlight anything related to Motorola, ADB, Google ADB driver, Samsung ADB driver etc and then right click and select 'Uninstall Selected Devices'. Done with this program.
2.) In DriverStore Explorer [RAPR.exe] click on Enumerate, then you'll also want to select the checkboxes next to anything related to items listed in step 1, then on the right side choose 'Force Deletion' box, then click Delete Package. Done with this program.
3.) Restart Windows
4.) Download Lollipop 5.0.2 for USC from http://motofirmware.center/files/file/169-victara_usc_502_lxe2246-33_cid9_cfcxmlzip/ or Lollipop 5.1 for USC from http://motofirmware.center/files/file/248-victara_usc_51_lpe2332-213_cid9_cfcxmlzip/ depending on your current firmware version.
5.) Install Motorola USB drivers for our device (#82) from http://androidxda.com/download-motorola-usb-drivers
6.) Connect your phone, let Windows install the necessary drivers.
7.) Run RSD Lite, browse for the firmware you downloaded earlier, choose 'Decompress and Flash' on the box that pops up. *Do not try to downgrade Lollipop versions as it will fail and you'll end up with a third of the files flashed before it errors*
8.) Wait for your firmware to flash, no need to wipe after the flash since RSD Lite runs the 'erase userdata' & 'erase cache' commands after flashing.
I recommend flashing with RSD Lite since it does everything correctly and automatically. These steps will help make sure your system has Motorola device drivers properly installed.
Try this and let me know if this works. If not, we'll troubleshoot further.

Thanks for such a detailed description man. Drivers are something I always struggle with. I'm downloading everything now and ill try when I get home. I'll let you know how it turns out. Thanx again

Unlocked Bootloader Error Message - System Update Failing

I am from India and I exchanged my iPhone 4S for a Moto X 2014 just this evening wanting to try my hands on the Android experience.
I do not know what the seller did to this phone but I now have two issues. I tried to call the seller immediately after I noticed these problems when I came home but the number is switched off. Shame on him!
After Google'ing I found this forum for android support so I hope posting the problems here would give me some solution
Problem #1: Every time when I boot my phone, it has the warning screen which says "Warning unlocked bootloader".
Problem #2: The warning went off and landed me on the home screen. I connected to my WiFi and saw that there is a software update. I downloaded it and chose to install it. It kept rebooting for 4-5 times and then said "System Update - Failed".
Can anyone please be patient enough to give me step by step solution with download links to get my Moto X2 back in shape as how it was out of the box?
I googled a lot for the keywords "relock bootloader moto x 2014", "unroot moto x 2014" and plenty of links with different download links came up. I do not know which one to trust. I am not dumb and I can easily follow instructions. So, please anyone wanna help?

If the OTA (software update) is failing, maybe it's because the firmware you have was installed via custom recovery, not stock, or even the firmware is custom too, that's why you get a bootloop if you try to install the update.
Can you post a screenshot of your "About phone"? (Settings>About phone).

Nek0x90 said:
If the OTA (software update) is failing, maybe it's because the firmware you have was installed via custom recovery, not stock, or even the firmware is custom too, that's why you get a bootloop if you try to install the update.
Can you post a screenshot of your "About phone"? (Settings>About phone).
Click to expand...
Click to collapse
Thank you for the reply. Attached the screenshot.
i64.tinypic.com/2nu3asn.png

I fiddled around to find out how to get into the Fastboot mode... and I observed something weird there..
AP Fastboot Flash Mode (S)
60.16 (sha-#some checksum number key with date 2015-04-02 and time#
CPU: MSM8974AC EA1.1
eMMC: 2048MB Samsung RV=07 PV=0B TY=57
Battery OK
Device i UNLOCKED. Status Code: 3
Software status: Official
I mean Seriously? I see the word Samsung in a Moto phone? I so regret buying from this seller... too much for a first Android phone :crying:
Well I also managed to Google more and installed the device drivers and the Fastboot software in my Windows PC.
Booted my device in fastboot mode and issues the below commands:
fastboot devices
#my device was shown#
fastboot oem lock
#told me to use the command with begin#
fastboot oem lock begin
#Said something like the image is ready#
Nothing happened then though. I powered on my device and I still see that warning. Still the software update is failing. :crying::crying::crying:

You don't need to unlock your bootloader, it is already unlocked, that's why the bootloader says that the "Device is unlocked", but also says your firmware is stock (Status software official).
If your firmware is stock, I don't know why its failing to apply the update, maybe is because your phone has a custom recovery. Try to enter into that option in the bootloader and see what happens.

Nek0x90 said:
You don't need to unlock your bootloader, it is already unlocked, that's why the bootloader says that the "Device is unlocked", but also says your firmware is stock (Status software official).
If your firmware is stock, I don't know why its failing to apply the update, maybe is because your phone has a custom recovery. Try to enter into that option in the bootloader and see what happens.
Click to expand...
Click to collapse
I am not trying to unlock my bootloader. I am trying to restore it back to the "out of the box" state. I mean I want to lock it and I want it to be in the state how it usually is when bought from the store.
Ok... I google'd how to go into the recovery mode and found this link (teamandroid.com/2015/01/08/enter-recovery-mode-moto-x/).
I followed those steps:
1. Turn OFF your phone.
2. Press and hold the Volume Down button for 2-5 seconds. While holding the Volume Down button, press the Power Button for 1-2 seconds and release.
3. I used the Volume down key to highlight "Recovery" and clicked on the power button to select it.
4. My screen went off. I mean the light gone.
Then I had to press and hold the power on button, it booted my phone with that warning unlocked bootloader message.
What am I doing wrong?
UPDATE:
I did a fastboot, connected phone to PC and issued the below command from PC and get below error:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
UPDATE 2:
I enabled the developers option (by tapping on the Build number multiple times)
So, I installed an app called MobileUncle Tools.
I then opened the app from my mobile and clicked on "Reboot into recover".
It says "Please root your Android first".
OK.. so looks like the phone is not rooted - which is good.
Only the bootloader is unlocked. All I need to figure out is - re-lock my bootloader and make the system update go through successfully.
Any help please?

You must unlock the Developer Options in your phone, and then activate the debugger mode to be able to use adb commands like "adb reboot recovery".
In the About phone menu in settings, press five times the option of "Build number", then the Developer options in settings will be available. Navigate to that menu and activate the Android debugging option, then you should be able to use adb from a command window in your PC.
EDIT: Also, you have to press the up volume button in the bootloader to choose an option, not the power button.
Having the bootloader unlocked doesn't affect system updates via OTA or anything if your firmware and recovery are stock. Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery.

Nek0x90 said:
You must unlock the Developer Options in your phone, and then activate the debugger mode to be able to use adb commands like "adb reboot recovery".
In the About phone menu in settings, press five times the option of "Build number", then the Developer options in settings will be available. Navigate to that menu and activate the Android debugging option, then you should be able to use adb from a command window in your PC.
EDIT: Also, you have to press the up volume button in the bootloader to choose an option, not the power button.
Having the bootloader unlocked doesn't affect system updates via OTA or anything if your firmware and recovery are stock. Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery.
Click to expand...
Click to collapse
I have one question for you:
What do you mean by "Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery".
My understanding is - you are saying my stock firmware is intact because it said Official in the fastboot screen. Right?
Ok... now back to the recovery check... I think I did it.
1. I went in the fastboot mode
2. Used volume down key to scroll down to Recovery option (2nd option)
3. Pressed Volume up key to select it
4. The phone rebooted (The white screen "warning unlocked bootloader" message was displayed this time too)
5. I saw a dead android symbol with the word "No command."
6. I pressed Power and Volume Up key. I saw the recovery screen I guess. There were many options - Wipe data, Wipe Cache, Install from SD, etc.
What do I need to check there?
EDIT:
Ok I noted this number from there:
Android system recovery <3e>
LPE23.32-25.1
followed by the options
reboot system now
apply update from sdcard
etc.
I think this is what has happened:
Google says "LPE23.32-25.1" is the Android 5.1 Lollipop update (v23.16.1, build LPE23.32-25.1)
However, the current Android version on my device "About" screen is 4.4.4
The OTA system update, my device telling me about is Android 5.0 Lollipop version: 22.21.19.en.EU (which is a lower version than my recovery's version)
My menu options look all white and after google'ing I realize that it has Android L's menu. Please see the screenshot i65.tinypic.com/14l4mmb.png
Could that be that reason? What can I do t rectify it?

1) You most likely will want to keep your bootloader unlocked, since it'll give you more freedom to deal with roms and flashing. It won't affect taking OTAs, in fact, I've just taken the 6.0 OTA and my bootloader is unlocked.
2) Don't worry about the Unlocked Bootloader Message. That can be fixed by flashing the correct logo.bin file.
3) If your device is in KitKat (4.4.4) but your bootloader is from Lollipop (5.0 or 5.1), DON'T TAKE THE OTA. There's one post here saying that it'll cause a hardbrick. Your solution will be to manually flash the correct firmware or use RSD Lite.

joseph_1802 said:
1) You most likely will want to keep your bootloader unlocked, since it'll give you more freedom to deal with roms and flashing. It won't affect taking OTAs, in fact, I've just taken the 6.0 OTA and my bootloader is unlocked.
2) Don't worry about the Unlocked Bootloader Message. That can be fixed by flashing the correct logo.bin file.
3) If your device is in KitKat (4.4.4) but your bootloader is from Lollipop (5.0 or 5.1), DON'T TAKE THE OTA. There's one post here saying that it'll cause a hardbrick. Your solution will be to manually flash the correct firmware or use RSD Lite.
Click to expand...
Click to collapse
THANK YOU SO MUCH for clearing that point 1 and 2. That is a relief!
Point #3 - "Your solution will be to manually flash the correct firmware or use RSD Lite."
What do I flash? OTA 5.1 (because my bootloader is from 5.1) or OTA 22.21.19.en.EU (because that is what I see in my phone's Software Update Available screen.
Where do I download those OTA files?
How do I flash using RSDLite? Any guide?
Thank you!
UPDATE:
Found the guide forum.xda-developers.com/showthread.php?t=2231249
I only need to know what I version I need to flash AND where can I download it from. Please?

Best option is flashing the entire firmware of your phone variant using RSDLite. The firmware you're looking for (based on what Google says) is VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3
Can you confirm this? If it's correct, then the firmware is in this folder (Firmwares 5.1 stagefright solved): https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg

Nek0x90 said:
Best option is flashing the entire firmware of your phone variant using RSDLite. The firmware you're looking for (based on what Google says) is VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3
Can you confirm this? If it's correct, then the firmware is in this folder (Firmwares 5.1 stagefright solved): https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Click to expand...
Click to collapse
My recovery screen showed LPE23.32-25.1
So there is just the last number change... the download link you gave is for the version ending with .3 where my recovery shows .1
That should not be a problem, or should it?

Flower07 said:
My recovery screen showed LPE23.32-25.1
So there is just the last number change... the download link you gave is for the version ending with .3 where my recovery shows .1
That should not be a problem, or should it?
Click to expand...
Click to collapse
No it's not a problem. This will give you the latest version with the stagefright patch.
Sent from my XT1095 using Tapatalk

It is .3 because it has the stagefright patch, the .1 version doesn't have that patch but both of them are basically the same, so there's no problem if you flash one or another.

[GUIDE] Return to Stock and Upgrade

Hey guys, I am new to this gear live dev and I want to help out. I just got my gear a few days ago and I'm still playing with it I figured that my device is at 5.0.1 and has Dev-Key in the build number. I went ahead and did some research (more than 35 hours) and came to a conclusion. I figured I can help a lot of people by posting my method here. I am currently on 5.0.2 and I am trying to figure out why I still did not get the 5.1.1 update. Looks like Samsung is slow and I will ask around if anyone got the OTA or I'll sideload the OTA scripts. Making the long story short.
Entering the bootloader (hard way)
Press and hold down the power button until your device reboots. Don't let go yet. As soon as you see the Samsung logo you have to swipe from the top left corner to bottom right corner really fast 2 times. Now let go of the power button and you should be in bootloader. If not keep trying again. I would recommend this as the last resort.
Entering bootloader (easy way):
Enable USB debugging by going to settings -> about device -> tapping build number 7 times. A new option should now show up under settings called developer options. At this point make sure that you have proper adb fastboot drivers. If not you can use the minimal ADB FASTBOOT 15 second Installer I will provide a link to the thread. Make sure that the watch is paired with your phone and keep the phone near you. Connect the watch to your machine via USB and let it recognize the device. Open a terminal or cmd window and enter adb devices. You will most likely be returned with some number and unauthorized. At this step if you get an error such like ADB is not an executable program then you have not installed ADB correctly. Switching over to your phone you will now see a debugging request from your watch. Go ahead and it always allow. Now you have granted debug permissions on you watch. Run the command again and this time, the device should return authorized. Run " adb reboot bootloader ". You will be taken to the bootloader.
Unlocking Bootloader and Flashing and relocking the bootloader:
The first step is to unlock the bootloader (don't know if this voids the warranty but I think it will). After you unlock the bootloader (fastboot oem unlock) WARNING: THIS WILL WIPE YOUR DEVICE and then boot back to the OS set it up and redo the steps under Entering bootloader. Once you have entered the bootloader you will need the stock os which is KMV78Y_stock. It is 4.4w and we will upgrade it soon. Open a cmd and run fastboot devices and you should see your device in the list. If not something is wrong , check if you have the right fastboot drivers and your watch is connected properly. Try a different usb port and don't use a usb HUB. ON WINDOWS extract the zip and navigate to the folder till you see the image files. Here shift+right click and you should see an option for open command windows here. For rest of the other people without windows cd to where the image files exist. Run the command “fastboot flash system system.img ” and “ fastboot flash boot boot.img ” . Once you have done that you will have to relock the bootloader. Relocking the bootloader is an important step to receiving further updates so I recommend relocking it. IF YOU DON'T RELOCK THE BOOTLOADER THEN YOU ARE STUCK ON 4.4W WHICH SUCKS SOOOO MUCH!!!!. Relock the bootloader by running “ fastboot oem lock “. Just keep in mind that you can re-unlock your bootloader after you have upgraded but unlocking bootloader will wipe your device again. *SIGH* I ALSO HATE READING LONG INSTRUCTIONS BUT YOU ARE ALMOST AT THE END!!!. After you relock your bootloader go ahead and swipe down on the screen until you highlight the recovery option and swipe right to select. Once you have booted into recovery you will see a warning sign. Don't Panic. Just tap on the screen and you will be brought to the recovery screen once again select reset and select yes.After the reset go ahead and reboot the device. You will be brought into the android wear stock os. Go ahead and set up your device again and go to the setting ->about device -> software updates. You will see that the update is available. There you go install the updates until you get to android 5.0.2. GREAT YOU HAVE UPGRADED YOUR WATCH. There a few ways to get to 5.1.1 but I have not tried them out. I will post the instructions as soon as I have tried it. If your watch says that there is an update the go ahead and install it. Samsung does not push the update to all users at once as it may kill their servers but roll the update out in batches. If you want to sit tight and wait till it comes through or I will be posting a how to soon.
UPDATING TO 5.1.1 AND TO 6.0
Hey, figured out how we can upgrade without waiting. It is actually really simple and easy. You will need to have a locked bootloader to do this or apply any stock update. It does not work with an unlocked bootloader. Your computer will not recognize your watch when sideloading if you have an unlocked bootloader. So let's get started. Download the ota update zip from the links below leave it in the downloads or move it wherever you want it. Open a terminal window or cmd window to the location of the zip either by shift+rightclick (only windows) or by cd’ing you way. At the location of the zip prepare your watch for sideloading. Reboot to recovery by commanding “ adb reboot recovery” or “ adb reboot bootloader” then going to recovery, or going to fastboot the hard way then to recovery. The choice is yours. Once you are in recovery select adb sideload. Now go back to your computer and hit " adb devices ". You should see your device and sideload. If not then something is wrong. Since you are already in the folder where the zip exists simply enter “adb sideload LIVE.zip” and it should send the file to devise. Don't panic if you interrupt the transfer. It will not apply the changes until the entire file has been transferred. Just redo the steps above to resend it. After the update is complete you can restart your device. Upon restart, you will see that your device has upgraded to 5.1.1. Congratulations. Now to go to 6.0 just go to software update and search for another update. I am starting to love this watch at what it can do in 6.0 so I suggest you upgrade.
Thank you, all and I hope this helped a lot of people out there.
Links:
Stock OS:
Android 5.1.1 OTA:
ADB AND FASTBOOT:
I will post inks as soon as I upload them.
-Soma

No Command/Device is corrupt/update

My stock Nexus 6 wanted to update to April security update. (I believe my phone storage was almost full)
It failed the update, is stuck on No Command dead android guy and then pops this address up.
g.co/abh
Factory reset the only option?

You might want to try flashing the update manually, using ADB and Fastboot. Doing so will wipe your device, so if you have anything in the internal storage, back it up if you can.

I try flashing manually via adb/nexus toolkit and it just says error code 7 on the phone. The device is bootlocked.

this may help
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660

Are you trying to update with an OTA? If I remember correctly, error 7 means an OTA update check found that your phone isn't stock. This happens if you have messed with the system (rooting and other stuff), have a custom recovery (TWRP) or a custom kernel.
If the above applies to you, use factory images and fastboot to update instead (leave out userdata.img so as not to wipe your data). Ooops. Just saw you're bootloader is locked. Your data will get wiped when you unlock... Make sure to have a backup.

I have no backup, the phone is under warranty and as this has happened before. Stock update killed phone, i'm taking it to vodafone today.
I can't be bothered to mess about when my contract comes with warranty

Good thinking...

Didgeridoohan said:
Are you trying to update with an OTA? If I remember correctly, error 7 means an OTA update check found that your phone isn't stock. This happens if you have messed with the system (rooting and other stuff), have a custom recovery (TWRP) or a custom kernel.
If the above applies to you, use factory images and fastboot to update instead (leave out userdata.img so as not to wipe your data). Ooops. Just saw you're bootloader is locked. Your data will get wiped when you unlock... Make sure to have a backup.
Click to expand...
Click to collapse
Exactly same problem, struggling for a day now.
unable to unlock bootloader for flashing the device
"fastboot flashing unlock" returns OKAY but the screen still shows "Device is LOCKED. Status Code: 2"
any suggestions??

Try "fastboot oem unlock".

Strephon Alkhalikoi said:
Try "fastboot oem unlock".
Click to expand...
Click to collapse
"fastboot oem unlock" gives:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.001s
But of course I can't do that as I cannot get it to start. I tried "adb sideload image-shamu-mmb29x.zip" too, but it fails for signature verification probably because it shows I have "MMB29V" on the phone. Downloading "MMB29V" image now, will try that too.

With your bootloader locked, you cannot flash factory images using fastboot, and ADB is not for flashing factory images. You have to flash the Android N preview as an OTA in recovery to restore your device to an operable state. Once Android N finishes optimizing apps and is booted, you need to go into the hidden Development Options menu in Settings and tick "Enable OEM Unlock". Then you can unlock the bootloader in fastboot with the command " fastboot oem unlock" so you can flash factory images.

Aston Martin said:
My stock Nexus 6 wanted to update to April security update. (I believe my phone storage was almost full)
It failed the update, is stuck on No Command dead android guy and then pops this address up.
g.co/abh
Factory reset the only option?
Click to expand...
Click to collapse
Got into the same situation yesterday. Seems like it was not just a security update (it didn't say so though), but it was update for the Android-N preview.
Wasted a whole day trying to figure out what did I do to brick my phone. In the end it was just the stupid update by google.
The solution to the problem now is to update your phone to Android-N preview OTA update - you can get it from here: http://developer.android.com/preview/download-ota.html
aHR0cDovL2RldmVsb3Blci5hbmRyb2lkLmNvbS9wcmV2aWV3L2Rvd25sb2FkLW90YS5odG1s --> base64decode this to get the link [new users not allowed to put direct links ]
Steps for solving your problem:
Connect your phone to the computer
On your phone go to the No Command screen and press the three buttobns (Vol-UP + Vol-DOWN + POWER) simultaneously [it will take a couple of tries before you succeed]
You will now reach the Android Recovery screen
Select the option "Apply update through ADB"
From the computer execute "adb sideload <OTA_UPDATE_FILE_NAME>.zip"
Wait for a few minutes and you will see the update progress on adb
Here OTA_UPDATE_FILE_NAME.zip is the name of the ota-update file you download from the developer.android.com link [given above as base64]. For Nexus 6 it is - shamu-ota-npc91k-201dd8d1.zip
Hope it will save someone a lot of their important time.

Well, I am having the same issue as OP. Stock Android on Nexus 6 (t-mobile), received OTA security patch last night. Checked that I have a little over 1GB storage left (24.90GB out of 25.98GB available) and proceeded with installation. Now it says "device is corrupt" and after the four rotating colorful circle animation it gives me the "Unfortunately, Settings has stopped" message box over and over again which I cannot get past. I tried safe mode and it hits the same error.
I am trying the manual OTA update now as ravikumr posted, but I suspect it may run out of storage space since the zip file is 855MBs. Any way I can go in and clean up some space before the installation?
If the reason the original OTA update failed was due to insufficient storage, that would be a really stupid way to annoy the user. I have been reasonably happy with my phone so far but this experience today sucks. I depend on the phone for a lot of things so I never tried to root it or modify in any way, but I guess that's still not enough to make the phone reliable.
I will post my results with the manual update.

Finding update package...
Opening update package...
Verifying update package...
Installing update...
Target: google/shamu/shamu:N/NPC91K/2751853:user/release-keys
Patching system image unconditionally...
Verifying the updated system image...
E:unknown command [retry_update]
system partition has unexpected contents after OTA update
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
Anyone has suggestion I can try?

I couldn't wait since I needed the phone to work so I did factory reset. I had to do it twice since the first time it looked hung formatting /data (I waited over an hour) but second time it went through fairly quickly. Afterwards it was stuck on the google logo at boot, probably due to the bad system. I reinstalled the Android N preview OTA patch and it successfully completed this time, and I was off setting up the phone again.
I am still not convinced that what I have experienced was not a simple mistake that whoever put this package together forgot to put in code to check for available storage space before allowing the installation to proceed, or it could be a bug that when space ran out the installation code didn't handle it gracefully and started to do bad things. Either way it was a bad experience for me. Luckily I saved all my pictures and videos a week ago so only lost a few pictures plus other data.

I was experiencing this problem with a Nexus 6 - Update failed due to insufficient space, and it was impossible to get back into Settings to unlock the bootloader, to be able to use the Nexus toolkit or to otherwise flash a factory image.
Forgive any repetition herein, I am simply explaining how I was able to fix everything.
I am explaining how to fix this on a Windows PC. Sorry Mac/Linux users.
Firstly - if your bootloader is locked - the simplest way to get the phone back up and running is to download the Android N OTA.zip - download that here: http://developer.android.com/preview/download-ota.html
You will need to have the android sdk toolkit installed - or the basic adb/fastboot version. Click here if you need a guide on how to do that - http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Once you have got the OTA update, and adb is installed do the following:
1. Move the OTA update into the android sdk folder.
2. Rename it Update - for simplicity's sake.
4. Reboot your phone into Recovery mode (switch phone off, hold Volume Down and Power until you get to the Bootloader Menu, Use volume down to navigate to "Recovery" and then press Power. You'll see a dead looking android dude - hold Power and press and release volume up. You'll now be in stock Recovery)
5. Scroll down to Apply update through ADB and select.
6. On your PC - in the Android SDK folder, hold down Shift and then Right Click. Select "Open Command Window Here".
7. Type the following command - "adb sideload <OTA_UPDATE_FILE_NAME>.zip" and press Enter. As explained above, to make this easier I renamed the .zip as "update". It is still a .zip file, so make sure you type adb sideload update.zip.
8. You'll see the progress and once it has done, reboot the phone.
9. If you want to stick with Android N - enjoy your phone.
10. If you don't - do this. You cannot select unlock OEM from Developer options as it is grayed out. Instead (and you need to have signed into your device with a gmail address, and selected yes to be part of the Android Beta Programme) go to the following web address - https://www.google.com/android/beta?u=0
Sign in with the same google account you signed into your device with. Select enrol device. Now select de enrol device - you should then receive a notification for a system update that will downgrade your device to the latest publicly available, stable, Marshmallow build.
And thats it.
I hope this has been helpful, apologies for any repetition.
Thanks

Kam_El said:
I was experiencing this problem with a Nexus 6 - Update failed due to insufficient space, and it was impossible to get back into Settings to unlock the bootloader, to be able to use the Nexus toolkit or to otherwise flash a factory image.
Forgive any repetition herein, I am simply explaining how I was able to fix everything.
I am explaining how to fix this on a Windows PC. Sorry Mac/Linux users.
Firstly - if your bootloader is locked - the simplest way to get the phone back up and running is to download the Android N OTA.zip - download that here: http://developer.android.com/preview/download-ota.html
You will need to have the android sdk toolkit installed - or the basic adb/fastboot version. Click here if you need a guide on how to do that - http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Once you have got the OTA update, and adb is installed do the following:
1. Move the OTA update into the android sdk folder.
2. Rename it Update - for simplicity's sake.
4. Reboot your phone into Recovery mode (switch phone off, hold Volume Down and Power until you get to the Bootloader Menu, Use volume down to navigate to "Recovery" and then press Power. You'll see a dead looking android dude - hold Power and press and release volume up. You'll now be in stock Recovery)
5. Scroll down to Apply update through ADB and select.
6. On your PC - in the Android SDK folder, hold down Shift and then Right Click. Select "Open Command Window Here".
7. Type the following command - "adb sideload <OTA_UPDATE_FILE_NAME>.zip" and press Enter. As explained above, to make this easier I renamed the .zip as "update". It is still a .zip file, so make sure you type adb sideload update.zip.
8. You'll see the progress and once it has done, reboot the phone.
9. If you want to stick with Android N - enjoy your phone.
10. If you don't - do this. You cannot select unlock OEM from Developer options as it is grayed out. Instead (and you need to have signed into your device with a gmail address, and selected yes to be part of the Android Beta Programme) go to the following web address - https://www.google.com/android/beta?u=0
Sign in with the same google account you signed into your device with. Select enrol device. Now select de enrol device - you should then receive a notification for a system update that will downgrade your device to the latest publicly available, stable, Marshmallow build.
And thats it.
I hope this has been helpful, apologies for any repetition.
Thanks
Click to expand...
Click to collapse
This works if you are completely stock with no custom recovery and your OS is gone ? When your phone gets downgraded, does the OEM unlock appear in developer options so you can toggle it ? If so there are a lot of phones in all the threads that have been RMA due to this.

mikeprius said:
This works if you are completely stock with no custom recovery and your OS is gone ? When your phone gets downgraded, does the OEM unlock appear in developer options so you can toggle it ? If so there are a lot of phones in all the threads that have been RMA due to this.
Click to expand...
Click to collapse
This worked for me, specifically with the update issue on a fully stock and OEM locked Nexus 6 that became buggy after the update was attempted but there was not enough memory. After the update failed and it booted back up (there was an error your device is corrupt message on bootup) there were a ton of error messages and the settings app was broken. Package installer was also broken and Google play and media services were broken, therefore couldn't use the Wugfresh Nexus toolkit, couldn't use fastboot as OEM was locked and couldn't access settings to change it. Factory reset from stock recovery did not fix the errors and following bootup the startup wizard couldn't start either.
The only option was to sideload the OTA - however, for the Nexus 6, after the OTA installed the OEM unlock option was transparent and set at off (because my bootloader was always locked). I then enrolled the device on the Beta programme, and then unenrolled it. Almost immediately a downgrade able OTA notification arrived which dropped it back down to Marshmallow. After bootup all seemed fine, then play services stopped working. I was worried until I recieved a notification for a Marshmallow update - after that was installed everything worked fine as normal. The OEM unlock option was again available (although I decided to keep it locked).
For other devices it won't work, as I believe the Android N OTA is for a select few Nexus devices and possibly GPE devices (full list available on the website above).
Whether this work if you've completely deleted the OS - again I'm not sure. But I cannot see the harm in trying in that scenario. More experienced users could assist here. It should work as long as you can get into stock recovery.
Hope this helps.

Thanks Kam_El for posting the instructions. I followed the exact same steps except that "adb sideload update.zip" command wasn't successful (see my posts above). It only worked after I did a factory reset. My phone was stock Android with latest patches.
I followed your last step to downgrade the Android N back to Marshmallow. The main issue I have with N is that wechat crashes the system as soon as it's launched and only a reboot can fix it.

lyuanrich said:
Thanks Kam_El for posting the instructions. I followed the exact same steps except that "adb sideload update.zip" command wasn't successful (see my posts above). It only worked after I did a factory reset. My phone was stock Android with latest patches.
I followed your last step to downgrade the Android N back to Marshmallow. The main issue I have with N is that wechat crashes the system as soon as it's launched and only a reboot can fix it.
Click to expand...
Click to collapse
Glad to have helped. I had already attempted a factory reset before momentarily losing hope lol. Incidentally I'm now running N on my Nexus 9 - loving the new notifications.
Anyway ✌?