So I rooted my phone following this tutorial :-
https://www.google.co.in/amp/s/foru...1-oreo-8-0-disabling-ota-magisk-t3728654/amp/
And then I subsequently followed the steps in the guide linked in that tutorial which tells you what to do when an OTA arrives. (Basically, it says to revert back to stock boot image from within magisk and then let the OTA install as is.)
The problem I face is - the OTA downloads normally but then as soon as it starts installation process step 1, an immediate error is thrown saying "Installation Problem". I'm sure that most of you are familiar with this error but then I don't know how to resolve it.
One thing I might have done which could have caused this but I ain't sure - I updated Magisk from within the app. In an earlier rooting tutorial, I remember seeing a warning to never update Magisk from within the app but I never got around to knowing why. However, this tutorial didn't mention anything of the sort, so I went ahead and did it.
As it stands now, I have the January patch waiting in the notifications panel but I don't know how to proceed. Flashfire doesn't work either, I tried.
Any fixes?
anirbannath said:
As it stands now, I have the January patch waiting in the notifications panel but I don't know how to proceed. Flashfire doesn't work either, I tried.
Any fixes?
Click to expand...
Click to collapse
Hello:
I had the same problem, exactly don't know why, I could fix it flashing december 29 again saving user data using the .bat gave in the fastboot rom (You can do it with MiFlash if you want), give it a try, maybe this solution could be your salvation .
black_arashi said:
Hello:
I had the same problem, exactly don't know why, I could fix it flashing december 29 again saving user data using the .bat gave in the fastboot rom (You can do it with MiFlash if you want), give it a try, maybe this solution could be your salvation .
Click to expand...
Click to collapse
Hi. I had already tried this before posting the question but the problem that occurred then was that the December 29 update is actually Android N as far as I remember. For some reason, whenever I try dirty flashing Android N from Android O, my phone goes into boot loop. The thing is I don't want to flash any more ROMs because that tutorial said that I don't have to. Otherwise, I am aware that that is the standard procedure.
I simply want OTA to work as it says in the tutorial. That's all. But thanks anyway.
By the way, I forgot to mention this - I am currently on the buggy (stable) version of Android O that was released on December 31st. The update that I am waiting on is the 89 MB patch that was released last week.
anirbannath said:
Hi. I had already tried this before posting the question but the problem that occurred then was that the December 29 update is actually Android N as far as I remember. For some reason, whenever I try dirty flashing Android N from Android O, my phone goes into boot loop. The thing is I don't want to flash any more ROMs because that tutorial said that I don't have to. Otherwise, I am aware that that is the standard procedure.
I simply want OTA to work as it says in the tutorial. That's all. But thanks anyway.
By the way, I forgot to mention this - I am currently on the buggy (stable) version of Android O that was released on December 31st. The update that I am waiting on is the 89 MB patch that was released last week.
Click to expand...
Click to collapse
Hello:
When I mean December 29th I was mencionating the compilation day (7.12.29 in this case) hovewer the December 31st is the same as the 29th just the release date or the compilation day are the difference. Anyway here you have the December 29th Oreo fastboot rom. It's the same that was release for a few hours in the official site if you want to give it a try. Good luck!
Exactly same problem here
So I restored original bootimage, relocked the phone through fastboot and tried again
But... Now the OTA disappeared
Just waiting a few days to see If It appears again
---------- Post added at 02:14 PM ---------- Previous post was at 01:39 PM ----------
black_arashi said:
Hello:
I had the same problem, exactly don't know why, I could fix it flashing december 29 again saving user data using the .bat gave in the fastboot rom (You can do it with MiFlash if you want), give it a try, maybe this solution could be your salvation .
Click to expand...
Click to collapse
Could you install january patch successfully?
Fusquinha77 said:
Could you install january patch successfully?
Click to expand...
Click to collapse
Hello:
Yeah I have the january patch installed, I just fully unistalled magisk(boot image and app too) and flashed December 29th oreo patch saving user data with the .bat included in the fastboot ROM, when installed looked for the January Patch, installed it and I rooted my device an again.
If you don't have the Oreo image of the December 29th you can download it from here
black_arashi said:
Hello:
I had the same problem, exactly don't know why, I could fix it flashing december 29 again saving user data using the .bat gave in the fastboot rom (You can do it with MiFlash if you want), give it a try, maybe this solution could be your salvation .
Click to expand...
Click to collapse
black_arashi said:
Hello:
Yeah I have the january patch installed, I just fully unistalled magisk(boot image and app too) and flashed December 29th oreo patch saving user data with the .bat included in the fastboot ROM, when installed looked for the January Patch, installed it and I rooted my device an again.
If you don't have the Oreo image of the December 29th you can download it from here
Click to expand...
Click to collapse
Successfully fastbooted Dec 31 Oreo. But no OTA...
Will wait 2 days. Otherwise I'll install the TWRP version.
Still no January OTA here.
Does anyone facing the same problem?
Received the OTA today again
Jan patch, 89 MB
Fully uninstalled Magisk, rebooted, and updated successfully
Related
Hi,
I have Oppo find 7.
Firstly, tried to install nightly dated 13/10/14 .. go a red error message on TWRP, unable to install, just kept booting back into TWRP.
So I did not bother installing that one. Waited for one of the 14th ( today ).
Just tried to install nightly from 14Th. Install went ok but the screen stays stuck on main flash screen.
Have tried to install it twice now with same problem.
Flashed back to nightly dated 12th, all working ok.
Whats been going on since 12th ?
Anyone else with an issue ?
sohotha said:
Hi,
I have Oppo find 7.
Firstly, tried to install nightly dated 13/10/14 .. go a red error message on TWRP, unable to install, just kept booting back into TWRP.
So I did not bother installing that one. Waited for one of the 14th ( today ).
Just tried to install nightly from 14Th. Install went ok but the screen stays stuck on main flash screen.
Have tried to install it twice now with same problem.
Flashed back to nightly dated 12th, all working ok.
Whats been going on since 12th ?
Anyone else with an issue ?
Click to expand...
Click to collapse
You should probably pay attention to the device-specific threads instead of posting here.
Something's wrong, not sure what yet.
Entropy512 said:
You should probably pay attention to the device-specific threads instead of posting here.
Something's wrong, not sure what yet.
Click to expand...
Click to collapse
ok, will try posting device specific thread.
OK, I see that there are many problems with the Nougat currently so I will not consider that. What my problem is is that I have the November 2015 build and I have a March 2016 security update that simply does not work.. I always end up with the Robot lying on its side and a red mark and ! and the word I think "failure" ? I have tried this 3 times now with same results.. My bootloader is unlocked.. What am I doing wrong as it basically was downloaded and all I had to do was to push the install option but I always wind up at the end with the robot on its side?
Thank you
painfree said:
OK, I see that there are many problems with the Nougat currently so I will not consider that. What my problem is is that I have the November 2015 build and I have a March 2016 security update that simply does not work.. I always end up with the Robot lying on its side and a red mark and ! and the word I think "failure" ? I have tried this 3 times now with same results.. My bootloader is unlocked.. What am I doing wrong as it basically was downloaded and all I had to do was to push the install option but I always wind up at the end with the robot on its side?
Thank you
Click to expand...
Click to collapse
By going back to March security update, you mean that you are flashing the factory image, or restoring a Nandroid?
If you have ever restored an EFS backup made by TWRP 3.0.2-1, then you may observe such things. If it is so, you can apply the fix from the following thread: http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
DJBhardwaj said:
By going back to March security update, you mean that you are flashing the factory image, or restoring a Nandroid?
If you have ever restored an EFS backup made by TWRP 3.0.2-1, then you may observe such things. If it is so, you can apply the fix from the following thread: http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
Click to expand...
Click to collapse
No actually I never did any updates as I did not want to compromise the radio and the T-Mobile Band 12 which I did with the first update and I had to flash the radio back.
I did not do any upgrades since Nov 2015 and on my phone I mistakenly downloaded the March 2016 security update by I believe putting phone in my pocket and moving around... In any event it says install and I tried that 3 x and I can never get it to work..my current build is: MDB08L
Thank you,
painfree said:
No actually I never did any updates as I did not want to compromise the radio and the T-Mobile Band 12 which I did with the first update and I had to flash the radio back.
I did not do any upgrades since Nov 2015 and on my phone I mistakenly downloaded the March 2016 security update by I believe putting phone in my pocket and moving around... In any event it says install and I tried that 3 x and I can never get it to work..my current build is: MDB08L
Thank you,
Click to expand...
Click to collapse
Just download the latest factory image and fastboot flash the partitions as per Heisenberg's guide. You'll be far better off. Not sure what you mean by Nougat having a bunch of problems, as there aren't any I have encountered.
Sent from my Nexus 6P using Tapatalk
I saw the guide but I do not want to risk my phone catching fire as I need to stay in contact with my children. I do not understand the process of flashing a "partition".
Is there a Heisinburg for Dummies documentation as all I want to do is to upgrade to Nougat and not have to restore/reinstall anything on my phone.
Thank you..
painfree said:
I saw the guide but I do not want to risk my phone catching fire as I need to stay in contact with my children. I do not understand the process of flashing a "partition".
Is there a Heisinburg for Dummies documentation as all I want to do is to upgrade to Nougat and not have to restore/reinstall anything on my phone.
Thank you..
Click to expand...
Click to collapse
What don't you understand about flashing a partition? What can be made clearer for you so that you are more comfortable with the guide by Heisenberg?
It's slightly technical but I think it's thorough in breaking down the steps for beginners. Section 9, is the way to go to fastboot flash a factory image:
http://forum.xda-developers.com/showthread.php?t=3206928
The easiest route is via adb sideload. Click on "latest Nexus OTA images" and follow the instructions by Google. Download the NRD90U OTA image.
https://developers.google.com/android/nexus/ota
Sent from my Nexus 5X using Tapatalk
Please Don't Open Multiple Questions for the same Problem. Here's the original.
I have my Nexus 6p and it will not install the March 2016 update.. robot on side red/
Thread Closed.
So I was reading that the US beta launch was supposed to happen next month, but I just got an email from the FUT testing team about the rollout being tomorrow, March 15th. I signed up on that Goggle Forms sheet the day it was posted on XDA since I've been checking for news every hour it seems like.
Did anyone else get the email? I really hope it's the case that us Yanks are getting the update just days after the Spain/France/Italy/Germany beta rollout.
Yeah, I got the email too! Here's the email in full:
Hello FUT Testers,
We'd like to thank everyone that has chosen to participate in our newest FUT trial for the Android O. The update will be releasing tomorrow March 15!
It will be a staged rollout through out the day and everyone should have the update before the end of the week.
Here are the steps to take to see if the update is available:
1. Go to "Settings" and scroll to "System"
2. Select "System Update" and give it a few seconds run a quick scan
3. Hit "Check for Updates" option, if no update apears select top right menu option (looks like three dots) and hit "Download latest full package"
4. If successful please install update, if nothing shows up please wait a few hours before trying again
Please use this email address to provide us details of any issues or new features you might run into or like. We are looking forward to hearing from you all.
Thanks again for everyone that has participated in this release. We are looking forward to hearing all the feedback!
Thank you,
Honor FUT Team!
Click to expand...
Click to collapse
Super excited!
I received the email as well.
Sent from my BND-L24 using XDA Labs
Same, but I flashed TWRP. I'm concerned that this won't work, just like the previous update, unless we can 1. find a way to make a TWRP-flashable zip or offline version to sideload, 2. get the firmware already to reflash to stock and go from there.
Are ya'll in the same boat?
johncro13 said:
Same, but I flashed TWRP. I'm concerned that this won't work, just like the previous update, unless we can 1. find a way to make a TWRP-flashable zip or offline version to sideload, 2. get the firmware already to reflash to stock and go from there.
Are ya'll in the same boat?
Click to expand...
Click to collapse
I didn't install TWRP on mine because I didn't see a reason with no functional ROMs available.
On a side not can someone explain why someone can't just factory reset and get a backup of the stock US ROM for everyone else?
I believe we haven't had any volunteers.
I got the email too awesome
I also got it :good:
I got it as well! Looking forward for oreo goodness tomorrow!
PwnedBySumo said:
I didn't install TWRP on mine because I didn't see a reason with no functional ROMs available.
On a side not can someone explain why someone can't just factory reset and get a backup of the stock US ROM for everyone else?
Click to expand...
Click to collapse
There appears to be several TWRP versions available in these forums for non-L24 variants. Can someone with an L24 confirm that they were successful in backing up and then later restoring their ROM? Which TWRP image did you use? Once this is confirmed, creating a backup of the stock ROM really shouldn't take that much effort.
Until then, I'm reluctant to flash one the TWRP images available. On some phones, one could use "fastboot boot <image>" (without any other undocumented parameters) to boot into a third party recovery such as TWRP without replacing the stock recovery. However, at least on MY L24, I receive a remote command failed error (with FRP and bootloader unlocked). Therefore, one can not easily make a backup of the stock recovery.
... And without stock recovery, you can not perform OTA updates because Huawei uses its own update.zip format. Judging by the screeshot from https://forum.xda-developers.com/showpost.php?p=75892852&postcount=55, it looks like that's exactly how they're rolling out the Oreo trial for the European variant. So let's hope the timeline for mid-March for releasing stock ROM and recovery is correct.
Just my luck, didn't get the email.... I signed up early, but no joy.
PsionicFrost said:
So I was reading that the US beta launch was supposed to happen next month, but I just got an email from the FUT testing team about the rollout being tomorrow, March 15th. I signed up on that Goggle Forms sheet the day it was posted on XDA since I've been checking for news every hour it seems like.
Did anyone else get the email? I really hope it's the case that us Yanks are getting the update just days after the Spain/France/Italy/Germany beta rollout.
Click to expand...
Click to collapse
Would be great if someone with an L24 does a backup Rom. I flashed the OpenKirin ROM but need to go back to stock
Surprise everyone
wisdomzw said:
Would be great if someone with an L24 does a backup Rom. I flashed the OpenKirin ROM but need to go back to stock
Click to expand...
Click to collapse
Do you still get the orange security warning screen when you reboot? If so, follow the instructions about pressing Vol Up button, etc. to get into eRecovery. (Alternatively, try "adb reboot erecovery".) If eRecovery is still there, you would boot into a EMUI screen which supposedly allow you to download stock recovery and stock rom. (Another poster said that eRecovery won't work since Huawei hasn't released stock rom yet but it's worth trying.)
iammudd said:
Do you still get the orange security warning screen when you reboot? If so, follow the instructions about pressing Vol Up button, etc. to get into eRecovery. (Alternatively, try "adb reboot erecovery".) If eRecovery is still there, you would boot into a EMUI screen which supposedly allow you to download stock recovery and stock rom. (Another poster said that eRecovery won't work since Huawei hasn't released stock rom yet but it's worth trying.)
Click to expand...
Click to collapse
Yes I tried that but eRecovery fails, doesn't find any Roms available
wisdomzw said:
Yes I tried that but eRecovery fails, doesn't find any Roms available
Click to expand...
Click to collapse
Thanks for the feedback. Did it manage to restore stock recovery though?
iammudd said:
Thanks for the feedback. Did it manage to restore stock recovery though?
Click to expand...
Click to collapse
Not at all. Once it fails, there's no going any further than that
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Reflash it
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Wolfhawke said:
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Click to expand...
Click to collapse
Why? Root works fine with it, this has nothing to do with that.
crixley said:
Why? Root works fine with it, this has nothing to do with that.
Click to expand...
Click to collapse
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
jmill75 said:
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
Click to expand...
Click to collapse
Yes it works fine and the issue has nothing to do with root. Probably half of us using it are rooted without issue
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
tliebeck said:
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
Click to expand...
Click to collapse
Just got my Essential Phone today as well and did the exact same thing, flashed straight from 7.1.1 to P. I thought I was seriously going to have to send the phone back due to a broken Wi-Fi chip or something. You are seriously a lifesaver!
rignfool said:
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
If I take your post at face value... You have a bad flash and need to try again... Or blame your cable... And go buy a new one...
Otherwise... You have a bad download... Or there is something wrong wrong with your zip or batch/script... Or you're not completely unlocked
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Same here but can't roll back to Oreo
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
1jason said:
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
Click to expand...
Click to collapse
Yes flash the july oreo flashall. Bat
Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
I had the same problem. went back to stock on July's build (was on January's stock build previously) and reflashed P. Been smooth sailing ever since
jacksummers said:
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Click to expand...
Click to collapse
The reason is because one of the OTAs did not have the partition you're looking for... And it created a mismatch somewhere...
You DO NOT need to have the same software on A and B... It just makes troubleshooting easier from our perspective... And... It forces you to reflash and probably fix the problem...
As intended... There should ALWAYS be a mismatch between A and B... At least a monthly security update... If not an Android versioning difference
Edited. We are all just trying to help others. Lets keep it that way.
so, uhmmm like yea...... there is this thread here, called the stock images thread (link for posterity https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 ) this is firmware images, directly from essential. I have added the remaining images that you dont get from essential, so that way you can reflash, and get the same version of software on both sides. there are wipe and no wipe bat files in there, twrp11 (the working twrp we have), and the fix red boot (in case you broke verity), and a stockboot.img (coincidentally the same file as called boot in the zip, but renamed for your twrp/rooting pleasure).
These images work great, many many many people have used them to go back and forth between O and P, OTA, or recover from catastrophe. As usual, beware of dragons, make SURE SURE SURE SURE you have a working adb/fastboot environment (use the version that comes with essentials drivers) (you can always do ADB VERSION or FASTBOOT --VERSION ) to check your version and where its working out of. It is 1 stop shopping. I also know the guy that makes the zips
jacksummers said:
Edited. We are all just trying to help others. Lets keep it that way.
Click to expand...
Click to collapse
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
rignfool said:
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
Click to expand...
Click to collapse
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
jacksummers said:
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
Click to expand...
Click to collapse
Wouldn't it be easier to attempt to port the 2 or 3 features we don't have as a separate systemui.apk or framework-res.apk?
And use Magisk?
Since we don't have that fancy hardware photo rendering thingymabob
I'm about to jump of a ledge over here. So, I've read about this online as well.
I try to install 11.0.2.2.1N11AA and, by the numbers, this is what happens:
1. It says "Installation will continue when device isn't being used. To install now, tap Resume."
2. I tap resume.
3. It says: "Couldn't update
Installation problem"
4. I see and tap "Try again".
5. Loopback to step 1 -- ad infinitum.
How can I update this thing? Anyone have any luck?
And, on another note, at what point is my device not being used exactly? What is using my device that makes this update unworkable? I searched online, others have problems, no one seems to have solutions.
Others noticed this problem on XDA, nobody said anything so far. I found this thread through Google: https://forum.xda-developers.com/t/...-dumper-magisk_patched-guides.4175033/page-13 The Nov 23, 2020 at 10:44 AM reply. That man is in a similar situation as I!
I went through the remainder of the thread, searching for the username "raashnal" in each page until the end of the thread. The logic being, if anyone addressed his concern they would reply to it and he would presumably reply to thank that person. So, I figure the name must come up; it did not; so I assume this thread does not have an answer.
reilus said:
I'm about to jump of a ledge over here. So, I've read about this online as well.
I try to install 11.0.2.2.1N11AA and, by the numbers, this is what happens:
1. It says "Installation will continue when device isn't being used. To install now, tap Resume."
2. I tap resume.
3. It says: "Couldn't update
Installation problem"
4. I see and tap "Try again".
5. Loopback to step 1 -- ad infinitum.
How can I update this thing? Anyone have any luck?
And, on another note, at what point is my device not being used exactly? What is using my device that makes this update unworkable? I searched online, others have problems, no one seems to have solutions.
Others noticed this problem on XDA, nobody said anything so far. I found this thread through Google: https://forum.xda-developers.com/t/...-dumper-magisk_patched-guides.4175033/page-13 The Nov 23, 2020 at 10:44 AM reply. That man is in a similar situation as I!
I went through the remainder of the thread, searching for the username "raashnal" in each page until the end of the thread. The logic being, if anyone addressed his concern they would reply to it and he would presumably reply to thank that person. So, I figure the name must come up; it did not; so I assume this thread does not have an answer.
Click to expand...
Click to collapse
Hello again
So are you rooted at the moment? Do you have oxygen updater installed?
If you are rooted then please disable any and all active modules then reboot your phone.
Then open oxygen updater.
Accept the agreement and provide it any rights it needs then take the update (a full update)
It'll push it to your phone.
Go to settings /system updates / local upgrade.
Choose the zip downloaded by oxygen updater.
Do not reboot when it's complete.
Press home then reopen magisk and click install, then click install to inactive slot after OTA.
Let they install then click reboot, that should be it.
If you're not rooted then let me know.
PS: that's my thread btw, your rationale doesn't quite make sense, an answer could have been given and thanks provided or not. Meaning their name doesn't necessarily have to come up again at all.
It's not that long a thread tbh. The amount of responses I've had and issues addressed and resolved I would say that pretty much any issue to do with payload dumper, root has been addressed
Thank you! I was just about to say, I ended up using Oxygen updater and then doing a local install.
I cannot do an incremental update, but I can do a full update.
I did have an interesting problem, which I also solved. I could not do the OTA install of Magisk! So, I swiped the Oxygen Updater off the recents. Then I tried again and it worked! So, if anyone else has that issue, maybe that will help them !
And I understand that my rationale is flawed, any rational position is flawed. In fact, you won't find any epistemic approach -- even science -- without flaws. I declared my biases and methods to show that I feel I put in a reasonable effort before asking for help. I hope that was part of your understanding. =)
reilus said:
Thank you! I was just about to say, I ended up using Oxygen updater and then doing a local install.
I cannot do an incremental update, but I can do a full update.
I did have an interesting problem, which I also solved. I could not do the OTA install of Magisk! So, I swiped the Oxygen Updater off the recents. Then I tried again and it worked! So, if anyone else has that issue, maybe that will help them !
And I understand that my rationale is flawed, any rational position is flawed. In fact, you won't find any epistemic approach -- even science -- without flaws. I declared my biases and methods to show that I feel I put in a reasonable effort before asking for help. I hope that was part of your understanding. =)
Click to expand...
Click to collapse
If you are rooted then you're certainly not meant to do an incremental OTA as it needs to be a full update.
Haha and no need to prove your efforts to me pal, it's all good.
Just glad you're sorted.
PS: I've actually just updated the thread as 11.0.3.3 just arrived.
I've provided a patched boot img and have updated the guide already
reilus said:
I'm about to jump of a ledge over here. So, I've read about this online as well.
I try to install 11.0.2.2.1N11AA and, by the numbers, this is what happens:
1. It says "Installation will continue when device isn't being used. To install now, tap Resume."
2. I tap resume.
3. It says: "Couldn't update
Installation problem"
4. I see and tap "Try again".
5. Loopback to step 1 -- ad infinitum.
How can I update this thing? Anyone have any luck?
And, on another note, at what point is my device not being used exactly? What is using my device that makes this update unworkable? I searched online, others have problems, no one seems to have solutions.
Others noticed this problem on XDA, nobody said anything so far. I found this thread through Google: https://forum.xda-developers.com/t/...-dumper-magisk_patched-guides.4175033/page-13 The Nov 23, 2020 at 10:44 AM reply. That man is in a similar situation as I!
I went through the remainder of the thread, searching for the username "raashnal" in each page until the end of the thread. The logic being, if anyone addressed his concern they would reply to it and he would presumably reply to thank that person. So, I figure the name must come up; it did not; so I assume this thread does not have an answer.
Click to expand...
Click to collapse
I always have the same problem when I try to update. For whatever reason before I update I have to flash boot the "stock" boot.img and then my phone will accept the update.
State.of.mind said:
I always have the same problem when I try to update. For whatever reason before I update I have to flash boot the "stock" boot.img and then my phone will accept the update.
Click to expand...
Click to collapse
That's not true mate, if you're rooted there is simply no need to change the boot.img, use magisk to install to inactive slot before rebooting, that is it.
The update method you use whilst rooted is oxygen updater and it's a full OTA
dladz said:
That's not true mate, if you're rooted there is simply no need to change the boot.img, use magisk to install to inactive slot before rebooting, that is it.
The update method you use whilst rooted is oxygen updater and it's a full OTA
Click to expand...
Click to collapse
dladz said:
That's not true mate, if you're rooted there is simply no need to change the boot.img, use magisk to install to inactive slot before rebooting, that is it.
The update method you use whilst rooted is oxygen updater and it's a full OTA
Click to expand...
Click to collapse
I was sharing my experience with updates. Regardless of the update platform Oxygen Updater or One Plus I ALWAYS have to flash the stock boot.img prior to receiving an update.
I think the problem could be that when I flash the patched magisk boot image I flash it to both slots and not one single slot. I'll try the newer method when another update is released.
State.of.mind said:
I was sharing my experience with updates. Regardless of the update platform Oxygen Updater or One Plus I ALWAYS have to flash the stock boot.img prior to receiving an update.
I think the problem could be that when I flash the patched magisk boot image I flash it to both slots and not one single slot. I'll try the newer method when another update is released.
Click to expand...
Click to collapse
Yep again mate you don't need to do that, regardless where you download the update from provided it is in fact a full update