Related
Mod edit: 13. Advertising and Income Generation
Commercial advertising, advertising referral links, pay-per-click links and other income generating methods are forbidden. Do not use XDA-Developers as a means to make money.
Sorry but what are you on about? Android 7.0 hasn't even been released for this device yet....
This is all well and good but as stated by Alex Android 7 isn't out for S6 edge + yet. And I'm pretty sure when it does come out it will change the boot loader and reverting back to 6.0.1 will cause imei and baseband loss.
Alex---1 said:
Sorry but what are you on about? Android 7.0 hasn't even been released for this device yet....
Click to expand...
Click to collapse
If it came out but not officially since the rom filter is that of developers
kdogguk said:
This is all well and good but as stated by Alex Android 7 isn't out for S6 edge + yet. And I'm pretty sure when it does come out it will change the boot loader and reverting back to 6.0.1 will cause imei and baseband loss.
Click to expand...
Click to collapse
I was on Nougat multiple times (Khongloi S7 port ROM and DevBase 7.0 ROM modifications), returning to MM was as easy as going to TWRP and flashing a MM ROM, without any bootloader business involved... In my case I simply flashed the V15 Note 7 port by Khongloi, and I was back on MM without any bugs or problems. And if you didn't notice, the firmware in this guide includes a bootloader, so even in the case of the bootloader changing with Nougat, there would be no issue reverting back. I've downgraded my Note 4 from Marshmallow to Kitkat multiple times (for testing purposes), and it's as easy as doing the same steps that are provided in this guide
Go down to the development section, you can see that there are multiple Nougat ROMs that exist for this device already, all based on a leaked base ROM that was meant for app developers. The ROM is nowhere near to finished, it drains battery and the performance is poor, and for that reason many users will consider downgrading, and this thread works for that purpose
galaxyYtester said:
The ROM is nowhere near to finished, it drains battery and the performance is poor
Click to expand...
Click to collapse
You must be living in some alternate reality.
0rigin said:
You must be living in some alternate reality.
Click to expand...
Click to collapse
No, the performance and battery life ratio really is worse in the ROM, it doesn't benchmark even close to stock MM and battery drains fast on some occasions
galaxyYtester said:
I was on Nougat multiple times (Khongloi S7 port ROM and DevBase 7.0 ROM modifications), returning to MM was as easy as going to TWRP and flashing a MM ROM, without any bootloader business involved... In my case I simply flashed the V15 Note 7 port by Khongloi, and I was back on MM without any bugs or problems. And if you didn't notice, the firmware in this guide includes a bootloader, so even in the case of the bootloader changing with Nougat, there would be no issue reverting back. I've downgraded my Note 4 from Marshmallow to Kitkat multiple times (for testing purposes), and it's as easy as doing the same steps that are provided in this guide
Go down to the development section, you can see that there are multiple Nougat ROMs that exist for this device already, all based on a leaked base ROM that was meant for app developers. The ROM is nowhere near to finished, it drains battery and the performance is poor, and for that reason many users will consider downgrading, and this thread works for that purpose
Click to expand...
Click to collapse
This might be due to the fact that they are ports of 7.0.
Im just warning people that update to official when it comes out that it has been known that it updates files that once done cannot be reverted back or it will cause problems, one being the null baseband/imei.
But yes, reverting back at the moment is as easy as flashing a 6.0.1 rom or stock firmware.
Either way hopefully people back up their efs!
i updated to an official 7.0 firmware and now i can't flash 6.0.1 bootloader. Any ideas or am i stuck at 7.0?
kdogguk said:
This is all well and good but as stated by Alex Android 7 isn't out for S6 edge + yet. And I'm pretty sure when it does come out it will change the boot loader and reverting back to 6.0.1 will cause imei and baseband loss.
Click to expand...
Click to collapse
hello
is there any way to avoid this baseband and imei issue or to downgrade BL?
game.gallery said:
hello
is there any way to avoid this baseband and imei issue or to downgrade BL?
Click to expand...
Click to collapse
Well hopefully people will back up their EFS which is a MUST do before starting to flash roms etc.
If you have I think you can use odin to go back to 6.0.1 and then restore the backed up EFS from that version of Android.
Other than that you're stuck on nougat roms.
If you have reverted back to older and you lose imei and/or baseband then you'll need to reinstall nougat rom to get the imei/baseband back.
But as I haven't flashed an official nougat rom I can't say if this will all work or not. I'm going by past experience when I did this with jellybean - kitkat on my old phone.
kdogguk said:
Well hopefully people will back up their EFS which is a MUST do before starting to flash roms etc.
If you have I think you can use odin to go back to 6.0.1 and then restore the backed up EFS from that version of Android.
Other than that you're stuck on nougat roms.
If you have reverted back to older and you lose imei and/or baseband then you'll need to reinstall nougat rom to get the imei/baseband back.
But as I haven't flashed an official nougat rom I can't say if this will all work or not. I'm going by past experience when I did this with jellybean - kitkat on my old phone.
Click to expand...
Click to collapse
thanks for reply.
but the one that i have was officially bought with nougat
Do you know where to get pit file for SM-G928G?
Hello there!
I'm still running the old Oreo firmware on my note 5 pro (global), but I've been having some issues and I feel its time for a reinstall.
However as far as I can see, every ROM under the sun requires the "new" (well, its not new anymore) Pie firmware, and as I understand it, that firmware brings a slight downgrade in battery life among other things, but it seems to depend upon which version is installed.
So, which version of the Pie firmware is considered the best as of now in terms of performance/battery and all that jazz.
Any advice would be very appriciated!
TwentyØnePenguins said:
Hello there!
I'm still running the old Oreo firmware on my note 5 pro (global), but I've been having some issues and I feel its time for a reinstall.
However as far as I can see, every ROM under the sun requires the "new" (well, its not new anymore) Pie firmware, and as I understand it, that firmware brings a slight downgrade in battery life among other things, but it seems to depend upon which version is installed.
So, which version of the Pie firmware is considered the best as of now in terms of performance/battery and all that jazz.
Any advice would be very appriciated!
Click to expand...
Click to collapse
11.0.3.0
or more detailed
miui_HMNote5Global_V11.0.3.0.PEIMIXM_ff4c5a6b1a_9.0
Good luck
TwentyØnePenguins said:
Hello there!
I'm still running the old Oreo firmware on my note 5 pro (global), but I've been having some issues and I feel its time for a reinstall.
However as far as I can see, every ROM under the sun requires the "new" (well, its not new anymore) Pie firmware, and as I understand it, that firmware brings a slight downgrade in battery life among other things, but it seems to depend upon which version is installed.
So, which version of the Pie firmware is considered the best as of now in terms of performance/battery and all that jazz.
Any advice would be very appriciated!
Click to expand...
Click to collapse
I've used many firmwares but 9.4.25 is best for me bcoz it shows correct battery specification while charging (4000 mAh)
Does firmware version make a noticable difference? Also, it's safe to downgrade Pie firmware?
Letrix said:
Does firmware version make a noticable difference? Also, it's safe to downgrade Pie firmware?
Click to expand...
Click to collapse
Not much, it is safe to downgrade without any brick (make sure u flash above 9.5.19)
Sidgup1998 said:
I've used many firmwares but 9.4.25 is best for me bcoz it shows correct battery specification while charging (4000 mAh)
Click to expand...
Click to collapse
This is what i've heard as well, (one on 9.xx but i dont remember which one it was, haha) but I figure it's safer to go with this and upgrade later if it gives me trouble. I am on ARB4 and I don't know how the different firmware versions play with it...
drnightshadow said:
11.0.3.0
or more detailed
miui_HMNote5Global_V11.0.3.0.PEIMIXM_ff4c5a6b1a_9.0
Good luck
Click to expand...
Click to collapse
Interesting, I don't think I've seen 11.xx recomended that much, have you found it to be better.
Also just generally I know this is a very nitpicky subject, but since Xiaomi has blessed their phones with ARB I really dont want to screw it up, need the phone to keep on working, haha
TwentyØnePenguins said:
This is what i've heard as well, (one on 9.xx but i dont remember which one it was, haha) but I figure it's safer to go with this and upgrade later if it gives me trouble. I am on ARB4 and I don't know how the different firmware versions play with it...
Interesting, I don't think I've seen 11.xx recomended that much, have you found it to be better.
Also just generally I know this is a very nitpicky subject, but since Xiaomi has blessed their phones with ARB I really dont want to screw it up, need the phone to keep on working, haha
Click to expand...
Click to collapse
Don't worry 9.4.25 is safe. It is arb 4
TwentyØnePenguins said:
This is what i've heard as well, (one on 9.xx but i dont remember which one it was, haha) but I figure it's safer to go with this and upgrade later if it gives me trouble. I am on ARB4 and I don't know how the different firmware versions play with it...
Interesting, I don't think I've seen 11.xx recomended that much, have you found it to be better.
Also just generally I know this is a very nitpicky subject, but since Xiaomi has blessed their phones with ARB I really dont want to screw it up, need the phone to keep on working, haha
Click to expand...
Click to collapse
It has newer blobs and vedors stuff. I'm using custom Q(android 10) ROM, soo I must using Q firmware for compatibility.
Besides that any ABR4 firmware is good to go.
Hello All,
It has been a while since I have been around the XDA forums, needless to say I needed a new user! haha. I used to run custom ROMs on older Samsung devices, but got out of the game when I could never pass safetynet. Needless to say, I have now stepped into the world of OnePlus, and so far I am impressed! I managed to snag a 9 Pro for a good price, but it is the Chinese version (Needed dual-SIM), meaning it came with Color OS.
I have already managed to "Downgrade" the Color OS to Oxygen OS using another thread here. Worked flawlessly other then the IEMI...It's currently on 11.2.2.2DA.
Is there anyone that has managed to swap from 11.2.2.2DA to BA? I don't really want to root at this moment (maybe ill get into that at a later date)
I do have an OTA file for 11.2.2.2BA but when I use the local update, it just says it can't upgrade to a lower version.
Any ideas?
Natester769 said:
Hello All,
It has been a while since I have been around the XDA forums, needless to say I needed a new user! haha. I used to run custom ROMs on older Samsung devices, but got out of the game when I could never pass safetynet. Needless to say, I have now stepped into the world of OnePlus, and so far I am impressed! I managed to snag a 9 Pro for a good price, but it is the Chinese version (Needed dual-SIM), meaning it came with Color OS.
I have already managed to "Downgrade" the Color OS to Oxygen OS using another thread here. Worked flawlessly other then the IEMI...It's currently on 11.2.2.2DA.
Is there anyone that has managed to swap from 11.2.2.2DA to BA? I don't really want to root at this moment (maybe ill get into that at a later date)
I do have an OTA file for 11.2.2.2BA but when I use the local update, it just says it can't upgrade to a lower version.
Any ideas?
Click to expand...
Click to collapse
You have to wait for the next version.
excute this command and you can install the BA vesion package on DA 11.2.2.2
Q: How do I switch to Europe or Global OS?
A: Wait for the new version, download the #Full package and Local Update it. If you have Magisk installed, you can try to Local Update after entering the following command (need ROOT access).
resetprop ro.build.date.utc 1400000000
resetprop ro.system.build.date.utc 1400000000
Wait for coloros to oxygenos step
Thanks for the quick replies,
It appears everything ColorOS wise always points towards the Indian Edition. Not that it isn't stable or anything, I think the UK Version covers more radio bands which may work better here in NA. I was under the impression once I am on OOS, I am no longer tied to anything COS...
I see that 11.2.3 is available as an OTA update, but I don't see any links yet. My history with rooting and roms was that I could always change to the same version or higher, just never lower. I'm doing this in my case, but maybe that is changed with Oneplus where it wants to see higher only.
I will just wait till a link for 11.2.3 is available from OTA and go from there!
Thanks.
Hello all,
As the 11.2.3.3 OTA update came out for BA today, I tried to perform a local update to get it to BA.
Looks like everything went great. IEMI is still broken due to the COS to OS swap, but it isn't really concerning to me at the moment. I have backups of the original so I should be good.
Just posting to let anyone who reads know!
Actaurian said:
excute this command and you can install the BA vesion package on DA 11.2.2.2
Q: How do I switch to Europe or Global OS?
A: Wait for the new version, download the #Full package and Local Update it. If you have Magisk installed, you can try to Local Update after entering the following command (need ROOT access).
resetprop ro.build.date.utc 1400000000
resetprop ro.system.build.date.utc 1400000000
Click to expand...
Click to collapse
Do you mean going into fastboot, and entering these commands, and then subsequently rebooting into system, and then try and local upgrade? Please be clear with these steps and descriptions.
Actaurian said:
执行此命令，即可在DA 11.2.2.2上安装BA vesion软件包。
问：如何切换到欧洲或全球操作系统？
答：等待新版本，下载#Full软件包并对其进行本地更新。如果安装了Magisk，则可以在输入以下命令（需要ROOT访问权限）后尝试进行本地更新。
resetprop ro.build.date.utc 1400000000
resetprop ro.system.build.date.utc 1400000000
Click to expand...
Click to collapse
Ťthanks!
Natester769 said:
Hello All,
It has been a while since I have been around the XDA forums, needless to say I needed a new user! haha. I used to run custom ROMs on older Samsung devices, but got out of the game when I could never pass safetynet. Needless to say, I have now stepped into the world of OnePlus, and so far I am impressed! I managed to snag a 9 Pro for a good price, but it is the Chinese version (Needed dual-SIM), meaning it came with Color OS.
I have already managed to "Downgrade" the Color OS to Oxygen OS using another thread here. Worked flawlessly other then the IEMI...It's currently on 11.2.2.2DA.
Is there anyone that has managed to swap from 11.2.2.2DA to BA? I don't really want to root at this moment (maybe ill get into that at a later date)
I do have an OTA file for 11.2.2.2BA but when I use the local update, it just says it can't upgrade to a lower version.
Any ideas?
Click to expand...
Click to collapse
Hi, I have an OP9 Pro China version with Color OS and I also want to flash it to Oxygen OS. The Color OS version of my OP9 Pro was upgraded to A.04 version. Please advise if I can flash my phone to 11.2.2.2DA. I am not sure if 11.2.2.2DA is the higher version or not (compared with Color OS A.04). Please also advise if you followed the instructions from the post on OP Chinese forum to flash your 9 pro to 11.2.2.2DA, then use the same method to flash it to 11.2.2.3BA. Have you tried to flash your 9 pro to the AA global version? Sorry for so many questions. I haven't flash ROM since OP3T and I forget how it works. Thanks.
waiwaifong said:
Hi, I have an OP9 Pro China version with Color OS and I also want to flash it to Oxygen OS. The Color OS version of my OP9 Pro was upgraded to A.04 version. Please advise if I can flash my phone to 11.2.2.2DA. I am not sure if 11.2.2.2DA is the higher version or not (compared with Color OS A.04). Please also advise if you followed the instructions from the post on OP Chinese forum to flash your 9 pro to 11.2.2.2DA, then use the same method to flash it to 11.2.2.3BA. Have you tried to flash your 9 pro to the AA global version? Sorry for so many questions. I haven't flash ROM since OP3T and I forget how it works. Thanks.
Click to expand...
Click to collapse
I basically followed this guide on getting COS to OOS. https://www.oneplusbbs.com/thread-5895784-1.html. I believe I was on version A.03 when I did the update, but I could have been on A.04. It was as easy as downloading the right firmware and applying it via a local update. It brought me right to 11.2.2.2DA. *This does seem to break IEMI*
I then used the 11.2.2.3BA version downloaded right from XDA, and applied it via a local update.
I have not gone to global as I need dual SIM. So I can't help you there....
Natester769 said:
I basically followed this guide on getting COS to OOS. https://www.oneplusbbs.com/thread-5895784-1.html. I believe I was on version A.03 when I did the update, but I could have been on A.04. It was as easy as downloading the right firmware and applying it via a local update. It brought me right to 11.2.2.2DA. *This does seem to break IEMI*
I then used the 11.2.2.3BA version downloaded right from XDA, and applied it via a local update.
I have not gone to global as I need dual SIM. So I can't help you there....
Click to expand...
Click to collapse
Thanks for your detailed reply. Will try soon.
Hi ,
Need advice on the best way to upgrade Android version on my new (really new) Pixel 3 XL- still waiting for it.
In the lights of latest news on "EDL Bug" bricking lots of Pixel 3 phones( just search the Internet for last few days ),
I started to doubt if purchasing it was a good idea. So either I return it right away (EBay purchase- 14 days return )
or try to risk it and install Android 10 only and then wait for stable Android 12.... from all of the research it looks like
security update for Android 11 can be the culprit here? Is it possible to jump /omit upgrading to certain versions like jumping
from ver 9 to ver 10 and later straight to ver 12, or does it have to be done in sequence ?
Sorry for a noob question ,,, but until now i was using only IPhone , and now decided to try Pixel devices.
If upgrade HAS to be done in sequence, then risk of Bricking it is too high and I rather return the device , loosing on
shipping only.
Thank you very much,
Lino
Anybody ?....
Please , I will need to make a decision as soon as I receive the new phone!
I am sure that there is a lots of people here, for whom this question is very trivial...
Can I upgrade from Android Pie straight to Android 12, OTA... or should I go in steps..
Thanks. Lino
you can flash the full factory image of android 12 beta, or android 11, whichever you prefer, and google made it easy using the online android flash tool. when using this, you don't need to go in steps whatsoever.
lino96 said:
Anybody ?....
Please , I will need to make a decision as soon as I receive the new phone!
I am sure that there is a lots of people here, for whom this question is very trivial...
Can I upgrade from Android Pie straight to Android 12, OTA... or should I go in steps..
Thanks. Lino
Click to expand...
Click to collapse
Im running the Scorpian Rom right now. Really do not know whats causing the bricks but im gonna stick to custom roms from here on out.
I'd go with Android 12. Either Beta 4.1, or wait a week or so for the public release. The EDL thing I read is only happening on Android 11, so I think you'll be safe updating to 12.
Ok , thank you all
I think when I receive the phone, I will update OTA to version 10 first , then I wait for official stable version 12
and Sideload it ? Yes? ....Sorry i am totally new to this...
So I have to unlock the bootloader first, do i have to root it ?... like using Majisk ? in order to sideload the stable
version 12 ?
Anybody has a links to good step by step tutorial ? Will appreciate it !
Anyway watching lately lots of you tube videos about unlocking etc,
Will appreciate any general pointers how to go about it, egz. what to do first , second etc.
Thank you, Lino
How is it possible pixel 6 pro to be faster and smoother on a beta version than stable android 12???
Fingerprint sensor is very good, brightness is higher than android 12 specially under sun and camera is far way more derailed than android 12 stable... Why is this happening? Are they trolling us?
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
NippleSauce said:
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
Click to expand...
Click to collapse
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
biohaz55 said:
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
Click to expand...
Click to collapse
Ok then Beta 2,1!
Noexcusses said:
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
Click to expand...
Click to collapse
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Alekos said:
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Click to expand...
Click to collapse
Hope so... Im on beta 2.1 also and i have realised brightness improvements and charging improvements too... Battery duration on 2.1 isn't so good as Android 12 but is fine as soon as is so early Beta.
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Lughnasadh said:
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Click to expand...
Click to collapse
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
NippleSauce said:
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
Click to expand...
Click to collapse
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
uicnren said:
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
Click to expand...
Click to collapse
Thank you for this! Unfortunately, downgrading the phone app to V81 didn't resolve the issue. I have also tried some of the other methods that were being discussed in that Reddit post but haven't had any luck with those tricks either.
I'm going to try removing myself from the Google Phone Beta next though. Worst comes to worst (if removing myself from the phone beta list doesn't work), I'll have to wait a few weeks for the next Android 13 beta update.
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Im not rooted sir
notnoelchannel said:
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
Click to expand...
Click to collapse
On android 13 beta 2,1 photos are much better than android 12...
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Amd4life said:
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Click to expand...
Click to collapse
It seems to be a known error after clean wipe updates to the latest A13 beta build based on @uicnren 's post. According to users on the Reddit thread, the issue has to do with the beta and a current OS build miscommunication with the phone carriers in the United States. So, if this is truly the case, users experiencing this issue won't have it resolved until the next beta build release (or later). Time will tell =)
I'm abut ready to jump in and load the 13 beta on my P6 and wanted to know it there are any hotspot issues since that would be the one deal breaker for me.
Does anyone know When would be next Beta update?
Thanks...