Essential phone locked out - Essential Phone Questions & Answers

Hello everyone, I am in need of some help, I have this old Essential Phone, I gave it to my son and he can't remember the unlock pattern, the bootloader is unlocked but usb debugging was not enabled after factory resetting it before handing it to him, booting with volume down takes me to a bootloader menu, but there's no option to factory restore, i can't wipe it using google, it says device not found...., Is there any way to unlock this even if everything gets lost?
adb is not listing any device, fastboot does show the serial number but refuses to flash anything.
Seeing as some threads get locked because of possible theft I can provide purchase receipts if needed.

Boot into recovery and just hit factory reset

Related

HELP - Nexus 4 Won't Boot + Other Issues

Hi All,
I tried to complete a manual update of the 4.3 OTA on my Nexus 4 this evening, however unfortunately it didn't work and my phone would not boot past the 'Google' screen. After wiping the cache, and still having the issue, I decided to do a factory data wipe/restore. However the problem still persisted.
With this, I thought the only way past this was to install the factory image. I installed the 4.3 factory image just fine (after going through the various steps, including unlocking the bootloader) and it was up and running for a while installing apps. However, with this, the device had a black/blank screen for a fair few minutes and after leaving it I thought I might has well reboot. Unfortunately, this time is did not boot again.
So; off to do the same previous steps again.... fastboot oem unlock (as I relocked the device previously), load bootloader, etc, etc. Got to the system update, and it passed an error saying that fastboot is not available on a locked device. Strange as I had unlocked it, but there is was on the menu "LOCK STATE - locked"....
I am now at the stage where I can't actually keep my phone unlocked. I can complete the command fastboot oem unlock, but once I complete fastboot reboot-bootloader, the device is stating it is locked again. - This is where I need some help, PLEASE.
Sorry for the long post, but wanted to describe the situation. If you need further info from me, just let me know. I'm hoping someone far wiser than I am can help me resolve this issue...
Any help on this? - It would be much appreciated.
I too have the same problem with my phone
but my phone is 4.2.2. rooted and wouldn't load past the 'google' boot screen
I can still go into clockwork recovery mode and I wiped cache, did factory reset and I can't even access my phone through the computer

Nexus 6P black screen will not boot into OS

Okay, so there is no screen protector or anything. Not rooted or unlocked or tampered in any way. I've had the phone for 26 hours and then the following happened:
EDIT: YouTube video added https://youtu.be/yAVmTz7MQbQ
I pulled the phone out of my pocket to unlock it. I see the lock screen and put in my pin (yes, I see the actual screen and stuff on it. Let me make that clear.) after I enter my pin successfully the screen locks itself. I contacted Google support and they said to factory reset it. I did the full factory data reset in the recovery mode (again, the screen works. I can see everything to do a FDR and I can see the boot animation) and it starts to boot up. Once I see the "welcome" screen it instantly locks itself. I can hear the audible "latch" locking sound that it makes when you press the power button. I know the buttons are not malfunctioning because they work perfectly fine in bootloader / recovery mode to scroll up and down and select things. I've tried multiple things but nothing seems to work. The problem here is that I want to try and do a factory image but my computer will NOT recognize my Nexus 6P when in recovery mode / bootloader mode. I have all the drivers installed but since I can't access the OS and enable OEM UNLOCKING there is no way to factory flash a factory image is there? Can someone maybe help point me in the right direction? Again, I can NOT access the OS at all whatsoever.
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
hutzdani said:
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
Click to expand...
Click to collapse
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
xandr00 said:
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
Click to expand...
Click to collapse
Can you run fastboot format cache and format user data? Then will anything happen ?
Sounds like you need to edit the partition that holds the data change for allow OEM unlock - there's a few threads about this on XDA for the N9 and N6 as far as I can remember.
It would seem the ability to flash a fresh system.img would solve this

OEM locked and stuck in Android safe mode "Decryption unsuccessful"

I recently successfully restored my Axon 7 (A2017U) to B20 and tried to OEM lock it again. After running "fastboot oem lock", the phone rebooted, but came up with something that said "To start Android, enter your password." I didn't have a password before, so I tried something I found online called default_password to see if it would unlock (which it didn't) & then other passwords to get the phone to wipe itself and essentially perform a factory reset. However, now it is stuck in Safe Mode and says "Decryption unsuccessful: The password you entered is correct but unfortunately your data is corrupt." When I try to wipe the phone, it says it is factory resetting, but then it restarts and goes to a blank screen. (Which I suspect is because TWRP is still installed as a recovery, not stock). In addition, power+volume up no longer works since the phone is oem locked, but power+volume down takes the phone into Factory Test Mode. My computer still recognizes the phone when it shows up in Safe Mode, but I cannot see it in ADB.
Where can I go from here to factory reset the phone? Is it possible to send this to ZTE to fix since it is OEM locked at the moment?
I followed razorblader's advice and successfully got the phone into EDL mode and ran tenfar's tool. However, that made it worse and now the phone just shows ZTE for the second & the screen goes blank.
EDIT: Nevermind, I was running that program without recovery.img/boot.img in the same directory, D'OH! Luckily, I still had comms with the phone after that mistake & I re-ran the program successfully. I can now get into TWRP recovery. However, booting into system still shows the corrupt data message. I'm going to try a factory reset from TWRP and see if that fixes the issue.
OK good news, got my Axon 7 working again, stock + locked & am currently posting this from it. One reason I wanted to relock it however was to get OTAs and right now B27 is showing up. Now before I almost brick my axon again, do I need to flash stock B20 recovery before I'm able to install this update? Also, I'd like to get to B29 eventually, but I'm guessing I need to update to B27 first. (correct me if I'm wrong though)

Nexus 6P Bootloop issue (latest solution did not work)

Hi I have a nexus 6p entering bootloop yesterday. fully stock with latest OTA update. device is locked, not rooted, bootloader LOCKED.
I can get to fastboot screen (android robot laying down), with "start, reboot bootloader, recovery, barcodes, poweroff", all options result in bootloop again (except power off and barcode). Cannot go into recovery mode, cannot wipe cache/factory reset.
I tried using the latest solution to disable to big cluster but that guide requires the phone to have a unlocked bootloader which I cannot unlock. I get the FAILED [remote: OEM unlock is not allowed], because I never enabled developer option to unlock the phone and never enabled USB debugging.
Phone was manufactured 12-2015. Called google and was told because the phone was not bought from google store there is nothing they can do. Called Huawei was told the phone is out of warranty and there is nothing they can do.
Tried heating the phone/blowdryer method. tried freezer method. Nothing worked.
What can I do at this point?
Same here
Same exact problem here - "Tried heating the phone/blowdryer method. tried freezer method. Nothing worked." Any thoughts... anyone?
I have the same problem. I'm not able to find any information how to unlock the phone in this state. Any hint?

Mistakenly run Google Remote Erase, Now the screen is frozen, probably FRP

I have mistakenly run Google Remote Erase https://android.com/find on my phone. The phone has done a complete factory reset. Now it boots to initial blue setup screen "Hi there...English...Start", but the touchscreen is not responsive. There is a lock icon in the left upper corner. So I assume it is FRP (Factory Reset Protection) by Google.
I repeated Hard Reset and even managed to boot to Safe mode (still the same initial blue setup screen) as per https://www.verizonwireless.com/support/knowledge-base-217744/
but still the touchscreen is not responsive.
The phone is from Amazon.com, I am in Canada. The bootloader was unlocked and then re-locked. So BL is now locked.
The short story long: -) I have had two identical G6Plus handsets. One was stolen 3 days ago. After that I changed my Google password and mistakenly run Google Remote Erase on the one which was NOT stolen
Will FW flashing remove FRP? To flash FW, I will need to unlock BL. Is it possible while FRP?
FRP remains activated even if you flash a new FW. It's possible to flash a FW while bootloader is locked. But it must be exactly the same build which is currently installed on the phone. Have a look on this page: https://mirrors.lolinet.com/firmware/moto/evert/official/
You'll find different folders for each software channel. To find your software channel you can boot into bootloader (power on while press+hold vol-) Watch out for XT1926-3 for example. The last digit (e.g. -3) defines the software channel.
rybshik said:
I have mistakenly run Google Remote Erase https://android.com/find on my phone. The phone has done a complete factory reset. Now it boots to initial blue setup screen "Hi there...English...Start", but the touchscreen is not responsive. There is a lock icon in the left upper corner. So I assume it is FRP (Factory Reset Protection) by Google.
I repeated Hard Reset and even managed to boot to Safe mode (still the same initial blue setup screen) as per https://www.verizonwireless.com/support/knowledge-base-217744/
but still the touchscreen is not responsive.
The phone is from Amazon.com, I am in Canada. The bootloader was unlocked and then re-locked. So BL is now locked.
The short story long: -) I have had two identical G6Plus handsets. One was stolen 3 days ago. After that I changed my Google password and mistakenly run Google Remote Erase on the one which was NOT stolen
Will FW flashing remove FRP? To flash FW, I will need to unlock BL. Is it possible while FRP?
Click to expand...
Click to collapse
Try LMSA'S Flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
sd_shadow said:
Try LMSA'S Flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Click to expand...
Click to collapse
I have removed FRP by connecting external Keyboard/mouth, then unlocked BL and flashed new FW. It works normal with external Keyboard/mouth now, but the touch screen is still not responsive. So it probably is just a hardware problem having nothing to do with FPR

Categories

Resources