Root magisk questions - Samsung Galaxy S20 / S20+ / S20 Ultra Questions &

Hey guys.
I'm reading the forum over and over, reading guides but still can't quite understand few things about magisk root.
1) Is it necessary to use TWRP for root using magisk? I found a guide to patch stock rom boot.img and then flash custom rom without TWRP. This way encryption also works (I read it doesn't if you use TWRP).
What is the purpose to use TWRP at all? What are the pros and cons of each method.
2) How is OTA update handled for Samsung with magisk? Do I have to revert back to stock rom using odin each time a new update appears?
Or I can do download OTA update, apply it, then without reboot, I just reinstall magisk from my phone and everything will work?
3) Can you make signed custom rom for samsung so you can lock bootloader after root, just like people do it for one plus on this forum?
Or it is not possible with samsung?
Thanks in advance for help.

Kape1234 said:
Hey guys.
I'm reading the forum over and over, reading guides but still can't quite understand few things about magisk root.
1) Is it necessary to use TWRP for root using magisk? I found a guide to patch stock rom boot.img and then flash custom rom without TWRP. This way encryption also works (I read it doesn't if you use TWRP).
What is the purpose to use TWRP at all? What are the pros and cons of each method.
2) How is OTA update handled for Samsung with magisk? Do I have to revert back to stock rom using odin each time a new update appears?
Or I can do download OTA update, apply it, then without reboot, I just reinstall magisk from my phone and everything will work?
3) Can you make signed custom rom for samsung so you can lock bootloader after root, just like people do it for one plus on this forum?
Or it is not possible with samsung?
Thanks in advance for help.
Click to expand...
Click to collapse
Hello,
First off I would just let you know that typically questions like this go in the Q&A section.. This is S20/S20+/S20U Snapdragon Development thread which is usually reserved for people who develop things such as roms, twrp, mods etc. etc. so be sure to ready the rules and other stickied information when considering to post just to be sure you post in the right section.
So next thing I want to say is that in order to use TWRP or root or anything custom really on a usa Snapdragon model (U/U1/W Models) you have to use paid service to unlock the bootloader IF your device is eligible to be unlocked which means you haven't updated to the latest OS, if it is, then you are out of luck for now until new method is developed using new security.
If you are unlocked already, can unlock or just want to know I will try and answer your questions now.
1) TWRP is not necessary. Neither is patching the full ROM. All you need to do (if you don't want to use TWRP) is take the boot.img from the stock firmware, patch it using Magisk app and then flash it in ODIN. Device will wipe most likely if encryption and vbmeta etc. isn't disabled already. I do not know if "encryption" works while just rooted using Magisk patched boot.img or not as I usually disable all that stuff. My guess is that in some form it would be encrypted, just not sure if it's the same thing you are referring to or not.
2) If you are on an unlocked bootloader and complete stock i.e. no root or anything just clean full stock then you should get OTA updates. If you use anything "custom" i.e. Magisk patched boot.img or TWRP installed or vbmeta disabled etc. etc. then OTA updates will NOT work. And no, you don't have to revert to stock in ODIN each time there is a firmware update. It really depends on the update but you can typically use the odin tar with home csc and it should update without wiping but at the same time you would lose root or need to re-patch the new boot.img etc. etc. but wouldn't necessarily have to flash stock first then start over. There's also "safe" updates available some posted by jrkruse in development sections. If you had a usa unlocked device that was unlocked using paid service then you do NOT want to take OTA's because Samsung has changed the way tokens are verified when device boots up so new OS can't read them and most devices have incremented the bootloader so if you did take an OTA you likely would lost your unlock and no way to downgrade.
3) No. In order to do that you would need Samsung's private keys since there is no way to load your own custom key to use.. you can't just sign it with any key.. Also, if you relock your bootloader on a USA model that was unlocked using paid service then you will not be able to unlock again.. either way, it's not possible to use a custom signed firmware then relock the bootloader and have it boot.. not on Samsung anyway..
Hope that clears it up for you.
Thanks

Related

[HELP!] Systemless Rooting on 6.0.1 Build MMB29P

Hi! So I'm looking to root my Nexus 5x following this guide. However, I can't find the modified boot.img for my build MMB29P. I have a brand new phone out of the box (my mic stopped working so this is a replacement) so I'd like to get this done in the next little while the phone has no data and I can wipe anything I need to without worry and use the restore afterwards. I also heard something about SuperSU being able to use stock boot.img or something of that nature, could someone clue me in? Thanks!
[GUIDE] Unlock/Root/Flash for Nexus 5X - Heisenberg's How-To Guide For Beginners
take a look at section 6
as an alternative there are some toolkits that may be more convenient to you (on-screen instructions and detailed faq/guides)
The latest version of SuperSU (v. 2.66 I believe) is automated for systems root. I actually used the SuperSU beta v. 2.62 to root. I just unlocked bootloader, flashed TWRP, and then flashed that version of SuperSU.
Sent from my Nexus 5X using Tapatalk
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
https://www.androidfilehost.com/?w=files&flid=43558
k.s.deviate said:
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
Click to expand...
Click to collapse
Even with systemless root?
When it comes to upgrading, there are a couple of routes you can take. Both involve downloading the official factory image ZIP first. Extract the contents, reboot into bootloader, and then you have option:
1. Edit the flash-all script (.bat for windows and .sh for Linux/Mac) by removing the -w option. Removing this option will prevent the upgrade from wiping user data. Once the option is removed, simply run the script to upgrade.
2. Flash the images individually. Sometimes certain things don't change like bootloader.img or radio.img. You should always flash boot.img, system.img, and vendor.img when updating. This is the route I take.
After flashing the images, you will need to reboot into Recovery mode and flash SuperSU. Then wipe cache and dalvik and reboot into system. If you use a custom kernel, you will need to reflash that as well after updating.
Sent from my Nexus 5X using Tapatalk
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
jkingaround said:
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
Click to expand...
Click to collapse
Google posts the official factory images on the developer site. Here is the link: https://developers.google.com/android/nexus/images
AFAIK the boot warning can't be removed, but I may be wrong. It's nothing to worry about though.
Having a custom kernel is not necessary, but there are benefits to using one. Custom kernels typically provide better battery life with same or improved performance. They can also make your device run cooler and use less memory. Custom kernels also allow for various tweaks such as change vibration intensty, screen DPI, headphone/speaker gain, etc. I personally use ElementalX with the Interactive Governor tweaks from the thread in the general forum, but I've read that Franco Kernel is very good as well and will probably try that out in the future.
Sent from my Nexus 5X using Tapatalk
jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
Just pick a custom rom to try and follow OP instructions. Cataclysm seems to be a hit...

How to remove Root from Galaxy Tab S?

I bought a second hand Samsung Galaxy Tab S a few months ago and it has been working fine.
However, when I looked at version of Android then seems a bit old (5.0.2) and when I did a check for updates it said that it couldn't update because "The operating system on your device has been modified in an unauthorised way". When I checked then it seems that the device has been rooted.
A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
So, should it be possible to remove the root and still preserve all my data, apps, settings, etc?
If so, is SuperSu the way to go or are there other tools I should look at, such as Kingo Android Root?
Or, am I faced with rebuilding with a stock ROM?
Thanks
There is no update. 5.0.2 is the latest.
ashyx said:
There is no update. 5.0.2 is the latest.
Click to expand...
Click to collapse
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
MysteryMan1 said:
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
Click to expand...
Click to collapse
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
3DSammy said:
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
I've tried to fire up SuperSU, but, run into problems, as described in my initial post, and this is what I need to resolve.
Any ideas?
MysteryMan1 said:
... A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
...
Click to expand...
Click to collapse
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
3DSammy said:
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
Click to expand...
Click to collapse
Thank you for your very helpful and comprehensive reply. I can't profess to understanding all of it, but, I am sure I will get there eventually!
I shall follow your suggestion of trying to get get SuperSU installed first.
:good:
If you want to go back to stock just flash the latest firmware with odin.

Want to root Friends Note 4, a few questions.

Hello,
I want to root my friends sprint note 4 (lolipop i believe). I was looking at this guide http://galaxynote4root.com/galaxy-note-4-root/how-to-root-galaxy-note-4note-edge-on-android-5-1-1/ and it seems straightforward. A little different than what I had to do with my phone becuase I had to unlock the bootloader and then flash the recovery and supersu. (I've never used odin) Does this mean the bootloader is already unlocked by default since all I have to do is install the recovery and then the kernel?
I'm a little confused, once I get the recovery, can I flash roms to it? Do I have to change the kernel again if I want to install a ROM? I don't plan on putting a custom ROM on his phone but I want reflash the stock rom or a debloated stock rom because he said even after a factory reset it was buggy (if you can link me to a proper stock rom that supports xposed I would be grateful).
And I also want xposed to work, is there a specific xposed version I should install?
And also, if I do flash something, is this method correct?
Backup data
factory reset
flash
clear cache
restore data
reboot
or do I restore the data later?
The thread and video are dated. A few key elementary facts are still relevant but as a whole, just not up to date. I wouldn't trust it and it lends to repeated help threads in this forum. If one read the OPs and threads of current ROMs in development and recent help threads, maybe less questions and help would be needed.
He omits current ROMs, didn't mention where the reactivation lock is for TW Android ROMs: Settings/Security/Reactivation lock (should be disabled). He doesn't mention Chainfire Auto root for Note 4 has been updated for 5.1 and will be key again for marshmallow (but that's only needed for rooting stock Odex). He also didn't tell you how to get to those old ROMs on his site. Some think you just Odin an old update but not so. That requires a 5.1 kernel matched with current bootloader rather than Odin downgrade.
The bootloader, while not locked to block root, is considered unlocked but actually is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Kernels should be kept in zip form because backing up a kernel in TWRP doesn't backup /system/lib/modules to restore and some custom kernels modify or add modules which may not work restored boot.img And restoring stock kernel on a rooted phone would cause a boot loop. So to restore that, you'd need to full un-root in SuperSU to avoid the boot loop there as well as restore the stock /system/lib/modules.
Root methods: unless you're using the full un-root or wiping everything but extSdCard (particularly user data and internal memory), you don't fully remove systemless root. Flashing a ROM or SuperSU with system based SuperSU over systemless root without the wipes would break things like root. Not seeing the SuperSU app or loss of ability to add new apps to superuser would be impacted but also a boot loop is possible if but patching stock kernel su.img to boot.
The basic principal is that to flash the custom deodexed ROM you need for Xposed, just make sure you're on the right update, Odin TWRP and follow the OP closely. If wiping internal memory is suggested by OP, I'd suggest that. To keep things simple, I backup and wipe everything but extSdCard for ports or where Xposed or systemless SuperSU is used. I typically do the same for stock tar updates as well.
As to recommended ROMs, I'd suggest any deodexed OK1 ROM for Xposed. tx_dbs_tx has a variety of OK1 ROMs. Freeza has one with Xposed integrated with Xposed modules in system. If Note 5 Moar port is a good fit, I'd recommend trying without Xposed until you determine the minimum of Xposed mods you're lacking so you're not overlapping features and you're getting to know the stability of it, first.
Rooting a friend's phone? IMO, you should be very sure and confident before proceeding and advise rather than do all the work and take the risks yourself. Use the correct USB driver, not just one that works. Setup his computer to root and sustain that phone.
Sent from my SM-N910P using Tapatalk
How is it dated exactly? I thought 5.1 is highest OTA for Note 4? Do OTA security patches change how things work now? I wouldn't know about security patches since I have a moto x 2013, we are left in the dust.
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version? Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
rapiollymega said:
How is it dated exactly? I thought 5.1 is highest OTA for Note 4?
Click to expand...
Click to collapse
I answered that in detail.
rapiollymega said:
Do OTA security patches change how things work now?
Click to expand...
Click to collapse
No; it's the bootloader and updates that did that.
rapiollymega said:
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
Click to expand...
Click to collapse
Good choice.
rapiollymega said:
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version?
Click to expand...
Click to collapse
Answered. Use Phone Info from Google Play or Galaxy Tools.
rapiollymega said:
Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
Click to expand...
Click to collapse
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
samep said:
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Click to expand...
Click to collapse
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
rapiollymega said:
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
Click to expand...
Click to collapse
It's the INTERNET that's ambiguous towards Touchwiz Android 5.1 There has been a few updates and each changed the way we do things. So when you say you're on Android 5.1, I say you need to be on the latest 5.1 update to have the greatest compatibility with the ROM you're choosing to flash.
Yes. You use Odin to install TWRP when rooting from full stock un-root to custom pre-rooted ROM. Perhaps my direction to Odin TWRP was ambiguous? Flash this in Odin AP slot with auto reboot unchecked- use the other option defaults from latest Odin:
https://dl.twrp.me/trltespr/twrp-3.0.0-0-trltespr.img.tar.html
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
I would restore data after installing Xposed. Keep in mind that these installation boots of custom ROM and Xposed take time. The less apps and data, the shorter the boot times will be. Plus the ROM will have more time to stabilize. After you've verified the last three of the bootloader and modem matches OK1, you can proceed with TWRP, then install ROM per the 1st post and immediate posts from OP. When you get to the Wi-Fi connection in setup wizard, make sure you have radio signal before connecting Wi-Fi. Make sure everything is stable and functional before Xposed installation.
Again, about the long boot times on installation. Best to keep case off the phone and ventilate phone with not too cool or ambient air. This will speed the process and possibly prevent component failure.
When your ready for Xposed, you need the Wanam unofficial Xposed framework.
http://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
You'll need sdk22 arm for Lollipop, not 64 bit Exynos or MM.
Currently it's the one labeled: xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip
Grab the uninstaller too, just in case. You shouldn't need it but be prepared.
Edit: be sure to get the deodexed version of that ROM. Makes things easier for Xposed and Xposed compatibility when adding system applications, if that applies to anytime later.
Sent from my SM-N910P using Tapatalk
Thanks for all the help, did it over the weekend and everything went smoothly. Well except for one part before installing the new ROM, I deleted everything in data/system and forgot that the zip was In the internal storage instead of the sd card . And for whatever reason the PC usb connection wasn't working in TWRP so I had to use a flash drive and otg cable to put the zip ROM back in the phone.

Help – I'm lost. New to HTC and quite confused about flashing/rooting/...

Hey there,
I've got my first HTC device some days ago (-> HTC 10), but coming from a Nexus 5 where things are handled differently, I'm currently quite confused on how all of this works with my HTC 10.
I'd like to apologize in advance if the following questions seem to be stupid or unnecessary, but I'd like to use my device to the fullest and therefore I need your help.
My device is not branded (as far as I can tell) and I've already unlocked it via the steps on htcdev.com + I've installed TWRP + SuperSU (thanks to my previous knowledge with my N5 this was somewhat easy).
Now I got my first OTA update and this is when things got complicated. Several questions popped up and I tried to answer them myself while looking over here, but after reading all those threads I'm even more confused than before :/
My questions are the following:
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2)
2) Do I need a microSD card in order to do so? I've seen several YT videos where they did a backup of the current system, but there still was a data wipe after flashing, so why even bother doing a backup at all?
3) My device is unlocked but with S-ON. Do I need S-OFF after all? As far as I can tell I don't need this, but is there any scenario I'd probably need it? (see question 4)
4) I'm thinking about getting a custom rom (Leedroid seems to be pretty decent). Can you recommend any of those custom roms and do I need S-OFF in order to flash them?
5) S-OFF + Locked or S-OFF + Unlocked? What's the difference? Any issues with the warranty?
6) If I do use a custom rom (e.g. Leedroid), is there also a way to update it to further versions without losing any data?
7) Where do I get the latest firmware for manually updating my device? I've already found a thread for it (http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297), but my current firmware (1.90.401.5) or the one for the OTA update that already popped up (1.95.401.3) isn't listed over there. [EDIT: found my current firmware. Do I need to flash to it in order to do the OTA update?)
8) One last general question: as far as I understand it, unlocking your device is also the same as debranding it? I'm not sure if I'm mixing things up when reading about this. Is there any way to see if my device was branded before I did unlock/root it though?
I'm completely fine with losing my current data if that means that I can set it up my device in such a way that I can avoid any further data wipes when flasing/updating.
I'd be absolutely grateful if someone would answer those questions and help me to understand all of this.
Greetings,
makit_
1) Yes..you can apply the OTA manually, which won't flash the firmware image in the update but you can then find a no-wipe version of the new firmware on xda and flash it. Check out the faq in the twrp thread
2) for flashing firmware packages generally yes its better to have an SD card but I *think* it's possible to do it by issuing fastboot commands
3) s-off is needed if you wanna flash a new firmware I believe
4) you don't need S-off to flash a new ROM that's compatible with your firmware. Leedroid should work for you (this answer can be easily found by checking out each ROM thread and reading the Prerequisites section)
5) yes, most of the time you can "dirty flash" a new version of the same rom on top of the old one without wiping. If any issues pop up, or if it's a new base with large differences, then a wipe is needed. You can usually tell if a wipe is required by checking out what the developer says in the thread when a new updated is posted
6) I'm sure it's in a thread somewhere, you gotta search (I think sneakyghost's thread might have them)! And again you need S-off if you wanna flash firmwares
not an expert but here's my thoughts...
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2) Yes. But if you want official update from HTC or your carrier via OTA you should be on stock. If you're on custom ROM, you can always dirty flash. But updating to a newer build, ROM dev sometimes recommend a full wipe
2) Do I need a microSD card in order to do so? I've seen several YT videos where they did a backup of the current system, but there still was a data wipe after flashing, so why even bother doing a backup at all?
SD card is not a requirement but is recommended since a full back-up size is ranging from 5gb-10gb maybe more depending in how many apps you installed. Backup is also recommended so you can always go back/restore your working ROM in case you messed up updating.
3) My device is unlocked but with S-ON. Do I need S-OFF after all? As far as I can tell I don't need this, but is there any scenario I'd probably need it? (see question 4). You need s-off mostly on updating your firmware or converting your device to other carrier or if you want to be unlocked. Right now you can flash any custom roms you like since we do not have a major update yet eg.1.x to 2.x. Once 2.x firmware is released, You can easily flash this firmware. But if you're S-ON, you can only update your firmware via official OTA from your carrier or if @Sneakyghost provide specific firmware for your carrier (matching cid and mid) in this thread else you're stock at 1.x firmware and ROMs that will only work on that specific firmware.
4) I'm thinking about getting a custom rom (Leedroid seems to be pretty decent). Can you recommend any of those custom roms and do I need S-OFF in order to flash them? See my answer in #3
5) S-OFF + Locked or S-OFF + Unlocked? What's the difference? Any issues with the warranty? If you're S-off you can always revert back to S-on and return to stock for warranty purposes.
6) If I do use a custom rom (e.g. Leedroid), is there also a way to update it to further versions without losing any data? Yes. see also #1
7) Where do I get the latest firmware for manually updating my device? I've already found a thread for it (http://forum.xda-developers.com/htc-...u-ota-t3359297), but my current firmware (1.90.401.5) or the one for the OTA update that already popped up (1.95.401.3) isn't listed over there. [EDIT: found my current firmware. Do I need to flash to it in order to do the OTA update?)See @Sneakyghost thread linked in #3. Firmware updating can be done via OTA or via fastboot(firmware zip can be downloaded) or full RUU (updating both ROM and firmware).
8) One last general question: as far as I understand it, unlocking your device is also the same as debranding it? I'm not sure if I'm mixing things up when reading about this. Is there any way to see if my device was branded before I did unlock/root it though? I think you meant sim unlocking here?? Generally, "unlocking" mostly mentioned in xda refers to bootloader
Tarima said:
1) Yes..you can apply the OTA manually, which won't flash the firmware image in the update but you can then find a no-wipe version of the new firmware on xda and flash it. Check out the faq in the twrp thread
2) for flashing firmware packages generally yes its better to have an SD card but I *think* it's possible to do it by issuing fastboot commands
3) s-off is needed if you wanna flash a new firmware I believe
4) you don't need S-off to flash a new ROM that's compatible with your firmware. Leedroid should work for you (this answer can be easily found by checking out each ROM thread and reading the Prerequisites section)
5) yes, most of the time you can "dirty flash" a new version of the same rom on top of the old one without wiping. If any issues pop up, or if it's a new base with large differences, then a wipe is needed. You can usually tell if a wipe is required by checking out what the developer says in the thread when a new updated is posted
6) I'm sure it's in a thread somewhere, you gotta search (I think sneakyghost's thread might have them)! And again you need S-off if you wanna flash firmwares
Click to expand...
Click to collapse
Thanks for your response! The numeration is wrong though as I edited my post while you were already typing your answers, but I figured it out nonetheless
–––––––––––––––––––––––
side_flip15 said:
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2) Yes. But if you want official update from HTC or your carrier via OTA you should be on stock. If you're on custom ROM, you can always dirty flash. But updating to a newer build, ROM dev sometimes recommend a full wipe
Click to expand...
Click to collapse
When using a custom ROM, is it also possible to save your data so you can restore it after the full wipe?
side_flip15 said:
2) Do I need a microSD card in order to do so? I've seen several YT videos where they did a backup of the current system, but there still was a data wipe after flashing, so why even bother doing a backup at all?
SD card is not a requirement but is recommended since a full back-up size is ranging from 5gb-10gb maybe more depending in how many apps you installed. Backup is also recommended so you can always go back/restore your working ROM in case you messed up updating.
Click to expand...
Click to collapse
As far as I can tell, when doing a backup, you dont save your data 'partition' as it is encrypted anyways. Do I assume right that when doing a backup, I cannot restore my data I had before doing the flash?
side_flip15 said:
3) My device is unlocked but with S-ON. Do I need S-OFF after all? As far as I can tell I don't need this, but is there any scenario I'd probably need it? (see question 4). You need s-off mostly on updating your firmware or converting your device to other carrier or if you want to be unlocked. Right now you can flash any custom roms you like since we do not have a major update yet eg.1.x to 2.x. Once 2.x firmware is released, You can easily flash this firmware. But if you're S-ON, you can only update your firmware via official OTA from your carrier or if @Sneakyghost provide specific firmware for your carrier (matching cid and mid) in this thread else you're stock at 1.x firmware and ROMs that will only work on that specific firmware.
Click to expand...
Click to collapse
I've already seen the sunshine thread which is about turning S-OFF. While it is possible to go back to S-ON, it was recommended to let your device stay in S-OFF. Is there a high risk in bricking your device when trying to go back to S-ON?
side_flip15 said:
4) I'm thinking about getting a custom rom (Leedroid seems to be pretty decent). Can you recommend any of those custom roms and do I need S-OFF in order to flash them? See my answer in #3
5) S-OFF + Locked or S-OFF + Unlocked? What's the difference? Any issues with the warranty? If you're S-off you can always revert back to S-on and return to stock for warranty purposes.
Click to expand...
Click to collapse
As far as I know, doing so will void your warranty. Won't they notice if I just revert it myself and then send it in for warranty?
side_flip15 said:
7) Where do I get the latest firmware for manually updating my device? I've already found a thread for it (http://forum.xda-developers.com/htc-...u-ota-t3359297), but my current firmware (1.90.401.5) or the one for the OTA update that already popped up (1.95.401.3) isn't listed over there. [EDIT: found my current firmware. Do I need to flash to it in order to do the OTA update?)See @Sneakyghost thread linked in #3. Firmware updating can be done via OTA or via fastboot(firmware zip can be downloaded) or full RUU (updating both ROM and firmware).
Click to expand...
Click to collapse
Sorry this might be a rather dumb question, but I always thought ROM and firmware are the same thing. Or is it that updating my device via OTA is updating my firmware, while installing something like Leedroid is altering my ROM?
Again, thanks for all your responses in advance! You're helping me out a lot!
Greetings,
makit_
When using a custom ROM, is it also possible to save your data so you can restore it after the full wipe?
Click to expand...
Click to collapse
its possible but there's possibility that you might have some issue. Not sure though, never done that. I always use titanium backup to restore my apps.
As far as I can tell, when doing a backup, you dont save your data 'partition' as it is encrypted anyways. Do I assume right that when doing a backup, I cannot restore my data I had before doing the flash?
Click to expand...
Click to collapse
Data partition can be backed up actually and can be restored.
I've already seen the sunshine thread which is about turning S-OFF. While it is possible to go back to S-ON, it was recommended to let your device stay in S-OFF. Is there a high risk in bricking your device when trying to go back to S-ON?
Click to expand...
Click to collapse
Agree. there is no sense in reverting back to s-on unless if it's for warranty purposes.
Is there a high risk in bricking your device when trying to go back to S-ON?
Click to expand...
Click to collapse
I would say NO. I never used sunshine to s-off. I am using a hardware s-off and I did not experience any issue going back to s-on.
As far as I know, doing so will void your warranty. Won't they notice if I just revert it myself and then send it in for warranty?
Click to expand...
Click to collapse
On the device itself, I don't think so as long as you return it in full stock state. But if I remember correctly HTC dev requires you to provide your imei when requesting for unlock token bin file used to unlock bootloader, So if your unlock you device via HTC dev they have your imei in their record. They know that you already unlocked your device and warranty is void already.
Sorry this might be a rather dumb question, but I always thought ROM and firmware are the same thing
Click to expand...
Click to collapse
Take a look at this link. It provides you a complete explanation between ROM and Firmware.
Or is it that updating my device via OTA is updating my firmware, while installing something like Leedroid is altering my ROM?
Click to expand...
Click to collapse
Updating via official OTA usually updates ROM and firmware.
Installing a custom rom does not update firmware. Yes, it only alters ROM. But your ROM should always match your firmware at least the first digit of the firmware version (eg. 1.xx). For instance Android N (firmware veraion to be 2.x) arrives and LeeDroid updates its ROM to this, to be able to flash this latest custom rom, your firmware should also be at latest 2.x firmware else it will not boot. In this case, you need to update your firmware either via OTA, Fastboot or RUU.
makit_ said:
Thanks for your response! The numeration is wrong though as I edited my post while you were already typing your answers, but I figured it out nonetheless
–––––––––––––––––––––––
When using a custom ROM, is it also possible to save your data so you can restore it after the full wipe?
As far as I can tell, when doing a backup, you dont save your data 'partition' as it is encrypted anyways. Do I assume right that when doing a backup, I cannot restore my data I had before doing the flash?
I've already seen the sunshine thread which is about turning S-OFF. While it is possible to go back to S-ON, it was recommended to let your device stay in S-OFF. Is there a high risk in bricking your device when trying to go back to S-ON?
As far as I know, doing so will void your warranty. Won't they notice if I just revert it myself and then send it in for warranty?
Sorry this might be a rather dumb question, but I always thought ROM and firmware are the same thing. Or is it that updating my device via OTA is updating my firmware, while installing something like Leedroid is altering my ROM?
Again, thanks for all your responses in advance! You're helping me out a lot!
Greetings,
makit_
Click to expand...
Click to collapse
Thats a thing that iam also interested in. Iam also new to htc.
I think with firmware they mean bootloader. But nobody gave me a good answer till now...
side_flip15 said:
its possible but there's possibility that you might have some issue. Not sure though, never done that. I always use titanium backup to restore my apps.
Click to expand...
Click to collapse
I know that app by name, but never used it. Will take a look into it
side_flip15 said:
I would say NO. I never used sunshine to s-off. I am using a hardware s-off and I did not experience any issue going back to s-on.
Click to expand...
Click to collapse
Do you mean like this? (found in another forum):
1. First step is to unlock bootloader:
a) If bootloader unlock is turned off on your phone, you need to turn it on first:
- Boot to Android OS and perform initial setup if necessary
- Go to Menu -> Developer settings and tick "Enable OEM unlock"
Run XTC 2 Tool and open "Bootloader unlock" tab, follow instructions to unlock your bootloader.
2. Reboot to download mode, open "HTC 10" tab and install twrp recovery, you can get it here:
[...]
or
[...]
3. Boot to Bootloader, and press "Reboot to recovery".
4. In "HTC 10" tab press "Do S-OFF button".
5. Wait for the process to finish. Done.
Click to expand...
Click to collapse
side_flip15 said:
On the device itself, I don't think so as long as you return it in full stock state. But if I remember correctly HTC dev requires you to provide your imei when requesting for unlock token bin file used to unlock bootloader, So if your unlock you device via HTC dev they have your imei in their record. They know that you already unlocked your device and warranty is void already.
Click to expand...
Click to collapse
Yeah, I've done it this way. Sucks. But maybe it's not this bad at all. As I'm trying to be safe anyway, I probably only need to make use of the warranty if I'd accidentally drop my device. Those cases are still valid for warranty as far as I can tell (extract from the htcdev.com site: 'Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader.'). Do you also know anything about this?
side_flip15 said:
Take a look at [... ]this link[/URL]. It provides you a complete explanation between ROM and Firmware.
Click to expand...
Click to collapse
Thanks, will look into it.
side_flip15 said:
Updating via official OTA usually updates ROM and firmware.
Installing a custom rom does not update firmware. Yes, it only alters ROM. But your ROM should always match your firmware at least the first digit of the firmware version (eg. 1.xx). For instance Android N (firmware veraion to be 2.x) arrives and LeeDroid updates its ROM to this, to be able to flash this latest custom rom, your firmware should also be at latest 2.x firmware else it will not boot. In this case, you need to update your firmware either via OTA, Fastboot or RUU.
Click to expand...
Click to collapse
Good to know. So in order to use the latest Leedroid and get rid of that OTA update notification, I should do the following:
1) Go back to stock (flash via RUU)
2) Hardware S-OFF (see above)
3) Flash latest OTA update
4) Custom Recovery again (TWRP) + Root (SuperSU)
5) Install latest Leedroid (have to read about it first, but afaik I have to install the zip of it via TWRP)
6) done
Is this correct or are there any mistakes?
And thanks a ton, you've helped me so much already!
Greetings,
makit_
makit_ said:
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2)
Click to expand...
Click to collapse
If you are stock with only SU, then this is how I've gone about installing OTAs without wiping data:
1. Download ota (Settings>About>Software Updates) and move downloaded OTA from /data/data/com.htc.updater/files to sd card
2. In TWRP restore stock 'System Image' and 'Boot'
3. Reboot to Downloader
4. Flash stock recovery (fastboot.exe flash recovery xxx.img) --> can use current ota.zip > extract firmware.img from zip (if using 7zip -> rename .zip to .rar to extract fw)
5. Reboot to stock recovery
6. Install OTA in stock recovery
7. Reboot to Downloader
8. Reinstall TWRP (fastboot.exe flash recovery twrpxxx.img)
9. Backup stock 'System Image' and 'Boot'
10. In TWRP reflash SuperSu/Xposed/etc
yankee1390 said:
If you are stock with only SU, then this is how I've gone about installing OTAs without wiping data:
1. Download ota (Settings>About>Software Updates) and move downloaded OTA from /data/data/com.htc.updater/files to sd card
2. In TWRP restore stock 'System Image' and 'Boot'
3. Reboot to Downloader
4. Flash stock recovery (fastboot.exe flash recovery xxx.img) --> can use current ota.zip > extract firmware.img from zip (if using 7zip -> rename .zip to .rar to extract fw)
5. Reboot to stock recovery
6. Install OTA in stock recovery
7. Reboot to Downloader
8. Reinstall TWRP (fastboot.exe flash recovery twrpxxx.img)
9. Backup stock 'System Image' and 'Boot'
10. In TWRP reflash SuperSu/Xposed/etc
Click to expand...
Click to collapse
This sounds very convenient and not far too different than what I was used to with my N5. Guess I'll give it a go! Already found a way to disable the HTC lock screen http://forum.xda-developers.com/htc-10/help/disable-htc-10-lockscreen-t3418108 (which is annoying especially when using a different launcher as the lock screen background is still the one from the stock launcher). Only thing bugging me now is that BoomSound notification, but I guess I can live with that
makit_ said:
This sounds very convenient and not far too different than what I was used to with my N5. Guess I'll give it a go! Already found a way to disable the HTC lock screen http://forum.xda-developers.com/htc-10/help/disable-htc-10-lockscreen-t3418108 (which is annoying especially when using a different launcher as the lock screen background is still the one from the stock launcher). Only thing bugging me now is that BoomSound notification, but I guess I can live with that
Click to expand...
Click to collapse
may look at installing XPosed as they have a module "XNotifications" that lets you hide any type of notification
yankee1390 said:
may look at installing XPosed as they have a module "XNotifications" that lets you hide any type of notification
Click to expand...
Click to collapse
Will also look into this. I've used Xposed on my N5 but wasn't sure the HTC 10 is already fully supported (have read something about that, but those threads were already 3-4 months old). Thanks!
So I'm trying to do the step-by-step instructions from yankee1390 because I guess that's the easiest way for me to handle things. Now I've already got my first (and hopefully only) issue with it: I did no backup when I first installed TWRP and before I've rooted my device. So in order to accomplisch step 2) (restore stock system image + boot in TWRP), can I use the files from the RUU provided here -> http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297?
I've found the one matching my current firmware (1.90.401.5), so is it ok if I use those for step 2?
And by the way, I guess I have to do a backup after every OTA update (and before rooting) so I always have the right files for restoring, huh?
Greetings,
makit_
edit: may have found the solution to it Will update once I'm done.
makit_ said:
So I'm trying to do the step-by-step instructions from yankee1390 because I guess that's the easiest way for me to handle things. Now I've already got my first (and hopefully only) issue with it: I did no backup when I first installed TWRP and before I've rooted my device. So in order to accomplisch step 2) (restore stock system image + boot in TWRP), can I use the files from the RUU provided here -> http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297?
I've found the one matching my current firmware (1.90.401.5), so is it ok if I use those for step 2?
And by the way, I guess I have to do a backup after every OTA update (and before rooting) so I always have the right files for restoring, huh?
Greetings,
makit_
edit: may have found the solution to it Will update once I'm done.
Click to expand...
Click to collapse
Link didn't work on my app so can't confirm if that will work. However any TWRP stock backup that matches your current version should work. RUUs will wipe your data if you use them.
Definitely good idea to backup after each ota before modifying system partition to make next ota easier. Though usually someone on here can provide a backup if you don't get one.
I know that app by name, but never used it. Will take a look into it
Click to expand...
Click to collapse
i suggest you purchase a pro version. It's a really a must-have app
Do you mean like this? (found in another forum):
Click to expand...
Click to collapse
Yes. This is the process how to s-off using xtc2clip - A very handy tool that works almost every HTC devices. Support is great too.
Yeah, I've done it this way. Sucks. But maybe it's not this bad at all. As I'm trying to be safe anyway, I probably only need to make use of the warranty if I'd accidentally drop my device. Those cases are still valid for warranty as far as I can tell (extract from the htcdev.com site: 'Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader.'). Do you also know anything about this?
Click to expand...
Click to collapse
Yeah. They might not know we can s-off. lol
Good to know. So in order to use the latest Leedroid and get rid of that OTA update notification
Click to expand...
Click to collapse
If you mean OTA notification from HTC, most of the custom ROMs already disabled that, I believe. And they provide you with their own OTA update (Not all, some do. Like ViperRom)
I should do the following:
1) Go back to stock (flash via RUU)
2) Hardware S-OFF (see above)
3) Flash latest OTA update
4) Custom Recovery again (TWRP) + Root (SuperSU)
5) Install latest Leedroid (have to read about it first, but afaik I have to install the zip of it via TWRP)
6) done
Click to expand...
Click to collapse
This is correct but there is an easier way after you s-offed.
1. Download the latest firmware.zip, if you're not on the latest yet. Flash it via fastboot commands in download.
mode. Instruction is available in the link I provided earlier in @Sneakyghost firmware thread.
2. Flash TWRP.
3. Download your desired custom ROM (LeeDroid). This is in .zip file.
4. Reboot to recovery, wipe data/factory reset then flash the LeeDroid.zip. Just follow the instructions in aroma.
by the way, if you'll flash firmware.zip make you select the matching CID and MID of your device. You might end up bricking your device flashing a wrong firmware. If you can provide me your CID and MID, I'll link you to the correct firmware for your device. To do so, reboot to bootloader and type the following commands in cmd, remove your IMEI and SN and post the result here.
And thanks a ton, you've helped me so much already!
Click to expand...
Click to collapse
You are welcome.
---------- Post added at 02:22 AM ---------- Previous post was at 01:44 AM ----------
I never done updating software via HTC official update. I don't know but for me I don't see any reason sticking to stock ROM. There are a lot of custom ROMs out there tweaked for better performance and battery life. They are also always updated to latest build.
side_flip15 said:
i suggest you purchase a pro version. It's a really a must-have app
Yes. This is the process how to s-off using xtc2clip - A very handy tool that works almost every HTC devices. Support is great too.
Yeah. They might not know we can s-off. lol
If you mean OTA notification from HTC, most of the custom ROMs already disabled that, I believe. And they provide you with their own OTA update (Not all, some do. Like ViperRom)
This is correct but there is an easier way after you s-offed.
1. Download the latest firmware.zip, if you're not on the latest yet. Flash it via fastboot commands in download.
mode. Instruction is available in the link I provided earlier in @Sneakyghost firmware thread.
2. Flash TWRP.
3. Download your desired custom ROM (LeeDroid). This is in .zip file.
4. Reboot to recovery, wipe data/factory reset then flash the LeeDroid.zip. Just follow the instructions in aroma.
by the way, if you'll flash firmware.zip make you select the matching CID and MID of your device. You might end up bricking your device flashing a wrong firmware. If you can provide me your CID and MID, I'll link you to the correct firmware for your device. To do so, reboot to bootloader and type the following commands in cmd, remove your IMEI and SN and post the result here.
You are welcome.
Click to expand...
Click to collapse
Thanks for all your help. I will look into it when I need it. For now I'll stick with stock (see below)
side_flip15 said:
I never done updating software via HTC official update. I don't know but for me I don't see any reason sticking to stock ROM. There are a lot of custom ROMs out there tweaked for better performance and battery life. They are also always updated to latest build.
Click to expand...
Click to collapse
I love using stock android, that's why I also loved using my Nexus 5. I used CyanogenMod with another device many years ago but I am willing to use a custom ROM for my HTC 10, but only after I already know how it feels with stock ROM. So I will stick with it for several weeks and see how it feels, and when I'm farmiliar with it, I will switch to a custom ROM So thanks a lot, you've given me a lot of information I will still need for further experimenting with my phone!
Piggybacking on this thread because my new-to-me HTC 10 is coming in the mail and I'm planning what to do with it. It is already bootloader unlocked and s-off. I would like to use Leedroid, ElementalX, Magisk, and Xposed.
I've never had an HTC device so I just want to make sure I'm doing this right. So I think this is what I need to do:
1) Flash TWRP via ADB
2) Flash SuperSU in TWRP
3) Flash everything else...Leedroid, ElementX, Xposed, Magisk. In that order? Can I flash them all at once (just keep adding zips to the TWRP list) or do I have to boot between each one?
Xposed is more important to me than a custom ROM, because I need to use Amplify and PowerNap to improve my battery life. Would it be better just to stay on stock instead of Leedroid?
@jrbmed08
TWRP is flashed via fastboot, not ADB.
No need to flash SuperSU via recovery since LeeDroid has root already.
You can flash everything at once.
Sent from my HTC 10
I love using stock android, that's why I also loved using my Nexus 5. I used CyanogenMod with another device many years ago but I am willing to use a custom ROM for my HTC 10, but only after I already know how it feels with stock ROM. So I will stick with it for several weeks and see how it feels, and when I'm farmiliar with it, I will switch to a custom ROM So thanks a lot, you've given me a lot of information I will still need for further experimenting with my phone!
Click to expand...
Click to collapse
When I said stock ROM, i meant stock HTC ROM and it's not stock Android. It's a skinned android called HTC sense. . If you want a stock android to run in your HTC 10 you can flash a AOSP based custom ROM.
Magnum_Enforcer said:
@jrbmed08
TWRP is flashed via fastboot, not ADB.
No need to flash SuperSU via recovery since LeeDroid has root already.
You can flash everything at once.
Sent from my HTC 10
Click to expand...
Click to collapse
Ah yeah, sorry, fastboot is what I meant. Thank you! I haven't had an unlocked bootloader in quite a while (was using TWRP and Sony stock-based ROMs on a locked Z3c), so it will be interesting to flash kernels and such again.
d_Schizzo said:
Thats a thing that iam also interested in. Iam also new to htc.
I think with firmware they mean bootloader. But nobody gave me a good answer till now...
Click to expand...
Click to collapse
not only bootloader, it contains everything. radio.img and any other thing. "low-lewel-stuff", kernel etc, recovery (if stock signed firmware, which is not modded/removed). there are many important things inside.
but firmware is meant for every device the same. it contains everything so that this device can run/work properly.

Ota update for pixel 2 xl with magisk and twrp already installed

I am sure this has been asked and answered 100 times but for the life of me I can't find a definite answer. I have a Pixel 2 XL and it is rooted and I have Magisk and TWRP installed on it. I want to be able to install the OTA for this month, but I do not want to lose anything on the phone. I also would rather not lose Magisk or TWRP. Normally on my android phones I use ROMs and can just update through TWRP, but I want to stay on stock because I don't want to lose Active Edge. So can someone please help me by giving me step by step instructions or point me to instructions that are simple to follow so I can take the OTA?
I really appreciate the help.
I was having the same problem and was helped by some of the members here.. Best way is to flash the firmware after removing the -w from the flash all file. Then flash twrp and magisk.
Ota
Thanks for your help. I will try that.
magicmaker said:
Thanks for your help. I will try that.
Click to expand...
Click to collapse
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:
Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.
rank78 said:
Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.
Click to expand...
Click to collapse
Not that I'm aware of, but maybe some on the horizon...
Badger50 said:
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:
Click to expand...
Click to collapse
Hi, quick question
I am only able to do them steps above if I have done 'fastboot unlock_critical'? I have only done 'fastboot unlock'
Also I would need to boot into TWRP and flash a kernel + magisk to retain root?
You have to issue the "fastboot unlock_critical" command in order for the bootloader to update, since the bootloader is included in both factory images and full OTAs. Speaking of full OTA's, one of our recognized developers, @elliwigy, revealed (thread here) that it is possible to flash a full OTA image through TWRP, which eliminates the need to open the factory image and remove the -w flag from the last line. Flashing the OTA works because TWRP doesn't check signatures like the stock recovery. You will lose both root and TWRP upon reboot however, so you will still need to connect to a PC in order to reinstall TWRP so you can subsequently replace the stock Kernel with the Flash Kernel and then root.
I can verify this works, as I tried it with the May update.

Categories

Resources