Related
So I'm running completely stock, never rooted Android 5.0 on my Nexus 5. I got the 5.0.1 update today and when I go to install, it gives me the dead android pic with "error". Anybody else having the same issue? Also, would me enabling developer options have anything to do with it?
P.S. Already cleared my cache partition and it's still giving me the error.
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
or just give it out so we noobs can easily be guided?
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
Except, like I said, I didn't. I did not root or unlock the bootloader or play around with the phone at all, strictly for this reason. I didn't want to go through the struggle of factory resetting my device every now and then. The closest thing to "modifying" the phone was me unlocking developer settings and I was asking if that could have something to do with it.
Every other thread on the forums has to do with people rooting so no, it's not like one of the millions of other threads.
Describe more.
The best way to update is by flashing the factory image in fastboot, i don`t trust/hate OTA`s personaly
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
kubus908 said:
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
Click to expand...
Click to collapse
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
kubus908 said:
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
Click to expand...
Click to collapse
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
May as well skip the ota if you're going to go through this process.
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
digitLIX said:
or just give it out so we noobs can easily be guided?
Click to expand...
Click to collapse
Or wait for the next time the question is asked.
Should be any minute now.
Thanks! I may just wait until the next update and see if there's a chance it'll work. Or I may just have to do a fresh new install which I am not looking forward to at all Lol. But thank you for your help!
Uhhhh, ok. So I'm not exactly sure what happened. I figured I'd give the OTA another try because why not...and it worked I noticed it downloaded a bigger file too, 30ish mb as opposed to the 13mb OTA that would give me an error. Not sure if I got sent a wrong update file or what, but if your issue comes close to what I experienced, just keep trying the OTA update. I'm also on T-Mobile (phone bought directly from T-Mobile) in case that makes any difference.
I Have H950 G Flex2, But i didnt get android 5.1.1 , i love this phone even it get hot somethimes, its good for me.
I want to know if maybe someone can help me to update to 5.1.1 because i dont have ota Update avalible and if is possible, try a stock or international room of 5.1.1 for the H950 Because att have a lot of bloatware.
Thanks all!
Yes
The various threads around here are quite helpful. If you're rooted, you're going to have to go back to stock. The OTA update should then kick in.
There's a thread over in the Android Development Section (It's at the top) that is exactly what you're looking for.
So, yes there are certainly methods by which you can update to 5.1.1!
Cmcarboni said:
The various threads around here are quite helpful. If you're rooted, you're going to have to go back to stock. The OTA update should then kick in.
There's a thread over in the Android Development Section (It's at the top) that is exactly what you're looking for.
So, yes there are certainly methods by which you can update to 5.1.1!
Click to expand...
Click to collapse
Can you help me with the link please? im searching since i buy it. Thank you
Of course I can help
kiscvik said:
Can you help me with the link please? im searching since i buy it. Thank you
Click to expand...
Click to collapse
This is a detailed tutorial on how to return your phone to stock. You'll end up with a data wipe, so make sure to back up anything you want to keep. You'll want to do this first. Nothing should go wrong (no guarantees though, as always), just make sure you pick up the H950 version of the system file (and put this in the root directory of your internal storage, and rename it to "system.img" if isn't already.)
Easy Restore/Recovery/Unbrick Tool for LG G Flex 2
You'll reboot to your bloated stock system, and you should be able to get the OTA update. If you come across the "Please wait 24 hours and try again" message, just go manually set your date and time ahead, that should get it working.
Then you'll want to use this link to update to flash a 5.1.1 (rooted) system file (similar to the way you did it before).
http://forum.xda-developers.com/g-flex2/development/root-easy-root-att-flex-2-5-1-1-t3178354
After a great deal of tediousness, you can install Titanium Backup and remove all of the bloatware. Obviously, be cautious, you might break things (and then you'll need to factory reset, yet again). In the near future I'll post a thread of all the bloatware I removed without any issue.
EDIT: I've created a freezable bloatware list for those of you unsure what's safe and what's not. The thread is here:
Ti Backup Bloatware Freeze List
Once you're done with that, if you're brave enough, you can install the XPosed framework (even though the bootloader is locked) using this link:
XPosed G Flex 2
The process is a bit sketchy, the extended periods of black screen are a bit foreboding, but it worked like a charm.
I am also in the same boat. Not receiving OTA, tried factory reset and date+1 doesn't work
Has anyone outside the US or AT&T network been able to update? Perhaps it works with a VPN? I haven't been able to update my brand new phone with zero modifications.
Im outside US, and i haven't got the OTA, i been trying changing the date and factory reset every now and then...
I will try a VPN and see how it goes.
Yes
When I returned to stock 5.0.1 I got the ATT OTA update. I'm in the US.
I don't claim to know the intricacies of flashing, but there are H950 5.1.1 system images floating around these boards. Could you flash one of those while on stock 5.0.1? I'm not sure. We do have an unbrick tool though so you'd probably be able to recover.
Let me know if anyone skips the part where they let the phone update itself, and go straight to flashing 5.1.1.
I just bought this phone brand new in the box because I heard the update was out on ATT, not for me I guess.
If you're already on 5.1.1 and you try to recover with the 5.0.1 image you will brick your phone.
As far as receiving the update notification on the AT&T version, I had to change the date forward a few days. I would check for updates after each date change and eventually got the notification. If that doesn't work, do a factory reset and try again.
Tikerz said:
If you're already on 5.1.1 and you try to recover with the 5.0.1 image you will brick your phone.
As far as receiving the update notification on the AT&T version, I had to change the date forward a few days. I would check for updates after each date change and eventually got the notification. If that doesn't work, do a factory reset and try again.
Click to expand...
Click to collapse
Sounds like a direct flash upgrade is a no go then. I also set my device forward a few days (like a week) to get the update.
I Just ordered this phone and will be using it on cricket wireless, does anyone know if I'll need an active at&t sim card to get the 5.1.1 update or will I be able to get the update with my cricket wireless sim card?
Nope
Using a Straight Talk SIM myself and I got the OTA update just fine.
Tikerz said:
If you're already on 5.1.1 and you try to recover with the 5.0.1 image you will brick your phone.
As far as receiving the update notification on the AT&T version, I had to change the date forward a few days. I would check for updates after each date change and eventually got the notification. If that doesn't work, do a factory reset and try again.
Click to expand...
Click to collapse
THANK YOU! after 7 painful days this solved my issue! you are awesome I never would have thought to take off auto time and date and jump forward. In one day increments it wouldnt grab the OTA. First time i went to september and boom, I got it. !
errcyco86 said:
THANK YOU! after 7 painful days this solved my issue! you are awesome I never would have thought to take off auto time and date and jump forward. In one day increments it wouldnt grab the OTA. First time i went to september and boom, I got it. !
Click to expand...
Click to collapse
Did you already update?
if not wait!! and send me a mp
Sj12345 said:
Did you already update?
if not wait!! and send me a mp
Click to expand...
Click to collapse
Sorry I am new as of today.. I just bought the xda app. I don't know what an mp is. Please tell me what I did wrong tho now I am paranoid
errcyco86 said:
Sorry I am new as of today.. I just bought the xda app. I don't know what an mp is. Please tell me what I did wrong tho now I am paranoid
Click to expand...
Click to collapse
Nothing is wrong, (pm is private message), did you already update your phone?
Sent from my Z812 using Tapatalk
Sj12345 said:
Nothing is wrong, (pm is private message), did you already update your phone?
Sent from my Z812 using Tapatalk
Click to expand...
Click to collapse
Yes, went from 5.0.1 to 5.1.1
I used the method above of changing the date a month forward.. It went from saying up to date to giving me the ota
I hope the update isn't crop because I don't know much of rooting and roming. Hoping to learn stuff here as xda is full of some smart folks.
errcyco86 said:
Yes, went from 5.0.1 to 5.1.1
I used the method above of changing the date a month forward.. It went from saying up to date to giving me the ota
I hope the update isn't crop because I don't know much of rooting and roming. Hoping to learn stuff here as xda is full of some smart folks.
Click to expand...
Click to collapse
No, you're fine. I think he just wanted the OTA file.
Sent from my LG-H950 using Tapatalk
??
errcyco86 said:
THANK YOU! after 7 painful days this solved my issue! you are awesome I never would have thought to take off auto time and date and jump forward. In one day increments it wouldnt grab the OTA. First time i went to september and boom, I got it. !
Click to expand...
Click to collapse
So how? Just change the date and what? i didnt understand, im outside US
Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.
Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available
bush911 said:
Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available
Click to expand...
Click to collapse
I have tried to stay away from flash fire because I know a couple buddies who soft-bricked by using it.
xxbilxx said:
Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.
Click to expand...
Click to collapse
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
TonikJDK said:
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
Click to expand...
Click to collapse
I don't have to sideload the March security patch first?
xxbilxx said:
I don't have to sideload the March security patch first?
Click to expand...
Click to collapse
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).
TonikJDK said:
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).
Click to expand...
Click to collapse
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.
xxbilxx said:
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.
Click to expand...
Click to collapse
Correct, you want N2G47E.
TonikJDK said:
Correct, you want N2G47E.
Click to expand...
Click to collapse
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!
xxbilxx said:
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!
Click to expand...
Click to collapse
No problem at all. Second to the last post in the same thread I linked you to before. It all still works fine on 7.1.2. Did all of this myself yesterday afternoon.
Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways
Download the OTA, Flash it from TWRP, reflash twrp and reboot
mikeprius said:
Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways
Click to expand...
Click to collapse
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
yeah saved it. There was only one section that had the w- and it was right before the update image. I can try it again at some point later on but that's what I did. I tried to sideload adb the OTA first which does not wipe data but kept getting an error saying device not found and emulator.
robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
Your instructions worked perfectly for me. I'm nor sure what setup the other guy had, but I did make sure I removed the -w like 20 times.
Juli112 said:
Download the OTA, Flash it from TWRP, reflash twrp and reboot
Click to expand...
Click to collapse
are you on the latest twrp rc2 or rc1?
Has anyone received the update ota on a stock google pixel XL for verizon. Mine keeps telling me I am current?
Hey all,
I've restored my girlfriends pixel using the original android 8 image. (It was using PureNexus before). However, she just got the update notification (september update?) but it doesn't do anything when she taps it. The phone should not be rooted, as I used the original clean factory image.
Any suggestions? I've looked at this thread https://forum.xda-developers.com/pixel/help/taking-september-security-update-rooted-t3672586 and so am prepared to download the latest update and remove the "-w" part, but shouldn't it allow her to take the update anyway? Am I going to have to always do this every time they release an update?
Thanks!
It should work, so long as you restored everything to stock - system, bootloader, recovery (dunno if radio matters).
If it's not working most likely there's something custom hanging around somewhere...
I believe it will also fail to update if the bootloader is unlocked. Not sure if you have a VZW device but that's how it works for them. I just update by flashing the full factory image, not an OTA file. Removing the -w will retain user data.
FernBch said:
I believe it will also fail to update if the bootloader is unlocked.
Click to expand...
Click to collapse
Nope, not true. I unlocked my bootloader (not a Verizon phone, bought it from Google), but I've have my phone 100% stock most of the time and I've taken many OTA updates. Including the recent Oreo Sept security update a couple of days ago.
jss2 said:
Nope, not true. I unlocked my bootloader (not a Verizon phone, bought it from Google), but I've have my phone 100% stock most of the time and I've taken many OTA updates. Including the recent Oreo Sept security update a couple of days ago.
Click to expand...
Click to collapse
I think that's the point they're trying to make. Its the Verizon version that is having the update problem if the bootloader is unlocked.
I am having the same issue (have a Verizon Pixel) but am on the ProjectFi network and can't update. I think I'll have to reset and lock the bootloader in order to get the update.
joeyfeffer said:
I think that's the point they're trying to make. Its the Verizon version that is having the update problem if the bootloader is unlocked.
I am having the same issue (have a Verizon Pixel) but am on the ProjectFi network and can't update. I think I'll have to reset and lock the bootloader in order to get the update.
Click to expand...
Click to collapse
Wait wait no. Just download the full image, edit the flashall bat file and remove the-w from it with a text editor. That will flash you back to stock and not wipe your data. Then reroot and so on.
Do not relock it, ever. If something goes wrong and you brick you are toast.
TonikJDK said:
Wait wait no. Just download the full image, edit the flashall bat file and remove the-w from it with a text editor. That will flash you back to stock and not wipe your data. Then reroot and so on.
Do not relock it, ever. If something goes wrong and you brick you are toast.
Click to expand...
Click to collapse
Oh gotcha gotcha.
Weird issue though I couldn't get update to the latest image. I was only able to flash the bootloader and radio. When I tried updating the image it said it couldn't find some of the files. Do I still need to keep the line as "fastboot -w update" when updating the image? won't the "-w" do the wipe?
Nevermind I figured it out. I guess I was inputting the wrong command.
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.