Related
Here is the both of the stock update packagea extracted from the phone I didn't do a thing to it.... In order to get to the official Froyo, you must be on stock DL17... From there, you should flash the EB01, and then the EC09 packages, respectively
Recovery Package [EB01]: http://www.mediafire.com/?nx6s6vt0l1t37cf
Recovery Package [EC09]:http://www.mediafire.com/?rvcd2l7ypux0ey0
Have fun
and if you are ever interested in donating to me, the link is to the bottom and left of the screen
Haha great
Sent from my SCH-I400 using xda premium
Whaaaaaat! Nom nom nom
Sent from my SCH-I400 using Tapatalk
Any chance you could pull the EB01 update package?
If someone can tell me how its done, ill revert and pull it.
Sent from my SCH-I400 using Tapatalk
What is EB01? :/
Sent from my SCH-I400 using Tapatalk
abby_nitewolf said:
What is EB01? :/
Sent from my SCH-I400 using Tapatalk
Click to expand...
Click to collapse
Did you notice that your phone did asmall update the big 1? That was e b 01
Sent from my SCH-I400 using Tapatalk
I believe that it gets downloaded to the /cache partition, and it is usually some random filename. I'm pretty sure if you get logcat while it's downloading, it'll tell you at least the URL it's pulling the file from, and possibly even the save location. Maybe Trailblazer will be able to provide some more detailed info though.
Txwolf1980 said:
Did you notice that your phone did asmall update the big 1? That was e b 01
Sent from my SCH-I400 using Tapatalk
Click to expand...
Click to collapse
I was wondering what that was, wow
Sent from my SCH-I400 using Tapatalk
imnuts said:
I believe that it gets downloaded to the /cache partition, and it is usually some random filename. I'm pretty sure if you get logcat while it's downloading, it'll tell you at least the URL it's pulling the file from, and possibly even the save location. Maybe Trailblazer will be able to provide some more detailed info though.
Click to expand...
Click to collapse
Ok. I assume verizon will push the update to the same phone, twice. I know it isn't an issue on GSM, but I'm not sure about CDMA, with the way it's set up. If they do, I'll revert tomorrow afternoon and see if I can find it to pull it.
Trailblazer, if you read this, before then, Something a little more comprehensive would be appreciated.
Txwolf1980 said:
Ok. I assume verizon will push the update to the same phone, twice. I know it isn't an issue on GSM, but I'm not sure about CDMA, with the way it's set up. If they do, I'll revert tomorrow afternoon and see if I can find it to pull it.
Trailblazer, if you read this, before then, Something a little more comprehensive would be appreciated.
Click to expand...
Click to collapse
You shouldn't have any problems updating to EB01 again.
I will get it for you when I get home imnuts great to here from you!
Sent from my SCH-I400 using xda premium
for some reason it wouldnt let me pull it, it just stops throwing data onto the screen and never issues the command
trailblazer101 said:
I will get it for you when I get home imnuts great to here from you!
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
Did you get home yet
oh my gosh, I am so sorry, haha... I will have it up and ready within the next hour, haha
EDIT: Officially Updated the OP for you Imnuts Can't wait for the source to drop, so we can hopefully get some fancy stuff for this phone! Thanks in advance!
Thanks Now my Continuum is on official Froyo
imnuts said:
Thanks Now my Continuum is on official Froyo
Click to expand...
Click to collapse
Is your Continuum not activated or something?
Sent from my SCH-I400 using XDA App
samuelhadams said:
Is your Continuum not activated or something?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
Nope, and if I did activate it, I'd need to go get a new SIM card for my phone.
I have some n00b questions that I would really appreciate some help on...
trailblazer101 said:
Here is the both of the stock update packagea extracted from the phone I didn't do a thing to it.... In order to get to the official Froyo, you must be on stock DL17... From there, you should flash the EB01, and then the EC09 packages, respectively
Recovery Package [EB01]: http://www.mediafire.com/?nx6s6vt0l1t37cf
Recovery Package [EC09]:http://www.mediafire.com/?rvcd2l7ypux0ey0
Have fun
Click to expand...
Click to collapse
Hi,
I have some n00b questions that I would really appreciate some help on...
1. Are these files also known as the "radio" and "kernel."?
EB01 = radio?
EC09 - kernel?
2. Do I have to rename them both to "update.zip" before I place them on my sdcard?
3. When I flash them from CWM recovery, do I select "install update.zip" or "install zip from sd card"?
4. Would it be a better idea for me to use an odin package (EC09 odexed)?
5. I already flashed to a build called "EC07_clean." Do I need to go back to a stock DL17 before I flash EB01+EC09, or can I just proceed from EC07?
Thank you to anyone who takes time to help me on these. I appreciate it!
firstand said:
Hi,
I have some n00b questions that I would really appreciate some help on...
1. Are these files also known as the "radio" and "kernel."?
EB01 = radio?
EC09 - kernel?
2. Do I have to rename them both to "update.zip" before I place them on my sdcard?
3. When I flash them from CWM recovery, do I select "install update.zip" or "install zip from sd card"?
4. Would it be a better idea for me to use an odin package (EC09 odexed)?
5. I already flashed to a build called "EC07_clean." Do I need to go back to a stock DL17 before I flash EB01+EC09, or can I just proceed from EC07?
Thank you to anyone who takes time to help me on these. I appreciate it!
Click to expand...
Click to collapse
1. Not really. I'm not the person to explain that, I'm sure Tx or one of the other, more experienced regulars could explain it better. EB01 only serves to fix OTA issues and prepare the phone for EC09. As EC09 is being flashed, the radio and kernel are patched/updated from DL17.
2. No. Leave them named how they are. Just be sure you know which one is which so you can flash them in the correct order. EB01, then EC09.
3. Choose "Install zip from sd card" and then navigate to where they are. Putting them on the root of the sd card makes it easier to find them.
4. You don't have to. I honestly find CWM to be easier as no PC required. Once again, one of the other regulars may have a better answer here.
5. Going back to stock DL17 and then flashing EB01/EC09 is the only way, I think. Going from EC07 to EC09 probably won't work.
I started doing the Google framework force stop and clear cache today while on wifi and was prompted after 5 or 6 tries. It downloaded, verified download, rebooted and TRIED to install. About 15% through, it said untrusted zip and cwm screen popped up top and asked 'install untrusted zip?' Of course I hit yes.. why isn't it trusted? Its straight from the carrier. Anyway it immediately said installation aborted. I repeated this process again and got the same results. Please someone help. Now that JB is finally here my phone won't take it???
Sent from my Galaxy Nexus using xda app-developers app
Your phone is rooted? If yes you can't install OTA updates
I'm rooted yes. So what do I do? Unroot?
Sent from my Galaxy Nexus using xda app-developers app
htc_woe_is_me said:
I started doing the Google framework force stop and clear cache today while on wifi and was prompted after 5 or 6 tries. It downloaded, verified download, rebooted and TRIED to install. About 15% through, it said untrusted zip and cwm screen popped up top and asked 'install untrusted zip?' Of course I hit yes.. why isn't it trusted? Its straight from the carrier. Anyway it immediately said installation aborted. I repeated this process again and got the same results. Please someone help. Now that JB is finally here my phone won't take it???
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
polimeno said:
Your phone is rooted? If yes you can't install OTA updates
Click to expand...
Click to collapse
Not true. Root makes no difference.
efrant said:
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
Not true. Root makes no difference.
Click to expand...
Click to collapse
So either way I will lose all my settings, home screens and what not?
I used Galaxy Nexus Toolkit to do all of my rooting, installing CWM and all-- is there a way to accomplish what I need to on there?
efrant said:
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
Not true. Root makes no difference.
Click to expand...
Click to collapse
It's exact. But root can only be done if you have bootloader unlocked, and with unlocked bootloader can not install OTA updates
htc_woe_is_me said:
So either way I will lose all my settings, home screens and what not?
Click to expand...
Click to collapse
No, updating using an OTA update file will NOT make you lose anything.
htc_woe_is_me said:
I used Galaxy Nexus Toolkit to do all of my rooting, installing CWM and all-- is there a way to accomplish what I need to on there?
Click to expand...
Click to collapse
I can't help you out with the toolkit, but have a look at my signature for some useful links on doing things without a toolkit.
efrant said:
No, updating using an OTA update file will NOT make you lose anything.
I can't help you out with the toolkit, but have a look at my signature for some useful links on doing things without a toolkit.
Click to expand...
Click to collapse
OK, so the best thing would be to flash the stock recovery? Sorry for all the questions, and I really appreciate all your help. I swear I used to know how to do this crap on my Dinc, but it's been years since I did all that.
htc_woe_is_me said:
OK, so the best thing would be to flash the stock recovery? Sorry for all the questions, and I really appreciate all your help. I swear I used to know how to do this crap on my Dinc, but it's been years since I did all that.
Click to expand...
Click to collapse
Go to the Google page with all the images and download the mysid IMM76K image, extract the recovery.img from within, and flash it using fastboot: fastboot flash recovery recovery.img
efrant said:
Go to the Google page with all the images and download the mysid IMM76K image, extract the recovery.img from within, and flash it using fastboot: fastboot flash recovery recovery.img
Click to expand...
Click to collapse
OK, I'm trying this now... I downloaded the images from Google.. extracted its contents... found the recovery image file. Do I need to put that file into a zip file?
htc_woe_is_me said:
OK, I'm trying this now... I downloaded the images from Google.. extracted its contents... found the recovery image file. Do I need to put that file into a zip file?
Click to expand...
Click to collapse
Gnex Toolkit wasn't working because of some missing file... re-installed it and flashed the stock recovery via Gnex Toolkit (I think). Is there a way to check which recovery is running? Anyway, if it is indeed stock, I just got prompted again for the OTA JB update.. it's installing now.... fingers crossed!!!
..OK so now it rebooted... started installing, got about halfway through.. paused, then it went to the stock recovery screen and stayed with a red triangle around an exclamation point! What is happening here?!
I have now re-locked the bootloader and received the prompt for OTA again....
Still won't work for me. I've tried even flashing the stock image and it won't install at all. Actually nothing is installing.
I've never done anything to the phone besides unlocking the BL and rooting and switching to CWM. It seems to have something to do with the SD mount.. nut then again I have no idea.
Where's all the Android gurus at?
Sent from my Galaxy Nexus using xda app-developers app
htc_woe_is_me said:
Still won't work for me. I've tried even flashing the stock image and it won't install at all. Actually nothing is installing.
I've never done anything to the phone besides unlocking the BL and rooting and switching to CWM. It seems to have something to do with the SD mount.. nut then again I have no idea.
Where's all the Android gurus at?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Follow the instructions in the "update" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Guys i am having this EXACT problem, except on a S4 (I337M to be exact)
Here is my thread with the details
http://forums.androidcentral.com/as...t-update-ota-failure-using-triangle-away.html
But basically, im just wondering how i can get stock recovery back and get this ota to work!!!
Thanks!
Using Root explorer (or another filesystem app with write access) go to /system/app/
search "dm"
add ".bak" to the following files (filename.apk becomes filename.apk.bak). you don't need to add the .bak to the odex files. that's just extra work
DMcommandService.apk
HtcCdmaMccProvider.apk
HtcOMADM_SettingsPlugin_VZW.apk
HtcOMADM_VZW.apk
This will make it so the apps are not functional, but you didn't (re)move them, so it can easily be undone, should you chose to. Once you do this you won't see "software update" option in the system settings and it won't be able to auto-check either. you may have to reboot to see the changes.
I've been running like this for a few days with no instability. everything is working 100%. I probably disabled more apps than necessary to prevent the OTA, but I wanted to be sure and, like I said, there's no negative results so far.
If your phone has already downloaded the OTA but hasn't installed it, you can find the file in /cache/fumo and remove it. If the notification doesn't disappear on reboot, accept the update, let it fail (since you deleted the file), and the notification to install should go away
EDIT: andybones has been kind enough to upload a flashable ZIP that will remove the OTA apks as well as the firmware file, in case your phone already downloaded, but did not yet install, the update. http://forum.xda-developers.com/showpost.php?p=46380185&postcount=13
The downloaded OTAPkg.zip was put in the "downloads" folder.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
kdj67f said:
The downloaded OTAPkg.zip was put in the "downloads" folder.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No. /cache/fumo in the root directory of your phone. (Root browser mode required). If you have one in downloads its because you downloaded it from your browser.
Op-
What do you have against the ota ?
http://forum.xda-developers.com/showthread.php?t=2469057
Sent from my Nexus 7 using Tapatalk 4
I didn't download it from a browser, but I did let the update failure out on installation so it would stop nagging me.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
kdj67f said:
I didn't download it from a browser, but I did let the update failure out on installation so it would stop nagging me.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It would not have downloaded to "downloads". Trust me on that. Check your /cache/fumo directory.
Sent from my Nexus 7 using Tapatalk 4
I just did. Empty folder. Using ES file explorer. I don't think I moved files for any reason, but I guess I could have accidentally moved that. I will take your word for it though.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
kdj67f said:
I just did. Empty folder. Using ES file explorer. I don't think I moved files for any reason, but I guess I could have accidentally moved that. I will take your word for it though.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep....if that file was present you'd be getting the nag. That's where they download to so anyone looking to follow op can delete theirs there.
Sent from my Nexus 7 using Tapatalk 4
dottat said:
No. /cache/fumo in the root directory of your phone. (Root browser mode required). If you have one in downloads its because you downloaded it from your browser.
Op-
What do you have against the ota ?
http://forum.xda-developers.com/showthread.php?t=2469057
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
that file is made to work while retaining S-Off. it's sideloaded, so technically not an "OTA" update. OTAs have a habit of losing people's root, and generally being a nuisance. I don't have anything against updating software. just trying to help people stay one step ahead of Verizon and HTC ruining our fun.
and yeah, it DEFINITELY didn't download to downloads. lol
dottat said:
Yep....if that file was present you'd be getting the nag. That's where they download to so anyone looking to follow op can delete theirs there.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Using ES Root explorer and a few others, there is no fumo folder in my cache folder
I keep getting the nag, and I have looked everywhere for a file called OTAPkg.zip where else would it be hiding??
TidusWulf said:
that file is made to work while retaining S-Off. it's sideloaded, so technically not an "OTA" update. OTAs have a habit of losing people's root, and generally being a nuisance. I don't have anything against updating software. just trying to help people stay one step ahead of Verizon and HTC ruining our fun.
and yeah, it DEFINITELY didn't download to downloads. lol
Click to expand...
Click to collapse
Read the thread I posted bro. Its straight up ota firmware and all . S-off is unaffected.
Sent from my Nexus 7 using Tapatalk 4
---------- Post added at 01:02 AM ---------- Previous post was at 01:02 AM ----------
Anthrax79 said:
Using ES Root explorer and a few others, there is no fumo folder in my cache folder
I keep getting the nag, and I have looked everywhere for a file called OTAPkg.zip where else would it be hiding??
Click to expand...
Click to collapse
Did you mount it as root explorer ? Otherwise you won't see the folder
Sent from my Nexus 7 using Tapatalk 4
I misunderstood when I read that topic.
and while the current .8 to .10 may be of no consequence, we can't say for sure when the NEXT update comes out, what will happen, so this topic is just for preventative measures.
TidusWulf said:
I misunderstood when I read that topic.
and while the current .8 to .10 may be of no consequence, we can't say for sure when the NEXT update comes out, what will happen, so this topic is just for preventative measures.
Click to expand...
Click to collapse
We agree on that point. Note the location I gave you for downloaded updates. Your file explorer must be in root mode or you won't see any files/folders in /cache. (There should be a couple)
Sent from my Nexus 7 using Tapatalk 4
Just flash this http://d-h.st/tfE and it will remove the OTA if it already was downloaded, along with the files needed to be removed.
And while I'm here it's always good to remind, as maybe someone doesn't know.
NEVER take an OTA, if you are rooted, and want to STAY rooted.
It very well could take away S-OFF.
Wait until it's confirmed or, just wait for a ROM to be made based off of it and flash the firmware and it's the exact same and you keep your S-OFF.
So, I deleted the downloaded update file and let the update process run again, and ES file explorer (actually ES download manager that was part of file explorer) was copying the update to the download folder. So, you guys were right, it was something I was doing wrong. Thanks for setting me straight!
So, I let the update download and run, then it fails out (knowing I have CWM recovery installed) and the nag goes away without updating my phone. I accidentally let it update when I was at work and didn't notice until it rebooted. I don't recommend anybody let it run and fail, but that is what happened to me.
andybones said:
Just flash this http://d-h.st/tfE and it will remove the OTA if it already was downloaded, along with the files needed to be removed.
And while I'm here it's always good to remind, as maybe someone doesn't know.
NEVER take an OTA, if you are rooted, and want to STAY rooted.
It very well could take away S-OFF.
Wait until it's confirmed or, just wait for a ROM to be made based off of it and flash the firmware and it's the exact same and you keep your S-OFF.
Click to expand...
Click to collapse
Has anyone tried to accept the OTA after being stock rooted? I know there isn't a whole lot of changes in the update...but wondering if flashing a new recovery to accept is even necessary with such a minor update...
brymaster5000 said:
Has anyone tried to accept the OTA after being stock rooted? I know there isn't a whole lot of changes in the update...but wondering if flashing a new recovery to accept is even necessary with such a minor update...
Click to expand...
Click to collapse
I've read if you have S-OFF you CAN accept the OTA.
brymaster5000 said:
Has anyone tried to accept the OTA after being stock rooted? I know there isn't a whole lot of changes in the update...but wondering if flashing a new recovery to accept is even necessary with such a minor update...
Click to expand...
Click to collapse
I posted a link to my thread showing how I did it earlier in the thread...
Sent from my Nexus 7 using Tapatalk 4
TidusWulf said:
Using Root explorer (or another filesystem app with write access) go to /system/app/
search "dm"
add ".bak" to the following files (filename.apk becomes filename.apk.bak). you don't need to add the .bak to the odex files. that's just extra work
DMcommandService.apk
HtcCdmaMccProvider.apk
HtcOMADM_SettingsPlugin_VZW.apk
HtcOMADM_VZW.apk
This will make it so the apps are not functional, but you didn't (re)move them, so it can easily be undone, should you chose to. Once you do this you won't see "software update" option in the system settings and it won't be able to auto-check either. you may have to reboot to see the changes.
I've been running like this for a few days with no instability. everything is working 100%. I probably disabled more apps than necessary to prevent the OTA, but I wanted to be sure and, like I said, there's no negative results so far.
If your phone has already downloaded the OTA but hasn't installed it, you can find the file in /cache/fumo and remove it. If the notification doesn't disappear on reboot, accept the update, let it fail (since you deleted the file), and the notification to install should go away
Click to expand...
Click to collapse
Thanks for this, worked great!
TidusWulf said:
Using Root explorer (or another filesystem app with write access) go to /system/app/
search "dm"
add ".bak" to the following files (filename.apk becomes filename.apk.bak). you don't need to add the .bak to the odex files. that's just extra work
DMcommandService.apk
HtcCdmaMccProvider.apk
HtcOMADM_SettingsPlugin_VZW.apk
HtcOMADM_VZW.apk
This will make it so the apps are not functional, but you didn't (re)move them, so it can easily be undone, should you chose to. Once you do this you won't see "software update" option in the system settings and it won't be able to auto-check either. you may have to reboot to see the changes.
I've been running like this for a few days with no instability. everything is working 100%. I probably disabled more apps than necessary
Click to expand...
Click to collapse
I purchased a factory refurbished Verizon HTC One on eBay with the intention of flashing to PagePlus. Before I had it flashed I rooted it and renamed these files. I wanted to prevent the OTA updates because I did not want them to break the flash.
I found that I was unable to get the phone flashed because we could never get the DM Command Service window to appear. I eventually realized that my renaming these files (undoubtedly the first one) caused the problem.
I returned the files to their original names and was able to get the phone flashed.
I have renamed the last three files. I'll post here if this is effective in stopping the updates. Verizon is supposed to push out Android 4.4 shortly.
cdavidhess said:
I purchased a factory refurbished Verizon HTC One on eBay with the intention of flashing to PagePlus. Before I had it flashed I rooted it and renamed these files. I wanted to prevent the OTA updates because I did not want them to break the flash.
I found that I was unable to get the phone flashed because we could never get the DM Command Service window to appear. I eventually realized that my renaming these files (undoubtedly the first one) caused the problem.
I returned the files to their original names and was able to get the phone flashed.
I have renamed the last three files. I'll post here if this is effective in stopping the updates. Verizon is supposed to push out Android 4.4 shortly.
Click to expand...
Click to collapse
Great thread!
This is what I do when I flash New Roma as well, but to be more or less safe this is what I do.
I let the Rom fully boot up
Let phone get passed the hands free activation*a must*
With es file explorer or in recovery then change file names, for me I don't change the vdmclient one only till recently.
In recovery you just system go to system/app and change the names.
Hi I just Rooted my T-mobile lg g3.
Using this method http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
I'm Pretty Much a Complete newb so that said.
From I understand I need to install a cusom recovery so I can flash the stock Rom in case something goes wrong.
Also do I need to turn off ota updates?
Could someone point to a custom recovery, and stock rom. (with detailed instructions)
If it helps the adroid version is 4.4.2, thats what came on it when I got it. which was Monday.
Any Help for a poor nooby would be much appreciated! Many Thanks.
Download TWRP Manager from the Play Store to download and install the latest TWRP version.
Sent from my LG-D851 using Tapatalk
bfederspill said:
Download TWRP Manager from the Play Store to download and install the latest TWRP version.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
well I followed he prompts and installed busybox and patced to write to external sd, but when i click to select my device name it just goes back to the main page of the app.
I think it says Twrp has stopped. very quickly then takes me back to home page of the app.
After checking I was getting the same error. I really don't know what is up with that program for it to do that. I mainly use it to reboot into recovery. You could find the latest TWRP on XDA, save it to your SD card and use a program called Flashify from the Play Store and flash it that way.
Sent from my LG-D851 using Tapatalk
bfederspill said:
After checking I was getting the same error. I really don't know what is up with that program for it to do that. I mainly use it to reboot into recovery. You could find the latest TWRP on XDA, save it to your SD card and use a program called Flashify from the Play Store and flash it that way.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Yeah I got it figured out. Thanks for the help got my backup and started messin around with 3g tweaksbox. Phone is pretty sick now. Do you have any idea how change the system font? Tried downloading some from the playstore, but no luck. it doesn't show in the menu, and I don't see any option to add them.
I'll try to check back asap. Work makes it difficult.
So I have an unlocked, rooted HTC 10 with Xposed and TWRP coming from a OnePlus One. With the One all you do is flash away, but it seems different for other brands. So my question is, how do I apply update 1.53 in my current setup? I've read about using the RUU, but I'm not too keen on wiping my data. Also not sure how to use the zip files provided in that thread.
Sent from my HTC 10 using XDA-Developers mobile app
DIngusxp said:
So I have an unlocked, rooted HTC 10 with Xposed and TWRP coming from a OnePlus One. With the One all you do is flash away, but it seems different for other brands. So my question is, how do I apply update 1.53 in my current setup? I've read about using the RUU, but I'm not too keen on wiping my data. Also not sure how to use the zip files provided in that thread.
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm not positive how xposed will affect your ability to ota as I don't use it. But with just root and twrp, you should not have to wipe data but you will have to restore stock system image and firmware, so after the update you will need to redo all of your xposed mods and any root apps that modify system.
I wrote a guide about how to ota if you get an error with it, but the steps should apply to your current state as well.
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
If you run into trouble ask in that thread.