I'd installed TWRP and was playing with some ROMs/Kernels when I hit a boot loop. I then used Flashtool ("Emma") to restore to factory. I haven't been able to send Fastboot commands since. I was wondering if anyone here might be able to point me in the right direction to help me sort this out.
When I connect the phone while holding volume up I still get a blue LED, but when I try to send a fastboot command besides "help", I get "waiting for any device" on Windows. On Mac, Terminal just hangs. I've been able to get the Mac to return the device ID using the "devices" command, but this is intermittent. Normally even this command causes Terminal to hang.
ADB debugging is "on". Flashtool works. ADB commands work. The phone can boot without issue. I can successfully get "fastboot help" to work.
What I've tried:
wiping the Mac HD, installing a fresh OS and installing the latest version of Fastboot from the SDK
Installing the Windows drivers directly from Sony and the latest Platform Tools directly from Google
Running "sudo fastboot" from Terminal on the Mac
Using various usb ports on both machines
Rebooting both machines between steps
Reflashing both Marshmallow and Nouget using Flashtool.
The USB cable I'm using is the one included with the phone. I could issue fast boot commands over this cable a few days ago.
Anyone got any ideas about what I've done wrong here? I'm really confused and I'd like to get rooted again if at all possible.
Try flashing stock firmware with Flashtool from Androxyde, not Emma if that may help.
ondrejvaroscak said:
Try flashing stock firmware with Flashtool from Androxyde, not Emma if that may help.
Click to expand...
Click to collapse
Thanks for trying to help me out!
So I tried flashing an Xperifirm stock ROM using Flashtool from Androxyde like you recommended. Unfortunately I get the error:
ERROR - Processing of system.sin finished with errors.
After this the phone will no longer boot. When trying to boot I receive the error message:
The software update failed. Make sure that your phone is connected to the computer and try again.
I've read that it may be a good idea to try multiple different images built from Xperifirm downloads, so I'll do that and report back what happens.
I got that error last time I updated, and was puzzled but tried to leave the phone in flash mode (green led) and flash it again. (I did not unplug the phone so I did not see the result of the first flash) This did leave flashtool without the initial phone info, checking for root and all that but this time the firmware flashed. I did include the fsc file into the ftf, I have no idea if it was a fluke or something but second flash with the phone already in flash mode worked. I know it sounds crazy but It might be worth a shot. Other than that it sounds like a bad cable with the inconsistent fastboot behavior but then again you could flash with Emma, which in turn should not affect fastboot. Odd.
88% said:
Thanks for trying to help me out!
So I tried flashing an Xperifirm stock ROM using Flashtool from Androxyde like you recommended. Unfortunately I get the error:
ERROR - Processing of system.sin finished with errors.
After this the phone will no longer boot. When trying to boot I receive the error message:
The software update failed. Make sure that your phone is connected to the computer and try again.
I've read that it may be a good idea to try multiple different images built from Xperifirm downloads, so I'll do that and report back what happens.
Click to expand...
Click to collapse
I would definitely try diferrent cable!
The Software update error means there is inconsistency in flash memory and bootloader fails to load initial image after flash. Also what may help, try to download firmware using Flashtool built-in Xperifirm, that is is called "Internal - Service Exchange Unit" and flash it first in Flashtool flashmode. Then let it boot and when it work, flash your desired version of firmware..
So I tried a number of images built from Xperifirm downloads and finally got one of them to flash properly. I'm not sure if this was due to the specific image or if I just got lucky, but my phone can boot again!
ondrejvaroscak said:
I would definitely try diferrent cable!
Also what may help, try to download firmware using Flashtool built-in Xperifirm, that is is called "Internal - Service Exchange Unit" and flash it first in Flashtool flashmode.
Click to expand...
Click to collapse
OK, I can try that. Just to confirm, is this a step that I should still take given that I can boot now? While I can boot, I still can't get into Fastboot through Terminal. I was successfully able to get a device ID using the "fastboot devices" command once, but running this command a second time caused a full system freeze on my desktop.
I've been able to use Fastboot again!!!
In case anyone else is unfortunate enough to come across this issue, it seems the solution was to reset the phone through Settings. (I have no idea why resetting the phone through settings would be any different than choosing to wipe via Flashtool though)
Thanks so much to everyone who helped with this! I think there's a good chance I'd still be stuck if I hadn't flashed the new image using Flashtool from Androxyde.
edit: I ran into this issue again and noticed that I missed a step in my original reply. In order to get Fastboot working again, I needed to connect using adb and tell the phone to remember my computer on the prompt.
88% said:
I've been able to use Fastboot again!!!
In case anyone else is unfortunate enough to come across this issue, it seems the solution was to reset the phone through Settings. (I have no idea why resetting the phone through settings would be any different than choosing to wipe via Flashtool though)
Thanks so much to everyone who helped with this! I think there's a good chance I'd still be stuck if I hadn't flashed the new image using Flashtool from Androxyde.
Click to expand...
Click to collapse
thanks for posting the cause/what you did to fix it.
it might help others, which is what the community is about.
Related
I was running streakdroid 1.8.1, and was having the wifi/3g problem, and after trying the below suggestion (which was posted in the dev section of the 1.8.1 thread post#367 link=http://forum.xda-developers.com/showpost.php?p=11869560&postcount=367):
--------------------------------------------------------------------------
Originally Posted by strvmarv
This put me on baseband GAUSB1A134031-US and appears to have cleared up the Data that wouldn't enable without a reboot, so far:
1. extracted the decoded ATT 2.2 340 pkg from here...it's the dropbox link BTW! (dropbox link)
2. grabbed the amss.mbn and dsp1.mbn (if you don't want to do step 1 then get the already extracted files here)
3. went into fastboot and flashed both of them
Dumb question, anyone know if it's possible to lose your carrier unlock when doing such things?
--------------------------------------------------------------------------
Now my streak doesn't boot, can't get to fastboot (pwr+camera), or recovery (vol+,vol-, pwr). Sometimes all three led's light up, and stay on and nothing happens, and sometimes the LED's stay off and nothing happens.
I tried using qdltool (vol+, usb connection to PC) , and it timesout after reboot ok message after I click RUN in qdltool. I installed both the qualcomm and dell fastboot drivers as per instructions, and I don't have a yellow ! in device manager.
Would appreciate any suggestions on what I should try next.
jfvidalc said:
I was running streakdroid 1.8.1, and was having the wifi/3g problem, and after trying the below suggestion (which was posted in the dev section of the 1.8.1 thread post#367 link=http://forum.xda-developers.com/showpost.php?p=11869560&postcount=367):
--------------------------------------------------------------------------
Originally Posted by strvmarv
This put me on baseband GAUSB1A134031-US and appears to have cleared up the Data that wouldn't enable without a reboot, so far:
1. extracted the decoded ATT 2.2 340 pkg from here...it's the dropbox link BTW! (dropbox link)
2. grabbed the amss.mbn and dsp1.mbn (if you don't want to do step 1 then get the already extracted files here)
3. went into fastboot and flashed both of them
Dumb question, anyone know if it's possible to lose your carrier unlock when doing such things?
--------------------------------------------------------------------------
Now my streak doesn't boot, can't get to fastboot (pwr+camera), or recovery (vol+,vol-, pwr). Sometimes all three led's light up, and stay on and nothing happens, and sometimes the LED's stay off and nothing happens.
I tried using qdltool (vol+, usb connection to PC) , and it timesout after reboot ok message after I click RUN in qdltool. I installed both the qualcomm and dell fastboot drivers as per instructions, and I don't have a yellow ! in device manager.
Would appreciate any suggestions on what I should try next.
Click to expand...
Click to collapse
search for the QDL tool, follow instructions and you will be in business again.
I tried QDL tool, and it fails with a fastboot timeout error:
"wait ADB fastboot mode timeout!"
That means you dont have the fastboot driver loaded right.
First is the qualcom driver which you made through... after the small stuff loads. It then pops over to fastboot driver.
Try another driver or pc
Sent from my Dell Streak using Tapatalk
I download and successfully installed the Dell R288920 drivers.
Is there some other driver that works better?
i would remove fastboot drivers... reboot, use reinstall drivers and use a different usb...
are you running x64 windows by chance?
I have both a 64bit Win7 and a 32bit WinVista. I followed instructions on streakdroid.com to install qdl tool on 64bit, as well as trying it on 32bit, and they both fail in the same place.
Here's the tail end of the qdl tool log file:
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device .........
ERROR[D2]: wait ADB fastboot mode timeout!
Please check that device is exist and driver is properly installed.
Download Fail! - 2011/03/06 23:34:45
Elapsed Time: 30.55 sec
It may be the drivers or it may be the Streak. I have a Streak that isnt recognized as a USB device when plugged in and will not boot into fastboot mode (black screen) with the camera+power buttons. I have tried on 3 PC's(2 windows 7, 1 linux) and none will talk to it via ADB. However they will talk to my other working Streak so I know it isnt the driver.
I suspect it is corrupt NAND memory and have come to the conclusion that the only way to fix it is to get someone to JTAG reprogram it or swap out the mainboard. I would love it if someone can prove me wrong though...
BTW i bought this Streak in this condition so I dont know for sure how it got in this state.
your missing something.. def a driver issue says so itself.
do you get fastboot to work at all outside the qdl tool? if so can you follow the following guide?
http://forum.pocketables.net/showthread.php?t=8285
That's just it, the streak won't power up (pwr+camera), which would allow me to do fastboot outside of qdl tool.
Before I bricked it, I was able to run fastboot outside of qdltool all the time without any problems.
its not bricked... there is an issue with the timing of the driver kicking in or something driver related.. try another pc.
this is a pc issue.. not a streak issue. This part was always the biggest pain in my ass.. took me hours to get my system working right for this stuff.. the streak.. no issues....
i think the streak is unbrickable like the galaxy s phones.
I've tried both my PC's (desktop Win7 64, laptop WinVista 32), and both get the same error.
I've also tried different usb ports. When I first tried fastboot a couple of months ago, I was able to install the correct driver because I was able to start the streak in fastboot mode which then allowed me to install the driver on the desktop ( called android something if I recall correctly).
The problem I had with the QDL tool was the ADB driver also. The instructions I watched didn't include installing it, but did include downloading the folder that had it. If you are following the visual tutorial from the streakdroid website, go into all the folders you downloaded in the process. Somewhere in there is your specifc ADB driver. I was getting the ADB fail also until I found my driver and it installed. Good luck.
Sent from my Dell Streak using XDA App
I agree with the above post. You havent updated the correct driver. I noticed that when i searched through the recovery folders i notoced that the qcuser driver or whatever it was called, was in multiple folders....i experienced the same ADB error you did but i just kept switching with qcuser driver until i found the correct one. Go have a second look or third look....im sure ull find the right one.
Sent from my Dell Streak using XDA App
I've tried all three qcser,qcusb and qcmdm in the repairtool (qdltool) driver subdirectory for 32bit windows in winvista and wnet, with no luck.
Did any of you have problems putting the streak in fastboot mode independent of the PC, because that's not working for me. It used to work for me by pressing pwr + camera buttons.
I believe the ADB drivers were in the other folder you downloaded per the directions.
Also, I was able to get into fastboot prior to the QDL tool, but I don't believe that matters at all. The QDL tool is halfway there at the point it errors on you. You just need that correct ADB driver. You are so close, don't give up. Try the faq section of streakdroid.com
Furthermore, if you have access to an XP machine use it. You are almost back to Streakville.
Sent from my Dell Streak using XDA App
see if this helps:
http://forum.pocketables.net/showthread.php?t=8214
EUREKA!!!!.
Looks like the flashboot image on the streak was corrupt, so I was able to use streakflash to recover it.
Running nandroid restore as I type this. so hopefully I can get back in business.
Thanks to all of you guys for your suggestions.
I'll let you know if the nandroid restore is successful.
jfvidalc said:
EUREKA!!!!.
Looks like the flashboot image on the streak was corrupt, so I was able to use streakflash to recover it.
Running nandroid restore as I type this. so hopefully I can get back in business.
Thanks to all of you guys for your suggestions.
I'll let you know if the nandroid restore is successful.
Click to expand...
Click to collapse
What is streakflash? a new tool? like QDL?
Krad said:
What is streakflash? a new tool? like QDL?
Click to expand...
Click to collapse
See this page - it is a version of QDLTool that only flashes some files. I believe that it is used to repair the boot.img.
From this page:
Q: I’m trying to flash my Streak with the QDLTool but it keeps coming up with Error D2 ADB Timeout
A: This can be for a number of reasons. Firstly, look at what is displayed on the screen of the Streak:
Nothing / Screen is blank: This could be a sign of a corrupted fastboot image. Download streakflash.zip from the Downloads section and use the version of QDLTool it contains to reinstall the base images. You can then retry using QDLTool from repairtool.zip
Black screen, says “DT is in FASTBOOT_MODE”: This can be the sign of a driver issue – Try reloading the Fastboot/ADB drivers
White screen, says “FASTBOOT_MODE”: Go through the process again, this time using a different USB port.
Click to expand...
Click to collapse
Nandroid restore of streakdroid 1.6.0 successful.
I've been trying to upgrade to the more recent versions, but none of them (at least in my case) are as stable as 1.6.0.
1.6.1 with it's builtin perfmod is unstable.
Both 1.7.x and 1.8.1 are stable, but they suffer from the wifi/3g problem. Both wifi and 3g work, but I usually have to reboot to switch from one to the other, which is a hassle.
Yes, I've tried factory resets on all of them, but eventually, I either have random reboots, or FC's galore.
I know other people have gotten 1.6.1, 1.7.x, and 1.8.x to run stable, but I've had no such luck.
So for now, I'm sticking with 1.6.0 ( I get quadrant scores in the 1600-1700 range, which is pretty good).
Anyway, thanks again for all your help.
Hello everyone,
I'm writing here, because accidentally i turned my zenfone 2 into a brick, following an indian youtuber on this link https://www.youtube.com/watch?v=BJPEc1NG_k8&t=185s&list=FLJXXdfRBIfVwi7iWKHUJJrw&index=1 while trying to update to Nougat 7.1.
The guide is very well done and precise, in fact the fault is totally mine because i accidentally launched by using ADB, the bootloader of the Zenfone 2 ZE550ML then the screen became blank on power up...
So i followed this guide https://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 stopping before point 2) and at least i reached to get out from the permanent blank screen.
Now i'm in trouble because if i use ASUS flash tools (after installing Intel Driver), i am able to see the phone and trying to install on it the .raw file, but at the end of a while, it says "Flash image Failure (Wrong image format).
Then i tried the way "2", installing it by using fastboot, i unzipped the official ROM for ZE551ML and tried to install one per one as the described in the guide, the various parts of the SO, but each time i send a command (checked many times the sintax), the software starts downloading it on the phone and then stops, saying everytime with every file "Failed".
Thinked also to ADB, but by using "adb devices" it doesn't recognize any device...
So... may the bootloader given by the guide be wrong? or an old one version? What can i do?
If i try to get into recovery mode, it just shows an USB cable forever... i'm costricted to repeat the first part of the operation with xFsTK Downloader.
I thank you for any help or suggestion.
Linx91 said:
Hello everyone,
I'm writing here, because accidentally i turned my zenfone 2 into a brick, following an indian youtuber on this link
&t=185s&list=FLJXXdfRBIfVwi7iWKHUJJrw&index=1 while trying to update to Nougat 7.1.
The guide is very well done and precise, in fact the fault is totally mine because i accidentally launched by using ADB, the bootloader of the Zenfone 2 ZE550ML then the screen became blank on power up...
So i followed this guide https://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 stopping before point 2) and at least i reached to get out from the permanent blank screen.
Now i'm in trouble because if i use ASUS flash tools (after installing Intel Driver), i am able to see the phone and trying to install on it the .raw file, but at the end of a while, it says "Flash image Failure (Wrong image format).
Then i tried the way "2", installing it by using fastboot, i unzipped the official ROM for ZE551ML and tried to install one per one as the described in the guide, the various parts of the SO, but each time i send a command (checked many times the sintax), the software starts downloading it on the phone and then stops, saying everytime with every file "Failed".
Thinked also to ADB, but by using "adb devices" it doesn't recognize any device...
So... may the bootloader given by the guide be wrong? or an old one version? What can i do?
If i try to get into recovery mode, it just shows an USB cable forever... i'm costricted to repeat the first part of the operation with xFsTK Downloader.
I thank you for any help or suggestion.
Click to expand...
Click to collapse
same here brother...i am stucked from last night..getting no help nowhere..really upset..plz let me know if you figure out something.
Which raw file version are u using
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.
I'm going crazy with this.
I installed the lastest version of flashtool, along with the x10flasher.jar that makes it the latest version.
Both fastboot and google drivers are installed (from the drivers included in flashtool), the device is recognized, the fastboot mode too, USB debugging is activated, but Flashboot gives me these errors messages:
ERROR - No device is registered in Flashtool.
ERROR - You can only flash devices.
I did the same in another PC and is the same error.
Please help it's 3 hrs already with this i'm about to kill my PC i can't see where the problem is, any help is appreciated.
So do you want to flash with fastboot or do you want to flash an FTF? For flashing FTF you need to boot the phone with the other volume key pressed.
ypnos42 said:
So do you want to flash with fastboot or do you want to flash an FTF? For flashing FTF you need to boot the phone with the other volume key pressed.
Click to expand...
Click to collapse
I want to flash a FTF. The phones need to be in flashmode right? i tried with both flashmode and fastboot and it's the same result:
When i go to "flashmode" the device list that should pop up won't appear so i can't select the firmware that is in .flashTool > firmwares.
https://imgur.com/bSOpRM7
This has nothing to do with your phone. The dialog should work even without any device connected. In fact I always prepare the flash before I connect the phone to avoid that it falls asleep before flashing starts.
You seem to not have any flashable ROMs available. When the device filter is empty, you are supposed to see _all_ of your ROMs. Did you bundle the FTF as described in various guides? You cannot flash FTF directly, you have to bundle first.
Also the device filter selector should be populated with all models supported by flashtool. Again it has nothing to do with connected devices. Is your flashtool installation ok?
ypnos42 said:
This has nothing to do with your phone. The dialog should work even without any device connected. In fact I always prepare the flash before I connect the phone to avoid that it falls asleep before flashing starts.
You seem to not have any flashable ROMs available. When the device filter is empty, you are supposed to see _all_ of your ROMs. Did you bundle the FTF as described in various guides? You cannot flash FTF directly, you have to bundle first.
Also the device filter selector should be populated with all models supported by flashtool. Again it has nothing to do with connected devices. Is your flashtool installation ok?
Click to expand...
Click to collapse
When i try to create the bundle i can't complete the "device" field because the device list is empty. I reinstalled flashtool multiple times and still no list. I don't know if it's a problem with the installation, i had installed flashtool in april and use it to flash a FTF with my Compact without problems, the same installation wasn't working yesterday and today i reinstalled and still nope.
I think last time i didn't create a bundle bc flashtool does it automatically when you use the integrated xperifirm, i can't remember exactly anyways.
dnnz said:
I don't know if it's a problem with the installation
Click to expand...
Click to collapse
Well it certainly is.
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.