Its been ages since my last Android device, it was a galaxy nexus. Anyway I recall running CM, I tried a few different roms but kept going back to CM it was moderately light but packed with tons of settings and the ability to add on what I wanted. So Iv been using the Pixel now for a few days and I am already noticing it lacks some settings I want so what roms should I give a try after rooting? Is linage really just a CM port or whats going on there? I was also looking at the Dirty Unicorn rom, hows that compare to CM?
Honestly right now the only thing Id like to do that pixel does not do is. Get a dark theme going, transparent google assistant icon, maybe even slide it over even further so its less obtrusive or just get ride of that icon all together and just slide from the left to get to the assistant/search. also get ride of the dock background, make the app drawer transparent or dark. Does anyone give an option to make the address bar in the browser work on the bottom rather than the top of the page? Android for as old of an OS as it is hasnt seemed to embrace swiping or one handed control. BB10 works great one handed but BB had to go and kill it and conform.
Thanks, Thomas
Did you but from Google or Verizon/best buy?
If you got it from Google then..
-Unlock bootloader first with fastboot
-Follow instructions from TWRP thread for TWRP installation. Basically you are using fastboot to temporarily boot into TWRP and from there you have to flash the TWRP RC 1 zip file
-I think you have to boot phone once now and then go back to twrp and flash SU 2.79 SR2 zip
Definitely read over the OPs in the TWRP and SU threads first. The only thing you have to be careful with is the SU linked in the OP is outdated. Here is the latest.
http://www.apkmirror.com/apk/chainf...elease/supersu-2-79-sr2-android-apk-download/
aholeinthewor1d said:
Did you but from Google or Verizon/best buy?
If you got it from Google then..
-Unlock bootloader first with fastboot
-Follow instructions from TWRP thread for TWRP installation. Basically you are using fastboot to temporarily boot into TWRP and from there you have to flash the TWRP RC 1 zip file
-I think you have to boot phone once now and then go back to twrp and flash SU 2.79 SR2 zip
Definitely read over the OPs in the TWRP and SU threads first. The only thing you have to be careful with is the SU linked in the OP is outdated. Here is the latest.
http://www.apkmirror.com/apk/chainf...elease/supersu-2-79-sr2-android-apk-download/
Click to expand...
Click to collapse
Sorry I was searching within the forums and got a little confused but once I did a google search I found a decent guide that cleared things up. Iam going to tackle this tomorrow So I am just trying to get all my eggs in one basket to get a running start.
Thanks for the updated SU.
I got the phone from google.
Use pure nexus ROM.
Why exactly? I've seen a review on this ROM and it just looked like stock Android.
That would get me halfway to what I want. I want a none bloated ROM with lots of setting options and maybe even some security improves if possible.
You will need to wait until more options become available. CyanogenMod, as we all know, is no more. The source can now be found under LineageOS but I don't know how soon they are going to start publishing builds and if the Pixel will be a supported device.
Pure Nexus will give you theme support to get a dark theme. TBO has a blacked out and (I think) transparent Pixel Launcher which will give you all the stuff you were wanting with the exception of the hidden assistant icon. Browser bar is another ball game though. Not sure on that one. No promises but I can take a look at the Pixel Launcher and see about removing the assistant icon.
fritzgerald said:
Pure Nexus will give you theme support to get a dark theme. TBO has a blacked out and (I think) transparent Pixel Launcher which will give you all the stuff you were wanting with the exception of the hidden assistant icon. Browser bar is another ball game though. Not sure on that one. No promises but I can take a look at the Pixel Launcher and see about removing the assistant icon.
Click to expand...
Click to collapse
Well I got the bootloader unlocked. It was hard for me as usual because I am running linux and I am not very good with linux. However once I got adb installed and fastboot installed heck one simple command unlocked the bootloader. I still need to root. There are tone of how to's on this but they are all using windows and that actually makes it harder. The one how to for linux I did find worked part of the way and then the commands no longer worked. Once I got the bootloader unlocked I tried to go back to that one.
Anyway back at it.
twilk73 said:
Well I got the bootloader unlocked. It was hard for me as usual because I am running linux and I am not very good with linux. However once I got adb installed and fastboot installed heck one simple command unlocked the bootloader. I still need to root. There are tone of how to's on this but they are all using windows and that actually makes it harder. The one how to for linux I did find worked part of the way and then the commands no longer worked. Once I got the bootloader unlocked I tried to go back to that one.
Anyway back at it.
Click to expand...
Click to collapse
So you got fastboot working.... You are all set.
Copy TWRP RC1 to your fastboot folder. Copy SU 2.79 SR2 to your phone. Fastboot BOOT twrpfilename.img Reboot into TWRP and flash SU.
TonikJDK said:
So you got fastboot working.... You are all set.
Copy TWRP RC1 to your fastboot folder. Copy SU 2.79 SR2 to your phone. Fastboot BOOT twrpfilename.img Reboot into TWRP and flash SU.
Click to expand...
Click to collapse
The bootloader says its unlocked but I never got the boot to root to work? is the "boot to root" is that actually a copy of the sailfish pixel os? I am guessing thats what that is because when I downloaded it it was specifically for the sailfish pixel.
Also which copy of twrp RC1 do I need there is one labled md5, pgp signatur and another one that just twrp. I need the .img and the zip correct?
if I type " fastboot BOOT twrp-3.0.2-0-RC1-fastboot-sailfish.img" into my terminal while in recovery I just get waiting on device message. If I type that same quote into the bootloader menu I get a help menu.
I got it. I had to type type,
cd Downloads
cd fastboot
fastboot boot twrp.img
First I renamed the img to twrp.img to make it easier and than I used the terminal to navigate to the folder it was in and then manually launched it. I imagine this is the same was what you said but I am on linux and I am not the best at linux so it was just harder for me. I should creat a how to I mean heck this was all easy in hind sight but dang it took me hours for something that only needed minutes.
So technically if I want to install a custom rom ill just have to install it onto the phone and boot into recovery and install it? I no longer have to tether the phone and use the terminal, I only have to tether to phone to transfer files?
Sorry for all the questions, thanks for all the help though. I think I got it all done now I just have to wait for a custom rom I like.
For some reason I cant find the super user zip file to flash it. I boot into twrp and go to flash and it must be invisible because the file is just not their for me to click? Is it not compatible with twrp or is there another method for installing su? I seen that you can install super user SU using the boot to root is that the only way?
Ok so I found a super user zip file and just installed it using twrp apparently twrp couldnt see the apk? Well it seemed to have work but i didnt find super user on my phone so i went to the play store to download it and it says i do not have root access and that confuses me.
The phone says the bootloader is unlocked and i have twrp recover installed plus i installed the twrp img file which i was assuming was a rooted version of the pixel os. The next step was to add Super SU but i havnt been able to do that successfully yet. So why do I not have root and what do I need to do yet?
The only thing I did not do was install root to boot, i was going threw so many different methods to unlock the bootloader and install twrp and root and I am assuming that is just a different pixel img so I skipped over that to the twrp.img. Is this what I am missing do I need to go back and flash boot to root?
All problems have been solved at this time so far. I had to delete fstab.sailfish file and then install the supersu.zip.
Thanks all and thanks deez-troy. I am sure ill have more issues down the line lol.
Related
Hi, I recently decided to root my Nexus 5 using this guide on youtube: /watch?v=J1AKqrrf-5o
But after I'm all done with the rooting process, I noticed that my Nexus 5 has lost its LTE signal. Now it onlyy uses 3G. I managed to put it back on LTE by doing: *#*#4636#*#* and changed my prefered network, but by doing so, I lost my service with T-Mobile. Can't call or send messege with LTE on.
Please help me! I'm very new to Android and rooting but this first experience is not so good. Can you tell me what went wrong? Also, I rooted using the Linux guide.
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
You might need this first. http://forum.xda-developers.com/showthread.php?p=47156064
jd1639 said:
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
danny2146 said:
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
Click to expand...
Click to collapse
That's why I have you the second link
If all else fails flash the google stock images
Agreed. A root alone should not have caused an issue with your radio unless something went incorrectly. I would ( personally ) flash Google's stock nexus images and then possibly try again. Gaining root access can be done different ways, you may need to read into other alternatives...
I don't know. I use the ChainFIre CF Auto root on Ubuntu. I did unrooted the device earlier and was able to get LTE and service to work. Though after I use this samw method again, LTE stopped working properly, so I guess something is wrong with this method. Will try the "standard" method later though, if I can get a hold of a windows computer.
Let's back track a bit. What is the goal with root? Are you wanting to keep a custom recovery? What network are you using?
If you are going to just root stock and not go for a custom rom, I'd just flash a custom recovery via fastboot then boot to recovery and flash the SuperSU zip from Chainfire. At that point, you're rooted stock. If you decide to take an OTA update then you'll just need to make sure that you have the stock recovery installed. However, it's just as easy to flash the update when one of our devs packages it as a rom zip to flash via custom recovery, if not easier really.
Frankly, at this point my knowledge about android phone is still very hazy as this is acually my first ever phone, let along rooting, but I am eager to learn. So what's wrong if I didn't get a custom recovery? I just followed the instruction that they (chainfire autoroot) have for Linux and got this. Dunno if it was something in my phone nor the root. I am on T-Mobile BTW.
Yea, I'm baffled by that method affecting anything to do with service. It should be one of the least intrusive ways to root. However, weird things happen. So where are we now? Are you still rooted with the service issues? Which update / baseband are you on? You have the correct T-Mobile APNs? Have LTE(Recommended) selected under Preferred Network Mode in Settings / More... /Mobile Networks? Shouldn't really be necessary to mess with changing stuff in the Hidden Menu in this instance.
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
danny2146 said:
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
Click to expand...
Click to collapse
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
es0tericcha0s said:
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
Click to expand...
Click to collapse
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
danny2146 said:
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
Click to expand...
Click to collapse
Ok. So at this point, I would have the SuperSU zip (contains the SuperSU app and su binary) http://download.chainfire.eu/381/SuperSU/UPDATE-SuperSU-v1.91.zip on your phone, then fastboot a custom recovery like TWRP http://techerrata.com/browse/twrp2/hammerhead (fastboot flash recovery nameofrecovery.img), boot into recovery, and flash the zip. No need to wipe anything. Should just be able to flash and go. Then open SuperSU and make sure the binary is updated.
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
danny2146 said:
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
Click to expand...
Click to collapse
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
es0tericcha0s said:
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
Click to expand...
Click to collapse
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
danny2146 said:
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
Click to expand...
Click to collapse
Just boot into recovery and see what you have.
If you used CF-Root, then it would not have installed a custom recovery. This is something that you would have done on your own and not likely to have forgotten. If you root access is working properly, I'd suggest installing TWRP from the GooManager app as it's pretty easy and no PC required.
http://teamw.in/project/twrp2/205
Then make a nandroid back up of your phone and make sure to back up the EFS folder too and save them to a safe place. You can back that up in TWRP or from the method described here:
http://forum.xda-developers.com/showthread.php?t=2514095
Let's back up here. Why do you think you need root if you have no idea what you are doing? Are you just rooting because you can or do you have a real purpose?
Sent from my Nexus 5
Hello,
I got my Google Pixel literally two days ago and I was looking around xda and other websites for root on this phone. And so far, I haven't seen anything simple. I saw that Chainfire has rooted the Pixel and Pixel XL but I read some comments saying that if you installed the OTA update, then it won't work And I unfortunately installed an OTA that was available.
It was just overall confusing to read considering this isn't my first Android phone or is this my first root.
So I was wondering if I can still root the phone I have that's running Android 7.1.
I got my phone a few days ago as well, made sure everything was entirely up to date, and then rooted two days ago without a problem. I started with the boot-to-root version and then I updated to SR5... no problems thus far!
Fastboot boot TWRP and flash the newest SuperSU in the TWRP thread. Should work fine if you want stock recovery. But, this is Google.. boot TWRP then flash the TWRP zip then flash SuperSU. Be happy. Don't take otas and update via fastboot and repeat above steps.
???? said:
I got my phone a few days ago as well, made sure everything was entirely up to date, and then rooted two days ago without a problem. I started with the boot-to-root version and then I updated to SR5... no problems thus far!
Click to expand...
Click to collapse
What's an SR5 and what's the boot-to-root method?
k.s.deviate said:
Fastboot boot TWRP and flash the newest SuperSU in the TWRP thread. Should work fine if you want stock recovery. But, this is Google.. boot TWRP then flash the TWRP zip then flash SuperSU. Be happy. Don't take otas and update via fastboot and repeat above steps.
Click to expand...
Click to collapse
So fastboot boot TWRP, then the TWRP zip and finally SuperSU?
binaryn00b said:
What's an SR5 and what's the boot-to-root method?
So fastboot boot TWRP, then the TWRP zip and finally SuperSU?
Click to expand...
Click to collapse
Yes, fastboot boot TWRP, once booted in, flash the TWRP zip (it flashes to both partitions) then flash the SuperSU zip. Reboot, profit.
k.s.deviate said:
Fastboot boot TWRP and flash the newest SuperSU in the TWRP thread. Should work fine if you want stock recovery. But, this is Google.. boot TWRP then flash the TWRP zip then flash SuperSU. Be happy. Don't take otas and update via fastboot and repeat above steps.
Click to expand...
Click to collapse
Is updating via fastboot same as nexus format?
Fastboot flash boot/system/cache(na in pixel) /recovery(?)/vendor
Asking cause there's so many new files inside the Ota zip folder.
queerquirks said:
Is updating via fastboot same as nexus format?
Fastboot flash boot/system/cache(na in pixel) /recovery(?)/vendor
Asking cause there's so many new files inside the Ota zip folder.
Click to expand...
Click to collapse
Here's a good guide: http://www.androidcentral.com/how-manually-upgrade-your-nexus
binaryn00b said:
What's an SR5 and what's the boot-to-root method?
Click to expand...
Click to collapse
If you see here there are different builds. SR3 (boot-to-root) does NOT use TWRP, so I used that and then I updated to SR5 here.
My Google Pixel will be here in a few days. I downloaded these files:
SR5-SuperSU-v2.78-SR5-20161130091551.zip
twrp-3.0.2-0-alpha2-fastboot-sailfish.img
(I also have twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip on hand in case I need it.)
Will this method work?
Copy SR5-SuperSU-v2.78-SR5-20161130091551.zip to the device
adb reboot bootloader
fastboot boot twrp-3.0.2-0-alpha2-fastboot-sailfish.img
From TWRP install the SR5 zip
I don't need TWRP for anything more than rooting (which I have always done on my Nexus devices), but I keep seeing instructions where a TWRP img is first booted, then a TWRP zip is installed. Is it necessary to install TWRP in order to root because of the new partition layout, or can I root by simply booting to TWRP?
CatThief said:
My Google Pixel will be here in a few days. I downloaded these files:
SR5-SuperSU-v2.78-SR5-20161130091551.zip
twrp-3.0.2-0-alpha2-fastboot-sailfish.img
(I also have twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip on hand in case I need it.)
Will this method work?
Copy SR5-SuperSU-v2.78-SR5-20161130091551.zip to the device
adb reboot bootloader
fastboot boot twrp-3.0.2-0-alpha2-fastboot-sailfish.img
From TWRP install the SR5 zip
I don't need TWRP for anything more than rooting (which I have always done on my Nexus devices), but I keep seeing instructions where a TWRP img is first booted, then a TWRP zip is installed. Is it necessary to install TWRP in order to root because of the new partition layout, or can I root by simply booting to TWRP?
Click to expand...
Click to collapse
You can just root by booting twrp. Don't have to flash it if you don't want to. Though it could be useful for flashing other zips and kernels.
Sent from my Pixel using Tapatalk
CatThief said:
My Google Pixel will be here in a few days. I downloaded these files:
SR5-SuperSU-v2.78-SR5-20161130091551.zip
twrp-3.0.2-0-alpha2-fastboot-sailfish.img
(I also have twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip on hand in case I need it.)
Will this method work?
Copy SR5-SuperSU-v2.78-SR5-20161130091551.zip to the device
adb reboot bootloader
fastboot boot twrp-3.0.2-0-alpha2-fastboot-sailfish.img
From TWRP install the SR5 zip
I don't need TWRP for anything more than rooting (which I have always done on my Nexus devices), but I keep seeing instructions where a TWRP img is first booted, then a TWRP zip is installed. Is it necessary to install TWRP in order to root because of the new partition layout, or can I root by simply booting to TWRP?
Click to expand...
Click to collapse
i just did this, exactly. one thing I didn't anticipate is TWRP asking me for a 'password' in order to decrypt the filesystem. I had to provide my PIN as I don't use a password. everything went fine!
poolemit said:
i just did this, exactly. one thing I didn't anticipate is TWRP asking me for a 'password' in order to decrypt the filesystem. I had to provide my PIN as I don't use a password. everything went fine!
Click to expand...
Click to collapse
Thank you for reminding me. I always keep screen lock disabled on my devices, so I assume I need to set up a PIN with the Pixel. I recall a bug in a prior version of TWRP for the Nexus 9 where there was a prompt for a password, but even after I set one up and tried again I couldn't get into recovery. It sounds like it actually works this time.
Thank you guys for all the help! I managed to successfully root my phone and install TWRP.
One thing I'm having trouble with right now is that in Titanium Backup, when I try to change the file directory, it says that I cannot access the '/' folder.
Any help?
Also, another small thing. I remember in the Pixel Launcher, instead of the date appearing next to the Google search icon, the weather would appear. I messed around with all the settings I could find, and I can't seem to change the date back to the weather. Is that something that can be changed in Nova Launcher or no? Because I'm gonna recreate the Pixel Launcher in Nova.
Hi, I rooted my a9 back in May right around when 6.0.1 came out. Long story short, my device just gave up the ghost after a nasty interaction between the screen and concrete, so now I have a new device being shipped tomorrow. I figured the first thing I'll do is let it run any updates / OTAs it might have to get it up to date then attempt to root again.
I've been looking around for the past several hours trying to determine what the correct rooting method might be now given Nougat's rollout, but I haven't come across anything truly definitive yet. If anyone could enlighten me on what I'll need to do now to root this new version I'd be very appreciative.
Thanks in advance guys!
Just got the phone today and updated to 7.0 (software version 2.18.651.2) Still searching around and not seeing a definitive answer on whether or not the old method for rooting works for this or not. I'm hesitant to attempt it without knowing, so any advice would be greatly appreciated.
Last time I rooted, I used Windroid toolkid to unlock the bootloader, flash TWRP and apply SU. I'm wondering, would the same program work if I replaced the recovery.img file in the Data folder with the TWRP 3.0.3 unofficial recovery I saw floating around in here for nougat?
txag2011 said:
Just got the phone today and updated to 7.0 (software version 2.18.651.2) Still searching around and not seeing a definitive answer on whether or not the old method for rooting works for this or not. I'm hesitant to attempt it without knowing, so any advice would be greatly appreciated.
Last time I rooted, I used Windroid toolkid to unlock the bootloader, flash TWRP and apply SU. I'm wondering, would the same program work if I replaced the recovery.img file in the Data folder with the TWRP 3.0.3 unofficial recovery I saw floating around in here for nougat?
Click to expand...
Click to collapse
You can unlock it on the HTCDEV website, although if you've already got it unlocked I doubt you need to do it again. To root I just ADB fastboot flashed TWRP 3.0.3-4, then used that to flash Magisk, mounting system read only. I'm fairly sure some people are using Su on Nougat, so it'll probably work.
Never used the Windroid toolkit so I can't comment on that, but I've also never minded typing commands to the prompt. I'd imagine if you gave it the right TWRP it'd flash it OK..
JohnRogers23 said:
You can unlock it on the HTCDEV website, although if you've already got it unlocked I doubt you need to do it again. To root I just ADB fastboot flashed TWRP 3.0.3-4, then used that to flash Magisk, mounting system read only. I'm fairly sure some people are using Su on Nougat, so it'll probably work.
Never used the Windroid toolkit so I can't comment on that, but I've also never minded typing commands to the prompt. I'd imagine if you gave it the right TWRP it'd flash it OK..
Click to expand...
Click to collapse
That actually doesn't sound too bad; From that it seems like the process is still more or less the same. Why is the system mounted as read only though? After looking through most of the older step by step guides it doesn't mention anything about doing that. From what I see, after i run the command "fastboot flash recovery recovery.img" i boot into TWRP and then proceed to do a factory reset and wipe the cache, presumably to remove the encryption iirc, then install the supersu.zip is that still the correct procedure, or does this require mounting the system as read only now?
If you don't mind me asking, what steps exactly did you take to root yours? from what I've found all I need to do is get the bootloader unlocked with the steps from HTCDev, drop into download more, fastboot flash recovery recovery.img to get TWRP, boot into TWRP, run a format to get rid of the encryption, then install supersu.zip and that should be it. IS this correct or am I missing something?
I'm about to start the process trying to root using the above methods.. I'll post again when I have results.
txag2011 said:
That actually doesn't sound too bad; From that it seems like the process is still more or less the same. Why is the system mounted as read only though? After looking through most of the older step by step guides it doesn't mention anything about doing that. From what I see, after i run the command "fastboot flash recovery recovery.img" i boot into TWRP and then proceed to do a factory reset and wipe the cache, presumably to remove the encryption iirc, then install the supersu.zip is that still the correct procedure, or does this require mounting the system as read only now?
If you don't mind me asking, what steps exactly did you take to root yours? from what I've found all I need to do is get the bootloader unlocked with the steps from HTCDev, drop into download more, fastboot flash recovery recovery.img to get TWRP, boot into TWRP, run a format to get rid of the encryption, then install supersu.zip and that should be it. IS this correct or am I missing something?
Click to expand...
Click to collapse
It wasn't bad at all. The reason I mounted R/O is because I'm using Magisk and not disabling dm-verity. I'm not sure if it works the same on 7, but SuperSu should disable dm-verity, so if you're using it you might not need to mount R/O, I haven't been keeping up on that at all. Benefits of Magisk include Android Pay and being able to take an OTA.
That all sounds like exactly what you need to do, except I believe it's fastboot mode (the one with the black screen?) to flash TWRP. I also didn't have to format anything, but I believe you do if you're using Su and disabling forced encryption. You may want to take a system image backup before you change anything, so you can go back to stock and get an OTA, or in case something goes wrong, but other than that it sounds correct to me.
JohnRogers23 said:
It wasn't bad at all. The reason I mounted R/O is because I'm using Magisk and not disabling dm-verity. I'm not sure if it works the same on 7, but SuperSu should disable dm-verity, so if you're using it you might not need to mount R/O, I haven't been keeping up on that at all. Benefits of Magisk include Android Pay and being able to take an OTA.
That all sounds like exactly what you need to do, except I believe it's fastboot mode (the one with the black screen?) to flash TWRP. I also didn't have to format anything, but I believe you do if you're using Su and disabling forced encryption. You may want to take a system image backup before you change anything, so you can go back to stock and get an OTA, or in case something goes wrong, but other than that it sounds correct to me.
Click to expand...
Click to collapse
huh... Magisk can utilize android pay and OTA's? I'm a little bit intrigued.. I just might have to give that a quick look now. Was it difficult to get up and running, and is there a fairly decent guide for doing it?
txag2011 said:
huh... Magisk can utilize android pay and OTA's? I'm a little bit intrigued.. I just might have to give that a quick look now. Was it difficult to get up and running, and is there a fairly decent guide for doing it?
Click to expand...
Click to collapse
Magisk is a framework for systemlessly modifying /system, so safety net works and you can take an OTA (with stock recovery), and also includes root. It's brilliant, but not quite as powerful as Xposed. Not difficult at all to get running, all it needs is to flash the magisk installer zip in TWRP (system mounted R/O of course) and then install the Magisk Manager app from the play store.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
JohnRogers23 said:
Magisk is a framework for systemlessly modifying /system, so safety net works and you can take an OTA (with stock recovery), and also includes root. It's brilliant, but not quite as powerful as Xposed. Not difficult at all to get running, all it needs is to flash the magisk installer zip in TWRP (system mounted R/O of course) and then install the Magisk Manager app from the play store.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
I might give this a shot then, thank you for that. I'm about to try flashing TWRP 3.0.3-0. From the looks of it this is the most current one available. I'll update when it's done
txag2011 said:
I might give this a shot then, thank you for that. I'm about to try flashing TWRP 3.0.3-0. From the looks of it this is the most current one available. I'll update when it's done
Click to expand...
Click to collapse
Go to the TWRP thread, hit the download tab, pick one of the newer ones there. I went with 3.0.3.-4.
JohnRogers23 said:
Go to the TWRP thread, hit the download tab, pick one of the newer ones there. I went with 3.0.3.-4.
Click to expand...
Click to collapse
Did just that. Got TWRP installed successfully. I PM'ed you a second ago but I might as well ask this here for everyone else to see in case someone else is wondering this too.... So if I'm understanding Magisk correctly, all I do now is hit install and choose Magisk v11.1?
Edit: I did just that, but it doesnt seem to have done anything.. I dont see and magisk apps, and root checker says i'm not rooted.. Did I miss something?
edit 2: scratch that... I just installed the magisk manager app from the playstore.. according to it, the latest version of magisk is in fact, installed, and it's rooted with magisksu (despite not showing so in rootchecker).. Little confused now. Is that everything that needs to be done?
edit 3: I went back in after seeing something mentioning installing phh's superuser via TWRP and installing the app after installing magisk. Did both, but noticed safety net wasn't passing. found an option in settings to hide magisk, which seems to fix that. I also ran root checker again and it shows I have root.
unless I missed anything you can think of I think that about finishes things. If thats it thank you for all the help @JohnRogers23
txag2011 said:
Did just that. Got TWRP installed successfully. I PM'ed you a second ago but I might as well ask this here for everyone else to see in case someone else is wondering this too.... So if I'm understanding Magisk correctly, all I do now is hit install and choose Magisk v11.1?
Edit: I did just that, but it doesnt seem to have done anything.. I dont see and magisk apps, and root checker says i'm not rooted.. Did I miss something?
edit 2: scratch that... I just installed the magisk manager app from the playstore.. according to it, the latest version of magisk is in fact, installed, and it's rooted with magisksu (despite not showing so in rootchecker).. Little confused now. Is that everything that needs to be done?
edit 3: I went back in after seeing something mentioning installing phh's superuser via TWRP and installing the app after installing magisk. Did both, but noticed safety net wasn't passing. found an option in settings to hide magisk, which seems to fix that. I also ran root checker again and it shows I have root.
unless I missed anything you can think of I think that about finishes things. If thats it thank you for all the help @JohnRogers23
Click to expand...
Click to collapse
I'm glad you got it working. Strange you had to flash phh's Su separately though. Anyway, glad I could help.
Well Working !
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system and enter into Recovery TWRP..
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3 via TWRP.. Finally Reboot into system..
*2 bootloops are common, do not give up for at least 3 bootloops..
*It will take a long time to boot as you have done a factory reset.. So be patient and wait for at least half hour..
Dr.Anshuman said:
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system and enter into Recovery TWRP..
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3 via TWRP.. Finally Reboot into system..
*2 bootloops are common, do not give up for at least 3 bootloops..
*It will take a long time to boot as you have done a factory reset.. So be patient and wait for at least half hour..
Click to expand...
Click to collapse
Thanks! I got it more or less and went with magisk. Couldn't pass up a chance to have root and still get OTAs and use android pay. I'm still monkeying around trying to figure out how to use it to get liveboot back up and running.
Greetings to anyone that may see this - I am new to the android root thingy, so I apologize in advance if I have a stupid question. I have only rooted an old tablet with Kingoroot which used SuperSU as the root manager. First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.) I tried the regular guacamole image, but the phone didn't seem to want to boot the image. I am going to try guacamoleb. If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
UrAverageNerd said:
First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.)
Click to expand...
Click to collapse
Haven't seen guacomoleb (different code name to me implies a different device, but I'm not sure in this case). Just use the file from the dev's TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Unofficial version -75 is the current version. Use the version ( Q versus Pie) for your current Android/OOS version. Might be obvious, but some folks have asked about that.
UrAverageNerd said:
If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
Click to expand...
Click to collapse
Per the developer in his thread I linked above, for a stock device, if you flash TWRP, you should root (with Magisk) or the phone might not boot. Some folks have reported that they can flash TWRP and not Magisk and still boot. But there is not point in risking it, since your intent is to root anyway. Fastboot boot TWRP img, then flash TWRP installer zip, and just flash Magisk right away at the same time, then reboot. It's pretty easy.
Also note that installing TWRP is somewhat optional. You can just fastboot boot TWRP img, then flash Magisk to root. It is a matter of preference whether to have TWRP installed or not, and folks are pretty split on this. My opinion, TWRP installed (while not required) does give some potentially useful features if things ever go wrong. I personally don't see much advantage to not installing TWRP, but just my opinion.
Hi there. I ran into similar problems when I was a Root noobie (which I still am). Try the All In One Tool that can be found in this forum. That will help you flash TWRP. It got me there when I was struggling to Flash TWRP.
redpoint73 said:
Haven't seen guacomoleb (different code name to me implies a different device, but I'm not sure in this case). Just use the file from the dev's TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Unofficial version -75 is the current version. Use the version ( Q versus Pie) for your current Android/OOS version. Might be obvious, but some folks have asked about that.
Per the developer in his thread I linked above, for a stock device, if you flash TWRP, you should root (with Magisk) or the phone might not boot. Some folks have reported that they can flash TWRP and not Magisk and still boot. But there is not point in risking it, since your intent is to root anyway. Fastboot boot TWRP img, then flash TWRP installer zip, and just flash Magisk right away at the same time, then reboot. It's pretty easy.
Also note that installing TWRP is somewhat optional. You can just fastboot boot TWRP img, then flash Magisk to root. It is a matter of preference whether to have TWRP installed or not, and folks are pretty split on this. My opinion, TWRP installed (while not required) does give some potentially useful features if things ever go wrong. I personally don't see much advantage to not installing TWRP, but just my opinion.
Click to expand...
Click to collapse
Thanks for your help. Apparently the Android Q unofficial build -75 doesn't have any mirrors. It's still searching. I like using TWRP because it's convenient if I wan't to flash something else without a PC or Mac.:laugh:
UrAverageNerd said:
Apparently the Android Q unofficial build -75 doesn't have any mirrors. It's still searching.
Click to expand...
Click to collapse
Something wrong with the "main" download link (androidfilehost)?
UrAverageNerd said:
Greetings to anyone that may see this - I am new to the android root thingy, so I apologize in advance if I have a stupid question. I have only rooted an old tablet with Kingoroot which used SuperSU as the root manager. First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.) I tried the regular guacamole image, but the phone didn't seem to want to boot the image. I am going to try guacamoleb. If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
Click to expand...
Click to collapse
Use adb & fastboot via powershell
Get the adb files in a folder
Copy the twrp.img to the adb folder and on phone /storage/emulated/0/
Get a copy of the twrp installer on your phone anywhere works
Open adb folder
Hold shift and right click a empty space
Open powershell & type
Adb boot bootloader
Fastboot boot twrp.img (you can drag and drop the file into powershell if your lazy like me)
Flash the twrp installer on your phone
Done?
Reboot and go back into recovery to see if it works
Tip for updates:
After you get the update
Flash via twrp
Then flash twrp (so you don't need your computer)
Flash magisk if you want superuser
Reboot
Reboot recovery
Flash magisk again (seems it takes two flashes)
None of the tools work for my devices anymore just powershell
All in one doesn't read my fastboot
Cmd has a remote error after attempting to boot it.
UrAverageNerd said:
First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.)
Click to expand...
Click to collapse
Just noticed that the TWRP "guacomoleb" is the "unified" version that works with both the OnePlus 7 and the 7 Pro. Shouldn't make a difference whether you use the "unified" version or the 7 Pro specific TWRP.
Hey y'all,
I'm switching back to Android after 3 years on iOS and I'm a bit stuck on some changes.
First off, battery life on OOS was terrible and they ended support for OP7Pro this year, with no more major (or even security updates) so I decided to get a custom ROM, and I got this Pixel Experience ROM from here. I'm stuck with a few things:
Trying to root it, looks like the procedure is as simple as patch the boot image in that link with Magisk and flash it from the bootloader via "fastboot flash boot patched.img" but every time I do that and reboot, I get the 1+ splash screen and then nothing, black screen. If I boot back in bootloader and flash the original boot image via "fastboot flash boot original.img" it boots again. Same happens if I just run "fastboot boot patched.img", completely black until I reboot. Does anyone know what could be going wrong here?
Is there any way to install TWRP and make a NAND backup with this ROM? I've been out of the game for a while and I'm confused about why there's no recovery partition but there's A and B partitions, and I keep reading that TWRP can't decrypt data or something like that (I'm pretty sure it could 3 years ago tho)
Thanks!
I would never switch to an iphone for a personal phone because I can't stand it.
I have'nt had to root op7 pro till now because I had enough options. now with support ending I'm on 12.
If you have already upgraded to 12 like me you will probably have to downgrade to 11 first to unlock the bootloader if you haven't unlocked it already. I will not try till may when I get back from my vacation because I can't afford for the phone to go crazy right now. before you attempt to downgrade if you do make sure you back up everything to another spare phone or tablet and make sure you have a backup plan in case you soft brick before you attempt it. https://droidwin.com/downgrade-oneplus-7-7t-7t-pro-android-12-to-android-11-2-methods/ . Man if there is a new way to not have to first downgrade to android 11 someone please chime in, as it would reduce my headaches. Also I need someone to clarify if after I unlock the bootloader, I'll have to flash back to 12 via twrp and reformat the phone again to install Pixel experience?
dragancla said:
boot image in that link
Click to expand...
Click to collapse
That is probably where the problem is.
Which boot image to use depends on exactly which OS version you’re using, and the exact model number of your device.
A lot has changed in the Android world in the last 3 years.
TheMystic said:
That is probably where the problem is.
Which boot image to use depends on exactly which OS version you’re using, and the exact model number of your device.
A lot has changed in the Android world in the last 3 years.
Click to expand...
Click to collapse
Yeah, but that IS the boot image for that OS version and that device, that's why you can download both the ROM and the boot image for that ROM from the same link I posted. If I boot that specific image the device works fine. If I patch that same boot image and boot it, it doesn't work.
dragancla said:
Yeah, but that IS the boot image for that OS version and that device, that's why you can download both the ROM and the boot image for that ROM from the same link I posted. If I boot that specific image the device works fine. If I patch that same boot image and boot it, it doesn't work.
Click to expand...
Click to collapse
Then it means that the patching is not happening properly. Something is not right with the patched image, even if you don't get any errors. Search for this problem on Google. Also see if you can extract the boot image of your device yourself, instead of using the one you have in that link.
billperrotta said:
I would never switch to an iphone for a personal phone because I can't stand it.
I have'nt had to root op7 pro till now because I had enough options. now with support ending I'm on 12.
If you have already upgraded to 12 like me you will probably have to downgrade to 11 first to unlock the bootloader if you haven't unlocked it already. I will not try till may when I get back from my vacation because I can't afford for the phone to go crazy right now. before you attempt to downgrade if you do make sure you back up everything to another spare phone or tablet and make sure you have a backup plan in case you soft brick before you attempt it. https://droidwin.com/downgrade-oneplus-7-7t-7t-pro-android-12-to-android-11-2-methods/ . Man if there is a new way to not have to first downgrade to android 11 someone please chime in, as it would reduce my headaches. Also I need someone to clarify if after I unlock the bootloader, I'll have to flash back to 12 via twrp and reformat the phone again to install Pixel experience?
Click to expand...
Click to collapse
I already have Pixel Experience installed, so my bootloader is unlocked. Has been since I bought the phone 3 years ago
TheMystic said:
Then it means that the patching is not happening properly. Something is not right with the patched image, even if you don't get any errors. Search for this problem on Google. Also see if you can extract the boot image of your device yourself, instead of using the one you have in that link.
Click to expand...
Click to collapse
Google yielded no results, decided to post here to see if anyone else ran into this, I'll try to extract it myself somehow.
Coming out of left field but maybe you need to return to stock with bootloader unlocked. Flash 12 ota then rewipe for PE to get 12 latest firmware? https://www.xda-developers.com/oneplus-7-7t-end-of-life-final-update/
used to flash otas through TWRP when I had a rooted op5T with an unlocked bootloader. So Sad, Oxygen was so good till this last crummy update. Now they are forcing my hand to return to custom roms since OP insists on abandoning Support for the best phone they ever made.
Nothing worked, so I fixed it by wiping the phone and starting from scratch. Guess something bugged out.
thats usually the end all solution. but I have seen situations where you have to be on latest stock firmware to continue. I assume you don't have to copy any partitions because this software is already past Android 10 where treble was first introduced? I'm just asking as many questions as possible because I'm planning to overhaul in may. Did you use the pixel experience flashing instructions from pixel experience.org?
ill probably flash the ota back to twelve through twrp. then flash pixel experience recovery over that when I wipe and start over after the downgrade and bootloader unlock.
billperrotta said:
thats usually the end all solution. but I have seen situations where you have to be on latest stock firmware to continue. I assume you don't have to copy any partitions because this software is already past Android 10 where treble was first introduced? I'm just asking as many questions as possible because I'm planning to overhaul in may. Did you use the pixel experience flashing instructions from pixel experience.org?
Click to expand...
Click to collapse
I was on latest stock (12) before I started doing this. Had my bootloader unlocked since Android 9. Since it's impossible to do anything without unlocking it, that's your first step. I posted the link to PE website in my first post. Didn't copy any partitions. I just installed it and rooted it with a few commands from terminal (with the phone connected):
adb reboot bootloader
fastboot flash boot BOOT.img
fastboot reboot recovery
-- on the phone: wipe data, select install from sideload --
adb sideload ROM.zip
adb reboot
-- on the phone: wait for it to boot, enable developer options --
adb install MAGISK.apk
adb push BOOT.img sdcard/Download
-- on the phone: patch the boot image with Magisk --
adb pull sdcard/Download/magisk_patched-25200_xxxxx.img
adb reboot bootloader
fastboot flash boot magisk_patched-25200_xxxxx.img
fastboot reboot
That's it, installed and rooted. Stop at step 6 if you don't want root.