HTC 10 updates thread - HTC 10 Guides, News, & Discussion

For HTC 10 please put any information you have here regarding updates.
update includes improvements for the camera http://www.smartphonesupdates.com/unlocked-htc-10-update-currently-rolling-u-s/

Just got the update myself, downloading it now
Sent from my HTC 10 using Tapatalk

Firmware Upgraded To Version 1.53.617.5.
This morning (May 10th in Northern California) my HTC 10 was upgraded to Firmware Version 1.53.617.5. After a very short test, laser focusing seems to be improved but there is still room for more improvement.

Just got mine
Sent from my HTC 10 using XDA-Developers mobile app

Willy_P said:
This morning (May 10th in Northern California) my HTC 10 was upgraded to Firmware Version 1.53.617.5. After a very short test, laser focusing seems to be improved but there is still room for more improvement.
Click to expand...
Click to collapse
This is my current Baseband..... See screenshot
Can you please post yours
My reception is unfortunately worse than my Nexus 6 was and I'm hoping it's a baseband issue
{
"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 HTC 10 using XDA-Developers mobile app

got the upgrade
with a super quick test, auto focus does seem better.

This update only for USA? I am on 1.30.401.1
Sent from my HTC 10 using Tapatalk

jcrompton said:
This is my current Baseband..... See screenshot
Can you please post yours
My reception is unfortunately worse than my Nexus 6 was and I'm hoping it's a baseband issue
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
hosmsdos said:
This update only for USA? I am on 1.30.401.1
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
The update was for the unlocked variant (617). You're both showing that you have the WWE variant (401).

Sent from my HTC 10 using XDA-Developers mobile app

may 10 update breaks autofocus
just FYI - the May 10th update brings me back to the auto-focus problem. after the update...now every time i open the camera app i get the laser-autofocus error again. it seems that it only pops up once and then goes away but i am back to this issue >-|
EDIT - so i decided to try a few things: settings -> apps -> camera: clear cache / clear data ..... reboot into bootloader, then recovery and format cache.
i received the laser autofocus error once on the first reboot and have not seen it since. Might help others if people are having similar issues. try to wipe cache first before admitting defeat! =)

no problems for me. in fact the update seems to have helped autofocus on my device a bunch. I haven't had the deal where it pulses to get focus either

No problems here either. On the contrary, the laser autofocus seems to be much more responsive for me.

jollywhitefoot said:
The update was for the unlocked variant (617). You're both showing that you have the WWE variant (401).
Click to expand...
Click to collapse
No I started out as an unlocked US variant but flashed firmware to be able to flash LeeDroid's ROM

jcrompton said:
No I started out as an unlocked US variant but flashed firmware to be able to flash LeeDroid's ROM
Click to expand...
Click to collapse
You can run LeeDroid on the 617 firmware without issue. In fact, it might be better depending on the bands that the 401 radio has available.
Edit: and seeing your original post, I wonder if your reception issue is indeed linked to you using the 401 radio. If you want I can get you the latest 617 firmware, or at least the 617 radio that you can flash.

jollywhitefoot said:
You can run LeeDroid on the 617 firmware without issue. In fact, it might be better depending on the bands that the 401 radio has available.
Edit: and seeing your original post, I wonder if your reception issue is indeed linked to you using the 401 radio. If you want I can get you the latest 617 firmware, or at least the 617 radio that you can flash.
Click to expand...
Click to collapse
You are reading by mind....... Thank you!!!!!!!!!!!!!

TBH and I have done this since my Skyrocket days everytime I OTA (bigger than 100mb especially) I always factory reset 3 times. I have never had any issues aside from issues that where present in the update itself. I tried on my note 4 to take an OTA and not factory reset and my fingerprint reader wouldnt work at all. So my advice is to factory reset. This being almost a 400MB update there are chances an app or random code is causing issues.

I would try a factory reset it sucks but a lot of times it solves problems like that
Sent from my HTC 10 using XDA-Developers mobile app

jcrompton said:
You are reading by mind....... Thank you!!!!!!!!!!!!!
Click to expand...
Click to collapse
Here is the firmware zip.
https://drive.google.com/open?id=0B8OH6sFjVE1ld1ptNTFEaEc3Rms
Can you tell me if VoLTE and call forwarding (go to settings>call >call forwarding and see if the Forwarding to numbers show up or if they all just say disabled) work for you on LeeDroid? I'm pretty sure these ATT features do not work on Lee Droid at the moment.

jollywhitefoot said:
Here is the firmware zip.
https://drive.google.com/open?id=0B8OH6sFjVE1ld1ptNTFEaEc3Rms
Can you tell me if VoLTE and call forwarding (go to settings>call >call forwarding and see if the Forwarding to numbers show up or if they all just say disabled) work for you on LeeDroid? I'm pretty sure these ATT features do not work on Lee Droid at the moment.
Click to expand...
Click to collapse
So sorry for the delay
Yes they do not work.... I kinda got the idea of that when I was setting up my Youmail app
Any work around? We should make sure @LeeDroid is aware
BTW. Should I flash this entire zip per can I just flash the radio?

jcrompton said:
So sorry for the delay
Yes they do not work.... I kinda got the idea of that when I was setting up my Youmail app
Any work around? We should make sure @LeeDroid is aware
BTW. Should I flash this entire zip per can I just flash the radio?
Click to expand...
Click to collapse
Just flash the whole thing. It won't hurt anything and you'll be more up to date than the European build.
Lee probably isn't too worried about it, US carrier support can be a pain for European devs and he hasn't implemented any carrier support yet, anyway. If I have time, I'll flash his rom again and try a couple of things.

Related

CM13.0 for LEX720 -Team Superluminal-

I want to inform people that there is another CM-13.0 available in Team Superluminal web site.
Thanks and enjoy!
Do I have to create a login to download?
Tikerz said:
Do I have to create a login to download?
Click to expand...
Click to collapse
It's worth it trust me.
ekkilm said:
It's worth it trust me.
Click to expand...
Click to collapse
Thanks. I'm about to flash it.
Update: Not flashing for me. I'm stuck at "Patching system...."
Has anyone done a dirty flash over the other CM build successfully? I'm about to give it a try.
Edit: Just flashed over the old build with no issues. Thanks!! I'll provide a screenshot once it finishes preparing the apps.
NOTE: Remember install gapps in same time with the rom (if you need/like)
NOTE2: Remember factory reset and format system partition when coming from any other ROM than previous version of TS CM13.0
tim08 said:
Has anyone done a dirty flash over the other CM build successfully? I'm about to give it a try.
Edit: Just flashed over the old build with no issues. Thanks!! I'll provide a screenshot once it finishes preparing the apps.
Click to expand...
Click to collapse
Are you using x720 or x727?
Sent from my LEX727 using Tapatalk
Had an issue with the PIN being overwritten I believe... just followed this guide and all is well again.
Edit: I'm using LEX727, about to edit build.prop again
{
"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"
}
tim08 said:
Had an issue with the PIN being overwritten I believe... just followed this guide and all is well again.
Edit: I'm using LEX727, about to edit build.prop again
Click to expand...
Click to collapse
Weird, it's not flashing for me. I'm stuck on patching system. I'm coming from stock.
I also noticed the ZIP contains firmware images. Not knowing where they're from, I'm a little worried if something goes wrong or is in compatible I can't get the x727 firmware files back.
tim08 said:
Had an issue with the PIN being overwritten I believe... just followed this guide and all is well again.
Edit: I'm using LEX727, about to edit build.prop again
Click to expand...
Click to collapse
I have seen conflicting info on this can you give me the exact edits u did to the build prop if it works please. Since you are on the 727 don't you need to flash the band 12 also?
Please read description and instructions before any steps.
It's for LEX720 and we've added LEX720 FW files in the rom also.
How to install:
NOTE: You have to have custom recovery installed, before any steps.
0) If you want to be safe: Backup apps/sms/etc with some app (e..g Titanium)
1) boot into marshmallow compatible TWRP (or similar) recovery
2) Backup -> swipe to backup
When coming from ANY other ROM than TS CM13:
2.1) Wipe -> Advanced Wipe -> Select system, data, cache and dalvik cache partition (Swipe to wipe)
3) install cm-13.0-xxxxxxx-UNOFFICIAL-le_zl1.zip (select from storage or via adb sideload) and must install gapps same time with the rom if you make clean install (if you need/like)
4) reboot
5) profit
NOTE: All changes in system partition are lost when you update ROM.
Click to expand...
Click to collapse
Followed the directions here and everything going ok for now. Restoring my apps via titanium backup.
I don't think any modem is flashed at least I haven't had any issues needing to flash the modem for band 12.
I edited "ro.product.model=LEX720" to "ro.product.model=x727" and "persist.radio.multisim.config=dsds" to "persist.radio.multisim.config=NA" but it doesn't seem to want to find the SIM card now...
Nevermind, I guess it's not intended for the X727 US version so I'll be flashing back to the old CM
the differences between cm-13.0-xxxxxxx-UNOFFICIAL-le_zl1.zip and CM13.0 for LEX720 -Team Superluminal? witch version is better?
tim08 said:
I don't think any modem is flashed at least I haven't had any issues needing to flash the modem for band 12.
I edited "ro.product.model=LEX720" to "ro.product.model=x727" and "persist.radio.multisim.config=dsds" to "persist.radio.multisim.config=NA" but it doesn't seem to want to find the SIM card now...
Nevermind, I guess it's not intended for the X727 US version so I'll be flashing back to the old CM
Click to expand...
Click to collapse
Arent they the same except for build prop and band 12? I can't make heads or tails. I thought otherwise tehy are the same.
zmanfarlee said:
Arent they the same except for build prop and band 12? I can't make heads or tails. I thought otherwise tehy are the same.
Click to expand...
Click to collapse
I thought so too but when I edited build.prop for one sim it failed to find the card and said one wasn't inserted. So I'm just gonna flash the old CM build which I know works with one sim, I could keep it on the setting for two but then it takes forever to lock on and seems to lose service.
tim08 said:
I thought so too but when I edited build.prop for one sim it failed to find the card and said one wasn't inserted. So I'm just gonna flash the old CM build which I know works with one sim, I could keep it on the setting for two but then it takes forever to lock on and seems to lose service.
Click to expand...
Click to collapse
I think the x720 firmware files has something to do with it. Hopefully when you restore the firmware files are still there from x727.
EDIT: Just thought of something, maybe flash the US modem along with doing the build.prop edit will work for this ROM on x727?
tim08 said:
I thought so too but when I edited build.prop for one sim it failed to find the card and said one wasn't inserted. So I'm just gonna flash the old CM build which I know works with one sim, I could keep it on the setting for two but then it takes forever to lock on and seems to lose service.
Click to expand...
Click to collapse
Weird when I boot it flashes a signal then sim then signal within 2 seconds and I am locked in. Weird. I did not expect this x720 vs x727 to be such a huge issue.
I installed it and will try it on lex720 for some days. The chinese one has a realy bad battery. Hope this will be better
I have it running on a US 727, it works fine, doesn't have any of the chinese junk off the other app. I don't know how to check band 12, and I'm not sure it matters in my area. Also the themer works.

[Rom].[Cook].[7.0].[G920P]-(Vien X HungPham Space Rom V1.1.1).(27/4/2017)

MOD EDIT: THREAD CLOSED AS THIS IS NOT THE OP'S ORIGINAL WORK
GALAXY S6 SPRINT G920P NOUGAT
VIEN X HUNGPHAM
SPACE ROM V1.1.1
-Rom was mod on Stock 7.0 Nougat Firmware G920P
#HOW TO INSTALL?
Uplate stock 7.0 for G920P
Download the Rom (link will be post down)
Go into recovery
Select the Rom downloaded
Flash it
Reboot
ENJOY!
- Fix auto reboot after uplate ota 7.0
- Update icon Video theme S8
- Snote
- fix google
- Delete redundant app in the system
- fix wifi hotspot
- fix Bixby
- Icon app port S8 (only icon)
- S8 widget, Launcher
- Smart Manage add More options
- fix 2K, FHD, HD
- fix, uplate SHeath
- Call recording
- Optimize system, speed up boot
link rom (old) v1: MOD EDIT: DOWNLOAD LINK REMOVED
ROM ONLY FOR G920P
NOTE: WHEN YOU TALKED THE ROM ERROR 7. LOUNGE, START RETURN, UP TO WHITE BOOT SAMSUNG IS OK, AFTER 15-20 MINUTES
ROM OS Version: 7.0 Nougat
ROM Kernel: 3.10.61
ROM Firmware Required: Latest 7.0 Firmware
Based On: Samsung Nougat firmware
Thanks: VIEN X HUNGPHAM
Screenshoot
{
"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"
}
thanks, anyone try this out yet
Thanks bro. Gonna try this out.
Sent from my SM-G920P using XDA-Developers Legacy app
2 things.
when flashed through recovery (dirty install) got a failed flashed but still loaded rom within minutes as if it was a little patch for stock. filled with new features which is great, but google apps forced closed when launched so tried to do clean install, got a failed error also and when booted couldn't seem to get passed checking network during setup. maybe because my phone doesn't have a sim cause its disconnected. overall these might just be my issues so i guarantee no one else will face these problems. not mad about it either, i like doing this. I'm going to put stock firmware, set it up again, root and flash rom and get back with you.
btw thanks for making the first sprint nougat rom. bet everyones happy.
- also keep getting google play services failed popup.
Checking Network.
I'm currently stuck in this portion of setup, and I don't know what to do.
SorryImRaymond said:
2 things.
when flashed through recovery (dirty install) got a failed flashed but still loaded rom within minutes as if it was a little patch for stock. filled with new features which is great, but google apps forced closed when launched so tried to do clean install, got a failed error also and when booted couldn't seem to get passed checking network during setup. maybe because my phone doesn't have a sim cause its disconnected. overall these might just be my issues so i guarantee no one else will face these problems. not mad about it either, i like doing this. I'm going to put stock firmware, set it up again, root and flash rom and get back with you.
btw thanks for making the first sprint nougat rom. bet everyones happy.
- also keep getting google play services failed popup.
Click to expand...
Click to collapse
NOTE: WHEN YOU TALKED THE ROM ERROR 7. LOUNGE, START RETURN, UP TO WHITE BOOT SAMSUNG IS OK, AFTER 15-20 MINUTES
Please update google latest version
alienmerc said:
i'm currently stuck in this portion of setup, and i don't know what to do.
Click to expand...
Click to collapse
note: When you talked the rom error 7. Lounge, start return, up to white boot samsung is ok, after 15-20 minutes
giaoluanawm said:
note: When you talked the rom error 7. Lounge, start return, up to white boot samsung is ok, after 15-20 minutes
Click to expand...
Click to collapse
Are you saying checking network takes 15-20 minutes?
AlienMerc said:
Are you saying checking network takes 15-20 minutes?
Click to expand...
Click to collapse
i am sorry, After you install rom then no network connection? you cant flash V1
Sorry all, I'm fixing version V1.1.1. You can install v1. And I will update v1.1.1 soonest
giaoluanawm said:
Sorry all, I'm fixing version V1.1.1. You can install v1. And I will update v1.1.1 soonest
Click to expand...
Click to collapse
Can't wait. Thanks for the update
I'm assuming you'll be fixing the issue, of having no mobile data. Right?
AlienMerc said:
I'm assuming you'll be fixing the issue, of having no mobile data. Right?
Click to expand...
Click to collapse
Is it working for you? My phones disconnected so i couldnt test mobile data. maybe someone else has data working?
SorryImRaymond said:
Is it working for you? My phones disconnected so i couldnt test mobile data. maybe someone else has data working?
Click to expand...
Click to collapse
nope data doesn't work
AlienMerc said:
I'm assuming you'll be fixing the issue, of having no mobile data. Right?
Click to expand...
Click to collapse
Mobile data still works normally, but some devices do not work with moble data. I am finding fault and how to fix it
giaoluanawm said:
Mobile data still works normally, but some devices do not work with moble data. I am finding fault and how to fix it
Click to expand...
Click to collapse
i'm excited for the update
AlienMerc said:
i'm excited for the update
Click to expand...
Click to collapse
Now, you cant flash V1(old). And can you tell me if it has moble data error?
giaoluanawm said:
Now, you cant flash V1(old). And can you tell me if it has moble data error?
Click to expand...
Click to collapse
neither version had data
AlienMerc said:
neither version had data
Click to expand...
Click to collapse
I have downloaded and installed fine
just curious, why was the link for v:1.1.1 deleted?

Lineage 14.1 hotspot error if mobile data on (logcat)

Good evening.
This is my first time posting here so hello from southeast Queensland, Australia
I recently purchased an AGM A8 4GB ram/64GB storage model. It came with a practically stock Android 7.0 with gapps preloaded. It was great to use but Firefox and Adblock browser crashed within seconds of launching, regardless of what I tried (factory reset, arm, arm64, versions between 35 and 57.0.1).
I decided to try Lineage 14.1 which is the other ROM available for this phone and Firefox finally works!
The only issue I'm having is I can't activate my hotspot unless mobile data is disabled (a string saying 'error' appears underneath the label when I switch it on).
I have searched and searched for a fix without success. I have recorded logcat to provide if that will help? Not certain what is the preferred way to share it here on XDA.
Here is how the error string appears (not my screenshot):
{
"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"
}
My phone is rooted, in case this makes implementing a fix easier.
Thank you very much for your time!
Seems device specific
Thank you for the fast reply. I don't believe this is device specific as I've seen many other phones with the same issue (Zuk Z2 Plus -snapdragon 820, One Plus 3 which I believe is the 820 again, Nexus 5 which is the snapdragon 800).
My device is using the snapdragon 410. It seems like this is a common bug with android 7.1.1 and/or lineage 14.1 and may have been introduced in android 7.1 but I'm not certain.
I did see one brief thread on XDA regarding a fix for a Nexus 6 (snapdragon 805) running 7.1.1. The recommendation was to flash ex kernel, while another person said to flash blackbird kernel. I believe kernels are device and/or SOC specific?
Thanks for your time.
Bump. Here's my logcat when I try to turn on my hotspot while mobile data is enabled. I've had to use pastebin as it's too big to post here:
pastebin dot com/pHXQKvi6
Thank You.
Have I asked for help in the wrong subforum? Perhaps somebody can recommend another forum altogether if I'm in the wrong place? Thank you
jeremyf50 said:
Have I asked for help in the wrong subforum? Perhaps somebody can recommend another forum altogether if I'm in the wrong place? Thank you
Click to expand...
Click to collapse
https://forum.xda-developers.com/ge...on/agm-a8-rugged-info-msm8916-review-t3542052
Thank you for your reply. Unfortunately that thread is closed and the OP's account is disabled. There's no relevant information to my problem in that thread but I have sent a PM to ffboy2009 in hope that he (as the AGM A8 Lineage 14 dev) can assist me with this issue. The issue isn't specific to this model, however. I will keep this thread updated.
Thank You.
jeremyf50 said:
Thank you for your reply. Unfortunately that thread is closed and the OP's account is disabled. There's no relevant information to my problem in that thread but I have sent a PM to ffboy2009 in hope that he (as the AGM A8 Lineage 14 dev) can assist me with this issue. The issue isn't specific to this model, however. I will keep this thread updated.
Thank You.
Click to expand...
Click to collapse
Yea I have the same problem
Sent from my [device_name] using XDA-Developers Legacy app
Happy new year!
Back to the thread. It has been over two weeks and I haven't received a response from ffboy2009. Can anybody else suggest how we can rectify this issue? Thanks.
Bump. Basically a month of no progress on this. There's more than one person on more than one handset effected by this!
jeremyf50 said:
I've seen many other phones with the same issue (Zuk Z2 Plus -snapdragon 820, One Plus 3 which I believe is the 820 again, Nexus 5 which is the snapdragon 800).
Click to expand...
Click to collapse
I guess I can confirm that this is not device specific, because I have a Nexus 5 (on latest lineageOS) and can confirm I do not have this problem. Then again that also confirms it's not a straight out lineageOS bug.
Have you tried the agonizing "Network settings reset" in the settings? (it is in "Wireless and settings" > "More").
Fetching far, I'm also wondering if this could be triggered by the network provider. (could the network provider in some way, maybe via APN settings, indicate to android that this is not allowed).
If the above network settings request doesn't do it yet, you could also manually go into your APN settings and try resetting those. (the 3-dot menu offers to reset them to defaults).
Also/alternatively, providers offer a way to have their APN settings sent to your phone. I guess worth a try as well. (because the APN settings lineageOS has as defaults are not necessarily the same the provider distributes)
That's all i can think of for now. good luck
Good Morning, lePoMo.
Thanks for the reply. My LineageOS version is 14.1-20170401-UNOFFICIAL-HS8939QC and the build number is lineage_HS8939QC-userdebug 7.1.1 NOF27B91eef740bf test-keys so I don't believe this is the 'final' release which others may be running. It's the latest I could find for my phone though.
I haven't heard of my provider disallowing tethering and tethering worked with the stock Android 7 ROM that the phone came with. I only changed from that ROM because Firefox and Adblock browser crashed within seconds of opening (irrespective of versions tried). The stock ROM was basically vanilla Android 7 but I'm not sure of the exact version/build.
I have tried my SIM card (provider: Telstra) in slot 2 on my phone just in case it was related to that. It's the same problem with both SIM slots. I will try another provider SIM this evening (Optus) and report back to this thread. I'll also reset my network settings and confirm the APN details. Is it just the 'Data' APN which will be relevant here and not MMS etc?
Thank You.
I have confirmed my APN settings are correct and performed a Network Settings reset. I am still experiencing the same problem. Hopefully I can test using another provider SIM card this evening.
Problem fixed. Culprit was a Magisk module.
For me the problem was solved by:-
1)Uninstall Magisk manager
2)Reboot
I have a link which explains the same.
Forum is not allowing me to post it.
I have same error and I am not sure I have Magisk.
How can I fix this error?
AGM A8 stock ROM
Guys, how do I install stock ROM back to my AGM A8. Currenty I have only TWRP available on my AGM A8, /system, /data, /cache partitions are all wiped out. I tried to install stock rom, placed a file T88Q_14.bin to phone's SDcard but when I press vol +, vol - and power button I get this message - Authority identification not found!

General 11.2.6.6 NA Rolling Out

I got the NA build for 11.2.6.6 this morning. Installed and rooted without issue via the normal restore image, update, install active/inactive method.
Not seeing it yet on oxygen updater...
I'm past ready!
galaxys said:
Not seeing it yet on oxygen updater...
I'm past ready!
Click to expand...
Click to collapse
I never use Oxygen Updater, I just got it through the normal OTA/System Updates thing.
It was released some days ago and started with IN region, below is the changelog
{
"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"
}
Still not out for EU, Why is India prioritised now? Most users?
djsubterrain said:
Still not out for EU, Why is India prioritised now? Most users?
Click to expand...
Click to collapse
Because it's the best android flagship in Indian market right now with good price.
djsubterrain said:
Still not out for EU, Why is India prioritised now? Most users?
Click to expand...
Click to collapse
There are various reasons which should not be discussed here but let me just say no 5G in India yet definitely plays a role as the builds don’t have to be certified separately with carriers if that makes sense.
Appropriately, NA = Not Available!
avid_droid said:
What does that even mean? NA? NORTH AMERICAN? Sorry to burst your bubble but try to be specific with a model or region number/code. There is no NA model in OnePlus.
Click to expand...
Click to collapse
NA stands for the Global devices (LE2125) with build tag LE15AA sold outside the below regions.
LE2123: EU is the European Version (Build Tag BA)
LE2121: IN is the India Version (Build Tag DA, generally the first to receive the update)
Chinese units (LE2120) run ColourOS out of the box.
LE2127 units are T-Mobile units running LE5ACB builds and will be the last to receive the update.
Hope this clarifies all the confusion
Could someone grab the package before it gets deleted from their phone?
avid_droid said:
What does that even mean? NA? NORTH AMERICAN? Sorry to burst your bubble but try to be specific with a model or region number/code. There is no NA model in OnePlus.
Click to expand...
Click to collapse
11.2.6.6 NA Rolling Out
I got the NA build for 11.2.6.6 this morning. Installed and rooted without issue via the normal restore image, update, install active/inactive method.
forum.xda-developers.com
I am sure you probably had an idea anyway. NA is also the common reference used by OnePlus as well.
Don't worry, my bubble is ok.
dmarden said:
I got the NA build for 11.2.6.6 this morning. Installed and rooted without issue via the normal restore image, update, install active/inactive method.
Click to expand...
Click to collapse
Is anyway you could write exact instructions please how to update the system not using full zip? I'm still on 11.2.4.4 and rooted.
netgar said:
Is anyway you could write exact instructions please how to update the system not using full zip? I'm still on 11.2.4.4 and rooted.
Click to expand...
Click to collapse
I go into magisk and choose the uninstall/restore images option.
Let system update download and install. Once it's done, I do not reboot.
I go into magisk and install to both the active and inactive slots (this works because until you reboot, you're still loaded into the OS with root).
Reboot
Hope it helps
avid_droid said:
Yeah that's still stupid because if referenced as NA the LE2127 should also be referenced the same as it is a NA model also. It's just dumb in my opinion
Click to expand...
Click to collapse
Your opinion is fine and valid, you just don't need to take it out on me is all. I forgive you.

			
				
After this update, i noted no real changes on the connectivity, still low signal, still some lags and stutter when scrolling, the camera i don't know i don't use it that much, and also still got the dead spot on touch near at the bottom ledt corner or right where the enter and the ?123buttons are on keyboard, some times i need to push 3 or 4 times for it to work, on the keyboard or even to launch an app or when using an app
BA-Version is now offered via Oxygen updater
dmarden said:
I go into magisk and choose the uninstall/restore images option.
Let system update download and install. Once it's done, I do not reboot.
I go into magisk and install to both the active and inactive slots (this works because until you reboot, you're still loaded into the OS with root).
Reboot
Hope it helps
Click to expand...
Click to collapse
U mean to install incremental update or full zip update?
As far as I know if my phone is rooted I need to install full zip update, otherwise I can screw up.
Correct me if I am wrong please
netgar said:
U mean to install incremental update or full zip update?
As far as I know if my phone is rooted I need to install full zip update, otherwise I can screw up.
Correct me if I am wrong please
Click to expand...
Click to collapse
Just the incremental update via the stock updater. That's how I always do it, it's fine.
dmarden said:
Just the incremental update via the stock updater. That's how I always do it, it's fine.
Click to expand...
Click to collapse
I thought you always need to install full zip update ones you are rooted. That's ev
dmarden said:
Just the incremental update via the stock updater. That's how I always do it, it's fine.
Click to expand...
Click to collapse
Last question...
Does the stock image boot always get restored during rooting process?
I am not sure if my stock boot image was restore during rooting.
Thank you for your help

General New A13 update for T-Mobile OP9Pro

T-Mobile has finally released the long overdue Android 13 update for the LE2127 which is called LE2127_11_F.27 and apparently the rollout has begun. I never got a push notification but I've been checking for updates for the last few days and it just finally became available this morning.
{
"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"
}
Be sure to give a concise review after you have used it for awhile please!
TheGhost1951 said:
Be sure to give a concise review after you have used it for awhile please!
Click to expand...
Click to collapse
It doesn't seem any different from the global or eu firmware. Just hopefully it doesn't come with the network issues that I had while on the global/eu firmwares, because on the F17 and F72 I had an issue where the person I was talking to couldn't hear me. Sometimes everything was crystal clear and sometimes the person on the end of the line just heard total silence.
Masterchief87 said:
It doesn't seem any different from the global or eu firmware. Just hopefully it doesn't come with the network issues that I had while on the global/eu firmwares, because on the F17 and F72 I had an issue where the person I was talking to couldn't hear me. Sometimes everything was crystal clear and sometimes the person on the end of the line just heard total silence.
Click to expand...
Click to collapse
Who is your carrier?
TheGhost1951 said:
Who is your carrier?
Click to expand...
Click to collapse
Metro/T-Mobile
I use to run custom roms years ago. But these days, from what I have been seeing, the phones work best with the firmware that matches the phone model for best operation and hassle free.
can you upload the update somewhere?
You don't download TMOA UPDATES, and trying to catch the update before rebooting is difficult.
Zeus0fyork said:
can you upload the update somewhere?
Click to expand...
Click to collapse
That's not something I know how to do, but if you msm back to stock then go through all the updates it should be available.
TheGhost1951 said:
I use to run custom roms years ago. But these days, from what I have been seeing, the phones work best with the firmware that matches the phone model for best operation and hassle free.
Click to expand...
Click to collapse
Well the consensus seemed to be that the full ota to A13 on the global and EU firmwares fixed the network issues as long as you didn't take any initial OTAs after the initial update to A13. That wasn't the case for me though.
I used to use custom roms a lot too back 5-10 years ago but now it seems everything I used to know is obsolete.
I MSM'd back to 11 and took the OTA to get to A13. It's working nicely. No more battery drain or 5G issues (losing connection, slow to connect after reboot).
Now just waiting patiently for someone to post the LE2127_11_F.27 boot.img file so that I can install MAGISK.
Nevermind, I was able to extract it via the MSM Readback method mentioned in the following post
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
weissco said:
Nevermind, I was able to extract it via the MSM Readback method mentioned in the following post
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
Click to expand...
Click to collapse
I don't know anything about using the msm tool to pull partition images from the phone, but here's the way I do know.
1. Unlock bootloader if not already unlocked
2. "fastboot getvar all" or "fastboot getvar current-slot" to see which slot is active
3. "fastboot boot name_of_twrp_recovery.img" to boot twrp recovery
3. run the "adb shell" command or launch the terminal emulator in the advanced section of twrp recovery
4. Once you've launched adb shell or the terminal run the "su" command to get root permissions
5. Use the command "dd if=/dev/block/by-name/boot_a.img of=/SD card/boot_a.img" if slot a is active, or "dd if=/dev/block/by-name/boot_b.img of=/SD card/boot_b.img" if slot b is the active slot
After a few seconds you'll have a copy of the boot image in the root of your internal storage.
Alternatively, you could just flash the latest magisk apk through twrp, but as I understand it this method is not recommended anymore, and I don't think you'd have an unaltered copy of the boot image this way.
Has T-Mobile rolled this update out in the states? It's quite the lengthy process for me to upgrade, with about 9000 apps to restore lol.
DaveImagery said:
Has T-Mobile rolled this update out in the states? It's quite the lengthy process for me to upgrade, with about 9000 apps to restore lol.
Click to expand...
Click to collapse
In in GA and got the update this morning.
mulletcutter said:
In in GA and got the update this morning.
Click to expand...
Click to collapse
Okay cool, thank you
DaveImagery said:
Has T-Mobile rolled this update out in the states? It's quite the lengthy process for me to upgrade, with about 9000 apps to restore lol.
Click to expand...
Click to collapse
I'm in FL and got it yesterday.
Masterchief87 said:
I'm in FL and got it yesterday.
Click to expand...
Click to collapse
Did you just update? or clean install? Remember coming from 11-12 it was hot garbage. Wonder if my ReVanced will get messed up.
mulletcutter said:
Did you just update? or clean install? Remember coming from 11-12 it was hot garbage. Wonder if my ReVanced will get messed up.
Click to expand...
Click to collapse
I just took the ota and haven't done a factory reset. I have noticed that the voice/data signal icon doesn't match the wifi icon. I haven't noticed any other issues yet.
I didn't think they were suppose to match since two different types of network.... Per your image

Categories

Resources