Related
Q&A for [ROM] [5.1.0] [AOSP Grogg's Way]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [5.1.0] [AOSP Grogg's Way]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I also made the plunge after CleanRom support was discontinued. Everything works great so far, awesome rom!!
TXJim said:
I also made the plunge after CleanRom support was discontinued. Everything works great so far, awesome rom!!
Click to expand...
Click to collapse
Same here. Running smoothly so far. Just got everything installed!
Is this ROM actually 5.1 ... cause google haven't released the factory image's yet...?
obsidianuk said:
Is this ROM actually 5.1 ... cause google haven't released the factory image's yet...?
Click to expand...
Click to collapse
I assure you, this is 5.1.0. It is not a modified factory image. Its AOSP compiled from source.
GROGG88 said:
I assure you, this is 5.1.0. It is not a modified factory image. Its AOSP compiled from source.
Click to expand...
Click to collapse
That miscellaneous category is in my battery stats again. Anyone else have it too? Doesn't seem to be draining battery, so I don't know what to make of it.
LucentBirch said:
That miscellaneous category is in my battery stats again. Anyone else have it too? Doesn't seem to be draining battery, so I don't know what to make of it.
Click to expand...
Click to collapse
Previous build had an option in dev settings that was added to remove unaccounted and overcounted stats from showing up. For some reason google only chooses to apply the changes to release builds. I removed that code to get a look at it, but you're right it is still there. I have re-committed the changes and have builds uploading in a bit.
GROGG88 said:
I assure you, this is 5.1.0. It is not a modified factory image. Its AOSP compiled from source.
Click to expand...
Click to collapse
Are you going to build again when the n7 2013 factory image is posted by google - or is there no point (I guess the real question is will there be specific changes for our device when the image is officially out?)
I'm trying to decided to flash now or wait... ☺
obsidianuk said:
Are you going to build again when the n7 2013 factory image is posted by google - or is there no point (I guess the real question is well there be specific changes for our device when the image is officially out?)
I'm trying to decided to flash now or wait...
Click to expand...
Click to collapse
Yes, I'll be building with new binaries and with whatever other changes may be implemented at that time...
obsidianuk said:
Are you going to build again when the n7 2013 factory image is posted by google - or is there no point (I guess the real question is will there be specific changes for our device when the image is officially out?)
I'm trying to decided to flash now or wait... ☺
Click to expand...
Click to collapse
My 2¢: flash now & start enjoying this incredibly smooth & fast ROM.
just a simple question: whenever u update this ROM, is it necessary/recommended to wipe the device again? or is the first wipe good enough?
and if its necessary, will the backup of all apps and system settings affect the performance after updating?
lucass001 said:
just a simple question: whenever u update this ROM, is it necessary/recommended to wipe the device again? or is the first wipe good enough?
and if its necessary, will the backup of all apps and system settings affect the performance after updating?
Click to expand...
Click to collapse
That really depends on the update.
@GROGG88 you say you're using elementalx kernel, right? Have you, or anyone else for that matter, had random reboots? I have at least 2 every day, if not more...
LucentBirch said:
@GROGG88 you say you're using elementalx kernel, right? Have you, or anyone else for that matter, had random reboots? I have at least 2 every day, if not more...
Click to expand...
Click to collapse
No random reboots on my N7
LucentBirch said:
@GROGG88 you say you're using elementalx kernel, right? Have you, or anyone else for that matter, had random reboots? I have at least 2 every day, if not more...
Click to expand...
Click to collapse
I have in the past, but currently I'm running my included kernel. Zero reboots...
USB OTG Support?
Does this have the ability to have dual charging and reading from a usb hub? I read the features and it didn't state that it did.
[email protected] said:
Does this have the ability to have dual charging and reading from a usb hub? I read the features and it didn't state that it did.
Click to expand...
Click to collapse
Then you have answered your own question. I do not hide features just so people are forced to question about them.
Hi thanks for the Rom works great.
One question is there a reason I lose all my none google email accounts in gmail when I upgrade to a new version?
nawo69 said:
Hi thanks for the Rom works great.
One question is there a reason I lose all my none google email accounts in gmail when I upgrade to a new version?
Click to expand...
Click to collapse
I'm not sure. I don't have non google contacts. Those should be stored in your data partition. Unless you're doing a wipe they should remain...
backup
I noticed you mentioned using backup apps with a clean install negates the wiping done. Is the same true for ADB and TWRP backups too?
https://download.lineageos.org/bacon
Currently Maintained by jrior001/
https://www.cyanogenmods.org/forums/topic-tag/jrior001/
Install instructions
https://wiki.lineageos.org/devices/bacon/install
Upgrade from official Lineage OS 14.1 possible but as usual clean install is better. Good time to wipe that phone clean.
Please update TWRP to the latest. If you have this device and don't know how to install please follow above procedure.
If you have device encryption enabled, consider removing as its a bit touch and go. As usual always have a full backup and separate copy of your data/pictures.
And the caveat you are responsible for what you do with your device applies and no one else is responsible for your action. People may be able to help if you ask kindly.
Official channel released finally on the 18th of July 2018.
Super effort by Devs specially jrior001, so please donate if you can.
PS I am just making this thread as there is none and it was released atleast 6 days ago and in no way taking any credit for the ROM or the work done by DEVS.
which is d stable twrp version???
jokermithun said:
which is d stable twrp version???
Click to expand...
Click to collapse
3.2.1-0
jokermithun said:
which is d stable twrp version???
Click to expand...
Click to collapse
I am sure you are joking but for those who dont know its 3.2.1-0
https://dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
Please select appropriate file and upgrade as image. If you dont know which file to use it means you need to read up more.
Is that cyanogenmods website some kind of fan site? It doesn't look official.
Kernel
Is anybody working on the included Kernel?
The background of my question is that I am experiencing spontaneous reboots when physically leaving a Wi-Fi connection, particularly my home Wi-Fi.
This defect was present in LineageOS 14.1 as well. There I could solve the problem completely by installing the latest Franco Kernel. However, in LineageOS 15.1 the Franco Kernel leads to very frequent soft reboots, like 5 in one hour, so I am now back on the stock kernel.
The only workaround I know is to disable Wi-Fi before leaving a Wi-Fi area, then re-enabling it.
Before other users jump in and state that they don't have this defect, not everybody has it. It is not clear under which conditions the defect shows up. It may depend on certain apps being present. But obviously it is not the apps' fault, as the fact proves that the Franco Kernel resolved it in LineageOS 14.1. Not to mention that no app has the right to reboot the system.
sn809 said:
I am sure you are joking but for those who dont know its 3.2.1-0
https://dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
Please select appropriate file and upgrade as image. If you dont know which file to use it means you need to read up more.
Click to expand...
Click to collapse
No sir....actually im nt frequent user of xda forums these days
NetGuard via VPN is not working for me. Under 14.1 was everything ok.
Hardware buttons backlighting is very dim for me even when set up to 100% brightness.
sn809 said:
PS I am just making this thread as there is none and it was released atleast 6 days ago and in no way taking any credit for the ROM or the work done by DEVS.
Click to expand...
Click to collapse
The Development section is for users to post their own development work, not links to the development work of others. Please refer to the sticky posted here and be sure to follow the forum rules.
THREAD CLOSED
hi guys,
i have a question about android. can i switch my rom to rolling release? thank you for your reply.
Need some more information here...
Unless I missed something idk what rolling release means?
"In software development, a rolling release, rolling update, or continuous delivery is the concept of frequently delivering updates to applications. This is in contrast to a standard or point release development model which uses software versions that must be reinstalled over the previous version."
sorry i dont know enough word to explain in english so i copied a bit and pasted. if you use a linux distro like arch linux, you just update packages like when you get play store updates and never get major updates like on ubuntu.
hajking said:
"In software development, a rolling release, rolling update, or continuous delivery is the concept of frequently delivering updates to applications. This is in contrast to a standard or point release development model which uses software versions that must be reinstalled over the previous version."
sorry i dont know enough word to explain in english so i copied a bit and pasted. if you use a linux distro like arch linux, you just update packages like when you get play store updates and never get major updates like on ubuntu.
Click to expand...
Click to collapse
Just install the alpha and beta version of the rom/firmware you would like for frequent updates.
But sadly it doesn't work like that on mobile, you get a huge update once a year and patches every month (if you are on "stable")
AWESOME1092387456 said:
Just install the alpha and beta version of the rom/firmware you would like for frequent updates.
But sadly it doesn't work like that on mobile, you get a huge update once a year and patches every month (if you are on "stable")
Click to expand...
Click to collapse
yeah im on latest miui tr and i get update every week but there must be a way i think.
hajking said:
yeah im on latest miui tr and i get update every week but there must be a way i think.
Click to expand...
Click to collapse
if our devices supported Project Treble we would be able to receive system-less updates, which are possible due to treble's A/B partition scheme (as far as i konw but i am not entirely sure)
AWESOME1092387456 said:
if our devices supported Project Treble we would be able to receive system-less updates, which are possible due to treble's A/B partition scheme (as far as i konw but i am not entirely sure)
Click to expand...
Click to collapse
thanx dude
AWESOME1092387456 said:
if our devices supported Project Treble we would be able to receive system-less updates, which are possible due to treble's A/B partition scheme (as far as i konw but i am not entirely sure)
Click to expand...
Click to collapse
Firstly, what's that "system-less" but still the updating of the "system"? Learn before talking and know what you're saying (no personal offense, btw).
Then again you're wrong as mi 6 doesn't have that a/b partition scheme (even though it's not that hard to repartition the device storage to have two boot and system partitions, you'll need to have or compile a new kernel that supports that partition and booting scheme - and we don't have that yet).
Treble will only let you to update your system without touching the separated vendor partition.
ccelik97 said:
Firstly, what's that "system-less" but still the updating of the "system"? Learn before talking and know what you're saying (no personal offense, btw).
Then again you're wrong as mi 6 doesn't have that a/b partition scheme (even though it's not that hard to repartition the device storage to have two boot and system partitions, you'll need to have or compile a new kernel that supports that partition and booting scheme - and we don't have that yet).
Treble will only let you to update your system without touching the separated vendor partition.
Click to expand...
Click to collapse
What i meant is we could update the phone without needing to do a full restart and i said "IF OUR DEVICE SUPPORTED PROJECT TREBLE" didn't you read the "IF"? And with "system-less" i meant mostly bugfixes that can be installed without the need of restarting the whole device as that particular service would for example shutdown and then start again and in this way we could receive security patches and minor stability updates, not full android releases or another version of miui (from v9 to v10) these kinds of upsates should still need to be performed through recovery, please next time read a response carefully before responding and i personally stated that i am not that sure either at the end of my response so don't just look for some keywords and then go bashing others for no reason.
AWESOME1092387456 said:
What i meant is we could update the phone without needing to do a full restart and i said "IF OUR DEVICE SUPPORTED PROJECT TREBLE" didn't you read the "IF"? And with "system-less" i meant mostly bugfixes that can be installed without the need of restarting the whole device as that particular service would for example shutdown and then start again and in this way we could receive security patches and minor stability updates, not full android releases or another version of miui (from v9 to v10) these kinds of upsates should still need to be performed through recovery, please next time read a response carefully before responding and i personally stated that i am not that sure either at the end of my response so don't just look for some keywords and then go bashing others for no reason.
Click to expand...
Click to collapse
Sorry my bad on that "if" part you're right.
But still, that's not a "system-less" solution but a "recovery-less" updating way as with the a/b partitioning what we get is not having to use anything other than the currently running system to apply the updates (and the ability to roll back to that very currently running system, is something goes wrong with the new)
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...
We all know the path OnePlus/Oppo went with development, MSM Tools and all, and I want to make it clear and short : I'm going to work on this phone no matter what. The OnePlus 10 series were a failure in this regard and I don't want the OnePlus 11 to experience the same.
I've been in this space for quite some years now, since Xperia X10 times and Android 2.3, and my last device has been a OnePlus 8 Pro that have provided me great service. Sadly, the battery is slowly dying and I can't bring myself to purchasing a phone I cannot tamper with. I've always loved OnePlus and I have hard times considering anything else.
If you're a developer, just wave at me using this thread. We need to know each other and work together to bring something to this phone. The obvious path would be to at least get a TWRP and a basic kernel built. I absolutely want to get to a LineageOS build.
If you're not a dev, but you have deep understanding on how fastboot, bootloader, and all else means, you can be a tester. I haven't bought the OnePlus 11 yet but I'm going to work on it and acquire it if some of you follow me.
If you're nether of these, you can still share the thread to other people to raise awareness.
I'll likely create a Telegram conversation if we get to a few devs. If you're interested in working on the OnePlus 11, please post a reply
@dekefake I've changed the prefix of your thread from "Development", for which it doesn't qualify, to "General"; do not revert that! Prior to your next posting, please read all announcements and guidances that are stuck at the top of every forum like
My phone android 8 m27 3 16 401 2v201U241a...
PS6IMG_PERF[email protected]60331.4_41.13_F_release_477358_combined_signed_2_4.zip...
forum.xda-developers.com
For example, you'll certainly easily recognise that only threads with own development qualify for the prefix "Development", and this doesn't apply to this thread.
dekefake said:
I'll likely create a Telegram conversation if we get to a few devs. If you're interested in working on the OnePlus 11, please post a reply
Click to expand...
Click to collapse
And a remark to your above statement: Regarding social media links please observe that as an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads and if thorough support is provided in the thread. Additional information is also available here:
Telegram Chat Channels - Way Forward
WhatsApp/Telegram Groups and Channels - Going Forward Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA. What does that mean? We will allow links to messages...
forum.xda-developers.com
If you intend to share links to Telegram, please only do so in your own development thread
Thanks for your future cooperation.
Regards
Oswald Boelcke
Senior Moderator
Are you sure TWRP would be necessary? We don't have it on the pixel 6 pro but the rom community is still large
Fingers crossed!
Adb sideload coop with OnePlus again!
Twrp is dead. Dont need it anymore
keaheng said:
Twrp is dead. Dont need it anymore
Click to expand...
Click to collapse
Not necessarily... It's still better and more practical without pc. But adb is good also
w_tapper said:
Are you sure TWRP would be necessary? We don't have it on the pixel 6 pro but the rom community is still large
Click to expand...
Click to collapse
zelos156 said:
Not necessarily... It's still better and more practical without pc. But adb is good also
Click to expand...
Click to collapse
keaheng said:
Twrp is dead. Dont need it anymore
Click to expand...
Click to collapse
Yes that's true, TWRP isn't really necessary anymore, but I feel like this small step would be quite a good start. Either way, having LineageOS booting is the most important and challenging task.
zelos156 said:
Fingers crossed!
Adb sideload coop with OnePlus again!
Click to expand...
Click to collapse
Lol yeah I really hope some devs and testers will join me on this.
Right. Able to boot lineage is the most important thing. Everything can be fixed with time.
dekefake said:
We all know the path OnePlus/Oppo went with development, MSM Tools and all, and I want to make it clear and short : I'm going to work on this phone no matter what. The OnePlus 10 series were a failure in this regard and I don't want the OnePlus 11 to experience the same.
I've been in this space for quite some years now, since Xperia X10 times and Android 2.3, and my last device has been a OnePlus 8 Pro that have provided me great service. Sadly, the battery is slowly dying and I can't bring myself to purchasing a phone I cannot tamper with. I've always loved OnePlus and I have hard times considering anything else.
If you're a developer, just wave at me using this thread. We need to know each other and work together to bring something to this phone. The obvious path would be to at least get a TWRP and a basic kernel built. I absolutely want to get to a LineageOS build.
If you're not a dev, but you have deep understanding on how fastboot, bootloader, and all else means, you can be a tester. I haven't bought the OnePlus 11 yet but I'm going to work on it and acquire it if some of you follow me.
If you're nether of these, you can still share the thread to other people to raise awareness.
I'll likely create a Telegram conversation if we get to a few devs. If you're interested in working on the OnePlus 11, please post a reply
Click to expand...
Click to collapse
keaheng said:
Twrp is dead. Dont need it anymore
Click to expand...
Click to collapse
It's not dead
AkayamiShurui said:
Click to expand...
Click to collapse
Hi ! Are you a developer ?
Let's goooo! Kernel source out for OP11
GitHub - OnePlusOSS/android_kernel_modules_and_devicetree_oneplus_sm8550
Contribute to OnePlusOSS/android_kernel_modules_and_devicetree_oneplus_sm8550 development by creating an account on GitHub.
github.com
oneplus 11 twrp install guide: https://www.bilibili.com/video/BV1Gv4y1r7Gv/
I develope the app and also update the video above.
Oneplus roms collection: https://op.daxiaamu.com (yes I maintained it)
I just pre-ordered the 11 and was lucky because I got a 100 Amazon gift card from Amazon so I can get a case and screen protectors I just hope we can get a working root soon I held off on upgrading my 8t because of lack of dual sim in us now one plus gave us dual sim and a bonus of esim so I can't wait as I use both sim slots I have a cheap plan on my main line and I get free unlimited data on my second sim which I need both so I'm happy
TWRP is necessary for NANDroid Backups, I'll join testing if come out.
Mine will be here Thursday. The sooner I can root / debloat etc, the better. I'm no dev, but I will be here testing.
daxiaamu said:
oneplus 11 twrp install guide: https://www.bilibili.com/video/BV1Gv4y1r7Gv/
I develope the app and also update the video above.
Oneplus roms collection: https://op.daxiaamu.com (yes I maintained it)
Click to expand...
Click to collapse
do you know how to save oneplus 11 in EDL mode ?
DonKilluminati23 said:
Mine will be here Thursday. The sooner I can root / debloat etc, the better. I'm no dev, but I will be here testing.
Click to expand...
Click to collapse
tnchng said:
TWRP is necessary for NANDroid Backups, I'll join testing if come out.
Click to expand...
Click to collapse
Okay nice. I don't think I'll try to build a TWRP first then. I may try to build a LineageOS build directly. Does someone here dumped an OxygenOS OP11 partition table including partition paths, names, and exact sizes ?
Okay well, I expected more engagement with this thread, and maybe some help..
Is there someone here with a rooted OnePlus 11 ? Or at least with unlocked BL ?
dekefake said:
Is there someone here with a rooted OnePlus 11 ? Or at least with unlocked BL ?
Click to expand...
Click to collapse
Unlocked bootloader: yes,
Root: Yes.
OP11, CPH2449_11_A.07.
What is it about?
qriozum said:
Unlocked bootloader: yes,
Root: Yes.
OP11, CPH2449_11_A.07.
What is it about?
Click to expand...
Click to collapse
Awesome !
To avoid any soft brick in the future while testing builds, we'd need to know exactly which fastboot features are enabled and which are not, starting with fastboot boot.
Could you please dump your recovery.img and boot.img, and try to fastboot boot each of them to confirm the phone is booting normally sideloading the boot.img, and booting in recovery correctly when sideloading recovery.img ?
Also, I currently have no idea of the partition layout of the OnePlus 11, is it the same as the OnePlus 8 Pro, or if things changed since then, it would be a good thing to dump information about the partition table, possibly using fastboot enhance. I've read in some other threads that someone needed to patch a partition called "init_boot", weighting 8mb, so maybe the kernel now resides in two different partitions : init_boot being the ramdisk and zImage being elsewhere. The best would be to gather more info about the partition table before trying any fastboot sideloading.
To begin, please install a terminal emulator, and type :
Bash:
su
ls -als /dev/block/bootdevice/by-name/ >> /sdcard/fstab.txt
Please upload the created fstab.txt file here