• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help with OTA 4.4 Upgrade

K

kwalla

Well-Known Member
So.. I got the notice that I was upgrading to 4.4 and was all happy. It did the download and then install.. but during the install there was an "error" and I got a nice little picture of the Android icon on its back and the words "no command". Rather cute, except for the whole no command bit...

I run an unlocked, but otherwise stock version of Android -- just unlock to take advantage of some root programs. So I'm a little surprised at the error.

If I hold Volume Up and Power, "Google" appears on the screen... but it ends up at the same "error" screen with a droid on its back and "no command" displayed.

Thoughts on what I do to get up and running?
 
From a black screen... if I hold Volume Up and Power, I get a vibrate and then "google" displays on the screen. I let go.. and it ends up at a screen with a Droid on it's back and "No command" beneath.

Is there a way to force a factory reinstall?
 
Id suggest booting into your boot loader if you can and fastboot flash the latest factory images so that everything is “fresh”
 
I can get into fastbook -- I can pick Start (ends in no command); restart bootloader (ends in no command); Recovery Mode (ends in no command) and Power off.. which ends in a blank screen that then displays a battery icon.

Sounds as though I'm screwed.. the OTA truly did brick my phone.

Again: I'm stock, just unlocked..
 
You're not screwed.
That menu you just described, that's where you need to be. The fact that you can get there is good news.

These instructions assume you are using Windows 7.

1. You need to download the Android SDK from Google, and the 4.4 factory images. Be ABSOLUTELY SURE to download the correct images. Some people have screwed up their phones by flashing the Nexus 7 image. You want the KRT16S for OCCAM.

2. These files are both about 2-400 MB. Unpack both the SDK and the images to a folder(for convenience, I created a new folder on my Desktop).

3. Make sure the proper drivers for the phone are installed. To know whether or not they are, boot into fastboot, open a command prompt in your new folder, and type the command 'FASTBOOT DEVICES'. If the drivers are set up right, you'll get some sort of serial number. If not, you need to uninstall your phone in Device Manger, and then install the proper Google ADB drivers(not the default drivers from plugging in your phone).

4. THIS PART ONLY APPLIES IF YOUR BOOTLOADER IS UNLOCKED. You can flash the images without losing your data by editing the flash-all.bat file that comes with the image. right click the file(Don't run the file), select Edit, and remove the -w from the last line. This will stop it from wiping everything. If you have a locked bootloader, this won't apply.

5. with your phone plugged in and in fastboot mode, run the flash-all.bat file. This should install 4.4 on your phone and clear up your bootloop. If it fails, try a different USB cable or a different port on your PC.
 
I am glad to hear that I'm close... but still not quite there. Sorry if I'm a newbie at this.. but I've downloaded and extracted the two files.

I am on Windows 7.

If I open a command prompt (get the old school DOS prompt) and typed in:

Fastboot Device (or devices)

I get: fastboot is not recognized.

So, I then opened opened up SDK Manager. This opens opens a new window with all sorts of options and whatnot. I picked 4.4 and Install License.. and it set about downloading files...

Even after installed, when I'm at the dos prompt and type in FASTBOOT DEVICES, I get Fastboot is not recognized as an internal or external command.
 
Make sure that in DOS, you are operating in the same folder as Fastboot.exe

There are tweaks to make this command work system wide, but that requires more detail. For the sake of our purpose here, just navigate to the same folder. If your folder is on the desktop, go to your desktop, hold SHIFT and right click the folder. One of the top options should be "Open Command Prompt Here".
 
So... A couple things (mostly to help anyone else in my position):

I had downloaded kitkat & SDK to separate folders, one folder is best -- 4.4. needs to be in the same folder as fastboot.exe. I, originally, had them in separate folders -- that won't work.

Fastboot.exe is in a subfolder that, for me, ended up being in:

C:<user>\Desktop\SDK Download\adt-bundle-windows-x86_64-20131030\sdk\platform-tools

I then moved the 4.4. file to inside this folder. Then when I doubclicked (ran) the flash-all.bat file (from which I removed -w as I'm unlocked)... everything seemed to work.

My phone flashed and did all sorts of things.. often with long pauses, but ended up at my usual lock screen when I go into settings -- it says 4.4.

I'm off to explore and see what's what!!

Thanks VERY MUCH to bjacks12 -- you are awesome!
 
kwalla said:
So... A couple things (mostly to help anyone else in my position):

I had downloaded kitkat & SDK to separate folders, one folder is best -- 4.4. needs to be in the same folder as fastboot.exe. I, originally, had them in separate folders -- that won't work.

Fastboot.exe is in a subfolder that, for me, ended up being in:

C:<user>\Desktop\SDK Download\adt-bundle-windows-x86_64-20131030\sdk\platform-tools

I then moved the 4.4. file to inside this folder. Then when I doubclicked (ran) the flash-all.bat file (from which I removed -w as I'm unlocked)... everything seemed to work.

My phone flashed and did all sorts of things.. often with long pauses, but ended up at my usual lock screen when I go into settings -- it says 4.4.

I'm off to explore and see what's what!!

Thanks VERY MUCH to bjacks12 -- you are awesome!
Click to expand...

Glad it worked. I know that sinking feeling when you think your device is toasted. Last month I tried rooting my phone through a faulty toolkit. Ended up in a bootloop. Fortunately the members here(especially Jhawkkw) got me up and going. Just trying to share the knowledge.


Keep us updated on how KRT16S is. I'm running the older build from last week, KRT16O. I haven't updated yet due to fears of bugginess.
 
bjacks12 said:
Glad it worked. I know that sinking feeling when you think your device is toasted. Last month I tried rooting my phone through a faulty toolkit. Ended up in a bootloop. Fortunately the members here(especially Jhawkkw) got me up and going. Just trying to share the knowledge.


Keep us updated on how KRT16S is. I'm running the older build from last week, KRT16O. I haven't updated yet due to fears of bugginess.
Click to expand...


Its running fine for me. I was just about to flash the KRT16S image and then the system update notification just popped up in my notification draw. If anything its less buggy then the first build which I found would make my music skip when playing on the phones speaker and laggy multi tasking. Multi tasking lagged maybe once or twice but its barely noticeable and will be smoothed out in the next bug fix.
 
I went ahead and flashed it and it seems to work fine.

Didn't resolve the issue I've been having with my phone not connecting to my uni's wifi. Works fine at home though.
 
bjacks12 said:
Glad it worked. I know that sinking feeling when you think your device is toasted. Last month I tried rooting my phone through a faulty toolkit. Ended up in a bootloop. Fortunately the members here(especially Jhawkkw) got me up and going. Just trying to share the knowledge.


Keep us updated on how KRT16S is. I'm running the older build from last week, KRT16O. I haven't updated yet due to fears of bugginess.
Click to expand...

The only real comment I can make today is that the battery (based on one instance) is greatly improved. My phone was at 98% when I went to bed, so I took it off the charger. When I checked it next, a little over eight hours later, it was 90%. Prior to this update, it would have been more like 80 or 82%.

This is with WiFi on and GPS set to Battery Saving.

I've not noticed anything buggy about the phone, but then.... I'm a simple user, not a tinkering power user.

Thanks again!
 
Hey guy
Few days ago i got the official 4.4 OTA update for my n 4 but while installing updates at cwm recovery after reboot , installing stops and i see ( signature verification failed) when try to disable verification i cant . The only choice i got is " install without verification ", but again i get the error " installing aborted".
My device is rooted with cwm installed .
I got the official update to 4.4 3times with the no luck for a successful update
Plzzzz any help
 
alikhd said:
Hey guy
Few days ago i got the official 4.4 OTA update for my n 4 but while installing updates at cwm recovery after reboot , installing stops and i see ( signature verification failed) when try to disable verification i cant . The only choice i got is " install without verification ", but again i get the error " installing aborted".
My device is rooted with cwm installed .
I got the official update to 4.4 3times with the no luck for a successful update
Plzzzz any help
Click to expand...

You need the stock Android recovery in order to apply OTA updates - or some folks have had success with recent versions of TWRP. CWMR won't cut it.
 
alikhd said:
Well i did upgrade from twrp to cwm ...any way that i can roll back to twrp ?
Click to expand...

Yep. Either find a flashable .zip of TWRP and flash it in CWMR, or else grab a .img of TWRP and flash it in Fastboot.

Or you can grab the stock recovery .img out of the factory image of whatever you're currently on and flash that through fastboot.

Or if you're going to be flashing through fastboot you might as well just flash the 4.4 factory image - much fewer issues there than with the OTA. Just be sure to remove the -w option from the flash-all script so your data doesn't get wiped.
 
You must log in or register to reply here.
Back
Top Bottom