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)
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 got my HTC 10 last week - phone is a big improvement from the m8.
I am running Telstra's latest firmware - Have s-off already...
Telstra's latest firmware is 1.53.841.6 with Leedroid ROM - have been trying to get VOLTE.
I never got VOLTE with stock because I rooted so fast and S-OFF and installed custom ROMs.
So I had to install stock system image 1.53.841.6, reinstall stock recovery and factory reset and VOLTE icon shows up instantly. Install TWRP and VOLTE remains. But if you install a custom rom and do a full wipe seem to lose VOLTE. Also have to have the telstra firmware to VOLTE to work, I tried with WWE and no go. Also had to ring up telstra as it wasn't activated. So if you are having trouble getting it - might be best to double check. Even though my provisioned flag was on. *#*#4636#*#* to check - tap phone info.
@xlrate reported not wiping data and installing VIPER was able to keep VOLTE. (Updated the customize folder in the rom with my Telstra back up, also the build prop to do this) Also TELST001 cid has to be on.
Has anyone got VOLTE working on a custom ROM on WWE Firmware?
So Aussies... Who's got their new HTC 10?
Update - 15/10/16
Thanks to @brantp for providing TWRP backups & OTAs
https://drive.google.com/drive/folders/0B6MWrHVBWC-xZlBQN1BqYUNPRW8
TWRP Backup (untouched System Image + Boot)
- 1.21.841.8 (+ Recovery)
- 1.53.841.6
- 1.80.841.1
- 1.95.841.3
Stock Recovery
- 1.53.841.6
- 1.80.841.1
- 1.95.841.3
OTA
1.21.841.8 --> 1.53.841.6
1.53.841.6 --> 1.80.841.1
1.80.841.1 --> 1.95.841.3
Firmwares- Refer to http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520 for more info
https://docs.google.com/spreadsheets/d/1EdAHLDDxqf9jH65me_8bY9oXdaYusI0eedpwO6yUY2s/pubhtml
Thanks to @Sneakyghost
Roms- Leedroid, ICE and Viper now support Telstra with carrier support.
If anyone has any of the other australian carriers firmware please post and I will add them to OP.
15/08/16
https://www.androidfilehost.com/?w=files&flid=60869
Telstra RUU provided by @Sneakyghost - Will restore OTA's if anyone has broken them
12/03/18
Telstra OREO update
http://fotadl-az.htc.com/secure/OTA....48.841.31_release_519847tp9bagwfkglchg5u.zip
@Sneakyghost isn't doing the firmware updates anymore.
If you need to use the firmware.zip out of the OREO zip and need to a custom recovery either replace the recovery.img with twrp.img (rename it of course) in the firmware.zip - or flash one after installation.
I got mine about a month ago.. All I've done so far is root it.. (even after all these years, it still sounds wrong)
I normally run ARHD, but, Mike hasn't mentioned developing for the 10, so, I'm stuck atm, not really interested in running a massively modded ROM. But, last night the OTA notification popped up for 1.53.841.6.. So, I'm going to have to do something - the notification is annoying me. So, I guess I have to work out how to update it.
I hadn't even considered the VoLTE requirements.. I just assumed it would all work, even on a custom ROM. 4G did, I didn't think this would be any different.
Is VoLTE worth hanging on to? I don't really get it.. Is it like VOIP for mobiles?
Vampyric said:
I got mine about a month ago.. All I've done so far is root it.. (even after all these years, it still sounds wrong)
I normally run ARHD, but, Mike hasn't mentioned developing for the 10, so, I'm stuck atm, not really interested in running a massively modded ROM. But, last night the OTA notification popped up for 1.53.841.6.. So, I'm going to have to do something - the notification is annoying me. So, I guess I have to work out how to update it.
I hadn't even considered the VoLTE requirements.. I just assumed it would all work, even on a custom ROM. 4G did, I didn't think this would be any different.
Is VoLTE worth hanging on to? I don't really get it.. Is it like VOIP for mobiles?
Click to expand...
Click to collapse
I have had VoLTE working with Leedroid after I used the telstra 1.53 system/customize & parts of the build.prop on the 1.30 base... Haven't been able to get it working on 1.80 base.
Have had to use the telstra firmware for it work, doesn't work on WWE. So it is kinda a pain to get working.
VoLTE is better call quality and if you are on a call you can use LTE/4g to use the internet... Without VoLTE when on calls your phone 3g
EDIT - don't think OTA will work since you are rooted unless you went systemless root
I guess I don't 'appreciate' VoLTE as much as I should, because I rarely make phone calls..
Sadly, not Systemless root. So, I think I need to go back to stock, update and re-root. It's not something I've had to worry about before. So, it's kinda frustrating, and a little too complicated for me to totally understand.
I was going to de-brand it, and just run the WWE RUU.. But, maybe I'll wait for the 1.80 Telstra update and worry about it then.
I got rid of the notification
**Sent from a uranium powered typewriter**
Anyone experiencing an issue with NFC? While on stock 1.21.841.8 (and locked), worked without issue. Since updating to 1.53.841.6 (and unlocked), can't read my Opal card now ie no vibration, no sound, no anything. Haven't tested my tap & pay banking app yet (which did work without issue prior to updating).
Yes I also had and issue with NFC. Would not read opal card and was an absolute pain to try and read my Amex and Visa card.
Ended up getting another issue with it and returned the phone under warranty for NFC and the other issue.
Still waiting to get a phone back ?
Sent from my HTC One_M8 using Tapatalk
Yeah NFC doesn't work with mine now on 1.53.
I did get a vibrate and a sound when I was on earlier firmware but not now.
Just hoping that the 1.8 update fixes this stuff.......
pablo11 said:
Yeah NFC doesn't work with mine now on 1.53.
I did get a vibrate and a sound when I was on earlier firmware but not now.
Just hoping that the 1.8 update fixes this stuff.......
Click to expand...
Click to collapse
Thats if we get 1.8
I have a feeling we will miss that and get the one after that.
xlrate said:
Thats if we get 1.8
I have a feeling we will miss that and get the one after that.
Click to expand...
Click to collapse
Aparently they have stoped rolling the 1.80 update. Im on vodafone and there website has no update for the htc 10 so i agree that we wont get it
yldlj said:
Aparently they have stoped rolling the 1.80 update. Im on vodafone and there website has no update for the htc 10 so i agree that we wont get it
Click to expand...
Click to collapse
Tried reflashing the 1.53 firmware again (twice) to see if it fixes it, but it's still not working ie Can switch it on and off, but it does not respond to my opal card.
It's only taken Telstra until this month to push out 1.53, so who knows when (or if) 1.80 will happen. Now I'm trying to decide whether it's worth sending back for another handset or waiting to see if the next OTA will fix it. My biggest concern is that the replacement could be on 1.21 and I could possibly end up with the same issue all over again!
pablo11 said:
Yeah NFC doesn't work with mine now on 1.53.
I did get a vibrate and a sound when I was on earlier firmware but not now.
Just hoping that the 1.8 update fixes this stuff.......
Click to expand...
Click to collapse
I just tried to NFC on 1.53 and it isn't working very well, hardly at all. I got it to work 3 times in about 15 mins...
Previously I think when I was on 1.30 firmware it was working well before but just had to hold it near the head phone jack.
Any Telstra users want to test out the Telstra firmwares
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520
Make sure you back-up the rom & back up internal storage refer to later posts in that thread.
https://crowdsupport.telstra.com.au/t5/Device-Updates/Software-Updates-01-07-2016/td-p/585953 Telstra 1.80.841.8 firmware is coming 25-Jul
Leedroid is the best rom for Telstra users. Running it myself and working perfectly, now supports Telstra with carrier support & VoLTE working - thanks @LeeDroid
*Only works on Telstra firmware.
Install Ice yesterday (only got my phone Friday ), really like it over the stock rom.
Some people complained about the LED but I like it. My only complaint about my M8 was how bright the LED was specially in the dark when you're trying to get to sleep.
Another problem I'm having is file transfers freeze when using a USB 2 port on Windows 10.
I like my new M10 but not sure if I like it over the M8 as of yet. I preferred the speaker arrangement on the M8 and having the home, back buttons etc on the screen rather then down the bottom.
I have to admit I'm not a fan of the "Samsung" look at all which is why I bought HTC in the past to begin with. I didn't want to be a part of the flock.
Hey guys,
I'm looking to get the 10 but imported, could someone (especially looking for someone with Optus) check their box to see what specific model it is (e.g. 10h or 10u)?
Thanks guys
The Telstra model is a HTC 10h
ICE (InsertCoin) v2.0.6 supports Telstra also now too. Thanks @baadnewz
morgy59 said:
The Telstra model is a HTC 10h
Click to expand...
Click to collapse
Awesome, thanks morgy59
Found out that Telstra's policy for DOA/ELF replacements are within 30 days of purchase. Since a return will result in a repair, I'll wait to see if the OTA will fix the NFC issue first before sending back.
Has anyone experienced an NFC issue on Telstra stock, only to have it disappear after switching to a cusom ROM?
brantp said:
Found out that Telstra's policy for DOA/ELF replacements are within 30 days of purchase. Since a return will result in a repair, I'll wait to see if the OTA will fix the NFC issue first before sending back.
Has anyone experienced an NFC issue on Telstra stock, only to have it disappear after switching to a cusom ROM?
Click to expand...
Click to collapse
I found it worked perfectly fine on wwe 1.30 firmware using Leedroid. Now I'm on 1.53, hardly works at all
Sent from my SM-P605 using Tapatalk
It's doesn't read card on 1.53 on Optus build 710
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!
Everyone, I have a locked Verizon P2XL running Android P DP3. I've been on the DP train since it went live after I/O and I've had so few problems it's actually surprised me. But that all changed on Wednesday. I have been using Google Pay with no problems up until Wednesday night when I took my wife to Starbucks for a coffee and a chat. I was unable to pay for our products using Google Pay. Weird but okay, I just used my debit card and moved along. When I got home I checked into it. I saw that my device is listed as uncertified in Google Play Store app settings. This was not the case previously. I rebooted into the bootloader and my device states that it is indeed locked. I've already done 2 factory resets, this didn't fix or change anything except that now I have had to sideload Netflix as it won't install from the Play Store on an uncertified device. So that is problem #1, what could have caused this? Will it be fixed (best guesses please) when the DP4 OTA hits my phone? If not will the official release ROM for Android P correct this?
Problem #2 is that I can't get back to stock Android Oreo. I've tried doing it the official way by Opting Out on the DP webpage and taking the OTA. Installation fails with no indication as to why. I've also downloaded the latest official Oreo OTA and used adb sideload to install it. It also fails but using this method I actually get an error message stating that the OTA is older than the currently installed ROM so installation was aborted. I called Google about this, no help. But the support rep agreed with my current idea to try to rollback to Oreo when July's OTA is released as the timestamp will be newer than DP3 so Pixel downgrade protection will be circumvented. Or should be. Back to problem #1, will flashing the July Oreo OTA fix my device uncertified problem? I haven't had this phone very long so I'm disappointed with myself for effing around with the beta program before I really had a chance to use it (got the device in late April).
Thanks for any help.
Problem #1 has been fixed by following the advice of @Phazonclash here: https://forum.xda-developers.com/pixel-2-xl/help/google-pay-issue-t3810129
Problem #2 remains but I'm less eager to revert to Oreo now that the first problem is fixed.
Glad you got it sorted! Anyway, dp4 will be here soon....
Same thing happened to me. DP 3 was running great then out of nowhere the Android Pay was disabled.
I used the ADB commands and reflashed the Oreo Image. Now everything is back to normal. I have read on several forums the same problem.
Looked like some sort of timing issues that inactivates the Android pay after a certain date anticipitating a new build?
Cc
cc999 said:
Same thing happened to me. DP 3 was running great then out of nowhere the Android Pay was disabled.
I used the ADB commands and reflashed the Oreo Image. Now everything is back to normal. I have read on several forums the same problem.
Looked like some sort of timing issues that inactivates the Android pay after a certain date anticipitating a new build?
Cc
Click to expand...
Click to collapse
Which model phone do you have specifically and which Oreo image did you use? As I said I have a Vzw P2XL and I tried to flash the June OTA for the P2XL and it was a no go. I'd love to hear how you managed to do what I failed so miserably at.
Image
I have an unlocked Google version of the Pixel 2 XL. Download the image from the Google site. You can also download the Verizon version.
Cc
Ok, bought the CN version of the pad 5 as I guessed it would be simple to swap regions and after that oh so long 7 days, it was a cinch.
Thing is, I flashed it with the global ROM so effectively nerf'd OTA updates, except it didn't. The next time an update came up on the tracker I downloaded it to transfer to the tablet, only to see a notification of update available. Yup, the tablet then updated the OS to the latest Global Version.
My question is, is this usual? I'm happy ofc but could I maybe relock then bootloader and still get the Global channel? Would be handy for my useless bank app.
Just struck me as odd and Google returned nothing so......