It is think February security.
This file is offical release by AT&T .
SS-N920AUCS4CQA1-to-S4CQB2.zip
If you want to try use ADB push but price for this is wipe of your device.
Info :
Here is the current update: Android 6.0.1 Marshmallow
The details
Release date: March 10, 2017
Android version: 6.0.1
Security patch level (SPL): February 1, 2017
Baseband version: N920AUCS4CQB2
Kernel version: 3.10.61-8961126
Build number: MMB29K.N920AUCS4CQB2
File size: 167MB
Previous version required: N920AUCS4CQA1
The updates
What's new: Android device security updates
This is amazing so many viewers and just one "thank you". I see how hard is to say thank you in today's world. I'm done for searching for any more files for anybody. Do it your self. I know next one will be Nougat. Good luck.
Clicking from Edge of Galaxy
Thank you so much for taking your time to find this
jaritico said:
if i update to this version, can receive next nougat update via adb/flash? bootloader or else will not block on this update? -
using this version (outside of U.S)
{
"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"
}
Click to expand...
Click to collapse
Looks like your bootloader version is 3. New one is 4. But we have you can Odin files with v4 bootloader. So I will say yes you will get ADB or Odin files to go back or update.
Clicking from Edge of Galaxy
jaritico said:
No future problems will there be risks to upgrade to nougat using the updated bootloader?
That is my current concern, that in the future v4 will not be able to upgrade to nougat via abd or odin (I do not know which one to choose)
Click to expand...
Click to collapse
V4 is current official AT&T bootloader for Note 5. You will be able to update if you are on V4 bootloader.
jaritico said:
got it, what is the best way to update my PHA to QB2? i wanna preserve my data (Let adb as the last possibility), i am new can explain me? thanks
Do you think it is better to wait for the next update of nougat (adb or else method)? It's what I prefer
Click to expand...
Click to collapse
If you ADB you wippe your data. I would wait for official release.
Clicking from Edge of Galaxy
jaritico said:
make a backup on Smart Switch of all content, can be restored after do this as if nothing happened
Click to expand...
Click to collapse
Only a Nandroid backup can be THAT good (on other rootable phones). With Smart Switch backups, I lose saved game data and other application data.
My device is still on CPHA or september 2016's patch. Can I go to this february update via adb sideload without updating the patch before this? I live outside US region
No. You need to update one by one
Clicking from Edge of Galaxy
redklaver said:
My device is still on CPHA or september 2016's patch. Can I go to this february update via adb sideload without updating the patch before this? I live outside US region
Click to expand...
Click to collapse
No. You need to update one by one
Clicking from Edge of Galaxy
norbarb said:
No. You need to update one by one
Clicking from Edge of Galaxy
Click to expand...
Click to collapse
Thank you, mate.. do you have patch all the way back from after the CPHA?
I just got this update OTA last night. This is what I was waiting for since I want to wait until the Nougat update to factory reset again. Seems good so far but haven't had it long enough to find major differences.
mattern1974 said:
I just got this update OTA last night. This is what I was waiting for since I want to wait until the Nougat update to factory reset again. Seems good so far but haven't had it long enough to find major differences.
Click to expand...
Click to collapse
Yes it is official release as of March 10
When does Android N update conning out
vasiaua said:
When does Android N update conning out
Click to expand...
Click to collapse
Yeah right.
Sent from my SAMSUNG-SM-N920A using Tapatalk
vasiaua said:
When does Android N update conning out
Click to expand...
Click to collapse
Not in next month, I don't see anything on At&t servers yet.
Clicking from the Edge of Galaxy
norbarb said:
Not in next month, I don't see anything on At&t servers yet.
Clicking from the Edge of Galaxy
Click to expand...
Click to collapse
What are you using to browse AT&T servers?
dezborders said:
What are you using to browse AT&T servers?
Click to expand...
Click to collapse
I'm sorry but I choose not tell anymore. Last time I share AT&T block access. I check servers every 2-3 days, when I find something I will share.
Clicking from the Edge of Galaxy
best way to upgrade from LMY47X.N920AUCU2APB2 to MMB29K.N920AUCS4CQA1
Hi,
Thanks a ton for the update!! I have a at&t note-5 being used on t-mobile and is currently on build number:LMY47X.N920AUCU2APB2(mar 2016 update) and I was wondering as to how to upgrade to the latest version MMB29K.N920AUCS4CQA1. Since I can't get my hands on a at&t sim I will need to update it manually. Could anybody please guide me as to what is the best way to get to the latest version. I did search the forum but there seem to multiple and sometimes confusing ways so wanted a little clarity on that. Thanks in advance!!
You can ODIN from your desktop PC directly to *****PK1
After that, you would then use ADB from your desktop PC (USB debugging enabled) to sideload the subsequent updates to your device as Nobarb suggested. However that last step would wipe your device (so a backup will be necessary).
I'm in the same boat as you are, so I'm just waiting for the next official update (or something flashable in ODIN to get me back up to date)
Related
There are so many threads and posts raging about "where is my 5.01 update" and "its past Dec 15, it should be here..." I figured I'd start a new post, rather than post this same stuff in many threads for others to see.
Well, reading the thread on Moto's site, and a few threads on XDA, it appears things have changed.... Here is the latest Based on threads/posts.
Google, Not Moto is pushing the update. (Per Matt, moderator of Moto's own forums)
Moto had posted a schedule and information on their internal forum saying that Android Wear 5.01 Build number: LWX48P was coming and would be pushed to 100% by 12/15/2015. See -> https://forums.motorola.com/posts/03d71d8377
Here we are Dec 16, and many still don't have it.
Before the 15th, there were posts from some who received LWX48P also getting "a second update."
Posted more recently are reports of Build LWX48T on their 360, including -> https://forums.motorola.com/posts/03d71d8377?commentId=852559#852559
Now there are posts that yes, the "second update" is LWX48P to LWX48T
See... http://forum.xda-developers.com/showpost.php?p=57531050&postcount=28 and http://forum.xda-developers.com/showpost.php?p=57532096&postcount=32 and http://forum.xda-developers.com/showpost.php?p=57537294&postcount=34
This would imply that the rumors of a bug being found, halting the roll out, and the roll out re-starting, could possibly be correct.
As I posted in another thread... I guess we'll have to start the waiting game over again.
Unknowns at this point...
What will happen with the roll out Now?
Will the remainder of the 48P roll out be scrapped in favor of sending a single push directly to 48T to those still on AW4.4w2? How would this impact the time table?
How soon will those on 48P get the update to 48T?
How soon will those still on AW4.4W2 get updated to AW5.01?
Take away child's toy and announce an update to an adult seems to have the same ending.
I just had an update from the xp to XT version
My trick to update has always been this..
1. Charge watch full battery
2. Restart watch, connect to phone
3. Check for update... It says up-to-date
Go to android wear app... Make it to "forget moto 360"
4. Re connect phone to watch
5. Check for update
Downloading...!!!!!
Sent from my SM-N910C using Tapatalk 2
The original post on Moto's forum -> https://forums.motorola.com/posts/03d71d8377 has been updated.
It now reflects Build number: LWX48T
And the schedule has been replaced with...
Rollout Schedule
Users will not be able to force an upgrade out of turn
Edited: Removed detailed rollout schedule. All Moto 360 users should receive the update by the end of this week.
[*]The new version is LWX48T
Click to expand...
Click to collapse
OMG these silly tricks!!! :fingers-crossed:
I got the update on thursday (im in la). yesterday at 635pm pacific i saw another update on the watch face. the watch was around 60 ish % charge. i just happened to glace at my arm and saw the update.
i was like huh? another one?
i quickly charged it up, and proceeded with the update.
never even had to do any of these tricks. the "trick" is to be patient.....
pakure said:
I just had an update from the xp to XT version
My trick to update has always been this..
1. Charge watch full battery
2. Restart watch, connect to phone
3. Check for update... It says up-to-date
Go to android wear app... Make it to "forget moto 360"
4. Re connect phone to watch
5. Check for update
Downloading...!!!!![emoji14][emoji14][emoji14]
Sent from my SM-N910C using Tapatalk 2
Click to expand...
Click to collapse
Tried that twice and it didn't work for me.
Reset trick worked for me
Here, pulled the LWX48T update.zip from my device.
https://mega.co.nz/#!dNBnyT7Q!qtPkmgOV-jrajJAAKDLE6cQWVHyDGi3OsEwmTq5jfOU
shabbypenguin said:
Here, pulled the LWX48T update.zip from my device.
https://mega.co.nz/#!dNBnyT7Q!qtPkmgOV-jrajJAAKDLE6cQWVHyDGi3OsEwmTq5jfOU
Click to expand...
Click to collapse
Any way to flash this without hacking together a USB cable?
TheAmazingDave said:
Any way to flash this without hacking together a USB cable?
Click to expand...
Click to collapse
nope, need root in order to force an ota.
shabbypenguin said:
nope, need root in order to force an ota.
Click to expand...
Click to collapse
Ok, thanks for the quick reply. If I can grow some bigger cajones before I get an OTA, I may have a go at it.
TheAmazingDave said:
Ok, thanks for the quick reply. If I can grow some bigger cajones before I get an OTA, I may have a go at it.
Click to expand...
Click to collapse
SMH.... is Cojones !
Cajones are boxes lol
chaco81 said:
SMH.... is Cojones !
Cajones are boxes lol
Click to expand...
Click to collapse
Don't be sexist, the amazing Dave might be a girl, in which case it would be correct
Sent from my Nexus 6 using XDA Free mobile app
compuw22c said:
Don't be sexist, the amazing Dave might be a girl, in which case it would be correct
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
{
"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"
}
LOL
It's been a looooong time since High School Spanish classes... Mah bad...
marctronixx said:
OMG these silly tricks!!! :fingers-crossed:
never even had to do any of these tricks. the "trick" is to be patient.....
Click to expand...
Click to collapse
Spoken like a true Jedi. Like Yoda. Then again, I guess he would have said, "To be patient...the trick is."
TheAmazingDave said:
Ok, thanks for the quick reply. If I can grow some bigger cajones before I get an OTA, I may have a go at it.
Click to expand...
Click to collapse
I'm pretty sure I've seen you do more amazing things....
shabbypenguin said:
nope, need root in order to force an ota.
Click to expand...
Click to collapse
You Rock!! Thanks
Colchiro said:
I'm pretty sure I've seen you do more amazing things....
Click to expand...
Click to collapse
I've been working on making a digital info display for my 71 Bug using an Arduino. So this isn't entirely out of my realm.
I guess I'm more concerned with breaking the seal on the watch to get to the pins.
Just as a quick update, what i had to do to get to the latest version:
Flashed back to 42R, did the OTA to KNX01S.
Booted to bootloader and fastboot booted TWRP, connected via adb in TWRP and followed the guide to flash 5.0
When i was done and on 5.0 i then repeated with the 5.0.1 update
If you are rooted the update will fail, this allows a "temp" root to allow you to write to /cache and force teh update.zip without breaking the update process. Once you are on 5.0.1 you can flash TWRP and teh supersu package from my twrp thread and it will root you on the latest version
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
I've heard there aren't many options because this particular model is difficult to unlock the bootloader.. however, I have managed to find someone who helped me get it unlocked and I would really like to install a custom rom on it that removes all the bloatware, removes gapps, and also gets rid of Bixby. Is there anything like this that exists for the the Samsung Galaxy S9+ SM-G965U? What would you recommend? I am also on Snapdragon 845 and Android 10 if that helps.
Thanks in advance.
EDIT: I just realized I posted in the wrong forum. I don't see an option to delete this thread so if a moderator could delete this I will post in the correct forum now. Thank you
That's the million dollar question!
sjamie said:
That's the million dollar question!
Click to expand...
Click to collapse
I take it there's nothing out there eh? So disappointing. It wouldn't be possible to install a rom for SM-G965F onto the SM-G965U would it? So long as the bootloader is unlocked, will it cause problems?
mind sharing how you unlocked the bootloader or who you had do it
Greetings everyone,
I am new to this, but, have learned a lot: and there's a lot to learn.
I have successively ROM-Ed my Phone from ATT Samsung 9 PLUS G965U (ARB7) Android 8.0 to Android 8.0 R16NW.G965U1UEU1ARBG, (My phone says SM-G965U1), using great information in the forum.
My question is in two parts, (I want to stay in Android 8);
1 - My network is in SPRINT, do I stay where I am at, for that network, or do , I ROM to SPRINT using Sprint Android 8.0.0 G965USQU1ARBG? I will need that file, if I do.
2 - I would like to get OREO 8.1 on the phone, and stop there; I like OREO 8.1 - Does anyone here, know where I can get it? And how to install in regards to the above?
Thank you..
emilienicole said:
I've heard there aren't many options because this particular model is difficult to unlock the bootloader.. however, I have managed to find someone who helped me get it unlocked and I would really like to install a custom rom on it that removes all the bloatware, removes gapps, and also gets rid of Bixby. Is there anything like this that exists for the the Samsung Galaxy S9+ SM-G965U? What would you recommend? I am also on Snapdragon 845 and Android 10 if that helps.
Thanks in advance.
EDIT: I just realized I posted in the wrong forum. I don't see an option to delete this thread so if a moderator could delete this I will post in the correct forum now. Thank you
Click to expand...
Click to collapse
mind sharing how you unlocked the bootloader or who you had do it
akhtarbalouch said:
mind sharing how you unlocked the bootloader or who you had do it
Click to expand...
Click to collapse
Yup see this thread here.
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Worked like a charm for me. It's a service you gotta pay for. I took the leap though and wasn't disappointed. They're legit.
emilienicole said:
Yup see this thread here.
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Worked like a charm for me. It's a service you gotta pay for. I took the leap though and wasn't disappointed. They're legit.
Click to expand...
Click to collapse
I second that! This worked for me too, as of this morning. But the main goal was to install something newer than Android 10 to my outdated smartphone.
Yes, it's now unlocked, rooted, on a custom kernel, with TWRP and with all possible warnings about running a modified software. But still on a stock ROM.
And now I'm puzzled - what can I do next?
Ok, I've just installed PixelExperience (https://forum.xda-developers.com/t/rom-12-unofficial-pixelexperience-plus-for-s9-s9-and-n9.4513473/) and it worked well!
I had to edit an Installer file inside the zip archive. There's a place with "assert" keyword where it compares the model/product name with "star2qltechn", and I had to modify it to "star2qlte" so that it could pass the check and continue.
Installed it through TWRP: first V4 TomKernel, then PE, then basic Gapps, and voi la!
(still need to fix Bluetooth editing some property file)
{
"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"
}
_SlaSh_ said:
Ok, I've just installed PixelExperience (https://forum.xda-developers.com/t/rom-12-unofficial-pixelexperience-plus-for-s9-s9-and-n9.4513473/) and it worked well!
I had to edit an Installer file inside the zip archive. There's a place with "assert" keyword where it compares the model/product name with "star2qltechn", and I had to modify it to "star2qlte" so that it could pass the check and continue.
Installed it through TWRP: first V4 TomKernel, then PE, then basic Gapps, and voi la!
(still need to fix Bluetooth editing some property file)
View attachment 5858359View attachment 5858361
Click to expand...
Click to collapse
Could you share the edited zip or tell me specifically where you edited?
\META-INF\com\google\android\updater-script
There's a line I edited:
assert(getprop("ro.product.device") == "star2qlte" || getprop("ro.build.product") == "star2qlte" || abort("E3004: This package is for device: star2qltechn; this device is " + getprop("ro.product.device") + ".");
Click to expand...
Click to collapse
I was able to install crdroid and pixel experience just by doing what @_SlaSh_ did I just had to modify the bluethot thingy and that was it.
Between Crdroid and PixelExperience, which one do you like more?
_SlaSh_ said:
Between Crdroid and PixelExperience, which one do you like more?
Click to expand...
Click to collapse
Well first used Pixel and the truth is good enough fluid system but I had a problem with whatsapp backups and the camera when you want to use whats web but other than that I would say that would return to it if not for that detail
Cr I changed it because of the problem of whats although the backups worked but the same problem of whats web still remains
but what I did see an improvement is that cr lets you modify issues that Pixel not as notifications, the status bar and others,
the other 2 I want to wait for a next update to test them.
Hello Vivo X80 Pro community,
I'm having issues flashing the rollback file from the Android 13 Developer Preview: https://developer.vivo.com/doc/detail?id=120
{
"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 guess is that the hyperlink is linking towards a W30 ROM instead of a W20 ROM. PD2185F_EX_A_12.0.12.5.W20.V000L1-update-full.zip.
Does anyone have a rollback file for the W20 version of the X80 Pro that they can upload to androidfilehost or Google Drive please?
I heard 12.0.11.2 is the best version to do a bootloader unlock so I'm hoping someone has this one, but right now I'll be happy just to go back to Android 12.
Thanks in advance!
it's best to write to Vivo. I couldn't find anything on the internet. Vivo linked an incorrect file.
Service Center | vivo Global
vivo provides comprehensive after-sales services and technical support for products. Check where our service centers are in your location here.
www.vivo.com
I thing the problem is you have a PD2185BF, the roll back is PD2185F....
morpheus620 said:
it's best to write to Vivo. I couldn't find anything on the internet. Vivo linked an incorrect file.
Service Center | vivo Global
vivo provides comprehensive after-sales services and technical support for products. Check where our service centers are in your location here.
www.vivo.com
Click to expand...
Click to collapse
That was the first thing I tried but I was thinking that surely someone had the ROM downloaded.
dzontra83 said:
I thing the problem is you have a PD2185BF, the roll back is PD2185F....
Click to expand...
Click to collapse
This was the A13 file I used to update successfully, so it is likely that PD2185F is my model number.
PD2185F_EX_A_13.1.8.7.W20.V000L1-update-full.zip
hamisgood said:
Hello Vivo X80 Pro community,
I'm having issues flashing the rollback file from the Android 13 Developer Preview: https://developer.vivo.com/doc/detail?id=120
View attachment 5690991
My guess is that the hyperlink is linking towards a W30 ROM instead of a W20 ROM. PD2185F_EX_A_12.0.12.5.W20.V000L1-update-full.zip.
View attachment 5690989
Does anyone have a rollback file for the W20 version of the X80 Pro that they can upload to androidfilehost or Google Drive please?
I heard 12.0.11.2 is the best version to do a bootloader unlock so I'm hoping someone has this one, but right now I'll be happy just to go back to Android 12.
Thanks in advance!
Click to expand...
Click to collapse
Try doing a reset of network only. That worked for me in the past with this issue.
diopskill said:
Try doing a reset of network only. That worked for me in the past with this issue.
Click to expand...
Click to collapse
Would you still happen to have the file you used for the rollback? I have tried to factory reset and it still did not help with the boot issue. I've also reported this to their support and they are working on a fix, but I am not sure how long it would take.
Edit - They fixed the link for the rollback file. I will now try to unlock the bootloader.
Edit 2 - I tried flashing unlocking the bootloader but it seems like it cannot be unlocked due to the June security patch. I am still hoping someone here has the 12.0.11.2 version firmware and it works to flashback...
hamisgood said:
Would you still happen to have the file you used for the rollback? I have tried to factory reset and it still did not help with the boot issue. I've also reported this to their support and they are working on a fix, but I am not sure how long it would take.
Edit - They fixed the link for the rollback file. I will now try to unlock the bootloader.
Edit 2 - I tried flashing unlocking the bootloader but it seems like it cannot be unlocked due to the June security patch. I am still hoping someone here has the 12.0.11.2 version firmware and it works to flashback...
Click to expand...
Click to collapse
Yes I have it ..
PD2185F_EX_A_12.0.11.2-BWDATA.W20.V000L1-update-full_1652274124.zip
drive.google.com
hamisgood said:
Would you still happen to have the file you used for the rollback? I have tried to factory reset and it still did not help with the boot issue. I've also reported this to their support and they are working on a fix, but I am not sure how long it would take.
Edit - They fixed the link for the rollback file. I will now try to unlock the bootloader.
Edit 2 - I tried flashing unlocking the bootloader but it seems like it cannot be unlocked due to the June security patch. I am still hoping someone here has the 12.0.11.2 version firmware and it works to flashback...
Click to expand...
Click to collapse
Did you download it?
diopskill said:
Yes I have it ..
PD2185F_EX_A_12.0.11.2-BWDATA.W20.V000L1-update-full_1652274124.zip
drive.google.com
Click to expand...
Click to collapse
Hi I just requested access! Many thanks for uploading it
Really strange, I am getting this error when trying to flash the package.. I'm gonna try to reboot to recovery and see if this can be flashed..
hamisgood said:
View attachment 5695503
Really strange, I am getting this error when trying to flash the package.. I'm gonna try to reboot to recovery and see if this can be flashed..
Click to expand...
Click to collapse
I flashed thru recovery. Only way it worked for me.
diopskill said:
I flashed thru recovery. Only way it worked for me.
Click to expand...
Click to collapse
Strange I can't flash through recovery, the only option I get is update through network.. Did u get to recover via "adb reboot recovery" or is there different recovery I need to access?
hamisgood said:
Strange I can't flash through recovery, the only option I get is update through network.. Did u get to recover via "adb reboot recovery" or is there different recovery I need to access?
Click to expand...
Click to collapse
I did a reset settings Not the erase all option. That did it for me
diopskill said:
I did a reset settings Not the erase all option. That did it for me
Click to expand...
Click to collapse
What I meant is this, I don't have the option to select the rom file apparently.
A few days ago I did have the option which is why I'm confused now
hamisgood said:
What I meant is this, I don't have the option to select the rom file apparently.
A few days ago I did have the option which is why I'm confused now
Click to expand...
Click to collapse
Oh...
I have that after every time I switch between beta and stable. Reset all settings fixes it every time.
diopskill said:
Oh...
I have that after every time I switch between beta and stable. Reset all settings fixes it every time.
Click to expand...
Click to collapse
Thanks! I will try resetting tonight or tomorrow if I have the time.
I do want to root (been using rooted Android since the Kindle Fire -> Galaxy S3 -> G2 -> V20 -> OP3T -> OP5T -> OP7T), but I seem to be surviving without root after blocking Ads through using AdGuard on private DNS settings.
Not being able to freeze apps on Titanium Backup is a bit of a pain but my banking apps work perfectly is pretty good upside.
hamisgood said:
Thanks! I will try resetting tonight or tomorrow if I have the time.
I do want to root (been using rooted Android since the Kindle Fire -> Galaxy S3 -> G2 -> V20 -> OP3T -> OP5T -> OP7T), but I seem to be surviving without root after blocking Ads through using AdGuard on private DNS settings.
Not being able to freeze apps on Titanium Backup is a bit of a pain but my banking apps work perfectly is pretty good upside.
Click to expand...
Click to collapse
I'm in the exact same boat. As you!! Nothing else to add lol!
diopskill said:
Try doing a reset of network only. That worked for me in the past with this issue.
Click to expand...
Click to collapse
Did reset network, all settings, but nothing helped
After I try to install A13 zip and failed of course I am receiving notification for a new version. I install this version and after another failed try of A13 is giving me the same version to download and install. And this is every time I try to install A13 I get PD2185F_EX_A_12.0.13.1.W30.
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