Related
Sorry to post this as my first thread here, but I'm running into a problem that I can't seem to get past. Trying to root an unlocked T-Mo T989. I followed the instructions in the developer's thread on how to do it, and I got the CWM installed properly and did a NANDROID backup. The problem I'm having is with any user of the SU binary and SUPERUSER.APK. I first tried to install the Superuser-3.0.7-efgh-signed.zip, but got an error that it was a bad zip, installation aborted. It's given me that error regardless of which downloaded version of that file I used, and I've D/L'd it from several different sites. So, I tried the instructions to use the deodexed ROM from this site. I re-CWM'd the phone, and tried to load SGH-T989-Deodexed-Root-Busybox-Superuser-by-teshxx-bubby323.zip from my SD card and I got the same error- bad zip, installation aborted. Can't be that many bad zips out there, and more to the point, I can unzip these files fine manually and see the data, so it's obviously something I'm doing.
Interestingly, SuperUser did get installed on the phone, but I don't seem to have SU rights to anything except that which I've installed. I'm trying to remove all the bloatware, but don't have rights to it.
I've had to rebuild all my personal data because bubby323's instructions here had me clean the partitions. I don't want to do that again except for when the phone is properly rooted, so I'm hoping that someone here will be kind enough to tell me how I'm screwing it up. Thanks,
..Joe
this not a rooting question, so don't hijack an unrelated topic for your troubles
the problem you are having is installing SU
just boot into CWR which you already have insalled, then use CWR to Flash the SU zip file
or if that is too complicated use then use the superoneclick method which will also install SU for you the easy way
Umm, sorry, but did you read the post? I did boot into CWR, and tried to install the SU zip, and that's where I get the error that it's a bad zip, installation aborted. Same thing for the one-click version by bubby. That's why I posted it in that thread: I did not try to hijack anything. That was the rooting and SU thread, hence the reason I posted it there.
For all I know it's a problem with CWR.
Geez, talk about jumping allover someone asking for help...
..Joe
AllGamer said:
or if that is too complicated use then use the superoneclick method which will also install SU for you the easy way
Click to expand...
Click to collapse
Agreed.
Use superoneclick if you can't install superuser via cwm. may be best to uninstall superuser if its on your phone but not working.
Sent from my SGH-T989 using XDA App
Actually this is quite an easy fix....
In CWM, run the install again. Hell, run it a couple times, until it says successful. I've done this on 5 sgsii's so far, and 3 of them had this problem. My best guess is it isn't mounting the partitions correctly, (which I am unable to verify. The installer script it right, and even if i mount the system partition manually before install it still failed.)
So, easy answer:
Boot to cwm.
Run the installer for su
if it fails, run it again without rebooting
if it fails, once again run it.....
eventually it will work, then reboot, and your rooted. (I'd also suggest after this is done to go into the superuser program settings, scroll to the bottom and update the su binary as well, but this isn't really required.)
Good luck.
you can also use the Fix Permission option in CWR
i know i came across that problem before, and it was able to install after i Fixed the permissions
Well, obviously I'm still doing something wrong. I restored the phone to stock using the CWN Recovery of the NANDROID backup I did when first attempting this. I then started over:
Up and down held down while inserting the USB cable.
From ODIN I select the CMW tar in the PDA, and that installs and reboots the phone.
Shut down phone and re-start with up and down keys depressed, USB cable out
Select Install zip from SD card
Select the Superuser-3.0.7-efgh-signed.zip (or the deodex, doesn't matter)
down 7 times to select
then I get this error:
Selecting SU Superuser-3.0.7-efgh-signed.zip...
Finding update package...
Opening update package...
E:can't open /sdcard/Superuser-3.0.7-efgh-signed.zip
(bad)
Installation aborted.
I get that no matter how many times I've tried to install it, and even after fixing permission, and even if I try to install it off the internal USB storage.
Any one have any ideas?
Thanks,
..Joe
Correction...
It doesn't like the SD card. I installed the deodex file from the internal USB storage, and this time, it finally took! Thanks to everyone for all the help.
..Joe
hi i have the exact same problem. Can you please explain what is a deodex file and how you installed it? thanks
i got the same error when rooting, however upon rebooting and going into my apps superuser had installed and was working even after receiving the error
sorry but i'm a bit confused here..my apps? what's the exact path to that?
I basically get that error, leaving me without root privilages, the only thing accomblished is the s-off. But without root access, i cant do anything.
Also, after that, my phone's reception is gone...
kostistheo said:
sorry but i'm a bit confused here..my apps? what's the exact path to that?
I basically get that error, leaving me without root privilages, the only thing accomblished is the s-off. But without root access, i cant do anything.
Also, after that, my phone's reception is gone...
Click to expand...
Click to collapse
the exact path to apps would be phone reboots, then upon reboot pay close attention here... upon reboot i click my app drawer, BAMMM theres my apps.. now i cycle thru until i get to the S section and look for super user...lol
---------- Post added at 03:01 AM ---------- Previous post was at 02:59 AM ----------
do this ... GOOGLE "HOW TO ROOT THE T989" there will be youtube video with the step by step hands on walk thru...watch it
thanks for the unnecessary sarcastic american comment...
thanks for the seemingly racist comment, ignorance must be a way of life for some.
kostistheo said:
sorry but i'm a bit confused here..my apps? what's the exact path to that?
I basically get that error, leaving me without root privilages, the only thing accomblished is the s-off. But without root access, i cant do anything.
Also, after that, my phone's reception is gone...
Click to expand...
Click to collapse
S-off? Our phone doesnt come with a locked boot loader... We arent using an htc device. never had s-on to begin with lol.
Sent from my SGH-T989 using XDA App
joegerardi said:
Sorry to post this as my first thread here, but I'm running into a problem that I can't seem to get past. Trying to root an unlocked T-Mo T989. I followed the instructions in the developer's thread on how to do it, and I got the CWM installed properly and did a NANDROID backup. The problem I'm having is with any user of the SU binary and SUPERUSER.APK. I first tried to install the Superuser-3.0.7-efgh-signed.zip, but got an error that it was a bad zip, installation aborted. It's given me that error regardless of which downloaded version of that file I used, and I've D/L'd it from several different sites. So, I tried the instructions to use the deodexed ROM from this site. I re-CWM'd the phone, and tried to load SGH-T989-Deodexed-Root-Busybox-Superuser-by-teshxx-bubby323.zip from my SD card and I got the same error- bad zip, installation aborted. Can't be that many bad zips out there, and more to the point, I can unzip these files fine manually and see the data, so it's obviously something I'm doing.
Interestingly, SuperUser did get installed on the phone, but I don't seem to have SU rights to anything except that which I've installed. I'm trying to remove all the bloatware, but don't have rights to it.
I've had to rebuild all my personal data because bubby323's instructions here had me clean the partitions. I don't want to do that again except for when the phone is properly rooted, so I'm hoping that someone here will be kind enough to tell me how I'm screwing it up. Thanks,
..Joe
Click to expand...
Click to collapse
I had this problem too, just do this:
Before attempting to install the SU zip again, wipe Dalvik cache
(under "advanced" in CWM recovery)
Then install the SU zip
Works everytime..
i tried what you post but still not rooted, I got super user but its still not roote
ingenious247 said:
I had this problem too, just do this:
Before attempting to install the SU zip again, wipe Dalvik cache
(under "advanced" in CWM recovery)
Then install the SU zip
Works everytime..
Click to expand...
Click to collapse
I tried that but my phone still not rooted, I've tried various methods and it still doesn't work I got the superuser app but still not root
hello
I am courious
how many of us are rooted already ?
what method did you use to root your phone ?
nowy57 said:
hello
I am courious
how many of us are rooted already ?
what method did you use to root your phone ?
Click to expand...
Click to collapse
Rooted since long ago... On every build... All the time. :good:
If you're still having trouble with rooting CM or Omni, try the following.
You should be able to flash the SuperSU zip in TWRP after clearing Dalvik and Cache. If that fails, try below.
If you have SuperSU installed already and are failing to get root, you may have to remove your current SuperSU version. Don't just uninstall SuperSU! Go into SuperSU and go to "Settings". Scroll way down to "Full Unroot". Let that run as it needs to, then reboot into TWRP and wipe Cache and Dalvik. Then flash the SuperSU zip. Reboot to system. Test root.
sorry mate
it doesnt work to me
I have tried two times
as you wrote
Harfainx said:
Rooted since long ago... On every build... All the time. :good:
If you're still having trouble with rooting CM or Omni, try the following.
You should be able to flash the SuperSU zip in TWRP after clearing Dalvik and Cache. If that fails, try below.
If you have SuperSU installed already and are failing to get root, you may have to remove your current SuperSU version. Don't just uninstall SuperSU! Go into SuperSU and go to "Settings". Scroll way down to "Full Unroot". Let that run as it needs to, then reboot into TWRP and wipe Cache and Dalvik. Then flash the SuperSU zip. Reboot to system. Test root.
Click to expand...
Click to collapse
I have the same issue too. SuperSU installed 3 times. Did the full unroot like you said and reran the install after wiping both the cache. Still no root access.
I think that magic which found us oppo+CM team is missunderstand couse when I first time heard about cooperation this two companies I was so much happy .
by now when I have it I know that maybe couple of hundred is sold this phones and nobody cares about support it .
1.ROM straight from CM/OPPO site doesnt install propely via TWRP( without ingeration for user-script)
2.no root acces yet
this is sad true .
I v got note3 and I see more future with this phone
AOSP/CM is on a way - a lot of android entusiasts is working for free of charge about better and better ROMs
I am dissapointed - no offens to anybody
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
ChodTheWacko said:
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
Click to expand...
Click to collapse
it is not installed under CM ROM
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
ChodTheWacko said:
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
Click to expand...
Click to collapse
The exploit method was apparently patched in the official CM release. That exploit doesn't work.
Harfainx said:
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
i am really confused couse I am pretty sure I am doing good as you said but no succes .
Harfainx said:
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
If TWRP doesn't work properly how did you root? With the stock recovery?
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
nowy57 said:
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
Click to expand...
Click to collapse
You can indeed install straight from stock recovery. I did it last night. You have to use the official rom for the n1. Works nicely. I also had root working on cm. I flashed cm from stock recovery then used fastboot to install twrp. After twrp i flashed supersu zip. After i did the fix root or remove or whatever it is in the ap, reinstalled and tested it in titanium. Said i did have access but then went back to coloros to try and fix my mediascanner issue.
Sent from my N1 using XDA Premium 4 mobile app
nowy57 said:
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
Click to expand...
Click to collapse
I mean straight flash CM on the stock recovery, not on TWRP. You would have to be on the stock recovery for it to work straight from the CM download. On the stock recovery though, you will not be able to flash SuperSU on it. I do not believe that Omni can be flashed from there either, but I could be wrong (I haven't tried it).
There's a thread in the dev section that has the stock recovery hosted there. You can always fastboot flash back to that at any time.
Okay, I decided to install Cyanogenmod for the heck of it.
I already had TWRP 2.6.3.1 installed,
I downloaded and modified cm-10.2-WPPH50O-n1-signed.zip as per this page's instructions:
http://forum.xda-developers.com/showthread.php?t=2553165
I also downloaded supersu (current version is 1.86).
I entered TWRP and installed it, following that page's instructions.
After the install, I selected 'reboot'.
When I selected 'reboot', It prompted me with:
install superSU now? this will root your device.
I said no, and then rebooted back into TWRP.
Now back in TWRP, I install SUPERSU.
Now reboot again.
Now in CM.
Now run SuperSU, select 'settings', and unclick 'Respect CM root settings".
Now root works for me.
Two notes:
1) Respect CM root settings implies that in 'developer settings', there is some sort of "allow root" checkbox. I can't find it.
2) If, after the CM install, you answer 'install SuperSU' with YES", then it installs SuperSU, and reboots.
When you go back in, and run SuperSU, it says "gee, you aren't rooted, install SuperSU?"
If you answer THAT with yes, then it downloads some version of SuperSU, reboots into twrp, and installs it.
So it's kinda pointless answering YES in the first place, imho.
Are you serious right now?! I was worried unchecking Respect CM root setting would mess things up. But now I have root access. OMG... I unchecked it and it works! ^_^
57 43235953
ChodTheWacko said:
...
Two notes:
1) Respect CM root settings implies that in 'developer settings', there is some sort of "allow root" checkbox. I can't find it.
...
Click to expand...
Click to collapse
There is actually a #Superuser control panel just below "{} Developer option" that has lots of useful settings for root user control.
I haven't rooted yet but it seems like handy stuff for supersu to respect? Once you go into #Superuser use the menu button and you can add a profile etc it seems.
It's all kind of oddly done since adding that control panel after activating developer mode doesn't actually add an "su" binary.
hammerandtongs said:
There is actually a #Superuser control panel just below "{} Developer option" that has lots of useful settings for root user control.
I haven't rooted yet but it seems like handy stuff for supersu to respect? Once you go into #Superuser use the menu button and you can add a profile etc it seems.
It's all kind of oddly done since adding that control panel after activating developer mode doesn't actually add an "su" binary.
Click to expand...
Click to collapse
On what version of CM? or did you mean OMNI?
Under 'System' I only have:
Date & time
Accessibility
Developer options
Performance
About phone
Unless you meant 'in {} Developer' but I don't see anything in there either.
- Frank
ChodTheWacko said:
On what version of CM? or did you mean OMNI?
Under 'System' I only have:
Date & time
Accessibility
Developer options
Performance
About phone
Unless you meant 'in {} Developer' but I don't see anything in there either.
- Frank
Click to expand...
Click to collapse
WOW...so it literally disappeared as I was composing this message.
Cyanogenmod "signed" installed with the oppo bootloader (not rooted as supersu doesn't install successfully through bootloader etc).
Some kind of UI refresh after I changed some home screen settings?
It was persistent through 5-10x reboots and now is gone.
Obviously a glitch since I don't have su and I'm not truly rooted but it WAS there :\
I'd say its a bug to be filed if you are rooted and it's not available.
Hi guys, please direct me to the correct place if this is not it. I am currently running revolt and I want to flash a new ROM. I had a status 7 error, which I have had before and I fixed that by updating CWM. But here is where I get hung up. I get an error that I thought was related to ROM manager not having the correct permissions. I went to update my supersu and give it the correct permissions, but I decided I wanted to change to Superuser and uninstalled supersu. I have now having an error where I can not download anything from he play store because my memory is full. When I check my memory it does not add up. I have 12gb of space and a I am using roughly 4 gb of that. If anyone knows of a way that I can fix the issue so that I can update my CWM and flash a new ROM it will be greatly appreciated!
Did you have the same error before changing your root managing app? You went from superuser to supersu
Sent from my ST18i
Guynan said:
Did you have the same error before changing your root managing app? You went from superuser to supersu
Sent from my ST18i
Click to expand...
Click to collapse
I tried to change from supersu to superuser and I can't download superuser because it says my memory is full.
eviltweak said:
I tried to change from supersu to superuser and I can't download superuser because it says my memory is full.
Click to expand...
Click to collapse
That is really confusing. When it says wrong permissions, it won't mean the root managing app has the wrong permissions, it means that the system has wrong permissions somewhere. This cannot be fixed through Supersu or Superuser. If you can still go into recovery, go into advanced, and then 'fix permissions' and that should fix issues if that is what it pertains to.
Because Android it is based off a Linux kernel, it is very picky with the permissions you give it. Too little and it doesn't work. Too much, and it doesn't work.
Let me know how you go.
I don't think I explained this very well in my first post. My issue lies when I try to flash the new version of cwm. I get this screen.
I went into recovery and advanced and I don't have an option that is fix permissions?
So you do have a current working recovery? Okay then advanced>Fix Permissions, at the bottom. If it isn't there, it might be the stock recovery included by Samsung. What is wrong with your current recovery? I can't seem to figure it out sorry.
Guynan said:
So you do have a current working recovery? Okay then advanced>Fix Permissions, at the bottom. If it isn't there, it might be the stock recovery included by Samsung. What is wrong with your current recovery? I can't seem to figure it out sorry.
Click to expand...
Click to collapse
I am running CMW 6.0.3.7. When I go to advanced all that I see is Reboot recovery, Reboot to bootloader, Power Off, Wipe Dalvik Cache, Report Error, Key Test, Show Log, *******Go back*******.
My recovery works, its just not up to date so when I go to flash a new ROM I get a status 7 error. I have had this issue before and I fixed it by updating my recovery. BUT this time when I go to flash an updated version of CWM I get the screen that I posted above.
the status seven error is usually to do with the updater-script. So make sure the ROM you want to flash is for your device, if it isn't (which may be why you have run into issues) don't flash it. But if you are sure it is, go into the ROM, META-INF>Android>Google>Updater-script (the android and google may be the other way round, it won't take you long to find it) And then open the updater script in a text editing program and remove the first few lines of stuff. It will have the words "assert" "getprop" and looks different to the rest, so just delete that section, and rezip if you have to, and try reflashing. But if that doesn't work and the issues are becoming intrusive, a full reset might be in order.
I have been trying to Google this but am a little confused on all the steps I need to (and don't need to) take at this point, especially since I am a little behind. So I wanted to ask for help on forums, if anyone is willing to give some advice on this.
First of all, I have a Sprint version of the HTC 10. I don't know if that matters or not (I recall back when I was trying to figure out the original Magisk, someone mentioned that a Sprint model HTC 10 could be an issue, but I am not sure why).
Also, so far all I have done in terms of rooting it is:
- Use the HTC Bootloader unlock
- Install TWRP Touch Recovery with the option of not modifying the system partition (From what I understand, this would cause it to be a temporary install that would go away after a reboot, but it seems to have stayed installed)
- Perform backups with TWRP
- Flash the SuperSU zip with TWRP
And... that's it, still on stock ROM and everything, didn't install anything else that depends on root like Xposed or whatever (That wasn't automatically installed by TWRP or SuperSU or something was it?). I am pretty sure root access is working because two of my apps (Titanium Backup and Chase) tried to request it, and I can see those requests in SuperSU, but other apps don't seem to act like I am rooted. Namely, Google Pay.
From what I understand, Google Pay is not supposed to work if you have root due to that SafetyNet API. However, when I start Google Pay, I see no error message or anything, it seems to work. Granted, I haven't added a credit card to it yet, does the error only happen when you try to make a payment or try to add a card or something? Or should I see it on starting the app? Did I somehow inadvertently setup my phone in a way where root is not being detected?
I also seem to be getting conflicting information on how I should install everything. The guide I followed for rooting my phone said to install SuperSU by flashing the zip, not through the app store.... but the guide for Magisk seems to claim to uninstall SuperSU and install phh's Superuser from the app store. Is there a reason I should do this one way, or another?
Also, all the guides for Magisk say that it is heavily recommended that I reset my phone to stock system, and I really can't reset the data on my phone. Can it be done without erasing anything? I am unclear what resetting to "stock system" would do exactly.
It sounds a little too simple: Uninstall SuperSU and install Superuser (though the method I should do it through is not clear), flash Magisk through TWRP, and then flash AutoMagisk through TWRP. I feel like I am definitely forgetting steps. That, and if somehow I am getting past SafetyNet with Android Pay I don't want to mess with something that might break however I managed to pull it off.
Another worry is breaking my cellular radio. I remember that SuperSU for a while did something (or rather, didn't do something with encryption that the HTC 10 needed which resulted in the cellular radio not working once it was flashed, and that for a while there was a special fork of SuperSU for HTC 10 phones to fix this until the main SuperSU app implemented it. I have no idea if Superuser or Magisk also could cause this issue. Does anyone have any idea?
Oh, and finally, my phone is complaining that an update is available, has been complaining for a while, update 1.80.651.6. Can I safely install this OTA update while rooted? Will it remove or break root if I do? And would it be recommended to install it now before I mess with Superuser and Magisk, or after?
Ummm, anyone?
Cyber Akuma said:
Ummm, anyone?
Click to expand...
Click to collapse
Its all there in the op of the magisk thread.
I read that thread, as I said, I still don't understand some parts.
Cyber Akuma said:
Ummm, anyone?
Click to expand...
Click to collapse
Have you tried posting in the dedicated Magisk thread?
Try installing leedroid nightly latest it has magisk available when you install rom
i did not try it, till now. I read something a few weeks ago.
But in the magisk thread the op said something that SuperSu is not the supported SU method? only phh superuser?!
I would ask the question in magisk thread.
Firstly: You ask a lot of semi-related questions, a lot of these are already answered, out there, in the appropriate threads.
Let me systematically try to answer your questions
What you have done:
- Use the HTC Bootloader unlock
- Install TWRP Touch Recovery with the option of not modifying the system partition (From what I understand, this would cause it to be a temporary install that would go away after a reboot, but it seems to have stayed installed)
- Perform backups with TWRP
- Flash the SuperSU zip with TWRP
Click to expand...
Click to collapse
When you install the TWRP recovery, you actually install it to the recovery partition of your device.
the option the "not modify system" has nothing to do with installing TWRP, but with installing other mods/roms
It's there so you can make a backup without modifying the system partition, that way you can go back to a working isntall if you do happen to mess something up.
And... that's it, still on stock ROM and everything, didn't install anything else that depends on root like Xposed or whatever (That wasn't automatically installed by TWRP or SuperSU or something was it?). I am pretty sure root access is working because two of my apps (Titanium Backup and Chase) tried to request it, and I can see those requests in SuperSU, but other apps don't seem to act like I am rooted. Namely, Google Pay.
From what I understand, Google Pay is not supposed to work if you have root due to that SafetyNet API. However, when I start Google Pay, I see no error message or anything, it seems to work. Granted, I haven't added a credit card to it yet, does the error only happen when you try to make a payment or try to add a card or something? Or should I see it on starting the app? Did I somehow inadvertently setup my phone in a way where root is not being detected?
Click to expand...
Click to collapse
SuperSu *should* break safetney and thus should break android pay, as Chainfire says in the following thread: http://forum.xda-developers.com/apps/supersu/supersu-safetynet-android-pay-t3298115
"In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU."
I also seem to be getting conflicting information on how I should install everything. The guide I followed for rooting my phone said to install SuperSU by flashing the zip, not through the app store.... but the guide for Magisk seems to claim to uninstall SuperSU and install phh's Superuser from the app store. Is there a reason I should do this one way, or another?
Click to expand...
Click to collapse
Installing SuperSu trough TWRP installs the dependencies (the actual root) and the application (which just manages the root access), the magisk guide tells you to first flash the preferred root (SuperSu or SuperUser phh's) trough recovery and then install the correct manager app trough the playstore.
This is probably so John doesn't have to keep on updating his zips everytime the makers of the manager apps update their apps, users can just download the latest version.
Also, all the guides for Magisk say that it is heavily recommended that I reset my phone to stock system, and I really can't reset the data on my phone. Can it be done without erasing anything? I am unclear what resetting to "stock system" would do exactly.
Click to expand...
Click to collapse
Resetting to stock is important for 2 reasons:
1. it cleans out all "old" root apps and methods
2. it cleans up a patched boot.img (kernel)
Then again, if you haven't flashed any other mods, you would probably be safe to install magisk on your rom.
One important thing everyone will always tell you: make a backup! (make a nandroid)
To do this, boot to TWRP and choose "backup" make sure to select: Boot, System and Data
It sounds a little too simple: Uninstall SuperSU and install Superuser (though the method I should do it through is not clear), flash Magisk through TWRP, and then flash AutoMagisk through TWRP. I feel like I am definitely forgetting steps. That, and if somehow I am getting past SafetyNet with Android Pay I don't want to mess with something that might break however I managed to pull it off.
Click to expand...
Click to collapse
The proper steps would be:
0. Make a nandroid backup in TWRP!!
1. Open SuperSU and choose to completly unroot (somewhere near the bottom of the settings menu)
2. Boot to TWRP and flash Magisk
3. Flash the phhh superuser zip file (from the magisk thread)
4. boot android and install the superuser app from the playstore
5. boot twrp and install AutoMagisk
That's it!
Another worry is breaking my cellular radio. I remember that SuperSU for a while did something (or rather, didn't do something with encryption that the HTC 10 needed which resulted in the cellular radio not working once it was flashed, and that for a while there was a special fork of SuperSU for HTC 10 phones to fix this until the main SuperSU app implemented it. I have no idea if Superuser or Magisk also could cause this issue. Does anyone have any idea?
Click to expand...
Click to collapse
Radio shouldn't be broken unless you flash very old zips, don't worry about it
Oh, and finally, my phone is complaining that an update is available, has been complaining for a while, update 1.80.651.6. Can I safely install this OTA update while rooted? Will it remove or break root if I do? And would it be recommended to install it now before I mess with Superuser and Magisk, or after?
Click to expand...
Click to collapse
I allmost enver use official OTA's so I can't say for certain buttttt as you used SuperSU, the root should be systemless so it should accept OTA updates..
What I would do:
1. make a nandroid
2. install OTA
3. See if everything works as expected
4. restore backup if something doesnt work properly =D
I would install the OTA before trying Magisk
Thank you, that was very helpful. I did try Googling all this, but couldn't find clear answers, which is why I am asking here.
And yes, I am definitely going to make a backup before messing with it. Is there any reason to make a Titanium backup too, or will the nandroid one be enough?
As for removing SuperSU, what would that system/boot stock reset delete? Would it delete any installed applications or application settings? Or undo updates to pre-installed system apps? Or reinstall apps that came with the phone that I uninstalled?
Got it working, thanks. (Though, AutoMagisk seems to only be available as an APK, not as a zip that can be installed from TWRP).
Seems like a few configuration settings got wiped due to the system partition being reset, but other than that most of my data seems perfectly intact.
Hi guys,
I bought a HTC One M9 from my friend but I discovered that it's rooted. That's not a big issue but I can't use Snapchat because the device has been rooted. I only know it's rooted with SuperSU.
I don't know anything about roots and ROMs so can anyone help me with this problem? I red some other threads but they didn't work out... The apps hidemyroot and Root Cloaker also didn't help me.
Thanks a lot!
You'd be best off either unrooting or flashing a fresh rom without any root, and using something like Titanium Backup to backup Snapchat, and whenever you re-root, restore from that backup. You won't have to login again. (Correct me if I'm wrong, as this process had worked in the past, however I am unsure if this is the case now.)
Andranoxi said:
You'd be best off either unrooting or flashing a fresh rom without any root, and using something like Titanium Backup to backup Snapchat, and whenever you re-root, restore from that backup. You won't have to login again. (Correct me if I'm wrong, as this process had worked in the past, however I am unsure if this is the case now.)
Click to expand...
Click to collapse
Thanks for your answer! I just don't know how you do everything with roots etc. Is it possible to get the root away? Would be the best solution for me because I never use it. Is there already a good thread which tells you how to unroot your HTC? My phone is S-On so they told me it was not possible...
If you desperately need snapchat that much then you'll have to flash the phone back to its stock state. There is a thread, by flippy, in the general section stickies that explains how to do that.
Beamed in by telepathy.
Don't listen to these guys, you can download a few things and be on your merry Snapchat. What you'll need (all can be found on XDA):
UnSU-signed.zip
SuperSU 2.79 SR3 zip
suhide zip
RootSwitch 1.3.3.2
xposed framework [optional] (I recommend version 86.2 by topjohnwu)
First reboot to recovery, flash UnSU zip, then reboot to system. Download SafetyNet Helper Test and check if you pass just without root, if it's green we're good to proceed. If it doesn't pass, blue or red, you'll want to flash a ROM and start fresh.
Reboot to recovery again, flash SuperSU zip, it should install as systemless automatically. After that you can install the suhide zip and if you want xposed, then wipe Dalvik and cache and reboot.
Once you're rebooted back in the system you'll want to install the RootSwitch apk and suhide GUI from the playstore. Once they are installed, open RootSwitch and select the options for Disable USB debugging and Stop all su daemons (I also have notification showing so I always know whether it's enabled or not). Open suhide GUI and make sure these items are checked off: Android Pay, Pokemon Go, SnapChat and SystemUI. Once those options are checked, go back to RootSwitch and hit Disable Root. Open SN Helper and test again; it should be green.
You now have a device with systemless root and xposed that can be disabled at any time without a reboot and used as a stock device, working with Android Pay and other apps that block rooted phones, including SnapChat. ?
Of course, if you don't want any of this and just want a stock HTC M9, I recommend downloading the RUU for your model direct from HTC and doing a full restore on it.
Hope this helps.