Database Users

[Q] Device Offline: Brand New Nexus 4, 4.2.2

So, got a replacement Nexus 4 today, and it's been updated to 4.2.2 and for some reason, it comes up as offline on ADB no matter what I do.
However, the funny thing is, my other Nexus 4, the one I was getting the replacement for, connects to ADB wonderfully. Shows up as a device, no problem. It's on 4.2.1.
Question 1: How can I manage to get the gosh darn thing to be recognized as online. I've tried two different cables, both of which connect with the 4.2.1 nexus but not the 4.2.2.
Question 2: Can I install a custom recovery without ADB?
EDIT: Consider this solved... it seems I had a bit much to drink... little did I know I don't need ADB... just fastboot.
Oh well All is well.

x3phyr said:
So, got a replacement Nexus 4 today, and it's been updated to 4.2.2 and for some reason, it comes up as offline on ADB no matter what I do.
However, the funny thing is, my other Nexus 4, the one I was getting the replacement for, connects to ADB wonderfully. Shows up as a device, no problem. It's on 4.2.1.
Question 1: How can I manage to get the gosh darn thing to be recognized as online. I've tried two different cables, both of which connect with the 4.2.1 nexus but not the 4.2.2.
Question 2: Can I install a custom recovery without ADB?
Click to expand...
Click to collapse
Is the device recognized by Windows? Checking under Computer>Properties>Device Manager does the phone show up correctly?

Use the search in the future please. Just update ADB. With 4.2.2 the phone will pop up to ask you if you want to authorize your computer to access the phone, this "feature" requires the updated ADB, no change to fastboot, so you'll be fine getting the recovery on there, but ffr with ADB.

Unlock and Root 4.2.2
h.nocturna said:
Is the device recognized by Windows? Checking under Computer>Properties>Device Manager does the phone show up correctly?
Click to expand...
Click to collapse
If you're trying to unlock and root your nexus, you can follow the steps on this forum http://forum.xda-developers.com/show....php?t=2147413 There's another way to unlock and root your device (via adb) since Wugfresh's NRT doesn't support 4.2.2. Just make sure you use the correct .img file for your specific device.
You can also update any old SDK files by opening the SDK Manager on your pc.

USSENTERNCC1701E said:
Use the search in the future please. Just update ADB. With 4.2.2 the phone will pop up to ask you if you want to authorize your computer to access the phone, this "feature" requires the updated ADB, no change to fastboot, so you'll be fine getting the recovery on there, but ffr with ADB.
Click to expand...
Click to collapse
I did use the search feature and I will have you know that the FIRST THING I DID was download and update the absolute most recent ADB so thank you, but the degrading "learn to search" comment was not applicable.
Anyhow, this whole conversation is fairly irrelevant since I got what I needed to do, done.
Thanks for the help everyone.

Mind telling me what you did, im stuck in the same situation

gsusx said:
Mind telling me what you did, im stuck in the same situation
Click to expand...
Click to collapse
same situation. whatd you end up doing?

gsusx said:
Mind telling me what you did, im stuck in the same situation
Click to expand...
Click to collapse
whocanhebe said:
same situation. whatd you end up doing?
Click to expand...
Click to collapse
Download this and replace your old adb & fastboot
http://forum.xda-developers.com/showpost.php?p=37935821&postcount=26

Have you tried entering:
adb kill server
adb start-server
Read this:
http://stackoverflow.com/questions/8162581/why-does-adb-return-offline-after-the-device-string
It worked for me. I did it last night when I had the same issue.

hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong

gsusx said:
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
Click to expand...
Click to collapse
if you have updated adb try killing the server with adb kill-server

EZ
Hey
Guys had the same problem and it was really simple to solve.
When you start adb and type adb devices and your device comes offline.
Go to settings>developer options - unchecked USB debugging and check it again, right after your computer will recognize your phone and in the phone will appear a box with your computer's Mac address asking you to allow connection.

gsusx said:
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
Click to expand...
Click to collapse
Have you downloaded the updated version of adb from post #8? And make sure you use that rather than whichever you were using? That was all I needed to do to get my offline Nexus 4 online again...

It have something to do with usb debugging not being enabled on the new phone?
Sent from my Nexus 4 using Tapatalk 2

VoiD_Dweller said:
It have something to do with usb debugging not being enabled on the new phone?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
In that case, I don't think you get the "offline" status from adb - I think it wouldn't appear at all?

It appears that the Linux SDK isn't fully updated (as of today, newest build is 0219). My adb version is 1.0.29, and from a bit of research it seems that that version cannot ask your device for the OK it needs in 4.2.2. I hope I'm wrong though...
EDIT: When I had basically given up, I re-checked one last time, and there it was on my screen; the OK. Unfortunately, I have no idea what permitted this. Let the building start. Good luck to all of you!

jotss said:
Hey
Guys had the same problem and it was really simple to solve.
When you start adb and type adb devices and your device comes offline.
Go to settings>developer options - unchecked USB debugging and check it again, right after your computer will recognize your phone and in the phone will appear a box with your computer's Mac address asking you to allow connection.
Click to expand...
Click to collapse
^ This worked for me. Thanks a lot! :good:

[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.

Zenfone 2 and Fastboot with Ubuntu

This post is for everyone having trouble using Fastboot with his Zenfone 2 under Ubuntu and derivatives.
My sending was recognized immediately by ADB on my Linux install but Fastboot wouldn't recognize it by no means. I was sure that the phone was in Bootloader mode, the access rules were set up correctly for my USB device as well but still bo Fastboot.
After browsing the web for quite some time, I finally found the culprit!
The Fastboot version that is installed by
Code:
*sudo apt-get install android-tools-fastboot
Is outdated and not working with Intel-based phones.
You need at least fastboot version 1.0.32.
Being by no means a Linux specialist, I simply downloaded the newest Fastboot binary, replaced the old one and that's it.
Make sure to give the appropriate user and execution rights to the new binary.
Please note that copying the binary is a noob solution. Real experts would have synchronized the appropriate repository and compiled it from sources but I am not at that level.
If this has already been described somewhere in this forum, please apologize.

Super new to this but I hate the ZenFone UI. I'm wondering if you happen to have steps to root and flash cm for ZenFone 2 using Ubuntu. Everything I have found says that windows is needed.
1. Are the tools automatically downloaded. I think I have those.
2 I have adb and fastboot downloaded and my ZenFone 2 is recognized.
I got nervous once i got here because I was reading that a lot of people were bricking their phones following instructions. Thanks in advance!
Sent from my ASUS_Z00AD using XDA Free mobile app

Jerict09 said:
Super new to this but I hate the ZenFone UI. I'm wondering if you happen to have steps to root and flash cm for ZenFone 2 using Ubuntu. Everything I have found says that windows is needed.
1. Are the tools automatically downloaded. I think I have those.
2 I have adb and fastboot downloaded and my ZenFone 2 is recognized.
I got nervous once i got here because I was reading that a lot of people were bricking their phones following instructions. Thanks in advance!
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
To flash CM you don't need Windows.
I believe Ubuntu has Fastboot in the terminal integrated already.
I'm not sure how it works, to be honest but the same old command
Fastboot Flash Recovery nameofrecovery.img AFTER you unlock the bootloader, which is also done through Fastboot, should work the same way as it does on Winblows.

Just take it slow. Maybe try rooting first, see how that goes for a few days, then consider the bootloader unlock and reflashing.
I prefer ubuntu, and tried to root with method 3 via ubuntu 14.04. After spending 2 hours trying to get the right tools and configuration to talk to the phone with only partial success, I gave up and used windows. Within about 5 minutes I had my phone rooted.

What are the best precautions to to not brick your device? Also i have seen many threads to rooting and flashing, is there an url you can redirect me too? I almost forgot to ask, is twrp an app you install after root or do you have to install that when you unlock boot loader? And do I have to downgrade my firmware before the install? Thanks in advance for all of your all's help, I'm sure its annoying answering these questions!!!
Sent from my ASUS_Z00AD using XDA Free mobile app

rbrewer123 said:
Just take it slow. Maybe try rooting first, see how that goes for a few days, then consider the bootloader unlock and reflashing.
I prefer ubuntu, and tried to root with method 3 via ubuntu 14.04. After spending 2 hours trying to get the right tools and configuration to talk to the phone with only partial success, I gave up and used windows. Within about 5 minutes I had my phone rooted.
Click to expand...
Click to collapse
Same thing here.
Is impossible to make fastboot to work in Zenfone 2 using Ubuntu, since there's no mention to fastboot 1.0.32 in the internet.
Today is may day 2 trying and I'm already setting ADB and Fastboot on Windows to root my device.

[Question] Use Tab A 10.1 tablet as PC for ADB and fastboot?

Hey all... Hoping someone could direct me to a guide for installing adb and fastboot to my tab a 10.1 sm-t580. There is a catch... ADB and fastboot would have to be able to detect Android 6.0 devices and higher.
I have found guides helping me install ADB and fastboot on my tablet. But everyone I found is not capable of detecting Android lollipop and higher devices.
Or at least every version I have tried gives me the output of "device offline"... Which from my searching is because lollipop and higher is not compatible.
Thanks in advance

30mmrain said:
Hey all... Hoping someone could direct me to a guide for installing adb and fastboot to my tab a 10.1 sm-t580. There is a catch... ADB and fastboot would have to be able to detect Android 6.0 devices and higher.
I have found guides helping me install ADB and fastboot on my tablet. But everyone I found is not capable of detecting Android lollipop and higher devices.
Or at least every version I have tried gives me the output of "device offline"... Which from my searching is because lollipop and higher is not compatible.
Thanks in advance
Click to expand...
Click to collapse
I think you're getting a bit confused about adb and fastboot.
Fastboot isn't supported on Samsung devices.
ADB isn't installed to an android device, it's already part of the firmware, it's also not dependent on Android version.
If you are getting the offline message then you need to enable USB debugging in developer settings and then accept the pop up to allow ADB access.

ashyx said:
I think you're getting a bit confused about adb and fastboot.
Fastboot isn't supported on Samsung devices.
ADB isn't installed to an android device, it's already part of the firmware, it's also not dependent on Android version.
If you are getting the offline message then you need to enable USB debugging in developer settings and then accept the pop up to allow ADB access.
Click to expand...
Click to collapse
you could be right I am still newer to modding phones... Thanks for the correction.
However, what I'm trying to do is used my tab a to fastboot my Moto G4 and to be able to use my tab a instead of a PC on the go. While trying this I confirmed that my Moto G4 did in fact have USB debugging enabled but I was still getting the device offline error in the ADB terminal. Any other thoughts or suggestions to check?
From what I've been able to tell... It's because my G4 is running Android 6.0. But maybe I could be misled that that is the cause of the issue.

30mmrain said:
you could be right I am still newer to modding phones... Thanks for the correction.
However, what I'm trying to do is used my tab a to fastboot my Moto G4 and to be able to use my tab a instead of a PC. Wind trying this I confirmed that my Moto G4 did in fact have USB debugging enabled but I was still getting the device offline error in the ADB terminal. Any other thoughts or suggestions to check?
From what I've been able to tell... It's because my G4 is running Android 6.0. But maybe I could be misled that that is the cause of the issue.
Click to expand...
Click to collapse
You need to use a PC with ADB, as you need to authorise the PC to have the RSA finger print of the PC match the adb device key, otherwise you will get the device unauthorised error.
Not sure how you are trying to do this from another Android device?
Also Fastboot and ADB are 2 different modes.
Can you explain in more detail what you are attempting to do?

ashyx said:
You need to use a PC with ADB, as you need to authorise the PC to have the RSA finger print of the PC match the adb device key, otherwise you will get the device unauthorised error.
Not sure how you are trying to do this from another Android device?
Also Fastboot and ADB are 2 different modes.
Can you explain in more detail what you are attempting to do?
Click to expand...
Click to collapse
So I found a guide that will let you use ADB and fastboot on an Android device while in a terminal. I was hoping to use my tab a to unlock bootloaders, falsh recoveries, falsh logo.Bin files and other related tasks while on the go. Instead of needing to have access to a PC.
The main driving factor behind this to be able to still tinker around while others use the home PC for homework, watching movies, and other stuff like that.
So if using an Android device for this is not possible... Well then at least I know. But if it is... And I'm looking in the wrong direction... Please show me the right one!

30mmrain said:
So I found a guide that will let you use ADB and fastboot on an Android device while in a terminal. I was hoping to use my tab a to unlock bootloaders, falsh recoveries, falsh logo.Bin files and other related tasks while on the go. Instead of needing to have access to a PC.
The main driving factor behind this to be able to still tinker around while others use the home PC for homework, watching movies, and other stuff like that.
So if using an Android device for this is not possible... Well then at least I know. But if it is... And I'm looking in the wrong direction... Please show me the right one!
Click to expand...
Click to collapse
ADB is a command line utility intended for use with a PC.
Pretty much all of the commands you can use in ADB you can use in a terminal on the Android device itself.
You can still achieve what you require via a root shell in a terminal on the device.
You don't always need a PC running ADB. ADB is basically just an interface between PC and Android device.
The commands you use are actually part of the android device software not ADB.
There are also other ways to customise a device, for instance a custom recovery such as twrp is a must for anyone that wants to modify or flash things to an android device as is a rooted device.
There are also apps like FLASHFIRE that can accomplish much the same thing.

ashyx said:
ADB is a command line utility intended for use with a PC.
Pretty much all of the commands you can use in ADB you can use in a terminal on the Android device itself.
You can still achieve what you require via a root shell in a terminal on the device.
You don't always need a PC running ADB. ADB is basically just an interface between PC and Android device.
The commands you use are actually part of the android device software not ADB.
There are also other ways to customise a device, for instance a custom recovery such as twrp is a must for anyone that wants to modify or flash things to an android device as is a rooted device.
There are also apps like FLASHFIRE that can accomplish much the same thing.
Click to expand...
Click to collapse
Thanks a bunch bud... You have been really helpful! I'll start doing more research based on your suggestions.

LG aristo 2 (K8 2018)

Since the majority of the hardware between the devices is gonna be almost exactly the same, I'mma give a shot at rooting it. Picking up tomorrow, so hopefully it goes well

I just got this phone. Let me know how what happens please.

tge101 said:
I just got this phone. Let me know how what happens please.
Click to expand...
Click to collapse
Yeah, I'll keep a heads up. I'm sitting in metro now tryna see what's going on, small argument. Their commercials in Philly don't mention that you need to switch carriers for the rebates.

I'll probably be getting one next week. Says it has 7.1.2 an it weighs less? Cool

attempt
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.

tribal1209 said:
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.
Click to expand...
Click to collapse
Are you trying to root the aristo or aristo 2?

Aristo 2. Sorry, kind of diving in head first with this whole process. If im doing something obviously wrong go easy on me lol.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
Aristo 2

Hmm and you flashed the twrp that was for the aristo right?

Well the TWRP files i used were on *How To* forums posts and youtube videos for the original LG Aristo. Everything was going fine but the touch screen while in TWRP does not work. Maybe there os a different version I can try? Do any of you guys have any ideas, my understanding though is that TWRP has to be created for a specific device once released. Is thats whats going wrong?

you unlocked the bootloader and flashed the aristo 1 recovery thats what you did so far right?

The aristo 1 recovery will not work at all.
The screens are of the same build, but different composition.
That's why I wanted to test this myself before posting further on the subject.
I can risk my phone, most of you cant.

I figured as much. Thanks for the info! Just got mine today. Glad the aristo's battery works in the aristo2 as i bought a couple batteries for it. I still do like the aristo though it feels a bit better in my hand.

Well luckily It seems i have not screwed up my phone. Have reset and wiped it multiple times which was annoying, but seems to be ok. It sucks because it looks like the touch screen alone is whats screwing me over. If only i had a way around it. Then again im sure you guys have a better idea of whats going on. Guess ill just be patient until more is posted on subject.

We need a new recovery for this anyway. Since the aristo 2 isn't gonna have multiple versions (besides the Korean base model the 2 is built after), we should be able to build just one recovery using the model number as it's target, we can make it borderline universal if a new version were to pop up.
I decided against going the metro route, buying mine in bulk. So I'll have one to smash when this is all over.

The TWRP method works the same as the Aristo, and the TWRP recovery IS compatible. However the touch screen does not function.. Is there a way to get it to work?

@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App

brad2192 said:
@[email protected]@tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Not to sound sceptical but is this the real deal?

spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Please someone let me know! I want this phone rooted (Its an awesome phone) but want some verification before I start flashing and downloading random files.

spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Yes, it is. What I did was use LG firmware extractor and extracted the boot image, then I proceeded to patch the boot image with magisk manager. Enabling OEM unlock allows me to flash the boot image with the newly-created custom one. Remember though, you should create a backup of your device because enabling OEM unlock will completely erase everything.

brad2192 said:
@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Supposedly the img you posted is simply a modified version of Magisk you posted. Someone please explain to me (Who is new to this whole process) why this supposed explanation does not involve any recovery program or requiring of wiping/clearing any cache or what have you?