Related
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.
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!
UPDATE -- ISSUE RESOLVED
*** New OTA available ***
See links below
Updated zip confirmed working here:
https://plus.google.com/100708818877715770270/posts/dEyVgqmURw2
Android Beta Program:
https://g.co/androidbeta
OTA Download:
NEW (fixes both OTA and sideload failures)
https://ota.googlezip.net/packages/.../1c0e174d9aeefbb176b4dd38b48270a0fd4082d9.zip
pangolin.rollin said:
For those experiencing issues updating to 8.1 on locked n stock f/w there is now a fix!!!
Source and Credit goes to "AC" : [url]https://issuetracker.google.com/issues/68264793[/URL]
See post #64 and #71
FIX SUMMARY
1. Enroll in beta ota
2. Download ota
3. Enable Developer mode
4. When update screen says "Reboot to update" DON'T click it but rather issue "adb reboot recovery"
5. Once in bootloader go to recovery like normal and ensure it says recovery 8.1
6. You may then enable update from adb for sideload.
7. When pixel is in ready to receive update issue "adb sideload <update.zip>"
8. Profit
Android Beta Program:
https://g.co/androidbeta
OTA Download:
[url]https://ota.googlezip.net/packages/ota-api/google_sailfish_sailfish/42c4425cf03125fe7c535e39cbac7d17c1a2f65a.zip[/URL]
Please post your success stories or issues.
I was on OPR3.170623.008 when this was done.
Click to expand...
Click to collapse
Credit goes to @ACastanza ,
Here is the mentioned fix by him/her : https://forum.xda-developers.com/showpost.php?p=74331289&postcount=51
Although i commend you trying to summarize the steps, they are wrong
adb reboot recovery is not a valid command ; i believe what you meant was
Code:
adb reboot bootloader
And i am not sure about this, but i think turning on developer mode is entirely optional.
NoobInToto said:
Credit goes to @ACastanza ,
Here is the mentioned fix by him/her : https://forum.xda-developers.com/showpost.php?p=74331289&postcount=51
...
And i am not sure about this, but i think turning on developer mode is entirely optional.
Click to expand...
Click to collapse
Oops yeah updated to bootloader, hadn't seen the post before or anything on XDA. Been following the normal circles. Can't hurt to spread the news!
The whole reason for suggesting the "optional" part of developer mode is cause if you try just the regular reboot /key press combo and miss it you have to redo the OTA download which is rather annoying. Rather just remove that possibility.
NoobInToto said:
Credit goes to @ACastanza ,
Here is the mentioned fix by him/her : https://forum.xda-developers.com/showpost.php?p=74331289&postcount=51
Although i commend you trying to summarize the steps, they are wrong
adb reboot recovery is not a valid command ; i believe what you meant was
Code:
adb reboot bootloader
And i am not sure about this, but i think turning on developer mode is entirely optional.
Click to expand...
Click to collapse
adb reboot recovery is definitely a valid command (assuming you're running a current version of ADB).
Enabling developer mode was not part of my original post, I don't think it is required, but then I was running it anyway. Entering recovery through a command rather than having to catch it at exactly the right moment with the key command is definitely easier, but I hadn't tested it that way when I did this originally. Glad this works too, it's much easier.
Also, glad people are finding this useful!
pangolin.rollin said:
Oops yeah updated to bootloader, hadn't seen the post before or anything on XDA. Been following the normal circles. Can't hurt to spread the news!
The whole reason for suggesting the "optional" part of developer mode is cause if you try just the regular reboot /key press combo and miss it you have to redo the OTA download which is rather annoying. Rather just remove that possibility.
Click to expand...
Click to collapse
Ah, now I get it. I forgot you needed usb debugging for adb when booted in system.
Anyways, booting in bootloader mode was easy, it is very hard to miss. One has to press power+volume down immediately after first bootloop, when the screen is back, and i was able to get into bootloader mode within 1 second.
---------- Post added at 05:11 AM ---------- Previous post was at 05:09 AM ----------
ACastanza said:
adb reboot recovery is definitely a valid command (assuming you're running a current version of ADB).
Enabling developer mode was not part of my original post, I don't think it is required, but then I was running it anyway. Entering recovery through a command rather than having to catch it at exactly the right moment with the key command is definitely easier, but I hadn't tested it that way when I did this originally. Glad this works too, it's much easier.
Also, glad people are finding this useful!
Click to expand...
Click to collapse
I had checked adb reboot recovery when booted in system. It did not work in 8.0.0.
Woops, I only read the first part of your post. Nevermind.
NoobInToto said:
I had checked adb reboot recovery when booted in system. It did not work in 8.0.0.
Click to expand...
Click to collapse
Your right it doesn't work in 8.0. That's why I specified to do it when it says "reboot to update" because when the system "pre-loads" the OTA it switches the active boot slot for next reboot. That's why doing it this way works as well.
ACastanza said:
Woops, I only read the first part of your post. Nevermind.
Click to expand...
Click to collapse
Huh? lol..
Anyways man didn't mean to steal your thunder. Just glad we're on 8.1.
You're the best! :good:
pangolin.rollin said:
Huh? lol..
Anyways man didn't mean to steal your thunder. Just glad we're on 8.1.
You're the best! :good:
Click to expand...
Click to collapse
No worries! Just glad people are getting updated without needing to factory reset.
(ADB rebot recovery actually does work on 8.0 but you need to have adb debugging enabled and need a new-ish version of the ADB binary).
ACastanza said:
No worries! Just glad people are getting updated without needing to factory reset.
(ADB rebot recovery actually does work on 8.0 but you need to have adb debugging enabled and need a new-ish version of the ADB binary).
Click to expand...
Click to collapse
Oh, yeah, the latest one not only has reboot recovery, but direct reboot to sideload options too....sweet
Btw there is a second workaround. It involves adb sideloading the same build (8.0.0) and then sideloading the Dev preview.
This worked for me. Looked like it was bootlooping again at first, but eventually booted into 8.1.0. Thanks!
invisibro said:
This worked for me. Looked like it was bootlooping again at first, but eventually booted into 8.1.0. Thanks!
Click to expand...
Click to collapse
Yup, strangely enough, that is the expected behavior for this workaround. @pangolin.rollin should include info about it in the OP post.
What am I missing here? I enrolled in the beta (Verizon locked bl) yesterday and within about an hour I had a notification to update to the beta. I clicked download and install and on the reboot I was running 8.1. What's all this about bootlooping, slots, rebooting bootloader? I did none of that and it worked flawlessly.
NoobInToto said:
Yup, strangely enough, that is the expected behavior for this workaround. @pangolin.rollin should include info about it in the OP post.
Click to expand...
Click to collapse
Updated op thanks
** Fixes "parse error -22" and update not installed, while this works first boot looks like it's looping. **
bobby janow said:
What am I missing here? I enrolled in the beta (Verizon locked bl) yesterday and within about an hour I had a notification to update to the beta. I clicked download and install and on the reboot I was running 8.1. What's all this about bootlooping, slots, rebooting bootloader? I did none of that and it worked flawlessly.
Click to expand...
Click to collapse
Your lucky then! Not sure of the official cause of the errors and why some work and some don't. But seems some devices have issues verifying. That's why Google even pulled ota images.
So I presume that the only problems were with sideloading? I never do that on my Pixel since I just like it updating in the background, reboot and done. With a locked bootloader I can't take a chance of doing something wrong. If they send me an image or OTA that bootloops then it's not my problem and they have to either fix it or replace it. Nonetheless, it's working very well and the reboot wasn't long at all. Might be the better way to go.
I did this fix and although it did work, now when I wake the device back up it takes a long time to do so. Double tapping the screen doesn't work at all, and when I hit the power button it takes about 5 seconds before the screen turns on. I'm going to try to sideload the ota again and see if it fixes it.
EDIT: Nope, still having the same issue
cred05 said:
I did this fix and although it did work, now when I wake the device back up it takes a long time to do so. Double tapping the screen doesn't work at all, and when I hit the power button it takes about 5 seconds before the screen turns on. I'm going to try to sideload the ota again and see if it fixes it.
EDIT: Nope, still having the same issue
Click to expand...
Click to collapse
Haven't heard of this problem yet.. were you on stock OPR3 with locked bootloader?
There is a new OTA (for same build, but new working OTA) for 8.1 rolling out.
https://plus.google.com/100708818877715770270/posts/dEyVgqmURw2
Please can someone grab the OTA URL?
Settings > System > Developer Options > Take Bug Report > Full Bug Report, then email it to yourself (or PM it to me) and search for the URL ending with ".zip".
I don't have a sailfish device on me right now to do it myself. Thanks!
Edit: here it is
https://ota.googlezip.net/packages/.../1c0e174d9aeefbb176b4dd38b48270a0fd4082d9.zip
pangolin.rollin said:
Haven't heard of this problem yet.. were you on stock OPR3 with locked bootloader?
Click to expand...
Click to collapse
I was on stock 8.0 OTA, locked bootloader. The issue seemed to have gone away by itself. Very strange
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?
Since I bought the OnePlus 5 when it launched, I have not rooted a phone since. I have since gotten rid of my windows computer and now have a Chromebook. Can anyone point me to a how to with a Chromebook if possible? All I find are articles on rooting/unlocking a Chromebook. Thanks for the help.
Sent from my ONEPLUS A5000 using Tapatalk
jbela1911 said:
Since I bought the OnePlus 5 when it launched, I have not rooted a phone since. I have since gotten rid of my windows computer and now have a Chromebook. Can anyone point me to a how to with a Chromebook if possible? All I find are articles on rooting/unlocking a Chromebook. Thanks for the help.
Click to expand...
Click to collapse
I plan on doing this too, you have to put your Chromebook in developer mode and then you can use ADB and Fastboot, they are built in. The only possible snag I was reading about is that you might have to use a script to update ADB and Fastboot for them to work properly. Then you can use Fastboot to unlock the bootloader and boot or flash TWRP. I'm hoping it will work, I have done it before. Once your Chromebook is in developer mode(not the developer channel), you can open up the terminal and type 'shell', and you will have ADB and Fastboot there.
It is indeed possible. I have a Chromebook Pro and had to do this for my Mate 10 which was a *****. Let me find the thread, it essentially has a script that allows certain apps to run in system mode, that way you don't have to keep using +r etc etc. i'll find it.
And yes, it has to be in Developer mode and it's different depending on which Chromebook you have
EditL https://www.xda-developers.com/adb-fastboot-chromebook-chrome-os/
YrrchSebor said:
I plan on doing this too, you have to put your Chromebook in developer mode and then you can use ADB and Fastboot, they are built in. The only possible snag I was reading about is that you might have to use a script to update ADB and Fastboot for them to work properly. Then you can use Fastboot to unlock the bootloader and boot or flash TWRP. I'm hoping it will work, I have done it before. Once your Chromebook is in developer mode(not the developer channel), you can open up the terminal and type 'shell', and you will have ADB and Fastboot there.
Click to expand...
Click to collapse
sledgie said:
It is indeed possible. I have a Chromebook Pro and had to do this for my Mate 10 which was a *****. Let me find the thread, it essentially has a script that allows certain apps to run in system mode, that way you don't have to keep using +r etc etc. i'll find it.
And yes, it has to be in Developer mode and it's different depending on which Chromebook you have
EditL https://www.xda-developers.com/adb-fastboot-chromebook-chrome-os/
Click to expand...
Click to collapse
Ah thanks, I came across that thread when I was researching it too. I've never rooted a Huawei phone before, but I believe the OnePlus should be pretty easy, it just needs a couple of basic fastboot commands so I'm hoping it's just a matter of getting fastboot to recognize the device and run the commands.
jbela1911 said:
Since I bought the OnePlus 5 when it launched, I have not rooted a phone since. I have since gotten rid of my windows computer and now have a Chromebook. Can anyone point me to a how to with a Chromebook if possible? All I find are articles on rooting/unlocking a Chromebook. Thanks for the help.
Click to expand...
Click to collapse
So I was able to unlock the bootloader with my Chromebook. I had to put it into developer mode, and then I ran a quick script that I found on a guide here: https://www.howtogeek.com/358285/how-to-use-adb-and-fastboot-on-a-chromebook/amp/
Then once I booted my Oneplus 6T into fastboot mode, fastboot recognized the device and unlocked the bootloader.
Another update: everything works fine, ADB and fastboot. The 6T does not have an official TWRP Recovery yet, but the unofficial one works okay, and you can just boot it rather than installing it, and then sideload Magisk to root that way. All up and routed here with Chromebook only.
YrrchSebor said:
So I was able to unlock the bootloader with my Chromebook. I had to put it into developer mode, and then I ran a quick script that I found on a guide here: https://www.howtogeek.com/358285/how-to-use-adb-and-fastboot-on-a-chromebook/amp/
Then once I booted my Oneplus 6T into fastboot mode, fastboot recognized the device and unlocked the bootloader.
Click to expand...
Click to collapse
I cannot for the life of me get this to work on my Chromebook plus. The scripts down work. I unrooted my phone to test some things, then my computer died. I desperately want to root again without waiting for my laptop to get fixed.
Ryano89 said:
I cannot for the life of me get this to work on my Chromebook plus. The scripts down work. I unrooted my phone to test some things, then my computer died. I desperately want to root again without waiting for my laptop to get fixed.
Click to expand...
Click to collapse
Which Chromebook plus do you have? I just remembered that, according to the guide, the scripts to fix ADB and fastboot work on intel-based Chromebooks.
YrrchSebor said:
Which Chromebook plus do you have? I just remembered that, according to the guide, the scripts to fix ADB and fastboot work on intel-based Chromebooks.
Click to expand...
Click to collapse
I believe that mine is the lesser hexacore version.
Ryano89 said:
I believe that mine is the lesser hexacore version.
Click to expand...
Click to collapse
that must be the exynos processor so I'm not sure what the fix is if there is one. Just brainstorming here but could you install ADB and fastboot on the Linux terminal if your Chromebook has Linux app functionality already?