I have Oneplus 5, I was initially running Open Beta 14, I installed Mokee ROM for Android P and later again flashed OP5 to OxygenOS 5.1.3 Android 8.1 using Qualcom MSM Tool.
But I am not able to Flash Open Beta(s) now,, I tried Open beta 13 and 15, none worked.
I clean wiped using stock recovery, didnot work.
Wiped using TWRP by BluSparx 3.2.3 - vendor still not mounted( as it doesnot exists) and - still Open Beta not flashed after wipe.
I also switched to Android 7.1.1 and tried installing Open Beta 13 and 15 - still didnot work.
Please help me switch to Open Beta ROM for Oxygen OS Oneplus 5
First flash open beta 12 then you can flash ob 14 or 15.
Sent from my OnePlus 5 using XDA Labs
Any solution to this problem
a-jai said:
Any solution to this problem
Click to expand...
Click to collapse
Have you read the post above yours? It's mandatory to update to a special ob first so vendor partition will be created.
It's not made clear in the installation notes for OB14, 15, 16 etc but yes as @bkma says, you need to flash OB 12 first if you are coming from non-OB.
seanp25 said:
It's not made clear in the installation notes for OB14, 15, 16 etc but yes as @bkma says, you need to flash OB 12 first if you are coming from non-OB.
Click to expand...
Click to collapse
The problem is that oneplus did not implement clean flashing of every beta/stable. The updates are always seamless ota updates, hence its not possible for normal users to skip updates and continue with ob16 when coming from OB11 for example.
That's a thing people don't understand here. The process provided by oneplus is fool proof, but when you did not follow the official way, it can be hard, as always.
Therefore its not mentioned in later open beta changelogs or installation instructions. It was mentioned when vendor partition came up.
strongst said:
The problem is that oneplus did not implement clean flashing of every beta/stable. The updates are always seamless ota updates, hence its not possible for normal users to skip updates and continue with ob16 when coming from OB11 for example.
That's a thing people don't understand here. The process provided by oneplus is fool proof, but when you did not follow the official way, it can be hard, as always.
Therefore its not mentioned in later open beta changelogs or installation instructions. It was mentioned when vendor partition came up.
Click to expand...
Click to collapse
I see where you are coming from, and you're right, if you were on the Open Beta program all along, this is fool proof.
I bought a new OnePlus 5 about a month ago, I think OB14 was the latest beta release about then. I had not been messing around with rooting, 3rd party roms, kernels, twrp, anything like that. I was just looking for OnePlus official way to get on to the latest beta. It took me a bit of searching through old forum posts (posts which were made before the time I was even thinking of getting a OP5) to find out how to do it.
The information on the OnePlus website currently is insufficient for new beta users to install it from stable. (unless if you go digging through the old release notes) It's not a complaint, just pointing out that it is a subtlety of going to the latest OB that people would have to be aware of if they are new to the OP5 (or if they have recently decided to move from stable to beta).
Related
Well you all would have already know that-↓
Lineage 15 is released for our Z2 Plus and is also available for download
I tried to install that rom
But I was getting error 7 and then error 6 !!
But Somehow I managed to get rid from it installed the rom successfully as well as gapps but it's not booting up
:crying:
And yes I how did I manage to install it?
I was getting error 7 and error 6 then I opened the "update script" file into the rom and deleted all asserts coding and even then it did not work. So after trying for 2 to 3 times it installed easily but was not booting up.
Just want that if you guys can check it and somehow it boots up
Download link for Rom
https://yadi.sk/d/a-h59kHU3MThx6
Download link For Android 8.0 UNOFFICIAL GAPPS
http://www.lineageosroms.org/forums/topic/gapps-lineageos-15-android-oreo-roms/
For Source or Thread
http://www.lineageosroms.org/forums/topic/lineageos-15-zuk-z2-lenovo-z2-plus-android-oreo-8-0-rom/
I did not understand what you were doing
Nitink200 said:
Well you all would have already know that-↓
Lineage 15 is released for our Z2 Plus and is also available for download
[/SIZE]
I tried to install that rom
But I was getting error 7 and then error 6 !!
But Somehow I managed to get rid from it installed the rom successfully as well as gapps but it's not booting up
:crying:
Just want that if you guys can check it and somehow it boots up
You can find Source in LINEAGE ROMS WEBSITE
Click to expand...
Click to collapse
How did you finally manage to install the rom? Did you succeed? You did not write clearly. And where are the files located?
Wait for Oreo releases of the XDA Devs here instead of flashing untrusted stuff from the internet.
Z2 Plus is not officially supported by Lineage OS for now, so possibility of getting early builds is kind of unlikely, so please verify the source of the download once and refrain from flashing anything thats not released by our devs for now
I am new to XDA and That's why I was not permitted to add any external link to the rom (files) itself.
If I still can add external link so please tell me how to do it
And yes I how did I manage to install it?
I was getting error 7 and error 6 then I opened the "update script" file into the rom and deleted all asserts coding and then it did not work. So after trying for 2 to 3 times it installed easily but was not booting up.
Here's the link to download rom ↓↓
https://yadi.sk/d/a-h59kHU3MThx6
(This download link can also be located in thread itself)
And for thread in LINEAGE OS visit the link below↓↓
http://www.lineageosroms.org/forums/topic/lineageos-15-zuk-z2-lenovo-z2-plus-android-oreo-8-0-rom/
DISCLAIMER:
THIS IS AN INITIAL BUILD WHICH MAY NOT BOOT AT ALL. EVEN IF IT BOOTS, IT MAY HAVE MANY MORE BUGS THAN YOU CAN IMAGINE. HAVE A BACKUP BEFORE FLASHING THIS AND TRY AT YOUR OWN RISK.
Click to expand...
Click to collapse
Do you even read at all?
I have read it all and That's why posted a question here so that you guys can somehow make it bootable because I am too excited and Oreo is ported without boot related bugs even for the older device like Moto x 1st Gen then why not for our device?
Nitink200 said:
I have read it all and That's why posted a question here so that you guys can somehow make it bootable because I am too excited and Oreo is ported without boot related bugs even for the older device like Moto x 1st Gen then why not for our device?
Click to expand...
Click to collapse
calm yourself and just gently show patience.
the devs here on XDA are working on Oreo, check the Offical AEX thread, Davide stated that the next build is going to be Oreo.
I wouldn't flash any ROM without having the ability to see the source code atleast. The site you found the ROM at does not look legitime to me at all.
Who knows what it will do/did to your device.
I mean if you dont care..
calm yourself and just gently show patience.
the devs here on XDA are working on Oreo, check the Offical AEX thread, Davide stated that the next build is going to be Oreo.
I wouldn't flash any ROM without having the ability to see the source code atleast. The site you found the ROM at does not look legitime to me at all.
Who knows what it will do/did to your device.
I mean if you dont care..
Click to expand...
Click to collapse
Thanks
calm yourself and just gently show patience.
the devs here on XDA are working on Oreo, check the Offical AEX thread, Davide stated that the next build is going to be Oreo.
I wouldn't flash any ROM without having the ability to see the source code atleast. The site you found the ROM at does not look legitime to me at all.
Who knows what it will do/did to your device.
I mean if you dont care..
Click to expand...
Click to collapse
Thanks
I got a new OP5 (had a OP3). I unlocked the bootloader, installed TWRP, and was looking to root and load LOS 15.1.
I did that, sort of, but then got spooked because every zip I flashed, I got this error:
failed to mount partition '/vendor' (invalid argument)
I flashed back to stock and all seemed well, though I also got stock recovery. When I installed TWRP again and then a custom kernel, I got the same error. Then I couldn't boot with the custom kernel and now I'm headed back to stock.
When I go in to Mount in TWRP, it won't let me select vendor to be mounted.
What's causing that and how do I fix it?
TWRP is just complaining about the missing 'vendor' partition, that only exists in Project Treble ROMs. Therefore, there's nothing to fix. Ignore the error.
https://forum.xda-developers.com/showpost.php?p=76621704&postcount=285
That one has been modified to remove the warning.
As already wroted, it's just a "cosmetic" bug. Imho it's not a good thing to fix it: every time TRWP release a new patch of their software, you have to wait a lone programmer that modifies the new patch in order to remove this message error.
Consider also this: with next release of Android, named P for now, that is already available as beta for Oneplus 6, the project Treble will be mandatory and not optional as for Android Oreo. There are already some rumors that Oneplus 5/5T will receive update to Android P, and the problem with vendor partition will be gone forever.
Elleby said:
As already wroted, it's just a "cosmetic" bug. Imho it's not a good thing to fix it: every time TRWP release a new patch of their software, you have to wait a lone programmer that modifies the new patch in order to remove this message error.
Consider also this: with next release of Android, named P for now, that is already available as beta for Oneplus 6, the project Treble will be mandatory and not optional as for Android Oreo. There are already some rumors that Oneplus 5/5T will receive update to Android P, and the problem with vendor partition will be gone forever.
Click to expand...
Click to collapse
That's true, but till then, this lone programmer (me ) will patch any updated TWRP that is released so that the the error isn't displayed if you aren't on a treble-compatible ROM.
Thanks all. That makes sense, and also explains why I didn't see it previously with TWRP for OP3.
Elleby said:
As already wroted, it's just a "cosmetic" bug. Imho it's not a good thing to fix it: every time TRWP release a new patch of their software, you have to wait a lone programmer that modifies the new patch in order to remove this message error.
Consider also this: with next release of Android, named P for now, that is already available as beta for Oneplus 6, the project Treble will be mandatory and not optional as for Android Oreo. There are already some rumors that Oneplus 5/5T will receive update to Android P, and the problem with vendor partition will be gone forever.
Click to expand...
Click to collapse
Source of this, please?
Astur_Torque said:
Source of this, please?
Click to expand...
Click to collapse
Check out this article, point 3 under "Will my device benefit from Project Treble".
Official statement on Oneplus forum. That part in particular:
Over 135,000 of our users signed up to review the OnePlus 6 early via The Lab. With the OnePlus 6 device in their hands, they'll be among the first in our community to be able to download the Android P Build. (OnePlus 5/5T friends, we'll have something nice lined up for you later this year.)
Click to expand...
Click to collapse
For me that means that they will release Android P on Oneplus5/5T after the initial release for Oneplus 6.
And Project Treble mandatory, link on discussion on reddit. That part in particular:
Devices launching with Android O will come Treble-enabled out of the box.
Click to expand...
Click to collapse
shadowstep said:
Check out this article, point 3 under "Will my device benefit from Project Treble".
Click to expand...
Click to collapse
But there does not mention anything about that is compulsory Treble on Android P (on preoreo phones), just it says its compulsory on Oreo recent-released devices
Astur_Torque said:
But there does not mention anything about that is compulsory Treble on Android P (on preoreo phones), just it says its compulsory on Oreo recent-released devices
Click to expand...
Click to collapse
It's true for Android Oreo and above. Treble is the reason why there are Android P Betas available for non-Google devices. Also, here's an excerpt from this article: "Going forward, updates to phones will become far more common, as all devices that launch with Android Oreo or newer are required to implement Treble."
shadowstep said:
It's true for Android Oreo and above. Treble is the reason why there are Android P Betas available for non-Google devices. Also, here's an excerpt from this article: "Going forward, updates to phones will become far more common, as all devices that launch with Android Oreo or newer are required to implement Treble."
Click to expand...
Click to collapse
Yes I agree with you with that... However... "All devices launched with oreo"... One plus 5 is not one of those... Just 6 and incoming..
Enviado desde mi Oneplus 5 mediante Tapatalk
Astur_Torque said:
Yes I agree with you with that... However... "All devices launched with oreo"... One plus 5 is not one of those... Just 6 and incoming..
Click to expand...
Click to collapse
You're spot on. I never said that OP5/5T will definitely get Treble. Also, I'm not the OP, if you haven't realized that yet. OnePlus got away with having to mandatorily provide Treble to the OP5/5T by launching the device with Nougat (but making it upgradeable to Oreo) -- meaning that these devices don't come under the category of devices that launch with Android Oreo, thereby putting OnePlus under no compulsion to provide Treble to these devices. However, there are rumours that have been floating around that even though there is no compulsion, OnePlus is considering providing Treble to these devices.
Hi guys!
So I rooted my OP5, tested a few custom ROMs, decided to go back to the stock ROM. Installed the most recent stable version and now I tried to install a downloaded full Beta stock ROM and voila:
This package is for OnePlus 5 devices, this is OnePlus 5T
Do you have any guess what is the problem and how it can be corrected? Is it the TWRP's problem? I tried both the base version and codeworkx. What is my main fear the problem may persist even with any future stable versions.
Any insight is welcomed, thanks
I don't know what the updater script checks for. Could you send it to me so I can have a look? You find it somewhere inside the Meta-Inf folder inside the rom zip.
Hey man, thanks for the help, I solved the problem by installing Beta 12 first, THEN Beta 14 package. Well, I'm now subject to other problems, but that is the way of "hacking" phones
Biges said:
Hey man, thanks for the help, I solved the problem by installing Beta 12 first, THEN Beta 14 package. Well, I'm now subject to other problems, but that is the way of "hacking" phones
Click to expand...
Click to collapse
XD whatever does the job
I just picked up the 5 for a family member. She needs working Xposed (or rather, *I* need working Xposed to set everything up well), so no Pie. What is the latest Oreo I can get? The official ROM mirror thread lists 5.1.7 for stable and, for some reason, two open beta 21 zips. OOS has releases up to 5.1.11 on other Oneplus devices. Am I right in assuming they didn't release them for the 5? Is OB 21 farther along than 5.1.7? If so, which of the two zips should I be using? I apologize for posting, but neither search nor bruteforce reading of threads has yielded an answer.
The fixes listed in post-5.1.7 releases look valuable. "Fixed system stability issues", for one. Am I jut SOL on those?
Cheers,
-ln
lndck said:
I just picked up the 5 for a family member. She needs working Xposed (or rather, *I* need working Xposed to set everything up well), so no Pie. What is the latest Oreo I can get? The official ROM mirror thread lists 5.1.7 for stable and, for some reason, two open beta 21 zips. OOS has releases up to 5.1.11 on other Oneplus devices. Am I right in assuming they didn't release them for the 5? Is OB 21 farther along than 5.1.7? If so, which of the two zips should I be using? I apologize for posting, but neither search nor bruteforce reading of threads has yielded an answer.
The fixes listed in post-5.1.7 releases look valuable. "Fixed system stability issues", for one. Am I jut SOL on those?
Cheers,
-ln
Click to expand...
Click to collapse
You can find download links (including mirrors) of all the OxygenOS Oreo builds for the OnePlus 5 from here. OxygenOS 5.1.7 (the last stable build based on Android 8.1 Oreo) was released after OxygenOS Open Beta 21 (the last open beta build based on Android 8.1 Oreo), so I suggest you go for the stable build as it might have some patches that aren't there in the open beta build.
shadowstep said:
You can find download links (including mirrors) of all the OxygenOS Oreo builds for the OnePlus 5 from here. OxygenOS 5.1.7 (the last stable build based on Android 8.1 Oreo) was released after OxygenOS Open Beta 21 (the last open beta build based on Android 8.1 Oreo), so I suggest you go for the stable build as it might have some patches that aren't there in the open beta build.
Click to expand...
Click to collapse
Yeah, I've seen the mirror thread obviously - and even started trying to read all of it. It's brilliant. However, while it lists all of the available stock/OB zips, what it doesn't do is actually explain what they contain and the chronology, hence my questions. Thanks for the info, much appreciated. Would've taken me ages if not for your help mate
-lr
Released April 20, 2019 - 777.09MB
OmniROM Beta 1
Can it be installed on RNE-L21 (currently having OmniROM Pie Alpha 5.2)
Actually I am confused over EMUI version, Plz help shall I flash OmniROM Beta 1 from
fastboot and as per normal procedure described there
usman400 said:
Released April 20, 2019 - 777.09MB
OmniROM Beta 1
Can it be installed on RNE-L21 (currently having OmniROM Pie Alpha 5.2)
Actually I am confused over EMUI version, Plz help shall I flash OmniROM Beta 1 from
fastboot and as per normal procedure described there
Click to expand...
Click to collapse
I messed up, wrong post.
Edit: I've read that page and a believe you are good to go if you already are running one of their 9.0 builds
usman400 said:
Released April 20, 2019 - 777.09MB
OmniROM Beta 1
Can it be installed on RNE-L21 (currently having OmniROM Pie Alpha 5.2)
Actually I am confused over EMUI version, Plz help shall I flash OmniROM Beta 1 from
fastboot and as per normal procedure described there
Click to expand...
Click to collapse
I tested it, it does not start for us (emui 8.0).
*** it is only for emui 9.0 .
Chisetdel31260 said:
I tested it, it does not start for us (emui 8.0).
*** it is only for emui 9.0 .
Click to expand...
Click to collapse
Were you running one of the pie alpha builds?
AztekSoul said:
I messed up, wrong post.
Edit: I've read that page and a believe you are good to go if you already are running one of their 9.0 builds
Click to expand...
Click to collapse
Yup I am already on OmniROM Pie Alpha 5.2, which is Android 9 version
Thanks, I will give it a shot surely
I had 2 mate 10 RNE-L21 phones both having OmniROM Pie Alpha 5.2, so I tried OmniROM Beta 1 on one of
them and got bootloop on Factory Reset (it restarts around 20/25%)
usman400 said:
I had 2 mate 10 RNE-L21 phones both having OmniROM Pie Alpha 5.2, so I tried OmniROM Beta 1 on one of
them and got bootloop on Factory Reset (it restarts around 20/25%)
Click to expand...
Click to collapse
Yes, that's because you (we) need to wait the official update to Android 9 Pie, after that, we can flash these ROMs.
How is OmniROM Pie Alpha 5.2? Works fine? Battery life etc...?
davideakc said:
Yes, that's because you (we) need to wait the official update to Android 9 Pie, after that, we can flash these ROMs.
How is OmniROM Pie Alpha 5.2? Works fine? Battery life etc...?
Click to expand...
Click to collapse
Yup I was thinking like that as well
Yes ROM is very good, I am using it now on both phones, satisfied, only problem is stock camera
gets stuck if u switch between vdo/image, and some time even if u do not switch, still it will close after a while
So have to use Open camera or Google camera, for which I am not satisfied with both of them
usman400 said:
Yup I was thinking like that as well
Yes ROM is very good, I am using it now on both phones, satisfied, only problem is stock camera
gets stuck if u switch between vdo/image, and some time even if u do not switch, still it will close after a while
So have to use Open camera or Google camera, for which I am not satisfied with both of them
Click to expand...
Click to collapse
what about the microphone? recording and such? for instance, everytime I tried recording voice messages on Instagram or messenger it would always sound glitched/robotic
usman400 said:
Yup I was thinking like that as well
Yes ROM is very good, I am using it now on both phones, satisfied, only problem is stock camera
gets stuck if u switch between vdo/image, and some time even if u do not switch, still it will close after a while
So have to use Open camera or Google camera, for which I am not satisfied with both of them
Click to expand...
Click to collapse
Have you test this https://forum.xda-developers.com/pr...abled-device-development/9-0-omnirom-t3901305 ??
all I'd like to know is if there's any pie rom without the microphone problem
usman400 said:
Yup I was thinking like that as well
Yes ROM is very good, I am using it now on both phones, satisfied, only problem is stock camera
gets stuck if u switch between vdo/image, and some time even if u do not switch, still it will close after a while
So have to use Open camera or Google camera, for which I am not satisfied with both of them
Click to expand...
Click to collapse
How do you have installed the ROM?
I followed the guide on OpenKirin site but I'm stuck in the page says my device is unlocked and can't be trusted, I've pressed power key to confirm the boot but nothing, it says: "Your device is booting now" but it doesn't go on.
I've tried with another ROM (OmniROM Pie Alpha 5.2 and OmniROM Pie Alpha 4) but same error...
Why?
davideakc said:
How do you have installed the ROM?
I followed the guide on OpenKirin site but I'm stuck in the page says my device is unlocked and can't be trusted, I've pressed power key to confirm the boot but nothing, it says: "Your device is booting now" but it doesn't go on.
I've tired with another ROM (OmniROM Pie Alpha 5.2 and OmniROM Pie Alpha 4) but same error...
Why?
Click to expand...
Click to collapse
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
here you go, also the microphone isn't working in this Pie ROM either.
shevoK said:
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
here you go, also the microphone isn't working in this Pie ROM either.
Click to expand...
Click to collapse
I followed that guide but nothing.
Now I'm restoring it with eRecovery because the ROM doesn't start.
What you mean with "microphone isn't working"?
davideakc said:
I followed that guide but nothing.
Now I'm restoring it with eRecovery because the ROM doesn't start.
What you mean with "microphone isn't working"?
Click to expand...
Click to collapse
if you try recording a voice message, the sound is very glitchy and it has a lot of static in it, it's probably happening cause we don't officially have EMUI 9
tho it will release in july or late october for mate 10 lite
davideakc said:
I followed that guide but nothing.
Now I'm restoring it with eRecovery because the ROM doesn't start.
What you mean with "microphone isn't working"?
Click to expand...
Click to collapse
Hi,
I installed it on my rne-l21c432b338, then on b340 and on b341.
he always starts.
I use hurupdater to install the stock firmware. (check that you have the three firmware files of the same version.)
a faith installed, I go to REBOOT, select recovery. do factory rest and wipe cache. it restarts clean.
then connect to the PC.
with adb and fastboot, I install SYSTEM.img omnirom. (of course omnirom alpha 5.2
not the new version it is only for emui 9.)
faith flashed, unplug the cable and pushed it into recovery mode and make factory rest and wipe cache.
he starts for me.
Chisetdel31260 said:
Hi,
I installed it on my rne-l21c432b338, then on b340 and on b341.
he always starts.
I use hurupdater to install the stock firmware. (check that you have the three firmware files of the same version.)
a faith installed, I go to REBOOT, select recovery. do factory rest and wipe cache. it restarts clean.
then connect to the PC.
with adb and fastboot, I install SYSTEM.img omnirom.
faith flashed, unplug the cable and pushed it into recovery mode and make factory rest and wipe cache.
he starts for me.
Click to expand...
Click to collapse
In the past I had already installed a ROM from OpenKirin, but there was some problems with it and then I removed it with eRecovery. It has downloaded stock ROM (about 2,7GB if I remember right) and installed it. So I think I'm already on stock ROM (or am I wrong?)
Today I've tried to install 2 ROMs from OpenKirin and nothing happen, I get stuck on "The device is booting now..."
I've never used HuRUpdater (like I said before, I've always installed the stock ROM using eRecovery).
I don't understand what files I need (I know where to find files, here, but there I don't understand anything ahaha)
Probably is this the problem?
how do i upgrade to emui on my mate 10 pro is it even possible with an unlocked bootloader without relocking? the omnirom one is extremely laggy for me even the notificationpanel is extremely difficult to pull down, trying to install the latest rom thats for emui9 just gives a bootloop
Hi guys, sorry for posting here but I really need some help becasue I bricked my Mate 10 lite, here is a link for more explonation:
https://forum.xda-developers.com/mate-10/help/bricked-mate-10-lite-t3926714
Thanks in advance
shevoK said:
what about the microphone? recording and such? for instance, everytime I tried recording voice messages on Instagram or messenger it would always sound glitched/robotic
Click to expand...
Click to collapse
I never tried that thing, calls work fine on Phone and Whatsapp etc.