Database Users

[Q] adb offline nexus 7 4.2.2

Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:

Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?

how to do that?
compty said:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
Click to expand...
Click to collapse
how to unlock bootloader 4.2.2?
yes usb debugging is enabled

I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.

google toolkit error trying to unlock
compty said:
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
Click to expand...
Click to collapse
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally

Same problem
leo9252 said:
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Click to expand...
Click to collapse
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.

Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981

further problems
sicameron32 said:
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Click to expand...
Click to collapse
So I was going to do it the old fasion way by following this guide
http://forum.xda-developers.com/showthread.php?t=2150661
I didn't quite get step four because the nexus 7 doesn't have an SDcard, but I copied the zip to the root of the device.
When I did step 7 the device did not go to Fastboot, it didn't go anywhere other than a black screen. I think I have a faulty unit, or the holding of the volume buttons with the power is really not the way to get to fastboot, either way I am looking at a brick right now. Any thoughts will be welcome. I messed around with it for 10 min now and got the device to re-boot. Not sure if I should try the fast boot option again.

Are you on Windows 8 by any chance?
Because I couldn't get it to work on Windows 8 and had to use Windows 7.

You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.

everyone i got it working! adb offline fixed
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.

leo9252 said:
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
Click to expand...
Click to collapse
It won't let me download and install anything from the 4.2 list...did you do anything else?

myleb said:
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
Click to expand...
Click to collapse
FWIW, here is my experience:
PC: Win7 Pro x64 SP1 - SDK platform-tools 16.0.1 - SDK Tools 21.1 - ADB v 1.0.31
N7: JDQ39 Stock *
( *OK, i diddled default.prop in my boot image to set "ro.secure =0". I don't know if that could make a difference or not )
The Nexus 7 asks for confirmation of inbound adb sessions for every new adb server invocation on the client PC.
When it does ask for credentials, you have to get to the on-screen display pretty quickly - a couple of seconds at most. If you don't the device will be reported as "offline" by the first invocation of
adb devices
If you accept the connection, the next time you run "adb devices", the status is back to normal (reports "device" instead of "offline").
You can test this out yourself - just iterate in a loop these three commands:
adb devices
adb devices
adb kill-server
Nothing that can't be understood by someone who knows what is going on; but I suppose that all the toolkits are running adb underneath the hood, so it is certainly possible to get tripped up when using a toolkit if you aren't Jhonny-on-the-Spot when that dialog pops up on the tablet.
Also, for the adventuresome:
I note that the new stock JDQ39 (4.2.2) ramdisk has a new line in the default.prop that was not in JOP40D (4.2.1) :
Code:
ro.adb.secure=1
I suppose that could be toggled off if you have a favorite kernel/ramdisk setup and you don't want to be bothered by this stuff. But it does mean unpacking/repacking your boot images.
cheers

I'm having the same problem. Never recognizes an ADB device. When it does it shows my serial number followed by "offline."
Any ideas? I'm ready to return this thing.
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Out of curiousity what driver are you using and how are you installing it?
Also where is your device coming up in the device manager?
I've tried so many things that I think I'm getting off track. Sadly my motorola phones were much easier to root.

how come you cant?
LucentBirch said:
It won't let me download and install anything from the 4.2 list...did you do anything else?
Click to expand...
Click to collapse
How come you can't download and install from the SDK manager?
That's how my problem got fixed.

Worked
jibdev said:
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
Click to expand...
Click to collapse
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.

you're welcome
sicameron32 said:
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
Click to expand...
Click to collapse
I knew someone would find this useful.
:laugh::good:

leo9252 said:
I knew someone would find this useful.
:laugh::good:
Click to expand...
Click to collapse
The sad thing is I have no idea what finally got it to work. Maybe just an extra reboot I had forgotten at some point. I do know however that I had to add a few extra lines (hardware ID) to the .inf file in the usb driver. Not sure which did the trick. I also used a combo of the toolkit to unlock and the manual method to root. Also I am unable to boot my device into the bootloader/fastboot via windows and rather have to manually (physically) shut down the device and enter the bootloader via the physical buttons. Probably an issue with the windows drivers again, but at least I have full functionality once in fastboot.
Only thing is now I can't get access to the storage via windows. And there's no way in hell I want to change the ADB drivers without knowing which finally worked for me. I'm thinking though that this is an entirely different device in device manager (I'm obviously not that knowledgeable).
Also I'm kinda annoyed by the unlocked padlock symbol on startup. I suppose that should be a welcome sign of achievement after spending all day trying to unlock/root, especially for such an unlearned person as myself.

did you clear this issue?
leo9252 said:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Click to expand...
Click to collapse
if not, pls gimme a mesg.
cause I'm a noob, I cannot use link here. :crying:
This issue is included in 4.2.2, and ADB is disabled by default for security.
I tested on my Nexus 4, 4.2.2 running. :fingers-crossed:

Okey. So to summarise: there is this new security feature in android 4.2. that makes the device show a popup if you want to allow the connected computer to use the adb = debugging bridge. But for this to work, you need to have the newest adb binary, which needs to print 1.0.31 when you run "adb version"
(found that info here --> http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ )
Under linux when you try to do it the old-school google-recommended way and download the huge "adt-bundle-linux-x86_64-20130219" and use the "android" tool to find new updates to the platform tools, it will tell you you already got the latest version which is rev 16.0.2 which contains an adb binary which will print version 1.0.26 which will not work with this new android 4.2.2 security feature.
So after searching for a linux adb 1.0.31 binary, I found it here:
https://github.com/mozilla/r2d2b2g/commit/2eefcc05366173ca51635da8f542fd8473ba0fea -->
https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/adb-1.0.31-linux.zip
with that binary I finally can use adb on my nexus 7 again.

[Q] please help with my nexus....

I went to flash cyanogenmod 10.1.
backed up rom via clockwork.
wiped data, flashed new rom.
flashed gapps.
I think i flashed the wrong gapps
upon boot I get "setup wizard has stopped" as well as one regarding gapps.
this prevents me from using the rom. I can access the calender and clock that is all. not the settings or reboot menu.
I can access the built in storage via windows, shows up as a nexus 7.
Ok, not a big deal, I will boot into recovery via the bootloader.
That no longer works. Sits at a google screen forever
Ok, I will use fastboot via the bootloader....
That no longer works. As soon as a usb cable touches the nexus either power or pc it freezes the bootloader requires a reboot.
windows rejects the usb and states is malfunctioned and unrecognised (though it works fine in the rom)
fastboot doesn't see the device.
I've tried:
three usb cables.
windows safe mode.
different ports
uninstall/install drivers.
nexus tool kit (doesnt recognise device)
wiggling the cable as suggested
anybody got an idea how I can either get the bootloader not to freeze when using a usb cable or how to boot into some kind of recovery (which was there!!!!!)
please? :fingers-crossed:

Something seems a little off here.
Was it a gapps package for some other device? Hard to see why flashing something to /system would produce the result you got, as the (gapps) edify script would at most specify a mount of "system", not a /dev/block/ device name.
Does adb work (with the ROM booted)? If so, can you get a root shell or install .apks?
The fact that the ROM boots suggests that the bootloader is working correctly enough to load and execute the LNX (boot) image. That means that in principle you could flash (using the "dd" command) a recovery image to the boot partition from a root-privileged command line (either an adb session or a terminal emulator). Performing a regular (power button) restart would boot you into a recovery session.
Obviously, this hinges on you getting a command line somehow with your reduced-functionality ROM limping along as it is. It's not obvious to me how you will make that happen though.
I am not at all confident that this will fix the bootloader <--> USB issue without somehow reflashing the bootloader without using fastboot!. The only way this has been observed for the N7 has been with the OTA process and a stock recovery - the OTA puts an image (**note - important!** this OTA bootloader image is slightly different from the bootloader image in the factory/fastboot ROMs) into the USP partition and some magic occurs on the next boot.
Well, anyway there's some ideas. Would you mind identifying the "wrong" gapps that you used? For the life of me I can't see how it caused the symptoms you are observing...
good luck

Hi. Many thanks.
Ok.....
Gapps. I downloaded the appropriate package via the link on the Rom page. However, I flashed a jellybean package I'd downloaded for my one x. I may be naive in thinking that Gapps is Gapps no?
I deduced it was that having googled the setup wizard problem and seeing that others had had it.
Bootloader.
Again. Ive googled around and can see many have the freezing bootloader with usb issue. Some say its the cable. Some say its the pc. But it does it with the charger as well. Again this is an issue for some. not sure what to do! Works fine until the cable goes in.
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Adb.
Never really used it. Used fastboot many times. I assumed you need to be able to access the developer options and activate debugging etc within the Rom to allow it to work? I can not do that. Its around 10% funtional. I can place a reminder on the calender but that's about it! No way to system settings.
Sorry if thats teaching you to suck eggs. You obviously know your stuff, just wanted to make it clear.
Ta.
Sent from my HTC One X+ using xda app-developers app

olly2097 said:
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Click to expand...
Click to collapse
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)

bftb0 said:
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
Click to expand...
Click to collapse
yeah, tried both ways.
The gapps I downloaded was a while ago. I've deleted it. was for 4.1.1
anyway. I....
Booted to bootloader, selected recovery, pressed power and rammed in the usb cable at the same time.
recovery
now running rom fine after flashing TW recovery via toolkit and mounting to pc.
I cant explain it. it took forever. but thank you

[Q] Screen broken, how to access my pics ?

Hi,
I broke my Nexus 4 screen so I can't do anything, the touchscreen is completely down. But the display is working.
I have bought a new Nexus 4 and I want to get my photos from the broken device. The problem is that I can't unlock the phone (pattern), so I can't access to these. USB debugging is off and the device isn't rooted.
I hope someone have a solution for me. Does any virtual touchscreen exist ?

Ghuillaume said:
Hi,
I broke my Nexus 4 screen so I can't do anything, the touchscreen is completely down. But the display is working.
I have bought a new Nexus 4 and I want to get my photos from the broken device. The problem is that I can't unlock the phone (pattern), so I can't access to these. USB debugging is off and the device isn't rooted.
I hope someone have a solution for me. Does any virtual touchscreen exist ?
Click to expand...
Click to collapse
Don't know if there is a simpler option, but this might help you:
http://forum.xda-developers.com/showthread.php?t=2433307
Not sure if adb works with usb debugging disabled though...

That has to be the Worst case scenario. Another reason I use Google drive and keep pics synced via cloud
Sent from my Nexus 4 using xda app-developers app

It's really annoying, I just need to unlock my phone but I can't !
I'm not comfortable with the idea having my pics on Google's servers, but I will find something to backup data now..
Maybe the only way is to wait the nexus to be obsolete and find a screen for a low price

Oh wait !
USB debugging is ON ! I didn't see the bean icon because there are a lot of notifications.
But I can't use adb :
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
Click to expand...
Click to collapse

Ghuillaume said:
Oh wait !
USB debugging is ON ! I didn't see the bean icon because there are a lot of notifications.
But I can't use adb :
Click to expand...
Click to collapse
I'm assuming that because your phone isn't rooted you don't have a custom recovery or an unlocked bootloader. Is this correct?

i know with my HTC desire i run adb, when the device is turned off and connected to PC .
i think you can try it with your N4 , there are tools to do it google it .
good luck

You can try some combination of Airdroid (older version) and adb/shell command. So you'll need your device connected and older version of Airdroid - not two, because it asks for user action to accept the connection, and the older one just gives random generated password for the user to input in their browsers.
Now, you'll need to push the apk on your phone, and then just start it from your adb shell with the following command:
am start -a android.intent.action.MAIN -n com.sand.airdroid/.Splash - this should work on the old version
am start -a android.intent.action.MAIN -n com.sand.airdroid/.SplashActivity_ this works on last airdroid
At least you can try with other app that doesn't need user interaction on their display to get into the phone memory from their browsers. You can just install them from play store.
The first time that I'm writing here in Nexus forum though I am here with my 2 old DHD for about 2 years and I hope my answer could be helpful. And now I am here because of my soon to come Nexus 4

You could try to unlock, flash CWM then "adb pull" the files from there. No need for the digitizer to get it done. Fully charge the battery before starting.

You don't need root access, just adb debugging.
For everything off your phone: adb pull /sdcard/
Done.
EDIT: If you just want your pics from your camera the command would be adb pull /sdcard/DCIM/Camera/

lopezk38 said:
I'm assuming that because your phone isn't rooted you don't have a custom recovery or an unlocked bootloader. Is this correct?
Click to expand...
Click to collapse
You don't need root to use adb.
You only need to for adb to access anything beyond the sdcard.
When you first use adb there is a pop up on the device that asks if you want to allow the pc access.
He can't use the touchscreen to confirm its ok. This is the reason after I flash a Rom hook up to my pc ASAP and have it remember my computer to allow me access if this were to happen to me.
illru said:
You could try to unlock, flash CWM then "adb pull" the files from there. No need for the digitizer to get it done. Fully charge the battery before starting.
Click to expand...
Click to collapse
HUGE reason why this won't work:
unlocking the bootloader wipes the entire device.
Which... is pointless if you're trying to recover data.

studacris said:
HUGE reason why this won't work:
unlocking the bootloader wipes the entire device.
Which... is pointless if you're trying to recover data.
Click to expand...
Click to collapse
If you flash the custom recovery immediately after unlocking (without rebooting into android in between) your data should not get wiped.

Well then... I sit here humbly corrected.

studacris said:
Well then... I sit here humbly corrected.
Click to expand...
Click to collapse
Dont worry, its not really an officially documented thing...more of just a bug with the bootloader.

Also if flashing your phone makes you nervous you could try to pull from in stock recovery but I don't know if it will work. Never played with stock recovery, it dose not last on my phone for very long.

illru said:
Also if flashing your phone makes you nervous you could try to pull from in stock recovery but I don't know if it will work. Never played with stock recovery, it dose not last on my phone for very long.
Click to expand...
Click to collapse
I dont think adb works in stock recovery. Only custom ones afaik.

[GUIDE] Simple Root Nexus 7 2013 LTE (deb)

Preamble
As a crotchety old man, my eye twitches and my back hurts every time I read a guide with superfluous steps, a root toolkit or an autoroot script for a nexus device. So, at the request of @thejmannnc, here's my simple root guide for Nexus 7 2013 LTE (deb).
NOTE: this will work just as well for the WiFi only version (flo), so long as you download the specific custom recovery for your device.
If your bootloader is locked (e.g. if this is your first time rooting this device)YOU WILL LOSE ALL YOUR DATA. There is no way around this.
Prerequisites
NOTE: I'm not writing a guide for these prerequisites
Prerequisite 1: "Fastboot" on a machine running a desktop operating system
Fastboot is one of the platform tools you can get from the android software development kit (SDK). You will need to install it. You can install the complete SDK, the platform tools, the two most basic platform tools (fastboot and adb), or, in theory, just fastboot.
*If you want to use adb as well, you will need to enable developer options and USB debugging on your N7. See the end of this post.
The SDK from Google:
http://developer.android.com/sdk/index.html
An XDA created tool for adb and fastboot. I haven't used it, but I'm told it works:
http://forum.xda-developers.com/showthread.php?p=42407269
A guide for installing the SDK for Windows 7:
http://forum.xda-developers.com/showthread.php?t=1830108
A guide for installing the SDK for Mac OS X:
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
Prerequisite 2: IF you use a Windows machine, USB DRIVER
Driver from Google. Note, the Google driver may not work for Windows 8:
http://developer.android.com/sdk/win-usb.html
If that doesn't work for you, try this driver:
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Prerequisite 3: A custom recovery .img file
Download a custom recovery .img file to your computer (or any machine with a USB port that runs a desktop operating system). Place the file in the same directory (folder) that houses fastboot. I recommend TWRP custom recovery.
TWRP for deb (LTE):
http://techerrata.com/browse/twrp2/deb
TWRP for flo (WiFi only):
http://techerrata.com/browse/twrp2/flo
THE ACTUAL GUIDE
Step 1: Unlock your bootloader
Power down your Nexus 7. Once you've totally powered down, hold down the power and volume down key on your nexus 7.
Plug your Nexus 7 into your computer.
Open a command prompt (Windows) or Terminal window (Mac OS X, Linux) in the directory that houses fastboot (or navigate to that directory using the command cd, or, if you've properly set up your platform tools in Mac OS X, don't pay any attention to the directory).
Type the following command (this is the step that wipes your device.):
Code:
fastbot oem unlock
Follow the prompts. Then reboot your Nexus 7 by pressing the power button when the menus says "START". During the reboot your N7 will go through a factory reset.
Step 2: Download the superuser binaries:
On your Nexus 7, download from this link:
http://download.chainfire.eu/
Step 3: Install TWRP and superuser binaries
Reboot into bootloader as you did for step 1:
Power down your Nexus 7. Once you've totally powered down, hold down the power and volume down key on your nexus 7.
Plug your Nexus 7 into your computer.
Open a command prompt (Windows) or Terminal window (Mac OS X, Linux) in the directory that houses fastboot (or navigate to that directory using the command cd, or, if you've properly set up your platform tools in Mac OS X, don't pay any attention to the directory).
Type the following command:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img
If you downloaded a different version (or the recovery for flo), replace "openrecovery-twrp-2.6.3.1-deb.img" with the file name for the image you downloaded.
Once you've flashed recovery, you should still be in the bootloader. Use the volume keys to navigate to "Recovery mode". (Hint, it's two taps of the volume down button. Press the power button to reboot into recovery mode.
Once recovery reboots, you'll see a menu with 8 buttons in a 4x2 grid. Tap "Install".
Navigate to your Download directory, where you'll find the file "UPDATE-SuperSU-v1.75.zip" (or whatever version was current when you downloaded it). Tap that file.
Swipe to confirm flash.
Once the superuser binaries have installed, tap the "Reboot System" button.
Congratulations! You're now rooted.
Epilogue:
If you want to use the android debug bridge (adb) you'll need to enable developer options and usb debugging.
Under settings, about tablet, tap build number 7 times to enable developer options, back out to settings, developer options, check USB debugging

You are the Man!! Thank you for taking the time to help me make this process so easy on me. You have definitely simplified the process. There's not alot of people in this world that would take their time and knowledge to help out a stranger. Not many people out there left like you! Im sure this will also help out countless others out there like me as well.
Cant say thanks enough,
Jimmy aka thejmannnc

thejmannnc said:
You are the Man!! Thank you for taking the time to help me make this process so easy on me. You have definitely simplified the process. There's not alot of people in this world that would take their time and knowledge to help out a stranger. Not many people out there left like you! Im sure this will also help out countless others out there like me as well.
Cant say thanks enough,
Jimmy aka thejmannnc
Click to expand...
Click to collapse
Your welcome. Please let me know if you have any trouble.
Sent from my Nexus 6 using Tapatalk 4

I had done the step above, however I am in boot loop now. I can not seem to get out of it.
I had tried to Factory Reset within TeamWin Recovery, however it is giving me a failed message.
Please help
---------- Post added at 12:06 AM ---------- Previous post was at 12:06 AM ----------
I had done the step above, however I am in boot loop now. I can not seem to get out of it.
I had tried to Factory Reset within TeamWin Recovery, however it is giving me a failed message.
Please help

xdhall said:
Your welcome. Please let me know if you have any trouble.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Hello,, I just got the nexus 7 and it immediately wamts to update to 4.4. Should I let it? Didnt know if this would affect using the guide you created. I wont touch anythimg until I hear from you to be on the safe side.
Thanks,
thejmannnc

cs378 said:
I had done the step above, however I am in boot loop now. I can not seem to get out of it.
I had tried to Factory Reset within TeamWin Recovery, however it is giving me a failed message.
Please help
---------- Post added at 12:06 AM ---------- Previous post was at 12:06 AM ----------
I had done the step above, however I am in boot loop now. I can not seem to get out of it.
I had tried to Factory Reset within TeamWin Recovery, however it is giving me a failed message.
Please help
Click to expand...
Click to collapse
To recover from bootloop, turn off your device, let it sit for a couple of minutes, reboot into recovery and wipe cache/dalvik cache.
If this doesn't work, verify that you downloaded the correct TWRP image for your device. (Deb = LTE, flo = Wi-Fi only).
Sent from my Nexus 6 using Tapatalk 4

thejmannnc said:
Hello,, I just got the nexus 7 and it immediately wamts to update to 4.4. Should I let it? Didnt know if this would affect using the guide you created. I wont touch anythimg until I hear from you to be on the safe side.
Thanks,
thejmannnc
Click to expand...
Click to collapse
Yes. Update to 4.4. It won't impact the guide.
Sent from my Nexus 6 using Tapatalk 4

xdhall said:
Yes. Update to 4.4. It won't impact the guide.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Ok. Thanks for getting back to me so quickly, would have been just my luck!!

xdhall said:
Yes. Update to 4.4. It won't impact the guide.
Sent from my Nexus 6 using Tapatalk 4[/QUOT
For some reason I am having trouble installing the driver. Downloaded, extracted, now stuck. Maybe im just tired and stressed but never had trouble with drivers before. Well at least the tablet was delivered today! Am I missing something simp
e?
Click to expand...
Click to collapse

thejmannnc said:
xdhall said:
Yes. Update to 4.4. It won't impact the guide.
Sent from my Nexus 6 using Tapatalk 4[/QUOT
For some reason I am having trouble installing the driver. Downloaded, extracted, now stuck. Maybe im just tired and stressed but never had trouble with drivers before. Well at least the tablet was delivered today! Am I missing something simp
e?
Click to expand...
Click to collapse
You don't need to enable USB debugging to root with fastboot, but it's possible that you need to in order to install the drivers. I don't use a Windows machine, so I don't have specific knowledge of the driver installation procedure. Enabling USB debugging is described in the guide epilogue. If that doesn't work, you'll have to ask someone with more experience on a Windows machine (or find a machine running a Linux based OS like Mac OS X or Ubuntu--they don't need drivers). Wish I could be more help.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse

xdhall said:
thejmannnc said:
You don't need to enable USB debugging to root with fastboot, but it's possible that you need to in order to install the drivers. I don't use a Windows machine, so I don't have specific knowledge of the driver installation procedure. Enabling USB debugging is described in the guide epilogue. If that doesn't work, you'll have to ask someone with more experience on a Windows machine (or find a machine running a Linux based OS like Mac OS X or Ubuntu--they don't need drivers). Wish I could be more help.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Got it all taken care of! Time to relax!!! Thanks for all your help!! If your ever in NC look me up and ill buy you a beer!!
Have a good one!
Thejmannnc
Click to expand...
Click to collapse

Thank you for such a easy to do guide. Android amateur is now rooted and ready to install custom ROM onto his 2013 LTE
I did the Mac part of guide. No problems.

ROOT with PIE Guide

Hi All,
In the best interest to provide clarity I'm creating this quick and easy tutorial on how to root your Razer Phone 2 after the Pie Upgrade. Please send me any feedback to improve this post, we need to build up a strong community.
*As usual, I'm not responsible of any damage or brick to your phone, do it at your own risk.
Pre-Requirements:
-Be sure to have at least 70% of charges... or plug your phone to power
-Backup anything you consider important
-Already installed Pie Upgrade via OTA or Side Loaded​
-Enable Developer Options
• Open Phone "Settings" and scroll down.
• You will see an option "Build Number".
• Simply tap on it 7 times to enable it on your Android Oreo based device.
• Your device immediately display a message on screen that will say "You are now a developer".
• The Developer Option is now available in the Settings>System>Developer Options. Enjoy!​
- Install Android Drivers (https://developer.android.com/studio/run/win-usb) and ADB, I personally recommend -[TOOL]Minimal ADB and Fastboot [2-9-18] - https://forum.xda-developers.com/showthread.php?t=2317790
-Unlock Bootloader
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
• Using ADB commands reboot on bootloader​
adb reboot bootloader​
• After reboot completes follow phone menus and select "UNLOCK BOOTLOADER"; accept all warnings, after restart you have completed the unlock.​
Root and Installing Magisk
Since our phone doesn't have a proven customer recovery fully working (Ex TWRP) Magisk needs to be installed by manually patching the device boot image.
Making leverage of Warrior1988 post [Root Magisk Pie Update For Unlocked Devices] all credits to him. Download the image from his post
• Boot in fastboot mode To boot into fastboot, press and hold the Power button + Volume Down Keys for few seconds; Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot​
Install Magisk Download the apk and install it as usual on your RP2, that should be all.
DONE!!!! You now have a unleashed the beast! Please send me any recommendations to improved this guide.

chpimentelpr said:
Install Android Drivers and ADB
Click to expand...
Click to collapse
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
chpimentelpr said:
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
Click to expand...
Click to collapse
I assume this is where we plug our phone into our computer?
chpimentelpr said:
• Using ADB commands reboot on bootloader
Click to expand...
Click to collapse
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
chpimentelpr said:
• Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash*boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.

AbsoluteContingency said:
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
I assume this is where we plug our phone into our computer?
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
Click to expand...
Click to collapse
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot

Warrior1988 said:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
No asterisk. Cool. Got it. Thank you, dude.

The drivers are the regular ones for android nothing specific, they can be downloaded from their SDK https://developer.android.com/studio/run/win-usb

App root detection?
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?

Bounty33 said:
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Click to expand...
Click to collapse
You can use magisk to hide the root from those apps. In general banking app are not affected by root. Google pay could be affected, but I don't use it so can't be sure. And you can always unroot.

AbsoluteContingency said:
No asterisk. Cool. Got it. Thank you, dude.
Click to expand...
Click to collapse
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.

chpimentelpr said:
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
Click to expand...
Click to collapse
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?

AbsoluteContingency said:
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
Click to expand...
Click to collapse
Yes, install them as any other driver.

After rooting can you relock the boot loader or will that brick the phone?

ndragon798 said:
After rooting can you relock the boot loader or will that brick the phone?
Click to expand...
Click to collapse
Not sure, but why you want to relock the boot.

chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Mostly to get rid of the startup message

Very nice. I've rooted a ton of phones over the years, but they had more established communities and had well-explained (and tested) methods of rooting. The previous guide posted (that you referenced) was fine enough, but it was very much lacking a couple prerequisites that I was wondering/concerned about. This guide has cleared all of that up for me, and I now feel confident about rooting this phone.
Just as soon as I charge up the phone and install the OTA I've been avoiding until now... lol. Hoping somebody will make a Magisk module to move the clock back to where it belongs (if they haven't already).
EDIT: Just wanted to add my success story to this. Only thing I had to do that wasn't listed in the instructions (but makes sense) is that fastboot didn't work until I enabled USB Debugging (again, after the wipe and reboot), and I had to very manually tell the computer which driver to use (ADB) after that. Didn't have that issue for the bootloader instructions beforehand (that time, the driver worked automatically), so I figured I'd mention it.

chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.

ndragon798 said:
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
Click to expand...
Click to collapse
I don't believe encryption is supported at the moment, and I don't encourage you to try it until TWRP is fully supported since you may end up in a boot loop. I'm eagerly waiting for the full encryption capability, so I will let you know as soon as something come up.

This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.

ChronosTrigger said:
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
Click to expand...
Click to collapse
i'm glad it helps.

Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!

xttweaponttx said:
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
Click to expand...
Click to collapse
I doubt the issue with the wifi is related with the image, since it doesn't have anything to do with it. If your phone doesn't detect the update you will need to sideload it. Then try the root guide again. Let us know how it goes, it the first time I hear something wrong with WIFI after rooting.