Develop Bugs

Collection of ROMs for the Flashaholics Volume 2

FOREWORD
HUGE Credit to crpalmer & BadDaemon aka Micheal W for rock-solid device tree & kernel source ... :good:
INSTALLATION
Wipe Data/ Factory Reset
Wipe System, Data, Cache, Dalvik/ Art Cache
Flash ROM <= Very important, do not reboot & proceed with the next step
Flash Gapps <= If you did then a Wipe Data/ Factory Reset will fix the FC
Finally reboot and enjoy !
* First boot may take awhile if you choose to use full Gapps, nano will do but that is entirely up to you to choose the Variant.
BUG Reporting
How to Report Bugs Effectively <= Original link from here... :good:
If you wanna help out on improving on these ROMs then install Syslog, follow the procedure here then report it directly to respective ROM Google+ with logs... :good:​
All credit goes to the ROM Developer/ ROM Development Team of the respective custom ROM... :good:
{
"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 to RD Santhosh M for recommending me to build this first awesome ROM... :good:
Temasek ROM Source
Old build EMUI 3.1 LP base Download link
ROM Preview
Final build Download Link tweet by Temasek himself
Note : Requires EMUI 4.0 MM base. If you're a Flashaholic & you couldn't wait until official updates then follow the steps at post#2
Emotion ROM Source
Download link
ROM Preview
TipsyOS ROM Source
Google+
Download link
ROM Preview
Latest updates then refer to gopinaidu77's thread... :good:
Tesla ROM Source
Google+
Download link
ROM Preview
AOSP-CAF ROM Source
Download link
Note : Requires EMUI 4.0 MM base. If you're a Flashaholic & you couldn't wait until official updates then follow the steps at post#2
ROM Preview
Latest updates then refer to gopinaidu77's thread... :good:
www.google.com => Broken OS google+ => Search Community => kiwi
Note : Requires EMUI 4.0 MM base. If you're a Flashaholic & you couldn't wait until official updates then follow the steps at post#2
ROM Preview
Updates : i really don't understand why D-FUSE came to XDA to promote it, he even hijacks one of my thread & now he deletes everything, all download links & all google+ post has been removed... If you still desperately want to try it then pm gopinaidu77
XDA:DevDB Information
[Stable] For the Extreme Flashaholics V2, ROM for the Honor 5X
Contributors
yuweng
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Stable Release Date: 2016-05-30
Created 2016-06-01
Last Updated 2016-11-29

For temasek
Those of you having random screen off/ on issue refer to this temporary fix, Thanks to gopinaidu77... :good:

Wow... such development much wow... thnx a lot bro...
Sent from my KIW-L21 using Tapatalk

What works and doesn't work?
Sent from my KIW-L24 using XDA-Developers mobile app

Presumably the same as cm-13.0... i'm a new user to this ROM too, so far tested on the telephony side (phone calls, WiFi, BT, GPS, FM) & etc, all is working though the data connection is a bit tricky, you'll have to go to Settings => SIM cards => Cellular data => select SIM1 or 2 then only LTE will work... RD Santhosh M has shared a tip, go to Settings => Spare Parts... :good: Else then it's almost the same as a stock cm-13.0 ROM....

Been using this ROM and have found that this is the only ROM I've tried that lets ALL apps write to the SD card. So, if you use Titanium backup you don't need to use your internal storage. All browsers can save to the SD card as well.

Temasek has been developing this ROM since the cm-7 days ! And he only cherry-picked only the goodies from many sources while UI stays as cm-13.0 & yet nobody is trying this awesome ROM, it has been three weeks now & the downloads is just 108 as of today...
Code:
[U][COLOR="Blue"]Features[/COLOR][/U]
Call Recording
Selinux Switcher
OnTheGo Mode
3 finger gesture screenshot
PIE
OTA's
OmniSwitch
AppBar
App Circle bar
Gestures Anywhere
Heads Up Notifications
Network traffic meter
DPI Settings
More youtube Temasek ROM feature review... :good:

I guess there are so many ROMs now, folks must be confused btw, am using your Xperiance ROM and its been amazing so far!

So many ROMs now ? There are hundreds or may be even thousands of Android custom ROMs available on github but most probably just fifty over are buildable as of today & we're not even halfway there yet... My XPerience ROM ? Nay, i'm just a ROM Cooker, the XPerience ROM belongs to TeamMex... :good: That's why it is important to feedback bugs reporting directly to the ROM DEV & not me however you can share whatever findings on that particular ROM on those threads accordingly...

Very well, I am always thankful to this xda community! Such wealth of info and dedicated folk here....kudos to all!

yuweng said:
Temasek has been developing this ROM since the cm-7 days ! And he only cherry-picked only the goodies from many sources while UI stays as cm-13.0 & yet nobody is trying this awesome ROM, it has been three weeks now & the downloads is just 108 as of today...
Code:
[U][COLOR="Blue"]Features[/COLOR][/U]
Call Recording
Selinux Switcher
OnTheGo Mode
3 finger gesture screenshot
PIE
OTA's
OmniSwitch
AppBar
App Circle bar
Gestures Anywhere
Heads Up Notifications
Network traffic meter
DPI Settings
llMore youtube Temasek ROM feature review... :good:
Click to expand...
Click to collapse
Its become my DD. I try out all ROMs but keep coming back to this one.

I don't own a Honor 5X but its in my list of options for my next phone. This ROM seems great and its sad with how open the android development world is that even a great ROM by a experienced DEV if you will has low interest. Its to bad there isn't a way to better acknowledge good ROM's vs the randomness of it all. Rom1 vs Rom2 VS Rom3 and so on. Its weird in the jailbreak world a good app/theme/tweak either crashes or burns but android well its android.

MustangLife03 said:
I don't own a Honor 5X but its in my list of options for my next phone. This ROM seems great and its sad with how open the android development world is that even a great ROM by a experienced DEV if you will has low interest. Its to bad there isn't a way to better acknowledge good ROM's vs the randomness of it all. Rom1 vs Rom2 VS Rom3 and so on. Its weird in the jailbreak world a good app/theme/tweak either crashes or burns but android well its android.
Click to expand...
Click to collapse
The fact is this phone didn't get great reviews and was a poor seller. You must remember only a very small portion of phone buyers care about rooting and roms and if the phone does not sell well it only means the number of downloads for x rom will be low as well. Same thing happened with the HTC M9, It's a great device but never sold well so the developers had very small number of followers.

clsA said:
The fact is this phone didn't get great reviews and was a poor seller. You must remember only a very small portion of phone buyers care about rooting and roms and if the phone does not sell well it only means the number of downloads for x rom will be low as well. Same thing happened with the HTC M9, It's a great device but never sold well so the developers had very small number of followers.
Click to expand...
Click to collapse
I moved from the LG G3 to Huawei 5X and truthfully much happier with this phone. A lot don't know about it, but with the custom ROMs, this phone works well. I can only imagine that the higher end Huawei's phones are impressive with custom ROMs. I will try this ROM, presently on AICP and loving it!

[9.0][Official] XenonHD [OTA][PME]

{
"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"
}
TeamHorizon's XenonHD ROM For The HTC 10 (pme)
[url]http://www.xenonhd.com/[/URL]
XenonHD is a custom firmware aka ROM for various Android devices. It is based on LineageOS 16.0 with additional features, performance and battery life improvements.
The idea behind XenonHD is to give users a ROM that is "blazing fast, rock stable and buttery smooth".
Device Source:
Device
Kernel
Vendor
Download Links:
ROM: Experimental Builds
Gapps: Open Gapps
​
Other Links:
Github
Google+
Telegram
XDA:DevDB Information
XenonHD, ROM for the HTC 10
Contributors
AnierinB, fagyi, holofractal
Source Code: [url]https://github.com/TeamHorizon[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Oreo
Based On: LineageOS, AOSP
Version Information
Status: Experimental
Created 2019-01-29
Last Updated 2019-03-03

Bugs:
*IMS - VOLTE is broken
*SlowMo doesn't work
*SeLinux permissive

Reserved

Wow a new pie rom OMG thank you! I will test this tomorrow.

I brushed running very smooth good ROM thank god

good
Dear Sir,
Thank you for rom created.
kindly please Add "Quick Unlock" Option (Unlock Automatically when the correct Pin/Password is entered.
Your ROM Very Fast and Stable. thank you so mach.

Nice work
Did anyone try it on Sprint HTC 10 S-ON Unlocked bootloader?
Edited : Booted fine on Sprint HTC 10. Testing now. Thanks for beautiful rom

b.i said:
Dear Sir,
Thank you for rom created.
kindly please Add "Quick Unlock" Option (Unlock Automatically when the correct Pin/Password is entered.
Your ROM Very Fast and Stable. thank you so mach.
Click to expand...
Click to collapse
Might be available through settings>security>gear icon
XenonHD likes to keep things neat and clean. For instance, quick setting configurations are available through the panel itself when the editor is brought up.

Hi @AnierinB,
Good to see another favourite ROM brought to our device, will try it out during the weekend and share feedback.
Thank you.
Sent from my HTC 10 using XDA Labs

Works fine
UI is good
Battery is decent
Automatic Brightness adjustment is way more aggressive
If you dont like stock , you can install Htc apps including sense home etc
---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------
Which is safe way to root this rom (without wiping data?
Thanks
Edit : rooted sucessfully

Ahmed Xperia p said:
Works fine
UI is good
Battery is decent
Automatic Brightness adjustment is way more aggressive
If you dont like stock , you can install Htc apps including sense home etc
---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------
Which is safe way to root this rom (without wiping data?
Thanks
Click to expand...
Click to collapse
Root the rom without wiping data???? Install Magisk.
Nevermind didn't see your edit. Sorry

thank you to build this i'll download it

Announcement!
I will be officially maintaining XenonHD on pme.
Well what does this mean?
• XHD Signed Builds
• OTA/Consistent updates
• ROM side support from the XenonHD telegram
Official build will be available within the next day or so. Be on the lookout for a release announcement and link to official download page

AnierinB said:
Announcement!
I will be officially maintaining XenonHD on pme.
Well what does this mean?
• XHD Signed Builds
• OTA/Consistent updates
• Support from the XenonHD telegram
Official build will be available within the next day or so. Be on the lookout for a release announcement and link to official download page
Click to expand...
Click to collapse
So the 3 things that weren't working are fixed?
Thanks for looking us out with another great ROM for our beloved HTC10s

kend0g said:
So the 3 things that weren't working are fixed?
Thanks for looking us out with another great ROM for our beloved HTC10s
Click to expand...
Click to collapse
That doesn't mean those are fixed yet, no. It just means what I've stated here in my last comment about gaining official support, signed builds and ota updates. They're experimental builds with some added perks.
Again, this wouldn't be possible without @fagyi for his trees and @holofractal (Older bro) for constantly letting me compile for pme and ether on his server.

AnierinB said:
That doesn't mean those are fixed yet, no. It just means what I've stated here in my last comment about gaining official support, signed builds and ota updates. They're experimental builds with some added perks.
Again, this wouldn't be possible without @fagyi for his trees and @holofractal (Older bro) for constantly letting me compile on his server.
Click to expand...
Click to collapse
OH. I'm sorry man. I thought I read one of his(Fagyi's) posts that said the only way most roms would let you have official support would be if SELinux had enforcing fixed. I must of been reading that from something else maybe anyway. Again I apologize.

kend0g said:
OH. I'm sorry man. I thought I read one of his(Fagyi's) posts that said the only way most roms would let you have official support would be if SELinux had enforcing fixed. I must of been reading that from something else maybe anyway. Again I apologize.
Click to expand...
Click to collapse
No need for the apology and I understand where you're coming from. Lineage OS has extremely high standards for official support granted selinux enforcing makes you're device a lot more secure than permissive. Ideally I'm sure people would want me to release official with SELinux in enforcing but as I said, these are extremental builds.
Here take a look:
https://github.com/LineageOS/charter/blob/master/device-support-requirements.md

Soon as you drop the next build I will be definitely check'in 'er out. Thanks man.

AnierinB said:
Announcement!
I will be officially maintaining XenonHD on pme.
Well what does this mean?
• XHD Signed Builds
• OTA/Consistent updates
• ROM side support from the XenonHD telegram
Official build will be available within the next day or so. Be on the lookout for a release announcement and link to official download page
Click to expand...
Click to collapse
awesome job man!

After 2 days of testing here is my feed back
Battery : Good ( Better than Leedroid and official oreo. I get around 4 hrs SOT with 15-16 hrs of stand by)
Camera : Stock camera app is average. Gc cam port of pixel 3 works fine you can increase saturation level and picture will be great. Portrait mode works fine
Heating : Yes but much less than official oreo
Signals and call quality : Much better than leedroid and official oreo. On leedroid and official oreo siganl reception was just pathetic and inside basements etc it would go for emergency calls. I am using gsm auto in network setting. Since i am on Sprint Unlocked device 4G Lte doesn't work and i get only H plus. I tried erasing modemst fix which is posted in some other thread but did not wok, may be because of S-on i am unable to erase modem st. If somebody posts how to fix it with S 0n i would really appreciate it.
Automatic screen brightness is not working as it should, sometime it'll go all the way up up in low light and outdoors it'll stuck at lower level despite being in sun light
After 2 days i have started experiencing slight slutter and lag
Overall a good , beautiful and customisable rom

[CLOSED][TOOL] [9.0/10.0] Stock-Rom Flash Tool Nokia 7.2 [DDV_sprout]

{
"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"
}
Note - Iam Not Responsible for bricked devices
Disclaimer
This is specially designed for Nokia 7.2 With the help of this tool we can flash any stock home brew Roms and the links will be attached below .
How to use this?
Note - Make sure your phone bootloader is unlocked
1. Download Nokia-SDM660-Tool.zip & Copy Nokia-Tool.exe
2. Download latest HOME BREW Stock Rom And extract in one Folder and name it as STOCK ROM
3. Now add Nokia-Tool.exe & adb platform tools in to that respective STOCK ROM Folder
4. Now connect phone to pc
5. Go to fastboot mode
6. Now Open Nokia-Tool.exe
7. Now select Button according to your Phone code
8. Example Iam Using Nokia 6.1 Plus & My phone code DRG & so i will choose [ DRG B2N CTL PL2 ] same option for 6.1 , 7.1 & 7+ but for 7.2 & 6.2 users choose [DDV SLD]
9. i will click on [ DRG B2N CTL PL2} According to my phone as i explained in point no.8
10. wait for 10 min Tool will flash the rom & your phone reboots to system.
11. So finally this is what the exact standard method to flash stock rom on Your devices
Download Tool
Download stock roms
Credits
Massive thank you for hikari_calyx ( Without him and his support during hmd journey iam nothing )
&
My entire Nokia 7.2 community Thank you all for your massive support Again
​
XDA:DevDB Information
Stock-Rom Flash Tool Nokia 7.2
Contributors
Raghu varma , hikari_calyx
Source Code:
https://github.com/RaghuVarma331/Nokia-Tool.git
Version Information
Status: Stable
Current Stable Version: 1.5
Stable Release Date 2019-12-23
Created 2019-12-23
Last Updated 2020-04-07

Now Some common Questions
Q1. we still receive monthly updates?
A. obviously you will receive updates as like before
Q2. Can we try this on Locked Bootloader?
A. No
Q3. Can we use this without Adb Tools?
A. No
Q4. Can we use this tool on any Android version?
A. Yes works On Oreo , pie & Q but keep this point in your mind update your platform tools time to time due to For Q & Pie & Oreo all these 3 having different different platform tools so if you face any erros don't get scared just download latest adb platform tools

Hi there
First off thank you for your work on the Nokia 7.2, it's good to see someone doing stuff for this phone.
I have a couple of requests to make specifically related to this tool.
Firstly, is it possible to release the full sources of the tool? On your GitHub repository there's only one file related directly to the tool (Form1.cs), and the naming inside the file is all still the auto-generated code from the WIndows Forms designer in VS, which makes it very difficult for anyone to contribute simply because it's hard to figure out what's going on.
Secondly, as a continuation of the first issue, I see that you added entries to the flashtool to flash the 1.400 build for Nokia 7.2 (as per your Telegram channel - POST), however this release is not on the GitHub page. The last release was the original release on 23rd December 2019. I also checked your SourceForge page, however the tool doesn't appear there. This feeds back into the first issue where if I had the full source I could compile and flash the new ROM myself.
If you could at least upload the full source code for the first request, I would happily fork it and clean up the code a bit, even make it so you don't have to manually update the code every time a new release comes out.
Otherwise, keep up the great work man
R

Riccorbypro said:
Hi there
First off thank you for your work on the Nokia 7.2, it's good to see someone doing stuff for this phone.
I have a couple of requests to make specifically related to this tool.
Firstly, is it possible to release the full sources of the tool? On your GitHub repository there's only one file related directly to the tool (Form1.cs), and the naming inside the file is all still the auto-generated code from the WIndows Forms designer in VS, which makes it very difficult for anyone to contribute simply because it's hard to figure out what's going on.
Secondly, as a continuation of the first issue, I see that you added entries to the flashtool to flash the 1.400 build for Nokia 7.2 (as per your Telegram channel - POST), however this release is not on the GitHub page. The last release was the original release on 23rd December 2019. I also checked your SourceForge page, however the tool doesn't appear there. This feeds back into the first issue where if I had the full source I could compile and flash the new ROM myself.
If you could at least upload the full source code for the first request, I would happily fork it and clean up the code a bit, even make it so you don't have to manually update the code every time a new release comes out.
Otherwise, keep up the great work man
R
Click to expand...
Click to collapse
Well thanks for your feedback. But if you are familiar with visual studio. You won't say it is auto generated but the thing is formula which i used is same for 6 different handsets. But still SLD DDV is almost same but the thing is there is no rule to upload source code expect kernel sources until its related to Android operating system. But still i provided the main thing which contains everything in form1.cs well the thing is ui can't be run on another visual studio directly. If you know this point then you won't ask for full source code. Apart from your questions. You can't compile rom.zip because it's actually based on OTA.zip converted to fastboot with my shell script if you are familiar in all these definitely you won't ask about source code and zip and compilation stuff

How enter to download mode?
Nokia 6.2

Hello there,
I successfully installed the Android 10 Stock-ROM on my Nokia 7.2 some Weeks ago (Android 10.0.0 DDV2250 HOME BREW (March 2020)).
Today I received the first OTA-Update (V2.270) but I'm unable to install it. My Device is allways showing "Installationproblem" after a few Seconds.
How can I fix this?
I only unlocked the Bootloader to flash the Stock-ROM, there is no root, custom recovery or anything like that.
Thanks in advance!

raghu varma you r working hard keep it up

Since this tool works on Windows only, have you ever planned on releasing one for Linux?
I had three Xiaomi devices before I bought Nokia 7.2 and all of them had some sort of shell script, which worked flawlessly on my Linux distribution. I would be so happy to have a tool that works on Linux as well.

eX1337 said:
Hello there,
I successfully installed the Android 10 Stock-ROM on my Nokia 7.2 some Weeks ago (Android 10.0.0 DDV2250 HOME BREW (March 2020)).
Today I received the first OTA-Update (V2.270) but I'm unable to install it. My Device is allways showing "Installationproblem" after a few Seconds.
How can I fix this?
I only unlocked the Bootloader to flash the Stock-ROM, there is no root, custom recovery or anything like that.
Thanks in advance!
Click to expand...
Click to collapse
You can try to flash A and B to Stock and then try to update again. In case you thought that the downloaded files where Bad, you can download a newer full-update.zip and then make your own homebrew.

This tool doesnt do anything to the phone. It claims its rebooting the phone but nothing happens, even after waiting for well over 10 mins.

Same here as Talon Pro. Installed the stock like in instruction, rebooting the phone and android screen is freezing like forever...
any solutions?

You can alternative try downloading the Firmware from https://fih-firmware.hikaricalyx.com. Maybe, this script works better for you. All things flashed, a&b! Normaly, you can't do something wrong.

Hello,
i have from my friend this nokia 7.2 and is sw bricked...stuck on green logo.
I want to flash back stock firmware, but bootloader is locked and is impossible to enable oem unlock.
Only way how to bring it back to live is test to flash all roms for find correct one?
...i have tested switching slots...and still stuck

Can we flash it without ost

need nokia7.2 qfil file my phone daed now

CornholioGSM said:
Hello,
i have from my friend this nokia 7.2 and is sw bricked...stuck on green logo.
I want to flash back stock firmware, but bootloader is locked and is impossible to enable oem unlock.
Only way how to bring it back to live is test to flash all roms for find correct one?
...i have tested switching slots...and still stuck
Click to expand...
Click to collapse
same here

I cannot find DDV_sprout in location:
https://sourceforge.net/projects/ddv-sprout/files/HMD-RVDP/
This location was mensioned in:
[CLOSED] [FREE] [9.0,10.0 &11.0] Bootloader unlock for Nokia 7.2 [2021-06-22]
Free Bootloader unlock for Nokia 7.2 Well , after 2 years finally the dream come true. yes , we achieved what we seen in the title of my thread. atlast free bootloader unlock for Nokia 7.2 running on any android version especially android 10 &...
forum.xda-developers.com
Where to find proper DDV_sprout for Nokia 7.2 to unlock bootloader?

Thread closed on request of OP @Raghu varma

Question Oneplus 9Pro got "system update available, 4.53GB, but I am not a Beta tester, wth?

Hi into the forums,
I try to find out about this update, 'cause it is just "a bit big" for minor changes and a security patch, methinks. My guess, it is the Oxycolor13.
But I do not find any information about a stable version, only betas are out or pulled back, so what do they offer here?
Got that info/offer 2 days ago and are still clueless!
Can it be that it is somehow the ColorOs? Did read that China OP9Pro get updated with Color Os 13 for LE2120.
Mine seems to be a LE2125 (shown unter "about device"), but it is an import phone, out of the box with google, all languages, plus the former update to Oxycolor 12 worked the normal way.
Thanks for helping.
7/11
{
"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"
}

7-eleven said:
Hi into the forums,
I try to find out about this update, 'cause it is just "a bit big" for minor changes and a security patch, methinks. My guess, it is the Oxycolor13.
But I do not find any information about a stable version, only betas are out or pulled back, so what do they offer here?
Got that info/offer 2 days ago and are still clueless!
Can it be that it is somehow the ColorOs? Did read that China OP9Pro get updated with Color Os 13 for LE2120.
Mine seems to be a LE2125 (shown unter "about device"), but it is an import phone, out of the box with google, all languages, plus the former update to Oxycolor 12 worked the normal way.
Thanks for helping.
7/11
View attachment 5740937
Click to expand...
Click to collapse
Hi.
What's your OOS12 version?

That looks like a full-update to the latest OOS12 C.65, the same version many of us here have installed over the past week. Except we all mostly just got the incremental update, because OnePlus hasn't put out a full update file since last spring.. Until now, it seems.

AC130PL said:
Hi.
What's your OOS12 version?
Click to expand...
Click to collapse
LE2125_11_C.63
So it is another Android 12 update? Only? confusing

mlord said:
That looks like a full-update to the latest OOS12 C.65, the same version many of us here have installed over the past week. Except we all mostly just got the incremental update, because OnePlus hasn't put out a full update file since last spring.. Until now, it seems.
Click to expand...
Click to collapse
Ok, if it is that, I do appologyze for asking. Just confused, since everyone is talking about 13.
Edit: One more question: Do I have to do that full update to 12, with the 13 coming our way?

What does it say your model number is on physical box your phone came in
If you don't have the official box, it will be on the back of your phone, very close to the charger port at the bottom.

I haven't actively searched for information on it, but AFAIK OnePlus have not yet released an Android 13?
Anyone care to guess how long it'll take TMO to follow up with a massaged (spam filled) OnePlus Android 13 after it gets dropped?
I'll guess two months but it's a guess based on assumption, not facts or experience.

AndyC76 said:
What does it say your model number is on physical box your phone came in
If you don't have the official box, it will be on the back of your phone, very close to the charger port at the bottom.
Click to expand...
Click to collapse
Ok, that clears the model number, box says it is a chinese 2120.
Thanks, didn't think about checking the box.
Probably because with past models just the OS was the difference, not the hardware. And mine came with global pre-installed and I had no problems in the past

For future reference, the ColorOS/Oxygen OS 13 update has an F instead of C, so "LE2125_11_C.XX" is Android 12, while "LE2125_11_F.XX" is Android 13.

rmendez011 said:
For future reference, the ColorOS/Oxygen OS 13 update has an F instead of C, so "LE2125_11_C.XX" is Android 12, while "LE2125_11_F.XX" is Android 13.
Click to expand...
Click to collapse
Ah yeah, the "C" for Android 12 and the "F" for Android 13... makes complete sense

GolovaRaoul said:
Ah yeah, the "C" for Android 12 and the "F" for Android 13... makes complete sense
Click to expand...
Click to collapse
I am already questioning that they still call it LE2125_11_
Already for the Android 12 update, I was thinking: wth?
For me, it would be more logic to call Droid 11 updates _11+, followed by A or B or .... , for every next one
And
Android 12 =_12_
Android 13 = _13_
Since the 2125 is the model.
But hey, I am just a OP phone user.
Thanks to all for helping
Only one more question:
Do I need to flush this full update over my Android 12 version?
One of the last updates was already a "full one" (in GB , not MB), and with 13 coming out some time in the nearer future, ....
As bigger an update, as more problems to expect, imho.
Don't really need that twice in a couple of weeks or month!

GolovaRaoul said:
Ah yeah, the "C" for Android 12 and the "F" for Android 13... makes complete sense
Click to expand...
Click to collapse
Not saying it makes sense, but that's what OnePlus did for 9 Series.
For 10 Pro "A" is Android 12, and "C" is Android 13 LOL.

7-eleven said:
I am already questioning that they still call it LE2125_11_
Already for the Android 12 update, I was thinking: wth?
For me, it would be more logic to call Droid 11 updates _11+, followed by A or B or .... , for every next one
And
Android 12 =_12_
Android 13 = _13_
Since the 2125 is the model.
But hey, I am just a OP phone user.
Thanks to all for helping
Only one more question:
Do I need to flush this full update over my Android 12 version?
One of the last updates was already a "full one" (in GB , not MB), and with 13 coming out some time in the nearer future, ....
As bigger an update, as more problems to expect, imho.
Don't really need that twice in a couple of weeks or month!
Click to expand...
Click to collapse
I 100% agree, I've argued with people who said "LE2125_11_" was OOS 11. They should just go back to OOS 11.2.10.10 naming, OOS 12.X.XX.XX, and OOS 13.X.XX.XX.
To update to this version, you have to be on either C.63/C.65 for NA/IN, or C.64/C.65 for EU

Weird!
Yesterday, the update size changed, from 4,x GB to 409MB.
What is going on with Oppo's sub brand?

7-eleven said:
Weird!
Yesterday, the update size changed, from 4,x GB to 409MB.
What is going on with Oppo's sub brand?
View attachment 5751799
Click to expand...
Click to collapse
Incremental And the big Update is the full rom

But why did I get the full one offered, some weeks ago, but now just the little one?
And why do they have the same name?

Sry, double post

7-eleven said:
But why did I get the full one offered, some weeks ago, but now just the little one?
And why do they have the same name?
Click to expand...
Click to collapse
Were you rooted at that time and not rooted now?

TNSMANI said:
Were you rooted at that time and not rooted now?
Click to expand...
Click to collapse
Nope!.
Not rooted at all.
Just the message changed from 4,x GB to 400MB size for the available update.
Btw , I did the "small one", today.
Now the 9pro is "up2date".

Was I a bit premature, perhaps?
Got this today, october security update:
Perhaps that was the reason for switching from 4.xGB to 400MB for the last update?
"We need to convince them to update, there is another one waiting, already. They dont like 4GB? Try smaller"

General June 14, 2023 - Beta 3.1 UPB3.230519.014 Global - Android 14 "Upside Down Cake" - Pixel 6 Pro [Raven]

Android 14 Beta program for the Pixel 6 Pro [Raven]​
Download links in the center of the OP.
Welcome to the Android 14 Developer Preview! This first release is for developers only, to help with early development, testing, and feedback. Android 14 Developer Preview 1 is an early baseline build that's still in active development, so the Android system and apps running on it might not always work as expected.
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"
}
Note to anyone who flashes a Developer Preview or Beta OTA without having the capability to unlock your bootloader - you'll be stuck in the Developer Preview and Beta program until it goes final - in the case of Android 14, somewhere between August and October 2023. There is absolutely nothing that can be done about this without being able to unlock the bootloader. And even with an unlocked bootloader, you'll have to perform a complete wipe when going back to Stable.
June 14, 2023:
Beta 3.1:
Release notes | Android Developers
Release notes and known issues for the latest Android 14 builds.
developer.android.com
Factory images for Google Pixel | Android Developers
Instructions for downloading and installing preview system images for Pixel devices.
developer.android.com
OTA images for Google Pixel | Android Developers
Instructions for downloading and appying preview OTA images for Pixel devices.
developer.android.com
Get Android 14 | Android Developers
Get Android 14 on your eligible device.
developer.android.com
Android 14 Preview | Android Developers
How the Android 14 Preview works, the timeline, and what is included.
developer.android.com

Anyone want to test an OTA out and see if it works (locked bootloader) I started OTA on Dev Preview 2 last year
https://developer.android.com/about/versions/14/download-ota

Just added to the OP:
Release notes | Android Developers
Release notes and known issues for the latest Android 14 builds.
developer.android.com

Added the following (LONG!):
Android Developers Blog
News and insights on the Android platform, developer tools, and events.
android-developers.googleblog.com

Doug8796 said:
Anyone want to test an OTA out and see if it works (locked bootloader) I started OTA on Dev Preview 2 last year
https://developer.android.com/about/versions/14/download-ota
Click to expand...
Click to collapse
Note to anyone who flashes a Developer Preview or Beta OTA without having the capability to unlock your bootloader - you'll be stuck in the Developer Preview and Beta program until it goes final - in the case of Android 14, somewhere between August and October 2023.

Just a heads up... On A14 DP1, to root this device you must use the Pixel 7 Pro boot image and patch and flash that. Similar to the bug on A13 QPR2 Betas 1>2.1 on the Pixel 6 series (was "fixed" on QPR2 Beta 3).
Oh, I used Canary 25206 but I'm guessing Stable works as well.

roirraW edor ehT said:
Note to anyone who flashes a Developer Preview or Beta OTA without having the capability to unlock your bootloader - you'll be stuck in the Developer Preview and Beta program until it goes final - in the case of Android 14, somewhere between August and October 2023.
Click to expand...
Click to collapse
Totally content with this. 13 had its share of bugs, but I was happy to report to make a solid 13 experience for us all. I just dont want to brick. I know some people had issues trying to ota over. Let me know if ota works for you guys

The https://developer.android.com/about/versions/14/overview has already changed with some minor corrections.
It did say:
What's included in the Android 14 Preview?​...
SDK & NDK tools​...
SDK, NDK, and tools for Android 14
...
For more inforamtion, see Get Android 14.
Click to expand...
Click to collapse
Now it says:
What's included in the Android 14 Preview?​...
SDK & tools​...
SDK and tools for Android 14
...
For more information, see Get Android 14.
Click to expand...
Click to collapse

https://twitter.com/i/web/status/1623382609056129025

Lughnasadh said:
Just a heads up... On A14 DP1, to root this device you must use the Pixel 7 Pro boot image and patch and flash that. Similar to the bug on A13 QPR2 Betas 1>2.1 on the Pixel 6 series (was "fixed" on QPR2 Beta 3).
Oh, I used Canary 25206 but I'm guessing Stable works as well.
Click to expand...
Click to collapse
Wait huh? So I need to flash pixel 7 ota and then 6?

Doug8796 said:
Wait huh? So I need to flash pixel 7 ota and then 6?
Click to expand...
Click to collapse
No. You don't flash the OTA to root. Please read that post again.

Lughnasadh said:
No. You don't flash the OTA to root. Please read that post again.
Click to expand...
Click to collapse
OK. I cant root or unlock bootloader for that matter until 2025, so no problem there.
Has anyone flashed the ota from 13 qpr/ 13

Doug8796 said:
OK. I cant root or unlock bootloader for that matter until 2025, so no problem there.
Has anyone flashed the ota from 13 qpr/ 13
Click to expand...
Click to collapse
QPR1 stable or QPR2

pogo-airsupport said:
QPR1 stable or QPR2
Click to expand...
Click to collapse
Either.. From my understanding most fresh wipe for 14 Dev preview. I wanted to know if OTA worked. I got a real OTA on one of my beta and it wiped data.

Doug8796 said:
Either.. From my understanding most fresh wipe for 14 Dev preview. I wanted to know if OTA worked. I got a real OTA on one of my beta and it wiped data.
Click to expand...
Click to collapse
I've always dirty flashed. It worked this time as well. On P6P and P7P

Lughnasadh said:
Just a heads up... On A14 DP1, to root this device you must use the Pixel 7 Pro boot image and patch and flash that. Similar to the bug on A13 QPR2 Betas 1>2.1 on the Pixel 6 series (was "fixed" on QPR2 Beta 3).
Oh, I used Canary 25206 but I'm guessing Stable works as well.
Click to expand...
Click to collapse
Note also that you gotta fastboot flash the p7pro boot image
Code:
fastboot flash boot "pathtotheimage"
I tried booting it and root wouldn't stick

So far these mods/root apps are working for me:
JamesDSP
V4A_RE
AML
ACP
Adaway
Pixel Launcher Mod (Kieron Quinn)
Repainter
Substratum Lite (Iris Monet)
Revanced YouTube & YouTube Music mods by j-hc
Better Battery Stats is partially functional (need to wait a bit to see how functional)

@Displax Universal SafetyNet Fix v2.3.1-MOD_3.0 on GitHub - I haven't followed if the changes are applicable to Stable Android as well, or if they are geared towards this DP1. I'm also not sure I can find @Displax' sub/temp OP in @kdrag0n's Universal SafetyNet Fix thread.
Edit: @Displax's XDA OP here.

how to Update
com.shannon.qualifiednetworksservice_I14fc0eb39a63c279d7f28e503a12fec7dbb91966-53_minAPI33(nodpi).apk
and
com.shannon.rcsservice_2049646261396436336139366636366232653131643962316461616137663834646232363336616137342e48454144-34_minAPI30(nodpi).apk
from apkmirror to dp1… I cannot install it.

hanschke said:
how to Update
com.shannon.qualifiednetworksservice_I14fc0eb39a63c279d7f28e503a12fec7dbb91966-53_minAPI33(nodpi).apk
and
com.shannon.rcsservice_2049646261396436336139366636366232653131643962316461616137663834646232363336616137342e48454144-34_minAPI30(nodpi).apk
from apkmirror to dp1… I cannot install it.
Click to expand...
Click to collapse
Since it's usually a system app, you'd probably have to use a Magisk Module that spoofs putting the new apk(s) in the root system apps folder. I never remember the name of the modules that do this since I haven't had a need to, but I'm sure you can find them with some Googling.
It's probably impossible to just straight install them like a normal app.