Related
Hi,
So, cm-13 is very unlikely on our device, but i'll take a look anyway (a slow look as my time is very limited).
Here you'll find my "work" and "help requests".
First, for sure i didn't "worked" on a lot of device, but it's the first one i have with a dedicated partition to the kernel dts.
Code:
/dev/block/platform/hi_mci.0/by-name/dts /dts emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/boot /boot emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/recovery /recovery emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/misc /misc emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem /modem emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem_dsp /modem_dsp emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/sensorhub /sensorhub emmc defaults recoveryonly
- I wonder if the dts, which is kernel dependent, could be the major problem to get a custom rom version (kk, jb, mm), or even a stock huawei rom, to work from any base rom. I'll try to make some experiment soon.
- I did sync cm-13, and "of course" have cwm recovery working. But whatever i'm trying i can't get screen output on twrp 3.0. Does someone have a clue on this?
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Cpasjuste said:
@codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
You're looking at the wrong account.
https://github.com/honor6-dev
Start recovery and have a look at /tmp/recovery.log.
Hint:
https://github.com/honor6-dev/andro...common/blob/cm-12.1/BoardConfigCommon.mk#L150
https://github.com/CyanogenMod/andr...mmit/7273770a9fedff12ca80135356c52fee06c8aba0
Cpasjuste said:
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
Yes, I still have this device! I'll write you via pm my nickname.
good luck you guys
i have really nothing to offer ..
but please make this happen ..
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Cpasjuste said:
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Click to expand...
Click to collapse
pls we wait for a long time:good:
It would be great to se cm no this device. Good luck and hope you make it. I would help if knew anything about programming but unfortanatly i dont
Cm we want... thank you for your interest!! ?
Kzyw said:
Cm we want... thank you for your interest!!
Click to expand...
Click to collapse
+1
why is there not one custom rom for this device?
Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Scruffykid said:
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
i too have wondered about this. im sure its possible but it might be far to difficult an endeavor because if it weren't, someone would have attempted it by now. i really miss my nexus 5 with all its custom roms. i suggest that all mate 7 owners get in contact with huawei and demand they comply with the android user agreement. they are technically supposed to give up sources. we could fight, but not unless we unite.
Yes we can! Yes we can! Yes we can!
Scruffykid said:
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
You're right, extracting stock binary files is an essential part of roms porting but some important files can't be inherited because they are strictly hardware-related, therefore you have to compile the original android source and then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
gabry3795 said:
...then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
Click to expand...
Click to collapse
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Scruffykid said:
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Click to expand...
Click to collapse
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
gabry3795 said:
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
Click to expand...
Click to collapse
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
droidbot1337 said:
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
Click to expand...
Click to collapse
I agree. If you get that account running let us know here so that we can support it.
Cheers! :good:
---------- Post added at 12:03 PM ---------- Previous post was at 11:32 AM ----------
droidbot1337 said:
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Click to expand...
Click to collapse
Agreed.
Unfortunately I live in a place where just picking up a new phone is not as easy as 123, But I think I'll try and get my hands on a different phone this weekend. Huawei pisses me off.
No source release by Huawei.
No Kirin SOC support would be a huge problem to get it working I think.
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Mikxx said:
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Click to expand...
Click to collapse
Good question.
At least one would need to repartition internal card, if I understood. This alone is not impossible but a bit hard and not without risk.
That said often I wonder if it could be possible to boot, say, TWRP (or any other Linux) from USB and take full dd backup of internal card for all certainty (and then repartition). This is how many Android TV boxes can be backed up (they use u-boot infrastructure). So why not phones?
Dior DNA said:
Good question.
At least one would need to repartition internal card, if I understood. This alone is not impossible but a bit hard and not without risk.
That said often I wonder if it could be possible to boot, say, TWRP (or any other Linux) from USB and take full dd backup of internal card for all certainty (and then repartition). This is how many Android TV boxes can be backed up (they use u-boot infrastructure). So why not phones?
Click to expand...
Click to collapse
indeed and that is what made me think, because aftervall, android is build upon lnnux
Mikxx said:
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Click to expand...
Click to collapse
This question has been discussed lots before.
https://forum.xda-developers.com/oneplus-5t/how-to/change-org-project-treble-op5t-t3709841
Implementing Project Treble would require repartitioning storage. Also, it gives literally zero benefit to a custom ROM.
TL;DR: It's never going to happen.
the Doctor said:
[...]Also, it gives literally zero benefit to a custom ROM.[...]
Click to expand...
Click to collapse
I mark these words. Have a nice day.
update
Perhaps there is no functional benefit. But porting seems easier for some devices:
What about :
https://www.xda-developers.com/samsung-galaxy-s9-aosp-android-oreo-project-treble/
This is the Samsung Galaxy S9 running on AOSP Android Oreo thanks to Project Treble
the Doctor said:
This question has been discussed lots before.
https://forum.xda-developers.com/oneplus-5t/how-to/change-org-project-treble-op5t-t3709841
Implementing Project Treble would require repartitioning storage. Also, it gives literally zero benefit to a custom ROM.
TL;DR: It's never going to happen.
Click to expand...
Click to collapse
But it happened ?
cubandanger05 said:
But it happened ?
Click to expand...
Click to collapse
Yup, somebody saw a mountain and decided to climb it. We'll see what comes of it.
Yeah mokee ROM has treble working on the OnePlus One 5T. There's an unused partition that can be created without re-partition in the device and if you install a regular ROM it doesn't see it you install a treble ready ROM and you previously had mokee installed according to the mokee dev it works. It uses the ab style of treble. There is an "a" and "ab" and "a/b" versions from what I read. Mokee is releasing nightlies of their ROM
Haven't tried it on mine pretty happy with the aicp Oreo that I'm running so I can't tell you what bugs it has. Google it XDA has a discussion on mokee and treble with OnePlus 5t
Hey
I was just wondering why there is not that many custom roms.
I come from a pocoophone and there was nearly daily new roms .
- not a lot of devs have this device
- people that do have this device don't have resources to build
- check telegram, there are roms, just ask around
Lossyx said:
- not a lot of devs have this device
- people that do have this device don't have resources to build
- check telegram, there are roms, just ask around
Click to expand...
Click to collapse
So you are saying that there are more roms for 7T than just these which are listed on XDA forum? Could you share some links to these telegram groups? Thx
pesa44 said:
So you are saying that there are more roms for 7T than just these which are listed on XDA forum? Could you share some links to these telegram groups? Thx
Click to expand...
Click to collapse
I don't know any specific, but I see them all the time. You can try joining 7/T series discussion group and ask what ROM people are using, and ask in kernel chats (that is specific to oneplus devices of course)
InvolveX said:
Hey
I was just wondering why there is not that many custom roms.
I come from a pocoophone and there was nearly daily new roms .
Click to expand...
Click to collapse
No hype, no sales, no development.
I bet OnePlus 6/6T is having more ROMs
Kind of wondered the same thing, also coming from a pocophone. I had planned to go custom, but now question if it is even worth it as there seems to be little support. I haven't run non-aosp on a phone in forever.
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
Also curious how you find these groups - only thing I know when it comes to telegram is clicking on a link to a chat.
Found a group, but of course no links to the chinese twrp. Only links I have found are on weibo and just end up looping around
Other people will disagree but having no working twrp is a big factor. Let's see what happens when OnePlus release there android 11 mash up maybe we will have twrp working and more interest ?
a g bell said:
Other people will disagree but having no working twrp is a big factor. Let's see what happens when OnePlus release there android 11 mash up maybe we will have twrp working and more interest ?
Click to expand...
Click to collapse
This TWRP works fine for flashing and decrypting on custom ROMs. So it's not that.
And Android 11 will not magically fix everything, if anything, it'll break things like encryption even more.
TWRP is has lots of progress as of late, fastbootd tools has been implemented, dynamic partitions are better handled. Only significant thing left would be ADB sideload.
Lossyx said:
This TWRP works fine for flashing and decrypting on custom ROMs. So it's not that.
And Android 11 will not magically fix everything, if anything, it'll break things like encryption even more.
TWRP is has lots of progress as of late, fastbootd tools has been implemented, dynamic partitions are better handled. Only significant thing left would be ADB sideload.
Click to expand...
Click to collapse
Decryption is still broken on oos ? which is a OnePlus issue which will they will still break on 11?
Flashing ROMs from oos is a big issue which is still broken with this twrp
a g bell said:
Decryption is still broken on oos ? which is a OnePlus issue which will they will still break on 11?
Flashing ROMs from oos is a big issue which is still broken with this twrp
Click to expand...
Click to collapse
The decryption is broken because of OnePlus poor implemention of keymaster. Android 11 is once again changing keymaster which will break decryption even on devices that can successfully decrypt on Android 10. This means it will take time for TWRP to properly support decryption on Android 11.
When that happens, decryption might work for 7T/Pro because now OnePlus has to reimplement the new keymaster,. hopefully right this time.
As for flashing ROMs, just use adb push on your PC and push it to /cache or /mnt, then you can flash easily.
Lossyx said:
The decryption is broken because of OnePlus poor implemention of keymaster. Android 11 is once again changing keymaster which will break decryption even on devices that can successfully decrypt on Android 10. This means it will take time for TWRP to properly support decryption on Android 11.
When that happens, decryption might work for 7T/Pro because now OnePlus has to reimplement the new keymaster,. hopefully right this time.
As for flashing ROMs, just use adb push on your PC and push it to /cache or /mnt, then you can flash easily.
Click to expand...
Click to collapse
Just out of interest as you mentioned previously there has been a lot of progress on the twrp front why has nobody shared it ? is the source all available on git to build or am l missing something here ?
a g bell said:
Just out of interest as you mentioned previously there has been a lot of progress on the twrp front why has nobody shared it ? is the source all available on git to build or am l missing something here ?
Click to expand...
Click to collapse
https://github.com/TeamWin/android_bootable_recovery/commits/android-10.0
https://gerrit.twrp.me/q/status:open+-is:wip
I can try to build a test twrp and post here. I won't test it myself though, don't have time for it-
Lossyx said:
https://github.com/TeamWin/android_bootable_recovery/commits/android-10.0
https://gerrit.twrp.me/q/status:open+-is:wip
I can try to build a test twrp and post here. I won't test it myself though, don't have time for it-
Click to expand...
Click to collapse
Might setup building environment again and have a go myself if you do get the time to build l will give it try
Regretting going back to windows now
cheers ?
a g bell said:
Might setup building environment again and have a go myself if you do get the time to build l will give it try
Regretting going back to windows now
cheers
Click to expand...
Click to collapse
I am pretty sure you can just use WSL / 2 on Windows if you don't have Linux installed.
Everything has been built and shared over the last year. Name a rom. It's been built already. If you want more android R roms, just wait they're coming. But... Twrp works fine. Even on oos. Use LR Team Twrp (aka chinese twrp) it works perfectly. Flash away or what knot, I have never heard anything about a broken keymaster. that's the first I heard of that one. Flash whatever, build whatever, enjoy phone fun.
FullOfHell said:
Everything has been built and shared over the last year. Name a rom. It's been built already. If you want more android R roms, just wait they're coming. But... Twrp works fine. Even on oos. Use LR Team Twrp (aka chinese twrp) it works perfectly. Flash away or what knot, I have never heard anything about a broken keymaster. that's the first I heard of that one. Flash whatever, build whatever, enjoy phone fun.
Click to expand...
Click to collapse
Chinese twrp does not decrypt on stock oos properly unless there has been a new build recently ?
Has du been been built ?
a g bell said:
Chinese twrp does not decrypt on stock oos properly unless there has been a new build recently ?
Has du been been built ?
Click to expand...
Click to collapse
It absolutely does decrypt on oos. One must do a full format in twrp first. Then it works perfectly, every feature, 100%. Yes, I did du for 7t in December last year, or January.
FullOfHell said:
It absolutely does decrypt on oos. One must do a full format in twrp first. Then it works perfectly, every feature, 100%. Yes, I did du for 7t in December last year, or January.
Click to expand...
Click to collapse
Indeed it does you do a full format it works but then reboot and it's the same won't mount anything same as before.
a g bell said:
FullOfHell said:
It absolutely does decrypt on oos. One must do a full format in twrp first. Then it works perfectly, every feature, 100%. Yes, I did du for 7t in December last year, or January.
Click to expand...
Click to collapse
Indeed it does you do a full format it works but then reboot and it's the same won't mount anything same as before.
Click to expand...
Click to collapse
Funny I have had no problems for 10 months, on oos or custom.
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...
hello everyone, i want to buy this devie but as i see i cant install twrp!
if i can ask why? is it bc of oneplus or no devs to do it? also thx for all devs
i buy the phone for customs and roms and twrp and rooting and this things, this is my priorities
and is this device fully supported for development? any twrp coming soon?
and what about customs here? is they easy to install?
is this device good for gaming and daily use?
Evon88 said:
hello everyone, i want to buy this devie but as i see i cant install twrp!
if i can ask why? is it bc of oneplus or no devs to do it? also thx for all devs
i buy the phone for customs and roms and twrp and rooting and this things, this is my priorities
and is this device fully supported for development? any twrp coming soon?
and what about customs here? is they easy to install?
is this device good for gaming and daily use?
Click to expand...
Click to collapse
What device and firmware?
TheGhost1951 said:
What device and firmware?
Click to expand...
Click to collapse
i want to buy normal OP9P
Evon88 said:
i want to buy normal OP9P
Click to expand...
Click to collapse
The OnePlus 9 pro is good for customizing!
@Evon88, the fact is, TWRP hasn't been updated to properly support Android 12, at least not on the 9 Pro, and I'm beginning to suspect that it never will be. IMHO, it looks to me like encryption and other issues introduced by Google have simply gotten the best of the TWRP team. I'll be happy to be proven wrong, and will be pleasantly surprised if TWRP is updated to work with Android 12 and above, but right now, that remains in the realm of wishful thinking.
The good news is that the recoveries included with most Android 12 ROMs (based on the AOSP recovery) are functional, and are capable of doing the minimum work of flashing new ROMs and upgrades (i.e. Magisk and Gapps) just like TWRP. They certainly don't have the wealth of features that TWRP has (such as the ability to wipe only the data partition without erasing the media partition; it's either all or nothing), but then, they weren't designed to have them. I keep hoping that someone will take the AOSP recovery and use it as a base for a recovery that includes more of TWRP's features. (I'd do it if I had the knowledge. I'm knowledgeable enough to poke at AOSP and cherry pick features to create a custom ROM, but the intimate knowledge required to work with the recovery code is something I don't have.)
Evon88 said:
hello everyone, i want to buy this devie but as i see i cant install twrp!
if i can ask why? is it bc of oneplus or no devs to do it? also thx for all devs
i buy the phone for customs and roms and twrp and rooting and this things, this is my priorities
and is this device fully supported for development? any twrp coming soon?
and what about customs here? is they easy to install?
is this device good for gaming and daily use?
Click to expand...
Click to collapse
You can in fact install and boot TWRP. But you can't do almost anything in it... But this isn't OP9P problem but every phone with Android 12 and encryprion enabled. But as other said, TWRP isn't needed for flashing custom ROMs.
Evon88 said:
i want to buy normal OP9P
Click to expand...
Click to collapse
Don't let lack of twrp hold you back. It's a fun phone. I use it for gaming (CODM) on Android 11.2.10.10 just fine. I may end up flashing an old build of crDroid for Android 11 but I'm pretty happy with how everything is set up on regular OOS now and don't want to lose L1 and start back over.
Unlocked bootloader✓
Root/Magisk✓
SafetyNet✓
Netflix, GPay, Banking apps✓
L1 Widevine✓
Real OOS✓
65w charging✓
120hz LTPO✓
No Dual Sim
The tmobile variant is still for sale on ebay at $469 brand new in the box or from OnePlus directly (also Tmo variant) for $499
MJPollard said:
@Evon88, the fact is, TWRP hasn't been updated to properly support Android 12, at least not on the 9 Pro, and I'm beginning to suspect that it never will be. IMHO, it looks to me like encryption and other issues introduced by Google have simply gotten the best of the TWRP team. I'll be happy to be proven wrong, and will be pleasantly surprised if TWRP is updated to work with Android 12 and above, but right now, that remains in the realm of wishful thinking.
The good news is that the recoveries included with most Android 12 ROMs (based on the AOSP recovery) are functional, and are capable of doing the minimum work of flashing new ROMs and upgrades (i.e. Magisk and Gapps) just like TWRP. They certainly don't have the wealth of features that TWRP has (such as the ability to wipe only the data partition without erasing the media partition; it's either all or nothing), but then, they weren't designed to have them. I keep hoping that someone will take the AOSP recovery and use it as a base for a recovery that includes more of TWRP's features. (I'd do it if I had the knowledge. I'm knowledgeable enough to poke at AOSP and cherry pick features to create a custom ROM, but the intimate knowledge required to work with the recovery code is something I don't have.)
Click to expand...
Click to collapse
Bugscze said:
You can in fact install and boot TWRP. But you can't do almost anything in it... But this isn't OP9P problem but every phone with Android 12 and encryprion enabled. But as other said, TWRP isn't needed for flashing custom ROMs.
Click to expand...
Click to collapse
There's a user/team on the >OnePlus 6 & 6T forums<, that has had success with Android 12 and 13 decrypt, I use it on my 6T, and decrypt works flawlessly, I use it to flash Magisk when changing/updating ROMs.
It's Unofficial however, I hope it trickles to other devices.
Appreciative said:
Don't let lack of twrp hold you back. It's a fun phone. I use it for gaming (CODM) on Android 11.2.10.10 just fine. I may end up flashing an old build of crDroid for Android 11 but I'm pretty happy with how everything is set up on regular OOS now and don't want to lose L1 and start back over.
Unlocked bootloader✓
Root/Magisk✓
SafetyNet✓
Netflix, GPay, Banking apps✓
L1 Widevine✓
Real OOS✓
65w charging✓
120hz LTPO✓
No Dual Sim
The tmobile variant is still for sale on ebay at $469 brand new in the box or from OnePlus directly (also Tmo variant) for $499
Click to expand...
Click to collapse
thank you sir, what about chinese version? u recommend it? im pro at rooting and customs and msm, if the problem is just roms, i see used chinese new mobile, u recommend me to buy?
deleted
MJPollard said:
@Evon88, the fact is, TWRP hasn't been updated to properly support Android 12, at least not on the 9 Pro, and I'm beginning to suspect that it never will be. IMHO, it looks to me like encryption and other issues introduced by Google have simply gotten the best of the TWRP team. I'll be happy to be proven wrong, and will be pleasantly surprised if TWRP is updated to work with Android 12 and above, but right now, that remains in the realm of wishful thinking.
The good news is that the recoveries included with most Android 12 ROMs (based on the AOSP recovery) are functional, and are capable of doing the minimum work of flashing new ROMs and upgrades (i.e. Magisk and Gapps) just like TWRP. They certainly don't have the wealth of features that TWRP has (such as the ability to wipe only the data partition without erasing the media partition; it's either all or nothing), but then, they weren't designed to have them. I keep hoping that someone will take the AOSP recovery and use it as a base for a recovery that includes more of TWRP's features. (I'd do it if I had the knowledge. I'm knowledgeable enough to poke at AOSP and cherry pick features to create a custom ROM, but the intimate knowledge required to work with the recovery code is something I don't have.)
Click to expand...
Click to collapse
thank you bro for explain, what do you think about chinese OP9P? i can change the rom, 5G i dont care that much, anthing else? is quality the same like hardware and plastic and fiber and this things? i mean phone body and screen
Bugscze said:
You can in fact install and boot TWRP. But you can't do almost anything in it... But this isn't OP9P problem but every phone with Android 12 and encryprion enabled. But as other said, TWRP isn't needed for flashing custom ROMs.
Click to expand...
Click to collapse
thanks, <3
Evon88 said:
thank you sir, what about chinese version? u recommend it? im pro at rooting and customs and msm, if the problem is just roms, i see used chinese new mobile, u recommend me to buy?
Click to expand...
Click to collapse
All of them are made in china and I think will be good quality OnePlus phone. I don't know if they use anything different (except rom). You can change from colorOS to oxygenOS
twrp not needed
vincemue said:
twrp not needed
Click to expand...
Click to collapse
Needed, maybe not. Desired, definitely. It can do a lot of things that the stock and AOSP recoveries simply can't (to name just one: it can wipe data without wiping storage, as I mentioned above; stock/AOSP recoveries' "factory reset" wipe destroys everything).
MJPollard said:
@Evon88, the fact is, TWRP hasn't been updated to properly support Android 12, at least not on the 9 Pro, and I'm beginning to suspect that it never will be. IMHO, it looks to me like encryption and other issues introduced by Google have simply gotten the best of the TWRP team. I'll be happy to be proven wrong, and will be pleasantly surprised if TWRP is updated to work with Android 12 and above, but right now, that remains in the realm of wishful thinking.
The good news is that the recoveries included with most Android 12 ROMs (based on the AOSP recovery) are functional, and are capable of doing the minimum work of flashing new ROMs and upgrades (i.e. Magisk and Gapps) just like TWRP. They certainly don't have the wealth of features that TWRP has (such as the ability to wipe only the data partition without erasing the media partition; it's either all or nothing), but then, they weren't designed to have them. I keep hoping that someone will take the AOSP recovery and use it as a base for a recovery that includes more of TWRP's features. (I'd do it if I had the knowledge. I'm knowledgeable enough to poke at AOSP and cherry pick features to create a custom ROM, but the intimate knowledge required to work with the recovery code is something I don't have.)
Click to expand...
Click to collapse
I was on LE2127_11_C20 A12 with tarp and root.......the mail reason it worked was no lock screen security. I did try with setting a password is be cause a script to try and make partitions R/W but that put me in a bootloader loop. Went back to 11.2.9.9..
Did you follow a YouTube tutorial step by step guide to see if you made any mistakes?
dartballs said:
Did you follow a YouTube tutorial step by step guide to see if you made any mistakes?
Click to expand...
Click to collapse
Who are you asking?
Appreciative said:
Don't let lack of twrp hold you back. It's a fun phone. I use it for gaming (CODM) on Android 11.2.10.10 just fine. I may end up flashing an old build of crDroid for Android 11 but I'm pretty happy with how everything is set up on regular OOS now and don't want to lose L1 and start back over.
Unlocked bootloader✓
Root/Magisk✓
SafetyNet✓
Netflix, GPay, Banking apps✓
L1 Widevine✓
Real OOS✓
65w charging✓
120hz LTPO✓
No Dual Sim
The tmobile variant is still for sale on ebay at $469 brand new in the box or from OnePlus directly (also Tmo variant) for $499
Click to expand...
Click to collapse
The Indian variant has dual SIM. Maybe some others variants, too.