Related
Hi,
I am a Canadian Newbie to Android and just purchased a Nexus S from Fido. I tried to Unlock and Root my phone using this guide
http://forum.xda-developers.com/showthread.php?t=970237
As I have a Mac, but got stuck on the 5th instruction. I rebooted my phone and now can't get my data connection. I am left scratching my head what I did wrong. Thank goodness I didn't brick the phone, but I need to find a way to get this working or least take me back to where I started.
Any assistance would be great,
I got back my data connection and the phone is unlocked. I just want some assistance with the rooting process.
I don't have a MAC, so i'm not sure how you would proceed. However, if you have access to a Windows based PC, follow the instructions for the i9023 phone to unlock the i9020a version of the device.
The issue with Fastboot is related to drivers and in windows, there is a bug in the driver INF file, so read the instructions carefully.
If it is already unlocked, you should be able to reboot back into recovery, flash clockwork and install superuser (without rebooting)
I would first boot into recovery and resume from step 6 in the guide you were going through..
Basically you want to get clockwork flashed so that way you can install the superuser zip file from the SD Card...
So I need continue to follow these instructions? When I open terminal and put in step 6 nothing happens, that's why I stopped in the first place. Sorry to be a pain, but I am really new to this platform.
6) Copy/paste the following into the Terminal window:
Code:
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery-clockwork-3.0.0.5-crespo.img
Hit "Return" again and wait for recovery to boot.
For the following steps while in Recovery, use "Volume Down" to highlight a selection and "Power" to choose that selection:
8) Choose "mounts and storage"
9) Choose "mount USB storage". Your phone should now be mounted on the Mac as a Device called "NO NAME"
10) Move the zip file "su-2.3.6.1-ef-signed.zip" from the "adb-fastboot" folder to the "NO NAME" Device on you computer.
11) Eject/unmount your phone in the Finder on your Mac.
12) On your phone, choose "Unmount"
13) Choose "mount /system"
14) Choose "+++++Go Back+++++"
15) Choose "install zip from sdcard"
16) Choose "choose zip from sdcard"
17) Choose "su-2.3.6.1-ef-signed.zip"
Is there anyone on this forum who lives in Toronto and is willing to meet up to show me how to do this? Please let me know.
Thanks!
if you are running fastboot your phone must be on the bootloader menu.
so, turn off your phone. press volume up and power. don't enter recovery.
while in this state, continue with step 6:
fastboot flash recovery crespo.img and then enter recovery (now with clockwork)
while in recovery, mount sdcard (menus), adb push su.zip and adb push any_rom.zip (like cm7.zip) and then, back on the phone, install zip from sdcard, choose zip... (still from recovery). install what you need. reboot. you're done.
After typing in the commands for step 6, if the terminal says something like 3042 kbs/sent in or out (not exactly those numbers), then that's about it. Just press the volume rocker to highlight Recovery, and press the Power button to select it to follow from there. It may look like the command didn't do anything, but it actually temporarily replaced your recovery image. It is important that you follow through from there without booting into your phone. If you boot into your phone before installing the SU package, you will need to do step 6 again because the phone will reinstall its own recovery image on boot.
Ok, thanks for the advice. I will do my best and come back if I hit any snags.
did you get it
I actually got some help from a friend, but am still having trouble learning this stuff. Still looking for someone in Toronto that I can meet up with to show me how this platform works.
Here We have the Root And CWM for Nexus 7 On Android 4.2.2!
Step 1 - Download Android SDK from the Android Developers website and install with USB drivers. See: How to Set Up Android SDK (Fastboot / ADB) on Windows.
Step 2 - Enable USB Debugging mode in your Nexus 7 tablet.
Step 3 - Download Fastboot and extract it in android-sdk-windowsplatform-tools directory. Create directory if not already there.
NOTE: Skip Steps 1, 2, 3 if you already have them.
Step 4 - Download SuperSU v1.04 (UPDATE-SuperSU-v1.04.zip) and copy it to your sdcard on your Nexus 7 tablet.
Step 5 - Make sure you have backup your data as it will be removed. Then switch OFF your Nexus 7.
Step 6 - Download recovery-clockwork-touch-6.0.2.3-grouper.img and copy/paste it in the android-sdk-windowsplatform-tools directory.
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Step 8 - Navigate to android-sdk-windowsplatform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 9 - Type in the following command and press Enter.
fastboot flash recovery recovery-clockwork-touch-6.0.2.3-grouper.img
Click to expand...
Click to collapse
Step 10 - Once completed, choose RECOVERY MODE from the Fastboot menu and enter Recovery Mode.
Step 11 - Then scroll down to “flash zip from SD card” and press the Power button to select it.
Step 12 - Press the Power button again and select “choose zip from sdcard”.
Step 13 - Now using your volume keys, navigate to the UPDATE-SuperSU-v1.04.zip file that you copied to your SD card and select it using the Power button. Confirm the installation on the next screen and the installation procedure should start now.
Step 14 - After the installation completes, go to “+++++Go Back” and reboot the phone by selecting “reboot system now” from the recovery menu. Then Choose yes flash recovery back (this will make CWM your permanent recovery mode)
That’s it. Your Nexus 7 is now rooted on Android 4.2.2 JDQ39 software version of Jelly Bean and even has a custom CWM recovery installed. Check for the SuperSU app in your apps list to verify.
Root and CWM for Nexus 4
Root and CWM for Nexus 10
Reserved...
udimars30 said:
Reserved...
Click to expand...
Click to collapse
Thank you a lot...but the link for the fastboot its not aviable
Nano23 said:
Thank you a lot...but the link for the fastboot its not aviable
Click to expand...
Click to collapse
link updated
and this belongs in original development how? why not post a thread in original development asking about need for speed too..
Step 4 and step 7
I am a little confused about step 4 as I didn't think any nexus 7's had a SD card slot. I purchased mine right from google. I just put the zip file directly on the device itself and I know from my experience with my old Nexus One that this works too, just wondering who is selling the one with SD card slots. My second question, and really the more important one is step 7. I have tried to make the device go into fastboot several times and when I hold the volume keys down, the device boots to a black screen with no ability to do anything after that. If I mess with the power button (meaning I hold it in for a long time then let it out, and do this several times) I can get the device to preform a normal boot. Any thoughts?
thanks
Thanks its worked for my nexus 7..
udimars30 said:
Here We have the Root And CWM for Nexus 7 On Android 4.2.2!
Step 1 - Download Android SDK from the Android Developers website and install with USB drivers. See: How to Set Up Android SDK (Fastboot / ADB) on Windows.
Step 2 - Enable USB Debugging mode in your Nexus 7 tablet.
Step 3 - Download Fastboot and extract it in android-sdk-windowsplatform-tools directory. Create directory if not already there.
NOTE: Skip Steps 1, 2, 3 if you already have them.
Step 4 - Download SuperSU v1.04 (UPDATE-SuperSU-v1.04.zip) and copy it to your sdcard on your Nexus 7 tablet.
Step 5 - Make sure you have backup your data as it will be removed. Then switch OFF your Nexus 7.
Step 6 - Download recovery-clockwork-touch-6.0.2.3-grouper.img and copy/paste it in the android-sdk-windowsplatform-tools directory.
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Step 8 - Navigate to android-sdk-windowsplatform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 9 - Type in the following command and press Enter.
Step 10 - Once completed, choose RECOVERY MODE from the Fastboot menu and enter Recovery Mode.
Step 11 - Then scroll down to “flash zip from SD card” and press the Power button to select it.
Step 12 - Press the Power button again and select “choose zip from sdcard”.
Step 13 - Now using your volume keys, navigate to the UPDATE-SuperSU-v1.04.zip file that you copied to your SD card and select it using the Power button. Confirm the installation on the next screen and the installation procedure should start now.
Step 14 - After the installation completes, go to “+++++Go Back” and reboot the phone by selecting “reboot system now” from the recovery menu. Then Choose yes flash recovery back (this will make CWM your permanent recovery mode)
That’s it. Your Nexus 7 is now rooted on Android 4.2.2 JDQ39 software version of Jelly Bean and even has a custom CWM recovery installed. Check for the SuperSU app in your apps list to verify.
Root and CWM for Nexus 4
Root and CWM for Nexus 10
Click to expand...
Click to collapse
Thanks a million man! I was having all kinds of trouble updating to 4.2.2 and finally figured that out. Then I was having problems rooting again until I found this. Your method worked great but I used TWRP instead and it still did the trick. Thanks again.
I tried this but when I want to flash the recovery, my fastboot.exe will then not respond and will try to close. What gives?
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Click to expand...
Click to collapse
Just a quick note here, to enter Fastboot Mode you just need to turn the Nexus 7 off, then turn on again, soon as you see the Google logo press the Volume Down key and hold (Hold both Power button and Volume Down Key).
No need for holding the power button, the vol down button does the whole trick
worked for me. thanks very much
sicameron32 said:
I am a little confused about step 4 as I didn't think any nexus 7's had a SD card slot. I purchased mine right from google. I just put the zip file directly on the device itself and I know from my experience with my old Nexus One that this works too, just wondering who is selling the one with SD card slots. My second question, and really the more important one is step 7. I have tried to make the device go into fastboot several times and when I hold the volume keys down, the device boots to a black screen with no ability to do anything after that. If I mess with the power button (meaning I hold it in for a long time then let it out, and do this several times) I can get the device to preform a normal boot. Any thoughts?
Click to expand...
Click to collapse
yes you can do that for the normal boot
Spenzert said:
Just a quick note here, to enter Fastboot Mode you just need to turn the Nexus 7 off, then turn on again, soon as you see the Google logo press the Volume Down key and hold (Hold both Power button and Volume Down Key).
Click to expand...
Click to collapse
Thanks..
I don't have N7 that's why did not know!
Leonhan said:
I tried this but when I want to flash the recovery, my fastboot.exe will then not respond and will try to close. What gives?
Click to expand...
Click to collapse
re-install the fastboot with all it's extensions in the same folder!
If you want to use fastboot by a easy way, use this guide you don't need adb line command, just fastboot line command and it's an child game by this way
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "Fastboot.zip"
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
The line command is :
Code:
c:\fastboot>
Enter
Code:
c:\fastboot>fastboot flash recovery recovery.img
Enter
If you want to flash the "recovery.img" file
If you want to flash a boot.img:
Code:
c:\fastboot>fastboot flash boot boot.img
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
don´t i have to unlock bootloader first ?
Domx92 said:
don´t i have to unlock bootloader first ?
Click to expand...
Click to collapse
Yes, it is a prerequisite if you want to root your android device.
Ok, so I am running the 4.2.2 update, and after jumping through numerous hoops trying to have my device recognized by adb, I just want to make sure that my very first step should be to boot up in fastboot mode and then issue the following command...
"fastboot oem unlock"
???
Then I can go ahead and proceed to flashing the CWM recovery and flashing the SuperSU file...?
Sent from my SCH-I535 using Tapatalk 2
EDIT: I've tried multiple times, but everytime I boot into "fastboot" mode, which I guess is another way for saying the bootloader, ADB loses its connection with my Nexus 7! Also, if it helps anyone to know, I'm running Win7 64-bit.....I'm not sure if that matters, but the first time I booted up into fastboot mode, my computer recognized it and installed it as an "Android Bootloader Interface" in the Device Manager! When the device boots up normally, ADB does recognize it again, and it also shows up differently in the Device Manager (Android Composite ADB Interface)! ANY help or suggestions would be greatly appreciated, as I obviously can't issue commands to a device that ADB can't see when it's in fastboot mode!
vmancini3 said:
Ok, so I am running the 4.2.2 update, and after jumping through numerous hoops trying to have my device recognized by adb, I just want to make sure that my very first step should be to boot up in fastboot mode and then issue the following command...
"fastboot oem unlock"
???
Then I can go ahead and proceed to flashing the CWM recovery and flashing the SuperSU file...?
Sent from my SCH-I535 using Tapatalk 2
EDIT: I've tried multiple times, but everytime I boot into "fastboot" mode, which I guess is another way for saying the bootloader, ADB loses its connection with my Nexus 7! Also, if it helps anyone to know, I'm running Win7 64-bit.....I'm not sure if that matters, but the first time I booted up into fastboot mode, my computer recognized it and installed it as an "Android Bootloader Interface" in the Device Manager! When the device boots up normally, ADB does recognize it again, and it also shows up differently in the Device Manager (Android Composite ADB Interface)! ANY help or suggestions would be greatly appreciated, as I obviously can't issue commands to a device that ADB can't see when it's in fastboot mode!
Click to expand...
Click to collapse
Hi, vmancini3...
Forget about ADB when your tablet is in FASTBOOT/BOOTLOADER mode...
Here are the salient commands....
Code:
fastboot devices
- should return a serial number to confirm your FASTBOOT connection -
Code:
fastboot oem unlock
- will unlock the BOOTLOADER and will WIPE and FACTORY RESET THE DEVICE; unfortunate, but necessary .
--------------------
With the BOOTLOADER unlocked, begin to set up your Nexus 7 again... as though it was a brand new, just purchased tablet... ie., country, regionalization, WiFi key... etc.
Go online with your Nexus 7 browser (Chrome), and download Chainfire's SU Updater .ZIP package from here...
http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Upon completion of this download, shut down the tablet.
--------------------
Reboot again into FASTBOOT/BOOTLOADER mode... VOL down button + POWER ON button.
From your PC, run this command...
Code:
fastboot flash recovery recovery.img
....where the recovery.img is your CWM or TWRP .img file.
Both of which are available here...
CWM - http://www.clockworkmod.com/rommanager
TWRP - http://www.teamw.in/project/twrp2/103
--------------------
Congratulations.... you've just FLASHED a CUSTOM RECOVERY!!!
--------------------
When the self-congratulatory round of self applause has died down, ... and with the Nexus 7 still in FASTBOOT/ BOOTLOADER MODE, use the VOL buttons to navigate and the POWER button to select... reboot into RECOVERY.
Using the new CUSTOM RECOVERY, flash Chainfires SU updater package that you downloaded earlier... usually found in the /download folder...
Done.
Reboot.
Rooted.
--------------------
I really don't understand why some people seem to have a problem with this procedure... it takes less time doing it, than actually describing how to do it.
Rgrds,
Ged.
My wife has a rooted nexus 7 2012 wifi and she unintentionally accepted the ota Android 4.3 update. So of course it unrooted her.
I originally had a hell of a time rooting this tablet using wugfresh nexus toolkit. Took me several days to succeed and the same thing is happening again. My Windows 7 laptop keeps installing the wrong drivers even though I selected the option to disable the auto driver configuration. Also USBDeview never shows the installed Samsung adb drivers yet when I try to install them I am warned they are already installed. It's already been hours and who knows how many retries and reboots!
So even though I'm a newbie I decided to go the Android sdk route.
1. Where do I download the files I need to just root the darn tablet?
2. What do I do next?
Please keep it simple........
Anyone want to walk me through it on the phone?
Thanks
If you are new to using SDK, check this out for a well laid out tut on how to get set up and rooted.
I now have android sdk set up.
What are the commands I should issue to root?
Thanks
now you need to flash a custom recovery then flash a root zip file via windows command prompt...Have you figured out how to interface with your device and the windows command prompt? eg;
-a good first command is "adb devices" and see if it lists your device, if it does your golden...
-then you would issue "adb reboot bootloader"
-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"
-then while in bootloader toggle with the volume keys to "recovery" option and press power
-now you will be in your new recovery you just flashed and you can push the zipped root file you chose to the sdcard, "adb push rootyouchose.zip /sdcard/"
-once its been pushed you can flash it in recovery and reboot, and you are now rooted
-this is the latest cwm recovery that you could flash in fastboot as described above
-this would be the root file you want to push then flash in recovery
-this may be of some help, scroll down halfway
Thank you so much for helping. You can't know how much it is appreciated.
-a good first command is "adb devices" and see if it lists your device, if it does your golden...
Got that. It works!!
-then you would issue "adb reboot bootloader"
Worked! Got the Android on his back.
-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"
Is recovery image on my pc or the tablet?
Why do I have to indicate the img name here if I will later select it
When I write
Fastboot flash......... Img
I get
Unknown partition 'the image file name'
"error : cannot determine image filename for. '.......'
You need to have downloaded a recovery image, that is what you flash I linked to one on my last post, that file is called "recovery-clockwork-touch-6.0.4.3-grouper.img" so you would issue,
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img
"fastboot flash recovery" is telling it to flash a recovery file and "recovery-clockwork-touch-6.0.4.3-grouper.img" is the recovery file in this case to be flashed so, combined its, "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img"
I do not use Windows, I use a terminal instead of windows command prompt so I can't be specific as I am not too familiar with windows command prompt. With terminal it is much easier in my opinion but you need to be running nix or Mac OS to have a terminal
OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.
I have the proper drivers installed and it connects fine with my Windows 7 laptop.
From a Windows 7 command prompt
1. "abd devices "
Correctly returns the attached nexus
2. "abd reboot bootloader "
Correctly reboots the tablet
3. **here's where things breakdown :
I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)
" openrecovery-twrp-grouper.img"
However, when I now issue the command
"fastboot flash recovery openrecovery-twrp-grouper.img"
I get an error :
Cannot open openrecovery-twrp-grouper.img
The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.
So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?
Do I need to put the recovery image somewhere special in the nexus file structure?
I'm stuck.
Thanks
Anderson2 said:
OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.
I have the proper drivers installed and it connects fine with my Windows 7 laptop.
From a Windows 7 command prompt
1. "abd devices "
Correctly returns the attached nexus
2. "abd reboot bootloader "
Correctly reboots the tablet
3. **here's where things breakdown :
I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)
" openrecovery-twrp-grouper.img"
However, when I now issue the command
"fastboot flash recovery openrecovery-twrp-grouper.img"
I get an error :
Cannot open openrecovery-twrp-grouper.img
The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.
So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?
Do I need to put the recovery image somewhere special in the nexus file structure?
I'm stuck.
Thanks
Click to expand...
Click to collapse
Hi, Anderson2...
If I may throw in my couple of cents...
The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.
Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.
For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...
Code:
fastboot devices
This is purely diagnostic, and hopefully confirms a working fastboot connection.
You should see something like this...
Code:
025d2d424bxxxxx fastboot
A serial number followed by the word fastboot. If you see this, you can go ahead and run...
Code:
fastboot flash recovery recovery.img
(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).
My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".
If fastboot can't find it.. it can't open it.
Hope this helps.
Rgrds.
Ged.
GedBlake said:
Hi, Anderson2...
If I may throw in my couple of cents...
The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.
Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.
For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...
Code:
fastboot devices
This is purely diagnostic, and hopefully confirms a working fastboot connection.
You should see something like this...
Code:
025d2d424bxxxxx fastboot
A serial number followed by the word fastboot. If you see this, you can go ahead and run...
Code:
fastboot flash recovery recovery.img
(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).
My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".
If fastboot can't find it.. it can't open it.
Hope this helps.
Rgrds.
Ged.
Click to expand...
Click to collapse
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.
Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.
Anderson2 said:
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.
Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.
Click to expand...
Click to collapse
No, problem Anderson2... glad to help.
Adb and fastboot are indeed powerful and useful tools, and I would strongly recommend anybody wishing to 'modify' their Nexus 7 (everything from rooting to flashing Custom ROMs) to familiarise themselves with the fundamentals of their operation... rather than relying on toolkits.
There are actually ways of flashing TWRP or CWM Custom Recoveries directly from the Nexus 7 itself, without recourse to either fastboot or the need for a PC... by using apps like Flash Image GUI or Flashify. But these apps need you to be already rooted, unfortunately.
So to summarize how to acquire root the old fashioned way....
---------------------------------------
1). Unlock the bootloader first with fastboot oem unlock. For security reasons, this will factory reset the device... ie., WIPE everything on it.
...but I assume your Nexus 7's bootloader is already unlocked, given it's been rooted once before.
And so swiftly skipping forward to step 2...
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery recovery.img... where 'recovery.img' is the Custom Recovery of your choice. Reboot the device by using the Custom Recovery's own reboot option.
3). Download Chainfire's UPDATE-SuperSU-v1.65.zip root package directly to your Nexus 7. This DOES need to be on the Nexus 7. Most Android browsers (including Chrome) download stuff to the /download folder on the devices internal storage. You'll need to remember the location, for when you come to flash it with either CWM or TWRP.
4). Boot the Nexus 7 into the bootloader. Although you can do it with adb reboot bootloader, you can also do it manually as follows...
- Shut down the Nexus 7 completely.
- Press and hold the VOL-DOWN button... whilst holding, press the POWER-ON button for about 5-10 seconds. The device should now boot into the bootloader.
5). Boot into your Custom Recovery... whilst in the bootloader, use the VOL-KEYS to navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. The device will now boot into either CWM or TWRP Custom Recovery.... whichever one you fastboot flashed earlier.
6). Now to ROOT!
** If using TWRP... tap on the INSTALL button, and then navigate to the /download folder on the Nexus 7's internal storage, and where Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on it, and Swipe to Confirm Flash.
** If using CWM... tap on the INSTALL ZIP option, followed by CHOOSE ZIP FROM /SDCARD... tap on the folder 0/... this gives you access to the internal storage of the Nexus 7... from which you can navigate to the /download folder, where again, Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on NO (the first default option) or YES - Install UPDATE-SuperSU-v1.65.zip.
On every screen in the CWM filemanager (by which you navigate) there is ALWAYS a ++++Go Back++++ option at the bottom of the screen. So you can always backout out of anything. In CWM you can also use the VOL UP and DOWN keys to scroll, with the POWER-BUTTON to select an option.
Once you have flashed Chainfire's SuperSU root package, reboot the device with the Custom Recovery's own reboot option.
Upon reboot, and whichever Custom Recovery you're using , it ***MIGHT*** suggest you are unrooted... and offer to fix root for you. Ignore it, and continue to reboot.
---------------------------------------
And that's it... that's how you root a first generation Nexus 7 (2012).
Hope this is of use and... Good luck.
Rgrds,
Ged.
GedBlake said:
No, problem Anderson2... glad to help.
Adb and fastboot are indeed powerful and useful tools, and I would strongly recommend anybody wishing to 'modify' their Nexus 7 (everything from rooting to flashing Custom ROMs) to familiarise themselves with the fundamentals of their operation... rather than relying on toolkits.
There are actually ways of flashing TWRP or CWM Custom Recoveries directly from the Nexus 7 itself, without recourse to either fastboot or the need for a PC... by using apps like Flash Image GUI or Flashify. But these apps need you to be already rooted, unfortunately.
So to summarize how to acquire root the old fashioned way....
---------------------------------------
1). Unlock the bootloader first with fastboot oem unlock. For security reasons, this will factory reset the device... ie., WIPE everything on it. I assume your bootloader is already unlocked.
So swiftly skipping forward to step 2....
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery recovery.img... where 'recovery.img' is the Custom Recovery of your choice. Reboot the device by using the Custom Recovery's own reboot option.
3). Download Chainfire's UPDATE-SuperSU-v1.65.zip root package directly to your Nexus 7. This DOES need to be on the Nexus 7. Most Android browsers (including Chrome) download stuff to the /download folder on the devices internal storage. You'll need to remember the location, for when you come to flash it with either CWM or TWRP.
4). Boot the Nexus 7 into the bootloader. Although you can do it with adb reboot bootloader, you can also do it manually as follows...
- Shut down the Nexus 7 completely.
- Press and hold the VOL-DOWN button... whilst holding, press the POWER-ON button for about 5-10 seconds. The device should now boot into the bootloader.
5). Boot into your Custom Recovery... whilst in the bootloader, use the VOL-KEYS to navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. The device will now boot into either CWM or TWRP Custom Recovery.... whichever one you fastboot flashed earlier.
6). Now to ROOT!
** If using TWRP... tap on the INSTALL button, and then navigate to the /download folder on the Nexus 7's internal storage, and where Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on it, and Swipe to Confirm Flash.
** If using CWM... tap on the INSTALL ZIP option, followed by CHOOSE ZIP FROM /SDCARD... tap on the folder 0/... this gives you access to the internal storage of the Nexus 7... from which you can navigate to the /download folder, where again, Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on NO (the first default option) or YES - Install UPDATE-SuperSU-v1.65.zip.
On every screen in the CWM filemanager (by which you navigate) there is ALWAYS a ++++Go Back++++ option at the bottom of the screen. So you can always backout out of anything. In CWM you can also use the VOL UP and DOWN keys to scroll, with the POWER-BUTTON to select an option.
Once you have flashed Chainfire's SuperSU root package, reboot the device with the Custom Recovery's own reboot option.
Upon reboot, and whichever Custom Recovery you're using , it ***MIGHT*** suggest you are unrooted... and offer to fix root for you. Ignore it, and continue to reboot.
---------------------------------------
And that's it... that's how you root a first generation Nexus 7 (2012).
Hope this is of use and... Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you all very much. I greatly appreciate your help.
This post should be a sticky!
One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?
Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.
Anderson2 said:
Thank you all very much. I greatly appreciate your help.
This post should be a sticky!
One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?
Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.
Click to expand...
Click to collapse
Hello again, Anderson2...
Well, you sort of are already doing something in return.... you're asking questions.
Questions that require answers. Those answers, whoever posts them, may be of assistance to somebody else. Somebody else looking for a solution to a similar problem.
I always look upon these forums as a means of sharing. Not everybody can know everything. God knows, I don't know everything.... and I've been messing around with Android for three years now. So don't worry so much about it being a quid pro quo sort of arrangement.
I know what I know primarily as a result of my own experiences and what I've learned here from the many (in most cases, more knowledgeable) posters here on XDA. What you learn today, you can pass on to others, tomorrow (metaphorically speaking). We, all of us, stand on the shoulders of each other.
With regard to the second generation Nexus 7 (2013)... I'm afraid I really don't know much about it... but I'd be surprised if rooting it deviated significantly from rooting the first generation Nexus 7....
Namely...
1). Unlock the bootloader.
2). Flash a Custom Recovery.
3). Using that Custom Recovery, flash some SU root package... probably from Chainfire.
Anyway, I've found this tutorial here...
http://forum.xda-developers.com/showthread.php?t=2382051
...and it appears to follow a very similar template.
The Nexus 7 (2013) forum itself, which is also worth visiting, is located here....
http://forum.xda-developers.com/nexus-7-2013
Rgrds,
Ged.
I have not been on this site since posting my guide, i do want to let any future people reading this know that, I am not a professional. everything in this guide is using stuff from other peoples threads.... this thread is just step by step directions on how i rooted (and installed TWRP on) MY lg k7 (MetroPCs). Also i had to root before i unlocked the boot loader. Which is not safe, you should probably unlock the boot loader before you root, but i couldn't figure out how to unlock it without root access.
I AM NOT RESPONSIBLE FOR ANY THING THAT HAPPENS TO YOUR DEVICE!
YOU AND ONLY YOU CAN BE HELD RESPONSIBLE
~BACK UP FILES ON PC, YOUR PHONE WILL BE RESET TO FACTORY SETTINGS DURING THIS TUTORIAL~
Step One: Enable Dev Options
A) open settings>about phone>software info then tap "Build Number" really fast about 10 times
B) open settings>Developer Options, then check the box labeled "Enable OEM Unlock", and the box Labeled "USB Debugging"
Step Two: Install Android SDK/ADB/USB drivers
A) go to http://developer.android.com/sdk/index.html in your browser, and click download...
B) go to https://www.microsoft.com/net/default.aspx in your browser, and click the big blue button that says .NET
Framework 4.6.1 or X.X.X depending on when your reading this...
C) go to http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html scroll down until you get to the first box, labeled Java SE Development Kit 8u91 or XuXX Depending on when your reading this, then find your OS (ex: Windows x86, Mac OS, Linux, Etc..), then select the download link
Step Three: Installing LG K7's USB Driver's
A) unlock your phone
B) plug your phone into you Computer via USB
C) pull down your notifications, Tap on the USB icon which should be labeled "Media Device (MTP)," "Send Images (PTP)," or "Charge Phone"
D) if a dialogue box pops up asking to install drivers tap install, if not proceed to step E
1) Your PC should ask you if you want to auto run, Either auto run or open the folder and run LG_PC_Programs.exe then proceed to Step Four
E) select "Media Device (PTP)," if not already selected
1) click the three vertical dots next to the magnify glass in the upper right hand corner, select install pc drivers, then tap install
Step Four: Installing Java SE
A) return to the folder where you downloaded the files in step two, install the file which contains the word java in it
Step Five: Installing Microsoft .NET 4 Framework
A) now in the same folder as step four, install the with the name "NDP461-KB3102438-Web," the name might be different then mine depending on when you are reading this
B) if it is already installed it will notify you and you can proceed to the next step
Step Six: Installing Android Studio 2.0 (SDK/ADB Drivers)
A) in the download folder from step four & five, double click the remaining file, the name should contain the words "android", and "studio" in it
B) when the dialogue box opens requesting admin rights, select allow
C) click next
D) click next
E) make sure all boxes are checked and click next
F) read the license agreement, (unless your the 99.9% that doesn't) click i agree
G) you may click next or choose where you'd like to install android studio, and where you'd like to install SDK, for this tutorial i will change make a new folder in my docs named SDK then change the SDK install dir to My Docs
H) click next
I) it will take a moment to install so just wait
(note: the progress bar will fill up, then reset, as it is installing in two separate locations)
J) when finished, click next
K) uncheck the box and click finish
Step Seven: Root your device
(Note: I rooted before i unlocked my boat loader, as i could not get it to boot into boot loader mode until i rooted it)
A) go to http://www.kingroot.net/wap on your android device and download the apk file
B) go to settings>security and check the box labeled "Unknown Sources"
C) install the apk
Video tutorial for king root here: https://www.youtube.com/watch?v=tG_ruuTPVpU
(Not my channel or video)
D) open the king root app
E) make sure you have a charged battery or your phone is plugged in as the rooting process time may vary (better safe then sorry)
F) swipe up until you see a "TRY IT" button click it
G) under "Root Access not available" tap "Get Now
H) do not turn off your phone
I) when it is done you can tap optimize now if you wish, otherwise close the app
Step Eight: Replacing KingRoot with SuperSU ~ W0lfDroid Method
A) go to http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
B) scroll down until you see the word "download:" (should be right above the related posts
C) click on the "new link" next to "Replace_Kingroot_With_SuperSU.zip"
D) extract the .zip so that the "MRW" folder is on your internal storage
(Easiest way is to download it on PC and open up your k7 in "my computer" and select internal storage and drag the MRW folder inside the .zip there)
E) go to google play and search "terminal emulator for android" or use this link if your reading this on your phone https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
F) install the first one, or use this link if your reading this on your phone https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
G) open terminal emulator
H) type "su" without the quotations
(everything typed in the terminal is case sensative)
I) type "sh /sdcard/mrw/root.sh" without the quotations
J) you might see a few errors, that is fine
K) wait until it says finished
L) when SU opens, select "update" "install" or what ever pops up
M) when it asks to uninstall, uninstall it, it is not uninstalling SuperSU it is uninstalling Kingroot,
O) if 30 minutes pass and it is still uninstalling then exit the app and then reboot the phone
DO NOT STOP HERE ~ YOU HAVE TO UNLOCK THE BOOTLOADER, and OPTIONALLY FLASH TWRP
Step Nine: Unlocking The Bootloader
A) refer to step one and double check the OEM unlock is enabled and USB debugging is turned on
(If not then please enable them)
B) search quick boot on the google play store download the first app it should be a circle with a lightening bolt
C) open quick boot
D) when asked to "allow root access?" tap allow
E) if an add pops up close it with the ex in one of the corners
F) tap on the word boot loader
G) at the top of your phone you should see " * Welcome To Fast Boot Mode : "
H) now go to your SDK dir, in my case it is C:\Users\USER\Documents\SDK
I) hold shift, then right click on the "platform-tools" folder, then select "open command window here"
J) in the CMD window type "fastboot devices" - without quotations
(everything is case sensative)
K) then type "fastboot oem unlock" - without quotations
L) then type "fastboot getvar unlocked" if that doesn't work try "fastboot getvar" or "fastboot getvar unlock" to confirm if it is unlocked
(if non of the getvar commands work you did something wrong, and i wont be able to help you, but if you followed the tutorial you shouldn't have any issues as these are the exact steps i took)
M) then type "fastboot reboot"
LEAVE THE CMD OPEN OR YOU WILL HAVE TO REPEAT steps H-I
Step Ten: Flashing TWRP
A) go to http://forum.xda-developers.com/general/general/qa-metro-pcs-lg-k7-lgms330-t3331678 and click on the latest download for twrp for me it is BETA1
if the links on that page dont work then use the links here http://forum.xda-developers.com/showpost.php?p=66282525&postcount=42
B) extract the download into your SDK folder on your PC
C) in the sdk CMD window from Step nine
D) type "fastboot devices" - without qoutation
E) ~optional, HIGHLY RECOMENDED~
1)type fastboot "boot twrp-image-3.img" - this will boot up twrp WITHOUT flashing it, just so you can make sure everything is working right
in my case it was twrp-image-3.img check your twrp file name and replace fastboot boot twrp-image-3.img with
fastboot boot INSERT YOUR FILE NAME HERE.img
2)in twrp tap reboot>bootloader
F) when bootloader mode opens back up
G) type "fastboot flash twrp-image-3.img" or "fastboot boot INSERT FILE NAME HERE.img" depending on your file name
H) when finished flashing type "fastboot reboot"
Step eleven
A) follow instructions on step one
B) the reason you must do this is because when you flash TWRP it erases your entire phone and resets it
Congrats you have Successfully Rooted, Unlocked Your Bootloader, and Flashed TWRP, to your LG K7
Well done, my friend. Well done indeed.
[QUOTE
Congrats you have Successfully Rooted, Unlocked Your Bootloader, and Flashed TWRP, to your LG K7[/QUOTE]
is this ok with the gapps 5.1 instsall .zip for twrp install or should i use a different? also, do you have a suggested camera app? awesome thread btw. Nevermind simple twrp install fixed everything.
I have tribute 5 and can't access bootloader or install SuperSU.....always fails.
How can I get this to work?
Today backup important files you need!
Is this a real method BC everybody having problems rooting this device so I ask can u make a video and add screenshots
Sent from my LG-D800 using Tapatalk
I can confirm this method works. The only different thing i did was purchase Supersume pro from playstore. Worked like it said it would. The Ls675 is rootable. But no bootloader unlock or bootloader at all for that matter. Im running MS330 with TWRP full root and have twrp backups and fastboot flashable backups via flashfire....
---------- Post added at 02:28 AM ---------- Previous post was at 02:20 AM ----------
https://mega.nz/#!CRAVWAyI!QIbo20-0ZnVqlREs7ZXF66aB_Eh3UjCEMVQbLuP1Zec
https://mega.nz/#!zBoxGIQR!buXvorPkA14Vr2Idn7uhNPHanOL6wbvcEav3MhRdjv8
https://mega.nz/#!yQBg1ayC!r3qvWfLjCAKg0e8t91J1IEtae8_EwhvYTXjawv7b_2A
Screen shots of root, flashfire backups, and device info
While it does work I can find no method using the buttons to get into twrp all the instructions I find for recovery fail so I can only boot back to it after the phone boots, thus it's worthless at this point. Also the command is fastboot flash recovery imgagename.img and you'll need to remove kingroot from administrators to uninstall.
Anyone else been able to boot directly into twrp from the off position?
zgauthier8286 said:
I can confirm this method works. The only different thing i did was purchase Supersume pro from playstore. Worked like it said it would. The Ls675 is rootable. But no bootloader unlock or bootloader at all for that matter. Im running MS330 with TWRP full root and have twrp backups and fastboot flashable backups via flashfire....
---------- Post added at 02:28 AM ---------- Previous post was at 02:20 AM ----------
https://mega.nz/#!CRAVWAyI!QIbo20-0ZnVqlREs7ZXF66aB_Eh3UjCEMVQbLuP1Zec
https://mega.nz/#!zBoxGIQR!buXvorPkA14Vr2Idn7uhNPHanOL6wbvcEav3MhRdjv8
https://mega.nz/#!yQBg1ayC!r3qvWfLjCAKg0e8t91J1IEtae8_EwhvYTXjawv7b_2A
Screen shots of root, flashfire backups, and device info
Click to expand...
Click to collapse
can you please help me i have 2 MS330 that are bricked
callihn said:
While it does work I can find no method using the buttons to get into twrp all the instructions I find for recovery fail so I can only boot back to it after the phone boots, thus it's worthless at this point. Also the command is fastboot flash recovery imgagename.img and you'll need to remove kingroot from administrators to uninstall.
Anyone else been able to boot directly into twrp from the off position?
Click to expand...
Click to collapse
Try to do the factory hard reset trick but say no at the second screen. I haven't tried it out yet but I've been reading around several sites and that's a possible solution
zgauthier8286 said:
Try to do the factory hard reset trick but say no at the second screen. I haven't tried it out yet but I've been reading around several sites and that's a possible solution
Click to expand...
Click to collapse
Just reboots. Think we're going to have to change something? Boot image? Kernel?
callihn said:
Just reboots. Think we're going to have to change something? Boot image? Kernel?
Click to expand...
Click to collapse
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Does anyone know a way to successfully root this phone? Not just recover?
Sent from my LGMS330 using Tapatalk
callihn said:
Just reboots. Think we're going to have to change something? Boot image? Kernel?
Click to expand...
Click to collapse
Of other interest 5.1 is very dendent on Google apps and move app updates to the system via TB or Link2SD fails more than it succeeds, shows they moved but app inaccessible afterwards hence brick. Mine went down trying to integrate play services and reinstalling from adb didn't help. FYI if you relock the BL it'll lock the phone with a security error too. Moving play services causes unending error screens so you can't really see if it's done moving, but I waited a good 5 minutes before reboot. Issue on fails could have been the system not being r/w. Needless to say backup, backup, backup as I hadn't because I've never had a serious issue doing that and considered it a trivial task. Anyone had good success with integrating updates and cache? Anyone restored from twrp yet?
JayCouture.com said:
Does anyone know a way to successfully root this phone? Not just recover?
Sent from my LGMS330 using Tapatalk
Click to expand...
Click to collapse
Yes! Just follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=66456635&postcount=1
zgauthier8286 said:
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Click to expand...
Click to collapse
Can you figure out why we can't boot to recovery via hardware buttons? That's critical for tinkering and testing on the go since I always have my phone but not my laptop for booting into recovery with adb. Not sure exactly where to look, probably start with a search for the words "recovery" and "safe mode" for the buttons and "security error" in the boot.img files.
callihn said:
Can you figure out why we can't boot to recovery via hardware buttons? That's critical for tinkering and testing on the go since I always have my phone but not my laptop for booting into recovery with adb. Not sure exactly where to look, probably start with a search for the words "recovery" and "safe mode" for the buttons and "security error" in the boot.img files.
Click to expand...
Click to collapse
If your rooted u can dl a reboot recovery app on the play store I have one that works like a charm. But im gonna take a look through Linux at the kernel options using make menu_config and see if there's anything I can see in there.
zgauthier8286 said:
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Click to expand...
Click to collapse
im having a problem w the security 9 error boot loop. only seem to b able to get it into download mode , not bootloader or recovery. would your boot and recovery img's help me at all ya think ? thanks !
goitalone said:
I have tribute 5 and can't access bootloader or install SuperSU.....always fails.
How can I get this to work?
Click to expand...
Click to collapse
Thanks again. For anyone that has a soft bricked LG K7 see this man! He brought my S#!? To life through teamveiwer. Thanks again. From my LG K7.
Maybe just my experience, but regarding step 10. I had to have the twrp image in SDK>platform tools, also when you get to fastboot flash twrp-image-3.img, I couldn't get it to work, until I typed it as fastboot flash recovery twrp-image-3.img. Hope this helps anyone else getting errors during this part. Thanks for the writeup.
It would be nice to have step by step instructions for rooting.
Here's what I have thus far. The final root steps are not complete:
I. Enable Developer Options:
1. Go to your device Settings.2. Select “About phone” » tap seven times on “Build number”.3. This will enable Developer options under Settings.4. Go back to Settings » scroll down to Developer options5. Enable OEM Unlock: Open “Developer options” menu » enable OEM Unlock6. Enable USB Debugging: Open “Developer options” » scroll down to Debugging menu, enable “USB Debugging”
II. Unlock Bootloader - This will wipe your Pixel
1. Install ADB Installer 1.4.3 - http://downloadmirror.co/29Xn/adb-setup-1.4.3.exe2. Connect your Pixel device to the PC with a USB cable.3. Open a command window on your PC.4. Boot your Pixel device into bootloader mode using the following command:adb reboot bootloader[NOTE: You may get a request to authorize USB debugging on the device, accept it.]5. Once your dveice is in bootloader mode, issue the following command to unlock bootloader:fastboot flashing unlock6. You’ll get a confirmation screen on your Pixel device. Press Volume Up button to highlight Yes and press Power button to select it.7. You need to boot into system now, either press Power button to reboot OR issue the following command:fastboot reboot8. During reboot, your Pixel device will go through a factory reset and then finally boot into system.
[MISSING STEPS FROM THIS POINT ON]
III. ROOT
1. Download factory image for your model: https://developers.google.com/android/images- INSERT DESCRIPTION OF EACH - AT&T, Verizon, etc2. Extract the ZIP file3. Open the folder, locate the 2nd zip file, and extract it as well4.- Inside that folder, locate: boot.img and copy it to your Pixel 2
5. Download 2 Magisk filesMagisk Manager 5.4.1 APK- https://forum.xda-developers.com/attachment.php?attachmentid=4324973&d=1509987367Magisk 14.4 - https://forum.xda-developers.com/attachment.php?attachmentid=4324974&d=1509987379
6. Download a File Manager app from the Play Store, then find and install the Magisk APK???
7. Use Magisk to patch the boot.img file, which will then be found in /storage/emulated/0/MagiskManager/
Next steps??8. From command line to the ADB folder:adb reboot bootloaderfastboot flash boot patched_boot.imgPress power button to reboot
Click to expand...
Click to collapse
Wouldn't you have to copy patched_boot.img to your PC before you can fastboot flash it?
JimSmith94 said:
Wouldn't you have to copy patched_boot.img to your PC before you can fastboot flash it?
Click to expand...
Click to collapse
Yes, then recopy the APK back after the wipe.
Worked great. No issues. Nice work.
Bootloop?
So I get to the last step and flashed the patched_boot.img. The phone reboots, and I seem to be stuck at a perpetual "G" and progress bar. Looks like a boot loop. I waited 5 minutes hoping it would proceed with boot. I then tried to flash the stock boot.img. Still same apparent boot loop. I had to flash the stock restore image to get going again. Am I being impatient? Should it immediately boot up?
once magisk creates patched_boot.img ... do I need to copy this file and place it inside the ADB folder on the computer? if so, which folder do I drop this file in?
trixiejay said:
So I get to the last step and flashed the patched_boot.img. The phone reboots, and I seem to be stuck at a perpetual "G" and progress bar. Looks like a boot loop. I waited 5 minutes hoping it would proceed with boot. I then tried to flash the stock boot.img. Still same apparent boot loop. I had to flash the stock restore image to get going again. Am I being impatient? Should it immediately boot up?
Click to expand...
Click to collapse
Mine didn't take long at all to boot up. Pretty much like a regular restart.
---------- Post added at 02:15 AM ---------- Previous post was at 02:13 AM ----------
trim81 said:
once magisk creates patched_boot.img ... do I need to copy this file and place it inside the ADB folder on the computer? if so, which folder do I drop this file in?
Click to expand...
Click to collapse
I placed mine in the folder with my platform tools. With adb and fastboot.
trim81 said:
once magisk creates patched_boot.img ... do I need to copy this file and place it inside the ADB folder on the computer? if so, which folder do I drop this file in?
Click to expand...
Click to collapse
Platform tools folder. Then open a CMD prompt while you are inside that folder and put your phone in bootloader mode. Then fastboot flash boot patched_boot.img
shizat63 said:
It would be nice to have step by step instructions for rooting.
Here's what I have thus far. The final root steps are not complete:
Click to expand...
Click to collapse
The Magisk post in the section for ROMs , Kernels and other Development has full instructions on how to root with Magisk. It worked for me.
There's also another post in here where someone goes through steps to root, add a kernel, and get V4A running (to mixed success as normal), and although he uses steps different than the first post I referenced, it's working for him.
Magisk isn't producing out a boot.img
I'm using version 5.4.3
Once I select the boot.img. it just goes back to the magisk home screen and says "downloading magisk v14.zip"
What an Im I doing wrong