Should I flash stock ROM, to rectify issue? - One (M8) Q&A, Help & Troubleshooting

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.

Related

How do you root properly and other questions.

I am coming from a Samsung Moment with root, custom recovery, etc and I never had this many problems, what am I doing wrong or not understanding?
1. Why do I need to download or have an adb shell on my computer if I can install connectbot and do commands through the phone?
2.What is the proper method for rooting? My understanding is basically this:
A: Get Phone
B: Do not do the OTA update.
C: Download Toast's root (pc36img.zip)
D: Flash pc36img.zip
E: Done?
3. I can't get wireless tethering working using this method, and I have to download unrevoked's root to get it working.
But then again, is that even a root, or is it just for SU access?
4. How do I get the bug fixes from (1.32.651.6), and still maintain root? I downloaded the sprint ruu_1.32.651.6.exe provided in the forums and enjoyed having my phone not error and fc every 10 minutes, now I hear if I did that I just closed off toast's rooting.
5. Is there like an easy step by step instruction on how to make a custom recovery, nandroid backup, how to check for root, etc?
6. Did I kill my chances of root by installing and using ruu_1.32.651.6.exe?
Great first post.
All is explained in the dev forum.
There is no easy step by step method that I can find, sorry. A lot of threads and instructions assume that you have been using and flashing htc devices for a while. I'm coming from the moment and it's completely different.
I agree, it is confusing. I used toasts method and thought my phone was rooted until I tried Titanium Backup and it told me it couldn't get to root.
I figured I'd just wait til the rooting process is more stable. Sorry, I know this doesn't help

[Q] SuperSU says there is no SU binary and it can't install it, wat do?

Hello everyone, first time poster. In need of dire help.
So I got an unlocked phone.
Tried to use the method on the galaxynote2 website ( you can find it if you google "galaxynote2root easiest method" )
However Now SuperSU is telling me "there is no SU binary installed, and SUPERSU cannot install it. There is a problem!"
I tried updating SuperSU and downloading a putting in manually a newer version.
I have no idea what's going on in my phone since root checker is telling me I don't have root.
What do I do?
Hell, the only reason I rooted it is to unroot it because the previous root made my phone act strange.
I really would like to give this phone in for warranty.
mugoftea said:
Hello everyone, first time poster. In need of dire help.
So I got an unlocked phone.
Tried to use the method on the galaxynote2 website ( you can find it if you google "galaxynote2root easiest method" )
However Now SuperSU is telling me "there is no SU binary installed, and SUPERSU cannot install it. There is a problem!"
I tried updating SuperSU and downloading a putting in manually a newer version.
I have no idea what's going on in my phone since root checker is telling me I don't have root.
What do I do?
Hell, the only reason I rooted it is to unroot it because the previous root made my phone act strange.
I really would like to give this phone in for warranty.
Click to expand...
Click to collapse
Also it's not like I used any ol' root. This individual has a huge youtube channel dedicated to the note.
Also I forgot to mention that when I finished rooting, knox did say it did allow some sort of permissions with super su or something along those lines.

[Q] Used Odin3 to root, cant open SuperSU want to go back safely to dry again

Hi,
This is a great site.
I am doing this cause I deleted some photos by accident and want to use one single program that needs the phone to be rooted. Because there is no mass storage connectivity you know how it goes.
I used Odin3 to install "CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5" to my Samsung Galaxy Note 2 with Android 4.3.
Odin says "PASS!". When I try to start the SuperSU (version 2.01, was installed by Odin and CANT BE UPDATED in the play store, not even removed only opened form play store. This was the most common fix that people are giving to this situation, but it does not work for me because there is no update possibility) Because KNOX says unauthorized attempt to access not accessible areas. SuperSU does not prompt the possibility to terminate KNOX like some people are advising to do, even tough the 2.01 version of SuperSU should be able to do this. Even the RootChecker says that my phone is not rooted.
So my assumption is that the Root has not worked on my phone even tough Odin says so. So I want to try some other approach to root this phone. I just would like to know should I do some check for what Odin HAS changed in my phone and to try to change them back so I can for example try Kingos root safely.
So the questions are:
Does some one have a possible fix to my problem without me having to re root?
How can and what should I check before trying another root?
If I have to go back with stuff that Odin did, without it doing the root properly how can I do that?
And one a bit different question:
If I factory reset my phone it will install the 4.1 I thin on it, has no KNOX, will it write that on the part that is empty and might include that data of my deleted pictures or does it write it on the area that has the previous data of the Android system?
Thanks for advance if there is any advises.
Partial answer:
I followed basicly this instruction,
http://forum.xda-developers.com/showthread.php?t=2538991
just needed to find the correct TWRP for my phone and used the older 1.65 SuperSU, there is something wrong with the 2.01 and it compatibility with my phone.
This video also helped cause the information was similar to the one in the link.
https://www.youtube.com/watch?v=ZQAkLgXjnCo
Installed the DiskDigger and got most of the photos, so now I need to find out how to convert it from root version to version so I can upgrade my phone.
Everything is really easy with Odin. If the packet that I installed with it first that does't istall the custom recovery system would have had some other KNOX combatible version of SuperSU I think it would have worked. No I just needed to use the KNOX remover to remove it from my phone.
Thanks for the form all the answers where her and it just took me some time.

Root access for GT-I9195I?

Hi, I have a brand new, stock, unlocked, international version GT-I9195I, which I updated to Android 4.4.4 before attempting to root. I attempted to follow the instructions given here for root access. I didn't realize until just now that these instructions were for a slightly different model, the GT-I9195, not the GT-I9195I.
Two questions: first, have I done any harm by attempting to flash the GT-I9195 recovery onto my GT-I9195I? (It still boots and appears to work normally.) Second, where are the instructions to get root access for this particular model (Baseband version I9195IXXU1AOB1)? I found a thread here for installing TWRP but it doesn't seem to mention how to get root...
Use kingroot for rooting...just install the app and press root
Sorry for taking so long to reply. Thanks for the advice! Kingroot was successful on the second attempt at obtaining root access.
However, I do have a follow-up question. Can I install a superuser app like SuperSU, then uninstall kingroot, and still retain root access? Kingroot's Purify feature shut down my alarm clock app and some others I want to run at startup, and toggling apps in the "Auto-start" setting of kingroot seems to have no effect. I uninstalled Purify but it still interferes.
Yes, you need to use Super Sume: https://play.google.com/store/apps/details?id=darkslide.com.supersumepro

M8s on Marshmallow - systemless root - how?

Hi,
I recently had to return my phone back to stock because of a warranty issue. (battery dying between 25% and 40%)
So chances are high that I will get the phone back with Marshmallow instead of Lollipop.
is there a guide or can anyone give some pointers how to root this device? After a bit of reading I still have a few specific questions, so maybe someone here can help.
A) What TWRP version will I need for the M8s on Marsmallow?
B) Will Magisk systemless root work on this device?
C) If the rooting has succeeded and I remove some bloatware apps from /system/vendor and /privapp and such. Will this trip the Google safety net? Or is safety net not yet applied to our M8s devices?
Thanks!
I don't personally have the M8s version specifically. But as the device forum sections for all the M8 versions in general are becoming pretty quiet; I'll try to help you to the best of my knowledge.
A) The TWRP recovery posted in this (M8s) forum section should work fine on Marshmallow. Looks like it's only updated to 2.8.6
B) Should work, yes. I would suggest the current stable Magisk version, which is 14.0
Backup your stock (unrooted) ROM before trying to root (as you always should - this is best practice and just good common sense). Then if anything goes wrong, you can easily restore to stock.
C) Not sure. But I can tell you on my current device (OnePlus 3T) that removing system (bloat) apps does not trip safety net.
Hi @redpoint73,
Thanks. That takes away some worries and gives me some confidence for giving it a third shot . Nandroid's don't work on the M8s unfortunately, I've tried this once since I botched something up during my first root attempt, put back the Nandroid and my Bluetooth was dead. (and probably more, but I didn't investigate it further back then.)
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Thanks so far and I'll report back my results in this topic. Now I first have to wait to see if they give me my warranty, since the bootloader said relocked and the firm I had to send it to is notorious for blaming factory faults on rooting of the phone. Fingers crossed!
Thijs_Rallye said:
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Click to expand...
Click to collapse
Should be the same, yes.
The reason for this, is that the system is write-protected, even with root. On the M8, there is a kernel mod which disables the write protection (allows you to modify system while booted to OS), but I don't know if there is such a mod for the M8s. But if you were able to do it in TWRP, the same should apply on Marshmallow.
So I finally got my phone back, or well, to be accurate, I got another phone (albeit another M8s) back under warranty. I guess they f'd it up during repairs or something. And as expected my phone was upgraded to Marshmallow.
Anyhow, the more I read about Magisk and systemless rooting the more lost I seem to get lost. Is there somewhere a step by step guide for obtaining root on this phone?
Let me recap from what I've understood so far (SOURCE 1, SOURCE 2 and SOURCE 3)
1) Backup my boot partition, I am still searching how to accomplish this without rooting the phone first. Booting to TWRP without installing resulted in mangling some data in the boot partition, so unfortunately that is not an option. (blanks the OS version)
2) Boot to TWRP and flash the Magisk zip file. There should be an option somewhere in TWRP to enable systemless rooting.
3) ?
So if anyone knows if I am on the right (or wrong) track please let me know .
Thijs
Edit: I can't seem to get the phone boot TWRP for some reason (from my harddrive htc_fastboot boot twrp.img). This used to be possible on my old M8s which I had send in for repairs. Do I really have to flash it because I have no way of backing up the old original recovery .
Okay, since it is kinda dead in here let me bump this for anyone in the same situation. I've managed to install Magisk successfully. The steps involved
1) unlock bootloader
2) flash twrp (htc_fastboot flash recovery twrp.img) I've used the latest version from Captain Throwback which I've found in the OP of the Void_Zero Lineage OS thread.
3) boot the phone and copy magisk systemless root zip and the apk file to your internal storage Grab the uninstaller as well in the topic.
4) reboot to recovery (adb reboot bootloader)
5) flash the zip from within recovery
6) reboot the phone and install the Magisk app.
7) done
Use this guide on your own risk. It worked flawlessly for me but no guarantees .

Categories

Resources