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
Related
This is the Pixel 2 XL's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Cant wait to try it
Toejam1998 said:
Cant wait to try it
Click to expand...
Click to collapse
Tell me if it's work for you
I'll wait for a few others as well
Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly
does this do the critical unlock as well?
razgriz1234 said:
does this do the critical unlock as well?
Click to expand...
Click to collapse
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
mauronofrio said:
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
Click to expand...
Click to collapse
ok cool thanks for the quick reply
razgriz1234 said:
ok cool thanks for the quick reply
Click to expand...
Click to collapse
I saw now that i forgot to unlock the flash factory image option for all 4 Pixel, i have released an update to solve that, tell me if it works
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
jaythenut said:
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
Click to expand...
Click to collapse
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
mauronofrio said:
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
Click to expand...
Click to collapse
Yes mate
jaythenut said:
Yes mate
Click to expand...
Click to collapse
People like to see feedback and in this thread this is the first
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
I think way early on it was established we can't have it unencrypted once the OS install it's completed, unless something changed or I got it wrong. Lol
almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
mauronofrio said:
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
Click to expand...
Click to collapse
Grazie.
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
dricacho said:
I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
I think it too, but i don't know why.
dricacho said:
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
mauronofrio said:
I think it too, but i don't know why.
Click to expand...
Click to collapse
The device is very expensive, has dual partitions, has gotten a lot of bad press, and not near as Dev friendly as some others. Having said that, there are about 5 custom roms, root, exposed, substratum, and various launcher and active edge mods. So it's not like we're hurting too bad ??
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
{
"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"
}
LineageOS for Google Pixel 6 Pro[raven]
What is this?
We all know what LIneageOS is, The backbone to most custom android development with a tremendous list of supported devices
Whats working?
Everything I believe
Known issues
Not sure, none so far
DON'T FLASH GAPPS, IT IS ALREADY INCLUDED
Download
Install instructions
From custom recovery
** If not already installed, please download vendor_boot.img & flash via fastboot ( fastboot flash vendor_boot "location to downloaded file" ), then select boot recovery in fastboot after flash in finish.
vendor_boot.img
1. Factory Reset
2. Apply Update via ADB, sideloading the downloaded file
3. Reboot to system
DO NOT USE THE PIXEL LAUNCHER, USE TREBUCHET
Donate
Not needed but always welcomed
Keep in touch
Twitter
Reddit
Android OS version: 12.1
Kernel Source
alvin14 said:
LineageOS for Google Pixel 6 Pro[raven]
Click to expand...
Click to collapse
Any screenshots of settings etc.
Stock kernel or in-built custom?
Texan1 said:
Any screenshots of settings etc.
Stock kernel or in-built custom?
Click to expand...
Click to collapse
Prebuilt
When I attempt to flash your vendor_boot and then boot to recovery, I get stuck at a Google logo and then my phone reboots. Why?
EDIT: I had to extract the vendor_boot.img and boot.img from the Lineage ZIP to get a working recovery.
neelchauhan said:
EDIT: I had to extract the vendor_boot.img and boot.img from the Lineage ZIP to get a working recovery.
Click to expand...
Click to collapse
Would you mind outlining the exact steps you took to flash the rom as I'm a bit confused by the OP, thanks.
I've been using this ROM since yesterday and noticed one somewhat serious bug: touch and hold doesn't work near the screen edges (~1cm) after subsequent screen unlocks. It only works on the first unlock after booting.
Touch and hold worked on the edges before I flashed this ROM. I am using Magisk so should I try without it?
EDIT: Incoming calls also doesn't work on T-Mobile US, when it does on both ProtonAOSP and GrapheneOS. Outgoing calls works fine.
I get an error that says "Carrier settings has crashed". As much as I love LineageOS, I probably will have to flash another ROM for the time being.
Texan1 said:
Would you mind outlining the exact steps you took to flash the rom as I'm a bit confused by the OP, thanks.
Click to expand...
Click to collapse
You need to extract the payload from the OTA. Use a payload extractor, and then use the boot.img and vendor_boot.img from that.
when attempting to flash adb sideload gets hung up at 2% and one time 16%.
EDIT: upon restarting windows and trying brand new usb cord and different slot, i got the 47% and its just stuck there however the underline is still blinking.
EXTRA EDIT: nvm it finally decided to flash xD excuse me and my nonsense.
So looks like this isn't stable enough yet as a daily driver?
so far no issues except the holding on the edges. i have had that when trying to delete a message but a simple restart fixes that
Texan1 said:
So looks like this isn't stable enough yet as a daily driver?
Click to expand...
Click to collapse
Texan1 said:
So looks like this isn't stable enough yet as a daily driver?
Click to expand...
Click to collapse
I've actually been using it today as a daily driver and have came across a few issues such as the phone hanging for a few seconds when making an outgoing call or when receiving calls it'll send them to voicemail The Edge just seems to be an issue sometimes battery life is good with stock kernel.
Another weird quirk I was having. I was in my discord and we were all talking about pizza so I went to go order Domino's and remembered I didn't have the Domino's app and whatever reason could not find the Domino's app on the Google Play store nor could I find DoorDash but going back to derp fest I was able to go ahead and download those apps so I'm not sure if the Google Play store is from a different country? I'm not sure if that is even possible but yeah that was an issue I had last night.
Twiggy000b said:
Another weird quirk I was having. I was in my discord and we were all talking about pizza so I went to go order Domino's and remembered I didn't have the Domino's app and whatever reason could not find the Domino's app on the Google Play store nor could I find DoorDash but going back to derp fest I was able to go ahead and download those apps so I'm not sure if the Google Play store is from a different country? I'm not sure if that is even possible but yeah that was an issue I had last night.
Click to expand...
Click to collapse
Same I just tried to download the same apps and they're not available maybe this ROM is built the first specific country, charging is extremely slow for me...
That's what I was saying
I don't want to needlessly promote my post, but I have another LineageOS 19 build which is more stable: Link here.
My build also supports the regular Pixel 6, but I don't have access to one.
It does not include GApps, but GApps can be installed, and has far fewer issues. The only issue being that screen edges may not work with long press (which this ROM also suffers from).
No need for shameful posting, you're doing great work!
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.
We don't recommend installing this on your main device, and especially if you're not familiar with development or alpha/beta testing. There are quite a few known issues right off the bat:
{
"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"
}
Developer Preview 1
WLAN malfunctions in certain scenarios
Connection fails when casting to a TV display
Red screen is seen when switching from Guest mode to Owner mode in certain scenarios
Manual connection fails after the phone is disconnected from the tablet
WeChat calls may not ring with Bluetooth headsets
Red screen flashes when creating a new calendar
Screen freezes when taking picture with the front camera in WhatsApp
Which devices support the preview?
OnePlus 11 (all variants except carrier-branded e.g. TMO/VZW)
Where can I get the preview?Before installing, be aware that installing a developer preview carries a risk of bricking your phone. Make sure you know what you're doing, and backup your files/media before proceeding. Also ensure your battery level is at least 30% and you have at least 5GB space left on your device.
Refer to the forum threads for more information:
OnePlus 11:
Developer Preview 1
Can I revert to the stable version of OxygenOS?Yes, please read the forum thread of your device as linked above for detailed instructions. Rolling back will completely wipe all your data, so please take a backup before proceeding.
Below is the rollback/downgrade packages for the OnePlus 11. Make sure you choose the correct rollback package for your device and region. We are providing these links purely for your convenience, as rolling back isn't natively supported by our app. After downloading the correct rollback package, move the file from the "Downloads" directory to the topmost directory of internal storage (the same directory that the "Downloads" folder is in). You may also have to rename ".jar" to ".zip".
Then, open Settings -> About device -> Version and tap "Build number" 7 times. This will enable Android's built-in "developer mode" (you might have to enter your phone's PIN/password too). Once this is done, "Local upgrade" will once again be visible in Settings -> About device -> Software update -> top-right button. It it doesn't show up, download & install OPLocalUpdate_For_Android13.apk, and use that to install updates locally.
Rollback packagesThe following packages will rollback your device to Android 13, and will wipe all your data. Note that these rollback ZIPs will take you back to A.09 even though the latest OOS13 stable version at the time of writing is A.10. These are not the packages you should download if you're looking to update to Android 14/U.
OnePlus 11 / Rollback packages :
OnePlus 11 NA Version (A.09)
OnePlus 11 IN Version (A.09)
OnePlus 11 EU Version (A.09)
OnePlus 11 GLO Version (A.09)
Thumbnail and image credits: Google/AOSP/OnePlus
Source: Oxygen updater/OnePlus firum
Rollback packages can be very helpful to convert CN Modele to IN, EU or GLO and also to be flashed to solve softbrick devices.
Init_boot_CPH2449_Android 14_DP1
Steve0007 said:
Init_boot_CPH2449_Android 14_DP1
Click to expand...
Click to collapse
do you think flashing 2449glo on my 2451 would change it to a 2449glo? or is it just the reverts that work like that?
kevp75 said:
do you think flashing 2449glo on my 2451 would change it to a 2449glo? or is it just the reverts that work like that?
Click to expand...
Click to collapse
The rollback packages are very fresh, so untill someone try, it is difficult to say.
But theoretically it could work. At least with 2551 you will be able to get full OTA updates
Steve0007 said:
The rollback packages are very fresh, so untill someone try, it is difficult to say.
But theoretically it could work. At least with 2551 you will be able to get full OTA updates
Click to expand...
Click to collapse
exactly what I was thinking lololol
In the meantime... here's CPH2451 A14 Stock and Magisk Patched init_boots
@Steve0007
Could you please rename the topic to something more understandable and manageable?
E.g. "Android 14 beta 1 (DP) for OnePlus 11"
I don't understand why you called it "Google 14" - it just makes no sense.
Thanks.
Hey finally I can convert my phone back to the US firmware.
My OP 11 is stucked/rebooting in fastboot mode after flashed 14 beta EU. Booting to black screen. Can reboot to fastboot mode.
Tried to repaired via Fastboot Enhance and roll back package with no success.. I have to ignore some partinations. Any solutions?
lassetth said:
My OP 11 is stucked/rebooting in fastboot mode after flashed 14 beta EU. Booting to black screen. Can reboot to fastboot mode.
Tried to repaired via Fastboot Enhance and roll back package with no success.. I have to ignore some partinations. Any solutions?
Click to expand...
Click to collapse
Try switching fastboot slot. This fixed for me, although it will take you back to a13
JPower123 said:
Try switching fastboot slot. This fixed for me, although it will take you back to a13
Click to expand...
Click to collapse
Thanks, fixed!
cabagekiller said:
Hey finally I can convert my phone back to the US firmware.
Click to expand...
Click to collapse
what are/were you on for firmware?
Steve0007 said:
The rollback packages are very fresh, so untill someone try, it is difficult to say.
But theoretically it could work. At least with 2551 you will be able to get full OTA updates
Click to expand...
Click to collapse
mmm... 2451 only gets incrementals. I'm testing the 2449 A.09 downgrade right now
kevp75 said:
mmm... 2451 only gets incrementals. I'm testing the 2449 A.09 downgrade right now
Click to expand...
Click to collapse
Steve0007Welp... I can confirm.
The downgrade for CPH2449 GLO for my CPH2451 US boots.
Tested: calls, texts, wifi, camera, bluetooth, etc... all work fine.
About to root, and then upgraded to A.10
kevp75 said:
Steve0007Welp... I can confirm.
The downgrade for CPH2449 GLO for my CPH2451 US boots.
Tested: calls, texts, wifi, camera, bluetooth, etc... all work fine.
About to root, and then upgraded to A.10
Click to expand...
Click to collapse
Rooted fine, and upgraded to A.10 fine... (and now I have a full OTA package! lololol)
kevp75 said:
Rooted fine, and upgraded to A.10 fine... (and now I have a full OTA package! lololol)
Click to expand...
Click to collapse
Yep, as we thought
Hi, a stupid question, will running the downgrade from color os directly works fine? ;-D
t0ng00 said:
Hi, a stupid question, will running the downgrade from color os directly works fine? ;-D
Click to expand...
Click to collapse
Most probably yes if you want to go back to Color os. There is already an Android 14 DP 1 available.
Steve0007 said:
Most probably yes if you want to go back to Color os. There is already an Android 14 DP 1 available.
Click to expand...
Click to collapse
Sorry for not making myself clear, I mean, downloading the apk from the forum and take it to a CN color os device and forcefully "downgrade" it to the 13 ROM - could it be even possible?
Or forcefully for to DP1 NA first and then, down?