Ok, I'm planning on rooting, but seeing the same error from both methods:
https://forum.xda-developers.com/on...t-oneplus-6t-using-oneplus-6t-rooter-t3864238
and
https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3860279
I really don't want to run into the issue of the device not booting, or heat problems etc. So could anyone provide their experiences or opinion on which one works best? I have the regular OP6t, not T-Mobile, live in America.
I used the one click tool.. No heating probs, sot of 10 hours, boots allways, no bootloops, stable root.. Perfect.
Only problems with recovery. Flashed recovery, but somehownit wont stick. Have to flash recovery every time i want to use it. But i guess there is no need for twrp at the moment, so im satisfied with only root and the mods available.
They basically all just do the same thing.
I used fastboot manual commands, takes 5 minutes and at least you know what you're doing.
And your thread is not in the proper section, it should be in Q&A one, ask a Mod to move it
When I tried with command prompt, it said "waiting on devices". My apologies, as it's been about 4 years since I've done this with my Nexus 6
First, you disconnect the device and In command pront write the command + enter, after, when you see "waiting on devices" you have to connect the device and it flash your phone.
I did it like that.
phr0zen said:
When I tried with command prompt, it said "waiting on devices". My apologies, as it's been about 4 years since I've done this with my Nexus 6
Click to expand...
Click to collapse
Enviado desde mi ONEPLUS A6013 mediante Tapatalk
Yup, even tried the one-click method, and it hands on "waiting for device". Followed the directions just as they were innthe link and in the readme file. Phone boots into recovery and does nothing. Computer hangs at the command prompt telling me it's waiting. Installed the rooter setup, and when I open that, it says the phone isn't connected.
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
< waiting for device >
*DISREGARD THIS* did not have usb debugging checked after the reboot... the previous still hold true though
phr0zen said:
Yup, even tried the one-click method, and it hands on "waiting for device". Followed the directions just as they were innthe link and in the readme file. Phone boots into recovery and does nothing. Computer hangs at the command prompt telling me it's waiting. Installed the rooter setup, and when I open that, it says the phone isn't connected.
Click to expand...
Click to collapse
For me, the best option is this:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789
alfo!!! said:
For me, the best option is this:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789
Click to expand...
Click to collapse
OK, tried that one as well, and it's a no-go either. I installed the OnePlus drivers, and already had ADB binaries/drivers (1.4.3) installed, but decided to run the install again to make sure they were updated.
After this, I booted into fastboot and plugged my phone in the computer. I opened a command prompt and ran "fastboot devices" which returned negative results... it did not recognize my serial number, which indicate the drivers were not installed correctly.
How can they not be installed correctly when I ran it as device administrator?
are you sure that have you doing this step?
"Show File Extensions
Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files."
If it does not work well, I would change PC
alfo!!! said:
are you sure that have you doing this step?
"Show File Extensions
Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files."
If it does not work well, I would change PC
Click to expand...
Click to collapse
Yes, I did that.
Running "fastboot" comes up with all the options, as well as running "adb". Running "fastboot devices" does not show anything though. Unfortunately this is my only computer, which is a windows surface pro. Other laptop got the cord chewed by a hungry dog
I'm open to other options, but it sounds like maybe this computer doesn't play well.
Hi, if you're still looking for solutions.. I followed the first link (one with the rooter application). Peacefully rooted my phone. Didn't check much with recovery and all, but my phone is rooted and I'm able to use root applications and mods.
phr0zen said:
Yes, I did that.
Running "fastboot" comes up with all the options, as well as running "adb". Running "fastboot devices" does not show anything though. Unfortunately this is my only computer, which is a windows surface pro. Other laptop got the cord chewed by a hungry dog
I'm open to other options, but it sounds like maybe this computer doesn't play well.
Click to expand...
Click to collapse
If "fastboot devices" doesn't show a device, your system is not recognizing the device as a fastboot device. Check device manager. You can unplug and re-plug the device with device manager open to see what device your system sees it as and "update driver" that way or simply delete device selecting "delete device software" to completely remove. Re-plug the phone and hopefully it automatically installs with the proper drivers. Otherwise you have to do the "update drive" method to manually select the fastboot driver.
As for ADB, "adb devices" should also show your device listed. Won't show unless debugging is enabled and you can't interact with it unless you authorize the system on the phone. This will happen if you simply run the "adb devices" command while phone is connected with debugging enabled. If still not showing up with debugging enabled, you may have to use same method specified for fastboot above.
I booted into twrp. Enabled adb sideload and then just sideloaded the magisk zip.
Then I booted the phone, installed magisk manager and I was done.
Sent from my ONEPLUS A6013 using Tapatalk
hartleyshc said:
I booted into twrp. Enabled adb sideload and then just sideloaded the magisk zip.
Then I booted the phone, installed magisk manager and I was done.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
This and instead of sideload, you connect a flash drive and install the zips from TWRP.
phr0zen said:
Yup, even tried the one-click method, and it hands on "waiting for device". Followed the directions just as they were innthe link and in the readme file. Phone boots into recovery and does nothing. Computer hangs at the command prompt telling me it's waiting. Installed the rooter setup, and when I open that, it says the phone isn't connected.
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
< waiting for device >
*DISREGARD THIS* did not have usb debugging checked after the reboot... the previous still hold true though
Click to expand...
Click to collapse
is there a way to root the phone and apps like snapchat work?
Popsicle toast said:
is there a way to root the phone and apps like snapchat work?
Click to expand...
Click to collapse
Yes. Use magisk hide to hide root from the Snapchat application
Pain-N-Panic said:
Yes. Use magisk hide to hide root from the Snapchat application
Click to expand...
Click to collapse
im asking cuz i heard magisk hide dosent work on the 6t yet. im using v17.3.
Popsicle toast said:
im asking cuz i heard magisk hide dosent work on the 6t yet. im using v17.3.
Click to expand...
Click to collapse
Ah, I don't have the phone yet so I can't confirm
duvee said:
I used the one click tool.. No heating probs, sot of 10 hours, boots allways, no bootloops, stable root.. Perfect.
Only problems with recovery. Flashed recovery, but somehownit wont stick. Have to flash recovery every time i want to use it. But i guess there is no need for twrp at the moment, so im satisfied with only root and the mods available.
Click to expand...
Click to collapse
What was your screen on time before you rooted? Or did you rooted straight away?
What changes did you make after root to get 10 hours sot? Did you change the kernel?
Sorry for all the questions. I'm looking to root to get better sot but haven't done anything like this since the Nexus 5/6
Popsicle toast said:
im asking cuz i heard magisk hide dosent work on the 6t yet. im using v17.3.
Click to expand...
Click to collapse
All is working as intended, don't listen to 'people'. I have snapshat working without even using specific hiding option in magisk.
Related
Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
kjtay said:
Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
Click to expand...
Click to collapse
Under device manager, what is listed as your phone?
Ajxx16 said:
Under device manager, what is listed as your phone?
Click to expand...
Click to collapse
Unknown Device... It is worth noting that I have used Wugs Toolkit and followed every set of directions to a T. This includes a PC that that has never had my phone in it before. Followed all the steps before I even tried to connect. Also, both PC machine indicate that I have installed the most update driver.
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Ajxx16 said:
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Click to expand...
Click to collapse
I have tried all usb ports and a different usb cord. My OS is gone, so I was hoping to find some way to install a rom or stock. I am at a loss!
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Ajxx16 said:
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Click to expand...
Click to collapse
I do if I understand the term correctly. I am at the android "start" screen and underneath the android it says
Fastboot Mode
Product_Name - mako
lock state - unlocked
Now what?
Connect it to your computer, and I assume you have fastboot and adb set up correctly. In command prompt type fastboot devices and see if your phone is listed, should give the serial and say fastboot next to that
Not sure if I know how to set up adb correctly... as far as fastboot goes.. I assume that is set up correctly. Would adb work if the PC doesn't recognize my phone?
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Ajxx16 said:
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Click to expand...
Click to collapse
Don't mean to sound like an idiot (may be too late for that), but do you mean fastboot recognized on my PC when I plug in my phone? Or does is say fastboot on my phone? PC does not recognize my phone, but it does say fastboot enabled on my phone.
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Ajxx16 said:
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Click to expand...
Click to collapse
I can't get the PC to recognize the phone. The phone is in fastboot mode. It is looking mighty grim!
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Ajxx16 said:
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Click to expand...
Click to collapse
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Ajxx16 said:
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Click to expand...
Click to collapse
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
kjtay said:
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
Click to expand...
Click to collapse
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Ajxx16 said:
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Click to expand...
Click to collapse
I am pretty certain I have the proper drivers installed on 3 computers. Not a single one recognizes the device. I suppose it is possible that it is a hardware issue? If I can figure a way to the computer to recognize the phone I am certain I can save it. Right NOTHING has worked.
edit : As of today - 28th June, this method ONLY works on the H815 EU models
update 26th July : Please go check the dream team's ROOT thread located here : [ROOT] TMO/VZW/ATT/SPRINT/INTL Root your LG G4 with Low Effort Root!
Thanks @thecubed , @autoprime , @IllegalArgument & @jcase for their hard work
Hi guys, a quick step by step guide to how I was able to unlock, install TWRP and Root my H815. Please don't hold me responsible if any issues arise with your phone. If you do this, you take your own responsibilities.
I tend to download all the tools in a single folder so it is easier to manage.
The LG Site:
1. go to this LINK and register.
2. you will get a confirmation email.
3. go to this LINK to unlock your bootloader (you will find the information on how to get your IMEI and Device ID lower in the post)
Your PC :
1. Be sure to have the LG drivers (i connected my phone first, it automatically installed the drivers on the computer.
update 27th July : thanks @the_scotsman in case you have driver issues please download these provided by @autoprime : LGUnitedMobile_Win_Driver_Ver_3.14.1
2. Be sure you have installed the ADB stuff that can be found here : Minimal ADB & Fastboot & ADB Installer (type Y to all the questions asked)
Install Minimal ADB first. Then type Y to all the questions the ADB installer asks. Close both windows once done.
Download TWRP 2.8.7. for H815:
1. go to this LINK and download it. Add it to your folder
Download SuperSu 2.46:
1. Download SuperSu 2.46 HERE (thanks @Chainfire ) and add it to your folder
PC & G4 love :
Once you are sure you have completed all the above tasks start rolling :
A. Enter your IMEI on the LG page
- you can find your IMEI on the G4 by going to settings > about phone > status
B. Get your Device ID:
1. hook up your LG on your PC (be sure not to be locked on your lockscreen, That USB debugging is checked and OEM checked in the Developer Options)
2. launch your CMD and type:
Code:
adb reboot bootloader
your phone will reboot
3. type this to get your Device ID
Code:
fastboot oem device-id
4. You will see two lines of number. Copy them and paste them together (to make one line) in the the Device ID fields on the LG site.
5 type :
Code:
fastboot reboot
5. close CMD
5. click Confirm on the site and you will receive by email a file called : unlock.bin.
Unlocking your bootloader:
1. once you get your LG email, save the unlock.bin in your folder
2. launch CMD from the folder (hold shift, right click the folder)
3. in CMD type :
Code:
adb reboot bootloader
4. once your phone is rebooted in bootloader type :
Code:
fastboot flash unlock unlock.bin
5. then reboot your phone by typing :
Code:
fastboot reboot
Normally your phone now has it's bootloader unlocked. When it boots you should see a message on the top left of the screen saying that.
COPY SuperSu and the downloaded TWRP file onto your phone (i put it in the download folder in the phone, not the SD) so you are ready for the next steps
Booting TWRP via ADB and bootloader mode
I personally think this was the easiest way to be able to root and clean install TWRP. Be sure your TWRP is in the folder.
1. Launch CMD from the folder (hold shift, right click the folder)
2. type (again) :
Code:
adb reboot bootloader
3. once your phone reboots and is in bootloader mode type :
Code:
fastboot boot TWRP2861.img
the new name of the file
or
Code:
fastboot boot p1.img
if you didn't rename it.
4. now you will reboot into TWRP.
Installing SuperSu
1. once you are in TWRP click install and go find your SuperSu file.
2. Swipe to install.
3. Once installation is done, reboot to system.
Once you have rebooted into the OS you will find the SuperSu app. Download the TWRP manager just to have it handy. And now i would install the TWRP file you have copied on your phone with flashify. I think it's a great tool.
2 ways to do it:
1. locate the file, click on it and choose to open with flashify then choose recovery and follow the steps
2. find the file via flashify and install.
(Don't download TWRP for H815 in the TWRP manager or Flashify as they are not fixed by @wolfgart (correct me if I am wrong))
once all this done and rebooted. Your phone will have TWRP and would be Rooted. Choose the TWRP manager to boot into recovery when you want.
I preferred to reboot the phone every time just to be sure...
If you have any comments, or i wrote something wrong, don't hesitate to correct me.
Have fun
UPDATE : Thanks to @autoprime you can also update your H815 EU to the latest Stock ROM : 10C (don't forget to thank him, as those guys are working hard to make your life easier!)
@the_scotsman, maybe you can pin this to help the lost souls until a one app does it all appears?
Well that was quick.
mediumraresteak said:
Well that was quick.
Click to expand...
Click to collapse
Looks like it depends on getting info from LG... let's see how long that lasts!
Forgive me if im mistaken but there are already like 3 threads about this i believe.
Sent from my LG-H815 using Tapatalk
I read the LG boot unlock affects streaming services. Can you tell me if it's still possible to stream music from the google play music app, and also YouTube ? Cheers.
barondebxl said:
Forgive me if im mistaken but there are already like 3 threads about this i believe.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I have seen threads discussing about it yes, but haven't seen a clear guide on "how to" do it. Please enlighten me and i will ask this thread to be deleted. I don't like multi threads on the same subject, so i would be the first to ask that this thread be deleted.
pcoulson said:
I read the LG boot unlock affects streaming services. Can you tell me if it's still possible to stream music from the google play music app, and also YouTube ? Cheers.
Click to expand...
Click to collapse
I haven't had any issues with DRM, Camera or netflix streaming
SAO said:
I have seen threads discussing about it yes, but haven't seen a clear guide on "how to" do it. Please enlighten me and i will ask this thread to be deleted. I don't like multi threads on the same subject, so i would be the first to ask that this thread be deleted.
I haven't had any issues with DRM, Camera or netflix streaming
Click to expand...
Click to collapse
Yeah there arent any other guide, just threads discussing it. It just seems a lot since the LG site is pretty clear and self explanatory.
Sent from my LG-H815 using Tapatalk
I'm stuck on "fastboot oem device-id" command in cmd. Everything up to that point goes smoothly.
command line says "waiting for device" and the phone screen doesn't show phone ID, but gives me options 1-3. 1 being to show device ID, can't remember what the other ones are now. But I can't select "1". What am I doing wrong?
I have USB debugging on, also the OEM unlock is checked in development options.
Eclap78 said:
I'm stuck on "fastboot oem device-id" command in cmd.
command line says "waiting for device" and the phone screen doesn't show phone ID, but gives me options 1-3. 1 being to show device ID, can't remember what the other ones are now. But I can't select "1". What am I doing wrong?
Click to expand...
Click to collapse
unplug your device, if you can't restart it, by keeping your finger pressed for 10 seconds on the power button, take battery out.
Once you put the battery back in, restart the phone, plug in the phone in the computer, restart the CMD, and start the procedure again. :
2. launch your CMD and type:
Code:
adb reboot bootloader
your phone will reboot
3. type this to get your Device ID
Code:
fastboot oem device-id
SAO said:
unplug your device, if you can't restart it, by keeping your finger pressed for 10 seconds on the power button, take battery out.
Once you put the battery back in, restart the phone, plug in the phone in the computer, restart the CMD, and start the procedure again. :
2. launch your CMD and type:
Code:
adb reboot bootloader
your phone will reboot
3. type this to get your Device ID
Code:
fastboot oem device-id
Click to expand...
Click to collapse
I've tried this a few times now, same outcome, same thing, don't get a code, only get the 3 options and the power off 10 second thing, which doesn't work btw, have to pull battery every time
The numbers should show on your CMD window on your computer not the phone.
If the CMD window only shows "waiting for device", did you try to shut the CMD windows?
SAO said:
The numbers should show on your CMD window on your computer not the phone.
If the CMD window only shows "waiting for device", did you try to shut the CMD windows?
Click to expand...
Click to collapse
ah, thought they were supposed to show on the phone screen.
not sure what you mean by shutting the cmd window? I just get stuck on that "waiting for device" message in cmd, at which point I unplugged the phone, did a battery pull and tried again. I've tried about 5 times now, I double checked everything, have all the drivers installed etc.
Oh, and I do have the h815 EU version of the G4. I'll keep digging.
Could someone try out netflix, camera, divx files, YouTube and all the things that people were afraid of loosing. I for myself would really like to root but I dont want to loose any functions by doing that.
Sent from my LG-H815 using Tapatalk
Pyrres said:
Could someone try out netflix, camera, divx files, YouTube and all the things that people were afraid of loosing. I for myself would really like to root but I dont want to loose any functions by doing that.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I have no issues with Netflix, divx, camera or YouTube.
Just a reminder that this does not work with all H815's as of 6/5/15. I think those of us that got a non EU region specific H815's get stuck when requesting a bootloader unlock from LG. Most of us are getting "not found suffix" when trying to submit the IMEI# and device ID. Note: trying different internet browsers does nothing, so don't bother.
We'll have to wait for LG to either approve all region G4's or another method. Cheers for making a guide though.
AhsanU said:
Just a reminder that this does not work with all H815's as of 6/5/15. I think those of us that got a non EU region specific H815's get stuck when requesting a bootloader unlock from LG. Most of us are getting "not found suffix" when trying to submit the IMEI# and device ID. Note: trying different internet browsers does nothing, so don't bother.
We'll have to wait for LG to either approve all region G4's or another method. Cheers for making a guide though.
Click to expand...
Click to collapse
Thanks for the heads up.. i have put this in red in the first post.
Eclap78 said:
I'm stuck on "fastboot oem device-id" command in cmd. Everything up to that point goes smoothly.
command line says "waiting for device" and the phone screen doesn't show phone ID, but gives me options 1-3. 1 being to show device ID, can't remember what the other ones are now. But I can't select "1". What am I doing wrong?
I have USB debugging on, also the OEM unlock is checked in development options.
Click to expand...
Click to collapse
Got the same Problem and fixed it, because, that are restriction/Firewall/Domaincontroler/Groupright Problems on ur PC.
Here the link, were i short explain my problem. http://forum.xda-developers.com/g4/general/howto-unlock-twrp-root-1-thread-t3130538
And now i see there is a HOWTO Thread
SO i have doubled it :crying:
But same answers like here "we got like 5 Threads", but like u said @SAO NOT 1Thread were all-in-one is explained! :good:
Is there a reason why we have to temporarily boot into TWRP to install root and then install TWRP via a secondary method?
Like, why can't we just do a "fastboot flash recovery twrp.img" command to install TWRP like most other devices with an unlocked bootloader?
Does this method break DRM?
takuhii said:
Does this method break DRM?
Click to expand...
Click to collapse
yes
I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.
maltydog said:
I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.
Click to expand...
Click to collapse
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did to flash the stock firmware.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.
maltydog said:
I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.
Click to expand...
Click to collapse
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.
kbonnel said:
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.
Click to expand...
Click to collapse
Thanks, I understand now. I can't start this tonight, but I will try the again next time I have time at the desktop.
You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.
damn it, I read somewhere that there are problems while using adb on the current official beta. There was a command for getting connection again. But I can't find it right now.
Just to be clear. when the phone is on, you enabled USB debugging and plugged in the USB cable and checked the tickbox before you granted debugging access, right? If you don't check the box, there is no access granted after a phone reboot.
take care, I had problems getting through the initial phone setup after I did a factory reset. The Oreo beta still has some hickups. I got it to work after a few reboots. Without finishing the intial phone setup you can't enable USB debugging, you know.
emowing said:
You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.
Click to expand...
Click to collapse
Good point on the driver, I wasn't even thinking about that.
Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?
maltydog said:
Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?
Click to expand...
Click to collapse
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes.
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks.
F
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks. Trying to reply and it doesn't appear. Edit: Sorry for the multiple posts,they all appeared at once.
Okay, I am back to this now, I had time today. I installed the windows drivers from the Essential site (I am running Windows 10 64 bit) and the device was recognized in fastboot devices. The phone wiped my data and restarted with a setup screen. So far, so good. So I shut down the phone again, turned it on again in fastboot mode, it was unlocked. I went into a CMD screen and typed fastboot devices, and the phone was still listed there. So I opened windows explorer and got to the folder where I had unpacked the image files and also copied the flashboot file. I right-clicked the flashall.bat file, chose run as administrator. When I did this, I got a bunch of error messages that went by so fast, they were practically impossible to read, though they seem to say something about files not found. I didn't see any log file in the folder, so I guess they are not created. I went back to the Essential site and downloaded the zip file with the correct image files again and tried a second time, with the same results. Anyway I have wiped my phone, but still have not reinstalled the Sprint nougat software I need on this phone. Any other suggestions?
Okay, I tried again, and I was able to read the error message. They all said cannot load "filename" no such file or directory. It sounds like some kind of path error, right? I expanded the file from the Essential download for build Build NMI81C into their own directory, a subdirectory of a library where I have been keeping various android files, and I copied the flashboot file into the same directory from the platform-tools download, but only that file. That seems to be what instructions specify.
Also, I notice on this thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page3 it mentions also using the command "fastboot flashing unlock_critical" but I do not see that elsewhere.
I was able to get flashall to run using the command prompt instead of Windows Explorer. It seemed to run okay, except a couple of items cause me some concern.
I got a message "FAILED (remote: Flashing is not allowed for Critical Partitions)" for the abl.img file.
And the other command "Did you mean to fashboot format this ext4 partition".
Are either of these a problem?
Try running the commands one at a time. Open the flash-all.sh in a text editor and copy the commands.
As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.
maltydog said:
As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.
Click to expand...
Click to collapse
Did u not do the flashing unlock_critical?
Airwolf79 said:
Did u not do the flashing unlock_critical?
Click to expand...
Click to collapse
No I didn't. It was not mentioned by anyone but me in this thread until you did.
So far I have received no error messages since I did the reversion to stock. As I said,
I did get an update almost immediately.
I've tried several times to unlock the bootloader and it will not respond to any commands once in fastboot mode. I've tried to follow this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ but whenever I type "fastboot oem unlock" it just says "waiting for any device" and nothing happens. I have usb debugging enabled and oem unlocking on so I don't know what I'm doing wrong. I have the platform tools from Google installed. I can run adb and type "adb reboot bootloader" and it responds, but after that, no fastboot commands work. I mainly just wanted to root so I could restore my apps and data via Titanium Backup. Is there a temp root solution I can use? Or has anyone else experienced this?
Let me know if you need more info. Hopefully this is an easy one.
What do you get if you run "adb devices"?
thedrizzle said:
What do you get if you run "adb devices"?
Click to expand...
Click to collapse
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
blockhead428 said:
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
Click to expand...
Click to collapse
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes ? I'm not sure if I can put a link on here
DinarQ8 said:
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I've done that also. Developer options are enabled, USB debugging, and OEM unlocking. Are there newer drivers I need? But if that was an issue, it wouldn't allow me to do "adb reboot bootloader". It'll reboot to fastboot mode, but after typing "fastboot oem unlock" it just says waiting for any device.
blockhead428 said:
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
Click to expand...
Click to collapse
In the picture it shows you typed your commands all capitals letters
Dr8ven said:
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes I'm not sure if I can put a link on here
Click to expand...
Click to collapse
Try and post it. It let me post the link to the guide in the initial posting. You could be on to something.
This is where I got my version of ADB. https://developer.android.com/studio/releases/platform-tools It's not so much an "install" as it is unpacking a zip archive.
twinnfamous said:
In the picture it shows you typed your commands all capitals letters
Click to expand...
Click to collapse
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
blockhead428 said:
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
Click to expand...
Click to collapse
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
I used the adb installer from the same video. Once you unzip it. It's an .exe file which I granted administrator rights to install... it installs adb and drivers and it worked for me
That's the video and did it to a T
Another thing don't use power shell use command
twinnfamous said:
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
Click to expand...
Click to collapse
I'm following a video now. I'm thinking I didn't have the ADB drivers installed so I'm trying that now.
Let us know how it turned out ?
Dr8ven said:
Let us know how it turned out
Click to expand...
Click to collapse
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
blockhead428 said:
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
Click to expand...
Click to collapse
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
blockhead428 said:
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
Click to expand...
Click to collapse
I was thinking that maybe the latest OTA broke the bootloader unlock process, but someone else in this thread said they just unlocked theirs. I don't understand what the issues is. I've followed this video so closely I could re-enact it in my sleep.
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Nice! For a noob I wasn't too far off lol it just had to be one of those two issues
Enjoy happy rooting ?
blockhead428 said:
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Click to expand...
Click to collapse
Hi I have the same problem, when fastboot it says waiting device. I also had rooted my other phone, so how to find my other driver phone in device manager because I can't find it
Hi all; thanks for stopping by,
I've looked through multiple seemingly related threads but have been unable to find adequate answers and I am in way over my head to begin with, so please bear with me. Recently my LG G7 ThinQ became totally unresponsive so I figured I'd just use my old Moto G4 Plus while I work on fixing the G7. Problem is, the phone is locked and I have no idea what my swipe password is and I don't want to just completely wipe the phone as there is sentimental content on the phone which I'd like to access anyway.
The G4 Plus is OEM locked but I can access the bootloader, USB debugging is enabled, and I have an SD card. It is "athene_retail," operating on Android 7.0, and I do not have TWRP or CWM or the like installed on the phone. My PC is running Windows 10. Part of my problem is I'm not entirely sure how all this is supposed to work, but after hours of disorganized research I decided this thread was my best bet: https://forum.xda-developers.com/showthread.php?t=2620456 , so I have downloaded a lot of files and whatnot but am struggling with troubleshooting myself as I am likely not using them properly anyway. I tried the simplest-looking Methods -- 1 and 5 -- without success.
The problem I seemed to run into with Method 1 is at step #4 with "Apply update from ADB" and "Apply update from SD card" in Recovery Mode. What would happen is I'd "mount" the "/system" and proceed to choose one of the aforementioned "Apply update" options and the screen would just go black and then after a few seconds it would revert to a "No command" screen. Reading more into Method 1's instructions it seems like I might have to install TWRP or CWM onto my phone in order for this to work, but if that's right, how am I supposed to get them onto the phone if not through those options?
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
hackmythinq said:
Hi all; thanks for stopping by,
I've looked through multiple seemingly related threads but have been unable to find adequate answers and I am in way over my head to begin with, so please bear with me. Recently my LG G7 ThinQ became totally unresponsive so I figured I'd just use my old Moto G4 Plus while I work on fixing the G7. Problem is, the phone is locked and I have no idea what my swipe password is and I don't want to just completely wipe the phone as there is sentimental content on the phone which I'd like to access anyway.
The G4 Plus is OEM locked but I can access the bootloader, USB debugging is enabled, and I have an SD card. It is "athene_retail," operating on Android 7.0, and I do not have TWRP or CWM or the like installed on the phone. My PC is running Windows 10. Part of my problem is I'm not entirely sure how all this is supposed to work, but after hours of disorganized research I decided this thread was my best bet: https://forum.xda-developers.com/showthread.php?t=2620456 , so I have downloaded a lot of files and whatnot but am struggling with troubleshooting myself as I am likely not using them properly anyway. I tried the simplest-looking Methods -- 1 and 5 -- without success.
The problem I seemed to run into with Method 1 is at step #4 with "Apply update from ADB" and "Apply update from SD card" in Recovery Mode. What would happen is I'd "mount" the "/system" and proceed to choose one of the aforementioned "Apply update" options and the screen would just go black and then after a few seconds it would revert to a "No command" screen. Reading more into Method 1's instructions it seems like I might have to install TWRP or CWM onto my phone in order for this to work, but if that's right, how am I supposed to get them onto the phone if not through those options?
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
Click to expand...
Click to collapse
LMSA has a pin reset, you could try that.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
hackmythinq said:
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
Click to expand...
Click to collapse
"emulator-5554" ? This is a emulator and not your Moto G4. Are you using any emulator? If so, stop it and connect your G4.Once your G4 is connected to ADB, it should show your G4's Serial Number in list of devices attached.
[email protected]!$h said:
"emulator-5554" ? This is a emulator and not your Moto G4. Are you using any emulator? If so, stop it and connect your G4.Once your G4 is connected to ADB, it should show your G4's Serial Number in list of devices attached.
Click to expand...
Click to collapse
Thanks for the reply.
That did seem odd but I'm a noob, so I do have BlueStacks installed on my laptop but I don't believe it was even running at the time. Could that be it? In which case, that means my laptop wasn't even recognizing the phone at all to begin with? Hmm, ok, well I think I found the problem: when I click "adb.exe" a black screen (possibly cmd?) flashes on-screen for a tiny fraction of a second and that's it. Should it be doing something more than that? Does it have a GUI?
hackmythinq said:
Thanks for the reply.
That did seem odd but I'm a noob, so I do have BlueStacks installed on my laptop but I don't believe it was even running at the time. Could that be it?
Click to expand...
Click to collapse
Yes, it could be bluestacks. It's adb connection runs in the background.
In which case, that means my laptop wasn't even recognizing the phone at all to begin with? Hmm, ok, well I think I found the problem: when I click "adb.exe" a black screen (possibly cmd?) flashes on-screen for a tiny fraction of a second and that's it. Should it be doing something more than that? Does it have a GUI?
Click to expand...
Click to collapse
adb doesn't have any GUI and cmd flashing for a second is general behaviour when you run adb.exe. You should always run it from command prompt like you did before.
try installing Moto drivers : https://support.motorola.com/in/en/drivers
if already installed better try different port/cable/pc