Not my app but a find in the play store
https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
Just used it to update from 5.5 to 5.6.
I wasn't being offered it from system update so I thought I'd try it.
Worked first time.
Update: oxygen 11 released for the UK / EU
Thanks
Thanks for the post, just updated this way.
For some reason there were no update available for mine I was stuck on 5.4 - > Now 5.6 via this updater.
kalinlondon said:
Thanks for the post, just updated this way.
For some reason there were no update available for mine I was stuck on 5.4 - > Now 5.6 via this updater.
Click to expand...
Click to collapse
Nice one. Good to know it's not just me
After getting tired of waiting for the OTA update to 10.5.11.IN11BA to arrive, I used the Oxygen Updater to do it myself.
However, after the update I noticed that in the System Update screen, the changelog that was previously available at the bottom (as a slide up) is now gone.
Is this behavior expected? Should I worry for something, e.g. not getting any future OTAs?
dladz said:
Not my app but a find in the play store
https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
Just used it to update from 5.5 to 5.6.
I wasn't being offered it from system update so I thought I'd try it.
Worked first time.
Click to expand...
Click to collapse
Been using this app since I got my OP8P a month ago ?
Hugo_Sanchez said:
Been using this app since I got my OP8P a month ago ?
Click to expand...
Click to collapse
You have to be sure your getting the proper update for your phone version ie, China,UK, India, global They each have different ones
str8str said:
You have to be sure your getting the proper update for your phone version ie, China,UK, India, global They each have different ones
Click to expand...
Click to collapse
Actually the app identifies your model and will only provide updates for that model..
I mean that's my experiences of it.
dladz said:
Actually the app identifies your model and will only provide updates for that model..
I mean that's my experiences of it.
Click to expand...
Click to collapse
Yes of course ?
dladz said:
Not my app but a find in the play store
https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
Just used it to update from 5.5 to 5.6.
I wasn't being offered it from system update so I thought I'd try it.
Worked first time.
Click to expand...
Click to collapse
Is root necessary for updating with this app ?
xs1cht said:
Is root necessary for updating with this app ?
Click to expand...
Click to collapse
No
New dev preview available for the EU version via the app.
Haven't taken the plunge as I need stability at the moment.
Anyone flashes it, please let me know how it goes
10.5.12 is now available for the EU version of the device..
Downloading now..
Edit:
Installed and working well.
Couldn't comment on battery yet but feature wise it's about the same.
Thanks for writing about the app here. I just installed 10.5.14 on my EU OP8 Pro and everything is working well. The "official" installer didn't show this Update.
Magisk and NoLimits are working well.
drevel123 said:
Thanks for writing about the app here. I just installed 10.5.14 on my EU OP8 Pro and everything is working well. The "official" installer didn't show this Update.
Magisk and NoLimits are working well.
Click to expand...
Click to collapse
Yep absolutely, this app has been a god send to many, works with root albeit with an added process, beyond that's it's a spot on app.
Long may it last.
The official oxygen 11 update has rolled out for the UK / EU
Information as per oxygen updater.
Let the good times begin.
New update has arrived for the EU 2023
Will be updating and seeing if root, centre clock, xXx are affected..
Apparently canvas is now integrated too.
Does anyone have the OTA link for the new EU version?
Or the Stock boot.img ?
I downloaded it to my phone using the app, did a local update, before rebooting installed magisk beta to my inactive slot, and did a reboot.
Now its stuck while booting, and TWRP doesnt seem to boot either with fastboot boot twrp.img
Edit: Got it working again.
Does anyone have a working TWRP, the version i tried gave a Qualcomm Crashdump mode error. (Havent tried after it worked again).
Pekeltje91 said:
Does anyone have the OTA link for the new EU version?
Or the Stock boot.img ?
I downloaded it to my phone using the app, did a local update, before rebooting installed magisk beta to my inactive slot, and did a reboot.
Now its stuck while booting, and TWRP doesnt seem to boot either with fastboot boot twrp.img
Edit: Got it working again.
Does anyone have a working TWRP, the version i tried gave a Qualcomm Crashdump mode error. (Havent tried after it worked again).
Click to expand...
Click to collapse
No TWRP for A11
Pekeltje91 said:
Does anyone have the OTA link for the new EU version?
Or the Stock boot.img ?
I downloaded it to my phone using the app, did a local update, before rebooting installed magisk beta to my inactive slot, and did a reboot.
Now its stuck while booting, and TWRP doesnt seem to boot either with fastboot boot twrp.img
Edit: Got it working again.
Does anyone have a working TWRP, the version i tried gave a Qualcomm Crashdump mode error. (Havent tried after it worked again).
Click to expand...
Click to collapse
Why did you install twrp on 11? Just install your patched magisk partition.
All you needed to do was take the update then without booting go to magisk and install after OTA
dladz said:
Why did you install twrp on 11? Just install your patched magisk partition.
All you needed to do was take the update then without booting go to magisk and install after OTA
Click to expand...
Click to collapse
I tried to boot it, but didnt work.
But that was after i did the OTA from this app, and Magisk to the inactive slot.
Then a reboot and it didnt work, did not boot for some reason (Stuck on the red dot, with 2 white dots moving).
So then i tried the TWRP boot (No flash).
Maybe it was because of some Magisk modules (But it was just Smali and Recording enabler for OOS)
But its working again
But no option to boot TWRP so far when Android 11 is installed?
Thought it was OS independent.
Edit: patched and stock boot.img from Android 11 update from today (OnePlus8ProOxygen_15.E.31_OTA_0310_all_2011010124_d85208) for the OnePlus 8 Pro EU model.
Stock boot.img: test.jordykroeze.com/oneplus/android11_v2/boot.img
Magisk patched boot.img: test.jordykroeze.com/oneplus/android11_v2/magisk_patched.img
Related
[Dead Thread about Preview]
See this thread for discussing rooting 7.1.1 : -
Root Android Nougat 7.1.1 -- [NMF26F] -- SuperSU v2.78 SR5
Factory Image!
Successfully used flashfire to flash above factory image, along with SuperSU v2.78 SR4 ( instead of everroot) and ElementalX 5.05
Flashed with Flashfire. Root intact. Haven't looked at anything else yet.
Tapatalk on Nexus 9
ritchea said:
Flashed with Flashfire. Root intact. Haven't looked at anything else yet.
Click to expand...
Click to collapse
Did you use everroot option of flashfire? Which is still using su v2.78 SR1? I thought we would have needed SR4 for 7.1.
I need to make some backups and probably will flash this version on Thursday!
Made backups today (23/11) and successfully flash it! OP update with links!
Yes.
Tapatalk on Nexus 9
I flashed it a few minutes ago over stock 7.0 without wiping data and it seems to be the fastes and smoothest experience I ever had with this device. Can't say much more and didn't try to root, but I switched a few times between my two users und it's still fast and smooth. After switching between my users for two times with 7.0 a reboot was much needed! :fingers-crossed:
Mine is stuck at booting animation. No idea why first time this has happened to me before. Or does it just take like 20 minutes on first boot or what?
I flashed it manually through fastboot like normal.
jaju123 said:
Mine is stuck at booting animation. No idea why first time this has happened to me before. Or does it just take like 20 minutes on first boot or what?
I flashed it manually through fastboot like normal.
Click to expand...
Click to collapse
20 minutes is too long. Have you tried to just power off then on? Sometimes, that's all it takes. It's happened to me but not for this flash.
Tapatalk on Nexus 9
seems way faster than 7.0 so far.... I just did a full reset on 7.0 a week ago and experience immediate lag after I installed my apps. I flashed the 7.1 dev image today and went through the same process. So far so good. I'll report back after a couple of weeks of usage.
Did anyone enrolled in the beta program get the OTA yet ?
Previously I got it the same day an announcement was made. Nothing received yet. As a matter of fact, I didn't even receive the November security update this month.. Never rooted, never modified.
Had to post. Clean flashed new preview , temp boot of twrp to flash latest SU (SR4) for root and set up as new device. Best google effort yet! No problems adjusting build prop to enable assistant and both Pixel and Nova Launchers are go as is new systemless option adaway. Couldn't help notice how responsive UI is and chrome is stable for me 4-5 tabs in using sites like fark.com and no/very few redraws after pushing the tablet with moderate demands. Looking forward to the December release, noticed USB charging was still fairly slow still, hopefully the batt life is ok too. Go Google, they might just catch up to Craig's AOSP version/kernel performance if they're not careful !
Completed clean flash this preview
Rootless with supersu 2.78 sr4
Disable some app not use, very smooth
the.teejster said:
Did anyone enrolled in the beta program get the OTA yet ?
Previously I got it the same day an announcement was made. Nothing received yet. As a matter of fact, I didn't even receive the November security update this month.. Never rooted, never modified.
Click to expand...
Click to collapse
Same here. My device is enrolled but no update. I had to manually flash the November update. I did wonder if it was anything to do with flashing custom Roms. I am on full stock Google image but no update yet.
I never flashed a custom rom on my N9 nor has it ever been rooted. Still haven't received Nov update nor the Beta program update.
If you flash a factory image then you are fully stock and you should receive all updates from google.
Gold Ribbed said:
Same here. My device is enrolled but no update. I had to manually flash the November update. I did wonder if it was anything to do with flashing custom Roms. I am on full stock Google image but no update yet.
Click to expand...
Click to collapse
Has anyone received the ota yet? Or is google only doing a factory image this time for some reason?
Just manually flashed the stock preview. Much better than the stock 7.0 which is virtually unusable . This preview is solid and stable..
One of the main benefits of enrolling in the beta program was to be able to get OTA updates and not lose your data. Other devices in the program have received the OTA. Disappointing that the N9 hasn't to this date.
Gold Ribbed said:
Just manually flashed the stock preview. Much better than the stock 7.0 which is virtually unusable . This preview is solid and stable..
Click to expand...
Click to collapse
the.teejster said:
One of the main benefits of enrolling in the beta program was to be able to get OTA updates and not lose your data. Other devices in the program have received the OTA. Disappointing that the N9 hasn't to this date.
Click to expand...
Click to collapse
You can flash factory images without affecting your data partition. It is called "dirty flashing" for a reason.
My device has been through loads of updates, + the previous Preview images, by that method!
Checkout "Flashfire" app!
Flashfire
Click to expand...
Click to collapse
is the most advanced on-device firmware flasher available for rooted Android devices.
Click to expand...
Click to collapse
I realize this is the wrong thread for this discussion but to conclude. I'm not rooted and choose not to go down that path. My last comment still stands.
corkiejp said:
You can flash factory images without affecting your data partition. It is called "dirty flashing" for a reason.
My device has been through loads of updates, + the previous Preview images, by that method!
Checkout "Flashfire" app!
Click to expand...
Click to collapse
the.teejster said:
I realize this is the wrong thread for this discussion but to conclude. I'm not rooted and choose not to go down that path. My last comment still stands.
Click to expand...
Click to collapse
It is also possible to flash factory images with fastboot without wiping data.
Flashfire is just a convenient app for doing it (with needing a computer) for people who are rooted.
Updated OP since this thread became useful to track if magisk works with our stock ROM.
The most recent version you can use at the moment is magisk 16.7 and magisk manager 5.8.3.
I suggest that you change the update channel to custom and set the address to 127.0.0.1
For the most recent Magisk version:
mickey36736 said:
I tested 19.3 on B01 oreo and it still bootloop.
Click to expand...
Click to collapse
Thanks for checking @mickey36736
rzarectha said:
It bootloops
Click to expand...
Click to collapse
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.
raystef66 said:
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.
Click to expand...
Click to collapse
mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build
update: it bootloops on stock no matter what channel (stable/beta) you get it from.
I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
rzarectha said:
mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build
update: it bootloops on stock no matter what channel (stable/beta) you get it from.
I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
Click to expand...
Click to collapse
You can change the OP tittle by pressing Go Advanced button next to the Save button when editing the OP post.
Not only on stock...
I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.
Prophet 5 said:
I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.
Click to expand...
Click to collapse
use the uninstaller zip first
Try 17.1. supposedly solves the bootloops.
bootloops are easily fixed by using the uninstaller first.
koftheworld said:
Try 17.1. supposedly solves the bootloops.
Click to expand...
Click to collapse
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
KwesiJnr said:
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
Click to expand...
Click to collapse
You have to use the uninstaller first and then flash 17.1.
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
pnin said:
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
Click to expand...
Click to collapse
Did you use the magisk uninstaller? If not, just reflash your bootloader
koftheworld said:
Did you use the magisk uninstaller? If not, just reflash your bootloader
Click to expand...
Click to collapse
Excuse my ignorance but how would reflashing the bootloader help. Doesn't Magisk modify the boot image?
I figure that if flashing the uninstaller and then flashing v17.1 still results in a bootloop I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image). Flash Magisk 17.x afterward.
That said, I am a non-Magisk kind of guy (not present on any ROMs or devices) so I might not know what I'm talking about. [emoji16]
Dark ROM. FTW. [emoji41]
ZTE Axon 7 A2017U, AospExtended v4.6 ROM, LlamaSweet 0.5 Kernel, microG (NoGapps), Multiboot, XDA Legacy
marcdw said:
I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image).
Click to expand...
Click to collapse
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...
I have even had to restore recovery through fastboot mode now. :silly:
I did not flash Magisk 17.x on Stock B35 (stayed with v16.4), but installing the latest Magisk Manager (v5.9.1) resolved the previous SafetyNet Check errors
Using stock anything above and v17.0 will bootloop using stock,
Just my 2cents, if that your issue just do the following:
-Download v16.7 first in case you don't have it yet, and move it to the SDCard.
* Head back to TWRP
* Flash v16.7 or your preferred release.
* You're good to go.
pnin said:
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...
I have even had to restore recovery through fastboot mode now. :silly:
Click to expand...
Click to collapse
Not sure to be honest. Last time I had Magisk was around v15.x. When I initially rooted my Moto Magisk was part of the process. Even though the stock ROM is using SuperSU it seems I didn't fully remove Magisk. I have the following remnants visible in TWRP...
/data/magisk
/data/magisk.img
and files in /data/adb/
Not sure why everything is failing so badly on your end. I can't test things on my Axon 7 since I use DualBoot Patcher where Magisk is a no go.
Moto G5S Plus XT1806, MSM-Xtended v2.5 ROM, MultiROM, XDA Legacy
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).
Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).
I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
pnin said:
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).
Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).
I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
Click to expand...
Click to collapse
I'm not currently having Magisk issues, but Google Messages, after the recent update, does the same here. Gave up on it & switched to Textra.
New beta version released. Still bootloop
https://developers.google.com/android/images
picked it up via OTA. They seem to be doing a better job getting OTAs ready right away. $10 says the screen flash is still there.
It supposedly fixes sound in video recordings, so that will be interesting to see. I don't record much video, but when I do, I want it to sound decent.
I just wish they'd fix the Google Assistant to start responding to the Hey Google hotword again. It's super frustrating when a key feature doesn't work.
PuffDaddy_d said:
I just wish they'd fix the Google Assistant to start responding to the Hey Google hotword again. It's super frustrating when a key feature doesn't work.
Click to expand...
Click to collapse
I use "Hey Google" almost daily. I haven't seen reports of the hot phrase not working. Do many people have this problem?
- Pixel 3XL
Has anyone had any issues with Magisk on this January update? I just updated and tried installing Magisk v18 and started bootlooping. I may try v17.3. Ill report back
EDIT: v17.3 installed just fine
It appears I am $10 rich. I screen flash still there.
No worries. Just wait till the February update boys.
JJT211 said:
Has anyone had any issues with Magisk on this January update? I just updated and tried installing Magisk v18 and started bootlooping. I may try v17.3. Ill report back
EDIT: v17.3 installed just fine
Click to expand...
Click to collapse
Installed v18 on both a P3 and P3XL (from the TWRP .img). No problem with either.
l2tp bug is also still present! wtf Google. fix this!
sliding_billy said:
Installed v18 on both a P3 and P3XL (from the TWRP .img). No problem with either.
Click to expand...
Click to collapse
What was your process?
acidspider said:
What was your process?
Click to expand...
Click to collapse
1. Magisk saved to the phone (Just to be sure, I would confirm you have the one that Topjohn posted with the same version very shortly after originally posting V18 originally since there was an issue installing kernels after his 1st V18. The one on the main Magisk thread is the right/current one)
2. flash-all (without -w)
3. Once system boots back up, shut down, boot back to fastboot with key combo (I do all of my boots to fastboot from full shutdown and with key combo not ADB) and fastboot boot the current (different versions for my two phones) TWRP .img
4. Install Magisk V18
5. Reboot system from TWRP
6. Verify root and SafetyNet
7. Install ElementalX from EX application
8. After kernel forces reboot, just normal maintenance stuff like definitions for AdAway, checking modules, reinstalling BusyBox, installing native tethering prop
mikeprius said:
It appears I am $10 rich. I screen flash still there.
No worries. Just wait till the February update boys.
Click to expand...
Click to collapse
It's probably at the bottom of Google's list of priorities. It is hard to replicate, occurs rarely, and doesn't affect performance in any way. I wouldn't hold my breath waiting for a fix any time soon.
Installed v18 on both a P3 and P3XL (from the TWRP .img). No problem with either.
Click to expand...
Click to collapse
Yea I just installed v17.3 and upgraded to v18 through manager. Weird, must've been a bad download.
JJT211 said:
Has anyone had any issues with Magisk on this January update? I just updated and tried installing Magisk v18 and started bootlooping. I may try v17.3. Ill report back
EDIT: v17.3 installed just fine
Click to expand...
Click to collapse
I'm on canary 18.1 and it installed just fine.
I have been using the flash-all ( without -w) each month since I got the phone. I just installed the Jan update. However, the "Security patch level: September 5, 2018" still shows. Are you guys getting this too?
SmokinCharger said:
I have been using the flash-all ( without -w) each month since I got the phone. I just installed the Jan update. However, the "Security patch level: September 5, 2018" still shows. Are you guys getting this too?
Click to expand...
Click to collapse
It should say Jan 5. Something went wrong, redo it and make sure you redownload the Jan update. Feels like maybe you didn't clean up or grabbed the wrong image.
Strangely, since January update,I try to modify my host file again but it stay there only for a few minutes and get erase back to the original... Anybody know why?
Why does it matter if you reboot-bootloader or using the "key combo"? It shouldn't matter.
ShadowJP88 said:
Strangely, since January update,I try to modify my host file again but it stay there only for a few minutes and get erase back to the original... Anybody know why?
Click to expand...
Click to collapse
It seems like system write privileges aren't sticking with the January update. Check my magisk thread below for updates.
https://forum.xda-developers.com/pixel-3/how-to/magisk-pixel-3-t3853445
Cares said:
Why does it matter if you reboot-bootloader or using the "key combo"? It shouldn't matter.
Click to expand...
Click to collapse
I don't know, but I know there was some wonky behavior in TWRP a couple of months ago that only showed if you used ADB reboot or TWRP reboot. My only guess is that something gets cleared from memory during a full power down and that it simply looks like the difference is in the electronic vs. key combo method when it is actually in the power down function.
I think you are right. I talked about this on another thread because I have placed a LatineIME folder in my system/app folder, changed permissions, rebooted and used AOSP keyboard fine with every other update until Jan. Now, I place the folder in my system/app, change permissions, reboot and it is gone. I have tested this on three different phones, og pixel, Pixel 3, and Moto G5 Plus running custom Pie rom with Jan update. All three have the same problem.
PuffDaddy_d said:
It seems like system write privileges aren't sticking with the January update. Check my magisk thread below for updates.
https://forum.xda-developers.com/pixel-3/how-to/magisk-pixel-3-t3853445
Click to expand...
Click to collapse
Hey Guys,
what do you think is the best costum rom (stable) for the Mate 10 pro?
Is it possible to flash it with Pie 9.0.161?
Thanks for Help :victory:
Just wait for the ota update to pie.
that's definitely a worse rom. i'm on it right now.
wooley4766 said:
Just wait for the ota update to pie.
Click to expand...
Click to collapse
I already have the Pie Update via Firmware Finder.
But i want to flash to a stable Pie Rom :fingers-crossed:
Pie Update
HauAbDuLauch said:
I already have the Pie Update via Firmware Finder.
But i want to flash to a stable Pie Rom :fingers-crossed:
Click to expand...
Click to collapse
If you have the Pie update from firmware finder it's an approved ROM unless you have a modified recovery it checks and you wouldn't be able to install it if it wasn't approved so you probably have the latest approved ROM
revjamescarver said:
If you have the Pie update from firmware finder it's an approved ROM unless you have a modified recovery it checks and you wouldn't be able to install it if it wasn't approved so you probably have the latest approved ROM
Click to expand...
Click to collapse
but no custom
Hi! Quick question. My BLA-L09 is on build number 8.0.0.131(c782). I'm rooted with Magisk via Pretoriano's TWRP using the all in one tool. I can't receive firmware updates because of this (they fail to install).
If I update to Pie, will I be able to root again with Magisk? How can make this update? I suppose I would need stock recovery back and don't know where to get it from it how to flash it. It was my first time doing this on a Huawei, I'm used to Samsung devices. Any help would be appreciated.
Thanks!
93starletgt said:
Hi! Quick question. My BLA-L09 is on build number 8.0.0.131(c782). I'm rooted with Magisk via Pretoriano's TWRP using the all in one tool. I can't receive firmware updates because of this (they fail to install).
If I update to Pie, will I be able to root again with Magisk? How can make this update? I suppose I would need stock recovery back and don't know where to get it from it how to flash it. It was my first time doing this on a Huawei, I'm used to Samsung devices. Any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Nope, you won't. Any version from 8.0.0.146 and above will contain the new bootloader which won't let you unlock it or install twrp, magisk or whatever, most probably you will brick your phone like I did.
You'll be a lot safer to stay on what you're on. Huawei did a nifty development to make life miserable to anyone which likes to customize their phone. Maybe they should be called Huapple from now on...
I was in a similar situation as you, 141 if I remember correctly. Installed Xposed via magisk, got a bootloop, did a system restore via erecovery, got it working again and lost magisk/root so thought it would be the time to do the ota, didn't know about the bootloader change so found I was on emui 9, tried to install twrp but that bricked the phone. So I tried to do the system restore via erecovery again, but that didn't work.
After that tried every possible way (inc. paying funkyhw etc.) to recovery the phone, no way. If you try to downgrade it to a version before 146 it will hardbrick leaving you with a paperweigth.
So if I were you, I wouldn't touch a thing. I gave up and am waiting for my Oneplus 6, much better phone for this stuff.
mirandam said:
Nope, you won't. Any version from 8.0.0.146 and above will contain the new bootloader which won't let you unlock it or install twrp, magisk or whatever, most probably you will brick your phone like I did.
You'll be a lot safer to stay on what you're on. Huawei did a nifty development to make life miserable to anyone which likes to customize their phone. Maybe they should be called Huapple from now on...
I was in a similar situation as you, 141 if I remember correctly. Installed Xposed via magisk, got a bootloop, did a system restore via erecovery, got it working again and lost magisk/root so thought it would be the time to do the ota, didn't know about the bootloader change so found I was on emui 9, tried to install twrp but that bricked the phone. So I tried to do the system restore via erecovery again, but that didn't work.
After that tried every possible way (inc. paying funkyhw etc.) to recovery the phone, no way. If you try to downgrade it to a version before 146 it will hardbrick leaving you with a paperweigth.
So if I were you, I wouldn't touch a thing. I gave up and am waiting for my Oneplus 6, much better phone for this stuff.
Click to expand...
Click to collapse
Thank you for the info! And what about staying on my current bootloader and flash a custom ROM on my already installed TWRP?
93starletgt said:
Thank you for the info! And what about staying on my current bootloader and flash a custom ROM on my already installed TWRP?
Click to expand...
Click to collapse
There is a ResurectionRemix rom that can be used for that. Just search for RR-O-v6.0.0-20180402-bkl-OpenKirin.zip it should work as this one's flashable by twrp. I haven't tried it so can't tell if it does. I have the file but I don't know if it's complete as it only contains system.img which seems strange as normally there would also be a boot.img or at least a kernel.img
mirandam said:
There is a ResurectionRemix rom that can be used for that. Just search for RR-O-v6.0.0-20180402-bkl-OpenKirin.zip it should work as this one's flashable by twrp. I haven't tried it so can't tell if it does. I have the file but I don't know if it's complete as it only contains system.img which seems strange as normally there would also be a boot.img or at least a kernel.img
Click to expand...
Click to collapse
Thanks! Last question. If I would like to go back to stock using the All In One Tool, how can I flash stock recovery? And where can I find it? Many thanks for your help.
are there custom roms for the huawei mate 10 pro??
cause cant find it on xda.
mine is stock it works but the no status bar pull down on lockscreen is anoying ;( sometimes and that only the stock sms app show on the always screen on...
https://developers.google.com/android/ota
Ota is live too...
Where I found the changelog?
Thanks
shark147 said:
Where I found the changelog?
Thanks
Click to expand...
Click to collapse
Same place as always: https://source.android.com/security/bulletin/pixel/2019-05-01.html
There doesn't seem to be much though:
This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices.
Click to expand...
Click to collapse
No issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
sliding_billy said:
No issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Could you give me some more details on what you did to install Magisk? For the first time with my P3 I cannot get anything to work. I flashed the May update minus -w, but every method of installing Magisk 19.1 that I've tried ends up with a bootloop.
CSX321 said:
Could you give me some more details on what you did to install Magisk? For the first time with my P3 I cannot get anything to work. I flashed the May update minus -w, but every method of installing Magisk 19.1 that I've tried ends up with a bootloop.
Click to expand...
Click to collapse
1) flash-all (minus -w). Phone reboots to system automatically.
2) shut down and boot to BL
3) fastboot boot twrp-3.3.0-0-blueline.img (be sure to have a copy of the .img file on your phone)
4) install twrp using Advanced > Install Recovery Ramdisk > twrp-3.3.0-0-blueline.img
5) boot to system
6) shut down and boot to BL>recovery (TWRP loads)
7) install Magisk-v19.1 (I did already have 19.1 installed on this phone via Magisk Manager update/Magisk update from before the May image came out in case it matters, so if necessary install 18.1 and then update to 19.1 with Magisk Manager)
8) reboot to system
9) confirm root and install kernel (for me that was ElementalX automated install using EX Kernel Manager app but installing the kernel by going back to TWRP and flashing should do the same)
The two things I might be doing different than others are not using ADB to get back to BL or recovery (I always use the key combo) and booting to system before next step (I don't stack my TWRP/Magisk/kernel installs). Hope this helps.
Whew! Back in business. Thanks!
CSX321 said:
Whew! Back in business. Thanks!
Click to expand...
Click to collapse
That's cool. Which part was the culprit?
sliding_billy said:
That's cool. Which part was the culprit?
Click to expand...
Click to collapse
Well, I don't really know. I initially did what I always do: extract the new boot.img from the update, patch it with MM, run flash-all without -w, let the update finish, reboot and flash the patched boot to boot_a and boot_b. That bootlooped. I flashed stock boot.img and ran like that for a day. Next I booted (but didn't install) TWRP, and tried to install 19.1 (bootloop), and 18.1 (wouldn't install). I decided to try to downgrade to the April update and did flash-all from there (without -w). Big mistake, because then it stuck on the G screen and wouldn't boot at all. I ultimately was able to flash back to the May update, get it to boot, then followed your directions. I did have to install 18.1 first, because even after following your directions, 19.1 still bootlooped when installed from TWRP. MM was able to update to it fine, though, from 18.1. Who knows what the problem really was.
CSX321 said:
Well, I don't really know. I initially did what I always do: extract the new boot.img from the update, patch it with MM, run flash-all without -w, let the update finish, reboot and flash the patched boot to boot_a and boot_b. That bootlooped. I flashed stock boot.img and ran like that for a day. Next I booted (but didn't install) TWRP, and tried to install 19.1 (bootloop), and 18.1 (wouldn't install). I decided to try to downgrade to the April update and did flash-all from there (without -w). Big mistake, because then it stuck on the G screen and wouldn't boot at all. I ultimately was able to flash back to the May update, get it to boot, then followed your directions. I did have to install 18.1 first, because even after following your directions, 19.1 still bootlooped when installed from TWRP. MM was able to update to it fine, though, from 18.1. Who knows what the problem really was.
Click to expand...
Click to collapse
I'd just be spit balling at this point like you are, but at least you are up and running. I do think there is possibly something going on with Magisk going from 18.1 to 19.1 without Manager doing the back end work (even if it happened previously) since Magisk still does retain some data even if root is lost during the upgrade. There are certainly some changes that occured between 18.1 and 19.0 beta since coming from 18.1 you would need to redo your Magisk hide check marks. Either that or using MM to patch boot may have completely changed.
sliding_billy said:
There are certainly some changes that occured between 18.1 and 19.0 beta
Click to expand...
Click to collapse
I probably just had something in some weird state, because I ran 18.1, 19.something beta, 19.something canary, then back to 19.1 stable when it came out. I forgot, I also ran the uninstaller at some point in my previous attempts.
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Same question
djboydva1 said:
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Click to expand...
Click to collapse
I was coming to ask the same question, only I am in WA and have T-mobile. Stock, not rooted. Not had an issue before.
Same here. New P3 during April, so awaiting first security update for my new device. Carrier is AT&T, but why would that matter, right? Just seems strange having to wait. I got the impression that monthly updates for Pixels would come out the same day they were announced as being available. Live and learn I guess.
Finally popped this evening (5/16/2019). No clue why the delay.
djboydva1 said:
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Click to expand...
Click to collapse
I have a Pixel 3 on Google Fi and still haven't gotten the update. Contacted support yesterday and they couldn't find anything wrong. They "promised" I'd get it. Always gotten them within a day or two before.
I guess I just never looked into this before since I'm a new Pixel user or I'm just naive but I assumed when I got a Pixel phones updates would not have to be pushed through my carrier anymore? No May update here on my stock Pixel 3 on T-Mobile.
Always get OTA on the day of release, stock phone, T-Mobile, the Netherlands.
(Pixel didn't launch in the Netherlands, I got it from Germany)
Just installed the may update OTA.
Anyone else having issues with apps accessing the gallery. Both WhatsApp and stock messenger now taking ages to display the thumbnails of the images and videos in my gallery when I add them to a message.
ok could I get some hints here on how to update?
I have rooted and I have magisk.