Related
Hey guys I have been searching all over the place for this answer and I just cant seem to find anything on the topic.
This is my first time tinkering with my HTC One X (old version 4.0.3) and downloaded the most updated drivers which is where I believe I went wrong.
I have the 4.2.0.001 drivers and when I open the root.zip file nothing happens I get no errors I just get the "your HTC One X is rooted..." yet my phone simply doesn't reboot.
So I attempted to install the downgraded drivers the 3.0.0.007 which looking back has been the recommended drivers, however; when I extract those files and head into my device manager it does not pull up the androidusb.inf file to upload the 3.0.0.007 drivers.
Am I missing a proper BMP USB Driver and where can I find it? Or is there a root file that will work with the 4.2.0.001 drivers?
If there is any link to this topic please post it, I am very new to rooting or if I have made any mistakes please let me know.
social_spider said:
Hey guys I have been searching all over the place for this answer and I just cant seem to find anything on the topic.
This is my first time tinkering with my HTC One X (old version 4.0.3) and downloaded the most updated drivers which is where I believe I went wrong.
I have the 4.2.0.001 drivers and when I open the root.zip file nothing happens I get no errors I just get the "your HTC One X is rooted..." yet my phone simply doesn't reboot.
So I attempted to install the downgraded drivers the 3.0.0.007 which looking back has been the recommended drivers, however; when I extract those files and head into my device manager it does not pull up the androidusb.inf file to upload the 3.0.0.007 drivers.
Am I missing a proper BMP USB Driver and where can I find it? Or is there a root file that will work with the 4.2.0.001 drivers?
If there is any link to this topic please post it, I am very new to rooting or if I have made any mistakes please let me know.
Click to expand...
Click to collapse
Drivers are drivers. You can root with either. Old new, doesn't matter. It just allows your phone to be recognized by fastboot and ADB, that's all.
exad said:
Drivers are drivers. You can root with either. Old new, doesn't matter. It just allows your phone to be recognized by fastboot and ADB, that's all.
Click to expand...
Click to collapse
Thank you :good: so this means its something wrong with the root.zip file or the process Im doing to root? I just attempted it a few seconds ago this time the phone rebooted 2 times but I am not seeing any Su app on my phone
social_spider said:
Thank you :good: so this means its something wrong with the root.zip file or the process Im doing to root? I just attempted it a few seconds ago this time the phone rebooted 2 times but I am not seeing any Su app on my phone
Click to expand...
Click to collapse
The root methods simply give you temp root and super cid so you can unlock the bootloader. *facepalm*
Then when your bootloader is unlocked you can flash recovery and then flash su through recovery or install a custom rom which will already be rooted.
exad said:
The root methods simply give you temp root and super cid so you can unlock the bootloader. *facepalm*
Then when your bootloader is unlocked you can flash recovery and then flash su through recovery or install a custom rom which will already be rooted.
Click to expand...
Click to collapse
damn im an idiot haha thank you for clearing this up
I guess I am not understanding the core concept here, so I now I theoretically have a temp root with Super CID. I was under the impression that I was supposed to download Titanium Backup before attempting to unlock the bootloader. So I went to download and it told me I did not have root access so I could not run Titanium. I am afraid to attempt a bootloader unlock with out my rom being backed up. Can you please shed some light on this or post a link that would explain the process after temp root in detail thank you
social_spider said:
I guess I am not understanding the core concept here, so I now I theoretically have a temp root with Super CID. I was under the impression that I was supposed to download Titanium Backup before attempting to unlock the bootloader. So I went to download and it told me I did not have root access so I could not run Titanium. I am afraid to attempt a bootloader unlock with out my rom being backed up. Can you please shed some light on this or post a link that would explain the process after temp root in detail thank you
Click to expand...
Click to collapse
You can backup after your bootloader is unlocked.. bootloader unlock is just a flag that allows you to flash certain partitions like recovery.
Backing up before or after will make no difference. If you end up really messing up your device, a backup won't save you anyway so I don't see why you'd be worried. If you S-OFF, you can RUU to get back to stock any time no problem, unless you full on brick. Then only jtagg will save you.
Typically before I root a phone, I read all the stickies in all the subsections to understand how things work since every phone has differences, some subtle some not so subtle.
exad said:
You can backup after your bootloader is unlocked.. bootloader unlock is just a flag that allows you to flash certain partitions like recovery.
Backing up before or after will make no difference. If you end up really messing up your device, a backup won't save you anyway so I don't see why you'd be worried. If you S-OFF, you can RUU to get back to stock any time no problem, unless you full on brick. Then only jtagg will save you.
Typically before I root a phone, I read all the stickies in all the subsections to understand how things work since every phone has differences, some subtle some not so subtle.
Click to expand...
Click to collapse
Thank you very much before I unlock Im gonna hit the stickies and make sure I completely understand everything :good:
As the title suggest, does anyone else having such (one, more or all) issues on Nexus 5 after root?
1. Kitkat kinda initializes after every reboot. Not like the very first time starting the device (setup assistent) but installing/updating apps (which) are already on the device (same Verstion) and re-setting configuration to what it already should be.
2. Always showing H (internet connection) and at least two bars on signal strength even when there is no signal (accourding to chrome and (stock) dialer app.
3. Loss of signal but pretending there is one (like in 2.) and only regaining signal after reboot.
4. Loss of distance between apps within the appdrawer (more apps per page) until uninstallation of an app (remains normal after reinstall)
5. many app crashes (before and after rooting)
6. sometimes notification led keeps blinking after notification was dismissed, sometimes the notification led blinks very fast.
I rooted my device with cf auto root.
Except for 4 &5, yes.
I am glad that I am not alone but does anyone know whats the source of this strange behaviour or how this can be fixed?
In a case like this i would go back to stock, make a factory reset and then rooting the N5 again, manually, without using cf auto root.
Rooting manually it's just a good way to understand the android OS, and how it's made, imho.
Is there a good low-risk way (manual/tutorial) to manually root without a custom rom and custom recovery (CWM/TWRP) ?
Because besides root access I want to stay as close as possible to stock.
Nik_B said:
Is there a good low-risk way (manual/tutorial) to manually root without a custom rom and custom recovery (CWM/TWRP) ?
Because besides root access I want to stay as close as possible to stock.
Click to expand...
Click to collapse
Wugfresh's toolkit is imho the best and safest way to root and do most changes to all nexus devices. About the only difficult you may experience is usb driver/connectivity issues. The usb driver guides are well documented and easy to follow. It's no different than the standard adb usb drivers. Most have no issues, but that is the only thing that can cause problems with adb or Wugfresh's toolkit.
Read through Wugfresh's forum topic to acquaint yourself with mtp/ptp and driver installation and you should breeze through using his toolkit.
Sent from my Apple ] [e using ProTERM 2.2
Nik_B said:
Is there a good low-risk way (manual/tutorial) to manually root without a custom rom and custom recovery (CWM/TWRP) ?
Because besides root access I want to stay as close as possible to stock.
Click to expand...
Click to collapse
custom recoveries do not prevent the OTA.. plus you can just fastboot boot recovery whateverrecovery.img
i blame your problems on the CF-autoroot as i have none of the symptoms you describe.
Looking into the script chainfire offers shows me that there are only 2 commands executed.
the
fastboot oem unlock - command is clear to me that it unlocks the bootloader
but i have some questions about the second one: fastboot boot image\CF-Auto-Root-hammerhead... ...nexus5.img
Am I correct assuming that this command tells the bootloader to start this image instead of the regular android (once?)
which modifies "something" within the "original" android os (image)?
If yes, can somebody tell me?
Is the only modification made there the mount configuration of the system partition and/or user settings?
Is a documentation for such internal matters of rooting somewhere out there?
yeah I know I have lots of questions and yes I am very curious.
Thanks in advance
Nik_B said:
Looking into the script chainfire offers shows me that there are only 2 commands executed.
the
fastboot oem unlock - command is clear to me that it unlocks the bootloader
but i have some questions about the second one: fastboot boot image\CF-Auto-Root-hammerhead... ...nexus5.img
Am I correct assuming that this command tells the bootloader to start this image instead of the regular android (once?)
which modifies "something" within the "original" android os (image)?
If yes, can somebody tell me?
Is the only modification made there the mount configuration of the system partition and/or user settings?
Is a documentation for such internal matters of rooting somewhere out there?
yeah I know I have lots of questions and yes I am very curious.
Thanks in advance
Click to expand...
Click to collapse
unless someone looks into the boot image CF has setup, there's no way to tell what his image does.
thats why its easiest to just boot a custom recovery and then flash supersu.zip, yet a lot of people want to just use toolkits cause "its easier" but when you do use a toolkit, you end up with issues.
DreamLinker said:
In a case like this i would go back to stock, make a factory reset and then rooting the N5 again, manually, without using cf auto root.
Rooting manually it's just a good way to understand the android OS, and how it's made, imho.
Click to expand...
Click to collapse
Go with this guy.
As soon as I read your thread title, I knew you rooted using an "auto root". Rooting a device is actually very simple, just takes a few minutes of your time to research the steps. As long as you have 10 minutes, a USB cable and a Windows Computer, it should be easy and result in a errorless experience.
Zepius said:
unless someone looks into the boot image CF has setup, there's no way to tell what his image does.
thats why its easiest to just boot a custom recovery and then flash supersu.zip, yet a lot of people want to just use toolkits cause "its easier" but when you do use a toolkit, you end up with issues.
Click to expand...
Click to collapse
I already know that. Maybe my question was not correct.
What I wanna know is what happens when i flash a custom recovery, root my device and so on in the background
and what are necessary steps to such actions?
Because I would like to do all those actions on my own. (for example make my own image to boot for rooting)
But I won't unless I know exactly WHAT I am doing.
Hope this for wording made my intentions clearer. (Sorry I am not that good in English)
Nik_B said:
I already know that. Maybe my question was not correct.
What I wanna know is what happens when i flash a custom recovery, root my device and so on in the background
and what are necessary steps to such actions?
Because I would like to do all those actions on my own. (for example make my own image to boot for rooting)
But I won't unless I know exactly WHAT I am doing.
Hope this for wording made my intentions clearer. (Sorry I am not that good in English)
Click to expand...
Click to collapse
fastboot boot recovery recovery.img - this just boots into the recovery once, but leaves the stock recovery as the recovery that is written to the device
when you flash supersu.zip what it does is execute a script that places the su binary in /data/xbin i believe and gives it the proper permissions, and also places supersu app on your phone.
you do not need to make your own boot image, or anything of the sort.
The root process is not capable of causing any of these issues. Root using wugfresh is the exact same as using auto root and both of these are the same as manually doing it yourself. None of them can cause visual changes or signal loss alone, and the only reason we don't recommend toolkits or auto root is so people don't get comfortable with the idea that they don't need to know fastboot commands in the event that they boot loop, etc.
Sent from my Nexus 5 using Tapatalk
joshnichols189 said:
The root process is not capable of causing any of these issues. Root using wugfresh is the exact same as using auto root and both of these are the same as manually doing it yourself. None of them can cause visual changes or signal loss alone, and the only reason we don't recommend toolkits or auto root is so people don't get comfortable with the idea that they don't need to know fastboot commands in the event that they boot loop, etc.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Do I understand you correctly that neither wugfresh nor auto root are causing the problems in your eyes. I´m just curious because many people including me used Chainfire´s auto root but not all of them are reporting problems. In my case the Nex5 seems to forget already set default apps e.g. for tapatalk links, urls etc.
Cheers, T.
http://forum.xda-developers.com/showthread.php?t=2699089&page=40
I tried using that method to root my phone, but Super SU just won't install binaries. First time around it just wouldn't work, after a few tries I unrooted my device and started over. I got the same message, "Unable to install, reboot"
Then after that it said something like "If you upgraded to 4.3 then reroot" Something like that. Which is weird because I have 4.4.2.
What's going on? I tried Superuser but when I tried installing the binaries it crashed when it was doing a software update twice so I had to hold down on volume up and the power button to reboot it on both occasions.
Also, how do I do an ADB Reboot? What's the easiest method? I tried doing that on my PC but it keeps saying device not detected Maybe I'm not setting up the program for that right? Yes, Developer Options and USB Debugging are enabled.
Yes my M8 is from Verizon. Is there another method for one-click rooting?
Anyone?
CannedBullets said:
http://forum.xda-developers.com/showthread.php?t=2699089&page=40
I tried using that method to root my phone, but Super SU just won't install binaries. First time around it just wouldn't work, after a few tries I unrooted my device and started over. I got the same message, "Unable to install, reboot"
Then after that it said something like "If you upgraded to 4.3 then reroot" Something like that. Which is weird because I have 4.4.2.
What's going on? I tried Superuser but when I tried installing the binaries it crashed when it was doing a software update twice so I had to hold down on volume up and the power button to reboot it on both occasions.
Also, how do I do an ADB Reboot? What's the easiest method? I tried doing that on my PC but it keeps saying device not detected Maybe I'm not setting up the program for that right? Yes, Developer Options and USB Debugging are enabled.
Yes my M8 is from Verizon. Is there another method for one-click rooting?
Click to expand...
Click to collapse
Probably the last thing you wanna do but if it wont work have you considered a factory reset? Usually solves most issues & are you S-OFF? Asking the S-OFF question because if you are you can flash a custom recovery and just flash the binaries. 0% failure rate with that as far as I know. About the ADB Reboot question, did you install the HTC Sync Manager so it would install the proper drivers and then removed the Sync program (not drivers)?
S1L3nTShaDoWz said:
Probably the last thing you wanna do but if it wont work have you considered a factory reset? Usually solves most issues & are you S-OFF? Asking the S-OFF question because if you are you can flash a custom recovery and just flash the binaries. 0% failure rate with that as far as I know. About the ADB Reboot question, did you install the HTC Sync Manager so it would install the proper drivers and then removed the Sync program (not drivers)?
Click to expand...
Click to collapse
I have not considered a factory reset. Also, what's S-OFF? I'm not sure what that is. Also do you mean the HTC Transfer Tool? I don't have that.
CannedBullets said:
I have not considered a factory reset. Also, what's S-OFF? I'm not sure what that is. Also do you mean the HTC Transfer Tool? I don't have that.
Click to expand...
Click to collapse
I don't really know how to explain what "S" is other than its security/signature verification(not sure on signature verification), when your phone is S-ON you can't flash any non verified rom or write to protected areas of your phone such as /system which is required for root, etc and I know it does more than that but I'm not 100% educated as to what it means yet though so can't give you a 100% accurate or complete explanation.
Now based off of what I just said and a little research i'm quite sure you actually require it for a permanent root solution such as SuperSU but could be wrong.
Anyways if you're interested in doing it go here: http://forum.xda-developers.com/showthread.php?t=2708628 and follow the instructions carefully. This also unlocks your bootloader which means you can install custom roms, kernels, flash scripts, apps, SuperSU for PERMANENT root, etc. In order to do these things you'll need to flash a custom recovery such as TWRP or CWM (Team Win Recovery Project & Clockwork Mod/Philz Touch). Afterwards it's quite simple from there on out, just be careful and research before you do anything I've suggested/stated. Also on the Sync Manager thing, what you need to do is install it from here http://www.htc.com/us/support/software/htc-sync-manager.aspx and then let it install the phone drivers for your M8 on your computer and then you need to uninstall it "HTC Sync Manager" from your computer in order to do the S-OFF process.
Please do be careful and get a good understanding before you do this though, re-read things a few times and make sure you're well aware of what it means and how to do it properly.
S1L3nTShaDoWz said:
Probably the last thing you wanna do but if it wont work have you considered a factory reset? Usually solves most issues & are you S-OFF? Asking the S-OFF question because if you are you can flash a custom recovery and just flash the binaries. 0% failure rate with that as far as I know. About the ADB Reboot question, did you install the HTC Sync Manager so it would install the proper drivers and then removed the Sync program (not drivers)?
Click to expand...
Click to collapse
S1L3nTShaDoWz said:
I don't really know how to explain what "S" is other than its security/signature verification(not sure on signature verification), when your phone is S-ON you can't flash any non verified rom or write to protected areas of your phone such as /system which is required for root, etc and I know it does more than that but I'm not 100% educated as to what it means yet though so can't give you a 100% accurate or complete explanation.
Now based off of what I just said and a little research i'm quite sure you actually require it for a permanent root solution such as SuperSU but could be wrong.
Anyways if you're interested in doing it go here: http://forum.xda-developers.com/showthread.php?t=2708628 and follow the instructions carefully. This also unlocks your bootloader which means you can install custom roms, kernels, flash scripts, apps, SuperSU for PERMANENT root, etc. In order to do these things you'll need to flash a custom recovery such as TWRP or CWM (Team Win Recovery Project & Clockwork Mod/Philz Touch). Afterwards it's quite simple from there on out, just be careful and research before you do anything I've suggested/stated. Also on the Sync Manager thing, what you need to do is install it from here http://www.htc.com/us/support/software/htc-sync-manager.aspx and then let it install the phone drivers for your M8 on your computer and then you need to uninstall it "HTC Sync Manager" from your computer in order to do the S-OFF process.
Please do be careful and get a good understanding before you do this though, re-read things a few times and make sure you're well aware of what it means and how to do it properly.
Click to expand...
Click to collapse
Yeah I'll have to look into that. I'm not sure if I'll ever flash a custom ROM though on my M8, Sense 6 is good as it is, I need to get Cyanogenmod on my Razr Maxx, Motoblur on it is just slow ever since they updated it to 4.1.2.
CannedBullets said:
Yeah I'll have to look into that. I'm not sure if I'll ever flash a custom ROM though on my M8, Sense 6 is good as it is, I need to get Cyanogenmod on my Razr Maxx, Motoblur on it is just slow ever since they updated it to 4.1.2.
Click to expand...
Click to collapse
Most of the ROM's for the M8 are Sense based anyways so you won't have a problem if you want Sense.
S1L3nTShaDoWz said:
Most of the ROM's for the M8 are Sense based anyways so you won't have a problem if you want Sense.
Click to expand...
Click to collapse
I just had a strange morning. What's new right? This morning I saw that my Titanium Back had a superuser fail. I had no problems yesterday. I used SuperSU to root and checked to see if Titanium Back was granted rights and it was. Still no luck running it. So Titanium suggested I load Superuser which I was not running. I installed it and it said it could not update the binary. That's weird so I read this post and reflashed SuperSU and yep Titanium backup was denied in the grant list. I granted it and everything is OK now. I posted here because I saw an unusual program in the grant list in SuperSU. It is com.koushikdutta.superuser. I don't know what that is but I bet that was the culprit. It did not show before I updated so it was hidden. Anybody know where this came from?
Weaksauce will not install binaries that's why it needs to reroot your phone every time you reboot. If you want your root to stick you need to be S-OFF. Since you are on 4.2.2 you could try Firewater to gain S-OFF. (Only works for some M8'S on 4.2.2)
http://firewater-soff.com/instructions/
If firewater does not work then you need to use Sunshine which I believe it cost $25. (Will not work on 4.4.4!)
http://forum.xda-developers.com/showthread.php?t=2792487
Not sure if you have adb/fastboot set up on your computer but if not...Google! I know there are instructions on how to set that up because I had to Google it. I think that may be the hardest part of all of this, if you can follow instructions WORD FOR WORD after setting that up I don't see how you can mess up. If you do find yourself stuck well we are here
SOLUTION
CannedBullets said:
http://forum.xda-developers.com/showthread.php?t=2699089&page=40
I tried using that method to root my phone, but Super SU just won't install binaries. First time around it just wouldn't work, after a few tries I unrooted my device and started over. I got the same message, "Unable to install, reboot"
Then after that it said something like "If you upgraded to 4.3 then reroot" Something like that. Which is weird because I have 4.4.2.
What's going on? I tried Superuser but when I tried installing the binaries it crashed when it was doing a software update twice so I had to hold down on volume up and the power button to reboot it on both occasions.
Also, how do I do an ADB Reboot? What's the easiest method? I tried doing that on my PC but it keeps saying device not detected Maybe I'm not setting up the program for that right? Yes, Developer Options and USB Debugging are enabled.
Yes my M8 is from Verizon. Is there another method for one-click rooting?
Click to expand...
Click to collapse
**SOLUTION**
Download the SuperSU ZIP from the link below;
http://download.chainfire.eu/supersu
Reboot your device into your custom recovery of choice, install the ZIP (which should be in your download folder on "sdcard" by default), reboot.
It should now work with no issues!
KnightAlex said:
**SOLUTION**
Download the SuperSU ZIP from the link below;
download.chainfire.eu/supersu
Reboot your device into your custom recovery of choice, install the ZIP (which should be in your download folder on "sdcard" by default), reboot.
It should now work with no issues!
Click to expand...
Click to collapse
I installed CM13 on my Moto G 1st Gen also GApps, I also had TWRP working. So my next step was to install SuperSU (UPDATE-SuperSU-v2.46.zip) with TWRP, after it says it was succesfull, i wanted to reboot the system, it is stuck in the Cyanogenmod Bootanimation and won't boot into the system. And It also stuck in the TWRP loading screen when i want to load into recovery!
What can I do? I have still files on the phone which I want to preserve!
Umm. This is a HTC one m8 forum?
I've read a lot of guides both on this forum and using google. Some are saying to wipe the phone completely and flash SuperSU through TWRP, some are saying there is a chainfire auto-root method. Why am I like the only one confused? I just received my Nexus 5 (I know I'm late in the game), and updated to 5.1. I would like to root, but don't really know what the best way is. Should I just wait on a new, easier way that is currently in the development process?
Also I am reading I'd have to go back to stock to get any new OTA updates, and I read that can be kind of a PITA. So do you think root is still worth it? Honestly I just want viper4android, Adaway, and Greenify. That's it.
Thanks for the help and sorry for probably a very redundant question.
tuffluck said:
I've read a lot of guides both on this forum and using google. Some are saying to wipe the phone completely and flash SuperSU through TWRP, some are saying there is a chainfire auto-root method. Why am I like the only one confused? I just received my Nexus 5 (I know I'm late in the game), and updated to 5.1. I would like to root, but don't really know what the best way is. Should I just wait on a new, easier way that is currently in the development process?
Also I am reading I'd have to go back to stock to get any new OTA updates, and I read that can be kind of a PITA. So do you think root is still worth it? Honestly I just want viper4android, Adaway, and Greenify. That's it.
Thanks for the help and sorry for probably a very redundant question.
Click to expand...
Click to collapse
As long as you're familiar with adb/fastboot run the following:
Code:
[U]From Bootloader[/U]
fastboot oem unlock
fastboot flash recovery [URL="https://dl.twrp.me/hammerhead/twrp-2.8.6.1-hammerhead.img"]twrp-2.8.6.1-hammerhead.img[/URL]
Boot into recovery....
[U]From Recovery[/U]
adb sideload [URL="https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1"]UPDATE-SuperSU-v2.46.zip[/URL]
tuffluck said:
I've read a lot of guides both on this forum and using google. Some are saying to wipe the phone completely and flash SuperSU through TWRP, some are saying there is a chainfire auto-root method. Why am I like the only one confused? I just received my Nexus 5 (I know I'm late in the game), and updated to 5.1. I would like to root, but don't really know what the best way is. Should I just wait on a new, easier way that is currently in the development process?
Also I am reading I'd have to go back to stock to get any new OTA updates, and I read that can be kind of a PITA. So do you think root is still worth it? Honestly I just want viper4android, Adaway, and Greenify. That's it.
Thanks for the help and sorry for probably a very redundant question.
Click to expand...
Click to collapse
Both are right. There is a manual way (flashing SuperSU through TWRP) and there is an "automated" way (the chainfire auto-root). Pick your poison.
The manual way will most likely wipe your device because the "unlock" step does that. I'm honestly not sure about the auto-root method, but I'm going to guess it probably also wipes.
As for OTA, yes, you need a stock recovery to get OTA, because.... well... the OTA uses the stock recovery to update. Most people are of the mind that if you're the type of person who flashes a custom recovery like TWRP, you're also the type of person who doesn't care about OTAs (the .zip is typically posted here within hours of the OTA going live anyway).
There are risks and drawbacks to any kind of hacking of your phone. Risks obviously include bricking, but the drawbacks usually include having to wipe and reinstall things once in a while, and also the lack of OTAs. Pick your poison.
fosser2 said:
As long as you're familiar with adb/fastboot run the following:
Code:
[U]From Bootloader[/U]
fastboot oem unlock
fastboot flash recovery [URL="https://dl.twrp.me/hammerhead/twrp-2.8.6.1-hammerhead.img"]twrp-2.8.6.1-hammerhead.img[/URL]
Boot into recovery....
[U]From Recovery[/U]
adb sideload [URL="https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1"]UPDATE-SuperSU-v2.46.zip[/URL]
Click to expand...
Click to collapse
Being a Nexus device this process is pretty straightforward and does not need all of the utilities to obtain root
Hello guys,
Don't know if I should root my phone..if I root my phone can I go totally stock without problems (no boot warning and so on)?
And also is there a solution to get Netflix in hdr and better resolution with unlocked bootloader?
And which why should I root / which apps are really recommend to let me root
manutoxic said:
Hello guys,
Don't know if I should root my phone..if I root my phone can I go totally stock without problems (no boot warning and so on)?
And also is there a solution to get Netflix in hdr and better resolution with unlocked bootloader?
And which why should I root / which apps are really recommend to let me root
Click to expand...
Click to collapse
You should post your question on https://forum.xda-developers.com/oneplus-7-pro/help
No, rooting requires you to unlock your bootloader which means you will get the boot warning. I think there was a workaround for previous phones but I wouldn't recommend it. Google forced OEMs to add the warning.
Judging by your questions though, I would seem that you already knew the answers.
First of all, please search the forum, or just take a look at the threads at least, before making new threads. There is already a lengthy discussion on this exact question, right on the top page of Q&A: https://forum.xda-developers.com/oneplus-7-pro/help/root-yes-t3936633
And another here: https://forum.xda-developers.com/on...ens-unlock-bootloader-features-loose-t3932323
And here: https://forum.xda-developers.com/oneplus-7-pro/help/advantages-unlocking-bootloader-t3938457
Note that unlocking the bootloader and root go hand in hand. So even though 2 of the thread subject lines refer to unlocking the bootloader, a lot of the discussion involves root as well.
We really don't need a new thread, every time someone comes on here that can't make their own decision about root/no root. A decision that can be based on readily available info, that existed even before the above discussions existed!
Feeling charitable today, so I'll answer your questions as well as I can (my responses below in red font):
manutoxic said:
Don't know if I should root my phone..if I root my phone can I go totally stock without problems (no boot warning and so on)?
Return to full stock ROM, and relocking the bootloader should get rid of the boot warning, etc. I haven't tried it personally (restore to stock) but do a search if you want to verify, the info probably exists.
And also is there a solution to get Netflix in hdr and better resolution with unlocked bootloader?
Not sure yet (just got the phone and rooted it). There is a modded Netflix apk (older version, not for this device specifically) that some folks say will get back the 720p. But others report that it is still only 480p with the modded apk. And no HDR (as the apk is an old version that doesn't support it).
And which why should I root / which apps are really recommend to let me root
Root isn't typically achieved with an "app". But there is a toolkit that performs most of the functions. Although, all you really need is a couple files, and typing a couple fastboot commands. And frankly, if you don't know how to you fastboot, you really shouldn't be messing with root in the first place. My recommendation would be the method: unlock the bootloader, fastboot boot TWRP, in TWRP flash the TWRP installer zip, flash Magisk root, done. Pretty easy, and I did it with zero issues.
Click to expand...
Click to collapse
A wise man once said: If you have to ask, don't root.
B3311 said:
A wise man once said: If you have to ask, don't root.
Click to expand...
Click to collapse
Mr. XDA said that