Related
So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse
Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse
Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse
Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.
So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?
Hi, I'm a long time Android enthusiast, owning, rooting and modding a Nexus 4, LG Optimus V, and Honor 5X. However, the HTC 10 is really confusing to me because of its new Nougat update.
I currently have a US Unlocked HTC 10 with a freshly unlocked bootloader, S-On. I was wondering if I should root it with TWRP Recovery, and install an RUU to keep root, or is that not how it works? I'm jut very confused as to how to keep root going into the Nougat update. Thanks
Thats not how it works.
When you use an RUU, it will not keep root. It will wipe your device full factory reset.
I dont really recommend the 7.0 update just yet as there is no TWRP for it.
Since you are S-ON, you wont be able to downgrade back to 6.0.
You CAN root 7.0 using Magisk if you need to.
http://forum.xda-developers.com/htc-10/development/root-magisk-autoroot-magisk-phhs-t3507505
If Still you want to upgrade, then you should S-OFF FIRST.. so you can downgrade if you want. You can NOT S-OFF from 7.0 yet, and you can not downgrade without S-OFF, so it's a one way ticket if you don't S-OFF first. (for now.)
You cant really Keep root (AKAIK), you'll have to re-root after each update. Here is what I usually do (excluding the 7.0 update for now because there is no TWRP Yet)
1) Flash TWRP.
2) Backup System Image / Boot (Clean - before root).
3) Flash the latest SuperSU to root.
4) When there is a new OTA update, boot to TWRP, restore the Last Clean System Image / Boot images.
5) Flash Latest Stock Recovery.img. (You'll need to find it, or extract it from an OTA Zip)
6) Boot to Rom, Install OTA.
7) Repeat Steps 1-3
Check these links
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
x51 said:
If Still you want to upgrade, then you should S-OFF FIRST.. so you can downgrade if you want. You cant S-OFF from 7.0 yet, and you cant downgrade, so it's a one way ticket for now.
Click to expand...
Click to collapse
Is Sunshine still the only way to S-OFF? If so, is it still a paid option?
elguy said:
Is Sunshine still the only way to S-OFF? If so, is it still a paid option?
Click to expand...
Click to collapse
As far as I know, Yes and Yes.
I was getting along fine without it, until I upgraded to 7.0 and wanted to go back... now I'm stuck.
x51 said:
Thats not how it works.
When you use an RUU, it will not keep root. It will wipe your device full factory reset.
I dont really recommend the 7.0 update just yet as there is no TWRP for it.
Since you are S-ON, you wont be able to downgrade back to 6.0.
You CAN root 7.0 using Magisk if you need to.
http://forum.xda-developers.com/htc-10/development/root-magisk-autoroot-magisk-phhs-t3507505
If Still you want to upgrade, then you should S-OFF FIRST.. so you can downgrade if you want. You can NOT S-OFF from 7.0 yet, and you can not downgrade without S-OFF, so it's a one way ticket if you don't S-OFF first. (for now.)
You cant really Keep root (AKAIK), you'll have to re-root after each update. Here is what I usually do (excluding the 7.0 update for now because there is no TWRP Yet)
1) Flash TWRP.
2) Backup System Image / Boot (Clean - before root).
3) Flash the latest SuperSU to root.
4) When there is a new OTA update, boot to TWRP, restore the Last Clean System Image / Boot images.
5) Flash Latest Stock Recovery.img. (You'll need to find it, or extract it from an OTA Zip)
6) Boot to Rom, Install OTA.
7) Repeat Steps 1-3
Check these links
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Click to expand...
Click to collapse
I see. Seems as it it'd be better to wait for a confirmed root / twrp method for 7.0 first for a guranated method. Thank you, some of these terms are new to me....
x51 said:
As far as I know, Yes and Yes.
I was getting along fine without it, until I upgraded to 7.0 and wanted to go back... now I'm stuck.
Click to expand...
Click to collapse
Unlock bootloader, custom rom to 6.0. Then sunshine or contact me to s-off
ArtOfSnaila said:
I see. Seems as it it'd be better to wait for a confirmed root / twrp method for 7.0 first for a guranated method. Thank you, some of these terms are new to me....
Click to expand...
Click to collapse
I think there are many of us that are in this situation, I will be waiting patiently for a fix to the TWRP issue with 7.0 and then will enjoy the ride...
Sent from my HTC 10 using Tapatalk
Yep, same here. The best option is to wait for Captain Throwback to get TWRP spruced up for Nougat. Flash Nougat then flash TWRP.
stifilz said:
Unlock bootloader, custom rom to 6.0. Then sunshine or contact me to s-off
Click to expand...
Click to collapse
How would I custom Rom to 6.0 without TWRP?
x51 said:
How would I custom Rom to 6.0 without TWRP?
Click to expand...
Click to collapse
Oh yeah, good point lol. Would need to flash an older boot combination I guess. Way to dangerous for most, this is why I s-off first and mess around after. I imagine TWRP won't be long anyway
Hey guys!
First off: sorry if I simply cant search but I cant find an "oficial" guide on this anywhere.
I would like to go back to the latest OxygenOS version pre-nougat (3.8.2 from the top of my head) but I dont expect it to be just a simple flash from TWRP and I was wondering how I would go about downgrading.
Im rooted (with magisk) and I have the latest version of TWRP. Preferably, I'd like to go about it without data loss but if thats impossible so be it.
I'm downgrading because I just love my Xposed too much to drop it.
Thanks for any help you can provide!
Solution6996 said:
Hey guys!
First off: sorry if I simply cant search but I cant find an "oficial" guide on this anywhere.
I would like to go back to the latest OxygenOS version pre-nougat (3.8.2 from the top of my head) but I dont expect it to be just a simple flash from TWRP and I was wondering how I would go about downgrading.
Im rooted (with magisk) and I have the latest version of TWRP. Preferably, I'd like to go about it without data loss but if thats impossible so be it.
I'm downgrading because I just love my Xposed too much to drop it.
Thanks for any help you can provide!
Click to expand...
Click to collapse
I flashed it via recovery and I had problems, probably because the partitions. I recommend you to make a backup and flash it via QPST, this is what I did and It works perfect.
Flash 3.2.8 and after that do a factory reset. It will not work without factory reset.
Puddi_Puddin said:
Flash 3.2.8 and after that do a factory reset. It will not work without factory reset.
Click to expand...
Click to collapse
Is it actually that simple? Have you tried it and it didn't cause any issues?
arceoxis said:
I flashed it via recovery and I had problems, probably because the partitions. I recommend you to make a backup and flash it via QPST, this is what I did and It works perfect.
Click to expand...
Click to collapse
What exactly is QPST?
Solution6996 said:
What exactly is QPST?
Is it actually that simple? Have you tried it and it didn't cause any issues?
Click to expand...
Click to collapse
Well since you where on 4.0 you prob where on F2fs aswell, 3.2.8 doesn't support F2fs that's why you do a factory reset, downgrading and upgrading is no problem as long as you do a factory reset and most importantly install the full rom.
Solution6996 said:
Hey guys!
First off: sorry if I simply cant search but I cant find an "oficial" guide on this anywhere.
I would like to go back to the latest OxygenOS version pre-nougat (3.8.2 from the top of my head) but I dont expect it to be just a simple flash from TWRP and I was wondering how I would go about downgrading.
Im rooted (with magisk) and I have the latest version of TWRP. Preferably, I'd like to go about it without data loss but if thats impossible so be it.
I'm downgrading because I just love my Xposed too much to drop it.
Thanks for any help you can provide!
Click to expand...
Click to collapse
What I did (with an unlocked bootloader):
Titanium backup all apps and call logs/texts/wifi via XML.
Reformat data to ext4 via TWRP.
Flash TWRP 3.0.4-1 as image.
Flash ob7 within TWRP.
Reflashed TWRP (why not?)
Booted and factory reset.
Flash SuperSU.
Restored user apps and texts calls etc via tibu.
Worked flawlessly.
Just flash OxygenOS marshmallow version ( you can download from oneplus official website, support section), then do a factory reset. Hope its helpful to you.
losekay said:
Just flash OxygenOS marshmallow version ( you can download from oneplus official website, support section), then do a factory reset. Hope its helpful to you.
Click to expand...
Click to collapse
+1 on this. I downgraded from 4.0.3 to 3.2.8 with a simple ADB sideload. Download the ROM from the support site, then just adb sideload <name of zip>.zip. Done.
I was back on Marshmallow and had no issues. Then again, I wasn't running TWRP, everything was Stock.
@WhaleTrain when you said you sideloaded the rom and that everything was stock, was your bootloader locked or does it need to be unlocked to do it? can I simply boot into stock recovery and sideload?
Thanks
Sorry if this has been asked before (I couldn't find anything) but is it possible to upgrade a rooted 3aXL to Android 11? Or do I need to un-root, upgrade and try a fresh root on A11? Thanks.
boominski said:
Sorry if this has been asked before (I couldn't find anything) but is it possible to upgrade a rooted 3aXL to Android 11? Or do I need to un-root, upgrade and try a fresh root on A11? Thanks.
Click to expand...
Click to collapse
Download the full image for Android 11 then use either the flash-all.bat file (will do a factory format so beware) or adb sideload it.
Going to a new version of Android it's always recommended to factory format.
Either way you will need to re-root after using magisk canary
This is pretty much what I thought. So there's no way to keep root then :crying:
boominski said:
This is pretty much what I thought. So there's no way to keep root then :crying:
Click to expand...
Click to collapse
Cheer up @boominsko you act like you loose root permanently. After updating just do the patch boot.img thing. Make sure to use the latest Magisk Canary. Also make sure to switch to canary channel.
Haha! Yeah, it's not so bad. Just a bit of a pain in the backside to fiddle around with files and ADB etc. Oh well. Thanks for the advice though!
boominski said:
This is pretty much what I thought. So there's no way to keep root then :crying:
Click to expand...
Click to collapse
You have to redo root even after security patches every month. This is no different
Hi,
I am currently on Android 12, rooted with Magisk, and I update each month using the latest Factory Image.
If (when) I upgrade to Android 13...
- I know it's usually recommended to do a clean install when you go to a brand new build, which means wiping data. I'm okay with this ASIDE from the fact that I have GBs worth of music on my phone which takes forever to both back up and restore.
- Do I really need to install 13 to both slots?
- Is root / Magisk working fine on 13?
- Any other suggestions on how to make this upgrade easier?
Thanks in advance!
Tony
tonyfiore75 said:
Hi,
I am currently on Android 12, rooted with Magisk, and I update each month using the latest Factory Image.
If (when) I upgrade to Android 13...
- I know it's usually recommended to do a clean install when you go to a brand new build, which means wiping data. I'm okay with this ASIDE from the fact that I have GBs worth of music on my phone which takes forever to both back up and restore.
- Do I really need to install 13 to both slots?
- Is root / Magisk working fine on 13?
- Any other suggestions on how to make this upgrade easier?
Thanks in advance!
Tony
Click to expand...
Click to collapse
it would be recommended to flash at least the bootloader to both slots, root works perfectly fine
tonyfiore75 said:
Hi,
I am currently on Android 12, rooted with Magisk, and I update each month using the latest Factory Image.
If (when) I upgrade to Android 13...
- I know it's usually recommended to do a clean install when you go to a brand new build, which means wiping data. I'm okay with this ASIDE from the fact that I have GBs worth of music on my phone which takes forever to both back up and restore.
Click to expand...
Click to collapse
I haven't wiped before flashing a new version of Android on my Pixel phones in the last 5-6 years. Android 13 Stable that I manually updated using the full factory image, coming from the first Android 12 July update has worked fine for me.
Good thing, too, because I hate starting from scratch any more.
(I too have hundreds of GBs of music on my phone)
tonyfiore75 said:
- Do I really need to install 13 to both slots?
Click to expand...
Click to collapse
"Have to"? No. It would be good advice to install it to both slots, though.
tonyfiore75 said:
- Is root / Magisk working fine on 13?
Click to expand...
Click to collapse
Yes.
tonyfiore75 said:
- Any other suggestions on how to make this upgrade easier?
Thanks in advance!
Tony
Click to expand...
Click to collapse
No. Everything was just like every month's normal update process for me with flashing the full firmware zip to update, and then I flashed it again to the other slot the next day.
Thanks, everyone! I really appreciate it. I'll just flash the update as I normally would (editing the .bat file) to Slot A and then do the same to Slot B. Or can you flash it to -all slots at the same time? I know I used to do that with my Pixel 4 but that may have just been when flashing the magisk file.
tonyfiore75 said:
Or can you flash it to -all slots at the same time?
Click to expand...
Click to collapse
Yes, you can.
Cool, thanks.
Sorry it's my first time with root and a custom kernel in the pixel, I have never updated it because I installed it on June, could you post a guide with the commands please?
Thanks a lot!
jumpet said:
Sorry it's my first time with root and a custom kernel in the pixel, I have never updated it because I installed it on June, could you post a guide with the commands please?
Thanks a lot!
Click to expand...
Click to collapse
Hiya! Just click the yellow How To Guide quick filter at the top of list of threads in this section, and there are at least two or three threads for how to update. The OP of the thread in my signature below also has the commands.
roirraW edor ehT said:
Yes, you can.
Click to expand...
Click to collapse
If I have to flash to both slots with the factory image, do I also have to flash to both slots with the updated Magisk file as well?
Didn't come to the forum to read messages in the past few days! I updated my P6P from A13 beta 4.1 to official using the factory image -w method as I have done it in the past 10 months. It is now running smoothly and I didn't encounter any problem so far. I start reading messages saying that A13 has to be flashed in slot A and slot B. Since I already upgrade my machine with normal method, I still able to keep my data, root and API integrity, and most import booting up normally, so do I have do it again to reflash to this Slot A/B thing? I am not so sure I understand this new requirement, so sorry if this question sounds stupid.
tonyfiore75 said:
If I have to flash to both slots with the factory image, do I also have to flash to both slots with the updated Magisk file as well?
Click to expand...
Click to collapse
Not really. Just do it on the slot you end up running. The slot you won't be running won't have root, but that's okay. You'll likely never actually use the other slot, and if by some rare chance you do, it's an easy thing to flash the Magisk'd stock boot.img to it at that time.
acwcanada said:
Didn't come to the forum to read messages in the past few days! I updated my P6P from A13 beta 4.1 to official using the factory image -w method as I have done it in the past 10 months. It is now running smoothly and I didn't encounter any problem so far. I start reading messages saying that A13 has to be flashed in slot A and slot B. Since I already upgrade my machine with normal method, I still able to keep my data, root and API integrity, and most import booting up normally, so do I have do it again to reflash to this Slot A/B thing? I am not so sure I understand this new requirement, so sorry if this question sounds stupid.
Click to expand...
Click to collapse
I'm trying to answer on mobile, so it's tough for me because most detailed support I give I do from the computer but I can't right now.
Check out the OP and last few pages of the thread on my signature below (use desktop mode in a mobile browser if necessary) for more information about flashing to both slots.
Look at it this way. Normally you only flash the full factory image once (so only to one slot). This time you did it once already, so now you'll have to switch slots and flash it to the other slot.
You could then switch slots again and use the slot you already re-rooted. Both slots have the same exact apps and app data - the second flashed slot just won't have the rooted boot.img that you already have on the slot you're running now.
I think it's most simple to use the Google flash tool. You don't have to wipe anything, just unroot, run the tool, reroot. Not script editing and praying that you didn't screw anything up.
rhetorician said:
I think it's most simple to use the Google flash tool. You don't have to wipe anything, just unroot, run the tool, reroot. Not script editing and praying that you didn't screw anything up.
Click to expand...
Click to collapse
That's how I do it every month
roirraW edor ehT said:
I'm trying to answer on mobile, so it's tough for me because most detailed support I give I do from the computer but I can't right now.
Check out the OP and last few pages of the thread on my signature below (use desktop mode in a mobile browser if necessary) for more information about flashing to both slots.
Look at it this way. Normally you only flash the full factory image once (so only to one slot). This time you did it once already, so now you'll have to switch slots and flash it to the other slot.
You could then switch slots again and use the slot you already re-rooted. Both slots have the same exact apps and app data - the second flashed slot just won't have the rooted boot.img that you already have on the slot you're running now.
Click to expand...
Click to collapse
OK, thanks so much, achieved done that. One more question, how about the future updates? Do we have to do it every month in the future when Google provide the monthly updates?
acwcanada said:
OK, thanks so much, achieved done that. One more question, how about the future updates? Do we have to do it every month in the future when Google provide the monthly updates?
Click to expand...
Click to collapse
No, you only needed to flash to both slots this one time just to make sure both slots were on A13.
Lughnasadh said:
No, you only needed to flash to both slots this one time just to make sure both slots were on A13.
Click to expand...
Click to collapse
Thank you for the feedback.
rhetorician said:
I think it's most simple to use the Google flash tool. You don't have to wipe anything, just unroot, run the tool, reroot. Not script editing and praying that you didn't screw anything up.
Click to expand...
Click to collapse
No need to unroot - just run the tool (making sure wipe or force flash all partitions isn't selected), and then reroot.
I like the satisfaction of getting my hands a little dirty, plus the knowledge that if something goes wrong, it's most probably my fault!
I also like to Magisk my own boot.img from the factory image, and if I'm going to download it anyway, I figure might as well flash it.