SuperSU doesnt give me root access - Samsung Galaxy S Relay 4G

Hi, I downloaded UPDATE-SuperSU-v1.25.zip and saved it to my SD card. Rebooted into PhilZ recovery and installed it successfully. Rebooted and root checker basic says i dont have root access. is there something I'm missing?

DJRepresent said:
Hi, I downloaded UPDATE-SuperSU-v1.25.zip and saved it to my SD card. Rebooted into PhilZ recovery and installed it successfully. Rebooted and root checker basic says i dont have root access. is there something I'm missing?
Click to expand...
Click to collapse
SuperSU v1.25 is pretty old. Have you tried v1.93?
I don't know the process under PhilZ at all. You didn't mention which image you are using. TouchWiz? One of the custom images?

Magamo said:
SuperSU v1.25 is pretty old. Have you tried v1.93?
I don't know the process under PhilZ at all. You didn't mention which image you are using. TouchWiz? One of the custom images?
Click to expand...
Click to collapse
Where can I download 1.93?
I'm actually using one of the Team Apexqtmo ROMs from earlier this week.

DJRepresent said:
Where can I download 1.93?
I'm actually using one of the Team Apexqtmo ROMs from earlier this week.
Click to expand...
Click to collapse
In fact, looks like it was just updated to v1.94
http://forum.xda-developers.com/showthread.php?t=1538053
There's a download link in the OP of this thread, (Marked as the CWM/TWRP/Mobile ODIN version)

Magamo said:
In fact, looks like it was just updated to v1.94
http://forum.xda-developers.com/showthread.php?t=1538053
There's a download link in the OP of this thread, (Marked as the CWM/TWRP/Mobile ODIN version)
Click to expand...
Click to collapse
Installed it, but it didn't work. I used an app called Root Checker Basic and it says, "Sorry! This device does not have proper root access."
Any other ideas? Here's my device's information:
CyanogenMod Version: cm-11-20140329-NIGHTLY
Android Vers: 4.4.2
Edit: Weird, the SuperSU app didn't give me a "Not Rooted" error upon opening up. Anyways, can I overclock my phone now? What app can I use?

DJRepresent said:
Installed it, but it didn't work. I used an app called Root Checker Basic and it says, "Sorry! This device does not have proper root access."
Any other ideas? Here's my device's information:
CyanogenMod Version: cm-11-20140329-NIGHTLY
Android Vers: 4.4.2
Edit: Weird, the SuperSU app didn't give me a "Not Rooted" error upon opening up. Anyways, can I overclock my phone now? What app can I use?
Click to expand...
Click to collapse
Make certain that you set up SuperSU properly, and allow it to respect CyanogenMod's root access settings.

Magamo said:
Make certain that you set up SuperSU properly, and allow it to respect CyanogenMod's root access settings.
Click to expand...
Click to collapse
Yeah, it's already set to "respect." Not sure about the other settings, though. How do I overclock this piece?

I have a bad feeling that installing the old version first may have screwed up your new installation. If your root apps still fail to get permission, try going through the supersu settings to clean up for reinstallation, and go through the installation procedure again. Overclocking as you think of it is a function of the kernel, and I do not know of any custom kernels for the apexqtmo that allow for it. Besides, overclocking will give you no real performance benefit on the apexqtmo, and in fact will cause instability, and overheating, which will cause the phone to trip over into thermal protection mode much faster, which means it will automatically throttle back. (Which is precisely why the stock CM and HypnoToad kernels do not allow for frequency scaling in an upward direction from stock CPU speeds

I'm no expert, but maybe something just messed up. try flashing a rom so you can just start over.

Magamo said:
I have a bad feeling that installing the old version first may have screwed up your new installation. If your root apps still fail to get permission, try going through the supersu settings to clean up for reinstallation, and go through the installation procedure again. Overclocking as you think of it is a function of the kernel, and I do not know of any custom kernels for the apexqtmo that allow for it. Besides, overclocking will give you no real performance benefit on the apexqtmo, and in fact will cause instability, and overheating, which will cause the phone to trip over into thermal protection mode much faster, which means it will automatically throttle back. (Which is precisely why the stock CM and HypnoToad kernels do not allow for frequency scaling in an upward direction from stock CPU speeds
Click to expand...
Click to collapse
OK, thanks, I'll avoid doing it then.

Related

Super User on Charge won't update. Anyone else seeing this?

So I am getting the typical # notification that superuser binary is out of date. When I try to install the update it fails at Gaining root access .... It has always updated successfully in the past.
I still have root access, Open Garden wifi tethering is granted permissions when I use it, but superuser fails at the gaining root access point every time now.
Anyone else seeing this or have any suggestions? I would HATE to un-install superuser and not be able to gain root access after the fact !!!
Any suggestions or help greatly appreciated.
Chopstix9 said:
So I am getting the typical # notification that superuser binary is out of date. When I try to install the update it fails at Gaining root access .... It has always updated successfully in the past.
I still have root access, Open Garden wifi tethering is granted permissions when I use it, but superuser fails at the gaining root access point every time now.
Anyone else seeing this or have any suggestions? I would HATE to un-install superuser and not be able to gain root access after the fact !!!
Any suggestions or help greatly appreciated.
Click to expand...
Click to collapse
What ROM and kernel are you on?
There's an issue that Infinity ROM does not include su within the ROM package and relies on the kernel, and some versions of imo's kernel does not include it either.
shrike1978 said:
What ROM and kernel are you on?
There's an issue that Infinity ROM does not include su within the ROM package and relies on the kernel, and some versions of imo's kernel does not include it either.
Click to expand...
Click to collapse
I'm running DroidXcon's stock rooted EE4 with CWM. No additional kernals flashed. Have been using it a long time and all of a sudden this issue popped up.
Are you able to get root access in other apps?
shrike1978;Open18173949 said:
Are you able to get root access in other apps?
Click to expand...
Click to collapse
Hmmm..... Open Garden Wifi Tether says it has root access and it works, using it now, so I assumed I still had root. I just opened Titanium and ..... no root!!!
I wonder if applying the sd write protect or no battery popup fixes blew it away? Do I need to re-flash the ROM? Or is there a zip file I can apply via CWM to re-gain root?
This should work for you. Let us know if it doesn't.
http://db.tt/4b3IK0C
shrike1978 said:
This should work for you. Let us know if it doesn't.
http://db.tt/4b3IK0C
Click to expand...
Click to collapse
Nope I lost my root, that didn't do it.
I'm out of ideas
I actually have a similar problem and will not update to the 3.0
I updated and then flashed the binary successfully. Had to reboot the phone and it reports binaries are missing. downloaded manually and flashed and still have the problem after reboot.
Have you tried uninstalling the Superuser app and reinstalling? I had the same issue before and this worked for me.

AdAway - what am I missing?

Evening. I had previous installed WeakSauce and SuperSU on my Verizon HTC One M8.
today, I applied S-off, and flashed ClockwordMod Recovery Unofficial.
I installed Root from inside CWM.
However, I still cannot apply host files in CWM. This suggests that I don't necessarily have full root, so perhaps I missed a vital step somewhere.
Little help? That's all i want is proper ad blocking. otherwise, this phone runs just fine with Nova Launcher
thanks,
I always throw my Awaway apk into system/app. Not sure if that actually does anything, but it seems to apply more often than not. I've always had issues with adaway sometimes not applying, so you are not alone.
Myk Robinson said:
Evening. I had previous installed WeakSauce and SuperSU on my Verizon HTC One M8.
today, I applied S-off, and flashed ClockwordMod Recovery Unofficial.
I installed Root from inside CWM.
However, I still cannot apply host files in CWM. This suggests that I don't necessarily have full root, so perhaps I missed a vital step somewhere.
Little help? That's all i want is proper ad blocking. otherwise, this phone runs just fine with Nova Launcher
thanks,
Click to expand...
Click to collapse
Unfortunately, while booted into Android, the stock kernal prevents system partition write access. You'll need to disable it.
EDIT: I stand corrected.
MultiDev said:
Unfortunately, while booted into Android, the stock kernal prevents system partition write access. You'll need to disable it.
Click to expand...
Click to collapse
This. The modified kernel it's being worked on still but I believe it can be found in development
Sent from my HTC6525LVW using Tapatalk
Clarification
MultiDev, if I am understanding, you mean just disable AdAway because it wont work yet until a custom kernel or kernel mod is installed?
Myk Robinson said:
Evening. I had previous installed WeakSauce and SuperSU on my Verizon HTC One M8.
today, I applied S-off, and flashed ClockwordMod Recovery Unofficial.
I installed Root from inside CWM.
However, I still cannot apply host files in CWM. This suggests that I don't necessarily have full root, so perhaps I missed a vital step somewhere.
Little help? That's all i want is proper ad blocking. otherwise, this phone runs just fine with Nova Launcher
thanks,
Click to expand...
Click to collapse
download and flash this in recovery: http://download.chainfire.eu/345/SuperSU/
then open it so it can update (use recovery method when asked to update)
then run adaway
Got it
kwkw480 said:
download and flash this in recovery: http://download.chainfire.eu/345/SuperSU/
then open it so it can update (use recovery method when asked to update)
then run adaway
Click to expand...
Click to collapse
Thanks, it successfully applied after that. Apparently I missed step one in some previous instructions where it said to flash the SuperSU binary.
Last question. I assume at this point, I can uninstall WeakSauce since we have permanent proper root?
I gotta say, this was pretty easy in Linux Mint 16....
Myk Robinson said:
Thanks, it successfully applied after that. Apparently I missed step one in some previous instructions where it said to flash the SuperSU binary.
Last question. I assume at this point, I can uninstall WeakSauce since we have permanent proper root?
I gotta say, this was pretty easy in Linux Mint 16....
Click to expand...
Click to collapse
Yes, uninstall weak sauce
MultiDev said:
Unfortunately, while booted into Android, the stock kernal prevents system partition write access. You'll need to disable it.
Click to expand...
Click to collapse
S-Off'd and rooted through flashable zip. Installed adaway as a system app, and it's running fine here. Nothing else changed or added.
M8, nuff said.
Thank you
Thank you all for replying. Nice to have such a fast response.
All this because I missed the first line of the instructions...
If Verizon customer service was as good as the fine folks on this forum....
mchief298 said:
S-Off'd and rooted through flashable zip. Installed adaway as a system app, and it's running fine here. Nothing else changed or added.
M8, nuff said.
Click to expand...
Click to collapse
Yeah, I was wrong about that. The system partition is writable after S-off.
mchief298 said:
S-Off'd and rooted through flashable zip. Installed adaway as a system app, and it's running fine here. Nothing else changed or added.
M8, nuff said.
Click to expand...
Click to collapse
I also have s-off, uninstalled weak sauce, then flashed through CWM supersu.zip for full root, reboot. Downloaded latest AdAway apk found here on xda forum. I then ran apk file from my download folder, hit install. Open AdAway, click on Download fiels and apply add blocking. Now it just gets stuck on Applying... with the circle going around and around for over 15 minutes straight now! Yes i gave root access when asked. Is this normal?
Nevermind. Closed app, then reopened and it did the download thing like normal. Now says successful and applied hosts sources: 4/4.
So i'm good to go now? Does this need reboot like prompted?
deeznuts said:
I also have s-off, uninstalled weak sauce, then flashed through CWM supersu.zip for full root, reboot. Downloaded latest AdAway apk found here on xda forum. I then ran apk file from my download folder, hit install. Open AdAway, click on Download fiels and apply add blocking. Now it just gets stuck on Applying... with the circle going around and around for over 15 minutes straight now! Yes i gave root access when asked. Is this normal?
Nevermind. Closed app, then reopened and it did the download thing like normal. Now says successful and applied hosts sources: 4/4.
So i'm good to go now? Does this need reboot like prompted?
Click to expand...
Click to collapse
You don't NEED to, but it is recommended.
M8, nuff said.
This is the one app causing me problems. Adfree works problem free, but AdAway likes to keep getting stuck on "Applying...". I've got it to succeed once or twice by force closing and re-trying, but it's not reliable. I'm S-off, CWM recovery, SuperSU, and the modded kernel with RW permissions. What gives? :?
EDIT: Even tried installing Adaway as system app, problem still persists...???
EDIT2: Finally got it working. Noticed in the OP in the xda thread that there is a modded version to fix problem. All good
deeznuts said:
I also have s-off, uninstalled weak sauce, then flashed through CWM supersu.zip for full root, reboot. Downloaded latest AdAway apk found here on xda forum. I then ran apk file from my download folder, hit install. Open AdAway, click on Download fiels and apply add blocking. Now it just gets stuck on Applying... with the circle going around and around for over 15 minutes straight now! Yes i gave root access when asked. Is this normal?
Nevermind. Closed app, then reopened and it did the download thing like normal. Now says successful and applied hosts sources: 4/4.
So i'm good to go now? Does this need reboot like prompted?
Click to expand...
Click to collapse
Don't need to reboot. I never have and it works fine.
123421342 said:
Don't need to reboot. I never have and it works fine.
Click to expand...
Click to collapse
Thank you
I had to install the unsecure boot image in order for AdAway to work properly. Otherwise it just hangs on applying host files.
From what I understand, just because you're s-off still doesn't mean you have full write access. The stock kernel has the write protection modules built in.
Flashing the unsecure boot image fixed all issues I was having and I'm pretty sure if you're still having problems, flashing that will help
-HTC One m8-
I'm not disputing whether or not s-off provides full write access. But, I was able to install AdAway with full functionality without installing the unsecure stock kernel. It takes a while to download all the data and install it though (maybe 5 minutes or so?). Then, I rebooted and it's working very well. No more ads!

What I do to achieve root (please help me)

For the life of me I can't figure out why I cannot achieve root thru normal means on lollipop. Currently this is what I have to do when flashing a new ROM (even this method isn't 100 percent successful every time) :
First I flash my rom
Then, if I want to use supersu to manage root, I would flash koush's superuser (that's right you aren't hallucinating, I said koush's superuser)
Then I boot the phone, get it all setup
Then i boot into recovery again and flash supersu
Then reboot
Now I have root.
If I wanted to use superuser I would just do the opposite of what I listed.
And like I said, even this doesn't always work
What the hell fire and brimstone is going on? This should not be so hard., right
DaveKid said:
For the life of me I can't figure out why I cannot achieve root thru normal means on lollipop. Currently this is what I have to do when flashing a new ROM (even this method isn't 100 percent successful every time) :
First I flash my rom
Then, if I want to use supersu to manage root, I would flash koush's superuser (that's right you aren't hallucinating, I said koush's superuser)
Then I boot the phone, get it all setup
Then i boot into recovery again and flash supersu
Then reboot
Now I have root.
If I wanted to use superuser I would just do the opposite of what I listed.
And like I said, even this doesn't always work
What the hell fire and brimstone is going on? This should not be so hard., right
Click to expand...
Click to collapse
You might wanna check Chainfire's posts about rooting Lollipop on here or G+ - it's a bit different to other Android versions
You cant use anything other that SuperSU BETA 2.27 unless you're wanting to use a permissive kernel.
http://forum.xda-developers.com/goo...basic-overview-root-options-lollipop-t2947144
EddyOS said:
You might wanna check Chainfire's posts about rooting Lollipop on here or G+ - it's a bit different to other Android versions
Click to expand...
Click to collapse
You wouldn't happen to have the direct link to it.
And, you are completely correct. I read all about it and then completely forgot that I read it and that I need to send it through ADB to the phone as opposed to flashing it. I just can't find the link in my history.
Thanks
DaveKid said:
You wouldn't happen to have the direct link to it.
And, you are completely correct. I read all about it and then completely forgot that I read it and that I need to send it through ADB to the phone as opposed to flashing it. I just can't find the link in my history.
Thanks
Click to expand...
Click to collapse
Just read the link I posted
rootSU said:
Just read the link I posted
Click to expand...
Click to collapse
Yep, I got it, thanks.

Help! I want to root my new Xperia Z5 Dual running Lollipop 32.0.A.6.152

I bought new xperia z5 dual and for some unknown reasons I am unable to find a single working thread for rootin Xperia Z5 Dual running the build 32.0.A.6.152. Please I had been an xperia user for 2 years now and I know a lot of stuff about rooting sony phones but this one is getting on my nerves now as I have many important apps that require rooting but I am unable to find any solution. Kindly help me out.
Thanks in advance
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
this worked for me and i have a E6653 instead of the usual E6603
Envious_Data said:
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
this worked for me and i have a E6653 instead of the usual E6603
Click to expand...
Click to collapse
I am following this thread before you even suggested me, but its very confusing. I have made my TA Partition Backup. Now there are few steps which are totally out of sync by the writer of this thread himself. For example.
7.Unlock your bootloader now.request keys from here.follow the guide
http://developer.sonymobile.com/unlo...r-boot-loader/
He did not even mention how to unlock the bootloader, but nontheless I found out the steps to unlock my bootloader. But there is one problem with me. When I run that fastbood unlocker command, my pc gives error. I am pasting a screenshot of that error. Kindly follow it up and suggest me the fix for it.
noob_coder said:
I am following this thread before you even suggested me, but its very confusing. I have made my TA Partition Backup. Now there are few steps which are totally out of sync by the writer of this thread himself. For example.
7.Unlock your bootloader now.request keys from here.follow the guide
http://developer.sonymobile.com/unlo...r-boot-loader/
He did not even mention how to unlock the bootloader, but nontheless I found out the steps to unlock my bootloader. But there is one problem with me. When I run that fastbood unlocker command, my pc gives error. I am pasting a screenshot of that error. Kindly follow it up and suggest me the fix for it.
Click to expand...
Click to collapse
you have to go into your developer settings of the device and click "enable oem unlock" (an odd decision to have this if you ask me)
i tried this and had to enable that open aswell for me to unlock my bootloader
Envious_Data said:
you have to go into your developer settings of the device and click "enable oem unlock" (an odd decision to have this if you ask me)
i tried this and had to enable that open aswell for me to unlock my bootloader
Click to expand...
Click to collapse
Thanks buddy. It worked like charm :good: . But you know with greater possibilities comes greater mysteries. Now since I am rooted with my phone, there are strange things happening. For example Greenify is now acting like that it doesnt have full root access even though I have allowed it through SU and it will show Greenify - No Auto Hibernation, then it mentions Pending Manual Hibernation, when I click on manual hibernation it starts to Force Stop the apps using the Apps Module of the Android OS, a thing which never happened with me on any of my rooted android phones. :silly::crying:
Second problem is that the guide which made me root the one which you also suggested me, installed TWRP recovery on my device. :crying:For some funny reasons I never liked TWRP Recoveries and wouldn't stand a chance to use it. I tried to flash XZDual Recovery, but to of no avail. Is there any workaround to remove TWRP or Flash XZDual Recovery on top of TWRP and make XZ Dual Recovery as Default Recovery.?:silly::silly:
noob_coder said:
Thanks buddy. It worked like charm :good: . But you know with greater possibilities comes greater mysteries. Now since I am rooted with my phone, there are strange things happening. For example Greenify is now acting like that it doesnt have full root access even though I have allowed it through SU and it will show Greenify - No Auto Hibernation, then it mentions Pending Manual Hibernation, when I click on manual hibernation it starts to Force Stop the apps using the Apps Module of the Android OS, a thing which never happened with me on any of my rooted android phones. :silly::crying:
Second problem is that the guide which made me root the one which you also suggested me, installed TWRP recovery on my device. :crying:For some funny reasons I never liked TWRP Recoveries and wouldn't stand a chance to use it. I tried to flash XZDual Recovery, but to of no avail. Is there any workaround to remove TWRP or Flash XZDual Recovery on top of TWRP and make XZ Dual Recovery as Default Recovery.?:silly::silly:
Click to expand...
Click to collapse
Not that I know of and given the support and useful things in twrp i'd suggest you use it although you may not like it
Reinstalling apps usually works for me half the time if they are acting odd.
Sent from my E6653 using XDA-Developers mobile app
Envious_Data said:
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
this worked for me and i have a E6653 instead of the usual E6603
Click to expand...
Click to collapse
Envious_Data said:
Not that I know of and given the support and useful things in twrp i'd suggest you use it although you may not like it
Reinstalling apps usually works for me half the time if they are acting odd.
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
Buddy I think through this tutorial either root access is not properly allowed or maybe this whole tutorial had some kind of step which made partial rooting. Strange things are happeing with some applications. For example SD MAID PRO and ROOT UNINSTALLER PRO are working with root access without any problems. But GREENIFY and now CLEAN MASTER's AUTO START UP feature (requires root access) is not working even it says CLEAN MASTER has been given root access on my device. But then it fails to toggle enable/disable STARTUP ADDS which are around 34+. Second this Greenify is not even AUTO HIBERNATING the apps which are user apps. If I run it on NON ROOT MODE it says MANUAL HIBERNATION PENDING. If I run it on ROOT MODE it says on the top "No Auto-Hibernation" and down again written "Pending Manual Hibernation".
I have tried multiple SU packages like 2.71 Beta 2.65 but same ****s going on again and again. Can you figure it out :good::fingers-crossed::fingers-crossed:
noob_coder said:
Buddy I think through this tutorial either root access is not properly allowed or maybe this whole tutorial had some kind of step which made partial rooting. Strange things are happeing with some applications. For example SD MAID PRO and ROOT UNINSTALLER PRO are working with root access without any problems. But GREENIFY and now CLEAN MASTER's AUTO START UP feature (requires root access) is not working even it says CLEAN MASTER has been given root access on my device. But then it fails to toggle enable/disable STARTUP ADDS which are around 34+. Second this Greenify is not even AUTO HIBERNATING the apps which are user apps. If I run it on NON ROOT MODE it says MANUAL HIBERNATION PENDING. If I run it on ROOT MODE it says on the top "No Auto-Hibernation" and down again written "Pending Manual Hibernation".
I have tried multiple SU packages like 2.71 Beta 2.65 but same ****s going on again and again. Can you figure it out :good::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Open the SuperSU app and check if greenify and other apps have been denied root access.
Envious_Data said:
Open the SuperSU app and check if greenify and other apps have been denied root access.
Click to expand...
Click to collapse
No way MAN. They are all allowed. I know how to check SU for Denied & Allowed Apps in its list. This is really pissing me off. Any other ideas?
noob_coder said:
No way MAN. They are all allowed. I know how to check SU for Denied & Allowed Apps in its list. This is really pissing me off. Any other ideas?
Click to expand...
Click to collapse
not sure, it doesnt make Any sense that some apps work and some dont because i followed the same tutorial and ive not had any root related issues so im out of ideas really
but first make sure that if you flash a stock kernel then use the rootkernel tool to drm patch and well obviously allow root.
Envious_Data said:
Open the SuperSU app and check if greenify and other apps have been denied root access.
Click to expand...
Click to collapse
Envious_Data said:
not sure, it doesnt make Any sense that some apps work and some dont because i followed the same tutorial and ive not had any root related issues so im out of ideas really
but first make sure that if you flash a stock kernel then use the rootkernel tool to drm patch and well obviously allow root.
Click to expand...
Click to collapse
Greenify latest version is 2.8.1 . I removed it and installed an older version 2.7.1 and it is now working automatically hibernating the unncessary apps. Now remains only CLEAN MASTER. Its working with root only I cant use toggle enabling/disabling startup adds.:silly::silly::cyclops:
Envious_Data said:
Not that I know of and given the support and useful things in twrp i'd suggest you use it although you may not like it
Reinstalling apps usually works for me half the time if they are acting odd.
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
If you are following the thread. In the android folder of the downloaded folder there are folders of twrp recovery. Replace them with your desired recovery and then make rooted kernel with rootkernel oldkernel.img newkernel.img
And then flash it
Sent from my E6633 using XDA-Developers mobile app
Does rooting void the warranty of the device? And if yes, can we get the warranty back somehow?
Yes it will surely void the warranty
You can get back only if you unroot, re flash original Rom and update via OTA
Sent from my E6633 using XDA-Developers mobile app

I want to root my pixel 2

I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
ImIntoStuff said:
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
Click to expand...
Click to collapse
TWRP is custom recovery. It's still in beta.
As far as I know, there are no custom roms. 8.1 is too new and they are still working on things.
Root with Magisk. Plenty of how to threads.
Sent from my Pixel 2 using Tapatalk
ImIntoStuff said:
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
Click to expand...
Click to collapse
Diesel_Jeremiah said:
TWRP is custom recovery. It's still in beta.
As far as I know, there are no custom roms. 8.1 is too new and they are still working on things.
Root with Magisk. Plenty of how to threads.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
TWRP actually just came out of beta with 12/12 Walleye(12/14 Taimen) build, hopefully there will be some custom roms soon... You can use the Skipsoft Android toolkit to root, unlock, flash twrp etc. Or do it manually following guides here on XDA under development section https://forum.xda-developers.com/pixel-2/development, ADB has been updated so make sure to have the latest platform tools.
Currently theres no custom ROMs at all for Pixel 2.
TWRP is a recovery.
Rooting is pretty straight-forward I studied these 2 articles/thread:
http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
The kind of confusing part is when you want to change custom kernels and update TWRP.
As the recovery, kernel and root stuff all play around in the same partition now.
Read around the forum, since you got experience you will figure it out.
bland.life said:
Currently theres no custom ROMs at all for Pixel 2.
TWRP is a recovery.
Rooting is pretty straight-forward I studied these 2 articles/thread:
http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
The kind of confusing part is when you want to change custom kernels and update TWRP.
As the recovery, kernel and root stuff all play around in the same partition now.
Read around the forum, since you got experience you will figure it out.
Click to expand...
Click to collapse
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
ImIntoStuff said:
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
Click to expand...
Click to collapse
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
ImIntoStuff said:
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
Click to expand...
Click to collapse
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
ImIntoStuff said:
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
Click to expand...
Click to collapse
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Tucker204 said:
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Oh..so the android system error always happens? Ok..it does not seem to affect anything.
I used the Skipsoft package, which does all the things. Couple snags, it only wanted to accept the beta of magisk.
I'm thinking I got it all right now. I will report back if I find a problem
Tucker204 said:
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
So rooting your Pixel 2 will invariably trigger this error message on boot, for any user?
Are there other undesirable side effects to rooting your Pixel 2 at the moment?
Thanks

Categories

Resources