The title says most of my situation. I've had this since 2012 and some time early last year it just up and stopped booting into android. I have no idea what happened because my girlfriend was using it at the time and she swears she didn't change anything.
Anyways, the bootloader is locked and I have tried to go to recovery and factory reset with no luck. Wiped cache and did nothing as well. I am seeing that windows 7 is sort of recognizing the device. It shows up under device manager as "Android Bootloader Interface"
I've updated the USB drivers and installed ADB as well. When checking the command prompt for ADB Devices, it shows nothing.
I installed Wugs toolkit and it won't even find the nexus either. There has to be SOMETHING that can be done in this situation right?
:EDIT: I was able to unlock it using fastboot but I still can't get it to be found by anything else.
I can get it recognized using the fastboot command prompt, but I can't execute any commands in it. Everything like "fastboot flash boot boot.img" just returns a FAILED message with either invalid argument or no such address or device.
What I am trying to do is just recover it and start using it again. Of course I want to put Android 5.0 on it, but I would be okay with anything as long as it boots, really.
:EDIT: I was actually able to get it to work. I have no idea what specifically had fixed it, but I uninstalled and reinstalled the drivers a few times and ran fastboot and was able to wipe it and install Android 5.0! It was running great!
Hello this is my first post. I have searched the threads and internet for answers but I have not been able to find a solution.
I have been customizing my phones since the days of baked black bean on my galaxy S1, but I am no expert at this stuff. Until about a week ago, I was happily running RR on the OPO (great ROM) but it has gotten a bit slow so I figured it was time to get a OP5.
When I boot into fastboot, my device is recognized with the command fastboot devices. My phone showed the following:
fastboot mode
product_name - QC_Refernce_Phone
VARIANT - MSM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - c7ccda2
SECURE BOOT - yes
DEVICE STATE - locked
When I ran fastboot oem unlock, CMD prompt shows FAILED, however, the option to unlock the bootloader shows up on the OP5. I go through the process and wipe data. My phone now shows that it is unlocked, and I go into developer options to get advanced reboot/USB debugging/verify OEM unlock is still enabled. When I go back to fastboot, I am unable to flash TWRP. I have now seen a number of errors, usually:
FAILED (remote: Requested download size is more than max allowed) or target did not report max download size, or command write failed (no error). I have tried installing 4 different versions of ADB/fastboot from different sources, and I have tried TWRP cheeseburger 46, 58, and 62. I have also tried two different USB ports and 4 different USB drivers.
Does anyone know what could cause these issues or how to get TWRP installed? Any help would be much appreciated. I really want to get rooted and get substratum running.
hmm
did you type fastboot devices to check that u got connection ? do you have another pc to try ? another usb port
edit: also try disable developer option and aplly it again with oem unlock tapp
EDIT2: if you cant still get it work you can try
Advanced settings -> Backup & reset -> Reset all settings and after that unlock bootloader
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
bro do u find solutions for this
I found an actual fix for this problem. Basically I had to download Large Address Allocation Tool (LAA) which you can find online. I would link to it but I do not have the website handy.
I found this solution after soft bricking my phone by installing Oreo (I don't suggest using VPN to pretend you are in Canada. Just run the beta or wait for the US release).
Essentially, you just need to run this tool on your adb.exe. From what I understand, the issue is just that adb is not using enough RAM. I think you'll need to be running Windows 7 64bit with at least 4GB RAM. I hope this info can help someone else!
jsnell said:
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
Click to expand...
Click to collapse
Ever since i ditched windows and went with ubuntu i have not had one single driver issue, not one single hiccup on anything. It's been two months.. I'm never going back. lol. Every time I use adb and or fastboot it always works.
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.
Hi all. So I have a frustrating issue with my phone after having updated to the last official firmware from the Asus website. I noticed that the phone operation was very slow, so I decided to do a factory reset from recovery. Everything went well until I am somehow locked out of my phone via FRP. The weirdest thing is that instead of asking for google credentials, it's asking for a pattern, which I am correctly inputting but it refuses to recognize it. So now I'm stuck with a locked out phone. Am I SOL at this point or is there a way to get past this other than taking it to a service center?
Things I've tried that haven't worked:
1. tried to erase user config in fastboot (returned error FAILED)
2. wiped all data in recovery
3. tried to flash to an older version via asus flashtool but didn't work as the device isn't recognized
Any help would be greatly appreciated.
xenoche said:
Hi all. So I have a frustrating issue with my phone after having updated to the last official firmware from the Asus website. I noticed that the phone operation was very slow, so I decided to do a factory reset from recovery. Everything went well until I am somehow locked out of my phone via FRP. The weirdest thing is that instead of asking for google credentials, it's asking for a pattern, which I am correctly inputting but it refuses to recognize it. So now I'm stuck with a locked out phone. Am I SOL at this point or is there a way to get past this other than taking it to a service center?
Things I've tried that haven't worked:
1. tried to erase user config in fastboot (returned error FAILED)
2. wiped all data in recovery
3. tried to flash to an older version via asus flashtool but didn't work as the device isn't recognized
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Ok i had the exact problem the latest patch for the device , i manually updated to oreo 8.1, has some bug that sometimes it doesnt recognise pin or pattern after some reboots it recognized it but it's not persistent as it stopped working.
I was able to fix it by flashing an older version with sp flashtool. You need to download and properly install SPFlashtool and everything it needs then you have to search for an spflashable rom that it's compatible with the one you have.
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
McMeth said:
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
Click to expand...
Click to collapse
I've been reading around a little, it seems like it could be a recovery issue? try the official lineage recovery if you're not already. If you can get fastboot working at all try to reflash the stock rom and go from there.
I had a similar problem. Use a windows computer with the essential drivers (you can download from reddit) and use the official cable
DO NOT use the cable supplied with the Essential phone for data transfer, it is likely to brick your phone. Use a high quality one from a reputable manufacturer!