Hi all, I have a G8x that I got shortly after launch from AT&T that's never been able to receive an OTA update.
I've read online that an AT&T SIM is required to get updates, which I have. The OTA update menu just says that I'm up to date, currently on Android 9, software version G850UM10f
LG Bridge seems to connect to the phone, then says "Cannot check the software version. Try again." - I've tried every way I can to make it work, phone restarts, different cables, you name it and LG Bridge doesn't seem to like this phone either.
Do I have any options to get an update? I'd prefer not to flash it but if that's my only option I'm not completely against it. Does anyone have a good guide to do that, and where I can get the latest Android 12 firmware image?
Thanks in advance!
Keep it on 9. It's a great OS. If you go to the mess that's 12 it will suffer from the effects of cpu cycle sucking scoped storage among others horrors. Pie was the zenith for Goggle Android... in my opinion.
Rule #1 - if a OS is fast, stable and fulfilling its mission... let it be!!!
You're probably right, it's working fine. I just get a little worried when I see that Android security patch level from September 1, 2019!
I've been ignoring it for this long, I'll probably continue to ignore it until I get something newer. Still, just doesn't feel right!
foxtrotftw said:
You're probably right, it's working fine. I just get a little worried when I see that Android security patch level from September 1, 2019!
I've been ignoring it for this long, I'll probably continue to ignore it until I get something newer. Still, just doesn't feel right!
Click to expand...
Click to collapse
This N10+ was last updated Nov 2019, current load is over 2 yo, still fast, stable with minimal maintenance. Security is not an issue.
Don't sweat it one bit but be ready to reload if needed; keep critical data redundantly backed up. A factory reset will purge any rootkit on Android 9 and up. I never had to reload my device because of malware though, it does very well.
Using Karma Firewall*, Package Disabler, I watch all downloads and especially installed apps**, wifi and NFC always disabled. I primarily use Brave browser and will backout, shutdown the window, browser, whatever, if I get on a really bad site... occasionally had to clear the cache. Email is always kept in the cloud.
I also use the setting change which blocks ads globally and some blacklisted sites.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*Apps that don't need internet access are firewall blocked.
**anything sideloaded gets scanned with online Virustotal and it better not even look a little funny.
foxtrotftw said:
Hi all, I have a G8x that I got shortly after launch from AT&T that's never been able to receive an OTA update.
I've read online that an AT&T SIM is required to get updates, which I have. The OTA update menu just says that I'm up to date, currently on Android 9, software version G850UM10f
LG Bridge seems to connect to the phone, then says "Cannot check the software version. Try again." - I've tried every way I can to make it work, phone restarts, different cables, you name it and LG Bridge doesn't seem to like this phone either.
Do I have any options to get an update? I'd prefer not to flash it but if that's my only option I'm not completely against it. Does anyone have a good guide to do that, and where I can get the latest Android 12 firmware image?
Thanks in advance!
Click to expand...
Click to collapse
You need a active AT&T account,not just the sim card.If you have that,all you have to do is call tech. support and let them add the IMEI so it will push the update OTA to the device.Fairly simple!
Related
As some of you know, MR4 is set to roll out in stages starting today (July 16th) and is said to have many updates. Here is a list: Click
Does anyone know if this maintenance release will fix the "Silent Call" bug?
Looks as if that pdf is incorrect. The way that is describing its 2.1. I think Verizon forgot to update that particular pdf.
MR4 update is not Froyo. It should however fix the silent call bug on the device. I care not anymore as I have root, but it is still indeed going to be 2.1. I don't think the Eris is capable of having Froyo with HTC sense uploaded into the device. It might be too much for it, and that's ASSUMING that VZW will get the update sent out correctly this time.
Shadow
Just root and get KaosFroyo!
I already know it isn't 2.2. I was just asking if it would fix the particular bug I was talking about...
I actually called customer service and they told me it was rolling out on July 16th and my device would get it within 7 days. I didn't think I would get it 10 minutes after getting off the phone with her! I am now on MR4. Only time will tell to see if this "Silent Call" bug is fixed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
its kind of impossible for anyone to answer your question since youre the first report of someone receiving the update that Ive read ........ so how would anyone know?
of course the only way someone will know is for a person who likes to come to forums and ask alot of questions about will this do this or this do that to actually capture the link when they do the d/l so that the devs can pick it apart
this way instead of just asking questions that are impossible to answer..... the person might actually provide the information to make receiving an answer possible
just my 2 cents early morning rant
HTC Legion said:
I already know it isn't 2.2. I was just asking if it would fix the particular bug I was talking about...
I actually called customer service and they told me it was rolling out on July 16th and my device would get it within 7 days. I didn't think I would get it 10 minutes after getting off the phone with her! I am now on MR4. Only time will tell to see if this "Silent Call" bug is fixed.
Click to expand...
Click to collapse
If anyone else gets this, please capture your URL.
bftb0 said:
The OTA .zip files which are downloaded from a Google server are not signed the same way as the RUU "rom.zip" files - they use the app .apk manifest signing method. (manifests and certs a la "jarsigner").
If you are interested in looking at the process that HTC/Verizon uses for the OTA updates, you can get the URL for the OTA zip the following way:
Run logcat on the pc and accept the update on the phone
$ adb logcat > logcat_accept.txt
This will sit like this (it continues to log output into the output file) until the phone reboots. At that point, the adb logcat job will terminate, and the name of the zip file will be indicated in the logfile in a message similar to:
W/SystemUpdateHelper( 64): !!! REBOOTING TO INSTALL /cache/desirec-ota-104882.7b1e5cca.zip !!!
Then, take the name of the file and paste it on the end of android.clients.google.com/updates/partner, for instance, for the Eris 1.17.605.1 OTA, the complete url is:
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
Note: because the 2.1 release is so vastly different than the 1.5 release, an OTA (if that's the way VZW/HTC rolls it out) for that will probably be very different than a patch release like this example ... but it would still be very useful for anyone who gets notice of an update to capture the URL using the "logcat" method shown above. There might be "interesting" tools included that could be exploited.
I don't think this will help get an "early OTA" - I'm not sure that hboot/fastboot methods can make use of an "update.zip" with an unrooted phone. Someone can correct me if I am wrong about that.
bftb0
Click to expand...
Click to collapse
Sorry, I didn't know. I just though it would be some information that I missed. I know I'm new here, but you don't have to treat me like I'm an idiot. Jeez. =[
Sent from my Eris using Tapatalk
I was just wondering if anyone who has gotten this has tested the root methods to make sure they still work, or if Verizon has patched them.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I bought second hand z4 from some guy who work for Sony. How to flash normal (not prototype) rom in this device? Everything works fine, Camera., Apps, Android os is 5.0.2 kernel 3.10.49, everything is smooth, but there is anoying message "You have crash artifacts to upload" all the time!? If I cant flash normal rom, is there any method to kill that message? Thanks..
Bite_my_shiny_metal_ass! said:
I bought second hand z4 from some guy who work for Sony. How to flash normal (not prototype) rom in this device? Everything works fine, Camera., Apps, Android os is 5.0.2 kernel 3.10.49, everything is smooth, but there is anoying message "You have crash artifacts to upload" all the time!? If I cant flash normal rom, is there any method to kill that message? Thanks..
Click to expand...
Click to collapse
I believe that sticker talks for itself and my advice would be not to be so open about this transaction.
In any case unless you have an EMMA account with relevant privileges you can't do much.
If you are lucky enough and Sony enables OTA updates for customer acceptance firmware applicable to the variant you have then at least you might get a firmware update in the future. But if you have as you say the crash handling app installed then probably you have an quite old FW which might not get any OTA.
Is there any way to instal new firmware without OTA? I think for z4 actual android official version is 5.11? If i kill process com.sonymobile.crashmonitor.system and com.sonymobile.crashmonitor.ui anoying message "You have crash artifacts to upload" is gone. Z4 is alredy long time on the market, so stickers now dont have much point anymore?
Bite_my_shiny_metal_ass! said:
Is there any way to instal new firmware without OTA? I think for z4 actual android official version is 5.11? If i kill process com.sonymobile.crashmonitor.system and com.sonymobile.crashmonitor.ui anoying message "You have crash artifacts to upload" is gone. Z4 is alredy long time on the market, so stickers now dont have much point anymore?
Click to expand...
Click to collapse
The last part is something you need to discuss with Sony but I don't believe a prototype unit on the loose is something they don't take seriously.
If I were you I'd ask the seller to take it back and refund you because as I wrote the only option for updates you have is either EMMA access with the proper permissions to download customer acceptance firmwares, someone with such access to give you the firmware or sony to enable OTA for customer acceptance firmware. The latter happens some times.
With the current firmware you have you can of course kill as you said some processes to get rid of the crash monitor app and notifications but there are still other debug bits enabled. If the firmware has root access enabled - there are such debug firmwares and you can check that from adb shell with su - you can clean it up a bit more.
That is all I can provide as info.
Solution is very simple. I download latest firmware 28.0.A.8.260 with XperiFirm and flash with flashtool and everything works perfect! No anoying messages anymore, nothing..
Bite_my_shiny_metal_ass! said:
Solution is very simple. I download latest firmware 28.0.A.8.260 with XperiFirm and flash with flashtool and everything works perfect! No anoying messages anymore, nothing..
Click to expand...
Click to collapse
Prototypes have a different bootloader so you can't flash retail firmware on it and vice versa.
Up to Z3 tablet this was valid also for tablets, if they changed that in Z4 then you are lucky.
Hi everyone,
Did anyone else get an update?
I was already on android 10, decides to click update and instead of downloading a small incremental update. It seems to have downloaded the whole android 10 again. Was something like 1.3gb.
Anyone else?
sstanton86 said:
Hi everyone,
Did anyone else get an update?
I was already on android 10, decides to click update and instead of downloading a small incremental update. It seems to have downloaded the whole android 10 again. Was something like 1.3gb.
Anyone else?
Click to expand...
Click to collapse
Yes. Me too
Sent from my Pixel 3 using Tapatalk
Nothing here yet on my P3 (using on AT&T), but there is a long thread on AC. It's apparently a new version.
Sent from my Pixel 3 using Tapatalk
Anyone know of the changes? Weird for it to come out as a full download, especially before the normal beginning of the month cycle
Look at this https://developers.google.com/android/images 10.0.0 (QP1A.190711.020.C3, Sep 2019)
Its look like an update with patches ?!
Malinnn said:
Look at this https://developers.google.com/android/images 10.0.0 (QP1A.190711.020.C3, Sep 2019)
Its look like an update with patches ?!
Click to expand...
Click to collapse
Ahh nice one thanks!
I read it's like a kernel update to stop battery drain? At least that's what some on Reddit say!
Hello.
Multitasking have no freeze anymore! Super!
Will see about the battery drain.
I just got a small update. Unlocked with T-Mobile SIM. Currently on QP1A.190711.020.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 3 using Tapatalk
Magisk 19.5-debd1d7d (19403) works fine with the QP1A.190711.020.C3 release. Active Edge Mod also works just fine.
thegreatone3 said:
I just got a small update. Unlocked with T-Mobile SIM. Currently on QP1A.190711.020.
View attachment 4826909
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
Metoo
1.3gb update on Rogers in Canada
Also got the patch (2.4MB) to version QP1A.190711.020.C3. Seems like they patched something serious otherwise they'd probably postponed it till the October update which only a few days to go.
Coming from Beta6, then A10, I didn't see any changes so far ( e.g. had 4G/4G+ instead LTE already displayed before the patch like some folks mentioned).
yeah I got this update on vodafone/uk saying I can upgrade to the new android 10, but I was confused as I thought I already had android 10 installed. anyway, installed a massive update and can't see anything different. Definately wasn't on any beta scheme. very odd.
and now for some reason, my windows 10 doesn't "see" my pixel, pixel can't see pc anymore. :-/
My battery life seems to have improved quite drastically.
I also noticed my phone just 'feels' more responsive and snappier. Could it be the new kernel? Well, maybe, but I guess could also be a placebo!
My phone is still on the last version of Pie (August) as the earlier September Android 10 update would just cause my phone to bootloop. I tried flashing the factory image (flash-all.bat with "-W" removed) and also adb sideloading the OTA with both the .19 and .20 versions, both give the error "no valid slot to boot" in fastboot mode after failing.
Tried to use the new .20.C3 firmware by flashing factory image (again without wiping the phone) and tried adb sideload OTA... again caused me to bootloop. I'm not sure if there's a way around this without a factory reset...
I'm on Verizon Pixel 3. So far, I have noticed fingerprint sensor seems to be more responsive. My last couple speed test at home with satellite internet have been very good but maybe it's just a fluke. Radio strength doesn't seem better, but haven't had much chance to see strength and band hand off while traveling Eastern Tennessee. I do know that Verizon grossly exaggerates their coverage map looking at their claim using putting in your location per their website.
Battery feels better and the keyboard seems much more fluid. In fact I'm seeing better frame rate on lots of the heavier animations.
I flashed the Android 10 .019 file at the beginning of the month, no issues, I'm on Google Fi. Since I'm on version .019 I'm wondering if I should flash the 020.C3 update or just wait until the October update...
Has anybody out there on Fi Network flashed the new .020.C3 file?
jetfin said:
I flashed the Android 10 .019 file at the beginning of the month, no issues, I'm on Google Fi. Since I'm on version .019 I'm wondering if I should flash the 020.C3 update or just wait until the October update...
Has anybody out there on Fi Network flashed the new .020.C3 file?
Click to expand...
Click to collapse
I'm on Fi and although I didn't flash the update, I woke up to the new update. I don't seem to see anything different. We'll see.
Full big 1.3 GB on top of my Sep 1 Android 10 update. T-mobile in the U.S. Phone re-booting now...
Just got the OTA offer:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice. I'm assuming you have the unlock version. Still waiting on my TMobile variant
Nope, I'm locked/branded.
Scratchling said:
Nope, I'm locked/branded.
Click to expand...
Click to collapse
Now i'm on my pc, i can see your signature. looks like your version of the phone has a lot options in stock recovery than the one i'm seeing. I have the tmobile variant (also know as Tmobile Revvl 5g) in US, the recovery is stripped down more. Hopefully Tmobile would push out the update.
Anyway you could provide the files for this ota or pull it somehow?
ᐯerified Developer said:
Anyway you could provide the files for this ota or pull it somehow?
Click to expand...
Click to collapse
I've not installed it yet and was mulling over doing just that.
Suggestions? I assume it's retrieved by a system app so for the most part out of reach.
Update: Think I got it.
Sweet let us kno thats great. fingers crossed
2.83GB
https://mega.nz/file/pLpS1BqS#SyRbjoVrnnOJUQidxgxi9An1JSTzwqKvsxVBkOf9zVU
Code:
ota-property-files=metadata:69:392
ota-required-cache=147714048
ota-type=BLOCK
post-build=TCL/T790Y_EEA/Seattle:11/RKQ1.201004.002/2CBB:user/release-keys
post-build-incremental=2CBB
post-sdk-level=30
post-security-patch-level=2021-01-01
post-timestamp=1610543613
pre-build=TCL/T790Y_EEA/Seattle:10/QKQ1.200329.002/1AIB:user/release-keys
pre-build-incremental=1AIB
pre-device=Seattle
Il see what i can do with this thats great thank you mind tellin me how you pulled this url so i can attempt when verizon releases it?
Thank you for posting I just downloaded to look around the zip file. Has anyone here figured out how to correctly extract the OTA Firmware boot.img from boot.img.p file and try to patch with Magisk? 7z opens the boot.img.p as an archive. When running the file in magisk it does not recognize it.
Loosin hope on this phone so far no root .. the potential this phone could be doin if it was ... Just a shame smh tcl
nice
ᐯerified Developer said:
Loosin hope on this phone so far no root .. the potential this phone could be doin if it was ... Just a shame smh tcl
Click to expand...
Click to collapse
Yeah. Without the software support, hardware is meaningless.
Can you get the ota rom about TCL10 pro?
top170 said:
Can you get the ota rom about TCL10 pro?
Click to expand...
Click to collapse
Good question, it might be possible.
Issues I've had with 11:
- YT Music sometimes thinks its offline, only started when I installed 11 and its definitely not offline.
Another bodge I've had to do is disable absolute volume due to a BT speaker but thats the speakers fault (lowest gain is too high).
OTA released, Jan 2021 to May 2021 PL.
Received the OTA for Android 11 this morning (T-Mobile Revvl 5G variant)
Also received this OTA on both of my Revvl 5G devices. Getting the gut feeling it might shave an hour of SOT off, but didn't have enough time with 10 to properly compare (the OTA auto-installed). Didn't note any major differences/issues with the update otherwise.
To update. Compared against the 6B6XUMX1 that the device shipped with, the Android 11 OTA drained 10% overnight and reduced SOT a measured 2h. This is with a fresh wipe and minimal app reinstall. I'd avoid for now.
So Im on global (CPH2415) I just downloaded the downgrade package for global used it so back on Android 12 then I shut off auto updates and waited for the next day I checked oxygen updater and seen a update for (CPH2417) that was over 4GB so I let it download after saving the file and it let me use the system update app by OnePlus to upgrade into 2417.(if you need me to explain in more detail or tell you exactly how I did it just message me in private message)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
its about time. I was stuck on 2415EU version and now I'm back on 2417NA!
tdamocles said:
its about time. I was stuck on 2415EU version and now I'm back on 2417NA!
Click to expand...
Click to collapse
You got it downloaded and flashed back?
AkayamiShurui said:
You got it downloaded and flashed back?
Click to expand...
Click to collapse
Yes
tdamocles said:
Yes
Click to expand...
Click to collapse
Glad to hear it
Finally! That took forever. I'm flashing back to 2417 currently now as well.
AkayamiShurui said:
So Im on global (CPH2415) I just downloaded the downgrade package for global used it so back on Android 12 then I shut off auto updates and waited for the next day I checked oxygen updater and seen a update for (CPH2417) that was over 4GB so I let it download after saving the file and it let me use the system update app by OnePlus to upgrade into 2417.(if you need me to explain in more detail or tell you exactly how I did it just message me in private message)
View attachment 5780425
Click to expand...
Click to collapse
Is this for the T-Mobile version and what version of Android is it .I have model 2419 and when I try to update my phone or swap to anything but Global Android 12 my apps lock up and says contract phone error and my apps are disabled.
RomLord14495 said:
Is this for the T-Mobile version and what version of Android is it .I have model 2419 and when I try to update my phone or swap to anything but Global Android 12 my apps lock up and says contract phone error and my apps are disabled.
Click to expand...
Click to collapse
How to change regions on Oneplus 10T 5g via Update/Downgrade Packages:
(Moderators, please make this post a sticky, and i will keep it updated of any changes or issues that might come up in future builds, thanks) To clarify things.... I am the dude who figured out how to side-step from model to model... I have...
forum.xda-developers.com
RomLord14495 said:
Is this for the T-Mobile version and what version of Android is it .I have model 2419 and when I try to update my phone or swap to anything but Global Android 12 my apps lock up and says contract phone error and my apps are disabled.
Click to expand...
Click to collapse
So sadly I have had time to look up into the T-Mobile version so that is something I'm a lot of information for but a limit opposed to you that talks about that so hopefully that helps
I am currently on CPH2417_11_A.08 and I want to only go to A.13.. I DO NOT want to update to Android 13 (C.22).. but I cant seem to find this anywhere.. any ideas?
Oppo/Oneplus are systematically scrubbing all traces of the older OTA fw from all the known sites. This is why i havent made any updates to that thread for doing region swaps. My instructions still stand firmly for how its done and whats required, but now its kinda on a peer to peer basis, cuz all the OTA links that are now available anywhere have a new signature check that will make the fw not appear or fail flashing if you try them. But the steps still work... and Creeper36, if you came from a T-mobile original device, you do not want to take that next upgrade ... you CAN go up to A.12 and you will get your 5g , wifi calling, and volte all working... but anything A.13 and above will lock up all your apps and the only way to get the phone working again, is a factory reset, and a rollback. Some security function has been activated that can detect you original device fingerprint, and if you are on ANY fw other than a 2419 build, it triggers the app lock.
Im still working on finding out what needs to be removed from the CarrierDevicePolicy so that this doesnt happen, but i need root access to make progress, and i am on one of the newer 10T that have the Fastboot Protocol disabled. My advice would be to just search thru the oneplus community pages or go to the telegram/discord channels... both are user operated, so you can message someone or just ask the group for the file you want and chances are someone has it, who can help you. I have A.15 but its for the 2415 build. All the fw you find below that version on the common sites (gsm mafia... etc) are packages you will need the msm tool or qfil to flash.
Does this mean I can pull boot from this and finally bl unlock/root my 2417 on Android 13?!
Can someone explain me what is the difference between 2415Global and 2417NA versions of OOS? What is good and of course what is bad? I just flashed my ACE PRO to Global 2415 want to know if it is worth to change to 2417NA? Thanks in advance