One plus 3 rooting. - OnePlus 3 Questions & Answers

I had already rooted my oneplus 3 once but I unrooted it for some reason. Therefore, bootloader is already unlocked. I was just wondering if I flash Twrp and then install supersu. Would it wipe my data?

No it won't. I would keep TWRP just incase something happends. Also I prefer Magisk over SuperSU. It has a ton more features and is alot more user friendly and it will persists during system updates.

Related

Still confused about how to install Magisk/Automagisk on my HTC 10

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.

Snapchat login fail on rooted device

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.

Is my phona safe after kingroot?

Hi everyone!
I have rooted my phone. To be honest I don't even remember when
I've used kingroot. Don't remember version or source.
I have newest clean rom.
Didn't have any problems since rooting but I started to wonder if my data is safe. How Can I check it?
I've used KingRoot a few times for other devices, and it always makes me nervous. Use other methods for root if available.
The key to using KingRoot is to ONLY use it to obtain root to flash TWRP. Once you get TWRP recovery flashed, boot immediately into it and do a FULL wipe of everything except the recovery (ie system, data, etc, etc). Then just flash a custom ROM with a normal root like Magisk and that should keep you safe.
KingRoot is exclusively coded by a Chinese group, and it has been verified that the app has sent meta data back to China. So who knows what else it sends back to China. Sometimes on some of my devices it's the only option, so I just follow the steps above to stay safe.
Good luck! :fingers-crossed:
860lacov said:
Hi everyone!
I have rooted my phone. To be honest I don't even remember when
I've used kingroot. Don't remember version or source.
I have newest clean rom.
Didn't have any problems since rooting but I started to wonder if my data is safe. How Can I check it?
Click to expand...
Click to collapse
Your data is safe if you make a full wipe after rooting and flashed another rom.
On the orther side your imei is in their database now.

Safe to upgrade to Pie unlocked now?

Hi,
I have read that upgrading to Pie on an unlocked OP3 will wipe the phone - maybe worse, brick it.
I would like to find out:
a) the status on this (is it fixed in newer releases? Is it planned to be "fixed" or not?)
b) What is the process to upgrade safely (if we need to "re-lock" then upgrade, etc.) and what the repercussions would be (e.g. when you re-lock the BL it wipes your phone)
FYI - I have sock bootloader, stock recovery and stock OS image (even un-rooted before last upgrade), so everything is "correct" except the bootloader is unlocked.
I think these 2 questiosn are everything people need to know to make decisions on upgrading.
I've been scared to upgrade, even though it keeps asking me to, because there are a couple things I don't have backed up yet, but I want to upgrade and try the new OS.
Thanks!
--mobrien
If you relock the device, it will wipe anyway. I upgraded my daughter's phone (my old OP3) last night and it required a wipe installing the ROM. A few thing I found:
With an unlocked bootloader, the OTA would not install. The full, stock ROM download would also not install via stock recovery or through adb.
I had to copy the full ROM to the sdcard, then perform manual install through stock recovery option. It installs, but afterwards it makes you wipe the device.
I mean, I'm sure could've flashed twrp and installed, but I was being lazy.
Sent from my Mi MIX 2S using Tapatalk
noobtoob said:
I mean, I'm sure could've flashed twrp and installed, but I was being lazy.
Click to expand...
Click to collapse
I've had great success booting TWRP over USB. Used to root my phone after every OTA and never changed any stock partitions, other than adding SuperSU to root.
So, are you saying you think installing via TWRP may not make you wipe? (I don't think that's what you are saying, just being hopeful - I also think that TWRP flash even requires wipe more than OTAs usually do.
mobrien118 said:
So, are you saying you think installing via TWRP may not make you wipe? (I don't think that's what you are saying, just being hopeful - I also think that TWRP flash even requires wipe more than OTAs usually do.
Click to expand...
Click to collapse
Sorry man, I haven't a clue. Was hoping getting it to install via the stock recovery wouldn't have wiped it, but that turned up to be a wash. I honestly didn't check into it any further cause my daughter doesn't root or anything, just runs stock, so the priority was just that, get it to boot on the new OS. I back everything up myself, so restoring her stuff wasn't an issue.
If you are rooted but still running stock, why don't you use the migrate app from play store? Back up your data, copy to PC, whatever, then upgrade, root, restore via migrate again. App works wonders and saves a ton of time restoring apps and settings.
Sent from my Mi MIX 2S using Tapatalk
noobtoob said:
If you are rooted but still running stock, why don't you use the migrate app from play store? Back up your data, copy to PC, whatever, then upgrade, root, restore via migrate again. App works wonders and saves a ton of time restoring apps and settings.
Click to expand...
Click to collapse
I haven't used the migrate app. I've always used Titanium Backup in the past, but I've decided to not root my new phone (I've been feeling that it isn't necessary as much anymore and:
I am tired of having to keep re-rooting after every patch
I want to use Google Pay
I'm sure I'll have other reasons to want a locked bootloader that I don't know about yet
I want this phone un-rooted and locked, because I'm giving it to my mom and she will not want to deal with any of that - stock all the way is better for her.
I wonder if there is an app that will allow me to restore without root, even though I could still root my phone that I'm backing up *from*. I just want to migrate the apps to my new phone, but I don't want to wipe it, either, and it is not unlocked. Helium does not seem to work to restore to different hardware (or maybe it just doesn't work at all anymore).

HELP PLEASE: Bootlooped Mi Max 3 after botched Adaway Install

HI everyone I need your help. i installed Adaway using F-Droid without first installing and activating the systemless hosts modules -- which I thought was optional.
Supposedly, failing to activate "systemless hosts" triggers a warning to do so during install, but not in my case. My Mi Max 3 (Global Edition, Post ARB) is stuck on bootloop to OrangeFox.
Uninstalling Adaway from OrangeFox did not fix the bootloop.
I'd be okay with losing all data and reverting to unrooted stock but I don't know how to revert to unrooted stock in OrangeFox when OrangeFox isn't finding any backup images.
Might manually editing the hosts file perhaps fix this?
Should I go into Wipe and wipe everything? Or simply delete Magisk? Theoretically, should this result in a system reboot back to stock?
If I can't see any img files are they still hidden in the phone somewhere (stock images) to reboot to? Because I moved since I rooted and cannot find the backup drive with my images on them.
My OS is still stock Android and Miui. These are the modules installed in Magisk Version 20.3:
optimizedgpsconf
quickstepswitcher
riru-core
riru-edxposed
terminal_debloater
Please, any suggestions -- I am sorry for being so clueless despite being in this forum for five years but although I am good at following instructions this stuff remains basically "magic" to me.
Best wishes!
Anybody ever lose all recovery, including stock, after flashing?
Hi again, I'm the one that bootlooped following adaway install. Stopped mucking around, wiped my data and used Orangefox to flash the OTA, which fixed the bootloop but the phone was encrypted (I really did wipe everything and check all the right boxes in the Miui menu). No big deal. I booted back into Orange Fox and did another data wipe and was able to boot to system.
Unfortunately, not only did I lose root, I lost recovery -- no TWRP, no OrangeFox, no stock recovery. I can only boot into the system.
And yet oddly, I can still browse the root files using a root browser and some play apps for root users still detect Magisk. (but Magisk Mgr isn't one of them).
I'm guessing the wise thing to do at this point is to use ADB and start over from scratch, reinstalling TWRP, Orangefox, Magisk and the rom?
Again, if anyone has encountered this error or has any inkling of a quicker way to fix it, please jump in. Thanks!
I

Categories

Resources