yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] haet:
Great guide!

The package for the link https://developers.google.com/android/nexus/images#razorkrt16o fails verification for me as well and does not install once its side loaded. So it's probably beneficial to just point to the other link.:good:
[Nexus 7 (2013) General] sfhub:
The factory image isn't meant to be side loaded. It needs to be installed using fastboot/bootloader.
[Nexus 7 (2013) General] cincibluer6:
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.

If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.

The zip on the other hand is intended for sideloading and should update the OS no problem.
[Nexus 7 (2013) General] haet:
Gotcha.

There is quite a size difference between the the zip and the tgz format. Is this only because of compression format? Or is it more beneficial to flash one over the other?
[Nexus 7 (2013) General] cincibluer6:
^^ I won't go ahead and quote you but thanks for the full on summary. I knew what .tgz was and all that (using Linux for a few years now) but I'm new to most of the Android like stuff.

Thanks for clarifying and explaining it so well.
[Nexus 7 (2013) General] haet:
Just gave the sideload of SuperSU a shot and was given two errors:

failed to verify whole-file signature

signature verification failed
[Nexus 7 (2013) General] sfhub:
You cannot sideload the SuperSU update.zip using stock recovery because it isn't signed by Asus/Google.

It is signed, but using a generic cert.

You need to use custom recovery like TWRP or CWM to install it. You can use their menu system to choose the file or if they have sideload, you can sideload using custom recovery.
[Nexus 7 (2013) General] haet:
Makes sense. Thanks for the help!
[Nexus 7 (2013) General] jbwray:
Windows 2008 server usb drivers?

This guide was great, and everything worked fine until I reboot into recovery and choose to adb sideload an image. Then, the device doesn't get recognized, and the google drivers don't work. So, I can't see the device with the ADB interface driver.

Does any have experience with this? Am I out of luck? I couldn't find anyone talking about drivers for windows server 2008 anywhere -- but usually win7 drivers work fine -- just not here.

I don't have another windows installation anywhere, so if there isn't an answer, I will just have to wait for OTA :(

** UPDATE **

I found some universal drivers from Koushik Dutta: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH

Those drivers worked! Then I used the OTA download (your second option), sideloaded it, and got the update. Now running KitKat, so thanks a bunch! hopefully someone else will find this driver option useful.
[Nexus 7 (2013) General] Castle5665:
I'll give those universal drivers a go. Hell, I've tried everything else on the Internet with complete failure. One last try before I give up.
[Nexus 7 (2013) General] ganstar:
You sir are a genius (and the driver author). I had the exact problem and looked everywhere. I am low tech, too. So following these two guides;

http://phandroid.com/2013/11/13/how-to-install-kitkat-nexus-7/

http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/

I am now on 4.4. And everything is intact. Thank you!
[Nexus 7 (2013) General] doorunrun:
I also ran into Google USB driver problems after the Nexus dropped into recovery mode. So I gave up trying to use Windows 8 and switched over to using Ubuntu workstation. Getting ADB to run on Ubuntu is very easy and so flashing the Kit Kat OTA file was a breeze.

On Ubuntu there's no need to install the full SDK just to get ADB and Fastboot; the process is outlined here: http://xdaforums.com/showthread.php?t=1860108. From there it's just simple command line entries from a terminal i.e. "adb devices."

I was disappointed to see Google has kept the black top and bottom bars for tablets. I usually run Teslacoil's launcher and installed their beta launcher with transparent bars a welcome relief.
[Nexus 7 (2013) General] LoopDoGG79:
If you install the latest Google search apk and GEL from the nexus 5, you will have transparent nav bar.
[Nexus 7 (2013) General] andy_d0:
Hi. This will wipe the device right? We should have a backup before proceeding?
[Nexus 7 (2013) General] haet:
You should also know that Google has drivers as well located at http://developer.android.com/sdk/win-usb.html, which is what you would have downloaded right after you installed the SDK package.
[Nexus 7 (2013) General] BreakShadow:
For those who can't get their devices recognised even after doing everything correctly. Just boot the tablet and change from MTP to PTP. Worked for me.

Sent from my Nexus 7 (2013)
[Nexus 7 (2013) General] jbwray:
I was on PTP. still didn't work

I was on PTP. Still didn't work until I found those drivers. The drivers from Google were what I was using, but they didn't support the device in fastboot mode for the version of windows I was using. (2008 server R2)
[Nexus 7 (2013) General] ganstar:
I had those, they didn't work for me, as others have noted as well.
[Nexus 7 (2013) General] z0phi3l:
OK weird issue, can get to the sideload step, pushed bot version of the file in my attempts yet I still fail verification

I have a 2013 WiFi only N7, downloaded to zip file, renamed it to something manageable, and still get verification failed, completely stock and unrooted

Not sure what gives
[Nexus 7 (2013) General] Castle5665:
Thank you jbwray. Those drivers did the trick. Got 4.4 to side load with ease.
[Nexus 7 (2013) General] Bumoza:
hello

i did everything but when the tablet start to install i got this error E: signature verification failed

in the guide use said i have to use other package to install and you put the link but my tablet is LTE not wifi and i can the package in google site only

i downloaded the package many time with the same error
[Nexus 7 (2013) General] siemens_wolf:
what about LTE model？ how to make an update?

I also met the same case as you. Each time it says signature verification failed. Don't know what's going wrong.

But as I am using the NEXUS.7 2013 LTE, how to get the correct ZIP file? the file you attached later on should be for wifi only.

Many thanks!!
[Nexus 7 (2013) General] sfhub:
You cannot flash a factory image via sideload. The format is intended for fastboot/bootloader.

You can flash an ota via sideload, but only the WiFi ota URL has been posted so far.

At this point on LTE you either need to be patient, or you need to unlock the bootloader and flash the factory image.
[Nexus 7 (2013) General] z0phi3l:
Finally got our flashed, had to download from another source, but I'm on 4.4 and the new GEL
[Nexus 7 (2013) General] InsCof:
updating using fastboot

I followed the instruction but could not get beyond "E: signature verification failed". The OTA did not work either, it kept on giving errors( something /update.zip failed) . To make matter worse, I decided to wipe all data from recovery mode and now the nexus will only boot to recovery mode.

Anyway eventually (in desperation) I unzipped the image (tgz file, tar) and got to the flash-all.bat. Copied all the files( unzipped from the image) to the platform-tools folder and ran flash-all.bat. Once i rebooted to recovery fastboot.exe did its job and flashed Android 4.4 (no signature verification needed). Lost all my data but got the tablet back.

May be it will help you too.
[Nexus 7 (2013) General] Big_Red77:
Its because the zip just patches the files while the tgz replaces the files which is why the tgz can be used if you mess up. The zip is better for updates because it takes less download time because it doesn't have all the system files. That's why you can't use the zip if your on a different version that it was intended for but you can on the tgz format.
[Nexus 7 (2013) General] mstation86:
after reading a lot of comments i have noticed that i made a major mistake trying to sideload the factory image which, as pointed out, cannot be done.

the instructions to load the factory images are as follows:

download the factory image,

extract it using a program like 7zip,

you should now have a .tar file.. extract it again and you should now have a .img file, a .zip file and some scripts

place all these files into the platform-tools folder with adb and fastboot exes

now connect the tablet.. then in the command prompt run the following:

adb reboot bootloader

//this will reboot the bootloader

fastboot flash bootloader bootloader-flo-flo-03.14.img //or bootloader image filename

fastboot reboot-bootloader

fastboot -w update image-razor-krt16o.zip //or image filename

fastboot reboot-bootloader

this should allow you to flash the factory image directly
[Nexus 7 (2013) General] xdhall:
Yes, after seeing so many people worried about problems sideloading the OTA, I read your guide. Suggestion: update the OP. It's causing people a lot of grief.
[Nexus 7 (2013) General] HowardZ:
Since there is no update zip file for the N7LTE (razorg), I used the factory images downloaded from Google.

I edited the bat file to remove the "-w" to avoid wiping my settings and installed apps.

I also made sure to use the latest ADB/FASTBOOT related files from the android-sdk.

It all worked very well, and I am using KitKat KRT16O.

P.S. TWRP and the latest SuperSU flashed afterwards.
[Nexus 7 (2013) General] Knight-Rider:
I used the Nexus Root Toolkit v1.7.8 to update to 4.4 Kit. I was rooted 4.3, unrooted back to stock, than I went back and unrooted again using 4.4 Kit Kat than OEM locked that easy.
[Nexus 7 (2013) General] DarrelK:
Worked well, thank you!
[Nexus 10 Accessories] ShensMobile:
Hi guys,

I have the Nexus 10 book cover accessory from Google but I don't have the original piece that goes where the cover snaps on anymore. Looks like this:

I'm really contemplating not using the book cover anymore because I don't quite like the way it functions. Does anyone know where these are available to be purchased from?
[Nexus 10 Accessories] byt3b0mb:
hey i came across your post earlier today and searched google for nexus 10 parts and found the part you are looking for - its $20

http://www.powerbookmedic.com/Google-Nexus-10-Camera-Cover-p-24379.html
[Nexus 10 Accessories] ShensMobile:
Thanks for the reply man, but unfortunately they're out of stock! :(
[Nexus 10 Accessories] cdsbj6508:
I'm also looking for this and as stated before the website provided states it's out of stock,. Does anyone know where I can get one from.
[Nexus 4 Themes and Apps] isaakmg:
Enviado desde mi Nexus 4 usando Tapatalk 2
[Motorola Photon Q 4G LTE] ZaneKaminski:
Hi all. Trying to make this quick. I have been looking at this device, and it seems that, although it is advertised as having an MSM8960 SoC, that some/all of the Photon Q models actually contain Qualcomm's newer MSM8960DT processor. This is the one included in the Moto X and its Verizon siblings. There is further evidence to indicate that the same may be true of some other devices related to this one, including Droid Razr (Maxx) HD and Droid Razr M.

Is it the case that some of the Photon Q phones do include the 8960DT? Is it that Qualcomm/Moto is trying to consolidate manufacturing in the usual way?

Thanks for the info.
[Motorola Photon Q 4G LTE] arrrghhh:
No, the DT is only for the Moto X family as you stated.

The Razr M, Photon Q, etc all have msm8960's. No DT.
[Motorola Photon Q 4G LTE] ZaneKaminski:
That is what I would think. The 8960 and DT have different actual cores, as well as a substantially different GPU, aaaaaand the contextual processor stuff... not just some silicon revision. However, if you examine this search: https://www.google.com/search?q=%22msm8960dt%22+-%22moto+x%22+-%22droid+ultra%22+-%22droid+maxx%22+-%22droid+mini%22tbs=cdr%3A1%2Ccd_min%3A%2Ccd_max%3A6%2F1%2F2013&tbm=#es_sm=93&espv=210&q=%22msm8960dt%22+-%22moto+x%22+-%22droid+ultra%22+-%22droid+maxx%22+-%22droid+mini%22&tbs=cdr:1,cd_max:6/1/2013,sbd:1

You would find some (limited) info that seems to indicate otherwise. This doesn't really seem that consequential, but how/why would this be? This result I find to be of particular significance: http://xdaforums.com/showthread.php?t=2239042. This doesn't seem to be a typo, and I dunno why he would be outright lying lol. Moreover, the Moto X had not been announced when this thread was made, and so unless he reviewed Qualcomm's roadmap or something (unlikely), he wouldn't even know about the 8960DT.

There are similar occurrences of this type of thing with other devices, including the Electrify and Razr M.

Further questions: Are the 8960 and 8960DT pin compatible? I mean this in a similar way that, for example, the OMAP4470 and 4460/4430 are, or (poorer comparison) some Sandy Bridge and Ivy Bridge processor are compatible. If so, the conclusion that some of these devices had DTs becomes a lot more reasonable.
[Motorola Photon Q 4G LTE] arrrghhh:
lol... ok.

Believe what you would like to believe. cat /proc/cpuinfo does show

Hardware : msm8960dt

But that doesn't mean we have that processor ;)

I'm sure someone who knows more about the SoC can chime in here - but I know we do not have the new Moto X processor, heh.
[Motorola Photon Q 4G LTE] Skrilax_CZ:
That's just a f***ed up naming convention: in our case, msm8960dt means "MSM8960 - Device Tree".

Motorola Droid MAXX shows:

Hardware : msm8960dt

Revision : 8300

Don't have the Q with me now, but I think the revision will be different.
[Motorola Photon Q 4G LTE] arrrghhh:
Ah, thanks.

Yes, the revision is different.

Hardware : msm8960dt

Revision : 82b0
[Motorola Photon Q 4G LTE] kabaldan:
The original Motorola qcom msm8960 family (Razr HD, Razr M, Atrix HD, Photon Q) is based on Snapdragon S4 Plus (msm8960/adreno 225 GPU).

The Moto X family on Snapdragon S4 Pro (msm8960dt/adreno 320 GPU).

(And Moto G on Snapdragon 400 - adreno 305)

I don't think there are any exceptions...
[Nexus 4 Themes and Apps] isaakmg:
I don't see nothing for kit kat odex nav bar 36 dpi + volume awake.... Somebody help?

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Themes and Apps] isaakmg:
Nothing?:confused:

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Themes and Apps] d_phekt:
Give it a few days. I'm sure one of these awesome modders/themers is working on it
[Nexus 4 Themes and Apps] isaakmg:
Thanks..:):beer::thumbup:

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Themes and Apps] ajael44:
Hello,

I'm waiting for this too...

Enjoy !

;)
[Nexus 4 Themes and Apps] isaakmg:
Nothing?

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Themes and Apps] tuliopereza:
I need too

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Themes and Apps] thenobol:
go here:

http://xdaforums.com/showthread.php?t=2508185

by #gnome :D

working perfectly with ak204 using it since about a week ;)
[Nexus 4 Themes and Apps] isaakmg:
This not a mod, is a rom..... We aren't silly..:mad::banghead:

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Themes and Apps] youland:
I need volume wake up for kitkat.

Thanks.
[Nexus 4 Themes and Apps] thenobol:
.. sorry, skipped the heading :eek: !

xposed will be available as fast as possible, according to rovo89, then, xposed mods can be used.
[Nexus 4 Themes and Apps] tuliopereza:
Nothing??

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Themes and Apps] miticogirl:
No nothing, shut up.
[Nexus 4 Themes and Apps] CalicoJeb:
Try this, 36dpi nav bar ...works for me on N5 port

http://xdaforums.com/showthread.php?t=2528433
[Nexus 4 Themes and Apps] tuliopereza:
Work perfectly

flashable zips

http://xdaforums.com/showthread.php?t=2528433

[MOD][KRT16M] 36dpi Nav Bar - for stock ROM
[Nexus 4 Themes and Apps] kij01:
You can do both things in XBlast tools module for Xposed. Working fine on 4.4 stock.

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Themes and Apps] ernadr:
I am on KRT160, can I flash this mod?
[Nexus 4 Themes and Apps] Arhtard:
thought i'd share my setup for stock KRT16S odex

28x28x22 dpi navbar

screen wake on plug/unplug from charger disabled

transparent bars in lockscreen

disabled the constant "select input" notification in status bar
[Nexus 4 Themes and Apps] jcnbama:
So I'm a little confused. I'm on 4.4 KRT16S Nexus 4 stock ROM with ART enabled. Is this a flashable zip I can flash through TWRP? If looks like the one link is only for the Nexus 5 port? Is there one of these mods compatible with ART?
[Nexus 4 Themes and Apps] StormBlizzard:
I try make one on yesterday.

But for 4.4, the systemui.apk is located in system\priv-app folder, not in the system\app folder as before.

When I compile the systemui.apk, many faults or alert jumped up.

After copy the compiled systemui.apk into priv-app folder, reboot the phone, then systemui fault......

I guess maybe 4.4 changed something in this apk....
[Nexus 4 Themes and Apps] vaez666:
not working on 160s :(

i need 32dpi for 160s
[Nexus 4 Themes and Apps] vaez666:
no 36dpi mod for 160s ?

i need it

other mod is for 160 and not working on 160s :(
[Nexus 4 Themes and Apps] SamS1989:
off : how do you do the different lockscreen wallpaper and the another homescreen wallpaper ? used xposed on kitkat, or something else ?
[Nexus 4 Themes and Apps] Nohik52:
You can use Xposed framework with Gravity Box to change narbar dpi (and many tweaks).

Also try the module "Xposed addition" to remap volume up and volume down keys for wake up device when screen is off.

---------- Post added at 11:46 AM ---------- Previous post was at 11:41 AM ----------

Yes, you can do that with Xposed's module "Gravity Box" ;)
[Nexus 4 Themes and Apps] StormBlizzard:
I got a big return key when I use this file.

Could this issue be resolved?
[Nexus 4 Themes and Apps] Arhtard:
i set the wallpaper using the stock launcher then disabled wallpaper in apex launcher.
[Nexus 4 Themes and Apps] Arhtard:
the fix for this is in the systemui.apk.

i found the information here: Big back button fix for small navibar

my modified systemui is uploaded for you below, which has the big button fixed. remember mine is odex.

its a modified version of cargobr151s battery center clock mod. he has like 7 versions to choose from.

the picture i have attached is the mod version i picked and fixed the big back button for small navbar.

.

cargobr151 mods are found here, these have the big back button, and haven't been changed for small navbar just fyi: cargobr151 mod

remember - the files i have uploaded are for krt16s odex rom only

link to my frameworkres.apk is here: http://xdaforums.com/showpost.php?p=47814578&postcount=19
[Nexus 4 Themes and Apps] StormBlizzard:
really great!!! Works fine for meeee.....
[Nexus 4 Themes and Apps] isaakmg:
Thank you......Oleeeeé!!!!!!!!

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 5 Q&A, Help & Troubleshooting] ItzMar:
Hey everyone,

So I've had my Nexus 5 since launch and love it. :)

But I have a problem with dust.

When I take it out of my pocket I have pocket lint and dust all over the screen which I wipe off no problems.

But...

It often gets brushed in to the edge of the screen and falls down a minuscule crack all the way around the edge of the phone.

Anybody have any advice for cleaning this out?

As the white specs annoy me in contrast to the black phone :(
[Nexus 5 Q&A, Help & Troubleshooting] greveldinges:
Use a sheet of paper to get it out :)
[Nexus 5 Q&A, Help & Troubleshooting] nkia2sg:
Yess me too. Only at the bottom of the screen though but it is pretty annoying
[Nexus 5 Q&A, Help & Troubleshooting] lukas_s:
Yup, just noticed it on mine this morning. The corner of a piece of paper slips in there quite easily, less than a mm, and allows you to get most of the dust out.
[Nexus 5 Q&A, Help & Troubleshooting] ItzMar:
Cheers guys! Will try this soon! :cyclops:
[Nexus 5 Q&A, Help & Troubleshooting] Jeimygirl:
Post it would work better. With the tackiness of it it should grab the dust
[Nexus 5 Q&A, Help & Troubleshooting] mrro82:
You really needed a thread for dust? Normal dust. Not dust under the screen but normal dust? Come on man.

Sent from the jaws of my Hammerhead!
[Nexus 5 Q&A, Help & Troubleshooting] ItzMar:
Didn't realise the "Nexus 5 Q&A, Help & Troubleshooting" was limited to questions not concerning dust caught in cracks...
[Huawei Ascend P1] midan:
I wanted to know if any of the members of xda can compile a custom kernel for JB or kitkat for this terminal. Thank you in advance for those who will offer to fill it out I hope for your support.
[Huawei Ascend P1] joke19:
Ghithup?

Gesendet von meinem C5303
[Huawei Ascend P1] midan:
There is a modified kernel to 3.0.31 this upper end that is modded
[Sony Xperia S, Acro S, Ion] entermetallica:
I want to format the 32Gb storage to FAT32 but it keeps on formatting to generic hierarchical. I've heard that FAT32 is much better than generic hierarchical but my main reason is so that I can transfer large files to my Xbox. So is there any way?
[Sony Xperia S, Acro S, Ion] Envious_Data:
its already Fat32
[Sony Xperia S, Acro S, Ion] entermetallica:
I checked on my computer and it said GH

Sent from my Xperia SL
[Sony Xperia S, Acro S, Ion] Envious_Data:
You should download the Sdcard mounter in the theems and apps menu somewhere, it mounts your xs as Fat32
[Sony Xperia S, Acro S, Ion] OathYvne:
edit
[Android Head-Units] sciallo:
If we think about it, Android isn't even part of the equation reading those files really, just a bootloader or the unit's firmware. So the decription layer would have to be built into the bootloader or the raw firmware (read assembly or whatever)... I highly doubt it would be EFS.

As another observation, all filenames remain the same across the two updates and only one file has changed (and it's name remains the same. There goes the hash/sum/md5 like naming theory)...

diff android-4.1-2.6.40/ android-4.1-2.6.60/
Binary files android-4.1-2.6.40/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 and android-4.1-2.6.60/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 differ

That I'm guessing is our system file :)

[MENTION=255685]tin2001[/MENTION] [MENTION=5307836]Orisai[/MENTION] [MENTION=5492644]chris.r.r[/MENTION] <- in case you missed the switch to new thread :)
[Android Head-Units] KID52:
Yes, as you say, it is the only file that changes between the updates, and it is also the largest file so I think we can assume this contains the data we want.

Looking at the third update I have, it seems that file is again the only one changed. I will be testing this update out and uploading it shortly.

The file names must have some importance, as otherwise they could just call them "system.img", or something simple, but still encrypt them.
[Android Head-Units] sciallo:
Have you tried to see if it will read an external mass storage attached to usb? (usb stick, card reader, 2.5" portable hard drive)?
[Android Head-Units] KID52:
The default application yes, although I did not try what happens with multiple USB drives. The doubleTwist music player was unable to read a USB memory stick, or the MicroSD card. The actual unit seems to be able to cope with multiple memory sticks, I have tried three, and all were accessible using the ES File Explorer application.

The internal storage is mounted at "mnt/sdcard".

The MicroSD card is mounted at "mnt/usb/mmcblk1p1".

USB memory sticks are mounted at "mnt/usb/sda1", "mnt/usb/sdb1" etc.
[Android Head-Units] donaldta:
Have you checked for the presence of a hidden file called, ".nomedia" in the MicroSD card? The presence of this file will let most media players to skip this path for scanning for multimedia files.
[Android Head-Units] KID52:
Yes, this file is not present.
[Android Head-Units] sciallo:
You might want to try a few different players to see if it's the unit or the player...

From http://www.doubletwist.com/help/question/how-do-i-switch-from-internal-storage-to-sd-card/

I don't know if you can without root but you should be able to as normal user in a virtual terminal link /mnt/sdcard to /sdcard

ln -s /mnt/sdcard /sdcard

... Something to try. I think it won't survive reboot, but if it works you can possibly make a script for it to happen on boot.