Related
I am thinking of making the transition from a Galaxy Nexus to an HTC One. I am going to want to put on a custom rom and from my brief research it looks like the phone needs to be on its original software version to unlock and root. Is there a chance that the phone will come with updated software if I purchase it new directly from Verizon?
Thanks!
Wishka233 said:
I am thinking of making the transition from a Galaxy Nexus to an HTC One. I am going to want to put on a custom rom and from my brief research it looks like the phone needs to be on its original software version to unlock and root. Is there a chance that the phone will come with updated software if I purchase it new directly from Verizon?
Thanks!
Click to expand...
Click to collapse
There is the 1.10.605.08 version that it shipped with initially.
There are also 3 newer updates that have since been pushed, not just one.
All but the very latest 2.10.605.1 are exploitable still.
There is no guarantee what version you would get when ordering, unless you confirm it either in-store or via the rep.
There is still a chance that an update could get pushed to it before it reaches you, unless you buy it in store and know for sure what it has pre-loaded.
So, there is a chance it could come with the 4.3 update already, but many devices are still shipping with previous versions and prompting upon initial boot, to download or defer the update.
santod040 said:
There is the 1.10.605.08 version that it shipped with initially.
There are also 3 newer updates that have since been pushed, not just one.
All but the very latest 2.10.605.1 are exploitable still.
There is no guarantee what version you would get when ordering, unless you confirm it either in-store or via the rep.
There is still a chance that an update could get pushed to it before it reaches you, unless you buy it in store and know for sure what it has pre-loaded.
So, there is a chance it could come with the 4.3 update already, but many devices are still shipping with previous versions and prompting upon initial boot, to download or defer the update.
Click to expand...
Click to collapse
IOW, phones are stocked in various Verizon storehouses or retail stores with whatever version was installed when they left the factory. Since they aren't turned on, they haven't received any updates.
Hi guys, I can't update my stock AT&T m8. The ota software update isn't showing up at all. I unlocked the phone with a code I bought online Since Iam no longer using an AT&T sim. I switched to lycamobile. is that the reason I can't see the update? Is there anywhere I can download the ota file? I don't want to root my phone.
gabriox said:
I switched to lycamobile. is that the reason I can't see the update?
Click to expand...
Click to collapse
Yes and no.
Its correct that you will not receive updates for the AT&T version M8 if you aren't on AT&T's network. Some folks here may disagree, that aren't familiar with AT&T (most HTC phones will usually update fine OTA regardless of network). But AT&T is the oddball, you have to be connected to their network, or no OTA.
The other thing is, that the AT&T version hasn't updated to Lollipop yet, and no release date given (but hopefully soon). So even if you were connected to AT&T's network, you wouldn't be able to update to LP.
The latest official software for the AT&T version is Android 4.4.4. If you aren't on that version, you can download the RUU and update with it. Then wait for LP to release as RUU. RUUs are linked in my AT&T specific Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Your other option is to mod the phone and s-off in order to install LP firmware and run a stock or custom LP ROM. Or fully convert the phone to another carrier version (change CID).
redpoint73 said:
Yes and no.
Its correct that you will not receive updates for the AT&T version M8 if you aren't on AT&T's network. Some folks here may disagree, that aren't familiar with AT&T (most HTC phones will usually update fine OTA regardless of network). But AT&T is the oddball, you have to be connected to their network, or no OTA.
The other thing is, that the AT&T version hasn't updated to Lollipop yet, and no release date given (but hopefully soon). So even if you were connected to AT&T's network, you wouldn't be able to update to LP.
The latest official software for the AT&T version is Android 4.4.4. If you aren't on that version, you can download the RUU and update with it. Then wait for LP to release as RUU. RUUs are linked in my AT&T specific Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Your other option is to mod the phone and s-off in order to install LP firmware and run a stock or custom LP ROM. Or fully convert the phone to another carrier version (change CID).
Click to expand...
Click to collapse
i got the the latest at&t update. so should i wait for at&t to release the update or? i dont want a custom rom. just want a stock phone.
gabriox said:
i got the the latest at&t update. so should i wait for at&t to release the update or? i dont want a custom rom. just want a stock phone.
Click to expand...
Click to collapse
Its up to you to make that decision. LP release on AT&T is rumored by a decently reliable source to be "soon", but who knows what that means?
My personal opinion, there is absolutely no good reason to be on AT&T stock software if you aren't even on their network or in the US. Personally, I can't stand AT&T's bloatware and gimped features (you may notice that WiFi tethering is disabled). So converting to another (stock) version to me is highly preferable (or running a custom ROM for that matter).
Not sure what region or country you are in, but you may consider converting to Euro or "international" version (which would still be "stock" just stock international unbranded instead of AT&T). Not only will you get rid of AT&T software branding, but once you fully convert, you will also be able to get OTA updates. Plus, international M8 gets updated much earlier than AT&T.
To "convert", you need to s-off and change CID and MID. From there, you can convert your phone to any other version: http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
Honestly I agree with you. Is there way I can convert to the international version or preferably Google edition without all my files being deleted? btw Iam in the United states. And can you guide me on the process? Thanks
gabriox said:
Is there way I can convert to the international version or preferably Google edition without all my files being deleted?
Click to expand...
Click to collapse
Not that I am aware. Your best bet is to backup your data, then restore it (as appropriate) after you convert. Which you should absolutely do anyway, before undertaking any such major mods. Even if they were supposed to "keep" user data, as nothing is ever a "sure thing" and its always best to back up and avoid regret.
There are different methods to backup, and it also depends on exactly what data you want to keep. I personally have my contacts on Gmail, and don't use any other email on my phone aside from Gmail (so my contacts and Gmail are all just on the cloud). So for me, its mostly just app data that I want to backup, so I use Titanium Backup for that purpose. You can also use Titanium to backup and restore your SMS and call log; at least between Sense ROMs (don't know if this will migrate to GPE). Don't use Titanium to migrate any system data (will often cause bugs if you are moving between any ROMs that are significantly different). I just customize system settings manually after ROM flash, etc. Don't know what other files you may want to keep. If its just media (songs, pics, video) you can just copy those to your computer or removable SD as means of backup. Or there are a variety of cloud options you can use to backup pics and other files.
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Capture the URL for it ?
Here is the link: https://ota.googlezip.net/packages/ota-api/google_marlin_marlin/d872269d3aff80d3b7f81d28c972d1d59f36f8f6.zip
(I'm not allowed to link to it directly due to my account age - sorry!)
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
This happened to me. I have a Verizon version dePixel8 and sideloaded E build a few days ago. Today I got the update message and it upgraded to K in about 2 minutes.
Gather this is for the Verizon models?
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
It's an update specifically for the Verizon Pixels. It contains a number of bug fixes and improvements according to the release info. A simple Google search will locate more info including the specifics of the bug fixes and improvements.
So this OTA will update my Google store device to the Verizon build? Weird. I'll just flash the whole build later.
So, after applying this update - what build does it show?
Just flashed the OTA. It does indeed update Google Store devices to the Verizon build of 7.1.2, NHG47K. Looking in the OTA zip, the update may only affect the system and vendor partitions.
I had this happen after I flashed the January build I think it was. I have a play store pixel on vzw and it was trying to update my regular stock rom the vzw-specific version. It sounds like if you're on vzw service then you'd benefit from their improvements. I'm waiting for beans to update his rom before I update from 7.1.1. I just hope it includes these vzw changes.
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
alsip1023 said:
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
Click to expand...
Click to collapse
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
hub1 said:
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
Click to expand...
Click to collapse
I was referring to the difference between the 7.1.2 builds, not the phones.
alsip1023 said:
I was referring to the difference between the 7.1.2 builds, not the phones.
Click to expand...
Click to collapse
So was I.
TonikJDK said:
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
Click to expand...
Click to collapse
Thanks for playing the guinea pig. Good to know nothing obvious was added in terms of bloat.
With that being said, that Pixel update is handed to Verizon to "test and certify". Then it is sent to the Pixels. Verizon only promised to not delay updates. They may still add apps, bloat, etc... Should they so choose.
Added information:
Google Store Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the right (as in enabled) but is overall greyed out after "K" update.
Verizon Purchased Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the left (as in disabled) but is overall greyed out after "K" update.
Not sure what this means. If anything, I found it interesting. Once it's unlocked, unless I submit a relock, it can't be relocked by OTA right?
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
gordonlw said:
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
Click to expand...
Click to collapse
Hello,
You bought a Google version, you are fine. You can sideload Verizon's OTA if you are on Verizon's network. Otherwise, no benefits...
Even true Verizon's unlocked Pixel owners, as long as they don't lock bootloader, it will stay unlocked, no matter what they flash FYI.
You can install SU with fastboot boot twrp as well.
Cheers...
Worked great thanks!
Hi guys. I got a G8 from a friend whose friend's dad is a radio tower engineer for AT&T that got this phone early. It's a prerelease phone (says "not for sale") on the back, and it comes with software that is seemingly far behind what shipped with the public version of the device. It's Android 9 with the December 2018 security patch, SW version G820UM04b. This version is pretty buggy and doesn't have some features like air motion. It seems like the initial software release for the public phone was G820UM10g.
Whenever I try updating the device, it just says the software is already up to date. I've done more factory resets and tried more tricks than I can even recount. Got a fresh new SIM card. Called AT&T and got them to manually push the update to my IMEI (which is correctly registered), waited a day for the update. Tried LG Bridge but it's incompatible with AT&T devices. Looked for kdz files online for the AT&T version that I can flash using LGUP, but there's no AT&T files available (pls tell me if anyone knows of any out there).
I'm at my wit's end guys. Anyone have any ideas as to how I can get this phone updated? I'm realizing that I really took the ability to just unlock and flash my old OnePlus for granted
Where do you live ?
Mobile AT&T only support to update OTA if you live in US !
minhthien0711 said:
Where do you live ?
Mobile AT&T only support to update OTA if you live in US !
Click to expand...
Click to collapse
Sorry, forgot to clarify that. I live in the USA and I use AT&T.
On the face of it it's not looking good. There aren't any KDZs for ATT as standard, and you can't update OTA - one thing to check here is the S/N field, pre-production LG phones are usually missing this, which is usually why OTAs don't work.
However, pre-production devices can, sometimes, be cross-flashed. You could try using LGUP to flash a more recent US unlocked build. It is likely to give you the IMPL lock / mismatch / crossflashing not allowed error, but it's worth a shot.
If that doesn't work, your best bet will be to ask your friend's dad to take it in to work (when he can...) for whoever looks after devices for his team to flash it to production as a favour.
I purchased myself a used (good/mint condition) LE2125 phone from Swappa as an Xmas gift and have been using it for about the past week or so. Really liking the phone so far.
But it is still on Oxygen OS 11.2.10.10. And each time I check for updates, it still tells me I'm up to date. I am in the US using the phone with Spectrum mobile, although phone sees the Sim as Verizon.
To my knowledge, phone has never been rooted.
Shouldn't I have received the update by now? Although I am still a little afraid to take it based on the initial update fiasco.
Should I just download the Oxygen Update app and go that route?
ptmuldoon said:
I purchased myself a used (good/mint condition) LE2125 phone from Swappa as an Xmas gift and have been using it for about the past week or so. Really liking the phone so far.
But it is still on Oxygen OS 11.2.10.10. And each time I check for updates, it still tells me I'm up to date. I am in the US using the phone with Spectrum mobile, although phone sees the Sim as Verizon.
To my knowledge, phone has never been rooted.
Shouldn't I have received the update by now? Although I am still a little afraid to take it based on the initial update fiasco.
Should I just download the Oxygen Update app and go that route?
Click to expand...
Click to collapse
I also haven't received on the same device and version. So, it's seems like a slow rollout
If you manually check for updates in settings does it tell you you're up to date? If so, I'd just get the update from Oxygen Updater and do a local install. Some people did have issues with the first release of OOS12 (C36) but those should have all been resolved in the next one (C39). I never had any issues with the update personally.
Thanks,
The Oxygen updater wants to go to C.36 first. And then after that, I think straight to C.40. I will likely wait till later tonight to update as do not want to mess up phone while here at work today.
ptmuldoon said:
Thanks,
The Oxygen updater wants to go to C.36 first. And then after that, I think straight to C.40. I will likely wait till later tonight to update as do not want to mess up phone while here at work today.
Click to expand...
Click to collapse
Probably because C36 is the full update. If it won't let you download both C36 and C40 at the same time (before updating), I'd make sure you have access to wifi in case you're one of the lucky few affected by the mobile network issue in C36. But most likely you'll be fine, the other issues were very minor and you wouldn't even notice if you just install the second update right away.
Does Chrome auto fill work for you on 12? I heard that it was broken, but don't know whether it's been fixed with C40? Holding off on updating until someone can confirm. Thx
EDIT: Decided to bite the bullet and upgraded to C40 on my L2125. I actually like it quite a bit, but can confirm that for me, at least, Chrome auto-fill doesn't work. Other nit is you cannot put the battery percentage in the status bar AND remove the icon; either you have both, none, or just the icon. Also, Netflix is pre-loaded, but won't open or uninstall and update and when I go to the Play Store it shows as incompatible with my device?? (bootloader unlocked, but not re-rerooted yet). Also the power menu no longer gives you a recovery or bootloader option in rebooting. Good things include having more gestures (raise phone to answer) and a panel to control apps that auto-start or not. Also, somehow m yreboot sequence no longer includes the danger, your bootloader has been unlocked, screen (which I didn't think was possible to get rid of).
Rolling back to Android 11 for now. Also, many more root options still available there (like Gravity Box and JamesDSP)