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
I had rooted Nexus 5 with franco.kernel. Reverted back to stock kernel and flashed the OTA zip. Everything went perfectly and updated to 4.4.3, but unfortunately lost recovery and root access.
I tried to regain root by running CF auto root kit. No luck whatsoever. I can't flash TWRP, because everytime I type fastboot flash recovery recovery.img - it says it can't open recovery.img. The recovery.img is in the platform-tools folder, I am certain I did nothing wrong.
Can anyone give me a hand with this?
EDIT- You may delete this thread. Seems like the problem was that SuperSU didn't get installed but after downloading it from play store everything shows up as rooted now. Thanks.
ColdFire InOx said:
I had rooted Nexus 5 with franco.kernel. Reverted back to stock kernel and flashed the OTA zip. Everything went perfectly and updated to 4.4.3, but unfortunately lost recovery and root access.
I tried to regain root by running CF auto root kit. No luck whatsoever. I can't flash TWRP, because everytime I type fastboot flash recovery recovery.img - it says it can't open recovery.img. The recovery.img is in the platform-tools folder, I am certain I did nothing wrong.
Can anyone give me a hand with this?
EDIT- You may delete this thread. Seems like the problem was that SuperSU didn't get installed but after downloading it from play store everything shows up as rooted now. Thanks.
Click to expand...
Click to collapse
Ha,don't feel bad I spent 4hrs working on my.phone then all of a sudden it wouldn't take adb commands...Turns out I had to change my USB cable..
I have my M8 with S-OFF (Paid for Sunshine) and it is temporarily rooted with KingRoot. I'm just confused on what I need to do next to get fully rooted so I can start flashing some ROMS! I tried to install TWRP with the app but it doesn't seem to work and it just boots into the standard recovery mode and NOT TWRP.
So, where do I go after having S-OFF and temp root?
I would greatly appreciate anybodies help here, I've rooted several devices before but nothing has been harder or more confusing then rooting the m8 on 5.0.1!
Thanks in advance!
MTN927 said:
I have my M8 with S-OFF (Paid for Sunshine) and it is temporarily rooted with KingRoot. I'm just confused on what I need to do next to get fully rooted so I can start flashing some ROMS! I tried to install TWRP with the app but it doesn't seem to work and it just boots into the standard recovery mode and NOT TWRP.
So, where do I go after having S-OFF and temp root?
I would greatly appreciate anybodies help here, I've rooted several devices before but nothing has been harder or more confusing then rooting the m8 on 5.0.1!
Thanks in advance!
Click to expand...
Click to collapse
Flash twrp with fastboot and push/flash SuperSU in twrp.
--beaups
Sent from my XT1254 using Tapatalk
I'm having trouble finding some good directions on that stuff...
I'm trying to run the WinDroid program to flash twrp, it reboots the phone into fastboot but then WinDroid just says rebooting device and doesn't seem to get passed that. Should I just wait?
MTN927 said:
I'm trying to run the WinDroid program to flash twrp, it reboots the phone into fastboot but then WinDroid just says rebooting device and doesn't seem to get passed that. Should I just wait?
Click to expand...
Click to collapse
Shouldn't use apps like that. Just flash it with fastboot manually.
Sent from my XT1254 using Tapatalk
beaups said:
Shouldn't use apps like that. Just flash it with fastboot manually.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
This is where I'm not finding any good directions for these steps, as far as how to do the command prompts.
OK finally got TWRP installed, can I flash SU from the SU app?
You flash SuperSU from within twrp.
Sent from my XT1254 using Tapatalk
MTN, I know this can be frustrating for a newbie. There are plenty of walkthroughs, and I'm sure everyone else will tell you to google, but for the sake of being concise, here's the scoop:
1. Make sure you have ADB installed.
2. Go to your ADB prompt and make sure your device is showing up (need the HTC drivers installed) by doing:
adb devices
3. Reboot into fastboot:
adb reboot bootloader
4. Flash TWRP:
fastboot flash recovery twrp####.zip
5. Once you've got TWRP installed, you reboot INTO TWRP (full recovery) and let it patch your system because if you don't it will be overwritten. As follows:
- Reboot with VolDwn held.
- From bootloader, pick "recovery".
- Wait for TWRP to come up.
6. Once TWRP is in, drop supersu package ZIP (get the latest one, careful here!) into a directory, boot into TWRP, and install it.
Boom, your device is completely rooted.
But I think that the thing that you need to understand is that "rooted" only applies to the current ROM. Rooting isn't a magic thing - it simply means that you have root privilege on the current OS. It is separate from firmware, bootloader, etc. which all also have to be flashed/loaded/updated depending on what you are doing. There probably ought to be a newbie page somewhere that explains to people what each thing is. The ROM is essentially the same as whatever version of windows/linux/etc. you have on your home computer. It has nothing to do with the hardware, the firmware, or the bootloader.
On my phone, I followed the above procedure, but then proceeded to download and install a clean ROM that was pre-rooted. Then later I put back the stock Verizon ROM and had to reapply root. I then later removed root to return the phone to verizon for service. But I didn't uninstall Root, I simply flashed on a non-rooted ROM.
Does that make sense?
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Edit: CHECK THE COMMENTS FOR SOLUTION
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Ok, stop freaking, this is very fixable. Assuming you have the Google version, or the Verizon version unlocked.
Short answer, we are going to get it into fastboot mode and we are going to flash you back to stock and probably save your data.
First, we need to make sure you have the correct version of Fastboot/ADB. It must be from GOOGLE.
https://developer.android.com/studio/releases/platform-tools.html
Unzip that onto a spot on your desktop.
Then go here and download the latest image for the Pixel. I am assuming you are in the US, get 7.1.1 (NOF26V, Feb 2017) for the Pixel.
https://developers.google.com/android/images#sailfish
Unzip that into a the Platform folder you made above with the fastboot tools. When you are all done it should look like the picture below. The highlighted items are the items that came from the Factory Image you extracted in step two. Everything else is from the platform tools.
Now RIGHT click 'flash-all.bat' and edit it. Near the end...look for the -w and take it out and save it. Removing that is what is going to save your data.
Power down your phone, restart it in bootloader mode. Power and Vol Down. Connect it to your computer and then double click 'flash-all.bat'.
That will take you back to stock unlocked and all your data and settings will be there.
Get past that and let us know. Then we will get you properly rooted. Yea, you used the wrong root process.
I love you <3
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
AlexCoetzee said:
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
Click to expand...
Click to collapse
You are most welcome. Do you need help rooting now?
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
No thank you! I figured that out pretty quickly with TWRP and I am happily rooted now Quite a different process after jailbreaking iOS for 8 years. Thanks for your help!
Misterxtc said:
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
Click to expand...
Click to collapse
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Tulsadiver said:
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Click to expand...
Click to collapse
Good to see you here too. It feels great to be free of TouchWiz!!
Misterxtc said:
Good to see you here too. It feels great to be free of TouchWiz!!
Click to expand...
Click to collapse
And how. I'm done with Samsung.
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
stpbby said:
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
Click to expand...
Click to collapse
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Thanks! That worked.
I need help with unlocking bootloader and rooting phone
TonikJDK said:
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Click to expand...
Click to collapse
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If your on Verizon, no, you can't unlock the bootloader
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If it is a Verizon phone, no you can't unlock it. If it is a Google phone to unlock...below is a decent link on how to. Except use the ADB Fastboot tools I link to in the third post of this thread.
https://android.gadgethacks.com/how-to/unlock-bootloader-your-google-pixel-pixel-xl-0174627/
And be aware, when you unlock it...it will wipe all the data on your phone.
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
moeREM said:
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
Click to expand...
Click to collapse
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
TonikJDK said:
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
Click to expand...
Click to collapse
I think so, but am not 100% sure. Was bought unlocked from a retail shop. (Sorry, am a bit of a newb!)
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
TENN3R said:
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
Click to expand...
Click to collapse
I'm having bootloops at the initial white google logo screen with SR3-SuperSU-v2.79-SR3-20170114223742.zip flash method on 7.1.2-May
Re: https://theunlockr.com/2017/02/01/root-google-pixel-pixel-xl/2/
Hello. I recently tried to use Magisk Manager to root my phone using a step by step walk through. It worked, everything was great, I finally was able to get my mobile data to turn off automatically when I connected to Wi-Fi. Goal achieved. Hooray. But then a new update came out for the Pixel 2 XL, I believe what is called OTA? See how new I am, it's pathetic. Anyway, I can't get the OTA installed because I have Magisk. I found a good walk through to how to fix it github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips BUT when I go to uninstall Magisk and restore images, it says "stock backup does not exist". Guys. I'm in over my head and I don't know what to do to fix it. Can any one explain in simple language, maybe with pictures, so my idiot self can understand, how do I get a stock back up, and get Magisk to recognize it, so that I can proceed to install the OTA? Thank you so much for any advice,and your patience for dealing with me.
Megin said:
Hello. I recently tried to use Magisk Manager to root my phone using a step by step walk through. It worked, everything was great, I finally was able to get my mobile data to turn off automatically when I connected to Wi-Fi. Goal achieved. Hooray. But then a new update came out for the Pixel 2 XL, I believe what is called OTA? See how new I am, it's pathetic. Anyway, I can't get the OTA installed because I have Magisk. I found a good walk through to how to fix it github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips BUT when I go to uninstall Magisk and restore images, it says "stock backup does not exist". Guys. I'm in over my head and I don't know what to do to fix it. Can any one explain in simple language, maybe with pictures, so my idiot self can understand, how do I get a stock back up, and get Magisk to recognize it, so that I can proceed to install the OTA? Thank you so much for any advice,and your patience for dealing with me.
Click to expand...
Click to collapse
Search the forum, there are a lot of walk through threads.
You won't remove anything, IE Magik.
Download the Factory Image, OTA will not work.
You'll remove "-w" from one file to not wipe data.
Flash update.
Reroot with Magisk.
If you have problems finding the links or threads, I can link them.
Sent from my Pixel 2 using Tapatalk
What diesel said, it isn't really that hard ?.
Nathanchanche made a really good guide for us. Take your time to read it really well and you should be able to solve your problem.
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
In my experience, if rooted, don't use OTAs. Stick with factory images if possible.
Like other responses, it's best to use the guides on XDA. I usually do the following when an update is available:
- Download factory image
- Edit batch file (if you're using Windows) to remove the -w option so I don't lose my data
- Boot into bootloader (power off phone, then hold down power and volume down until you get to the bootloader)
- Run batch file (I have had issues on occasion with this). If you get an error, try using a different USB cable
- After factory image is installed, let phone reboot.
- After rebooting and device is fully ready to go, reboot back to bootloader.
- Install latest TWRP (follow instructions on their website...the steps they have works perfectly)
- After TWRP is installed, reboot phone back to bootloader and then go to the 'recovery' option. Make sure TWRP is working correctly and you can decrypt your data (that is, if you have a security password)
- After decrypted, you should be able to access your data where you've downloaded Magisk. You can then install Magisk.
- After install, reboot phone and you should be rooted.
These steps work for me, but I'm a bit anal when it comes to updates and rooting.
pgarlinski said:
In my experience, if rooted, don't use OTAs. Stick with factory images if possible.
Like other responses, it's best to use the guides on XDA. I usually do the following when an update is available:
- Download factory image
- Edit batch file (if you're using Windows) to remove the -w option so I don't lose my data
- Boot into bootloader (power off phone, then hold down power and volume down until you get to the bootloader)
- Run batch file (I have had issues on occasion with this). If you get an error, try using a different USB cable
- After factory image is installed, let phone reboot.
- After rebooting and device is fully ready to go, reboot back to bootloader.
- Install latest TWRP (follow instructions on their website...the steps they have works perfectly)
- After TWRP is installed, reboot phone back to bootloader and then go to the 'recovery' option. Make sure TWRP is working correctly and you can decrypt your data (that is, if you have a security password)
- After decrypted, you should be able to access your data where you've downloaded Magisk. You can then install Magisk.
- After install, reboot phone and you should be rooted.
These steps work for me, but I'm a bit anal when it comes to updates and rooting.
Click to expand...
Click to collapse
Ok what am I doing wrong here? prntscr.com/iqefpd
Megin said:
Ok what am I doing wrong here? prntscr.com/iqefpd
Click to expand...
Click to collapse
You need to install fastboot. Download plataform tools from the Android SDK and try again.
Megin said:
Ok what am I doing wrong here? prntscr.com/iqefpd
Click to expand...
Click to collapse
Follow the full tutorial in my signature, it will cover all the steps in detail.
Megin said:
Ok what am I doing wrong here? prntscr.com/iqefpd
Click to expand...
Click to collapse
As said previously you need fastboot.exe. Download from https://dl.google.com/android/repository/platform-tools-latest-windows.zip.
Extract everything to folder that contains your extracted image. If the fastboot.exe is still not recognized:
one option is to modify flash-all.bat line: PATH=%PATH%;"%SYSTEMROOT%\System32"; to PATH=%PATH%;"%SYSTEMROOT%\System32";"%cd%"
Telperion said:
Follow the full tutorial in my signature, it will cover all the steps in detail.
Click to expand...
Click to collapse
Worked!! Thanks