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.
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.
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.
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
After reading for hours, I was successful to find an OTG micro-USB adapter with male USB-A end which allowed a Logitech dongle to be inserted and the mouse allowed me to start afresh from a factory reset. The touch screen didn't work.
There was an OTA update and I got all excited thinking, "This will be the update that fixes the touch (or lack thereof) issue."
Sadly, after the message said this was the final update, the touch screen still didn't work.
I was successfully able to enable USB Debugging because of the OTG Mouse.
When I connect to the PC and run an ADB command (e.g. adb devices), a message pops up asking to verify I trust the RSA Fingerprint for that computer and to remember that device.
Now my huge predicament: there is no way for me to touch the checkbox and choose OK.
Once I unplug in the cable to connect the OTG Mouse, the dialog box disappears.
I read about TeamViewer on the PC and TeamViewer Host from the Play Store. I installed both and was able to see the Essential Phone on the computer but whenever I touched the screen of the computer (or used the trackpad), nothing happened on the phone.
I tried pressing spacebar thinking that might enable the checkbox but no remote response on the phone.
I'm so close...all I need is one checkbox and one ok and it'll remember the USB Debugging settings.
From there I can then figure how to either downgrade from Android 10 or hopefully some kind soul can let me know what file to install so I can get this stupid touch screen to work.
I explained in a lot of detail as I wanted you folks to know I've tried many options to troubleshoot this problem before asking for help.
If there's a non-USB Debugging checkbox checked way in Fastboot Mode (e.g. ADB Sideload in Recovery), I'm willing to try that.
Thanks.
Update 2020-07-07: I had an idea to connect a SteelSeries Stratus XL wireless gaming controller to the phone via bluetooth and was successfully able to use the controls of the controller to enable the checkbox and remember the RSA Fingerprint for USB Debugging. Whooo-hoo! Now for the rest of the matter...getting this darn touch screen working with an device image that solves the problem....
I had the same problem after flashing the newest (and final) Image on top of a rooted, very old marshmallow build.
I found a fix on reddit however, and hopefully it works for you too.
I tried the second method described there:
1. Connect to fastboot to unlock bootloader and critical
Code:
fastboot flashing unlock
(didn't do anything for me since I was already unlocked)
Code:
fastboot flashing unlock_critical
Let the phone wipe itself and reboot, then go into fastboot again
2. Then flash the image of September 2018 (PH1-Images-PPR1.180905.036) via the "flashall.bat". After a reboot my touchscreen worked again.
3. Upgrade to the newest image or whichever one you like.
I don't understand the whole problem exactly, so maybe you could try flashing the newest image directly after the unlock_critical step, but I just followed the instructions I found.
Good luck!
Thanks for the suggestion and the link for the file.
When I try and run the command
Code:
fastboot flashing unlock
in fastboot mode, I keep getting the message "Waiting for device".
Same thing, when I try and run the flashall.bat file.
I booted in to FastBoot mode, but when I type adb devices in an admin command prompt, it doesn't show any devices listed, even though adb devices does show the phone listed when the phone has booted up normally.
I have:
uninstalled the Essential Phone driver and reinstalled it (multiple times).
installed the 15 Seconds ADB installer and uninstalled it (multiple times).
rebooted the Windows 10 computer multiple times.
IconBoy said:
Thanks for the suggestion and the link for the file.
When I try and run the command
Code:
fastboot flashing unlock
in fastboot mode, I keep getting the message "Waiting for device".
Same thing, when I try and run the flashall.bat file.
I booted in to FastBoot mode, but when I type adb devices in an admin command prompt, it doesn't show any devices listed, even though adb devices does show the phone listed when the phone has booted up normally.
I have:
uninstalled the Essential Phone driver and reinstalled it (multiple times).
installed the 15 Seconds ADB installer and uninstalled it (multiple times).
rebooted the Windows 10 computer multiple times.
Click to expand...
Click to collapse
Make sure to use a proper cable and not the one that comes with the phone for charging.
I use the one from my Nexus 6p. The cable from Essential is only for charging, not data transfer.
I'm using a USB-A TO USB-C cable which shows device in normal boot mode.
I have tried three different cables which all work when using adb devices in normal boot mode.
Still no phone when List of devices attached is shown.
Just for clarity: adb and fastboot are completely different modes. To test if you successfully booted into fastboot and have a working connection, you have to type "fastboot devices". "adb devices" doesn't work here.
But the unlock command should have worked anyway. How did you boot into fastmode? Can you see this fastboot screen?
If not, the easiest way to get to fastboot is to connect the turned off phone to the PC while keeping the volume down button pressed, until you see the screen linked above.
But if you do see the fastboot screen, and still don't get anything from "fastboot devices", I'd try Google's official adb/fastboot tools.
xxera said:
...you have to type "fastboot devices".
Click to expand...
Click to collapse
Yes! I can see the device listed now! I had no idea that you had to type that command! Wow....years later of working with phones and I am still learning. :good: I guess I didn't progress because I mistakenly thought the device was not being found.
I ran both commands fastboot flashing unlock and fastboot flashing unlock_critical successfully.
Once the phone wiped itself and booted up (without progressing from the startup screen prompts), I shut it down then went back in to fastboot mode and successfully ran the flashall.bat command.
I shut it down and restarted it. Touchscreen is still not working. :crying:
When I finally get this working...would I just run the commands fastboot flashing lock and fastboot flashing lock_critical to relock the phone...? I need Google Pay and other banking apps to work so want the phone to be secure.
There is always more to learn
Shame that it didn't work, though :/ Did you flash the image from September 2018 that I linked, or the newest build? If you directly flashed the newest one, maybe try the 2018 build, since that worked for me. Alternatively, from the same reddit post I linked before, someone got it working by flashing the August 2018 build, and sideloading the September 2018 OTA Update after. But I never did this sideloading thing, so can't help much there. All builds and OTAs are available on this neat website by the way.
Regarding relocking, it is generally advised to only relock if you have a good reason to do it. You can only relock a completely unmodified stock image, otherwise your phone won't boot, so no root, magisk or anything.
My banking apps still work on my unlocked and rooted phone, but I'm using a Pixel 3, and not sure about Google Pay.
But yes, if you want to relock, make absolutely sure you're stock, and use the commands you mentioned. Just be aware that this also wipes the phone again.
xxera said:
Shame that it didn't work, though :/ Did you flash the image from September 2018 that I linked
Click to expand...
Click to collapse
Yes, I used the link you gave me for the Sep 2018 build.
I will try the Aug 2018 build and see if I get any joy with that.
Thank you so much for your patience and help!
Just to be clear, you should sideload the September OTA after that, the August build itself won't do much as far as I understood.
Glad to help, I just had the same hunt for clues behind me, I know how frustrating it can be
I tried the Aug 2018 build then sideload flashing the Sep 2018 build. No joy...touchscreen still not working.
The whole fastboot flashing worked except for this one error:
fastboot format userdata
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
This message came up once the flash was complete and the phone rebooted itself):
Android Recovery
essential/mata/mata
9/PPR1.180610.091/249
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
--------------------------------------------------
Try again
Factory data reset
--------------------------------------------------
There was no choice to Apply update from ADB so I can sideload the Sep 2018 update so I went ahead and chose Factory data reset.
Once it factory reset, I was able to go in to recovery and sideload the Sep 2018 update.
Have I missed anything in this procedure...?
I also tried fastboot flashing the Apr 2019 build but that hasn't helped either.
(Attached is a screenshot of the two files I downloaded. The links are the purple ones I chose). Did I get the correct ones?
The files look right to me.
After some research I found that updating the adb tools worked for some people with that error. The creator of the 15 Seconds ADB installer even edited the post and said the tool is outdated by now. There's a newer version in this post, and maybe you are already using that, but I'd strongly recommend the official ADB from google, since I never had a problem with that one.
Also, I read that you should use a USB-3 cable. The official one from essential itself is USB-2 which can cause some problems in flashing sometimes (which is pretty stupid tbh).
Yes, after you updated ADB/fastboot, I'd just try the Aug image + Sept OTA again. Or directly the Sept image.
Not sure about the factory reset message, I'd say yes again just in case.
Edit: Ah, since it says "can't load android system", I guess the flashing failed.
I managed to fix phones with flashing a second time exactly the same way many times, sometimes fastboot is just moody. But may updating ADB can help here.
I updated fastboot and adb from the Google site.
Reflashed Aug and Sep 2018 files.
No joy. Touchscreen still doesn't respond.
An idea...I tried to install TWRP to see if the touchscreen is actually working but get the error fastboot: error: Couldn't parse partition size '0x' when running the command to install the TWRP Mata recovery image file.
Any way to check if the screen/digitizer is not a hardware fault?
Weird error... Can you post the whole log? If the partition size was read as 0, something went wrong with identifying the partition (if I interpret the error message correctly). Did you correctly flash to boot_a/boot_b depending on which one is active?
But TWRP might not help diagnosing the issue, I think touch stopped working in TWRP for essential phone a while ago, because it is also very outdated...
But to me it sounds like the usual problem after updating that many people had. The screen stopped working after an update, right?
Also, did you make sure to use the new platform-tools fastboot? Google's version doesn't automatically install itself system-wide, so if you just type "fastboot" in the command line, that might still be the old "15 Seconds ABD installer" fastboot. You can type "adb --version"to find out, it tells you in which folder the adb.exe file is.