I've had an essential phone for a few months now. I just now decided to root the phone. I went through an installation guide where I have unlocked the bootloader using fastboot flashing unlock_critical and fastboot flashing unlock. My bootloader is unlocked, so I used the command to find which slot I have. I had an A slot so I followed the instructions, flashed twrp and now when TWRP boots. I have an unresponsive screen. It will not allow me to type anything.
Try booting from this twrp
https://drive.google.com/file/d/1YxJJj96Web0ikHXdHf_zboZT_KSYl7Nj/view
There was an issue with Touch and TWRP. I also ran into this. From within TWRP, I flash the TWRP.zip and it seems to have solved the issue, though touch is still a bit off (slightly skewed to the right but manageable).
I was able to gain root fairly easy. I was following a rooting thread from another forum. Once I switched back to following a root forum from xda. I was good to go. The issue I have now is I have an OTA update waiting, but now I have root. I had an issue with touch on twrp, but I have it solved now. I'm currently running stock with root. I "might" flash LOS soon, I'm not sure...
in the event of no touch you usually need to install twrp
download the twrp zip
and do this once in twrp
adb shell
twrp sideload , it will drop back to cmd line
then you can adb sideload twrp-installer
then you should have fully functional twrp
Related
Hi,
unlocked the bootloader, installed CWM (no_gui version)...didn't work so I've took the TWRP version posted in another community. It worked. rootet it with SU and adb shell commands.
No I only can get into TWRP. No matter what I try. Phone is recognized by adb (when booted into TWRP) but i cannot boot into system or bootloader anymore it simply everytime goes into TWRP.
How do I fix it?
OK solved it by myself
If you solved it, you should post how in case someone else gets the same isue.
Issue resolved, thread closed.
I've done a lot of research on a reliable way to root my Moto X Pure Edition XT1575 and want someone to check my plan before I pursue this. I'm gonna download TWRP for Clark and superSU 2.78 and put them in the same folder and open up the command prompt in that folder. Then hook up to the PC and enter the following command "fastboot boot twrp.img" then I'm gonna replace the twrp.img with the name of the twrp file and backup to the SD. Then reboot into the bootloader again and flash twrp with fastboot "fastboot flash recovery twrp.img" then start recovery and go to reboot into recovery again to lock it in. Then I'm booting back into twrp and going to Advanced & Terminal and entering the following command "echo SYSTEMLESS=true>>/data/.superSU then back home then flash superSU 2.78.
Please correct me on everything that may be wrong. If there's a better way to root, tell me how to do it your way.
My device info:
Moto X Pure Edition XT1575 (clark)
Build# MPH24.49-18
Kernel version 3.10.84
Android version 6.0
Bootloader OxAo48
Sent from my Moto X Pure Edition
ElectroJoe said:
I've done a lot of research on a reliable way to root my Moto X Pure Edition XT1575 and want someone to check my plan before I pursue this. I'm gonna download TWRP for Clark and superSU 2.78 and put them in the same folder and open up the command prompt in that folder. Then hook up to the PC and enter the following command "fastboot boot twrp.img" then I'm gonna replace the twrp.img with the name of the twrp file and backup to the SD. Then reboot into the bootloader again and flash twrp with fastboot "fastboot flash recovery twrp.img" then start recovery and go to reboot into recovery again to lock it in. Then I'm booting back into twrp and going to Advanced & Terminal and entering the following command "echo SYSTEMLESS=true>>/data/.superSU then back home then flash superSU 2.78.
Please correct me on everything that may be wrong. If there's a better way to root, tell me how to do it your way.
My device info:
Moto X Pure Edition XT1575 (clark)
Build# MPH24.49-18
Kernel version 3.10.84
Android version 6.0
Bootloader OxAo48
Sent from my Moto X Pure Edition
Click to expand...
Click to collapse
You've researched well. Couple things: The command is "echo SYSTEMLESS=true>>/data/.supersu", you added capitols on supersu. Next your first command of "fastboot boot twrp.img (or whatever you rename the TWRP recovery image to)" will live boot TWRP, which for our device is not necessary. Live booting is essentially booting into a custom recovery environment without actually installing the recovery. This is useful for devices that DO NOT have factory images available, which allows you to make a backup in the live environment prior to altering your device. We have factory images and factory recovery images, so you can skip this step and go right into "fastboot flash recovery twrp.img (or again, whatever you rename the recovery image to). Then after the recovery flash from within fastboot, you must reboot into recovery using the button select options within fastboot or your recovery will be overwritten by the stock recovery. Upon first boot of TWRP you'll have an option to keep your device read only or read/write. I personally choose NOT to keep it read only, rather read/write, because I don't care about taking OTA's with a custom recovery, but this is up to you. Then you'll want the supersu.zip on your device already (you want the regular standard current version, not a modded one from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703), either on your internal or external sd. And yes, prior to flashing supersu enter the command in TWRP without quotes "echo SYSTEMLESS=true>>/data/.supersu" (this prevents the bootloop that our device gets when flashing supersu in systemless mode). And your good to go. I just did this a few weeks ago from clean fastboot flashing the latest factory image, works perfectly.
Now for some clarity, I'd like someone else to chime in on the TWRP command "echo SYSTEMLESS=true>>/data/.supersu" that has to be entered. I know for sure entering the command prior works, and roots properly, but I have also read that the latest 2.78 version of supersu does not require this. I'd really like someone that KNOWS FOR SURE (no opinions) if this step can now be bi-passed, or if our device requires and will always require this step now and in the future. This will help solve a ton of questions about this issue that are spread throughout the forums so users don't have to dig to get a simple answer.
Thanks for taking the time to educate me on this. I'm gonna give it a try in a few minutes. Will I be a developer if I get it right? Hahaha I'll let you know how it goes
Sent from my Moto X Pure Edition
annoyingduck said:
You've researched well. Couple things: The command is "echo SYSTEMLESS=true>>/data/.supersu", you added capitols on supersu. Next your first command of "fastboot boot twrp.img (or whatever you rename the TWRP recovery image to)" will live boot TWRP, which for our device is not necessary. Live booting is essentially booting into a custom recovery environment without actually installing the recovery. This is useful for devices that DO NOT have factory images available, which allows you to make a backup in the live environment prior to altering your device. We have factory images and factory recovery images, so you can skip this step and go right into "fastboot flash recovery twrp.img (or again, whatever you rename the recovery image to). Then after the recovery flash from within fastboot, you must reboot into recovery using the button select options within fastboot or your recovery will be overwritten by the stock recovery. Upon first boot of TWRP you'll have an option to keep your device read only or read/write. I personally choose NOT to keep it read only, rather read/write, because I don't care about taking OTA's with a custom recovery, but this is up to you. Then you'll want the supersu.zip on your device already (you want the regular standard current version, not a modded one from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703), either on your internal or external sd. And yes, prior to flashing supersu enter the command in TWRP without quotes "echo SYSTEMLESS=true>>/data/.supersu" (this prevents the bootloop that our device gets when flashing supersu in systemless mode). And your good to go. I just did this a few weeks ago from clean fastboot flashing the latest factory image, works perfectly.
Now for some clarity, I'd like someone else to chime in on the TWRP command "echo SYSTEMLESS=true>>/data/.supersu" that has to be entered. I know for sure entering the command prior works, and roots properly, but I have also read that the latest 2.78 version of supersu does not require this. I'd really like someone that KNOWS FOR SURE (no opinions) if this step can now be bi-passed, or if our device requires and will always require this step now and in the future. This will help solve a ton of questions about this issue that are spread throughout the forums so users don't have to dig to get a simple answer.
Click to expand...
Click to collapse
It worked! I'm rooted and looking for a stable rom with a lot of features and customizations that works with Verizon LTE. I also want viper4android. I'm glad I backed up because I tried flashing a viper4android zip and it caused my phone not to boot. It just sat at the unlocked bootloader warning so I just restored it. Evidently, I was supposed to unzip the file in esfile Explorer and install the apk. I think I also needed the selinux mode changer app.
What would I gain by installing a custom Kernel to my rooted stock rom? Can I even do that?
Sent from my XT1575 using Tapatalk
ElectroJoe said:
It worked! I'm rooted and looking for a stable rom with a lot of features and customizations that works with Verizon LTE. I also want viper4android. I'm glad I backed up because I tried flashing a viper4android zip and it caused my phone not to boot. It just sat at the unlocked bootloader warning so I just restored it. Evidently, I was supposed to unzip the file in esfile Explorer and install the apk. I think I also needed the selinux mode changer app.
What would I gain by installing a custom Kernel to my rooted stock rom? Can I even do that?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Flash ViPER4Android from here, no SELinux changing app needed: http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
As for custom kernel, Frankenclark. Features available is in the post: http://forum.xda-developers.com/moto-x-style/development/kernel-frankenclark-t3289939
annoyingduck said:
Now for some clarity, I'd like someone else to chime in on the TWRP command "echo SYSTEMLESS=true>>/data/.supersu" that has to be entered. I know for sure entering the command prior works, and roots properly, but I have also read that the latest 2.78 version of supersu does not require this. I'd really like someone that KNOWS FOR SURE (no opinions) if this step can now be bi-passed, or if our device requires and will always require this step now and in the future. This will help solve a ton of questions about this issue that are spread throughout the forums so users don't have to dig to get a simple answer.
Click to expand...
Click to collapse
I literally did this to a fresh MXPE two weeks ago... misspelled the filename so it wasn't recognized (it isn't supersy apparently), and flashed SuperSU 2.78-SR1, rebooted and stuck at boot logo for 20 minutes. Rebooted into TWRP and entered the correct echo command to create the .supersu file and reboot, it looped twice quickly and then went to the lockscreen after a 2-3 minutes.
I have the US version of the Axon 7. TWRP 3.0.2, with locked bootloader, stock rom, no root.
Ultimately I want to follow this guide by @Oki, to root with safetynet:
https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
That guide says I have to have TWRP 3.0.3, so that's what I am trying to install.
I've already installed TWRP 3.0.2, following this guide, up through step A:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Once that was installed I tried to flash the official TWRP 3.0.3, using both TWRP and axon7tool, and it seems to flash, but recovery boots to a black screen. I'm pretty sure it is in edl mode. Shouldn't I be able to upgrade TWRP this way?
So I gave in and downloaded the gigantic unlock kit, and tried to follow the instructions from @jcadduono, except from TWRP 3.0.2. It fails trying to flash step 1 with an assert that product name isn't P996A0.
Help! What should I do next?
StickMonster said:
I have the US version of the Axon 7. TWRP 3.0.2, with locked bootloader, stock rom, no root.
Ultimately I want to follow this guide by @Oki, to root with safetynet:
https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
That guide says I have to have TWRP 3.0.3, so that's what I am trying to install.
I've already installed TWRP 3.0.2, following this guide, up through step A:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Once that was installed I tried to flash the official TWRP 3.0.3, using both TWRP and axon7tool, and it seems to flash, but recovery boots to a black screen. I'm pretty sure it is in edl mode. Shouldn't I be able to upgrade TWRP this way?
So I gave in and downloaded the gigantic unlock kit, and tried to follow the instructions from @jcadduono, except from TWRP 3.0.2. It fails trying to flash step 1 with an assert that product name isn't P996A0.
Help! What should I do next?
Click to expand...
Click to collapse
since you're in twrp you can open that step 1 full OTA zip in 7-zip and browse to META-INF/com/google/android and open updater-script file.
you will see a line starting with assert() somewhere, just remove that line and save, then flash it
alternatively you can find a stock P996A01 recovery, flash that, then flash the zips (unmodified) from there
First unlock your bootloader
What I did was this... Already have the old twrp as you do. I got the official twrp for the axon 7 global version (even though my phone is U). I then flashed it through fastboot. I never flash recovery images through twrp. It's never worked for me on many phones. Can't go wrong with fastboot though. Good luck. I recently got my bootloader unlocked and rooted and it was a nightmare digging through these many slightly different tutorials so I know this process is a pain
StickMonster said:
I have the US version of the Axon 7. TWRP 3.0.2, with locked bootloader, stock rom, no root.
Ultimately I want to follow this guide by @Oki, to root with safetynet:
https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
That guide says I have to have TWRP 3.0.3, so that's what I am trying to install.
I've already installed TWRP 3.0.2, following this guide, up through step A:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Once that was installed I tried to flash the official TWRP 3.0.3, using both TWRP and axon7tool, and it seems to flash, but recovery boots to a black screen. I'm pretty sure it is in edl mode. Shouldn't I be able to upgrade TWRP this way?
So I gave in and downloaded the gigantic unlock kit, and tried to follow the instructions from @jcadduono, except from TWRP 3.0.2. It fails trying to flash step 1 with an assert that product name isn't P996A0.
Help! What should I do next?
Click to expand...
Click to collapse
You need to install again the unofficial TWRP 3.0.2-2.
1. Download it to your computer from http://d-h.st/dgWW (it is signed so it is recognized as a ZTE recovery and bootloader won't reject it) and extract recovery.img from it.
2. Connect your phone to your computer and boot into bootloader. In your computer type the command
fastboot flash recovery recovery.img
At this point you will have unofficial bootable TWRP again. However you have to unlock your bootloader by following the DrakenFX's guide here https://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778. You can flash the file in the guide from TWRP too.
Only after the bootloader had been unlocked you will be able to use the official TWRP. The guide to have root+safetynet requires unlocked bootloader. You should have pay attention to the requirements before initiating the steps. However do not worry, your state is easily fixable following the steps.
Thank you everyone. I really appreciate the responses. I had already figured out how to re-install the unofficial twrp, so I just followed @jcadduono's modified instructions and got my bootloader unlocked and the official twrp. I didn't realize the official twrp required the bootloader to be unlocked. I was going to get there eventually anyway, though .
AS TITLE
Install all adb drivers properly on your PC.
If you're on Marshmallow, this might help you to unlock your bootloader https://www.asus.com/zentalk/in/thread-116376-1-1.html it's a simple APK you can install on your phone.
Connect your phone to PC and reach it with adb.
Go into fastboot mode (adb reboot bootloader) and type from your cmd "fastboot oem device-info" i think is still a must to check if it worked properly.
If you're sure it's unlocked now, then flash root .zip file with TWRP, I did not flash TWRP on my ze500kl, so I think on ze550kl you can try to boot TWRP rather than flashing it as well (fastboot boot TWRPname.img), try to boot TWRP, because if you flash it there are chances to brick your phone (for example if TWRP isn't right for it), but if you try to just boot it i don't think you can damage your rom.
If you flash a root .zip file, make sure you made a full nandroid backup with twrp first, or at least to have an uninstaller .zip for it as well.. I recommend you to make a stock nandroid backup anyway before any kind of modding (espacially FLASHING).
I personally use Magisk superuser (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
I don't own a ze550kl, i own a ze500kl and this method perfectly works for me. As long as you can unlock your bootloader, i think you can flash the root without problems if you manage to boot into the proper TWRP version for ze550kl.
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum
jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/
That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.
https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc
Was finally able to get into recovery, so all is well. Thanks for the help yall
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.