Related
Hey guys,
Yesterday I unlocked my bootloader, and rooted my phone for further flashing of the latest CM rom.
Today I wanted to finish what I'd started by flashing the radio img into it, which i've read there's no problem doing so after completing the rest of the process. However, fastboot devices won't see my phone and adb devices (with phone on) says the following:
Code:
List of devices attached
???????????? no permissions
I had seen this before and yet I could access it with fastboot, but not anymore.
I haven't found any thread on this so if someone has an idea regarding what might have happend I'd greatly appreciate it.
Thanks!
St.Jimmy! said:
Hey guys,
Yesterday I unlocked my bootloader, and rooted my phone for further flashing of the latest CM rom.
Today I wanted to finish what I'd started by flashing the radio img into it, which i've read there's no problem doing so after completing the rest of the process. However, fastboot devices won't see my phone and adb devices (with phone on) says the following:
Code:
List of devices attached
???????????? no permissions
I had seen this before and yet I could access it with fastboot, but not anymore.
I haven't found any thread on this so if someone has an idea regarding what might have happend I'd greatly appreciate it.
Thanks!
Click to expand...
Click to collapse
Make sure you have the correct drivers and usb debugging on
Sorry I forgot to say I'm on Ubuntu 9.10, so there is no need for any drivers as far as I'm concerned (I didn't need them the first time).
USB Debugging mode is ON.
Yeah, I had the same problem. It's already been discussed in the forums (search!).
This is the thread that fixed it for me:
http://forum.xda-developers.com/showthread.php?t=624065
I received a nexus 7 from a family member that has a X on it. I downloaded Nexus 7 Toolkit 4.0.0 and tried the stock reflash and all (option 9?) and it finally seemed to complete correctly after randomly closing a few times but now it's still stuck on the X.
How do I know my build to make sure I am selecting the right image? I just googled my baseband and the version 4.1.2 popped upbeside it in searches so I went with that.
It seems like I can't get the most recent update to the toolkit unless I pay for it, but I only planned on using it once and don't even know if that would solve my problem. If i knew for sure it would, sure I would purchase it. Any idea what I might be doing wrong?
Thanks
kmad86 said:
I received a nexus 7 from a family member that has a X on it. I downloaded Nexus 7 Toolkit 4.0.0 and tried the stock reflash and all (option 9?) and it finally seemed to complete correctly after randomly closing a few times but now it's still stuck on the X.
How do I know my build to make sure I am selecting the right image? I just googled my baseband and the version 4.1.2 popped upbeside it in searches so I went with that.
It seems like I can't get the most recent update to the toolkit unless I pay for it, but I only planned on using it once and don't even know if that would solve my problem. If i knew for sure it would, sure I would purchase it. Any idea what I might be doing wrong?
Thanks
Click to expand...
Click to collapse
I know this may seem kinda silly, but I had a really similar problem and I solved it by going into Recovery and wiping everything, then I was able to flash another ROM from too manager.
MarioES said:
I know this may seem kinda silly, but I had a really similar problem and I solved it by going into Recovery and wiping everything, then I was able to flash another ROM from too manager.
Click to expand...
Click to collapse
Yeah, that was the first thing I tried.
kmad86 said:
Yeah, that was the first thing I tried.
Click to expand...
Click to collapse
If that didn't work I'm afraid a manual flash is your only option, don't think any toolkits will work.
http://forum.xda-developers.com/showthread.php?t=1781250
Check that out, pretty straightforward and should do the trick.
MarioES said:
If that didn't work I'm afraid a manual flash is your only option, don't think any toolkits will work.
http://forum.xda-developers.com/showthread.php?t=1781250
Check that out, pretty straightforward and should do the trick.
Click to expand...
Click to collapse
I'm a rook when it comes to the command stuff. Some quick questions and I think I can be on my way.
1. How do I open a command prompt to my ADB and Fastboot directory? I have no idea what that means. Do I make a folder on my desktop titled Nexus 7, and inside that put something?
2. I can't boot into Android so what do I do when it says "if you're booted into Android" do I just put it in fastboot and say good?
(The last command prompt stuff I did was in 2002 for my computer using Windows XP it's been a while. Kinda rusty)
I appreciate the help guys, I'm learning! I guess I could send it in, but I like the learning experience and challenge.
kmad86 said:
I'm a rook when it comes to the command stuff. Some quick questions and I think I can be on my way.
1. How do I open a command prompt to my ADB and Fastboot directory? I have no idea what that means. Do I make a folder on my desktop titled Nexus 7, and inside that put something?
2. I can't boot into Android so what do I do when it says "if you're booted into Android" do I just put it in fastboot and say good?
(The last command prompt stuff I did was in 2002 for my computer using Windows XP it's been a while. Kinda rusty)
I appreciate the help guys, I'm learning! I guess I could send it in, but I like the learning experience and challenge.
Click to expand...
Click to collapse
You need to download the Android SDK for that so you can have the fastboot program. Download and install that first then you can proceed to flashing a rom using the fastboot command.
kmad86 said:
I'm a rook when it comes to the command stuff. Some quick questions and I think I can be on my way.
1. How do I open a command prompt to my ADB and Fastboot directory? I have no idea what that means. Do I make a folder on my desktop titled Nexus 7, and inside that put something?
2. I can't boot into Android so what do I do when it says "if you're booted into Android" do I just put it in fastboot and say good?
(The last command prompt stuff I did was in 2002 for my computer using Windows XP it's been a while. Kinda rusty)
I appreciate the help guys, I'm learning! I guess I could send it in, but I like the learning experience and challenge.
Click to expand...
Click to collapse
I'm not very good at this stuff either, and a manual flash was the first thing I tried. You'll get it!
If you can't boot into Android skip step 3 and go to 4, which is the same (just that you're loaded into the bootloader, which you should be able to access).
About the other issue, google it and look for a londatiga.net link (can't post links as a new user). All you need is the Android SDK
MarioES said:
I'm not very good at this stuff either, and a manual flash was the first thing I tried. You'll get it!
If you can't boot into Android skip step 3 and go to 4, which is the same (just that you're loaded into the bootloader, which you should be able to access).
About the other issue, google it and look for a londatiga.net link (can't post links as a new user). All you need is the Android SDK
Click to expand...
Click to collapse
I found FastBoot in the Platform-Tools folder, but I double click it and a command prompt looking screen pops up, but disappears.
EDIT: Got it.
Thanks for the help
Ok, so I figured out the command prompt.
For those of you searching for this, and in the same situation as I, I clicked on Start>and searched Command where my command prompt popped up as C:\users\admin> and i was really confused. From there my Toolkit was in Desktop>Nexus 7 Stuff>Toolkit>ADT Bundle>SDK>Platform-Tools.
I typed in command prompt "cd desktop" and enter. Then I was at C:\users\admin\desktop> From there I entered "cd nexus 7 stuff" and enter. and on to toolkit, then the next until I was at platform tools. Then I followed the instructions and whala!
(Now I am stuck on writing "boot") i've searched and found nothing.
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.
I know. You guys have heard it all before...but
I was using WugFresh to re-flash back to 4.3 from 4.4 and the recovery was taking so long. After an hour of running, I was moving the device to a coffee table when the cable fell out.
Hay, why isn't a message include in WugFresh like the backup process as to approximately how long this process takes? That brings up another issue in general with these old N7s is that these micro-USB female connectors get loose after so many years of use, makes connecting and charging difficult.
But I digress.
I have read often in the XDA forums about a factory reset ‘from bricked feature’ in WugFresh, but I can not find that feature anywhere where ‘bricked’. anything is. If it is there, where is it?
Anyway, how can I recover the bootloader and everything without having to learn doing everything via a cmd line or .bat process?
These are the facts:
Nexus 7 2012, 8g, re-flashing back to 4.3 from 4.4, using Nexus Root Kit
v1.8.2, Flash Stock + Unroot (I had read in XDA Forum somewhere where it was suggested to go back to a factory vs to use this option).
The N7 is currently has one of 4 states available: Bootloader screen (with below stated status), Google initial screen (with "Start" Showing and "Booting failed" in the upper right corner), or it can Power off. Recovery Mode is an option, but does nothing but cycles to the Google initial screen.
In Fastboot mode the status says this:
FASTBOOT MODE
Product name - grouper (it got that far)
Variant - grouper
HU version - E3
LOCK STATE - UNLOCKED
Bootloader Version - N/A
Serial Number - 015d2109ab281807
SIGNING - not defined yet
Of course I can't get an MTP connection to Microsoft XP, but an "Unknown
device" error shows up under USB when I connect the cable. No drivers from WMSDK kit or any from WugFresh worked.
Oh, and by the way, the WugFresh backup didn't work for me. It saved next to nothing, but I have another type of backup that works, so no worry.
GOT ANY SUGGESTIONS?
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Captain Sweatpants said:
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Click to expand...
Click to collapse
{Q} Thanks Captain, I have been following the Guide instruction, but I have some other questions before I proceed.
In your Quote above you said “follow the sticky for reflashing”, I don’t know what you mean by a “sticky” and I have looked though a lot of the pages after the "[GUIDE] Flashing a Factory Image with fastboot / return to stock" and I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Since I didn't know that answer, I went a head and read the whole Guide and other questions popped up: If I have to download Java SE JDK will the Version 6 I already have work? The Oracle website you directed me to won’t let me download Version 8; however, Android SDK did accept Version 6 to install.
I did re-download all the drivers as instructed and put the JWR66V bootloader into the place of the JWR66Y one and then inserted bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, and flash-base.sh all into <my sdk directory>\platform-tools as the Guide says.
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
I don’t know what you mean by a “sticky"
Click to expand...
Click to collapse
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top.
I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Click to expand...
Click to collapse
Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
Click to expand...
Click to collapse
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Now its Driver installation issues
Captain Sweatpants said:
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top. Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
{Q} Installing the driver now seems to be the issue. I tried a couple of things:
1. I know this was not exactly appropriate, but I went into Device Manager, located the USB “Unknown Device”, tried to update
the Driver after selecting it, directed the screens to both the ‘supposed’ drivers in WugFresh and Adb subdir’s. None took.
2. Then I forced a new device though the Control Panel’s, Add New Hardware, navigated to “Add a new hardware device” and
selected “Google Nexus 7 ADB interface”, and it created the new device. The Device Manager showed and error on the
device, so I refreshed it with the Adb driver, with no different results.
3. I then added the device driver “Google Nexus Bootloader Interface” via Add New Hardware
4. I rebooted the computer. After it came back up…
5. I looked at the Device Manager with no change in the status of any of the Android or the Unknown USB Device.
6. I insured the N7 was in bootloader mode by rebooting with volume keys/on key.
7. I went ahead and ran “adb drivers” cmd after entering the “cd’ cmd. I got the following:
Bear with me as I have no screen printing capability at this time.
>Command Prompt screen:
>C:\<adb dir>\platform-tools> adb devices
>List of devices attached
>C:\<adb dir>>\platform-tools>
And as you can see, NO listing showed.
So what’s next? I have another XP computer I can try this on, but I will have to get all the Abd stuff over to it 1st. While you answer I will try that.
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Captain Sweatpants said:
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device.
Click to expand...
Click to collapse
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
nickynooner said:
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
Click to expand...
Click to collapse
It wouldn't work as I would need to be able to press buttons on the nexus.
If none of this is working then try wugfresh NRT again make sure you have the most up-to-date version from www.wugfresh.com its 1.8.2
The option you are looking for is unroot/back to stock there is an option for soft bricked make sure that is ticked
Sent from my Nexus 7
Hit thanks if I've helped
The Fat Lady Just Sang an Unhappy Song!
Hi Captain,
Thank you for all of your help and patience with me. I have read a lot more about the status of my device through looking at the XDA forum about other devices that have the kind of issue I do, and I have concluded mine is HARDbricked. I went ahead and ordered another motherboard off of eBay. My device was an 8G and I got a 32G replacement, making sure it was for my age of my N7. XDA forum and other websites say the boards are interchangeable. I was thinking about buying a new device anyway and this way I can upgrade and still have the same familiar device with no learning curve of a new one.
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.