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.

Need root without computer, bootloader unlocked...

I have checked at least hundred threads now, but my problem seems unique! (First time this happened to me )
When I connect my N7 (WiFi, 32 GB) to my laptop (Win 8.1), it says "USB device not recognized - The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." In Device Manager, it is like the image attached, no other recognition for the device. Upon selecting Properties, It says "Code 43" in status, also says "A request for the device descriptor failed". That happened with 2 computers; I used 2 cables (both worked previously). So it means N7's USB port is somehow malfunctioning. But it gets charged as well as ever!!
This started after I tried an OTA update of 4.4 earlier (the download had not completed, but a prior small update (1-3 MB) was installed).
Now, I have Android SDK (latest version) and installed those google USB driver and platform-tools. I have NRT 1.7.9 (which worked for me previously). But I cant get my N7 to answer to ADB requests. [highlight]Upon connecting USB, it says "Charging (USB)" but no option regarding PTP or MTP appears.[/highlight] I have developer tools installed. I followed the instructions given in NRT about ADB installation to the letter but still no progress. I have tried a factory reset too.
BTW, I dont have a custom recovery flashed. It vanished along with the precious root privilage.
Now the N7 is in Android 4.3 (JWR66Y), bootloader is unlocked, SuperSU is Installed (but do not work due to having no root access and I cant even Uninstall it for the same reasons!!!). Now the OTA update also do not work mysteriously (it downloaded the 4.4.2 update and went on to install it, but as the bar started filling, it only said "error" and stopped!!! no explanations whatsoever!!!!). I will be very happy any of the followings:
[highlight]1. root without computer (wireless ADB is also welcome),
2. working OTA, or anyhow the 4.4.2 update
3. working ADB connection with my laptop.[/highlight]
Any help will be very helpful... Thank you in advance...

If you can not communicate via USB hardware, then using fastboot is not an option (obviously). And so therefore the lock state of your bootloader is quite irrelevant, too.
Even if you were to get adb over tcp (WiFi) working, that doesn't get you much, as an adb login shell on a stock ROM is just an unprivileged user; it's not much different from using a terminal emulator app (from a privilege escalation point of view).
The only other thing left is an exploit (privilege escalation) method that runs under the stock ROM. Something similar to that Motochopper exploit from some time ago. I suppose that particular hole was plugged; whether or not a new exploit exists, I can't tell you.
You could always just send the tablet back for repair. Seems like not having a working USB port is pretty crippling to someone who wants to root, flash ROMs, copy backups off the tablet, etc.

Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...

Aaron061992 said:
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Click to expand...
Click to collapse
Well that is very different than having a broken USB port.
You probably noticed in your search that this forum is littered with thousands of reports from users complaining about their Windows drivers. It gets pretty old, frankly. (No drivers are needed at all for Linux or Mac OS/X).
Here is a suggestion that I made in another thread just a few days ago about using fastboot under Linux - in your case, you will be on your way after installing a recovery, e.g.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-grouper.img
I even attached the most recent version of the (Android SDK Linux) fastboot to that post.
Note that you don't even need a dual-boot PC or PC with a semi-permanent Linux install; you can do the whole thing with one of those "Live CD" boots and a USB stick.
good luck

[Q] Ach! Doh! I did it. I bricked my N7 while going 4.4 to 4.3

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! New to LG; some basic ROM questions

Hi All,
My wife is headed to Italy at the end of the month, and I purchased an unlocked Verizon VS995 V20 off ebay for her.
She is running a stock ROM Galaxy Note 2 (she likes things the way they are on KitKat , but that's another story ).
I've rooted Samsung, HTC and Moto phones in the past, but this is my first LG. From what I can tell, the V20 is a solid phone!
I tried looking online but am not finding clear answers yet, so here's my basic questions:
1. since the phone is supposedly unlocked, is there a specific ADB command I can use to verify it? Or should I go through a root process to be sure?
2. we are on T-Mobile, so I'd like to go to a stock AOSP Android 7 ROM with no carrier bloat. If the phone is unlocked, or if I do root, would there be any issues since this is a Verizon-branded phone?
3. not trying to start any bickering, but any recommendations for a stock vanilla Nougat ROM?
My phone info:
Build # NRD90M
Config ver B26.LGE.VS995.0
Software ver VS99513A
I appreciate any replies and thoughts, and I'm looking forward to seeing what this phone can do!
regards,
motionmonk

First, this post belongs in the Q&A section, hopefully a mod will move it.
Second, what security patch version are you on. It is listed in software info. If it is anything later than Dec 2016, then you can't root (yet).

My apologies to the Mods; I wasn't sure which section this should go in.
The Security Patch Level is dated Dec 1, 2016. Would that still work?

Wrong thread

Yes, you can root. Before you do, find the patched LG UP thread and do a dump of your entire phone. If you ever want to go back to stock, you will have the files. Also, it is good to have a full backup of your phone as it currently is.
I don't have a VS995, but I am willing to offer all the help I can.
-- Brian

runningnak3d said:
Yes, you can root. Before you do, find the patched LG UP thread and do a dump of your entire phone. If you ever want to go back to stock, you will have the files. Also, it is good to have a full backup of your phone as it currently is.
I don't have a VS995, but I am willing to offer all the help I can.
-- Brian
Click to expand...
Click to collapse
Thank you very much for the offer of help. It's sincerely appreciated.
I have some more research to do today, and then I'll reach out with more specifics.
And to all, sorry for posting in the wrong area... it looks like the Mods moved this to the Q&A area overnite.
-motionmonk

Ok, I think I have everything now.
I am using the Dirty Santa setup, and have installed the Terminal Emulator to the V20, loaded the twrp image to my SD card, and have the Required Files from the c20-root.zip loaded on the desktop.
Inside Win7 I installed the minimal package for ADB and Fastboot, and then connected the V20 as a device. Double-clicking on RUNMEFIRST.bat briefly shows a window, but it auto closes itself. I tried running the adb shell and doing "adb devices", but nothing is showing up. Doing adb logcat says it's waiting for devices too.
I feel I've already missed a step...

You enabled USB debugging?

runningnak3d said:
You enabled USB debugging?
Click to expand...
Click to collapse
Interesting... no, it's greyed out. I did the 7x tap to get Developer Options before I started, and thought I had checked it.
I have the phone set for File Transfer when connected to the Computer... but I don't think that would effect this setting.
Any ideas?

motionmonk said:
Interesting... no, it's greyed out. I did the 7x tap to get Developer Options before I started, and thought I had checked it.
I have the phone set for File Transfer when connected to the Computer... but I don't think that would effect this setting.
Any ideas?
Click to expand...
Click to collapse
The USB mode setting has no effect on adb. Also how is it greyed out? Can't say I've ever heard of something like that before.

Thisisabadname said:
The USB mode setting has no effect on adb. Also how is it greyed out? Can't say I've ever heard of something like that before.
Click to expand...
Click to collapse
I certainly can't claim to know much about this process, but I've never seen it before either on any other phone I've rooted.
I'll try and upload a shot of the Developer Option screen to this msg. I haven't done that yet here.
Weird, huh?

motionmonk said:
I certainly can't claim to know much about this process, but I've never seen it before either on any other phone I've rooted.
I'll try and upload a shot of the Developer Option screen to this msg. I haven't done that yet here.
Weird, huh?
Click to expand...
Click to collapse
Did you try unplugging it before trying to turn it on? It might be blocked cause it's currently connected

Thisisabadname said:
Did you try unplugging it before trying to turn it on? It might be blocked cause it's currently connected
Click to expand...
Click to collapse
I think I understand what you are asking...
-disconnect phone from computer
-restart phone
-reboot Windows
-phone is up; check Dev Options-- no joy.
-connect phone to Windows, VS995 is recognized. Type adb devices... nothing listed.

Latest Update
<I messed up this post, so I'd like to take it back>

While booted into the OS, you have to authorize it. Plug in the USB cable, and a prompt will come up.

Can't open /system
Ok, I'm stuck on Step 1 (which is farther than I've been till now; don't laugh)...
Just before the start of Step2.bat instructions, I need to applypatch after checking with Terminal Emulator that I have an untrusted_app.
I copy/pasted the applypatch instructions, and it reports:
elsa:/ # applypatch /system/bin/atd /storage/emulated/0/dirtysanta
could not open /system/bin/atd
This one I can't figure out. Have I missed something?

Install a terminal on your phone. That command goes into a terminal on your phone, not on your PC.

Ack. It even says so
I started Step2, and as a Verizon phone, the vibrator is going off, which is recognized in the instructions.
How long does Step2 take? I've been going for almost an hour.
On Terminal Emulator, it reports:
[1140] Fastboot mode started

Does your PHONE say fastboot? It should not take more than a few minutes.
-- Brian

runningnak3d said:
Does your PHONE say fastboot? It should not take more than a few minutes.
-- Brian
Click to expand...
Click to collapse
I thought I sent a reply but I guess it didn't go through.
-Yes, the Phone screen does say FASTBOOT MODE in Red, then multiple spec lines of Product Name, HW Version, Serial number, then at the end it says [1140] Fastboot mode started.
Back from lunch. Should I pull the battery and restart from Step1? Or can I continue from Step2?
I don't know why the root is so confusing for me. Thank you again for all your help Brian!

[help] My Chinese Nokia X6 either is or appears to be rooted out of the box.

I bought a Nokia X6 from China and the phone appears to be rooted. The play store app System info says that I have all the correct specs but also tells me the phone is rooted. Additionally, when booting my phone gives me a message that says: Your device has loaded a different operating system. I have pretty much no idea what to do and honestly just would want a normal stock phone so any help would be very much appreciated.

Same here, except I have no issues with it saying its rooted
just the boot message

If you want a normal stock phone then don't buy Chinese oem devices. They have to add tons of tracking and spying software that is required by the Chinese government. You can research it. Many are even banned in many countries due to their back ally tactics

Darth_revan_returns said:
Same here, except I have no issues with it saying its rooted
just the boot message
Click to expand...
Click to collapse
I managed to solve the problem. If you don't have a lot of experience with Android, you'll have to do a bunch of research, but you should manage. Very roughly, I pretty much flashed a new operating system on the phone. I found the correct os rom from here: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657. I'm definitely a novice in doing weird **** with androids so don't consider me an expert or anything, but I did get my phone to work.
If you don't know what to do here's a rough guide.
1. Get adb to work
Adb is basically a way for your computer to tell crude instructions to your phone and all kinds of random ****. The very very first thing you should do is unlock developer options and turn on developer options by going to settings->system->about phone and click on build number something like 7 times and then go back to system, where developer options have appeared and turn on OEM unlocking and usb debugging. You should be able to find some type of adb installer installer simply by googling how to install adb or something, I can't remember at all where i found mine from, but there are certainly a lot of guides online. It really doesn't matter that much if it's from a few years back, as long as adb works. Your phone should install all correct drivers from your phone simply by connecting it, but you may need to download qualcomm drivers online, I don't really know because I downloaded every random driver online until finally it worked. All I can say that to finally get it to work I connected my phone to my computer via cable with usb debugging enabled and clicked the windows message so that the phone agreed to the final necessary drivers and amazingly it worked. To make sure that everything you need is in working order type the following commands into adb:
First "adb devices" if it says something like device found, DRG...., everything's good so far
Then "adb reboot bootloader" and "fastboot devices", if it says the same thing again, adb is completely installed.
I found this to be by far the hardest part in the whole operation, because the Nokia X6 is such a new phone that there are no real guides or official drivers online. Don't be discouraged if it takes some time to get through this part!
2. Unlock your bootloader
Nokia is pretty cool and all, but that they are pretty restrictive with their phones so that you actually have to pay to a third party to be able to unlock your bootloader. You need to buy a bootloader unlock key from this place: https://www.techmesto.com/buy-nokia-bootloader-unlock-key/. I know it seems super shady, but it at least worked for me so there's that. I wouldn't really buy the unlock key before getting adb to work, though. After that, you'll probably be best off following this guide to unlock the bootloader: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
3. Install the nokia online service tool and nb0 unpacker
The Nokia OST you can find here: https://www.theandroidsoul.com/download-nokia-online-service-tool-ost/, and I think the guide there is pretty self-explanatory, so just follow that. The nb0 unpacker you can find here: https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464. This one should be very simple to install.
4. Download the Nokia X6 operating system and unpack it so you can flash it with the online service tool.
The nokia X6 operating system can be found from the google drive link in this post: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657, and be sure to pick the on mentioned in the post, the one labeled "DRG-229E-0-00CN-B01". After downloading it, you should be able to find a .nb0 file in the zip. Extract it somewhere nice and then use the nb0 unpacker you installed to unpack it. After this, open the mlf-file in the unpacked nb0 folder and follow the following instruction found on the download post i linked before:
"Modify *.mlf file, line 7 ~ 9;
INITOPTION = 0x20000
INITDLTYPE = 0x60
SECURITY_VER = 0x0001" @Xkernels
5. Flash the os on your phone
Make sure to delete everything from your phone before doing this, because every guide I've seen instructs to do this. This may not even be necessary as the OST setting you'll check later indicate that everything will be erased anyways, but idk what could happen so better safe than sorry. You can do this probably in many ways but one way i found is to go to recovery (type "adb reboot recovery" on your pc and then press the power and vol up button at the same time), and factory reset. Then go to the bootloader from there and type "fastboot erase system". A bunch of text should appear and you should be set to flash. Now with your phone connected to your pc, open the Nokia OST and "Select *.mlf files and tick "Normal Download", "Erase user data", "Erase error data", begin to flash." @Xkernels.
6. Your phone should be ready to use, though it will probably need some configuring
The first things you'll probably want to do is use the browser to download a google play apk online after which you can use the play store and download all necessary apps from online. I couldn't find netflix from the appstore but I simply downloaded the apk online and it works too. I had problems with the stock keyboard so I installed Gboard, but all apps should be in working order and my phone works without a hitch now!
For the record if you manage to brick your phone during the process, don't hold me liable. If you followed this guide, you probably bought a chinese random phone and it didn't work like you wanted it to and wanted to fix the problems by installing an operating system from online, using a guide from a person you didn't know at all. All I can say is that what I did worked for me and I simply wanted to help strangers on the internet and this worked for me. So if, because of this guide, everything is ****ed with your phone and your computer is full of viruses, I will most likely be glad to help and you can blame me by yourself, but I definitely would appreciate if you would simply be civil and not tell me how I'm an awful person, because once again, I'm just a Finnish guy, who himself bought a Nokia for 200€ from eBay and had to spend hours upon hours of my own time trying various methods of getting my phone to work and learning how to use adb and how to flash roms on my phone. Honestly the experience was pretty fun for me, because I like to do random **** like this and learning new things, but I did have other things to do with my time like study physics and even now I wrote this, in my own biased opinion pretty good, guide using my own time, simply because knowing I did something good brings joy to my heart.

vostok_amphibia said:
I managed to solve the problem. If you don't have a lot of experience with Android, you'll have to do a bunch of research, but you should manage. Very roughly, I pretty much flashed a new operating system on the phone. I found the correct os rom from here: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657. I'm definitely a novice in doing weird **** with androids so don't consider me an expert or anything, but I did get my phone to work.
If you don't know what to do here's a rough guide.
1. Get adb to work
Adb is basically a way for your computer to tell crude instructions to your phone and all kinds of random ****. The very very first thing you should do is unlock developer options and turn on developer options by going to settings->system->about phone and click on build number something like 7 times and then go back to system, where developer options have appeared and turn on OEM unlocking and usb debugging. You should be able to find some type of adb installer installer simply by googling how to install adb or something, I can't remember at all where i found mine from, but there are certainly a lot of guides online. It really doesn't matter that much if it's from a few years back, as long as adb works. Your phone should install all correct drivers from your phone simply by connecting it, but you may need to download qualcomm drivers online, I don't really know because I downloaded every random driver online until finally it worked. All I can say that to finally get it to work I connected my phone to my computer via cable with usb debugging enabled and clicked the windows message so that the phone agreed to the final necessary drivers and amazingly it worked. To make sure that everything you need is in working order type the following commands into adb:
First "adb devices" if it says something like device found, DRG...., everything's good so far
Then "adb reboot bootloader" and "fastboot devices", if it says the same thing again, adb is completely installed.
I found this to be by far the hardest part in the whole operation, because the Nokia X6 is such a new phone that there are no real guides or official drivers online. Don't be discouraged if it takes some time to get through this part!
2. Unlock your bootloader
Nokia is pretty cool and all, but that they are pretty restrictive with their phones so that you actually have to pay to a third party to be able to unlock your bootloader. You need to buy a bootloader unlock key from this place: https://www.techmesto.com/buy-nokia-bootloader-unlock-key/. I know it seems super shady, but it at least worked for me so there's that. I wouldn't really buy the unlock key before getting adb to work, though. After that, you'll probably be best off following this guide to unlock the bootloader: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
3. Install the nokia online service tool and nb0 unpacker
The Nokia OST you can find here: https://www.theandroidsoul.com/download-nokia-online-service-tool-ost/, and I think the guide there is pretty self-explanatory, so just follow that. The nb0 unpacker you can find here: https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464. This one should be very simple to install.
4. Download the Nokia X6 operating system and unpack it so you can flash it with the online service tool.
The nokia X6 operating system can be found from the google drive link in this post: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657, and be sure to pick the on mentioned in the post, the one labeled "DRG-229E-0-00CN-B01". After downloading it, you should be able to find a .nb0 file in the zip. Extract it somewhere nice and then use the nb0 unpacker you installed to unpack it. After this, open the mlf-file in the unpacked nb0 folder and follow the following instruction found on the download post i linked before:
"Modify *.mlf file, line 7 ~ 9;
INITOPTION = 0x20000
INITDLTYPE = 0x60
SECURITY_VER = 0x0001" @Xkernels
5. Flash the os on your phone
Make sure to delete everything from your phone before doing this, because every guide I've seen instructs to do this. This may not even be necessary as the OST setting you'll check later indicate that everything will be erased anyways, but idk what could happen so better safe than sorry. You can do this probably in many ways but one way i found is to go to recovery (type "adb reboot recovery" on your pc and then press the power and vol up button at the same time), and factory reset. Then go to the bootloader from there and type "fastboot erase system". A bunch of text should appear and you should be set to flash. Now with your phone connected to your pc, open the Nokia OST and "Select *.mlf files and tick "Normal Download", "Erase user data", "Erase error data", begin to flash." @Xkernels.
6. Your phone should be ready to use, though it will probably need some configuring
The first things you'll probably want to do is use the browser to download a google play apk online after which you can use the play store and download all necessary apps from online. I couldn't find netflix from the appstore but I simply downloaded the apk online and it works too. I had problems with the stock keyboard so I installed Gboard, but all apps should be in working order and my phone works without a hitch now!
For the record if you manage to brick your phone during the process, don't hold me liable. If you followed this guide, you probably bought a chinese random phone and it didn't work like you wanted it to and wanted to fix the problems by installing an operating system from online, using a guide from a person you didn't know at all. All I can say is that what I did worked for me and I simply wanted to help strangers on the internet and this worked for me. So if, because of this guide, everything is ****ed with your phone and your computer is full of viruses, I will most likely be glad to help and you can blame me by yourself, but I definitely would appreciate if you would simply be civil and not tell me how I'm an awful person, because once again, I'm just a Finnish guy, who himself bought a Nokia for 200€ from eBay and had to spend hours upon hours of my own time trying various methods of getting my phone to work and learning how to use adb and how to flash roms on my phone. Honestly the experience was pretty fun for me, because I like to do random **** like this and learning new things, but I did have other things to do with my time like study physics and even now I wrote this, in my own biased opinion pretty good, guide using my own time, simply because knowing I did something good brings joy to my heart.
Click to expand...
Click to collapse
Thanks man, now that the 6.1 plus is coming soon I think we'll be able to put it on using this guide!

vostok_amphibia said:
I bought a Nokia X6 from China and the phone appears to be rooted. The play store app System info says that I have all the correct specs but also tells me the phone is rooted. Additionally, when booting my phone gives me a message that says: Your device has loaded a different operating system. I have pretty much no idea what to do and honestly just would want a normal stock phone so any help would be very much appreciated.
Click to expand...
Click to collapse
Same here, so anyone help us to solve this problem?