Related
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
You need to unroot too.
Ota can be downloaded online.
d1wepn said:
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
Click to expand...
Click to collapse
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
rootSU said:
You need to unroot too.
Ota can be downloaded online.
Click to expand...
Click to collapse
I was hoping to use the factory OTA update method for a change. (Always manually update) But might just be easier.
Downloading OTA now. Thanks for the advice rootSU
Evolution_Freak said:
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
Click to expand...
Click to collapse
Might give this a try first. Worth a shot. Cheers mate.
OTA update downloads to system/cache folder ... It may get deleted soon after you try installing and restart the phone. You need rooted phone and a file explorer like es file explorer for accessing system folder.
Sent from android one lollypop 5.1
---------- Post added at 12:47 AM ---------- Previous post was at 12:38 AM ----------
Check first whether you have it in your phone already. Rooted phone go to /cache folder you'll find something.Zip there.
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Sorry I can't help you. I don't want that AT&T 5.1 update. So I did what you did and hit install. It of course didn't. I use TWRP also. But the damn 5.1 update is back!
Tappin from my Nexus 6
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Gage_Hero said:
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
um.. you are quite a bit late. this is an old thread, look at the dates. you responded to a question thats 6 month old.
liquidzoo said:
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Click to expand...
Click to collapse
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Rocky1988 said:
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Click to expand...
Click to collapse
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Amos91 said:
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Click to expand...
Click to collapse
How do you check version numbers for the other files? This may be what I'm after!
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
I'm unable to find the latest update in the /system folder (/system/cache doesn't exist on my device) or the /cache folder either.
/data/data/com.google.android.gms/app_download/update.zip
d1wepn said:
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Click to expand...
Click to collapse
Use Flashify to install OTA updates instead.
At last i found it
I have clock work recovery installed on my phone. It refuses to update my OTA factory software update, i searched for it and installed it manually. It was in /data/data/com.tinno.systemupdate/files/googleota/0/update.zip
Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.
pzzamakr1999 said:
Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.
Click to expand...
Click to collapse
logs from odin? Or any error code or anything?
Nothing from Odin at all. Odin registered it as a Pass. And I'm unsure how I would pull logs from the phone. Once the "Error!" appears during update, the phone will enter a bootloop unless I hold down the power button to enter Recovery. I was able to successfully enter Recovery, reinstall the Pie Beta Update from my SD card, and the phone works fine again. However, I do use Samsung Pay, and I've noticed that service has suffered considerably, so I'd like to go back to Oreo for the moment.
pzzamakr1999 said:
Nothing from Odin at all. Odin registered it as a Pass. And I'm unsure how I would pull logs from the phone. Once the "Error!" appears during update, the phone will enter a bootloop unless I hold down the power button to enter Recovery. I was able to successfully enter Recovery, reinstall the Pie Beta Update from my SD card, and the phone works fine again. However, I do use Samsung Pay, and I've noticed that service has suffered considerably, so I'd like to go back to Oreo for the moment.
Click to expand...
Click to collapse
I wouldnt be suprised if samsung locked going back same what they did with nougat/oreo . I cant help u, sry
pzzamakr1999 said:
Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.
Click to expand...
Click to collapse
Which ODIN are you using? Make sure you're using the modded 3.13.1. Try this: Uncheck the auto-reboot option on ODIN. Flash the Oreo firmware and let it finish. Once it's done, manually reboot into recovery and perform a factory reset. Then boot into the OS.
ScaleneVirus288 said:
I wouldnt be suprised if samsung locked going back same what they did with nougat/oreo . I cant help u, sry
Click to expand...
Click to collapse
That only happens when they update the bootloader version. It has nothing to do with the OS version. The Pie leaks are still on the v5 bootloader.
Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?
pzzamakr1999 said:
Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?
Click to expand...
Click to collapse
Also check the USB port, use the older USB port this has happened to me or PC and see the phone is probably not compatible with newest USB port....
Sent from my SM-N960U using Tapatalk
pzzamakr1999 said:
Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?
Click to expand...
Click to collapse
What issues are you having with Spay? It seems to work for everyone else, me included.
No, you can't flash a different radio.
Not sure yet what will be required when when the official drops. Won't know until it drops.
So the Pay app opens fine, and it authenticates the card without issue. It will also allow me to put my fingerprint in, and then have the countdown start. However, it doesn't seem to enable the mag spoofer or the nfc chip, and when put next to a mag reader or Pay system, nothing happens. The countdown will continue, and will restart if I ask it to. But again, the phone doesnt seem to do anything.
pzzamakr1999 said:
So the Pay app opens fine, and it authenticates the card without issue. It will also allow me to put my fingerprint in, and then have the countdown start. However, it doesn't seem to enable the mag spoofer or the nfc chip, and when put next to a mag reader or Pay system, nothing happens. The countdown will continue, and will restart if I ask it to. But again, the phone doesnt seem to do anything.
Click to expand...
Click to collapse
Weird. I'll have to try it. I thought it was working, but now I'm not sure. I use my Gear S3 so often to pay, now I'm not sure LOL.
Update on the effort to revert back to CRK1.
Used the modified Odin, and un-checked auto-reboot. Phone remained in Download mode.
I could not figure out a way to go from Download mode to recovery mode directly. If someone knows how to do this, it would be appreciated if you could let me know.
However, rather than the "Error!" message, I received a "Erasing" message. Than the phone rebooted, and just kept rebooting, going from T-Mobile splash screen to Samsung and back over and over, with some optimizing apps screens thrown in for good measure.
So I tried again with auto-reboot on, and this time received the "Error!" message, and was able to go into recovery once that happened.
The odd thing is, nothing on my phone was changed, other than having to redo the Samsung biometrics for security. All of my apps and accounts and emails were already there, undeleted.
One more update on the S-Pay. After reinstalling the Update.zip from my SD card in Recovery, iIt does seem like there may have been a change. It is now doing the vibrate thing, which I don't think it was doing before. I will put it to the test later this week.
Downgrade Successful
Performed Factory Reset from Phone menus. (not doing so kept resulting in an unauthorized factory reset prompt)
Performed Factory Reset from Recovery Menu.
Cleared Cache through Recovery Menu
Used Patched Odin
Kept Auto-Restart Checked
Used SamMobile CRK1
Phone restarted successfully.
pzzamakr1999 said:
Performed Factory Reset from Phone menus. (not doing so kept resulting in an unauthorized factory reset prompt)
Performed Factory Reset from Recovery Menu.
Cleared Cache through Recovery Menu
Used Patched Odin
Kept Auto-Restart Checked
Used SamMobile CRK1
Phone restarted successfully.
Click to expand...
Click to collapse
Yes! I'm sorry I thought I told you to try a factory reset. You have to factory reset when downgrading. Otherwise bootloop city. Sorry I wasn't more clear, I could've saved you some frustration.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
I just went back and re-read my posts. I never said try a factroy reset first. Grrr...I'm so sorry!
Mr. Orange 645 said:
Yes! I'm sorry I thought I told you to try a factory reset. You have to factory reset when downgrading. Otherwise bootloop city. Sorry I wasn't more clear, I could've saved you some frustration.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
I just went back and re-read my posts. I never said try a factroy reset first. Grrr...I'm so sorry!
Click to expand...
Click to collapse
No worries, and I did very much appreciate the help. I should have realized that that should come first. I was a bit frustrated and wasn't thinking logically. It was actually the "fixing apps" message you get when you upgrade that clued me in I wasn't properly resetting the phone prior to install.
Regardless, its all good, and now that I know how to do it, I'll be more inclined to try these out in the future.
Any specific reason for the downgrade? Anything not working?
Camera issues on pie beta
My ar emoji not working on this pie update and sometimes force closes any1 else having this issue
Fitted2 said:
My ar emoji not working on this pie update and sometimes force closes any1 else having this issue
Click to expand...
Click to collapse
Yes
Mr. Orange 645 said:
Yes
Click to expand...
Click to collapse
You downgraded because no AR emoji? And what force closes are you having?
dami00976 said:
You downgraded because no AR emoji? And what force closes are you having?
Click to expand...
Click to collapse
I never said I downgraded.
Hi everyone,
I know loads of people ask why they're not getting updates, I hope that my question is sufficiently different from those! If not then feel free to point me to the noob's corner.
In December I joined beta labs but never installed Pie beta before the programme was closed. Online I had the option to revert OTA but since I hadn't actually updated to Pie beta I didn't take that option.
In January I was offered the Pie update which I downloaded but then didn't install when I read that it was still full of bugs. I have disabled automatic updates in developer options which is how I was able to do this.
A few days after that my option of installing the Pie update I had downloaded disappeared and since then I have have not been offered any more updates. I have checked repeatedly. I asked support and they told me to try this:
Go to Settings > Apps and notifications > App info > Google Play services > Storage > Clear data and Clear cache
2. Settings > Security and location > Location Off
3. Soft reset: Press and hold at the same time Power key and Volume Up for Only 10 sec, until short phone vibration and Powered by Android message. Your phone will restart, without deleting your data.
4. Please remove the phone SIM card. (Also you can try it with SIM card from another operator)
5. After that, please check for the update availability via Wi-Fi network: Settings > System > System update > Check for update
Click to expand...
Click to collapse
This didn't work. They have also suggested trying a SIM from another operator or doing a factory reset, neither of which I have tried yet. I will try another SIM when I get chance, but for me the factory reset is a the almost last resort - the last one is sending for repair under warranty, which I will wait until the last minute to do.
The step above about clearing the cache made me wonder - could the fact that I have previously downloaded but not installed an update be blocking the process? Where would this downloaded update be stored and how would I clear it? Is it in the cache or data of an app?
I will also try booting into recovery and clearing the cache partition, but my phone won't boot into recovery using buttons, I have to use ADB, which I cannot do right now.
Any suggestions welcome.
Cheers
madb1lly said:
Hi everyone,
I know loads of people ask why they're not getting updates, I hope that my question is sufficiently different from those! If not then feel free to point me to the noob's corner.
In December I joined beta labs but never installed Pie beta before the programme was closed. Online I had the option to revert OTA but since I hadn't actually updated to Pie beta I didn't take that option.
In January I was offered the Pie update which I downloaded but then didn't install when I read that it was still full of bugs. I have disabled automatic updates in developer options which is how I was able to do this.
A few days after that my option of installing the Pie update I had downloaded disappeared and since then I have have not been offered any more updates. I have checked repeatedly. I asked support and they told me to try this:
This didn't work. They have also suggested trying a SIM from another operator or doing a factory reset, neither of which I have tried yet. I will try another SIM when I get chance, but for me the factory reset is a the almost last resort - the last one is sending for repair under warranty, which I will wait until the last minute to do.
The step above about clearing the cache made me wonder - could the fact that I have previously downloaded but not installed an update be blocking the process? Where would this downloaded update be stored and how would I clear it? Is it in the cache or data of an app?
I will also try booting into recovery and clearing the cache partition, but my phone won't boot into recovery using buttons, I have to use ADB, which I cannot do right now.
Any suggestions welcome.
Cheers
Click to expand...
Click to collapse
Another XDA member by the handle THMSP posted the Internal OTA for Android PIE in the main "Android 9 PIE Updates" forum, on page 42 to be precise. You could try to download the OTA and "flash" it manually using a dialer code THMSP included in his inital post
---------- Post added at 07:02 PM ---------- Previous post was at 06:58 PM ----------
https://forum.xda-developers.com/nokia-8/how-to/pie-near-beta-labs-available-nokia-8-t3867037/page42
Thanks for the tip. I didn't want to go down that road of sideloading updates from unknown sources, but it's good to know the option is there.
As it was, I tried an old SIM from a previous contract (therefore the SIM was no longer valid) and the phone immediately showed me the update. This is a tip worth knowing for anyone else that gets stuck (it was actually support which told me to try it, but I was skeptical and now please to see it worked).
Cheers
I went to check for system updates today and my pixel initially started to download the latest patch and then after a couple of seconds went straight to telling me that there is no update available. Anyone else have this issue and/or successfully update to the March 2020 OTA via the process below?
Updating Phone Once Rooted:
- Check for device updates, when found:
- Tap uninstall in 'Magisk Manager'
- Tap restore images
- install OTA (do not reboot)
- Back to magisk, tap install > select install to inactive slot
- When magisk installed, press the reboot button in it. It'll force to the other slot AND you'll be updated AND rooted​
I assume I should be able to go under 'System' -> 'Advanced' and get the OTA under 'System Update'. I've already disabled 'Automatic system updates' under 'Developer Options'. Just making sure google is somehow not blocking the update on rooted devices and that the above steps are correct. Thank you in advance!
Found similar thing on reddit here.
It's very common for unlocked and rooted Pixel phones to not "find" or complete the monthly OTA updates. There must be some sort of check in the OTA process that fails on rooted phones.
You should get familiar with the "sideloading" process of manually flashing OTA images.
Here is a set of instructions that I wrote in my Pixel 3a rooting guide. The process is exactly the same for the Pixel 4 series.
Taking an OTA update should be as easy as the above instructions. However there is another option available to install an OTA update called sideloading. Sometimes the update doesn't appear on the phone in a timely manner and you may want to manually install the update. Other times the OTA update seems to fail for some reason. In the end, you may decide to sideload the OTA instead of trying get it via the update feature on the phone. Surprisingly, it's actually faster to install the update via sideloading than it will be to take the OTA normally. I'll walk through the sideloading steps.....
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on some Android 10 images, but not all.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (See note below about initial boot times).
Step 9 - To obtain root again, please use one of the two root methods listed above
Please note, the initial boot may take quite a while. I've seen the process take upwards of 20 minutes and longer. I think part of the reason it can take so long is that it optimizes the apps during this boot process. The more apps you have, the longer the process may take. When you take a regular OTA update, the phone will change to a screen where is specifically tells you it is optimizing the apps and counts up as the apps are optimized to give you status updates. When you use the the side-load method, it all happens with just the regular boot animation running and without any status updates. Because of this, it is easy to assume something has gone wrong with the boot process while in fact the phone is working through the process normally. If it isn't boot looping (showing the initial power screen before moving back to the boot animation), everything is fine and you just be patient and let the phone complete the process.
Click to expand...
Click to collapse
sic0048 said:
It's very common for unlocked and rooted Pixel phones to not "find" or complete the monthly OTA updates. There must be some sort of check in the OTA process that fails on rooted phones.
You should get familiar with the "sideloading" process of manually flashing OTA images.
Here is a set of instructions that I wrote in my Pixel 3a rooting guide. The process is exactly the same for the Pixel 4 series.
Click to expand...
Click to collapse
Thanks for the reply! I'm very used to sideloading/dirty flashing the updates, was hoping to use the Magisk method . Seems like google is getting smarter with their updates. I am guessing the current inability to see the OTA is due to the updates with google pay and google wanting to ensure banks it is safe.
I just finished sideloading March's OTA and patching the boot.img and everything seems to work, just a bit more effort than leveraging Magisk.
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
I experienced same exact thing. Looks like it saw the update at first then after a few seconds reverted to No updates available. About to try uninstalling Magisk, if no bueno, then gonna just sideload.
Spookymyo said:
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
Click to expand...
Click to collapse
Did you disable 'Automatic system updates' on the phone? That should still allow the download to occur just not the install. It seems like google got smarter with this update to detect rooted phones.
Gooch4130 said:
Did you disable 'Automatic system updates' on the phone? That should still allow the download to occur just not the install. It seems like google got smarter with this update to detect rooted phones.
Click to expand...
Click to collapse
Yes I disabled automatic updates. It didn't do it automatically, I clicked the check for update button. Normally when I do that it says there's a download available and then I know to check online for the flash file. This time it updated without stopping.
FAILED (remote: Failed to write to partition Not Found)
what i am doing wrong ????
---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------
Boot loader is unlocked...
10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)
this version i did ota update
i am from germany.
okay, i found a way to root, but how is it with safety net fix ???
anyone an idea ???
Deleted
Spookymyo said:
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
Click to expand...
Click to collapse
It installed the OTA for me too, now I'm afraid to restart my phone.
mattcoz said:
It installed the OTA for me too, now I'm afraid to restart my phone.
Click to expand...
Click to collapse
I would flash Magisk again before you restart.
I still can't get my phone rooted. I'm not sure what's going on. I wonder if other people have been able to successfully root the March update.
I successfully rooted the March update, using the boot.img method.
Spookymyo said:
I would flash Magisk again before you restart.
I still can't get my phone rooted. I'm not sure what's going on. I wonder if other people have been able to successfully root the March update.
Click to expand...
Click to collapse
I rooted with boot.img method, as well
sruel3216 said:
I rooted with boot.img method, as well[/QUOTE
I ended up following this
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse
I got it rooted. It ended up taking a factory reset. It must have been some file interfering with the process. Once I reset my phone the rooting process went without incident.
As I'm searching for a more Phone based update wy, I'm thinking about to use maybe the Implemented OTA Process, but download the OTA-File manually... But for that We must know,how the OTA process is working. Did someone know:
- Where the update stores the download fine (I found a OTA and a OTA_Packge directory in the /Data/ folder)
- is there maybe a setting or information which must be injected somewhere (maybe a txt file)
- after that the ota update could then maybe started by hand
Has someone informations on that? If maybe someone where the ota still works and stil has root could check the files and places?
Chris.C said:
sruel3216 said:
I rooted with boot.img method, as well[/QUOTE
I ended up following this
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse
Worked like charm!! Thanks!! :good:
Click to expand...
Click to collapse
I unlocked the bootloader, sideloaded the August 2020 OTA and flashed the patched boot image. Kept bootlooping, then I restored to the original, booted in, installed Magisk Manager and then flashed the patched image again. Just leaving this here in case it helps someone.
Last night I did the system update and left it overnight. This morning the update wasn't installed and asked me to update again. So I started it again 3 hours ago and it's still not done. Anyone else's update taking this long?
Update: I attempted the system update again and left it overnight. This morning it's still stuck on the same installing screen.
Can someone share the Android Version screen of an unlocked Pixel 7. I think I might be updated and the update is just a bug?
Update: I determined I had an OTA update failure. So I just adb sideloaded the OTA file and it's fixed now.
KillerDroid96 said:
Last night I did the system update and left it overnight. This morning the update wasn't installed and asked me to update again. So I started it again 3 hours ago and it's still not done. Anyone else's update taking this long?
Click to expand...
Click to collapse
I saw your previous post about wifi not staying on. So if that happening while dl. It my screw it. Because it's jumping back to network data and the setting maybe set to only update over wifi.
ern88 said:
I saw your previous post about wifi not staying on. So if that happening while dl. It my screw it. Because it's jumping back to network data and the setting maybe set to only update over wifi.
Click to expand...
Click to collapse
It's set to mobile data and that should only impact the downloading not installing. 4 hours now and still stuck. I'm considering rebooting at this point.
I had the same problem, i rebooted and it all seems gone. But I checked the factory images and everything is up to date.
Giovanni9518 said:
I had the same problem, i rebooted and it all seems gone. But I checked the factory images and everything is up to date.
Click to expand...
Click to collapse
That didn't work. I'm back at the same screen as before after hitting restart now. I also noticed that Google play system update is on July.
KillerDroid96 said:
That didn't work. I'm back at the same screen as before after hitting restart now. I also noticed that Google play system update is on July.
Click to expand...
Click to collapse
My Google play system also states that too.
Well I give up. I restarted and I'm just not going to update for the time being.
ern88 said:
My Google play system also states that too.
Click to expand...
Click to collapse
I think I'm actually fully updated and its just a bug?
@ern88 can you share a screenshot of your Android Version screen please. I'm trying to determine if I'm fully updated and its just a bug.
KillerDroid96 said:
@ern88 can you share a screenshot of your Android Version screen please. I'm trying to determine if I'm fully updated and its just a bug.
Click to expand...
Click to collapse
Here is the ver I'm on. I see you still are on the factory version. Not the Oct update. By chance. Did your carrier give you a new sim card with your phone? Telus have me a new sim card when I bought the phone.
ern88 said:
Here is the ver I'm on. I see you still are on the factory version. Not the Oct update. By chance. Did your carrier give you a new sim card with your phone? Telus have me a new sim card when I bought the phone.
Click to expand...
Click to collapse
Thanks! I determined I had an OTA
update failure. So I just adb sideloaded the OTA file and it's fixed now.
So I'm having the same issue, but potentially for a different reason.
I'm rooted. Typically to resolve this issue, you
1 - select Uninstall Magisk/Restore Image. This restores your stock boot image
2 - Install OTA update
3 - You then install Magisk again once the update completes and select "flash to inactive slot" prior to reboot.
The Uninstall/image restore in Magisk is not removing Magisk and the update still fails.
I'm wondering if it is restoring the boot.img, when it is the initboot.img that has been modified.
I could be wrong, just thought I'd note my issue.
gorilla p said:
So I'm having the same issue, but potentially for a different reason.
I'm rooted. Typically to resolve this issue, you
1 - select Uninstall Magisk/Restore Image. This restores your stock boot image
2 - Install OTA update
3 - You then install Magisk again once the update completes and select "flash to inactive slot" prior to reboot.
The Uninstall/image restore in Magisk is not removing Magisk and the update still fails.
I'm wondering if it is restoring the boot.img, when it is the initboot.img that has been modified.
I could be wrong, just thought I'd note my issue.
Click to expand...
Click to collapse
They've covered this in the two big threads regarding unlocking / rooting in the 7 Pro-forum.