Develop Bugs

Should I flash stock ROM, to rectify issue?

My friend wanted to root his phone on the go, so he downloaded King Root and it sort of worked(explained later) but for the app he wanted to use he didn't have proper root access, his SU manager(Some Asian language) gave that app permissions but it won't work because it kept asking for root access. That's when I took over, i downloaded SuperSU and when i went on it i needed it said SU Binary needs to be updated, I went OK and chose normal installation(Didn't have TWRP), it didn't work so i downloaded TWRP Manager and installed in, surprisingly I had root access on it. TWRP was installed successfully, so I went back to install SU Binary through TWRP installation, it keeps failing, IDK why...
So i'm gonna properly root his phone following this video YOUTUBE: /watch?v=FOaRQoJWWDw (I'm new so can't post links)
So since i'm gonna be rooting it again, do I need to flash stock ROM onto his phone?
All answers will be appreciated.

Is the bootloader unlocked?
I only see one recent report of kingroot v4 working on the M8, and it was on KitKat: http://forum.xda-developers.com/htc-one-m8/general/kingroot-rooting-app-t2913123/page4
For the most part, root apps don't work on HTC devices unless you unlock the bootloader. At which point, the root apps are pointless, as you can just install TWRP and flash SuperSU to root, or any other variety of methods.
Also, I don't recommend using the toolkit to root as suggested in the YouTube video. The toolkits are outdated, install obsolete versions of TWRP, which will cause other problems. If you are serious about rooting and modding the phone, the best way to go about that is to read and learn the proper way (not with root apps or toolkits). The "sticky" guide and FAQ threads at the top of this forum section, and top of the "General" M8 forum section are a good place to start.

Root & TWRP for 20E

I spent a bunch of time last night helping my brother root his G3 and install custom recovery and Xposed. I wasted time trying root methods that didn't work because I didn't realize until after the fact that he was running a newer version of Lollipop than most tools were for. We installed Lollipop on his phone last night and rooted afterwards. Apparently the latest version for the Tmobile G3 is D85120E, aka 20E. Most guides and tools are written for 20B.
First, we rooted using this tool: http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
It worked well and was easy (once we found it, that is). After that, we wanted to install TWRP so we could put Xposed on there, but I couldn't find any information about how to do that. I was looking to install aboot and all that other stuff but couldn't find it for this phone/version. Well, it turns out that you don't need any of that stuff because you can install TWRP unmodified. We came to Tmobile from Verizon a month or so ago where we both had G2s, so I was familiar with that process and the hoops needed to jump through on VZW. Turns out that the bootloader for the Tmobile G3 is unlocked, so it's unnecessary. All I did was install TWRP Manager from the play store and installed the latest version of TWRP with it. We got a warning about not being able to write to the sdcard, but I ignored that and it worked fine.
The only issue we had was a constant FC after installing Xposed that LG Smart Cover stopped working. This can be remedied by freezing that with Titanium Backup before installing Xposed. We didn't know that beforehand though, so I used ADB to delete it by deleting the folder at /system/priv-app/LGCover
Also, some weather program FC'd at boot (only once or twice per boot, not constantly like the LGCover program), so we froze that with Titanium. That could be deleted as well, if you prefer or don't have TB.
I hope this helps. It turns out it was easier than expected to root, TWRP and Xpose the latest LP on Tmobile, just had to know that Tmobile had a newer version of LP and that the bootloader is unlocked by default.

Thanks.

A couple of questions about root and OTA

I have been on stock almost all my life, but I once thought what could go wrong with having a rooted phone. I unlocked the bootloader, and tried just booting a custom recovery TWRP, and it worked, although it didn't work before as I heard HTC disabled booting recoveries only. Flashed SuperSU, and VOILA!
I installed a couple of applications I wanted to try, first of them was Titanium Backup, and removed a couple of applications like the default "Internet" browser. I also installed greenify and played with it for while.
Yesterday, I tried installing the latest OTA that fixes the Stagefright exploit, and my phone got soft bricked stuck at the booting screen. Thanks to a Nandroid backup I made with TWRP before rooting - or even after rooting I really can't remember -, which I restored, got the OTA normally but wiped my phone.
Here are my questions:
- Does root only change system files?
- If I removed the default "Internets application that came with the phone after root "uninstalled" it, does this change stock?
- Would greenify with root cause that?
- Is there any official way to restore the stock system files?
I'm just trying to figure out the exact reason here..

@bingorabbit, I can answer 'some' of your questions.
1. Does root only change system files?
I think so, but Someone Else will have to give you a better answer on this one...
2. If I removed the default "Internets application that came with the phone after root "uninstalled" it, does this change stock?
Absolutely - & this particular OTA is really, really picky. If it's not absolutely untouched stock, it all goes wrong & your phone will hang on the boot screen, as both yours & mine did.
3. Would greenify with root cause that?
Whilst I don't know greenify, if it needs root, then yes, absolutely, your 'stock' will no longer be 'stock', & this OTA will all go horribly wrong...
4. Is there any official way to restore the stock system files?
Absolutely yes. Find out your CID, read up on how to deal with an RUU, find & download the right RUU, then walk a little further down the rabbit hole

JustinSB said:
@bingorabbit, I can answer 'some' of your questions.
1. Does root only change system files?
I think so, but Someone Else will have to give you a better answer on this one...
2. If I removed the default "Internets application that came with the phone after root "uninstalled" it, does this change stock?
Absolutely - & this particular OTA is really, really picky. If it's not absolutely untouched stock, it all goes wrong & your phone will hang on the boot screen, as both yours & mine did.
3. Would greenify with root cause that?
Whilst I don't know greenify, if it needs root, then yes, absolutely, your 'stock' will no longer be 'stock', & this OTA will all go horribly wrong...
4. Is there any official way to restore the stock system files?
Absolutely yes. Find out your CID, read up on how to deal with an RUU, find & download the right RUU, then walk a little further down the rabbit hole
Click to expand...
Click to collapse
I really appreciate your answer, regarding my 4th question, My CID is HTC__J15 but I couldn't find an official RUU for it, only found ones for the developer/unlocked edition on HTC's web site http://www.htc.com/us/support/rom-downloads.html#unlocked if so, should I change my CID to match the developer edition or can I just go on with that one?

Hey,
you can find more RUU and nand backups here : http://forum.xda-developers.com/showthread.php?t=2701376

Just got an HTC 10 -systemless everything

Hello everyone,
It's been a while since I've posted here, and I'm very very late to the party since HTC took its sweet time to bring the 10 to my country. Now I've finally got the phone (for entirely free through a corporate discount), and I'd like to do this properly, now. The key thing is that throughout all these steps, I want to maintain functionality of Android Pay. I have a few questions as well.
First, I'd like to S-OFF/unlock the bootloader. I tried entering bootloader mode (volume down + power keys) and noticed that there are a few new modes on this phone compared to my old M8, like Download Mode. What is it?
Next, I'd like to achieve systemless root - I understand this is entirely possible through the latest SuperSU.
Then, I would like systemless Xposed functionality. While searching around, I noticed a few new words thrown around like Magisk. What is it, and how do I get 'systemless Xposed'?
I'd like Adaway on my phone, and I believe it modifies the hosts file once again located in /system. Any way to work around this? Not to mention another couple of ad-blocking Xposed modules.
Next up, I'd like to install the AcoustiX audio mod. Not sure if that doesn't modify system files, once again.
Finally, I hope to remove some of the gapps like Play Music and Play Movies, and install the older HTC bundled apps.
Would any of the above conflict with Android Pay? How do I go about starting, and where do I look for more information for my questions (answers welcome too)?
Thanks in advance.

1. S-off, SunShine app or hardware solution like xtc2clip; why do you need S-off?
2. My SuperSU said systemless when it installed
3. http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
4. Good question; I'm curious also
5. I never messed with audio stuff; sure that's better than what htc provides?
6. Titanium Backup

Okay, so first of all I have a Verizon variant. I unlocked the bootloader/s-off with sunshine. Apparently you don't need to unlock the bootloader when you have s-off. I don't know why or how that works... I unlocked the BL anyways. You'll have to wipe your data if you do that. Just read up on that bit.
After that, you can install TWRP and do a full backup. Make sure you save that somewhere.
If you screw something up I think you can just RUU back to a working state. I think...
As far as Magisk... It's amazing. It's essentially a way for developers to make any flashable zip type mod systemless. To the end user it works similar to Xposed. You flash the framework in recovery (it won't modify the system, that's the whole point) and then you have an app to manage the framework and all your mods.
For example I have a Magisk mod that replaces my HTC dialer and contacts with Google's dialer and contacts (like a nexus). If I want to go back I just uncheck the mod in the app and reboot. HTC apps are back.
If you don't need SuperSU specifically, root can be achieved directly through Magisk with phh's superuser mod for Magisk. So the process would be:
1) download Magisk zip
2) download Magisk manager app
3) download phh's superuser for Magisk (Magisk manager won't function without some type of su)
**All of these can be found through the Magisk XDA thread
4) reboot to recovery and flash Magisk zip THEN flash phh's superuser mod for Magisk
5) reboot to system and install the phh's superuser app from the play store
6)install the Magisk manager apk from earlier
7)from within the Magisk app you can install Xposed as a Magisk mod. It's in the repository. Just install it and reboot. Boom, Xposed. If you want to disable it just uncheck it and reboot. Magisk mods work like Xposed mods so you can disable the entirety of Xposed in the same way you could enable/disable individual Xposed mods before (this is really useful if you have apps like Snapchat that won't work if you have Xposed installed). Another note is that you need to use the material Xposed installer. The old Xposed installer don't support systemless i don't think.
But yeah, good luck. I've found that systemless is a better way to go. For me I just like it because it's more organized. I can disable and enable whatever I want. I will mention though, don't expect Android pay to work. Magisk used to be used to make Android pay work on rooted and Xposed phones. It's moved away from that. It can still be done but it's a constant battle and it's not worth it. I'm not sure if I answered all the questions because I'm on mobile and I can't see the rest of the thread while km typing but yeah.. good luck man. Magisk is a great tool.
Sent from my HTC 10 using XDA Labs

Update: you can use SuperSU with Magisk but be careful with how it installs. I don't know how to force it to install systemlessly.
Sent from my HTC 10 using XDA Labs

elite001mm said:
Apparently you don't need to unlock the bootloader when you have s-off. I don't know why or how that works...
Click to expand...
Click to collapse
S-off unlocks the same partitions as unlocking the bootloader does...and then some (all?).
http://www.htcdev.com/bootloader/about_unlock_process
and
http://www.htcdev.com/bootloader/faq
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. ... Security is left on to protect things like the radio, and SIM lock.
Security is on by default for good reasons. There are partitions such as hboot which controls access to all other partitions which if made fully accessible could compromise security and very possibly allow for irreversible changes that could render your device inoperable.
Click to expand...
Click to collapse

Rolo42 said:
S-off unlocks the same partitions as unlocking the bootloader does...and then some (all?).
Click to expand...
Click to collapse
S-off + BL unlock means you can do whatever the hell you want (hboot, radios, CID, etc). So you need to know what you're doing before you flash something.
A simple bootloader unlock allows you to flash ROMs and kernels and recoveries.
These two things I understand... But...
------------------
What I don't understand is this (there's a post by jcase about it but I can't find it): When sunshine first came out for this phone, everyone was recommending to just perform s-off locked instead of s-off unlocked. I forget what the benefit was (I think it may have been avoiding the encryption corruption thing) but essentially from what I understood there was no downside to the locked bootloader.
Perhaps s-off just overrides everything but I didn't think that's how it worked. I've been away from HTC for a while and I'm not the most knowledgeable person anyways. I know enough not to break my phones but I remember back from the M8 days everyone wanted/needed s-off and the BL unlocked so I just went ahead and did that. I flash firmwares and radios and stuff so I didn't want to run into a roadblock in the future.
Sent from my HTC 10 using XDA Labs

elite001mm said:
S-off + BL unlock means you can do whatever the hell you want (hboot, radios, CID, etc). So you need to know what you're doing before you flash something.
A simple bootloader unlock allows you to flash ROMs and kernels and recoveries.
These two things I understand... But...
------------------
What I don't understand is this (there's a post by jcase about it but I can't find it): When sunshine first came out for this phone, everyone was recommending to just perform s-off locked instead of s-off unlocked. I forget what the benefit was (I think it may have been avoiding the encryption corruption thing) but essentially from what I understood there was no downside to the locked bootloader.
Perhaps s-off just overrides everything but I didn't think that's how it worked. I've been away from HTC for a while and I'm not the most knowledgeable person anyways. I know enough not to break my phones but I remember back from the M8 days everyone wanted/needed s-off and the BL unlocked so I just went ahead and did that. I flash firmwares and radios and stuff so I didn't want to run into a roadblock in the future.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
S-Off Unlocked = more restrictions.
S-Off Locked = less restrictions.
I know it's very backwards, but I believe that's the biggest advantage.
Personally, I changed my splash screen and flashed another hboot without the stupid red text on boot.

What about the newest Android Safety net issues around Unlocked bootloaders. If we setup our phone as S-off Locked, will it pass the safety net test? Ive read that the newest update is starting to fail on phones that aren't even rooted but have unlocked bootloader.
Sent from my HTC One_M8 using Tapatalk

SRSR333 said:
Would any of the above conflict with Android Pay? How do I go about starting, and where do I look for more information for my questions (answers welcome too)?
Click to expand...
Click to collapse
I've got a brand new unlocked HTC 10 with unlocked bootloader, TWRP, S-OFF, root (through flashing the latest SuperSU), and xposed also. Android Pay no worky :/

is my phone really rooted?

I used to be more active on these forums before I got my oneplus 5T and one of the biggest reasons was I wanted a clean fast OS without all the bloatware that many other manufacturers put on their phones. I tried a search but I did not find what I was looking for, so I apologize in advance if this is already covered in another thread.
Anyway, I picked up a 5T about a year ago while visiting family in Europe. (I'm the 2nd owner to the phone) I never bothered to install TWRP or anything else bcs the phone was running really well with stock. All OTA updates have been installing whenever they were released.
Now to my question. While trying to install workspace one app from playstore (my company requires it) the app won't install bcs it claims my phone is rooted. That is the only app that I have ever had any issues with.
I ran root check witch states "sorry! Root access is not properly installed on this device"
How do I unroot my phone if it's really rooted? Or lock the bootloader? maybe that's the same? TWRP is not installed, when I boot into recovery I get into oneplus stock recovery software.

Hi, unfortunately I can't tell you right off if your phone is rooted. If root checker is saying no, then maybe you aren't, but still check if you have magisk or some other root solution app installed. When you got it from someone, they also could have flashed ROMs etc and when they returned it to stock for resale, they night have missed something like relocking bootloader, even if they did re install stock recovery. If I were in your shoes though, I would reboot to bootloader and check if it's unlocked or not. If it is, it's a simple "fastboot oem lock" from terminal. If that's not the case or solution, I dunno what to say. One thing that I would do if I were desparate is to try to take a backup of all the music/pics/texts/whatever other essential bits of data. Then I would reinstall stock recovery, as well as the latest official (not beta) Oxygen OS from oneplus's page. You can find it under the support tab and then software upgrade, then choose the device. Not only that but maybe completely nuke it, as in format, wipe, etc. And lock the bootloader and also let it get encrypted and stuff.. in other words, restore to as stock as possible. Then once you are done you can test. If this fails and bricks, there's a unbrick guide somewhere here for our phone, and also the backup is there for you. If you successfully restore to stock and this does not work, then maybe it is just the app that has a problem with not super stock Android (OOS). I must warn you that this process is risky and I am in no way gonna be responsible for lost data, because I did say make a backup and also it is up to you to do this. I hope this helps a bit, and if you aren't super familiar with the process it may take a while, around an hour if you do not run into any hitches and your download speed is good enough.