I'm having trouble following the official instructions for installing the open beta for OOS13 onto me LE2125. I downloaded the apk through the link in the instructions, but curiously it had a .zip extension after the .apk extension. I tried deleting the zip extension, and installing the file as I would any other apk, but the app did not match the description in the instructions. First, it was called "MyApplication2," and second, the interface was different. There's no gear icon in the upper right, just a single button:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I tap the button, and select the installation file, the app immediately crashes. Clearly I'm doing something wrong, but I'm not sure what, and from past experience I thought XDA would be more helpful than OP tech support. Any suggestions?
I can't be certain about this process becuase I don't have OOS on my phone, but the installation instruction you linked talks about a ZIP file, rather than an APK:
Download the latest ROM upgrade zip package from the specified server.
Click to expand...
Click to collapse
In step 4 it tells you how to handle/what to do with it.
Normally, I have updated through the Oxygen Updater app and not how the official instructions tell you to. Seems to be a lot easier and they have easy to follow instructions for updating locally, as well as their own version of that- using official update files, of course.
kodayoda713 said:
Normally, I have updated through the Oxygen Updater app and not how the official instructions tell you to. Seems to be a lot easier and they have easy to follow instructions for updating locally, as well as their own version of that- using official update files, of course.
Click to expand...
Click to collapse
Thank you, Oxygen Updater is working better than the official APK.
I would also like to know since it's a beta if there would be a different procedure with updating. I'm rooted on open beta 1 and I can simply install ob2 with oxygen updater or system update then just flash magisk modified boot, correct?
Arcide said:
I would also like to know since it's a beta if there would be a different procedure with updating. I'm rooted on open beta 1 and I can simply install ob2 with oxygen updater or system update then just flash magisk modified boot, correct?
Click to expand...
Click to collapse
That's the problem, I had to unroot, then it started working.
mustangtim49 said:
That's the problem, I had to unroot, then it started working.
Click to expand...
Click to collapse
Unroot before updating?
Related
Hey there, I'm having trouble updating the lineageOS nightlies on my oneplus 2. I (clean!) flashed lineage-14.1-20170209-microg-oneplus2 first and had this problem there.. (just like this guy https://forum.xda-developers.com/general/xda-assist/lineage-os-14-1-check-update-internet-t3554440)
Then I tried flashing the current newest nightly, lineage-14.1-20170213-microg-oms-oneplus2... My problem is still existing, I can't manually update my OS.
screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update
Using the updater I have no luck at all. Just corrupted zip file message - running clark nightly on moto x pure with lineage os superuser and twrp but no other mods or tweaks or whatever. Then I i stumbled upon lineage OS changelog app in the play store and boom, easy smooth updates. I am a noob compared to most here, no developer, a nothing to do with any apps. This worked for me.
randymont77 said:
Using the updater I have no luck at all. Just corrupted zip file message - running clark nightly on moto x pure with lineage os superuser and twrp but no other mods or tweaks or whatever. Then I i stumbled upon lineage OS changelog app in the play store and boom, easy smooth updates. I am a noob compared to most here, no developer, a nothing to do with any apps. This worked for me.
Click to expand...
Click to collapse
Do you mean the "LineageOS Changelog" app by Vasudev B? (I'd post a playstore link but I'm unable to do so right now cause I'm new.)
I installed it but all I can do is to download the nightlies I click on with my browser.. Thats just like I'd download it on my pc and flash it on my op2.. no difference. I'm searching for a solution why I can't update LOS without manually installing it on my device and flashing it just like it worked on CM14/14.1 or simply the stock ROM for the op2...
Yakumichan said:
Do you mean the "LineageOS Changelog" app by Vasudev B? (I'd post a playstore link but I'm unable to do so right now cause I'm new.)
I installed it but all I can do is to download the nightlies I click on with my browser.. Thats just like I'd download it on my pc and flash it on my op2.. no difference. I'm searching for a solution why I can't update LOS without manually installing it on my device and flashing it just like it worked on CM14/14.1 or simply the stock ROM for the op2...
Click to expand...
Click to collapse
Yes that is the app. No it isn't quite automatic. Eiher that app itself, ROM toolbox or something i can't think of off of the top of my head picks it up right away but I still need to make a couple of button pushes. I think i could automate the process with an app but I am so new to this I haven't tried. The weekly update is still an adventure that I enjoy lol.
So I was driving back yesterday and my phone notifies me that I'm reaching my data limit. I thought, "That's odd, I've only used 0.1 GB". So I look down and see this monstrosity of data being used by the damn Android OS. How the heck can you see what would individually be using data in the "Android OS" package cause it could be any number of things. I'm guessing it could have been a system update pull but I did disable OTA updates in developer settings. I have root as well and I would like to freeze that process with Titanium Backup if anyone knows what that process might be on the Pixel. Also any other suggestions as how to further troubleshoot this would be appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's the update pull even though you are updated. We have seen this a few times with others. Get it updated.
TonikJDK said:
It's the update pull even though you are updated. We have seen this a few times with others. Get it updated.
Click to expand...
Click to collapse
Well when I go to system update and choose to install update it says that it failed. Any advice on that? Can you not properly install updates while rooted?
In terms of updating to the latest OTA I followed How To Geeks - FlashFire Guide which put my device into a endless bootloop so I don't recommend doing that.
Still looking to see if anyone knows what to freeze in Titanium Backup on Pixel to block OTA updates from downloading. Thanks.
ThePieMonster said:
Well when I go to system update and choose to install update it says that it failed. Any advice on that? Can you not properly install updates while rooted?
Click to expand...
Click to collapse
You must of modded something that is stopping it. There is a way to sideload the OTA, but the third post in the thread below is how I do it each month. Have ro reroot afterwards.
Pay attention to the part where you remove the-w from flashall bat file. That is what saves your data.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
TonikJDK said:
You must of modded something that is stopping it. There is a way to sideload the OTA, but the third post in the thread below is how I do it each month. Have ro reroot afterwards.
Pay attention to the part where you remove the-w from flashall bat file. That is what saves your data.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
I ended up flashing the original stock ROM off Google's website and then went threw the systemless root methods mentioned here.
I now have the below:
Android: 7.1.1 ROM: Factory (Rooted) Kernel: 3.18.31-ElementalX-P-1.08 Build: NOF27B
im having tons of data through the same thing. I ran a data manager app and it said its google.uid.system:1000 . I reset the rom to original as I have not installed any other rom then googles originals. I have some of the highest data downloads its crazy. I even turned off back up picture folders. Here is the data.
Hello,
I rooted my mi6 a few months ago. Last time it automatically updated to MIUI 9.2.2
Now when I try to update it to 9.2.3 after pressing "reboot" it boots into TWRP:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and then when I press reboot and system it boots but the it doesn't update.
what can I do?
Thank you
qrafzv said:
Hello,
I rooted my mi6 a few months ago. Last time it automatically updated to MIUI 9.2.2
Now when I try to update it to 9.2.3 after pressing "reboot" it boots into TWRP:
and then when I press reboot and system it boots but the it doesn't update.
what can I do?
Thank you
Click to expand...
Click to collapse
Donwload the update manually via miui site and flash it via twrp.
OTA only works on stock recovery. If you had done a quick research you would've found that.
Buthmann said:
Donwload the update manually via miui site and flash it via twrp.
OTA only works on stock recovery. If you had done a quick research you would've found that.
Click to expand...
Click to collapse
They also need to update that twrp version.
Official is up to 3.2.1 now....
So how come last update it worked without doing it manually?
And if I want to remove TWRP, how do i do that?
qrafzv said:
And if I want to remove TWRP, how do i do that?
Click to expand...
Click to collapse
You will have to use "Mi Flash" and then re flash the official rom you like.
wildger said:
You will have to use "Mi Flash" and then re flash the official rom you like.
Click to expand...
Click to collapse
will it wipe all my data?
qrafzv said:
will it wipe all my data?
Click to expand...
Click to collapse
Yes it will.
I don't understand that is wrong. First i have beta (developer) rom and after oreo first update have echo of conversation. Back to stable Rom. 9.2.2 and was good. Now stable Rom have update to oreo and then update Rom again echo of conversation. Back to 9.2.2. stable... But i want oreo. You don't haved problems?
how do i know which version of magisk patched boot img to flash? i recently updated to the newest version via OTA on stock, but i forgot to run the install again before rebooting, would it be the 12.C47 version that i flash?
The one which fits the OOS version number. So, if it's C47 then you need a boot.img made for C47 (patched with magisk).
ekin_strops said:
The one which fits the OOS version number. So, if it's C47 then you need a boot.img made for C47 (patched with magisk).
Click to expand...
Click to collapse
ah i see, thanks!
Veid71 said:
how do i know which version of magisk patched boot img to flash? i recently updated to the newest version via OTA on stock, but i forgot to run the install again before rebooting, would it be the 12.C47 version that i flash?
Click to expand...
Click to collapse
Settings > About Device > Version > Build Number
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure you've done all the OEM Unlock, etc first
djsubterrain said:
Settings > About Device > Version > Build Number
View attachment 5587231
Make sure you've done all the OEM Unlock, etc first
Click to expand...
Click to collapse
Thanks man, I was able to flash it and install, I enabled zygisk and put a bunch of apps on the deny list but for some reason I'm still failing YASNC for both basic and CTS I know it's off topic but any advice on how to fix that?
Veid71 said:
Thanks man, I was able to flash it and install, I enabled zygisk and put a bunch of apps on the deny list but for some reason I'm still failing YASNC for both basic and CTS I know it's off topic but any advice on how to fix that?
Click to expand...
Click to collapse
Jump in here :
Magisk
Magisk - The Universal Systemless Interface, to create an altered mask of the system without changing the system itself.
forum.xda-developers.com
Just Incase anyone else runs into this issue on that magisk forum there's a universal safetynet fix (UNSF) that you can download and it'll fix it
After being tortured over months by the converted Chinese OP11. I think I finally found a acceptable way to make my OP11 less Chinese more google without suffering auto brightness issue and random reboot.
After the following steps you will have a Clean Oxygen OS like Color OS, absolutely no oneplus Chinese apps, full Gapps (android auto working), no risks of get bricked after OTA (need to flash the my_xxx.img again after OTA though)
Clean flash PH110 COS A.11
Extract all the my_xxxx.img from the OOS payload.bin, I extracted the following img
my_stock.img
my_product.img
my_preload.img
my_heytap.img
my_bigball.img
Boot into fastbootd, using fastboot enhance to flash into the corresponding partitions.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Format Data after flashing and reboot, skip the wifi setting to avoid being stuck at the google setup wizard, then you will have a Oxygen Os like Color OS.
Things not working:
Google discover feed (disappered from the launcher, might be a way to get it back in settings)
Oroaming (might work after reinstalling the Chinese softesimredtearoaming.apk)
does "hey google" work and google assistant work as the default?
no more Breeno?
Thank you
Does push notifications of (Gmail, Messenger, Yahoo mail and etc) works fine?
does that google timeline can work?
its must be have lot of issue coz BL & modem parts is different
BL is the same I think.
Seems to work better, but we need to pinpoint which need to be flashed. I get sim manager error, my net works fine though.
Edit: it goes away and comes back, did not have that with full payload, so I am thinking something else needs to be done
How does this hybrid os OTA then?
Would it receive ColorOS OTA or OxygenOS OTA?
Obviously Cos updates. img(oos) are some preinstalled apps, like phone contacts chrome etc...
dna1982 said:
How does this hybrid os OTA then?
Would it receive ColorOS OTA or OxygenOS OTA?
Click to expand...
Click to collapse
dna1982 said:
How does this hybrid os OTA then?
Would it receive ColorOS OTA or OxygenOS OTA?
Click to expand...
Click to collapse
Yes, it will read at ColorOS
mdminhajulk said:
Please Describe about Hybrid flash method for chinese OP11
Click to expand...
Click to collapse
It is in the OP, is there something you do not follow?
wangdaning said:
Yes, it will read at ColorOS
It is in the OP, is there something you do not follow?
Click to expand...
Click to collapse
Do google FCM notifications work? Also can you restore backup from google cloud?
wangdaning said:
Yes, it will read at ColorOS
It is in the OP, is there something you do not follow?
Click to expand...
Click to collapse
is google assist working for you? "hey google"
hello , Can anyone please guide me how to extract my_xxxx.img ,please