Check out this VZW PDF document -
http://support.vzw.com/pdf/system_update/eris.pdf
It seems to have been authored only 6 days ago (Mon 21 Feb), and mentions a hitherto unknown Eris release - 2.41.605.6 (same radio as the July 2010 OTA, but different/newer ROM version number)
Anybody want to run stock 2.1 for a couple of days to see if they can capture an OTA download link?
I suppose it could be meaningful not only for 2.1/Sense dev ROMs, but also to Froyo/GB if there are any changes to any of the vendor hardware libraries (e.g. gps, rild, etc).
It does seems kind of odd though for HTC/VZW to be doing an OTA on a discontinued device - and no mention of 2.41.605.6 OTAs yet from non-rooted users. I wonder if this is real, or just a simple mistake on VZWs end of things.
??
bftb0
I think i will go back to stock and see if mine tries to update.
Sent from my Ginger Tazz using XDA App
It is a fact.
verison support site said:
Verizon Wireless recently released a software upgrade to the DROID Eris by HTC. All Verizon Wireless cell phone plan holders are encouraged to download this update for their HTC Droid Eris to improve the phone’s performance. The following instructions explain how to upgrade your phone’s software:
You will be notified that a system update is available via your notification bar. Select “system update available” to view the update details.
Read update details and when ready, select “Restart & Install”. Your device will power off and back on and the installation process will begin.
To manually update your phone or to check for updates to make sure you are running the most current software, go to Home > Menu > Settings > About phone > System updates. If an available update is shown, press “Restart & Install”. The device will power off and back on and the installation process will begin.
Note: If you have received and installed the update on your phone, you may experience delays in restoral of personal data, such as contacts, while the data is being re-synced. Data is normally re-synced within about 30 minutes after the update is complete. If for some reason the sync stalls or does not start, you can force a sync via “Sync Now” in Accounts and Sync menu or turning your phone off/on may help expedite the sync process. To see the order of sync and the sync status press Menu -> Settings -> Accounts & sync.
System Update While You Are Roaming
If you are roaming you will not receive a system update notice. You will need to enable Wi-Fi and wait for the update notice to appear.
To enable Wi-Fi, go to Settings > Wireless Controls and press Wi-Fi to enable.
To connect to an available Wi-Fi network, select “Wi-Fi settings” and choose an available Wi-Fi network or manually add a Wi-Fi network that has had security settings established.
Follow directions above to ensure proper installation of the updated software.
Click to expand...
Click to collapse
http://community.vzw.com/t5/Other-Android-Devices/HTC-DROID-ERIS-OS-UPDATE/ta-p/346372
There you go. The modified date is 1-24-2011.
Super_Dork_42 said:
http://community.vzw.com/t5/Other-Android-Devices/HTC-DROID-ERIS-OS-UPDATE/ta-p/346372
There you go. The modified date is 1-24-2011.
Click to expand...
Click to collapse
Except for the fact that not a single person has reported receiving a v 2.41.605.6 OTA. I suppose that rooters are the minority of users - so it would seems like somebody might have let out a peep if it was already being rolled out by VZW. Time will tell, I guess.
Super_Dork_42 said:
http://community.vzw.com/t5/Other-Android-Devices/HTC-DROID-ERIS-OS-UPDATE/ta-p/346372
There you go. The modified date is 1-24-2011.
Click to expand...
Click to collapse
That was last month?
Sent from my HTC Eris using XDA App
I was OTA 2.1 unrooted till last week and didn't get it.
Just ran the RUU, waiting for the phone to boot up.
Edit: System Updating
Would froyosense be nice. But I doubt it.
Sent from my GSBv1.7-ERIS using XDA App
spc_hicks09 said:
Just ran the RUU, waiting for the phone to boot up.
Edit: System Updating
Click to expand...
Click to collapse
I'm assuming the RUU gives you 2.36.605.1; let us know if you get anything besides 2.37.605.4 as a result of the OTA.
Changed nothing that I can see.
Firmware Version
2.1
Baseband Version
2.42.00.04.12
Kernel Version
2.6.29-8a03cb9a
[email protected] #1
Build Number
2.37.605.4 CL185970 release-keys
Software Number
2.37.605.4
Browser Version
WebKit 3.1
PRL Version
2.11_002
ERI Version
5
Afterwards I got "Your system is up to date"
Well, now to reroot.
I am kinda excited for this...I checked the HTC Developer site and at the top of the list is "Droid Eris by HTC - Eclair MR - 2.6.29 kernel source code" not sure when this was published and don't know the difference but this is all very interesting... the only difference is that earlier they released another one but is says Droid Eris by HTC (Verizon) - Éclair MR - 2.6.29 kernel source code....no Verizon in the newest one...
spc_hicks09 said:
Changed nothing that I can see.
Firmware Version
2.1
Baseband Version
2.42.00.04.12 <-- That is unexpected
Kernel Version
2.6.29-8a03cb9a
[email protected] #1
Build Number
2.37.605.4 CL185970 release-keys
Software Number
2.37.605.4
Browser Version
WebKit 3.1
PRL Version
2.11_002
ERI Version
5
Click to expand...
Click to collapse
Everything above seems like what would be expected from the July 2010 OTA - except the radio version. ( see here. )
spc_hicks09 said:
I don't think the update took or something. Phone is showing the wrong radio version and software number.
Click to expand...
Click to collapse
But something DID take - the RUU is 2.36.605.1, and you ended up with 2.37.605.4 (... and some strangeness involving the radio...)
All of the OTAs have been "incremental", not cumulative - they perform binary PATCHING of existing files, so they are highly sensitive to the starting version of the software. I would think that if VZW was really doing another OTA, the starting point would be 2.37.605.4. (There was a time when Google's servers simultaneously had two OTAs available: one that converted a Cupcake Eris @ 1.17.605.1 to 2.37.605.4, and one that upgraded the "Leak-V3/RUU" Eclair Eris @ 2.36.605.1).
bftb0
bftb0 said:
Everything above seems like what would be expected from the July 2010 OTA - except the radio version. ( see here. )
But something DID take - the RUU is 2.36.605.1, and you ended up with 2.37.605.4 (... and some strangeness involving the radio...)
All of the OTAs have been "incremental", not cumulative - they perform binary PATCHING of existing files, so they are highly sensitive to the starting version of the software. I would think that if VZW was really doing another OTA, the starting point would be 2.37.605.4. (There was a time when Google's servers simultaneously had two OTAs available: one that converted a Cupcake Eris @ 1.17.605.1 to 2.37.605.4, and one that upgraded the "Leak-V3/RUU" Eclair Eris @ 2.36.605.1).
bftb0
Click to expand...
Click to collapse
Could the radio just be because I flashed a radio when rooted ? I would think that the radio would have changed though when I ran the RUU. So the update itself, changed my radio ?
HaRdC0r3 said:
I am kinda excited for this...I checked the HTC Developer site and at the top of the list is "Droid Eris by HTC - Eclair MR - 2.6.29 kernel source code" not sure when this was published and don't know the difference but this is all very interesting... the only difference is that earlier they released another one but is says Droid Eris by HTC (Verizon) - Éclair MR - 2.6.29 kernel source code....no Verizon in the newest one...
Click to expand...
Click to collapse
Thanks for pointing that out - there are a LOT of files in there that have dates of 2011-02-23.
Maybe there is something to this after all.
They're probably just updating us to Honeycomb.
spc_hicks09 said:
Could the radio just be because I flashed a radio when rooted ? I would think that the radio would have changed though when I ran the RUU. So the update itself, changed my radio ?
Click to expand...
Click to collapse
The July 2010 OTA flashed a new radio as part of the update package.
The only way to know for sure what happened is for you (or someone else) to repeat the experiment you just went through, but make sure to capture the OTA download link. Then we can look into the update package and see what it is doing. It would be a surprise if HTC/VZW changed the radio version.
However - the 2.37.605.4 (July 2010 OTA) is old news - this thread is about something which is apparently more recent than that.
ONE MORE THING - there is a chance that the Android 2.1 (Evo/Unrevoked/wag3slav3) rooting exploit will be patched in a new update - there is a risk that if you roll back to capture a new OTA, you might end up with a phone which can not be re-rooted, as every OTAs has also replaced the recovery partition. If you are going to take that risk, you probably ought to have the S-OFF bootloader installed on the phone.
bftb0
I'll give it a try, after the update I was already able to reroot and flashed Ginger Tazz 8 again with no issues. I'll give it a try and run logcat so I can get the link.
If just the radio changed, Sprint recently updated the Hero radio to something newer than what we got in the July Update.
I wonder why Verizon would care if we rooted our Erises at this point?
Ok so the RUU i'm using says:
RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver
Will update again with logcat and phone info in about 10 minutes.
@ stonent .I was talkin to Verizon yesterday .. the guy told me I should look into.rooting lol I said I already have and running gb lol
sent from my invisable htc thunder bolt
Related
Hi,
I have a problem with a friend of mine's HTC Hero (GSM version), it was bought overseas, and at some point it started giving these update messages, see the image attached.
if we choose "update now" the phone reboots into "cyanogenMod V1.4 + JF recovery mode", I don't know exactly what to do from there, the "cyanogen" lead me to think that the phone is rooted but I tried to run some applications such as terminal and superuser permissions and both of them acted/reported as if the phone is not rooted.
I've searched the net for answers and found 2 solutions that are not applicable:
1. change a file named otacerts.zip to otacerts.bak - I've read that it makes the updater think that the file is corrupt and keeps downloading it indefinitely.
2. factory reset - but I'm afraid it will simlock the phone to its original vendor - preventing us from making calls and using 3G and remove our language support.
any help will be appreciated.
p.s :
I don't have the exact version number on me right now, I will post it if its critical.
We don't want to actually apply the update (unless it won't damage functionality), just to stop the notification.
You might want to provide us with your firmware version, what ROM your running and android version. Check by the settings>about phone>software info
thanks for the reply, here is the requested information:
Firmware version:1.5
Baseband version: 63.18.55.06EU_6.35.06.18
Kernel version: 2.6.27-8dd6deee
[email protected] )
Build number: 2.73.405.5 146733 CL#61267 release-keys
Software version: 1.0.0.A6288
Hm, it looks like your running a very old firmware. Android version 1.5. We have been officially updated to 2.1. That is probably what the over the air (OTA) nagging update is about. Now im not sure whether your phone is rooted or not since i dont know what "cyanogenMod V1.4 + JF recovery mode" is. However, i think if you update it thru the OTA, you will lose root access assuming that you have it already. The most commonly used recovery for flashing and updating firmware is this one: http://forum.xda-developers.com/showthread.php?t=561124
So i guess the next step is for you to decide whether you want your phone rooted or to just accept the OTA update (the update will wipe your phone i think). Or you can go to settings>about phone>system software updates>untick scheduled check to stop the nagging. Although i recommend either rooting the phone and installing custom firmware, or taking the OTA update jus to be up to date
Oh yea i believe this is only part 1 of the update, which isnt the 2.1 firmware yet. This is a preparation step. However, the second part should come to you shortly after you accept this one. So i dont think this first part will wipe your phone, but im not positive
Second, we need someone else with more knowledge to tell you if your phone is rooted
I am very interested to see if it helps!!
http://phandroid.com/2015/04/09/htc-one-m9-camera-update/
Me too
AT&T Update
What happened to the AT&T update they said would be released on the 17th (today)? Has anyone else on AT&T received it yet?
rmc69 said:
What happened to the AT&T update they said would be released on the 17th (today)? Has anyone else on AT&T received it yet?
Click to expand...
Click to collapse
I've been checking all day; No word from anybody. Even searched on Twitter to see if anyone mentioned it...
I just received this email:
Camera quality improvements
Update to the HTC camera is hitting the HTC One M9
An important update will begin rolling out to the HTC One M9 camera improving the overall image quality.
Expected results are:
• Reduced blur in photos thanks to enhanced exposure times
• Increased sharpness in photos making them clear but with a less artificial feeling.
• Reduced image noise
• Improved low light performance and HDR processing
• Better Auto Exposure interface performance when tapping the screen
The camera update is included in the launch software of the Verizon and Sprint variants. The T-Mobile camera update will come in the form of a user initiated over-the-air update on April 20th with the AT&T update coming on April 21st.
verks said:
I just received this email:
The camera update is included in the launch software of the Verizon and Sprint variants. The T-Mobile camera update will come in the form of a user initiated over-the-air update on April 20th with the AT&T update coming on April 21st.
Click to expand...
Click to collapse
:good:cool! I just got that too from HTC Champions. At least we know now.
verks said:
I just received this email:
Camera quality improvements
Update to the HTC camera is hitting the HTC One M9
An important update will begin rolling out to the HTC One M9 camera improving the overall image quality.
Expected results are:
•Reduced blur in photos thanks to enhanced exposure times
•Increased sharpness in photos making them clear but with a less artificial feeling.
•Reduced image noise
•Improved low light performance and HDR processing
•Better Auto Exposure interface performance when tapping the screen
The camera update is included in the launch software of the Verizon and Sprint variants. The T-Mobile camera update will come in the form of a user initiated over-the-air update on April 20th with the AT&T update coming on April 21st.
Click to expand...
Click to collapse
Thanks
Update is available on AT&T as of now. Downloading to phone, but am sure since the phone is rooted it won't install.
dratsablive said:
Update is available on AT&T as of now. Downloading to phone, but am sure since the phone is rooted it won't install.
Click to expand...
Click to collapse
I am rooted as well, but with stock recovery... downloading the update now. Is there a way to capture the update? Maybe someone can make a flashable zip of it.
sdotagain said:
I am rooted as well, but with stock recovery... downloading the update now. Is there a way to capture the update? Maybe someone can make a flashable zip of it.
Click to expand...
Click to collapse
That's what I am hoping for.
dratsablive said:
That's what I am hoping for.
Click to expand...
Click to collapse
I take it your update didn't install?
sdotagain said:
I take it your update didn't install?
Click to expand...
Click to collapse
Nope, failed probably because I have TWRP installed.
dratsablive said:
Nope, failed probably because I have TWRP installed.
Click to expand...
Click to collapse
Mine failed as well with stock recovery so it must be because of unlocked bootloader/root
sdotagain said:
Mine failed as well with stock recovery so it must be because of unlocked bootloader/root
Click to expand...
Click to collapse
The stock recovery is needed to install the OTA, but it won't download if the system partition has been modified. Having the beta version of TWRP won't break the ability to download an OTA, but having flashed a root package or any other modification will.
navalynt said:
The stock recovery is needed to install the OTA, but it won't download if the system partition has been modified. Having the beta version of TWRP won't break the ability to download an OTA, but having flashed a root package or any other modification will.
Click to expand...
Click to collapse
Will temp unroot fix the permissions?
dratsablive said:
Will temp unroot fix the permissions?
Click to expand...
Click to collapse
Nope. Once you make the modification you're done. What you could potentially do is restore someone else's unmolested TWRP backup of the system partition. The files can be found HERE and the process can be found HERE to get you started on that path.
There are usually drivers or firmware files within the ROM that interface with the device hardware/firmware so after upgrading to the new OTA you'll want to use the stock ROM or a custom ROM based on the same OTA. If you try to backup your current ROM and restore it afterwards you may not see the benefits or you could run into some funky problems with the camera and radios.
Stock 1.32.502.31 RUU
Stock AT&T 1.32.502.31 RUU
This software upgrade available for your HTC One provides the following key enhancements:
· Camera improvements
· Thermal improvements
· Various bug fixes and improvements
This will wipe your phone and restore it back to stock (how you purchased it)
RUU_HIMA_UL_L50_SENSE70_ATT_Cingular_US_1.32.502.31_Radio_01.01_U11440221_62.05.50320G_F_release_426950_signed_2.exe
MD5: e68438231773b8d93091392844939993
How to perform the ROM Update:
1. Download and save the HTC One™ update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC One™ ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, the device is ready for use.
Note : If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit download mode manually, use the volume keys to navigate to reboot and press the POWER button to select it.
So I have an unlocked Att M9 on T-Mobile, I'm gonna assume I have to do it manually via the RUU correct?
I used the RUU Utility provided on the HTC Website. At first it appeared to fail, and I had to restart the utility. It asked to repower the phone, but I could power it down. Thought it was a soft brick. But I reran the utility and it worked. Still unlocked and S-OFF.
effortless said:
Stock AT&T 1.32.502.31 RUU
This software upgrade available for your HTC One provides the following key enhancements:
Click to expand...
Click to collapse
Application fails to run on my PC - Win8.1/64 - anyone else having the same problem?
Reverted MT2-L03 back to stock, bootloader unlocked/rooted -, even reflashed stock recovery to be on the safe side (with root).
Unlike other people, whom seem to be getting a push notification for system update, this phone gives no such thing. I'm on Wind mobile, doesn't notify whether on WiFi or carrier network.
Reading "How To Get Update" on other sites tells me to go to Huawei's site directly, but all I see is a download for HiSuite.
For the heck of it, I also tried to fetch an update manually through "System Update" on the phone, and through HiSuite, no dice.
Don't need a recovery image, need this elusive update app/image everyone is talking about. That said, does anyone have a clean source for this, since Huawei isn't pushing it to my device? Thanks!
Other Info:
MT2-L03
Carrier: WIND Mobile (carrier does not impose any restrictions or software, stock = factory stock)
Android 4.3 (184 is still on 4.3 with some fixes right? Some select apps have issues with later ver. of Android)
Bootloader = UNLOCKED; Rooted with KingoApp, variant of SuperSU is the only thing installed (KingoUser) for permissions.
Current build: 128
volcolm said:
Reverted MT2-L03 back to stock, bootloader unlocked/rooted -, even reflashed stock recovery to be on the safe side (with root).
Unlike other people, whom seem to be getting a push notification for system update, this phone gives no such thing. I'm on Wind mobile, doesn't notify whether on WiFi or carrier network.
Reading "How To Get Update" on other sites tells me to go to Huawei's site directly, but all I see is a download for HiSuite.
For the heck of it, I also tried to fetch an update manually through "System Update" on the phone, and through HiSuite, no dice.
Don't need a recovery image, need this elusive update app/image everyone is talking about. That said, does anyone have a clean source for this, since Huawei isn't pushing it to my device? Thanks!
Click to expand...
Click to collapse
I also have a Wind MT2-L03, and mine has never had the bootlaoder unlocked, and never rooted, yet I'm also stuck on the build B128 that it came with, with no push notification for system update. So your issue has nothing to do with anything you may have done to your device. Looks like Wind users are left out in the cold on this one.
antinerd said:
I also have a Wind MT2-L03, and mine has never had the bootlaoder unlocked, and never rooted, yet I'm also stuck on the build B128 that it came with, with no push notification for system update. So your issue has nothing to do with anything you may have done to your device. Looks like Wind users are left out in the cold on this one.
Click to expand...
Click to collapse
It would seem that way. Perhaps Wind's version works well enough that they don't need to update said devices (or maybe issues aren't as prevalent on these). So far haven't noticed any issues, but I've emailed Huawei mobile support later in their afternoon, and just about 10 minutes ago, so awaiting what they say about any later firmware updates.
_____
That said, HiSuite finally pushed a version update (of HiSuite software) then checked for Android OS updates through it (sends IMEI back to Huawei then checks their database). It says "Your device has the latest version." So that answers that, at least.
So I just got a new moto e 2nd gen just a few days ago.
Currently running 5.0.2.
Hardware SKU XT1511.
As far as I understand the 5.1 OTA came out a few months ago, correct?
But when I go to the system update, it just says "Your device's software is up to date"
What's going on here? Is there a link to download the ota zip so I can just run adb and flash it myself???
Sent from my MotoE2 using XDA Free mobile app
Same thing happening here, but with XT1526 I live in another region, so I don't know if that has anything to do.
For what it's worth, I live in the USA and purchased this device brand new from best buy just a few days ago.
So yeah, not sure what is going on with the update.
This phone is the 3G version, the retail US model that has LTE connectivity is the one with the 5.1 update.
This phone model has been seemingly neglected by Motorola, this thread in the Motorola Forum has info about the updates of the Moto E 2015, no updates at all for the 3G model
I just purchased the XT1527 LTE model off Amazon for $100 for my grandma to use instead of her crappy ZTE flip phone. She is on my aunt's AT&T 60GB plan for her small business and when the phone first arrived, I signed into her Google account and got everything setup but when I tried to pull the 5.1 update, it wasn't getting it yet and said it was already up-to-date with 5.0.2.
Later that day we finally went to the AT&T store to get a SIM put in it and her number transferred over, but still, no 5.1 update for it yet.
Does anyone know why my XT1527 model can't pull the update yet? I thought for sure it would have been able to pull it when I first turned it on, before even getting the SIM for it.
Is there anyway for me to manually install the OTA without unlocking the bootloader or flashing TWRP or are we just stuck waiting?
dabug91 said:
I just purchased the XT1527 LTE model off Amazon for $100 for my grandma to use instead of her crappy ZTE flip phone. She is on my aunt's AT&T 60GB plan for her small business and when the phone first arrived, I signed into her Google account and got everything setup but when I tried to pull the 5.1 update, it wasn't getting it yet and said it was already up-to-date with 5.0.2.
Later that day we finally went to the AT&T store to get a SIM put in it and her number transferred over, but still, no 5.1 update for it yet.
Does anyone know why my XT1527 model can't pull the update yet? I thought for sure it would have been able to pull it when I first turned it on, before even getting the SIM for it.
Is there anyway for me to manually install the OTA without unlocking the bootloader or flashing TWRP or are we just stuck waiting?
Click to expand...
Click to collapse
Same thing here. I'm not getting 5.1 or any other update. XT1527 from Amazon. System version is 22.36.1.surnia_retus.retus.en.US Build LXI22.50-24.1.
Kernel is dated Feb 7 2015. Does anybody know why this is happening? Sorry to bump an old thread but I firmly believe this is relevant today.
By the way, I contacted Motorola support but they gave me a nonsense answer (i.e. that my phone is fine as it is with no 5.1.)
I have the XT1528 model and it says I have 5.1, but my phone still seems to be affected by stagefright 2.0. I assumed that 5.1 would fix that problem, but I am worried Motorola isnt even going to fix the issue.
That guy earlier said look at the link to see who is getting the 5.1 update rollup.
Don't expect to get it if your not only the list.
Also i seen myself that there was more than 1 stage fright update for 5.0.2
because there was more versions of the exploit that needed to be patched as time went on.
SO there was separate stage-fright updates for 5.0.2 and 5.1 respectively.
in other words you did not have to have 5.1 installed to get stage fright patched with an update.
They probably did that because they know most carriers are not pushing out 5.1 to their customers.
Which leads me to my next point..
It's not up to Motorola..
They can offer the update to any specific carrier but it's up to the carrier to decide if it is rolled out to customers.
It's been a long time now and most carriers did not get the 5.1 update.
It is doubtful i think anyone new is going on that list of who gets it.
For example my carrier in Canada Telus never rolled it out.
I had to get a stock firmware package for another carrier for 5.1 and put it on myself.
I chose to use the generic USA Retail Firmware package.
All has worked well but my phone model is suppose to be using LTE/cdma (surnia_umts)
But i have struggled to get it back on cdma.. with nobody out there with any suggestions on how to fix it.
Had i not tried to switch it over manually to GSM after install i would have given up.
Luckily my Carrier Telus supports CDMA and GSM.
I only found 1 guy who left a comment i seen way back saying he fixed his radio issue
by having his stock 5.0.2 Radio left intact then flashing all else to update.
That did not do me any good.. i have tried many variations with no difference.
I can confirm i was getting a new recent stage fright update OTA prmpt.
And there was a new updated firmware package shared recently that included this newer update.
I installed it and used a Stagefright checker App that scanned for about 10 variations of the exploit
and my phone was reported by the app as safe. (patched)
This version was just recently put on the web by someone..
XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml
MD5: 586d4a4888a570e6119c60d7437b6bcc
It has this OTA patch update integrated..
Blur_Version.23.11.15.surnia_retus.retus.en.US
MD5: 7b74752978545ccd0100c3d236cc88f6
xpmule said:
That guy earlier said look at the link to see who is getting the 5.1 update rollup.
Don't expect to get it if your not only the list.
Click to expand...
Click to collapse
My phone is on that list but it's not getting the 5.1 OTA.
xpmule said:
in other words you did not have to have 5.1 installed to get stage fright patched with an update.
They probably did that because they know most carriers are not pushing out 5.1 to their customers.
Which leads me to my next point..
It's not up to Motorola..
They can offer the update to any specific carrier but it's up to the carrier to decide if it is rolled out to customers.
Click to expand...
Click to collapse
It's not getting Stagefright patches either. Regarding the carrier, XT1527 is factory unlocked, which means it's not tied to a specific carrier.
Motorola should provide the updates since they say they do have a 5.1 update on their support site.
xpmule said:
I had to get a stock firmware package for another carrier for 5.1 and put it on myself.
All has worked well but my phone model is suppose to be using LTE/cdma (surnia_umts)
But i have struggled to get it back on cdma.. with nobody out there with any suggestions on how to fix it.
Click to expand...
Click to collapse
Did you try with 4G LTE Switch app? Its ID is com.tapbase.LTEswitcher
xpmule said:
I can confirm i was getting a new recent stage fright update OTA prmpt.
And there was a new updated firmware package shared recently that included this newer update.
XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml
It has this OTA patch update integrated..
Blur_Version.23.11.15.surnia_retus.retus.en.US
Click to expand...
Click to collapse
Interesting. Do you know if I can do this update to my phone without unlocking the bootloader? I don't want to void the warranty.
yituge said:
My phone is on that list but it's not getting the 5.1 OTA.
It's not getting Stagefright patches either. Regarding the carrier, XT1527 is factory unlocked, which means it's not tied to a specific carrier.
Motorola should provide the updates since they say they do have a 5.1 update on their support site.
Did you try with 4G LTE Switch app? Its ID is com.tapbase.LTEswitcher
Interesting. Do you know if I can do this update to my phone without unlocking the bootloader? I don't want to void the warranty.
Click to expand...
Click to collapse
Don't count on what i am saying i am a noob eh..
But yeah i think you can just flash that version i did.
Even if your bootloader is locked.
From the sounds of it i think that firmware i used on my Telus carrier phone
was actually originally intended for YOUR phone !
And 4G LTE Switch app?
Hmm no i have not seen that.. i should check it out thanks.
---------- Post added at 08:30 PM ---------- Previous post was at 08:16 PM ----------
I checked out that APP and all it does is open the settings menu for you.
You can just use the dialer instead..
*#*#INFO#*#*
That gives the same thing as that APP
I also have found it to be -read only- on my phone.
So if you change the option it actually doesn't work.
If you REALLY want to change it for real you have to use an alternate method such as..
connect with ADB using your computer.
then use this command..
Code:
adb shell
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
Note: That will force LTE/GSM (auto PRL)
you don't need root to do that in the cmd prompt either.
and most guys out there say do another cmd line..
Code:
settings put global preferred_network_mode2 9
But i had checked and that line did not exist so i doubt adding it will do anything.
Change those lines to "get" and look at the value currently set before changing them.
When i ran the 3rd line it said that key does not exist.
Also the number 9 is LTE/GSM (auto PRL)
SO if you use that dialer command or that app you can count down the drop down list
to see what option is what number (to force it via command line)
For example..
no. 8 is..
LTE/cdma (auto PRL)
xpmule said:
Don't count on what i am saying i am a noob eh..
But yeah i think you can just flash that version i did.
Even if your bootloader is locked.
From the sounds of it i think that firmware i used on my Telus carrier phone
was actually originally intended for YOUR phone !
Click to expand...
Click to collapse
Don't worry, I'm a noob too, just trying to read a lot before doing anything.
I checked my phone and everything matches to this ROM:
SURNIA_RETUS_5.0.2_LXI22.50-24.1_cid9_subsidy-DEFAULT_CFC.xml.zip
I also installed CID Getter for further confirmation and ro.boot.cid is 0x9 (i.e. CID9.)
Which ROM I should flash to my phone:
the older SURNIA_RETUS_5.1_LPI23.29-15_cid9_subsidy-DEFAULT_CFC.xml.zip
or the newer XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml.zip ?
Does the last one contain Stagefright patches?
My main concern is -if I'm not mistaken- that either one should be 100% official Motorola or it won't flash with a locked bootloader.
xpmule said:
I checked out that APP and all it does is open the settings menu for you.
You can just use the dialer instead..
*#*#INFO#*#*
That gives the same thing as that APP
I also have found it to be -read only- on my phone.
So if you change the option it actually doesn't work.
Click to expand...
Click to collapse
I see. I thought it could work for you, but at least you know a workaround. Thanks for sharing.
Just got the OTA tonight, 6/24
Notes:
Android security update: June 1, 2020
thanks
muffnman said:
Just got the OTA tonight, 6/24
Notes:
Android security update: June 1, 2020
Click to expand...
Click to collapse
ok
Still waiting on it here, anyone else?
I haven't been able to get it. I'm not particularly worried about it, being a security update it would be nice to have though. The last one took a while as well.
ttabbal said:
I haven't been able to get it. I'm not particularly worried about it, being a security update it would be nice to have though. The last one took a while as well.
Click to expand...
Click to collapse
I live in the Seattle area and I still can't get 36 yet.
Still haven't gotten it here either
Still waiting as well
Still nothing here also. Normally I would just run the MSM tool and get 10.0.36 that way, but my phone is running so nice on .35, I don't want to have to set it all up again.
NotATreoFan said:
Still nothing here also. Normally I would just run the MSM tool and get 10.0.36 that way, but my phone is running so nice on .35, I don't want to have to set it all up again.
Click to expand...
Click to collapse
Same. Wish there was a way to run msm tool without it wiping data or be able to extract fastboot images from it...
Everyone still waiting? Been 2 weeks since it was released and received by some/most...
Still waiting here- no update.
Yup. Tried unrooting just to see, no change. Weird, but I guess I don't NEED it. I do wish they would allow us to side load them though. I prefer to be up on security updates.
Woke up to some weird quirks with my phone and the Play Store, so after hours of troubleshooting, I just restored to 10.0.34 using MSM. I'm in the process of unlocking, fixing the reserve.img, and updating the 10.0.36 via OTA.
I'll update my reserve.img fix as soon as I'm done, so that anyone wanting to MSM straight to 10.0.36 won't have to jump through the same hoops.
Still waiting here in NY...
Still waiting in california
Im starting to think I will not get this update. Anyone find a reason why these updates are not coming through?
I think the issue is if you mount / (root) as r/w even once, it screws up the checksums and the updates don't come through.
I used the msm tool to update to 10.0.36 (losing all my data in the process) and the tool for 10.0.36 to restore reserve (tyvm @NotATreoFan), but even after updating, in security it was showing security update as June 1, 2020 (which is correct for 10.0.36) but for Google Play system update, it was still showing April 1, 2020 with a red icon instead of green. Clicking it and searching for updates didn't help (no updates found). Updating play services manually didn't help. But after 2 or 3 days, it must have updated in the background because Google Play system update is now showing July 1, 2020 (with security update showing June 1, 2020). Just FYI, the Google Play system update is part of project mainline (an extension of project treble) which allows Google to update parts of the phone without going through any oems or carriers. So even the msm tool for 10.0.36 only comes with the Google Play system update from April 1. Luckily as I said, it updates in the background after just approx 2 days.
But back to the main issue of not receiving the 10.0.36 update, maybe it's a waiting game, but it's never taken this long before. As I said, I think it's from you or a badly written magisk module from setting root directory to r/w even once (even if restoring it back to r/o without making any changes). If I'm correct, the only way to fix is by running the msm tool (since OnePlus refuses to let us have downloadable OTA updates or even a full fastboot package)
Edit: Also, if you have previously fixed your persist for FP to work, you'll have to restore your backup of fixed persist after running the msm tool and then unlocking the bootloader or your FP sensor won't work. Also, as mentioned above, you'll need to restore the reserve partition as well since the msm tool locks the bootloader and unlocking it causes reserve to be deleted. Don't you just love this phone...
Pic added to clarify the difference in the two types of security updates
I don't think there is any great need to update to this one, but I'll probably do the next one via MSM just to keep reasonably up to date.
Honestly, I really do like the device overall. It works well, is snappy, and has decent 5G support. I do not like that it's hobbled by TMO like most carrier devices on the software side. But at the same time, non-carrier devices often have issues with volte, which is going to be required here soon. Oneplus seems to support the international version pretty well, so it seems obvious this version is being held up by TMO. Sad, overall I like them.
What I don't get is that when I first got the phone I rooted it and few weeks later I got a OTA. I had to removed Magisk and replace the adb recovery with the stock one. Then the OTA updated without a issue and did the re-root procedure. After that I put back the reserve file(supposed to fix OTAs). And now no OTA? Weird because unless something was part of the updated I don't understand why the first update came through but not the next one...
t436h05t said:
What I don't get is that when I first got the phone I rooted it and few weeks later I got a OTA. I had to removed Magisk and replace the adb recovery with the stock one. Then the OTA updated without a issue and did the re-root procedure. After that I put back the reserve file(supposed to fix OTAs). And now no OTA? Weird because unless something was part of the updated I don't understand why the first update came through but not the next one...
Click to expand...
Click to collapse
Well if it had updated correctly previously, your reserve file had already been restored, so there was no need to restore it again.
But regardless, all of those errors that were seen if reserve hadn't been restored, or if boot or recovery images hadn't been restored to stock, were installation errors. The OTA was found, downloaded, but there was an issue on installation.
The problem now is that no OTA is being found. I'm beginning to think they possibly pulled 10.0.36 due to some bug, because no one has had to wait for an OTA this long previously. The only thing that should stop an OTA from being seen/found is if one had updated their fingerprint (to spoof a pixel for example).
At least from your screenshots, you see that Google was able to install their "project mainline" update. It's in the pics from security under Google Play System Update (is completely separate from Play Services) dated July 1, 2020.
Let's hope T-Mobile gets this missing OTA crap fixed asap