Related
I was running 3.2.8 as of this morning but decided to go back to stock, so I:
flashed stocked recovery
installed 3.2.8
setup my phone, etc
connected to my vpn
downloaded and installed the update
phone boots to 6.0.1/OOS 3.2.8
I don't get it. Originally I had an issue with the update, it wouldn't install. SO I rebooted to (stock) recovery and wiped cache, rebooted and was able to perform the update. But when the phone rebooted it booted to OOS 3.2.8. WTF?!
Update - it does NOT say update successful, okay so that's a little better. But why the OTA is failing is unknown.
dcdevito said:
Update - it does NOT say update successful, okay so that's a little better. But why the OTA is failing is unknown.
Click to expand...
Click to collapse
Why don't you try installing the update manually?
Formhault said:
Why don't you try installing the update manually?
Click to expand...
Click to collapse
I tried side loading but I get "can't read [filename].Zip"
dcdevito said:
I tried side loading but I get "can't read [filename].Zip"
Click to expand...
Click to collapse
Download the file again. It could be a bad download.
Also, make sure you're using the stock Nougat recovery.
Formhault said:
Download the file again. It could be a bad download.
Also, make sure you're using the stock Nougat recovery.
Click to expand...
Click to collapse
I reinstalled adb drivers and I can at least get the stock recovery to attempt to sideload it, but the install fails like it does from the system updater.
Could be the stock Nougat recovery that I am not using - perhaps I am using an older version - where can I verify the download for that?
For reference this is where I got the stock recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/recovery.img
(Update)
Got it to work - I get a dm-verity error on bootup, did a factory reset after the update but still get the error - but I got it. Thanks for your help, cheers
dcdevito said:
(Update)
Got it to work - I get a dm-verity error on bootup, did a factory reset after the update but still get the error - but I got it. Thanks for your help, cheers
Click to expand...
Click to collapse
How did you get it to work? Just curious.
About the dm-verity error... See this : https://forum.xda-developers.com/oneplus-3t/how-to/how-to-fix-dm-verity-issue-7-0-flashed-t3529680
Edit : whoops, it's for the 3T. Oh well...
Formhault said:
How did you get it to work? Just curious.
About the dm-verity error... See this : https://forum.xda-developers.com/oneplus-3t/how-to/how-to-fix-dm-verity-issue-7-0-flashed-t3529680
Edit : whoops, it's for the 3T. Oh well...
Click to expand...
Click to collapse
I re-downloaded the zip, I just wish I knew if the one I have was the latest version, and thus correct one.
Also, yeah I wish there was a OnePlus 3 Toolkit, not that I mind doing it all manually, I just don't have much time on weekdays to do this.....
dcdevito said:
I re-downloaded the zip, I just wish I knew if the one I have was the latest version, and thus correct one.
Click to expand...
Click to collapse
I see
dcdevito said:
Also, yeah I wish there was a OnePlus 3 Toolkit, not that I mind doing it all manually, I just don't have much time on weekdays to do this.....
Click to expand...
Click to collapse
Well, you missed this
Formhault said:
How did you get it to work? Just curious.
About the dm-verity error... See this : https://forum.xda-developers.com/oneplus-3t/how-to/how-to-fix-dm-verity-issue-7-0-flashed-t3529680
Edit : whoops, it's for the 3T. Oh well...
Click to expand...
Click to collapse
Formhault said:
I see
Well, you missed this
Click to expand...
Click to collapse
Cool, thanks - but I'm assuming this wasn't updated for Nougat, right?
dcdevito said:
Cool, thanks - but I'm assuming this wasn't updated for Nougat, right?
Click to expand...
Click to collapse
I stand correctd - looks like it TWRP and SU were indeed updated
Just got my nexus 5x a few weeks ago through google fi, got the phone rooted and TWRP installed. Got a message saying that an update was available, it downloaded and i restarted. Next time I looked at the phone it had loaded into TWRP. I booted into system, and the phone is still on 7.1.1, and if I try to run an update check it comes back saying I'm up to date... Anyone else have that issue, or suggestions?
pinkydw said:
Just got my nexus 5x a few weeks ago through google fi, got the phone rooted and TWRP installed. Got a message saying that an update was available, it downloaded and i restarted. Next time I looked at the phone it had loaded into TWRP. I booted into system, and the phone is still on 7.1.1, and if I try to run an update check it comes back saying I'm up to date... Anyone else have that issue, or suggestions?
Click to expand...
Click to collapse
It was your root and TWRP that prevented 7.1.2 update. Either flash factory images or use flashfire app to update..
indian84 said:
It was your root and TWRP that prevented 7.1.2 update. Either flash factory images or use flashfire app to update..
Click to expand...
Click to collapse
Thanks, I'll look at the flashfire. I'm debating trying lineageOS, but I'm hesitant to mess with a new phone too much.
https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Check out section 9. I do this with every new release and it works fine. I flash the files followed by TWRP and then Magisk/SuperSU
The1nonly1 said:
https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Check out section 9. I do this with every new release and it works fine. I flash the files followed by TWRP and then Magisk/SuperSU
Click to expand...
Click to collapse
Oooohhhh, Danke! I think I used that guide when I rooted my phone to begin with.
Ok, dumb question, if I flash the OTA image, does that wipe data?
pinkydw said:
Ok, dumb question, if I flash the OTA image, does that wipe data?
Click to expand...
Click to collapse
No, if you follow step 9 and not the others, you will keep all data. You do need to download the whole factory image and not the OTA as you cant use that to update since you are rooted and have TWRP installed. Use this link for the latest image - https://developers.google.com/android/images?hl=en#bullhead
The1nonly1 said:
No, if you follow step 9 and not the others, you will keep all data. You do need to download the whole factory image and not the OTA as you cant use that to update since you are rooted and have TWRP installed. Use this link for the latest image - https://developers.google.com/android/images?hl=en#bullhead
Click to expand...
Click to collapse
Finally got around to trying this, there was no cache file, does it take a while to load? Its got pass the google logo and doing the weird 4 circle animation thing.
https://forum.xda-developers.com/showpost.php?p=71723898&postcount=1744
I think this guy had the same issue, going to try his suggestion.
pinkydw said:
https://forum.xda-developers.com/showpost.php?p=71723898&postcount=1744
I think this guy had the same issue, going to try his suggestion.
Click to expand...
Click to collapse
Yes, the new 7.1.2 doesn't have cache file. I just got the one from the 7.1.1 build and used that.
The1nonly1 said:
Yes, the new 7.1.2 doesn't have cache file. I just got the one from the 7.1.1 build and used that.
Click to expand...
Click to collapse
That worked
Guess its time to try this again
I have Magisk installed and decided to try out some of the modules for it but could never get them to update it said on all that they would update on next reboot, well after several reboots nothing. I clicked on the little garbage can to delete and they wouldn't delete?? I ended up having to uninstall magisk to get rid of them and had to reinstall magisk to get root back.. Any one else have any problems with the modules??
blake .l said:
I have Magisk installed and decided to try out some of the modules for it but could never get them to update it said on all that they would update on next reboot, well after several reboots nothing. I clicked on the little garbage can to delete and they wouldn't delete?? I ended up having to uninstall magisk to get rid of them and had to reinstall magisk to get root back.. Any one else have any problems with the modules??
Click to expand...
Click to collapse
I had a similar problem. It took multiple reinstalls of magisk to get it working, hang in there you'll get it working. That's just one of the issues with how this phone handles many different things. T-Mobile has had to issue updates to fix updates and that has potential to turn people away from an otherwise great piece of hardware. Hang in there you'll figure this phone out.
Sent from my Moto Z (2) using XDA Labs
blake .l said:
I have Magisk installed and decided to try out some of the modules for it but could never get them to update it said on all that they would update on next reboot, well after several reboots nothing. I clicked on the little garbage can to delete and they wouldn't delete?? I ended up having to uninstall magisk to get rid of them and had to reinstall magisk to get root back.. Any one else have any problems with the modules??
Click to expand...
Click to collapse
Out of curiosity, did you go through the full TWRP installation, or just use it to boot and install Magisk?
dismembered3po said:
Out of curiosity, did you go through the full TWRP installation, or just use it to boot and install Magisk?
Click to expand...
Click to collapse
Did the full TWRP install them installed Magisk
Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.
Works fine for me.
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Working fine for me as well.
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.
RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.
Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018
I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse
Already prompted to install 11.2.7.7. About to install/re-root.
Normal process for taking the OTA and keeping root worked without any issue.
are you doing both Direct & Inactive slot Install before Reboot?
dmarden said:
Already prompted to install 11.2.7.7. About to install/re-root.
Click to expand...
Click to collapse
where did you get it?
dmarden said:
Normal process for taking the OTA and keeping root worked without any issue.
Click to expand...
Click to collapse
Can you give me the kernel patch file? magisk
Hey, I just got the update, and Restoring the boot image with Magisk no longer allows me to install the update without unrooting. at first it is downloading for a bit, then it goes to "installation problem", which is not something that happened last time
Is this normal?
Andrew8578 said:
Hey, I just got the update, and Restoring the boot image with Magisk no longer allows me to install the update without unrooting. at first it is downloading for a bit, then it goes to "installation problem", which is not something that happened last time
Is this normal?
Click to expand...
Click to collapse
You don't need to restore anything in order to update to a New OTA. Simply disable any magisk module you use. Reboot your device then let the OTA install it self. Once done, DO Not reboot and just go to magiskmanager, and install magisk to the available slot. After what you can reboot your device, re apply your magisk modules. Et voilà
Fre$h said:
You don't need to restore anything in order to update to a New OTA. Simply disable any magisk module you use. Reboot your device then let the OTA install it self. Once done, DO Not reboot and just go to magiskmanager, and install magisk to the available slot. After what you can reboot your device, re apply your magisk modules. Et voilà
Click to expand...
Click to collapse
I just did that and nothing has changed. If someone can give the 11.2.7.7aa image, that would help alot
galaxys said:
are you doing both Direct & Inactive slot Install before Reboot?
Click to expand...
Click to collapse
Yes
vibrantliker said:
where did you get it?
Click to expand...
Click to collapse
Just through the normal system updater.
dimmed said:
Can you give me the kernel patch file? magisk
Click to expand...
Click to collapse
No, sorry, I don't do this.
Andrew8578 said:
Hey, I just got the update, and Restoring the boot image with Magisk no longer allows me to install the update without unrooting. at first it is downloading for a bit, then it goes to "installation problem", which is not something that happened last time
Is this normal?
Click to expand...
Click to collapse
I followed my normal process (I don't use any Magisk modules):
Magisk Uninstall->Restore Images (do not reboot)
Take OTA (do not reboot)
Install Magisk to both active and inactive
Reboot
Worked without issue, as always.
I found 11.2.7.7.LE15AA, disabled all magisk modules rebooted, installed update reinstalled magisk to other slot, rebooted now I'm boot looped and in recovery, set it back from A to B (was previously on B), as obviously slot_A is non-functional or something went wrong with the upgrade from 11.2.5.5.LE15AA to 11.2.7.7.LE15AA, same problem still boot-looped.
Maybe teh custom kernel was to blame, I'll try restoring boot image and try again
I'd so prefer a full zip if they every provide one for the LE15AA version, as this method is never easy
egandt said:
I found 11.2.7.7.LE15AA, disabled all magisk modules rebooted, installed update reinstalled magisk to other slot, rebooted now I'm boot looped and in recovery, set it back from A to B (was previously on B), as obviously slot_A is non-functional or something went wrong with the upgrade from 11.2.5.5.LE15AA to 11.2.7.7.LE15AA, same problem still boot-looped.
Maybe teh custom kernel was to blame, I'll try restoring boot image and try again
I'd so prefer a full zip if they every provide one for the LE15AA version, as this method is never easy
Click to expand...
Click to collapse
Yeah, I don't do any custom kernel stuff or magisk modules, I cannot personally comment. What I know, for me, is the process fails 100% of the time if I don't do the Magisk image restore and it succeeds 100% of the time if I do.
I am currently on 11.2.4.4 AA (Global), rooted. Can I upgrade to the EU ROM since they tend to get full updates while AA has not been? If so, do I just flash the 11.2.6.6 EU ROM or should I flash 11.2.4.4 EU ROM then flash a more up-to-date ROM? If I flash the EU ROM, would I loose anything?
As rooted you have to flash OTA using full OTA zip file that you can download using oxygen updater app. Incremental OTA method cannot work properly.
On Oxygen updater app, download the full zip file (it will detect Magisk and advise you to use that method.)
Once downloaded, be sure that every magisk module are disabled and reboot.
Now go to parameters/system/system update then click on the upper right icon and chose local update. If it's not already done, point to the full zip file location and let the update process run to the end.
Once done, do not reboot and use magiskmanager to reflash magisk to the available slot.
Fre$h said:
As rooted you have to flash OTA using full OTA zip file that you can download using oxygen updater app. Incremental OTA method cannot work properly.
On Oxygen updater app, download the full zip file (it will detect Magisk and advise you to use that method.)
Once downloaded, be sure that every magisk module are disabled and reboot.
Now go to parameters/system/system update then click on the upper right icon and chose local update. If it's not already done, point to the full zip file location and let the update process run to the end.
Once done, do not reboot and use magiskmanager to reflash magisk to the available slot.
Click to expand...
Click to collapse
Not sure if this was for someone specific for their unique circumstance. If this was just meant generally, then it is inaccurate.
I don't use Oxygen Updater. I just take the incremental OTA using the steps I mentioned.
Fre$h said:
As rooted you have to flash OTA using full OTA zip file that you can download using oxygen updater app. Incremental OTA method cannot work properly.
On Oxygen updater app, download the full zip file (it will detect Magisk and advise you to use that method.)
Once downloaded, be sure that every magisk module are disabled and reboot.
Now go to parameters/system/system update then click on the upper right icon and chose local update. If it's not already done, point to the full zip file location and let the update process run to the end.
Once done, do not reboot and use magiskmanager to reflash magisk to the available slot.
Click to expand...
Click to collapse
Just letting you know, Oxygen Updater is stuck on 11.2.4.4, as is the OnePlus website.
dmarden said:
Already prompted to install 11.2.7.7. About to install/re-root.
Click to expand...
Click to collapse
I am also in 7.7 NA, is it possible to root NA version. As NA use google services for updates. how to update, i heard no full zips updates in NA
Atul Menon said:
I am also in 7.7 NA, is it possible to root NA version. As NA use google services for updates. how to update, i heard no full zips updates in NA
Click to expand...
Click to collapse
Easy. You open magisk and restore stock boot. Don't reboot yet. Download and install update. Don't reboot yet. Open magisk and install to inactive slot. Reboot.
dmarden said:
Normal process for taking the OTA and keeping root worked without any issue.
Click to expand...
Click to collapse
you are saying taking this incremental ota worked for you? I did the exact same steps (restore images, install without rebooting, install to inactive slot) and my system is still stuck on 11.2.4.4, I do not know what the issue is
thirtythr33 said:
you are saying taking this incremental ota worked for you? I did the exact same steps (restore images, install without rebooting, install to inactive slot) and my system is still stuck on 11.2.4.4, I do not know what the issue is
Click to expand...
Click to collapse
Works for me every time...that way just post it.
netgar said:
Works for me every time...that way just post it.
Click to expand...
Click to collapse
yeah my system reports 11.2.4.4, yet have an incremental update for 11.2.7.7, which is odd for a number of reasons. long story short I'm sure it will cause me issues to try applying an incremental update that is not in order, but idk why 11.2.7.7 is showing up on my system, bc 11.2.6.6 never installed (or the system doesn't report it did)