Related
Every time I try to flash the OTA update, it first asks me if I want to install the untrusted zip, which doesn't make much sense, because why would an OTA be untrusted?
Then, during the installation, it aborts for some reason. After that it asks if I want to fix root.
I have no idea why any of this is happening, but I can't install the update because of it. What should I do?
Sent from my Nexus 5 using Tapatalk
There should be a reason in recovery why it failed. We'd need to know it before we can help
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
For me at least (I didn't start this thread), it fails because Roboto-Bold.ttf contains unexpected content.
I don't recall ever changing Roboto-Bold.ttf, so I have no idea what about it is unexpected.
CarpeNivem said:
For me at least (I didn't start this thread), it fails because Roboto-Bold.ttf contains unexpected content.
I don't recall ever changing Roboto-Bold.ttf, so I have no idea what about it is unexpected.
Click to expand...
Click to collapse
It's a non standard font installed by something. If you have anything non standard on your phone the ota will fail
Thank you. I understood that.
What I meant to say is, how do I correct it? Where can I find a copy of Roboto-Bold.ttf that the update will be "expecting"?
And then, if/when it complains about another file being unexpected, where did I find THAT? etc, etc.
CarpeNivem said:
Thank you. I understood that.
What I meant to say is, how do I correct it? Where can I find a copy of Roboto-Bold.ttf that the update will be "expecting"?
And then, if/when it complains about another file being unexpected, where did I find THAT? etc, etc.
Click to expand...
Click to collapse
You need to read this http://forum.xda-developers.com/showthread.php?p=47369234. Basically you need to flash the stock system.img
Those instructions include "attach phone to computer while phone is in fastboot mode".
However, when I do that, when I attach my phone to the computer while in fastboot mode, my Nexus 5 is NOT SHOWN when I type "adb devices" OR "fastboot devices".
When my phone is in recovery mode, and I type "adb devices", then it IS shown. Additionally, if my phone is fully booted up as normal, if I type "adb devices", it IS shown then too.
But if there are things which need to be done from the computer at the command prompt (and it seems that there are) while the phone is in fastboot mode, well, I cannot do those things, as my device doesn't seem to recognized at all while in that mode.
CarpeNivem said:
Those instructions include "attach phone to computer while phone is in fastboot mode".
However, when I do that, when I attach my phone to the computer while in fastboot mode, my Nexus 5 is NOT SHOWN when I type "adb devices" OR "fastboot devices".
When my phone is in recovery mode, and I type "adb devices", then it IS shown. Additionally, if my phone is fully booted up as normal, if I type "adb devices", it IS shown then too.
But if there are things which need to be done from the computer at the command prompt (and it seems that there are) while the phone is in fastboot mode, well, I cannot do those things, as my device doesn't seem to recognized at all while in that mode.
Click to expand...
Click to collapse
Google tool adb fastboot drivers xda. Use that to get the drivers working with fastboot
jd1639 said:
You need to read this http://forum.xda-developers.com/showthread.php?p=47369234. Basically you need to flash the stock system.img
Click to expand...
Click to collapse
Will that do anything to root access?
Sent from my Nexus 5 using Tapatalk
kehlan said:
Will that do anything to root access?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
After taking the ota you'll have to re-root
I think it's finally happening. I think I'm finally done. I'm successfully running 4.4.2 on my rooted Nexus 5. Thank you so much for the help (especially since this isn't even my thread; it just had a title which aligned perfectly to my problem, so hopefully the OP was helped along the way also).
To recap, for future use other visitors to this thread...
1. I tried to apply the 4.4.2 update using an OTA.zip file I found elsewhere on the Internet. This is easy. You've probably already done this.
2. I was told "build.prop" contained unexpected content.
3. I remembered that I had changed the DPI, so I changed that back from my personal 420 to the default 480. This resolved the previous error message.
4. I tried again, but this time was told Roboto-Bold.ttf contained unexpected content. I have no idea why that was.
5. I followed SOME of the instructions on this page: http://forum.xda-developers.com/showthread.php?t=2513701
Specifically, from the "Method 2" section, I did the "fastboot flash system C:/image-hammerhead-krt16m/system.img" and "fastboot flash boot C:/image-hammerhead-krt16m/boot.img" commands. That's ALL I DID from the "type these commands" section of those instructions. Doing that, I did NOT lose data! (well, none that I've yet noticed, at least)
6. I tried AGAIN to flash the OTA.zip file from Clockworkmod Recovery. This time it finally worked!
7. I checked Settings > About Phone, and I'm running 4.4.2 now!
8. I'm having trouble changing the DPI back to 420. I'm probably not rooted anymore. I'll have to go do that again. No big deal. Everything else seems fine.
...along the way, I needed to install drivers, for which I tried so many things, I don't even remember anymore what was the best method. I think using "ADB Manager.exe" from within my ADB folder was best. I also, at one point, had to change my USB device type from MTP to PTP. That was done on the phone, by swiping down the notification area.
Ugh, I wish I remembered everything, so I could spell it out as directly and clearly as I would've appreciated it be this morning, but I've seriously done so much recently that I know I'm missing certain steps, and I feel really bad for anyone having problems. There are so many instructions on the Internet that say, "Do this, and then this will happen," but they never explain what to do if that DOESN'T happen. And now here I am, not being any better than any of them. Sorry. Good luck.
Glad you got it working
Hey guys,
I've been using XDA's awesome resources and the boatload of work that everyone here has done as a community for years to fiddle with every Android I've had. But finally it seems that the time has come that searching for similar problems to mine don't return any results. I've had a look around as much as I can and tried a bunch of solutions to no avail.
In the past I've flashed my phone while in fastboot mode with the relevant roms and gone on my merry way. Now when I try to do so I get either "neither -p product specified nor ANDROID_PRODUCT_OUT set" if I try and run "fastboot flashall", or I get an error for each part of the image if I try and flash them inidividually. For example "fastboot flash radio.img" returns "error: cannot load 'radio.img'". Lastly, if I just run the "flash-all.bat" file as administrator in the ROM's folder (where there is indeed also the fastboot.exe), I get the classic "'fastboot' is not recognized as an internal or external command, operable or batch file."
Up until today I was still running the Android L developer preview that came out last year. I never got around to updating to the stock release once it was out so I thought I'd wipe everything today and do so. After making sure I had the Universal Naked Driver installed correctly and making sure that fastboot recognized my device, I used TWRP to wipe everything. I booted to bootloader and opened a command prompt window into the folder where I had saved the Minimal ADB and Fastboot files, the extracted stock image, its subfolders, and also its extracted pieces (radio.img; system.img and so on).
I hate to be a bother, but my phone's unusable at the moment. Can anyone help me out or point me in the right direction?
Do you have the latest fastboot and adb versions? Android I requires the latest.
Sent from my Nexus 5 using XDA Free mobile app
If you try to flash while you have a lot of processes running, you may not have enough free RAM to flash.
jd1639 said:
Do you have the latest fastboot and adb versions? Android I requires the latest.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I used this guy. From June 2013, so proobably not the latest. Let me find a newer one and try again.
BirchBarlow said:
If you try to flash while you have a lot of processes running, you may not have enough free RAM to flash.
Click to expand...
Click to collapse
I don't think that was the case. I restarted a couple times and didn't open much.
B1azingPengu1n said:
I used this guy. From June 2013, so proobably not the latest. Let me find a newer one and try again.
I don't think that was the case. I restarted a couple times and didn't open much.
Click to expand...
Click to collapse
Google 15 second adb install xda. That'll install the latest.
Sent from my Nexus 5 using XDA Free mobile app
Hi guys,
i have a pixel and i want to enrrol to the beta program, i just done the process but it seams that update is not arriving, its posible that verizon pixels can't enroll to beta program?
http://www.droid-life.com/2017/01/30/android-7-1-2-beta-download-update-nexus-pixel/
Regards
You can download the full image here
I dont have oem unlocked. I can sideloade it?
Yea even i didn't get it. I guess it not for the verizon phones.
Can anyone who has upgraded to 7.1.2 let us know if it appears stable enough for a daily driver and have they noticed any differences ? Thank you.....
Another locked bootloader VZW customer here who enrolled and is waiting for OTA. I think we'll get it, just have to wait for OTA's to start. Google let us enroll, and we seem to have gotten updates from Google and not VZW so far. I think it'll just take a day or 2 to start rolling.
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
I am a non VZW pixel user (Koodo - Canada) and have not received the OTA after signing up yesterday. They note that it may take 24 hours and looks like it's going to for me.
k.s.deviate said:
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
Click to expand...
Click to collapse
I know that the bootloader is what loads the Android filesystem to the boot image, I wonder if it can somehow be manipulated to unlock and root since you mention that the boot image is different? Does anyone know? Thanks
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
farfromovin said:
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
Click to expand...
Click to collapse
Signed up yesterday for both my Pixel (VZW sim) and Pixel XL (Project Fi sim) both bought direct from Google. Pixel XL rec'd update almost immediately not yet on Pixel so far.
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Sent from my Pixel using Tapatalk
joshw0000 said:
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Click to expand...
Click to collapse
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Nope it's exactly that. Just remove -w so it doesn't wipe the device. It's how I update my Pixel and 5X since I'm impatient waiting for OTAs.
murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Sent from my Pixel using Tapatalk
joshw0000 said:
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Click to expand...
Click to collapse
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
OTA hasn't rolled for the pixel yet, likely "soon", my guess is today or tomorrow at the latest since XL has gone out. I am on project FI and got the pixel through the play store fyi
murryrulz said:
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
Click to expand...
Click to collapse
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
I am also in the waiting for the OTA camp and use an unlocked Verizon Pixel and PIxel XL. I have had better luck using the TWRP sideload method and it installing to the other slot with each subsequent sideload appears to me a more consistent way to keep everything updated in the same way that the system OTA works.
joshw0000 said:
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Get rid of windows, use Linux, no messing around with anything, it just works ?
-------- runs -----_ducks_---- runs ----
Sent from my Pixel using XDA-Developers Legacy app
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
electrogiz said:
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
Click to expand...
Click to collapse
Just got the OTA notification!
electrogiz said:
Just got the OTA notification!
Click to expand...
Click to collapse
I'll wait until I can manually flash.
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Updating now!!!
dhorgas said:
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Click to expand...
Click to collapse
Already disappointed on the modem firmware front. No upgrade there. Also, no ability to force full-screen. Going to pass judgement on stand-by bug after 48 hour or so, unless obviously an issue.
The fact that it was not released to beta first makes me think it may just be an official release of the beta
crixley said:
The fact that it was not released to beta first makes me think it may just be an official release of the beta
Click to expand...
Click to collapse
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
dhorgas said:
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
Click to expand...
Click to collapse
Hopefully. SoT and Deep-sleeps issues were horrendous!
epicbeardman911 said:
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
Click to expand...
Click to collapse
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
tanker666 said:
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
Click to expand...
Click to collapse
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
E: Package is for source build essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but expected essential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys
Installation aborted.
Click to expand...
Click to collapse
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
GospelNerd said:
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
Click to expand...
Click to collapse
I was in the same boat as you. I was on 8.1B1 rooted so I fastboot flashed the boot.img, then rebooted , downloaded the OTA which wouldn't install.
Went back to boot-loader, flashed the boot.img to both slots, rebooted, took OTA, and it still won't work. I get "couldn't update installation problem"
I didn't have an issue getting the last OTA, the same way.
I dunno
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
NaterTots said:
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
Click to expand...
Click to collapse
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Wonder if Essential pushed it since Pixel is now offering pre release of Android P?
My radio has noticeably improved, instead of VZW its finally showing Verizon wireless. And the new developer options are nice
GospelNerd said:
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Click to expand...
Click to collapse
My install wasn't working either at first (same boat as you guys, Magisk rooted with custom kernel). At first I just did a Magisk uninstall and reboot but it wouldn't install. Thought maybe I still had a custom recovery installed, but there was no TWRP in recovery. So, I just did a sideload install of the 8.1 beta using adb and then rebooted. That put me back on stock 8.1b1 and retained all my settings/data. Then I made sure my settings were correct in developer options (USB debugging, etc.), and it's finally installing. Not sure, maybe I just didn't hold my mouth right the first couple times, but it's working now.
Can anyone tell me if stable has multitouch issues that were on beta?
Rooted 7.1.1 took the update just fine, lost root and twrp
Looking at META_INF\com\android\metadata, it's expecting essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but, based on the text at the top of the screen when sideloading, the device is at ssential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys. Changing it is pointless, since META_INF\MANIFEST.MF contains a SHA-256 hash of of the metadata file. I'm going to try recomputing the hash and updating the OTA zip.
Edit: Didn't work. But has someone on reddit confirm Jank4AUs situation.
Who's ready for some official pie?
ME!!!
Downloading now! :good:
(System update notification received about 20 mins ago)
Update still hasn't shown up for me. Keep hitting that check button...
That was fast. Downloading it now.
Yeah, well, here we go. Remove PIN...undo overlays in Sub...download and pray!!!
techlogik said:
Yeah, well, here we go. Remove PIN...undo overlays in Sub...download and pray!!!
Click to expand...
Click to collapse
Or just navigate to root/data/ ota package/update.zip, then copy to internal.. then undo security, then flash adb sideload..
Edit. Dont do this, the package isnt signed and fails
I have the update but it keeps failing to install.
jacksummers said:
Or just navigate to root/data/ ota package/update.zip, then copy to internal.. then undo security, then flash adb sideload
Click to expand...
Click to collapse
Good idea, because it keeps failing on the install...will give this method a go...thanks. Plus they don't have the download zip on Essential support...so kind of have to try this if I want Pie..haha
Thanks
jgates86 said:
I have the update but it keeps failing to install.
Click to expand...
Click to collapse
It wont go twrp, have to use fastboot or adb sideload
My wife's phone got it before mine, still waiting :/
jacksummers said:
It wont go twrp, have to use fastboot or adb sideload
Click to expand...
Click to collapse
I'm straight stock DP5, no unlocked bootloader or anything so not sure why it won't update.
jgates86 said:
I'm straight stock DP5, no unlocked bootloader or anything so not sure why it won't update.
Click to expand...
Click to collapse
Oh then just take it ota
Fails the sideload as well.
Installing Update....
Step 1/2
Error applying update 20 (ErrorCode kDownload StateInitializetionError)
Error in /sideload/package.zip
Installation aborted
On my command prompt:
adb sideload update.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
Going to try a flashall.bat with the stock image file again, reboot and try to OTA it..see what happens.
jacksummers said:
Oh then just take it ota
Click to expand...
Click to collapse
That's where it;s failing, just downloads, starts step 1 of 2 and just says installation problem with no other info.
Just got it installing myself, been running the Beta Preview for months...we'll see what the Pie is like...hopefully it's not a Cleveland Steamer Pie...
OH well, the full file just showed up for download on the Dev Essential support site...will just update that way!!
Just installed and it looks good.
I think I would need some time to get familiar with the new navigation bar though.
OTA download is a little slow so you'll need to grab a beer and be patient.
There are a couple of changes that make it more iOS-like -- the smart text selection with the window and also the carousel that displays the recent apps when you swipe up. I wish the navigation bar were fully transparent, but I guess you can always revert back to a mod for that. I'm most interested to see if there is indeed an improvement in battery performance and whether signal improves with my T-Mobile service. Enjoy!
Update: the gestures implemented by Google seem a little half-baked in comparison to OnePlus'. The latter's is a more preferable interpretation to me.
Does the open market OTA work on Sprint version, or are we stuck waiting?