|
09.12.2013., 12:21 | #61 |
Protupožarac
Datum registracije: Aug 2007
Lokacija: Tamo gdje sunce vječno sja
Postovi: 22,222
|
Odlično. To onda znači da mi koji nismo nexusari, a dobit ćemo KK, da će to već tada biti prilično ispeglane verzije. Da, istina je da će nexus tad već bit na 4.5 ili 5.0 |
10.12.2013., 00:41 | #64 |
49%winner
Datum registracije: Sep 2007
Lokacija: PU
Postovi: 8,797
|
Načekat ćeš se bome Sideloadao sam maloprije 4.4.1 i odmah mi je bio ponuđen 4.4.2 (koji je izgleda pušten velikoj većini, ako ne i svim 4.4.1 korisnicima jer je to mali fix). Btw, out of the box mi nije nudio update ni na 4.4.1 niti na 4.4.2.
__________________
♕ Keep calm and fastboot oem unlock. ♕
|
10.12.2013., 07:57 | #65 |
Premium
Datum registracije: Mar 2006
Lokacija: Sv.Nedelja
Postovi: 5,642
|
Bit ce.... Why hasn't the OTA hit my device yet? I keep mashing the "check now" button! Morrill also explains the "rollout" process of Nexus OTA's. * Quote: Rollouts are conducted in phases. Typically they start at 1% of devices for around 24 - 48 hours; we watch the return rates and resulting device checkins and error reports (if any), and make sure nothing looks wrong before sending it to more. Then typically it goes to 25%, 50%, 100% over the course of a week or two. What the percentages mean is that when your device checks in, it has a 1% chance (for example) of being offered the OTA. If it doesn't (randomly) get an offer, it will never get an offer until the next batch. IOW, once your device checks in and gets turned down, that's it until the next batch. Mashing on the "check for updates" button just causes your device to check in again, and get automatically turned down again. Think about how that makes your device feel! WON'T SOMEONE PLEASE THINK OF THE PHONES?! That said, once the new batch does start, hitting that button does give you a new roll of the dice -- but once. Since devices usually only check in for system updates every 24 hours (I think? Certainly on a many-hours basis) this can get you your shot sooner than it would happen on its own. So, mash away. Just be patient, and mashing on it more often than once or twice a day isn't going to gain you anything. Edit: also, keep in mind that this isn't first-come/first-served. You're not racing other devices to get your slot in the current batch, or something. -Dan Morrill |
10.12.2013., 09:30 | #66 |
Premium
Datum registracije: Mar 2007
Lokacija: Split
Postovi: 407
|
Upravo stavija factory image KRT16S, i odma nakon instalacije napravija OTA update na 4.4.2. (Nexus 4). |
10.12.2013., 12:44 | #69 |
49%winner
Datum registracije: Sep 2007
Lokacija: PU
Postovi: 8,797
|
Q: Why do I get a "cannot read update.zip" error when trying to sideload? A: If you named the file update.zip, the actual name would be update.zip.zip. Windows auto names extensions by default. That could be your problem. If not try another usb cable or a different usb port. If that still doesn't work, make sure you type exactly what you renamed the file. You may have made a typo. It is also case-sensitive. http://forum.xda-developers.com/show....php?t=2523217
__________________
♕ Keep calm and fastboot oem unlock. ♕
|
10.12.2013., 16:34 | #71 |
49%winner
Datum registracije: Sep 2007
Lokacija: PU
Postovi: 8,797
|
Meni je prvi put izbacilo neki error jer imam stari adb. Kada upisem "adb devices" izlista uredjaj i pokaze ga kao offline, pa sideload nije prolazio. Na tom linku sam nasao novi adb i onda je prepoznao mob.
__________________
♕ Keep calm and fastboot oem unlock. ♕
|