Looks like Android 13 is in beta for Oppo Find N to certified chinese developers - so I assume it will skip A12 and go straight to A13?
Does anyone know how quickly historically Oppo phones go from firsts beta to public release?
I want to download and install it on mine but still can not find link in CN forum )
https://sbox.myoas.com/wcm/Mobile/Home/SubContent?pluginId=publish&code=B61dae773c9864547&lang=zh-cn#/publish?code=B61dae773c9864547&fileid=
All datas will be erased after the update 13 beta 1
Use the pc to download the zip
Paste to the phone
Activate the developper menu if not already done
Open the update menu/local installation
Unzip the file
Wait for upgrade and take a coffee
Any link to downgrade if needed
Any one try it to give feedback
anasmhds said:
Any one try it to give feedback
Click to expand...
Click to collapse
OPPO Developer
It seems there is a link to downgrade
I am testing it now installation is in progress
https://sbox.myoas.com/outpublish.html?code=B5881594033672a6c#view
My update has failed at the end of the process
I will retry
On onleplus 10pro, they gave us 2 links one for A13 developer preview and one for downgrade and most of the members returned to A12
babaorum1973 said:
My update has failed at the end of the process
Click to expand...
Click to collapse
I hope your phone is ok after the trial
Yes all ils ok Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had retried but without success 5 soft bootloops and after the phone came back to android 11 with update failed. May be is region related or a fix in another update but it's nice to see the find N jumping from Andoid 11 to 13. Final realese is for july
babaorum1973 said:
I had retried but without success 5 soft bootloops and after the phone came back to android 11 with update failed. May be is region related or a fix in another update but it's nice to see the find N jumping from Andoid 11 to 13. Final realese is for july
Click to expand...
Click to collapse
Maybe...
Thanks for sharing your experience, so, we will wait for OTA
anasmhds said:
Maybe...
Thanks for sharing your experience, so, we will wait for OTA
Click to expand...
Click to collapse
Yes the beta 1 had those issues
3. Known issues (model OPPO Find N)1) There may be stability and performance issues
2) The clock does not display after the screen is off
3) The gesture on the black screen fails 4) An exception occurs
after clicking the SIM card toolkit Home, AutoNavi, Ctrip, 58.com, Dianping, Baidu) 7) App icons are displayed slowly when entering the desktop 8) The startup animation of the small screen is abnormally displayed 9) The virtual keys of the large screen are abnormally displayed 10) The full screen gesture operation of the large screen Abnormal 11) Abnormal connection of bluetooth headset 12) When using mobile phone to move, the mobile phone restarts automatically
Global link and explanations before downloading
OPPO 开放平台-OPPO开发者服务中心
OPPO 开放平台，为开发者提供强大的应用分发能力，丰富的应用服务及推广变现支持，助力开发者实现业务增长和商业变现。
open.oppomobile.com
babaorum1973 said:
Final release is for july
Click to expand...
Click to collapse
Do you have a source?
What I have been painfully translating from Chinese to French, there is a very little change visible.
I hope they bring back voice over lte
babaorum1973 said:
I had retried but without success 5 soft bootloops and after the phone came back to android 11 with update failed. May be is region related or a fix in another update but it's nice to see the find N jumping from Andoid 11 to 13. Final realese is for july
Click to expand...
Click to collapse
I am also currently in the process of "updating", however it appears I am having the same bootloop problems, Hopefully they resolve themselves like yours did. haha
What is new in this software?
I have both beta 13 and downgrade package will test it out I am interested if the AutoStart limit is more than 5 items )
Anyone managed to downgrade back?
My settings keeps crashing so I can't do a local install...
Can anyone help me downgrade - keeps crashing... A lot of apps are crashing when I launch them...
Related
AFAIK there is no theme editor compatible with EMUI 9 yet. Not even Huawei official editor seems compatible with 9 yet. And I cannot find any themes for EMUI 9. The ones for 8 look mostly crappy. Is this correct or am I missing something? When can we expect a theme editor + themes for 9?
https://play.google.com/store/apps/details?id=com.mixapplications.themeeditor
Tiago A said:
https://play.google.com/store/apps/details?id=com.mixapplications.themeeditor
Click to expand...
Click to collapse
That's as far as I know not updated for EMUI9.
TigerSoul925 said:
That's as far as I know not updated for EMUI9.
Click to expand...
Click to collapse
I'm using it with EMUI 9. Not a single problem.
Tiago A said:
I'm using it with EMUI 9. Not a single problem.
Click to expand...
Click to collapse
Can it change the notification shade icons? Will the resulting theme not give the warning "this theme was made for a previous version of emui"?
Since the last update or security patch.. The Themes Manager ask me to "log in to Huawei ID to download more great themes" .. But isn't allowing me to .. It will let me change the few icon sets it offers and I was able to change my font before that update..
I'm on 9.0.0.126 - Patch 2..
When I click on "Customize" and then try to change "lock screen style", "text style" etc .. It just shows the spinning wheel of death .. Anyone else having an issue like this ?.. Or may know of something I may be doing wrong ?.
Thanks ...
Supertrooper said:
Since the last update or security patch.. The Themes Manager ask me to "log in to Huawei ID to download more great themes" .. But isn't allowing me to .. It will let me change the few icon sets it offers and I was able to change my font before that update..
I'm on 9.0.0.126 - Patch 2..
When I click on "Customize" and then try to change "lock screen style", "text style" etc .. It just shows the spinning wheel of death .. Anyone else having an issue like this ?.. Or may know of something I may be doing wrong ?.
Thanks ...
Click to expand...
Click to collapse
Had this bug. It worked again after resetting the phone, Not sure what I did or didn't that triggered it. There are probably other solutions.
TigerSoul925 said:
Had this bug. It worked again after resetting the phone, Not sure what I did or didn't that triggered it. There are probably other solutions.
Click to expand...
Click to collapse
So you did a back up, then reset your phone and started over ?.
Supertrooper said:
So you did a back up, then reset your phone and started over ?.
Click to expand...
Click to collapse
I noticed this during testing of devices due to the green screen issue. I'm not sure what element of the reset made it work. I did no backup as I hardly got anywhere into setting up the phone before returning it.
Huawei developer website
Check out the Huawei developer webpage apparently there is a tool for converting themes to emui 9 but I'm not able to test it right now as I'm not at a computer.
Neither can I share the link as I haven't posted enough on xda ?
{
"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"
}
Hi Guys,
Good to be back with a guide post on XDA after long time.
Background-
Let me start with the credit here, a big thanks to @Smaehtin for his tool and guide here .
This was not possible without his valuable contribution and excellent tool. He is the creator of this tool and all credit goes to him only. His method was working absolutely fine for any EMUI 8.0 user to update their phone to the stable EMUI 9.0 build but it was failing for beta EMUI 9.0 user due to change of ways the updates are working in EMUI 9.0.
In this guide, I will just share some tricks to update your phone if you are beta user from BKL-L09C675B108 (beta build) to a stable one out there B159. Few users got the updates but due to some issue, OTAs were stopped and we were struggling with beta build. I tried all the avaialble method possible but as I am non rooted or can not unlock my bootloader so could not do anything like no-check recovery installation or other ways.
Please follow the original thread if you are EMUI 8.0 user as it will work very easily and you can update. Please continue with this trick only if you are beta user.
P.S. I am not responsible for anything but this should doesn't harm anything and should update fine.
Long story short. I tried few versions of Hisuite but the one which worked for me is HiSuite_8.0.1.300_OVE, available on Huawei website, you can capture from here as well
Method-
1- Connect your phone to your computer through USB
2- Before proceeding, make sure HiSuite isn't running. Open Task Manager (Ctrl+Alt+Del, kill the service HuaweiHiSUite64.exe from services tab) and also make sure it is not running Processes tab, If it's running, right-click and select "End Task" to kill the process
3- Run "Launcher.exe" and HiSuite should open
4- Once the HiSuite is launched it will immediately ask for update HiSuite Application until you update you can't use the app. Notice the update option (for EMUI version) location on your screen with a red dot and close the HiSuite (it may sound weird but that is the trick)
{
"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"
}
5- Kill the app again from task manager and double launcher.exe again.
6- This time make sure to click few times the update option before the HiSuite Update window launches. Once it is launched, no matter if HiSuite update windows launches at the same time, you can still click on EMUI update options. (sometime HiSuite update window doesnt launch if you are fast enough to click on EMUI update option- mine was not launched in last attempt)
7- Once the EMUI update window is launched you can click on update and restore to earlier version (it will restore to the same stable EMUI 9.0 version BKL-L09C675B159) so just click on update .
8- Wait for HiSuite to finish installing the update on your phone.
9- Once Finish, phone will reboot and it will finish the installation and update.
10- During the update, it will optimize the application and once boothed, you will be on B159 stable version.
Before and After update screenshot.
Good luck and enjoy.
Reserved.
This may work with HiSuite version 8.0.1.303 as well but not working with 9.X version
i tried it with hisuite v 5 but the update pop appears very very fast i can't do ant thing
Mohamed Elhadad said:
i tried it with hisuite v 5 but the update pop appears very very fast i can't do ant thing
Click to expand...
Click to collapse
I was fast enough to do this on touch screen laptop. You may try a mouse, that's faster as well. Also, stable build is out now for many models so you can try official OTA
shashank1320 said:
I was fast enough to do this on touch screen laptop. You may try a mouse, that's faster as well. Also, stable build is out now for many models so you can try official OTA
Click to expand...
Click to collapse
I have tried fast but it gave me the same problem that i can't find switch to other version
I began to hate Huawei
Info: https://support.google.com/pixelphone/thread/175255708/google-pixel-update-android-13?hl=en
Download page https://developers.google.com/android/ota#oriole
Be aware:
{
"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"
}
There is face unlock in this device now?
Cause this is what i see in the changelog:
Fix for issue preventing face unlock to trigger in certain conditions *[3]
Edit: My bad, this is for pixel 4 devices
root real android 13 yet?
Sideloaded on my US T-Mobile P6, seems good so far.
TheUndertaker21 said:
root real android 13 yet?
Click to expand...
Click to collapse
Magisk 25.2 works fine.
Nova launcher working with gestures?
Lughnasadh said:
Magisk 25.2 works fine.
Click to expand...
Click to collapse
How you update? Patch boot.img with Magisk Manager, flash image & pateched boot like before?
Sh0X31 said:
How you update? Patch boot.img mit Magisk, flash image & than boot like before?
Click to expand...
Click to collapse
After updating to A13 stable, yes, patch and flash.
Does it allow multiple bluetooth devices to be connected simultaneously?
Oh and does it simply update your current install or does it wipe and install?
poit said:
Sideloaded on my US T-Mobile P6, seems good so far.
Click to expand...
Click to collapse
How do you sideload with the bootloader locked? Does it wipe your phone? Waiting (impatiently) for T-Mobile to send out the new update.
So if I'm on beta 4.1 and take this update it will put me on stable release. And if I unenroll immediately after the update I should be placed on the stable channel? No qpr updates n such?
mojorisin7178 said:
So if I'm on beta 4.1 and take this update it will put me on stable release. And if I unenroll immediately after the update I should be placed on the stable channel? No qpr updates n such?
Click to expand...
Click to collapse
Correct.
"If you’re currently enrolled in the Android Beta program, you’ll get the Android 13 final release and remain enrolled to receive ongoing Beta updates for Android 13 feature drops, starting later this year. If you’d like to opt out of ongoing Beta updates without needing to wipe your device, just visit the Android Beta site and opt out after you get the Android 13 final release and before taking the first beta for Android 13 feature drops."
Android 13 is in AOSP!
News and insights on the Android platform, developer tools, and events.
android-developers.googleblog.com
inumugi said:
How do you sideload with the bootloader locked? Does it wipe your phone? Waiting (impatiently) for T-Mobile to send out the new update.
Click to expand...
Click to collapse
Don't know if my phones bootloader is locked, but I bought it direct from T-Mobile US. Instructions for sideloading using ADB are on the top of the download page. It didn't wipe my phone and it's quicker than an OTA install. https://developers.google.com/android/ota#oriole
Anyone get it OTA yet? Purchased unlocked from Google and on AT&T; nothing yet for me.
Trying to sideload the OTA image file downloaded from Google, using latest version of adb, seems to getting stuck at "serving: 'oriole-ota-tp1a.220624.021-a13fd9d0.zip' (~3%)" - phone displaying "Verifying update package..."
I've sideloaded OTA images in the past without any issues, anybody have a suggestion?
Steve53 said:
Trying to sideload the OTA image file downloaded from Google, using latest version of adb, seems to getting stuck at "serving: 'oriole-ota-tp1a.220624.021-a13fd9d0.zip' (~3%)" - phone displaying "Verifying update package..."
I've sideloaded OTA images in the past without any issues, anybody have a suggestion?
Click to expand...
Click to collapse
When you say "using the latest version of adb", are you referring to the latest version of Platform Tools? Are your drivers up-to-date? Try using different cables and/or ports?
Yep, latest version of platform tools. Have tried 2 different cables (one of which is the one that came with the phone). Will check for driver updates, but have used this same PC to perform previous updates on my Pixel 6.
Steve53 said:
Yep, latest version of platform tools. Have tried 2 different cables (one of which is the one that came with the phone). Will check for driver updates, but have used this same PC to perform previous updates on my Pixel 6.
Click to expand...
Click to collapse
Did you confirm you got a clean download by running a SHA-256 checksum? Just a stab in the dark
Hello !
This update focus on the optimisation of the system AND the camera part.
What are your toughts on this specific matter ?
Better by any means ?
Yoodj said:
Hello !
This update focus on the optimisation of the system AND the camera part.
What are your toughts on this specific matter ?
Better by any means ?
Click to expand...
Click to collapse
Still on the 2030 version here, what region are you in ?
You can update manually, if you wish, by downloading the firmware from the asus support website and leaving the zip file on the root of the phone. A popup will appear upon reboot asking if you want to update.
I am on the latest and see no difference, unfortunately.
Eduardomcp said:
You can update manually, if you wish, by downloading the firmware from the asus support website and leaving the zip file on the root of the phone. A popup will appear upon reboot asking if you want to update.
I am on the latest and see no difference, unfortunately.
Click to expand...
Click to collapse
Will manual update force me to do it manually in the future?
someone asked the same on zentalk forum. I don't know, but supposedly no, I can only hope...
Kelevra1902 said:
Will manual update force me to do it manually in the future?
Click to expand...
Click to collapse
No, OTA functionality is intact, until you unlock the bootloader
I got the OTA of this update overnight
The the processing feels faster IMO but no quality change. I was also getting my screen stuck at 60hz after unlucking and the update seems to fixed it. Which is nice
No real improvement. I'm waiting for a fix when shooting raw - it takes 1 sec to take a picture after pressing the shutter.
I don't see any change in picture quality, sadly.
It seems there is a new fw on some - but not other - Asus support sites: asus.com/ch-de/Mobile/Phones/ZenFone/Zenfone-9/HelpDesk_BIOS/
Again they brag about camera improvements...
landsome said:
It seems there is a new fw on some - but not other - Asus support sites: asus.com/ch-de/Mobile/Phones/ZenFone/Zenfone-9/HelpDesk_BIOS/
Again they brag about camera improvements...
Click to expand...
Click to collapse
That seems to be only APN list update. No mentions of the camera
Try the Android 13 beta, the camera is better there. Also, the experience has been stable for me so far, no major bugs discovered yet. Nicely suitable for daily driver.
-=zipp=- said:
Try the Android 13 beta, the camera is better there. Also, the experience has been stable for me so far, no major bugs discovered yet. Nicely suitable for daily driver.
Click to expand...
Click to collapse
When was the latest update to the beta?
Two days ago.
BTW: no home gesture animation bug anymore!
-=zipp=- said:
Two days ago.
BTW: no home gesture animation bug anymore!
Click to expand...
Click to collapse
Thanks
I updated to the latest firmware and now I've lost contactless...
{
"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"
}
x2srj said:
I updated to the latest firmware and now I've lost contactless...View attachment 5734785
Click to expand...
Click to collapse
This issue has already been reported to ASUS:
Google wallet not certified ? Running 32.2040.2040.28
Please tell us some basic information before asking for help: Model Name: Zenfone 9 Firmware Version: 32.2040.2040.28 Rooted or not: stock Frequency of Occurrence: everytime APP Name & APP Version (If your issue relates to the app): Google wallet. In addition to information above, please also...
zentalk.asus.com
Yeah I'm one of the people that's posted on that thread. Ta
-=zipp=- said:
This issue has already been reported to ASUS:
Google wallet not certified ? Running 32.2040.2040.28
Please tell us some basic information before asking for help: Model Name: Zenfone 9 Firmware Version: 32.2040.2040.28 Rooted or not: stock Frequency of Occurrence: everytime APP Name & APP Version (If your issue relates to the app): Google wallet. In addition to information above, please also...
zentalk.asus.com
Click to expand...
Click to collapse
Yes by me.. Lets see if the next update fixes the certification again.
So Im on global (CPH2415) I just downloaded the downgrade package for global used it so back on Android 12 then I shut off auto updates and waited for the next day I checked oxygen updater and seen a update for (CPH2417) that was over 4GB so I let it download after saving the file and it let me use the system update app by OnePlus to upgrade into 2417.(if you need me to explain in more detail or tell you exactly how I did it just message me in private message)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
its about time. I was stuck on 2415EU version and now I'm back on 2417NA!
tdamocles said:
its about time. I was stuck on 2415EU version and now I'm back on 2417NA!
Click to expand...
Click to collapse
You got it downloaded and flashed back?
AkayamiShurui said:
You got it downloaded and flashed back?
Click to expand...
Click to collapse
Yes
tdamocles said:
Yes
Click to expand...
Click to collapse
Glad to hear it
Finally! That took forever. I'm flashing back to 2417 currently now as well.
AkayamiShurui said:
So Im on global (CPH2415) I just downloaded the downgrade package for global used it so back on Android 12 then I shut off auto updates and waited for the next day I checked oxygen updater and seen a update for (CPH2417) that was over 4GB so I let it download after saving the file and it let me use the system update app by OnePlus to upgrade into 2417.(if you need me to explain in more detail or tell you exactly how I did it just message me in private message)
View attachment 5780425
Click to expand...
Click to collapse
Is this for the T-Mobile version and what version of Android is it .I have model 2419 and when I try to update my phone or swap to anything but Global Android 12 my apps lock up and says contract phone error and my apps are disabled.
RomLord14495 said:
Is this for the T-Mobile version and what version of Android is it .I have model 2419 and when I try to update my phone or swap to anything but Global Android 12 my apps lock up and says contract phone error and my apps are disabled.
Click to expand...
Click to collapse
How to change regions on Oneplus 10T 5g via Update/Downgrade Packages:
(Moderators, please make this post a sticky, and i will keep it updated of any changes or issues that might come up in future builds, thanks) To clarify things.... I am the dude who figured out how to side-step from model to model... I have...
forum.xda-developers.com
RomLord14495 said:
Is this for the T-Mobile version and what version of Android is it .I have model 2419 and when I try to update my phone or swap to anything but Global Android 12 my apps lock up and says contract phone error and my apps are disabled.
Click to expand...
Click to collapse
So sadly I have had time to look up into the T-Mobile version so that is something I'm a lot of information for but a limit opposed to you that talks about that so hopefully that helps
I am currently on CPH2417_11_A.08 and I want to only go to A.13.. I DO NOT want to update to Android 13 (C.22).. but I cant seem to find this anywhere.. any ideas?
Oppo/Oneplus are systematically scrubbing all traces of the older OTA fw from all the known sites. This is why i havent made any updates to that thread for doing region swaps. My instructions still stand firmly for how its done and whats required, but now its kinda on a peer to peer basis, cuz all the OTA links that are now available anywhere have a new signature check that will make the fw not appear or fail flashing if you try them. But the steps still work... and Creeper36, if you came from a T-mobile original device, you do not want to take that next upgrade ... you CAN go up to A.12 and you will get your 5g , wifi calling, and volte all working... but anything A.13 and above will lock up all your apps and the only way to get the phone working again, is a factory reset, and a rollback. Some security function has been activated that can detect you original device fingerprint, and if you are on ANY fw other than a 2419 build, it triggers the app lock.
Im still working on finding out what needs to be removed from the CarrierDevicePolicy so that this doesnt happen, but i need root access to make progress, and i am on one of the newer 10T that have the Fastboot Protocol disabled. My advice would be to just search thru the oneplus community pages or go to the telegram/discord channels... both are user operated, so you can message someone or just ask the group for the file you want and chances are someone has it, who can help you. I have A.15 but its for the 2415 build. All the fw you find below that version on the common sites (gsm mafia... etc) are packages you will need the msm tool or qfil to flash.
Does this mean I can pull boot from this and finally bl unlock/root my 2417 on Android 13?!
Can someone explain me what is the difference between 2415Global and 2417NA versions of OOS? What is good and of course what is bad? I just flashed my ACE PRO to Global 2415 want to know if it is worth to change to 2417NA? Thanks in advance