Related
Hello,
I have a Nexus 6P stuck during boot on the white google logo. Apparently it happened during an update to N.
I have attempted a few solutions I have found either on xda or on other pages but the gist of what I’ve attempted so far is thus:
I have tried to reflash android stock after obtaining it from google : https://developers.google.com/android/images (MTC19T) but the oem option was unchecked so “fastboot flashing unlock” returns with an error.
I have tried to apply an OTA update, again I obtained the file from google (MTC19T) , via the recovery > apply update from adb . But it fails. The error from the phone is:
Code:
E: failed to verify whole file signature
E: signature verification failed
And on the pc side I believe that the failure comes from the fact that my pc has never been connected to the phone via ADB, so it’s unrecognized.
- I have also tried to bypass the adb pc signature issue by connecting a usb flashdrive to my phone via a usb-c adapter but the mount /sdcard command doesn’t work.
I’ve tried a few more esoteric solutions, like booting into Emergency Download (EDL) but my phone just boots into the google logo and stays there.
A few informations on my device (according to the fastboot/recovery screen)
Code:
BL: angler-03.51
Baseband: angler-03.61
Product/Variant: ANGLER-ROW-WN1
6.0.1/MTC19T/2741993
Current Build Number: MTC19T
So, to summarize: Fastboot is locked and won’t work, ADB is unrecognized and using a usb drive pretending to be an sdcard doesn’t work and I’m working with a stock recovery.
I'm looking for a way to bypass the fastbook lock or the adb verification. Or (even better) for anyone here to tell me that I've been going the wrong way all this time and that the solutions involves three easy steps...
Thank you!
Hipstronaute said:
Hello, I have a Nexus 6P stuck during boot on the white google logo. Apparently it happened during an update to N.....I'm looking for a way to bypass the fastbook lock or the adb verification. Or (even better) for anyone here to tell me that I've been going the wrong way all this time and that the solutions involves three easy steps...
Click to expand...
Click to collapse
Try again but you have to use an OTA that is newer than MTC19T. You still may be able to sideload when recovery is in ADB Sideload mode. There is no way to unlock your bootloader. Make sure you are using a recent, known working copy of ADB/Fastboot. The problem many people can't overcome is that they never set up ADB before or used it on a few occasions, so now the phone is dead they can't get it set up correctly. When the phone is connected in recovery>>ADB sideload update, what returns when you run "adb devices"? Do you have another phone you can use to confirm your ADB/fastboot setup is installed correctly?
Download the Nexus toolkit and then boot into recovery and select on the toolkit "softbrick" , good luck. Private message if you need any help
Sent from my Nexus 6P using Tapatalk
Hi,
Thank you for your answers.
@v12xke For the OTA after trying MTC19T I downloaded and tried half a dozen images from Google. Previous versions, next version of marshmallow, a few of the nougat versions. The results were exactly the same.
As for adb I just updated my Android studio, and it's not the first time I've used these tools. The process of sideloading the zip always stops at 47% but I can see that adb and the recovery are communicating.
Fastboot devices also detects my device, but I don't have my computer on me right now.
@DavidSantos I already tried the toolkit but it just launched my phone on the Google logo and got stuck there.
Hipstronaute said:
Hi,
Thank you for your answers.
@v12xke For the OTA after trying MTC19T I downloaded and tried half a dozen images from Google. Previous versions, next version of marshmallow, a few of the nougat versions. The results were exactly the same.
As for adb I just updated my Android studio, and it's not the first time I've used these tools. The process of sideloading the zip always stops at 47% but I can see that adb and the recovery are communicating.
Fastboot devices also detects my device, but I don't have my computer on me right now.
@DavidSantos I already tried the toolkit but it just launched my phone on the Google logo and got stuck there.
Click to expand...
Click to collapse
You have turn off your phone , press volume up and power key , then a menu will pop up , then plug in your phone with your PC
Sent from my Nexus 6P using Tapatalk
DavidSantos said:
Download the Nexus toolkit and then boot into recovery and select on the toolkit "softbrick" , good luck. Private message if you need any help
Click to expand...
Click to collapse
Best way to brick your phone if you don't know what kind of softbrick this tool has been made for... :good:
You have turn off your phone , press volume up and power key
Click to expand...
Click to collapse
Yes, I did that. The soft just makes my nexus reboot to the Google logo.
@v12xke: Looks like there are also more and more of those bootloader + recovery access bootloop. With sideload OTA fails...
@Hipstronaute: I have already seen one or two users with the same kind of problem and if I remember, nothing fixed the problem.
Good luck...
Might be a special edition Nexus 6P , oh well. Mine had the same problem and it worked just fine
Sent from my Nexus 6P using Tapatalk
5.1 said:
@v12xke: Looks like there are also more and more of those bootloader + recovery access bootloop. With sideload OTA fails...
@Hipstronaute: I have already seen one or two users with the same kind of problem and if I remember, nothing fixed the problem.
Good luck...
Click to expand...
Click to collapse
That's too bad. Sounds like the storage memory going bad and the write process is interrupted when it hits that area. Thing is, I've heard the same OTA write failure occurring several times at 47%. Wonder what that means? Anyway sounds like @Hipstronaute is looking at a replacement phone, under warranty or otherwise.
@v12xke
Anyway sounds like @Hipstronaute is looking at a replacement phone, under warranty or otherwise.
Click to expand...
Click to collapse
Gosh do I hope that won't be the last post on this topic.
So for reference I own a 2015 shield TV 16gb model. I've debated rooting and such but never followed thru with any of it. It was running 5.0 stock and kept prompting me for the 5.1 update which could (?) be the culprit. Anyway got home from work yesterday and it wasnt booting. I tried booting into recovery and clearing the cache, nothing. Then tried a factory reset, nothing. So I found the Recovery image for it and proceeded to flash it. After flashing the staging blob (Which is successful) It gets hung up when I try to flash the boot.img. I've tried re-downloading as well as trying the 5.1 image and nothing has worked. Has anyone else experienced this?
bsutton said:
So for reference I own a 2015 shield TV 16gb model. I've debated rooting and such but never followed thru with any of it. It was running 5.0 stock and kept prompting me for the 5.1 update which could (?) be the culprit. Anyway got home from work yesterday and it wasnt booting. I tried booting into recovery and clearing the cache, nothing. Then tried a factory reset, nothing. So I found the Recovery image for it and proceeded to flash it. After flashing the staging blob (Which is successful) It gets hung up when I try to flash the boot.img. I've tried re-downloading as well as trying the 5.1 image and nothing has worked. Has anyone else experienced this?
Click to expand...
Click to collapse
What do you mean with "hung up" ?
And are you certain you have the correct image downloaded?
(And did you make sure that you didn't just execute the flashall.bat? Because that's not the best way to flash the firmware, they should have left that one out....)
So are you able to boot into fastboot/bootloader mode in a stable way or does it reboot few seconds after booted up in that mode?.
First try with other USB cables (this is a well known issue, the Shield TV is picky), use the rear usb ports or your PC (the ones that are soldered to the motherboard) and avoid using usb 3.0+ ports.
If using a 4k or UHD TV, try with an up to Full HD TV or Monitor.
Do not mess with the bootloader (blob file), there was no need for you to flash that. Only corrupted bootloader flashing will hard brick your device, so be careful with it.
While you be able to boot into fastboot mode you can fix/recover your device.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
USB cable or USB port?
I had a similar thing happen with my SATV 2015 16GB model. Turns out it ended up being the USB3.0 ports on my Dell 5510 giving me grief. Each time I tried to adb the image files it was failing at different times. I made sure and got a good USB cable and used another PC with USB2 and it flawlessly put stock back on the shield. If you can fashboot, you can bring it back.
Well, I bricked my Ticwatch E about 15 minutes after getting TWRP loaded. I used the TWRP posted here and it worked as well as expected. I had previously made my own build but was having issues booting into recovery and recovery-from-boot.p was overwriting my version. After finding that relocking and unlocking forced it into recovery I thought I was set. I flashed my version over the posted version from the bootloader and rebooted. I must have messed something up in my version, I suspect the ramdisk was missing something, and it tries to boot to recovery and fails. Instead of trying to boot back into the system it is stuck trying to boot into a broken recovery. The power button is non-responsive as far as I can tell and nothing seems to interrupt the process.
Someone suggest Smart Phone Flash Tool, so I downloaded it. After installing the VCOM drivers I do get a response from USB. It's only about a second but I do see the VCOM Preloader device show up in device manager. There is a stock recovery image in the working TWRP thread. I've never used SPFT but I gather I need a scatter file to tell it where the partitions are. If anyone has one or could make one and kindly share it, I would be very grateful. I'm not 100% it'll work but it seems like my only option at this point. Or if anyone has any other ideas, I'm open to suggestion. I have another watch on it's way but would love to get this one recovered.
BackCheck said:
Well, I bricked my Ticwatch E about 15 minutes after getting TWRP loaded. I used the TWRP posted here and it worked as well as expected. I had previously made my own build but was having issues booting into recovery and recovery-from-boot.p was overwriting my version. After finding that relocking and unlocking forced it into recovery I thought I was set. I flashed my version over the posted version from the bootloader and rebooted. I must have messed something up in my version, I suspect the ramdisk was missing something, and it tries to boot to recovery and fails. Instead of trying to boot back into the system it is stuck trying to boot into a broken recovery. The power button is non-responsive as far as I can tell and nothing seems to interrupt the process.
Someone suggest Smart Phone Flash Tool, so I downloaded it. After installing the VCOM drivers I do get a response from USB. It's only about a second but I do see the VCOM Preloader device show up in device manager. There is a stock recovery image in the working TWRP thread. I've never used SPFT but I gather I need a scatter file to tell it where the partitions are. If anyone has one or could make one and kindly share it, I would be very grateful. I'm not 100% it'll work but it seems like my only option at this point. Or if anyone has any other ideas, I'm open to suggestion. I have another watch on it's way but would love to get this one recovered.
Click to expand...
Click to collapse
Did you ever find a solution to this? I am stuck in a bootloop at the ticwatch screen where the power button is unresponsive as well.
joelt2855 said:
Did you ever find a solution to this? I am stuck in a bootloop at the ticwatch screen where the power button is unresponsive as well.
Click to expand...
Click to collapse
No, I only made it worse and hosed the bootloader completely.
Hello all. I have owned my shield for 2 years now and for the first time attempted to root it. I made it to the twrp image and instead of loading the needed option to root it stayed on the nvidia image. I am guessing the twrp is old and there for not 8.0 twrp. At anyrate now ehen I turn on my shield it says I need to relock the boot loader and that I am not protected. My question is how do I fix this or do I need to ? Does anyone know where to find the current twrp and do I need to relock the bootloader and start over or can I finish from here ? Will I screw anything up keeping it unlocked ?
First of all, what experience version are you on?
And the warning that comes up when you turn on your shield is just a warning, because you have unlocked the bootloader.
You don't need to worry about it.
If you root, you wanna leave the bootloader unlocked.
mLgz0rn said:
First of all, what experience version are you on?
And the warning that comes up when you turn on your shield is just a warning, because you have unlocked the bootloader.
You don't need to worry about it.
If you root, you wanna leave the bootloader unlocked.
Click to expand...
Click to collapse
Thank you for responding ....
I am on 8.0 oreo
elderbrain said:
Thank you for responding ....
I am on 8.0 oreo
Click to expand...
Click to collapse
For Oreo there is only an experimental twrp, but you don't really need twrp to root.
You can use this guide for Nvidia Experience 7.2.3, which is Android 8.0 Oreo.
https://forum.xda-developers.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254
So to be sure, you are on Android 8.0 Oreo (Nvidia Experience 7.2.3) Correct?
And not Android 9.0 Pie (Nvidia Experience 8.0)
correct. I have a nvidia shield running 8.0 oreo. do I start from where I left off or from the start ? At this point no command workd for me and the shield is not detected. I have a brand new usb cord plugged in and all things enabled.....power shell says the commands i cut and pasted from your link are not correct commands and the minimal and fast boot says I have no device detected.....so at this point non of this matters untill I can fix this. whats the best command prompt to get this going ?
elderbrain said:
correct. I have a nvidia shield running 8.0 oreo. do I start from where I left off or from the start ? At this point no command workd for me and the shield is not detected. I have a brand new usb cord plugged in and all things enabled.....power shell says the commands i cut and pasted from your link are not correct commands and the minimal and fast boot says I have no device detected.....so at this point non of this matters untill I can fix this. whats the best command prompt to get this going ?
Click to expand...
Click to collapse
I'm using minimal adb and fastboot https://forum.xda-developers.com/showthread.php?t=2317790
Use the shortcut it makes when installed to open a command prompt.
What version of the shield do you have?
And are you booted into the bootloader?
I have the 16 gb running 8.0 oreo. I have unlocked the bootloader yes. I did every step up to loading the twrp. I used a you tube video by TT Technology. Made it to the last and final step. As of now my shield keeps disconnecting and reconnecting when connected to through usb so it does not detect any devices. I get lucky for a moment but it then stops recognizing the shield. Whats odd is that the shield is listed and I can open it and access all the storage including the mounted through the computer even when the connection drops. Right now untill i fix this issue everything else is moot.
I didn't ask if you unlocked the bootloader.
I'm asking if you are able to get into it where you do the fastboot commands?
Ah sorry. No, no commands work and I am not able to load the bootloader. It says deamon failed to start and it does not see the shield as a connected device.
elderbrain said:
Ah sorry. No, no commands work and I am not able to load the bootloader. It says deamon failed to start and it does not see the shield as a connected device.
Click to expand...
Click to collapse
If you own a SHIELD Controller
Unplug SHIELD TV.
Connect SHIELD controller to SHIELD TV with a USB cable (use port closest to HDMI).
While holding the A and B buttons at the same time, connect power to SHIELD TV.
If you do not own a SHIELD controller
Unplug SHIELD TV.
Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV.
Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Click to expand...
Click to collapse
This will get you into the bootloader, and you should be able to use fastboot commands
I tried both keyboard and controller and this is not do anything. When I fire up the command prompt two things happen I get this message:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
adb server version (40) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found.
Or it finds the shield and says its offline. My usb connection has been fixed. I was able to run a game through game stream to my pc and even watched a movie with my computers dvd player on my tv using wiredxd. So I know i have a solid connection. I am clearly doing something wrong here as I clearly am connected to the pc now.
elderbrain said:
I tried both keyboard and controller and this is not do anything. When I fire up the command prompt two things happen I get this message:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
adb server version (40) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found.
Or it finds the shield and says its offline. My usb connection has been fixed. I was able to run a game through game stream to my pc and even watched a movie with my computers dvd player on my tv using wiredxd. So I know i have a solid connection. I am clearly doing something wrong here as I clearly am connected to the pc now.
Click to expand...
Click to collapse
Oh my bad, I didn't think you were able to boot.
Have you enabled usb debugging on the shield in the developer options?
Anyways, that error is usually because of using an out of date adb.
try this minimal adb and fastboot
https://www.androidfilehost.com/?fid=745425885120698566
Yes. I have made sure all 3 possible options where enabled, from developer options to usb debugging. I even got the message to allow it always on this device. I have full access to the shield through usb and it appears in my DM.........I have tried all three versions I can find for minimal fastboot. v 14.1......1.4.3 and the one you said to try 1.4.2. All have the same message. It just either does not detect a device or it says its offline. I have pretty much thrown in the towel at this point as all options have been attempted and hours of googling where wasted. I really have no idea where to go now. I tried resetting the shield a few times.....then tried revoking usb and re enabling and nothing will get it to connect to the deamon. Thank you for all the help. I appreciate you trying
In what state is your shield currently ? From what I read in your posts , your shield doesn't currently boot ? You said it's stuck at the nvidia logo. I am no expert, but if you really are stucked at the nvidia logo, until you enter fastboot mode properly, ADB won't be of any help. If that's the case , then follow any of the methods in post #10 of this thread to properly enter fastboot mode. From there you'll be able to fix things. Since it was you that unlocked the bootloader then it means that the cable, the drivers and your installation of ADB were all in working order at that moment. Now has to why you are stucked on the nvidia logo , you didn't mention which step of which guide you were following when that happened , but at the very least your recovery.img or boot.img have issues. If it's the recovery (twrp) then you're using a wrong one. I don't think a bad recovery.img will let you get as far as the nvidia logo so I doubt that's the issue here. Your boot.img seems corrupted and cannot proceed past the nvidia logo, so perhaps you tried a pre-patched boot.img that isn't the correct one for your current system version or you patched it yourself with a magisk manager that doesn't properly patch the boot.img . I would suggest that next time you type "fastboot boot boot.img" (boot instead of flash) so that you at least try the boot image before you go on and flash an untested file (not a blame, if its the case then you followed a guide that didn't mention this precaution first). Anyways , if you're stuck at the nvidia logo , then what you should do first is try to flash a clean boot.img . Go to nvidia's site and grab the proper recovery for your system version (7.2.3 you said) by scrolling down to Recovery Images , and first choosing your correct hardware and next the image you need. Extract these files in the same folder as your ADB installation so that you can just click "flash-all.bat" and it will fix your shield (it will flash the correct recovery.img and boot.img). Of course this has to be done while you are in fastboot mode , so it comes back to this, get your device into fastboot mode properly. Any USB keyboard you have around the house should work to do this :
Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV. --- I add this : Hold the keys until something happens. Release them only once you reach fastboot mode or the nivida logo and try it with every usb port before ruling it doesn't work.
Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Oh, if you get into fastboot mode and the commands still give you errors about client versions not matching, that might be an issue with other software running on your pc, but we'll stay out of this for now.
Roamin64 said:
In what state is your shield currently ? From what I read in your posts , your shield doesn't currently boot ? You said it's stuck at the nvidia logo. I am no expert, but if you really are stucked at the nvidia logo, until you enter fastboot mode properly, ADB won't be of any help. If that's the case , then follow any of the methods in post #10 of this thread to properly enter fastboot mode. From there you'll be able to fix things. Since it was you that unlocked the bootloader then it means that the cable, the drivers and your installation of ADB were all in working order at that moment. Now has to why you are stucked on the nvidia logo , you didn't mention which step of which guide you were following when that happened , but at the very least your recovery.img or boot.img have issues. If it's the recovery (twrp) then you're using a wrong one. I don't think a bad recovery.img will let you get as far as the nvidia logo so I doubt that's the issue here. Your boot.img seems corrupted and cannot proceed past the nvidia logo, so perhaps you tried a pre-patched boot.img that isn't the correct one for your current system version or you patched it yourself with a magisk manager that doesn't properly patch the boot.img . I would suggest that next time you type "fastboot boot boot.img" (boot instead of flash) so that you at least try the boot image before you go on and flash an untested file (not a blame, if its the case then you followed a guide that didn't mention this precaution first). Anyways , if you're stuck at the nvidia logo , then what you should do first is try to flash a clean boot.img . Go to nvidia's site and grab the proper recovery for your system version (7.2.3 you said) by scrolling down to Recovery Images , and first choosing your correct hardware and next the image you need. Extract these files in the same folder as your ADB installation so that you can just click "flash-all.bat" and it will fix your shield (it will flash the correct recovery.img and boot.img). Of course this has to be done while you are in fastboot mode , so it comes back to this, get your device into fastboot mode properly. Any USB keyboard you have around the house should work to do this :
Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV. --- I add this : Hold the keys until something happens. Release them only once you reach fastboot mode or the nivida logo and try it with every usb port before ruling it doesn't work.
Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Oh, if you get into fastboot mode and the commands still give you errors about client versions not matching, that might be an issue with other software running on your pc, but we'll stay out of this for now.
Click to expand...
Click to collapse
I have all but gave uop at this point, but to answer your question. My shield works and runs it is just in the state where the bootloader is unlocked and I get the warning. I have attempted the instructions before, holding down the a and b keys on both the game controller and a wired keyboard and it does nothing. I agree that the twrp is not current and that I need the proper files. As of now my shield is just not recognized period. That is why holding down the aand b keys does not work ( IE it in the command prompt it says shield is offline or it sees it and when I enter fastboot it just says waiting for device and does nothing more. So half way through it looses connection to the shield ) Untill I can get the shield to be recognized none of these instructions matter. As of now I have decided to give up and maybe in a while try again. I would like to completely restore my shield to the state it was in so I can start from scratch. That is what I am focusing on now, but untill my shield is recognized I dont think even that is possible. Thanks for your post. I appreciate all the help all of you have offered.
Impossible d'accéder au recovery
Bonjour j'ai fait une erreur de flashing, le fimware de NVIDIA Shield TV n'était pas bon, donc le logo NVIDIA reste bloqué, j'ai essayé de faire a et b mais impossible d'accéder au booloader et au recovery comme faire ?
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.