We might be able to install OTA without restoring the /system /boot and so on.
In /system/usr/bin there are a few programs for installing and checking the OTA package,
One of them is "update_engine", which is called just before my update fails, it returns:
Code:
update_engine: [1124/214750:ERROR:utils.cc(193)] fd >= 0 failed: No such file off directory
Later it tries to read from fstab and return a hash of a partition which fails, because it is modified.
Do you think it is possible to trick it in to returning positive hash or am I wrong.
More info in the screenshot.
EDIT: added OTA log
Bump.
I'd love an easy solution for this as well! I'm unlocked/rooted/stock and would love an easier way to apply OTA updates than waiting for someone to post the full patched firmware.
hugehead83 said:
Bump.
I'd love an easy solution for this as well! I'm unlocked/rooted/stock and would love an easier way to apply OTA updates than waiting for someone to post the full patched firmware.
Click to expand...
Click to collapse
1) Just flash the lastest stock firmware over your current install but don't wipe 'userdata'.
2) Take the latest OTA
3) Re-root.
Takes 10-15 min tops.
ptn107 said:
1) Just flash the lastest stock firmware over your current install but don't wipe 'userdata'.
2) Take the latest OTA
3) Re-root.
Takes 10-15 min tops.
Click to expand...
Click to collapse
Why wouldn't you just flash the latest update instead of going through all that?
ptn107 said:
1) Just flash the lastest stock firmware over your current install but don't wipe 'userdata'.
2) Take the latest OTA
3) Re-root.
Takes 10-15 min tops.
Click to expand...
Click to collapse
I keep getting E: failed to mount / in recovery
Ok, I did some more digging and as it turn out, even when I restored my phone to stock and tried to install from OTA, it somehow set the ROOTED flag to true, I don't understand why since my deice wasn't rooted at that moment.
TeamRainless said:
Why wouldn't you just flash the latest update instead of going through all that?
Click to expand...
Click to collapse
That only works if you are not rooted unfortunately : (
---------- Post added at 02:45 PM ---------- Previous post was at 02:27 PM ----------
ptn107 said:
1) Just flash the lastest stock firmware over your current install but don't wipe 'userdata'.
2) Take the latest OTA
3) Re-root.
Takes 10-15 min tops.
Click to expand...
Click to collapse
Thanks,
I've been looking for the latest stock firmware but can't find it anywhere. Also: wouldn't the latest stock firmware also include the latest OTA?
hugehead83 said:
That only works if you are not rooted unfortunately : (
---------- Post added at 02:45 PM ---------- Previous post was at 02:27 PM ----------
Thanks,
I've been looking for the latest stock firmware but can't find it anywhere. Also: wouldn't the latest stock firmware also include the latest OTA?
Click to expand...
Click to collapse
There is a collection of them on afh
hugehead83 said:
That only works if you are not rooted unfortunately : (
---------- Post added at 02:45 PM ---------- Previous post was at 02:27 PM ----------
Thanks,
I've been looking for the latest stock firmware but can't find it anywhere. Also: wouldn't the latest stock firmware also include the latest OTA?
Click to expand...
Click to collapse
Not necessarily. The latest firmware usually lags behind the latest OTA by a month or more. The latest flashable firmware is OPWS28.46-21-14 (Oct patch) and the latest OTA is OPWS28.46-21-16 (Nov patch).
ptn107 said:
The latest flashable firmware is OPWS28.46-21-14 (Oct patch) and the latest OTA is OPWS28.46-21-16 (Nov patch).
Click to expand...
Click to collapse
True. This is what I ended up doing, and it worked out ok:
- Took a nandroid backup in TWRP as a precaution (takes ~10-20 mins)
- Flashed full firmware from October w/o data wipe (took 2-3 mins)
- Booted normally. It took a few minutes for the "check for updates" to work, but eventually the November patch came in. It actually took ~20-30 minutes to apply.
- Rebooted to bootloader, then booted to TWRP img and pushed zips for TWRP and Magisk. (~5 mins)
- Booted normally, applied ad-blocker stuff
- Rebooted back to bootloader to flash the better boot logo
- Rebooted normally, all done.
hugehead83 said:
True. This is what I ended up doing, and it worked out ok:
- Took a nandroid backup in TWRP as a precaution (takes ~10-20 mins)
- Flashed full firmware from October w/o data wipe (took 2-3 mins)
- Booted normally. It took a few minutes for the "check for updates" to work, but eventually the November patch came in. It actually took ~20-30 minutes to apply.
- Rebooted to bootloader, then booted to TWRP img and pushed zips for TWRP and Magisk. (~5 mins)
- Booted normally, applied ad-blocker stuff
- Rebooted back to bootloader to flash the better boot logo
- Rebooted normally, all done.
Click to expand...
Click to collapse
Did this reset the modified flag in booloader?
vidra said:
Did this reset the modified flag in booloader?
Click to expand...
Click to collapse
I cannot recall or say for sure, but if you can tell me where specifically to look for that I'll check for you.
Related
I'm rooted and have S-off and have twrp for my recovery and the OTA downloaded to my phone and set it to update in a couple hours and im wondering if this is going to mess anything up if it updates? Im completely stock btw. If it is going to mess my root/s-off is there any way to stop it other than installing a rom?
tdc0z10 said:
I'm rooted and have S-off and have twrp for my recovery and the OTA downloaded to my phone and set it to update in a couple hours and im wondering if this is going to mess anything up if it updates? Im completely stock btw. If it is going to mess my root/s-off is there any way to stop it other than installing a rom?
Click to expand...
Click to collapse
It cannot flash on twrp. Did you mess with your rom other than rooting it?
dottat said:
It cannot flash on twrp. Did you mess with your rom other than rooting it?
Click to expand...
Click to collapse
No i havent flashed a rom or and mods since iv had it rooted/s-off. I delayed to update until 9:00Pm eastern, so it wont update since i have twrp?
tdc0z10 said:
No i havent flashed a rom or and mods since iv had it rooted/s-off. I delayed to update until 9:00Pm eastern, so it wont update since i have twrp?
Click to expand...
Click to collapse
So you will want to flash stock recovery back to the phone. Let it update. Then flash the newest twrp in fastboot. Then boot to Twrp and flash su.zip
dottat said:
So you will want to flash stock recovery back to the phone. Let it update. Then flash the newest twrp in fastboot. Then boot to Twrp and flash su.zip
Click to expand...
Click to collapse
can i just flash a rom to stop the update? if i cant flash stock recovery and the update goes through what is going to happen?
tdc0z10 said:
I'm rooted and have S-off and have twrp for my recovery and the OTA downloaded to my phone and set it to update in a couple hours and im wondering if this is going to mess anything up if it updates? Im completely stock btw. If it is going to mess my root/s-off is there any way to stop it other than installing a rom?
Click to expand...
Click to collapse
I just got done flashing the new OTA. I kept S-Off and bootloader unlock. In order to do this, you will need to flash stock recovery.
Flash stock recovery
Download 4.4.3 OTA in About > Software update > Check new
Install update
Reboot
Boot into bootlader and flash TWRP 2.8
Root
Just make sure you're S-Off and bootloader unlocked before you take the new OTA.
Andrew C said:
I just got done flashing the new OTA. I kept S-Off and bootloader unlock. In order to do this, you will need to flash stock recovery.
Flash stock recovery
Download 4.4.3 OTA in About > Software update > Check new
Install update
Reboot
Boot into bootlader and flash TWRP 2.8
Root
Click to expand...
Click to collapse
do you have a link for the stock recovery?
tdc0z10 said:
do you have a link for the stock recovery?
Click to expand...
Click to collapse
So just flashing a ROM wont do any good? im not at my computer to flash stock,but i do have a custom rom on my phone i can flash if that would stop the update from going through. if not then i guess im stuck with letting it go through? is my phone going to go into boot loop?
tdc0z10 said:
do you have a link for the stock recovery?
Click to expand...
Click to collapse
Stock recovery
---------- Post added at 05:13 PM ---------- Previous post was at 05:07 PM ----------
tdc0z10 said:
So just flashing a ROM wont do any good? im not at my computer to flash stock,but i do have a custom rom on my phone i can flash if that would stop the update from going through. if not then i guess im stuck with letting it go through? is my phone going to go into boot loop?
Click to expand...
Click to collapse
You won't be able to flash the OTA with a custom recovery. You have to have un-modified stock ROM and stock recovery.
Andrew C said:
Stock recovery
---------- Post added at 05:13 PM ---------- Previous post was at 05:07 PM ----------
You won't be able to flash the OTA with a custom recovery. You have to have un-modified stock ROM and stock recovery.[/QUOTE
I really dont want the OTA i just dont want it to do anything to my phone if it does update.
Click to expand...
Click to collapse
tdc0z10 said:
Andrew C said:
Stock recovery
---------- Post added at 05:13 PM ---------- Previous post was at 05:07 PM ----------
You won't be able to flash the OTA with a custom recovery. You have to have un-modified stock ROM and stock recovery.[/QUOTE
I really dont want the OTA i just dont want it to do anything to my phone if it does update.
Click to expand...
Click to collapse
Download m8vzw_OTA-Killer.zip | m8vzw_OTA-Killer.zip in this thread then. be sure to thank the OP of that thread.
Click to expand...
Click to collapse
I'm having trouble getting root back. I was attempting to flash supersu using TWRP, and it says it's successful but when I go to my apps list it's not there. Any suggestions on what I'm doing wrong? I'm S-Off still after I took the 4.4.3 OTA.
Andrew C said:
I just got done flashing the new OTA. I kept S-Off and bootloader unlock. In order to do this, you will need to flash stock recovery.
Flash stock recovery
Download 4.4.3 OTA in About > Software update > Check new
Install update
Reboot
Boot into bootlader and flash TWRP 2.8
Root
Just make sure you're S-Off and bootloader unlocked before you take the new OTA.
Click to expand...
Click to collapse
dmdobson88 said:
I'm having trouble getting root back. I was attempting to flash supersu using TWRP, and it says it's successful but when I go to my apps list it's not there. Any suggestions on what I'm doing wrong? I'm S-Off still after I took the 4.4.3 OTA.
Click to expand...
Click to collapse
Try downloading SuperSU from the market and installing from there.
Andrew C said:
Try downloading SuperSU from the market and installing from there.
Click to expand...
Click to collapse
Is it safe to update the binary the "normal" way, it recommends using TWRP.
Edit: excellent, that worked great. Got my root back, xposed framework updated, now I'm back to where I was but with the new 4.4.3 update.
dmdobson88 said:
Is it safe to update the binary the "normal" way, it recommends using TWRP.
Edit: excellent, that worked great. Got my root back, xposed framework updated, now I'm back to where I was but with the new 4.4.3 update.
Click to expand...
Click to collapse
I'm glad you got it working!
OTA hanging with stock recovery
I have reverted back to stock recovery (file downloaded from the link in this threat) but the OTA is still not working. After downloading, the update begins and I see the small icon of the phone with a green update symbol (two circular arrows). The green progress bar starts up, but then in a minute, it stops and the screen immediately jumps back to the stock recovery screen (phone icon with red triangle and exclamation point).
The process has run three times with the same result.
Can someone verify the md5sum of the stock_recovery.img file is d296a9a7289e10b2f04983e07409ee6c
Any ideas?
nachoport said:
I have reverted back to stock recovery (file downloaded from the link in this threat) but the OTA is still not working. After downloading, the update begins and I see the small icon of the phone with a green update symbol (two circular arrows). The green progress bar starts up, but then in a minute, it stops and the screen immediately jumps back to the stock recovery screen (phone icon with red triangle and exclamation point).
The process has run three times with the same result.
Can someone verify the md5sum of the stock_recovery.img file is d296a9a7289e10b2f04983e07409ee6c
Any ideas?
Click to expand...
Click to collapse
Not being on a completely unmodified stock HTC ROM is usually the case. Other than that this worked for me with no issues.
nachoport said:
I have reverted back to stock recovery (file downloaded from the link in this threat) but the OTA is still not working. After downloading, the update begins and I see the small icon of the phone with a green update symbol (two circular arrows). The green progress bar starts up, but then in a minute, it stops and the screen immediately jumps back to the stock recovery screen (phone icon with red triangle and exclamation point).
The process has run three times with the same result.
Can someone verify the md5sum of the stock_recovery.img file is d296a9a7289e10b2f04983e07409ee6c
Any ideas?
Click to expand...
Click to collapse
Have you modified any system files or froze any stock apps?
dottat said:
Have you modified any system files or froze any stock apps?
Click to expand...
Click to collapse
Crap, I can't even remember if I have messed with any of the stock apps. I've been into this device in so many ways in a short period of time. I'll have to dig deep into my memory... Thanks for the suggestion!
nachoport said:
Crap, I can't even remember if I have messed with any of the stock apps. I've been into this device in so many ways in a short period of time. I'll have to dig deep into my memory... Thanks for the suggestion!
Click to expand...
Click to collapse
Same I was trying to tell you, you're welcome
Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!
Fablus said:
Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!
Click to expand...
Click to collapse
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.
Mysticodex said:
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.
Click to expand...
Click to collapse
Maybe we need http://forum.xda-developers.com/google-nexus-5/general/stock-checker-zip-prepare-ota-t2927865?
Gosh, this used to be so easy all the time.
if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.
simms22 said:
if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.
Click to expand...
Click to collapse
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
-Do a factory reset (maybe you can keep data coming from STOCK 4.4.4 - maybe)
Click to expand...
Click to collapse
And I didn't want to count on a maybe.
I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.
Fablus said:
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
Click to expand...
Click to collapse
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
Mysticodex said:
I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.
Click to expand...
Click to collapse
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.
simms22 said:
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.
Click to expand...
Click to collapse
Trying to remove the root right now via SuperSU. I am hopeful it will work better afterwards.
Edit: SuperSU unrooted it, rebooted, did OTA again, error again. Is there no way to find out what this error is?
I saw a notification for a new system OTA and, without thinking, I downloaded and installed it even though I'm rooted.
So when the install starts, it just boots to TWRP. And every time I reboot back into system, it attempts to install the OTA again and just boots me back to TWRP.
Any help?
clankfu said:
I saw a notification for a new system OTA and, without thinking, I downloaded and installed it even though I'm rooted.
So when the install starts, it just boots to TWRP. And every time I reboot back into system, it attempts to install the OTA again and just boots me back to TWRP.
Any help?
Click to expand...
Click to collapse
A quick Google search would have yielded the answer almost immediately, just clear (wipe) caches and reboot.
acejavelin said:
A quick Google search would have yielded the answer almost immediately, just clear (wipe) caches and reboot.
Click to expand...
Click to collapse
thank you
so your phone survived the update? I would like to know if I can install it on my TWRP'd phones. Thanks.
bradmoss said:
so your phone survived the update? I would like to know if I can install it on my TWRP'd phones. Thanks.
Click to expand...
Click to collapse
It won't install, it will get stuck in recovery... Wiping cache deleted the update file and allows the phone to boot to its previous state.
where is the update file?
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
I wiped the cache but it still keeps in the loop...
bradmoss said:
where is the update file?
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
I wiped the cache but it still keeps in the loop...
Click to expand...
Click to collapse
All you did was try to update and wiping cache didn't fix it? Then there is more wrong. Backup in TWRP and do a factory reset (wipe data and caches)
In twrp go to file manager and find cache folder inside there is file update ( -----.zip) deleted then reboot
Hello is there a way to install the new update zip file from Motorola on stock Android from Motorola; 6.0.1
Agiofws said:
Hello is there a way to install the new update zip file from Motorola on stock Android from Motorola; 6.0.1
Click to expand...
Click to collapse
Are PURE stock and are certain you have the correct OTA zip file? Then sure... Start recovery, go to the menu and select Update via ADB, then on PC use 'adb sideload update.zip'
But to be honest, I don't think people capture the update zip or url on this device, so it probably isn't feasible.
---------- Post added at 07:03 AM ---------- Previous post was at 06:57 AM ----------
[/COLOR]
acejavelin said:
Are PURE stock and are certain you have the correct OTA zip file? Then sure... Start recovery, go to the menu and select Update via ADB, then on PC use 'adb sideload update.zip'
But to be honest, I don't think people capture the update zip or url on this device, so it probably isn't feasible.
Click to expand...
Click to collapse
My phone is rooted and unlocked and has TWRP. The update zip file file was automatically downloaded by Motorolas-androids OEM. System updates which I accepted. But as I can see from custom recovery it has a message about something like a pure signature to install even when I try manually. Thank you
When will the update madness with our phone ends???
Downloading right now...has anyone installed it yet?
liquor said:
When will the update madness with our phone ends???
Downloading right now...has anyone installed it yet?
Click to expand...
Click to collapse
When will it end? Probably August 2020 as Essential has promised 2 years of OS updates and 3 of security updates like the Pixel. Android Q would be the last OS update, followed by a year of security updates. And August because the phone launched late August. It might get support through September. All assuming nothing happens to Essential before then.
Installed the zip from Essential, haven't had much time to see if any differences that are noticeable.
OTA Zip
Fastboot zip
Anybody else getting "Couldn't Update" message after reverting back to May update from Q Beta?
goofball2k said:
Installed the zip from Essential, haven't had much time to see if any differences that are noticeable.
OTA Zip
Fastboot zip
Click to expand...
Click to collapse
Do you apply those OTA.zips like you would for any ROM? Or do you wipe dalvik, system, and data then flash the OTA.zip. I wanted to ask before I winded up in some crazy ****. I went ahead and backed up my phone.
jxcorex28 said:
Do you apply those OTA.zips like you would for any ROM? Or do you wipe dalvik, system, and data then flash the OTA.zip. I wanted to ask before I winded up in some crazy ****. I went ahead and backed up my phone.
Click to expand...
Click to collapse
I have TWRP installed. This is my way of doing the update.
Ensure the OTA zip and TWRP zip (optional, you can choose to install TWRP your own way) and Magisk zip (optional, only if you want to be rooted) are on the phone storage
Reboot to TWRP recovery
Select Install, then install the OTA zip file and then the TWRP recovery zip.
Reboot to system, or if you wish to have Magisk installed, flash the Magisk zip file.
knochnkopf said:
Anybody else getting "Couldn't Update" message after reverting back to May update from Q Beta?
Click to expand...
Click to collapse
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
cjscholten said:
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
Click to expand...
Click to collapse
I had no issues installing the June OTA through TWRP after going back to stock May ROM from the Q Beta.
I would recommend you to back up again and start with the stock fastboot June ROM.
Good luck.
Sent from my PH-1 using XDA Labs
cjscholten said:
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
Click to expand...
Click to collapse
Have you contacted Essential about the issue? I sent them a message yesterday with my device info and the process I used to flash back to the May 2019 update. Haven't heard from them yet. Seems like an odd problem. Only thing I can think of is maybe it has something to do with a scripting error in the batch file used to flash back to stock. I also went into my bootloader to verify that was locked so it should for all intents and purposes behave as a stock device. I have no root or custom recovery installed.
---------- Post added at 09:46 AM ---------- Previous post was at 09:22 AM ----------
Anybody know if flashing the OTA file from the Essential website vs the FastBoot file will completely wipe my device or just install over the top like a normal OTA? Only reason I ask is the OTA download is 330MB but the OTA file from the website is over 1GB. I really don't want to wipe my device AGAIN after just doing it less than a month ago.
Update: Flashed OTA zip from stock recovery without loss of data. They should really make that clearer on their website because it says flashing OTA "may" result in loss of data.
knochnkopf said:
Have you contacted Essential about the issue? I sent them a message yesterday with my device info and the process I used to flash back to the May 2019 update. Haven't heard from them yet. Seems like an odd problem. Only thing I can think of is maybe it has something to do with a scripting error in the batch file used to flash back to stock. I also went into my bootloader to verify that was locked so it should for all intents and purposes behave as a stock device. I have no root or custom recovery installed.
---------- Post added at 09:46 AM ---------- Previous post was at 09:22 AM ----------
Anybody know if flashing the OTA file from the Essential website vs the FastBoot file will completely wipe my device or just install over the top like a normal OTA? Only reason I ask is the OTA download is 330MB but the OTA file from the website is over 1GB. I really don't want to wipe my device AGAIN after just doing it less than a month ago.
Click to expand...
Click to collapse
I flashed the OTA via TWRP and retained all app's and the data without any problems.
Sent from my PH-1 using XDA Labs
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Jz5678910 said:
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Click to expand...
Click to collapse
There's a fastboot zip linked in the previous page. Not sure if it'll help but maybe.
Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy
marcdw said:
There's a fastboot zip linked in the previous page. Not sure if it'll help but maybe.
Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy
Click to expand...
Click to collapse
Actually I did try that, but I can't flash it due to fastboot not working unfortunately. It seems like one of my slots is corrupted.
Jz5678910 said:
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Click to expand...
Click to collapse
I don't use TWRP, but I was able to successfully flash Magisk-patched boot image after the latest update, so fastboot seems to be working just fine for me...
Im currently on 9.5.7 stock(Converted tmobile device to international), with a custom kernel,Root ,a couple of magisk modules and viper4AndroidFX.
I want to take the OTA that is available to 9.5.8 and future updates, so I was curious what the appropriate method is so that I dont lose anything or end up with a bootloop.
Download the OTA, the latest TWRP and Magisk. Reboot to TWRP then flash OTA > TWRP > Magisk. After that reboot and you'll be updated.
whatthekj said:
Download the OTA, the latest TWRP and Magisk. Reboot to TWRP then flash OTA > TWRP > Magisk. After that reboot and you'll be updated.
Click to expand...
Click to collapse
Sweet thanks! How should I download the OTA? Just wanted to make sure I don't accidentally take the update without realizing it.
EDIT: Does it matter if I use the "Full Update" from the "Oxygen Updater" app in the play store?
HaiKaiDo said:
Sweet thanks! How should I download the OTA? Just wanted to make sure I don't accidentally take the update without realizing it.
Click to expand...
Click to collapse
Use this thread https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585 to get the OTA files. Assuming you converted to GM1917 you'll want to download the GM21AA Signed flashable zips.
I've only used the updater app once because those files are available faster than what appears on XDA. I usually like to wait until the Fastboot files become available on XDA in case I have to restore because of some bootloop, bug, etc. But I would just follow the directions on the app. I think it explain which update you need for a rooted device.
Good instruction on how to update a rooted phone, are on the TWRP thread (top post): https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
As well as here: https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
HaiKaiDo said:
Does it matter if I use the "Full Update" from the "Oxygen Updater" app in the play store?
Click to expand...
Click to collapse
Using the "Oxygen Updater" app should be okay, as long as you follow the instruction in the second link I gave above.
As far as the "full update" you must flash this (versus the partial patch) since you are rooted, or you will bootloop (at least, that was how it worked for past OnePlus devices). The updater should detect you have TWRP/root and download the full update anyway.
redpoint73 said:
Good instruction on how to update a rooted phone, are on the TWRP thread (top post): https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
As well as here: https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
Using the "Oxygen Updater" app should be okay, as long as you follow the instruction in the second link I gave above.
As far as the "full update" you must flash this (versus the partial patch) since you are rooted, or you will bootloop (at least, that was how it worked for past OnePlus devices). The updater should detect you have TWRP/root and download the full update anyway.
Click to expand...
Click to collapse
Will this take me back to the stock kernel? I kind of want it to so that I can flash another and try it out lol.
Id like to know too. I want to try out EXkernel but be able to flash back to stock. so flashing the full 2gb rom will not wipe any data on my phone?
HaiKaiDo said:
Will this take me back to the stock kernel? I kind of want it to so that I can flash another and try it out lol.
Click to expand...
Click to collapse
Yes, it will re-install the stock kernel. It's a full stock image.
Make a backup of the stock boot.img in TWRP, before flashing a custom kernel, in the event you want to revert later (without flashing the whole update image).
---------- Post added at 09:18 AM ---------- Previous post was at 09:12 AM ----------
equlizer said:
Id like to know too. I want to try out EXkernel but be able to flash back to stock. so flashing the full 2gb rom will not wipe any data on my phone?
Click to expand...
Click to collapse
Yes, it should retain your data. I just updated to 9.5.8 a few days ago, and it kept my data intact (by the process of updating in settings, don't reboot, in Magisk Manager install TWRP installer in inactive slot, etc.).
But what I always say when attempting a "dirty flash" (flashing the ROM, but retaining data) is: hope for the best, prepare for the worst. Backup anything that is important to you before any big update, just in case. What should happen, and what actually happens, are not always the same thing!