Database Users

Recovery problem.

So I have an Evo and got it last Tuesday, 7/6/2010. I have been trying to hack so many different ways and flashed PC36IMG. I want to install new roms but I am not able to change my recovery image. I have used rom manager, tryed flashing different recovery images and nothing. On the screen with the red triangle, it says "E:Can't open /cache/recovery/command" I have tried anything but get stuck in boot loops and other things that don't work. I was wondering if anyone else has had this problem and has a fix for it?

Which root method are you trying? Do you currently have root? If so, You need to use use the start over method in the development section of the forums. I believe OPs name is whitslack or something similar.
Here...i found the link for you.
http://forum.xda-developers.com/showthread.php?t=715915
If you don't have root yet use this page. Follow all steps. http://forum.xda-developers.com/showthread.php?t=705113
This is assuming you were privy enough not to install any OTAs.

Have you tried simple root?
Sent from my PC36100 using XDA App

Please, help a n00b. I think I broke my Nexus S 4G

Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.

westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
What version of CWM did you flash?

Pm me and we will use a chat service (aim, yahoo messenger) and I will walk u through it.

My suggestion of what I would do is this. Find a windows computer somehow. Go to the development section and look for the sticky about rooting the ns4g. Look for the link to flash the d720 back to stock. Download all those files to a flash drive. Take the drive to the windows computer and set things up then flash the phone back to out of the box stock.
Then you can go back to the Mac and do the root and 3024 cwm recovery and rename the sh file that puts stock recovery back in at boot time. After all this you can do what you want but I would suggest staying with the stock experience. This might be extreme to fix this but in my opinion, I wouldn't waste time trying to fix it, especially since you are new to this. It's like computers, yeah you could try to fix it but you could be opening a can of worms. It might take less wasted time putting it back to complete stock instead of f-ing around trying to figure out what happened and how to fix it. You could take hours trying to fix an install of windows that keeps falling on it's face, or you could format and install windows fresh and new in maybe thirty minutes. Which is easier?

CM7 will not work at the moment because it still uses 2.3.3, go find instructions for a 2.3.4 Nandroid. if you want though,i heard that supeaosp works on a ns4g.
Sent from my Nexus S using XDA App

westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
Dude, you can't flash regular Nexus S ROMs on the Nexus S 4G.
Reflash the latest clockwork recovery.
Use fastboot flash recovery recovery.img
then...
Go to recovery, mount the USB storage, and put this zip on the usb storage:ROM
Go to recovery and flash that zip

here's the recovery that works. cwm and stock. How many times is this going to happen with new people and this phone in this forum section before a new subsection is made? We are going to be putting out a lot of these unnecessary fires with people making first time mistakes until something is done so as to not confuse them. Some don't realize that there are different versions of the same phone that aren't necessarily compatible with each other.
The way things are set up now, it isn't making this problem go away. I think that a different method should be tried if the current one isn't working too well. I'm flogging a dead horse now......

I'm looking to root my new NS4G as well -- and do it right the first time. On a Mac as well.
If the similarly-suited OP had issues I'm a bit more skeptical about my effort.
A separate forum might be necessary so people with the D720 hardware don't have near-brick experiences.
Sent from my PC36100 using XDA Premium App

soooo....did the op ever get it running again? i wonder if anyone ever took up on his paypal offer

[Q] Taboonay 2.1 suddenly unable to connect to WiFi

I flashed Taboonay 2.1 to my Icona Tab A500 last night. Everything was great. I retrieved all my usual apps and previously purchased apps back down from the market, network was working fine. Turned on tab this morning and it is unable to connect to wifi. Keeps trying several times and then says the attempt has been disabled. It sees the Motorola Surfboard but can't connect. I thought I would try to re-flash since the .zip was still on my external SD. I attempted to boot into CWM but it won't come up. It just says loading image and never goes into CWM, that's it. So, I have no ability to connect by Wifi and am unable to download Acer Recovery Installer in order to re-install CWM. Apparently the CWM image is corrupt. The CWM ROM Manager Premium is still on my desktop but it can't do any sort of recovery because if I bring it up and choose "_install .zip from SDCard" it reboots into recovery mode and can't load the recovery image either. Does anyone have any ideas? Taboonay 2.1 is Android 3.2 it has the xda ad hoc wifi patch in it (which has never been quite right) in my opinion. So I found a copy of the 3.1 wpa_supplicant file and installed it into the /system/bin folder using root explorer to set the permission correctly after renaming the one installed by Taboonay to wpa_supplicant.old and re-enabled Wifi. Still it would not connect. The only difference I could see was that it no longer could see ad hoc wifi networks but still would not connect to my infrastructure wifi although it could see it. This particular wpa_supplicant file that I went back to came from Acer 3.1 stock ROM and worked perfectly under 3.1. I'm basically out of business at this point with no network and no way to flash a new ROM or restore a backup. Does anyone have any idea what to do next. Has anyone else had wifi issues with Taboonay 2.1? I did see an update 2.1b for Taboonay 2.1, but I can't get into CWM to apply it. I might as well be totally bricked. I can connect to the tablet and have full access to the 2 SD cards via Windows and a USB cable, but I can't download Acer's Installation Recovery from the market from a Windows browser. I'm sure its not the router because 3 Windows 7 SP2 Computers can connect to it and so can my wireless HP printer. Everything seems to be a Catch 22. Help! Anyone had trouble with Wifi on Taboonay? Does anyone have any ideas or how to get out of this situation? Any suggestion would be appreciated.

Hey gradyzero sorry to see the trouble buddy but the tabooney 2.1b update is made for wifi updates issues and SU perm, im currently running tabooney 2.1b and full with new market and i have no issues. As far as the recovery have you tried new THORS 1.5 cwm can you try using adb to push recovery.img to the tablet, or maybe using terminal emulator theres a new 1.5 cwm update you can try doing that. just extract recovery img to internal sd and go into thors website "google it" and follow every step except for #3
good luck buddy if not hit me up side PM ill see what i can do atleast to try to get recovery back

I don't think I had restored the terminal program back yet let me check. The apk is something I haven't tried. Thanks for the suggestion. I have thor's 1.5 update on my SD card but not quite sure what use it can be until I can get the ability to connect to boot up in recovery. I'll go to his web site and read the instructions there again, overlooking step 3. I have read them once before but didn't have this problem so I just grabbed the download and planned to update it after the Taboonay flash. Figured it would just have to be redone after the flash anyway. Thank for you idea. I should be able get an .apk onto the SD from Windows and should be able to install it. Again, thanks much buddy. I'll post back to this thread what the outcome is.

Restoration of boot image doesn't resolve the problem.
Okay Crashpsycho I download an Acer Install Recovery apk and CWM Launcher 1.0.0.0 apk. Both appeared to install correctly. Acer Install Recovery came up and I was able to choose to install CWM 1.3.4 image. However, when I reboot into recovery I still stop at "Booting recovery kernel image". So reinstalleing the CWM 1.3.4 image that the Acer Install Recovery show as an option didn't fix anything. Any ideas about why recovery might stop when loading the kernel image? When it says "the Kernel Image" is it talking about the base Linux kernel? I seem to recall reading somewhere that Taboonay replaced the Linux kernel with its own version. Is that true? I thought maybe the recovery image was corrupt but assuming the Acer Install Recovery really did reinstall the recovery CWM 1.3.4 image as it said, then something else is wrong. I did manage to get a terminal program installed so I'll try your second suggestion to force the CWM 1.5 image using adb. If Taboonay really did replace the stock Linux kernel, I have no idea how to recover from that. I'm not quit sure exactly where a recovery image goes and so I suspect that adb will ask for the destination. Maybe I'm wrong but do you know? Does adb know automatically where to install a recovery image? If the Linux kernel has to be replaced then I could get bricked if Tabtoonay won't boot up because a different Linux kernel is installed. What is your thinking about all of this? This is getting heavy. Thanks again for your help. Anyone else that has any fresh ideas is encouraged to jump in here and post to this thread. I'll post back here with the results once I try to force the CWM 1.5 image.

Installing other kernel solved issues for me, using thor kernel 3.5

installing 1.5 use terminal emu, extract the recovery.img from zip folder and place on root of sd go to thors website tegraowners and follow all steps except #3 and that will force 1.5 to tablet. have you tried installing stock recovery image using the acer recovery app

So Sector51 are you telling me you had the same issue. Where booting into recovery locked at loading kernel image? I'll try your suggestion. If it doesn't require you to be able to boot into recovery which I can't. Thanks for the tip.

Crashpsycho, I just completed the terminal method you suggested and followed all the instructions except #3 wihch was a mount, if I remember correctly. I extracted the image file from Thor's 1.5 put it on my external SD by copying it from Windows and then went through Thor's instructions step by step. Recovery boot still hangs at loading kernel image. Thor actually says to install itsmagic into /data/local directory both in his adb push and in his terminal emu methodology. There is no copy of itsmagic in his distribution and I can't find such a file on my tablet. BTW, I also tried the adb push from Windows but the recovery image is pushed to the SDCard so I assume he intents for me to then boot into recovery and to install it. So that's not going to work unless I have itsmagic. The Windows adb method also pushes itsmagic out to the /data/local folder but I can't complete that part and I think it is critical to both methods. Any idea where I get this file? Google search returns nothing except that one entry has been removed due to copyright issues. I think that it is the key to installing from the SDcard. I remember seeing that file on my rooted 3.1 but apparently Taboonay removed it. Can you enlighten me on itsmagic? What is it? Where do I get it? I have currently installed the Stock USA 1.31.06_COM_GEN1 recovery in Acer Recovery but reboot into recovery still hangs at loading kernel image.
This is another side issue but do you know if it would be possible to install the Taboonay 2.1b manually. Is it an update zip or a ROM flash? I'm beginning to think that if I could get back my Wifi back I would just forget the recovery reboot as a last resort. I'm going to investigate what is involved in the kernel update suggested by Sector51. But basically I'm not doing anything else until I can fully complete thor's 1.5 update. Man, I've spent 3 entire days trying to resolve this. I'm going bonkers. It certainly gives me a bad taste for Taboonay that probably isn't deserved because I don't see other post about this particular issue. So please educated me on itsmagic and we'll go from there. Thanks dude for all you help.

I found a copy of itsmagic here on xda. Downloaded it and completly went through the terminal emu process exactly as posted on Thoor's Website for 1.5. Everything seemed to work this time including the execution of itsmagic which spit out a nasty message to Acer something about Its Magic. Acer why did you say the bootloader is locked when it isn't? So this tells me that everything should now be good. I rebooted into recovery and this time it acted a bit different. It still said loading boot kernel but then in about 30 seconds rebooted back to Taboonay automatically. So I'm stumped. Does anyone have and new ideas? BTW, the 1.5 recovery image has a date of 29 Feb 2008. Is that right?

Finally suceeded with 1.5 Recovery, Thanks
This message is specifically addressed to Crashpsycho and Sector51. After four attempts I was finally successful at getting Thor's 1.5 recovery booted. I immediately backed up the current version of Taboonay 2.1 and then applied the 2.1b update. Everything in term of recovery is now good. One problem, the update did not fix the the WiFi problem as I am still unable to connect via WiFi. But that's a totally different issue, which I can deal with. Meantime thank to both of you for generously taking you time to help me resolve this recovery boot problem. I would still like to know what I did wrong during the original ROM flash to Taboonay 2.1 to destroy itsmagic. As well as what I did wrong in my first 4 attempts at repairing the recovery. However, I won't dwell on that as I need to proceed on with working on the WiFi issue. Thanks a million to both of you for all your help and suggestions. You are both what makes xda a truly wonderful and unique place for lovers of mobile devices. I am a programer and web developer and I hope I can contribute eventually to the growing Android mania. I personally think it will eventually dominate the table and phone market, if it already hasn't done so retail wise. I'll return to lurker stats for a while and learn more about the SDK while I try to resolve the WiFi issue. One side note, I recently flashed my HTC HD2 phone from Window mobile 6.5 to Widows mobile 7.5. That involved the flashing of 3 ROMs and then upgrading the OS. It runs beautifully and was much more complicated than what should have been a relatively simple task of upgrading to Taboonay 2.1. I'm sure I missed some small detail that caused the problem with the Icona Tab. You guys helped me greatly and I hope to be able to return the favor at some point. So I consider this issue closed and the moderator should feel free to consider it resolve. xda is power to the people.
Final Note: The adb push from Windows was the last attempt and was apparently the one that successfully fixed everything. As a certified Unix Engineer and somewhat of a Linux expert I opted to use the terminal emulator technique since I knew the commands and what they were doing, but typing in a long stream of commands is always more prone to user error. My advice to anyone else with this problem is to install the Windows Android SDK and use adb push to update as it appears the most recent version takes care of most all the permission issues and is almost fool proof. Again thanks to you guys. The Problem is resolved. Mister Moderator consider this thread closed and resolved.

great job man atleast you got the recovery to work. i cant say much for the wifi issue or what happen to recovery i would say if anything the issue must have came from the wifi ad hoc patch/change but im not fully technically skilled to say that it really was but great job hope you get it back up and going

I am enbrased to admit this but I feel it only fair since so many people attempted to help me. I've search around and apparenty no one has run into this here yet, but it needs to be posted for future reference. Most all of my boot recovery issues took place while the tablet was docked in the Acer A500 docking station. When I have trouble in recovery mode, with the image loading message just hanging up, 100% of the time removing the tablet from the docking station resoves the problem. Just thought I should pass this on. I know it is stupid that I didn't realize this before now. If you are docked, don't boot into recovery' not even with1.5 installed. I have no idea why this is true, but it is. If you have the Acer docking station DO NOT BOOT IN TO RECOVERY WHILE DOCKED!

Open up Rom Manager and click "Fix Permissions" let it do its thing then restart. That worked for me.

can someone please help?

I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!

You can use fastboot to erase your current partitions then manually flash the 4.3 stock images.

I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.

chrisbo4 said:
I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.
Click to expand...
Click to collapse
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.

Rirere said:
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.
Click to expand...
Click to collapse
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.

chrisbo4 said:
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.
Click to expand...
Click to collapse
Install this through device manager.
http://d-h.st/kDu

Username invalid said:
Install this through device manager.
http://d-h.st/kDu
Click to expand...
Click to collapse
Okay, it's installed. I'm not sure what I should unzip though?

chrisbo4 said:
Okay, it's installed. I'm not sure what I should unzip though?
Click to expand...
Click to collapse
You can either flash stock images with fastboot or install TWRP then flash stock zip file.

chrisbo4 said:
I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!
Click to expand...
Click to collapse
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!

gunner1937 said:
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!
Click to expand...
Click to collapse
Thank you for the information, and I'm not offended at all. I spent most of last night reading, and attempting to get adb running on my computer. I experienced issues getting drivers installed, and the computer recognizing the device. Also, trying to find the directories... I'll keep searching to see if I can get this figured out. Thank you again!

Thanks to everyone for helping me through this problem. After a lot of searching, research, reading, and video tutorials, I flashed stock images to the N7 via fastboot. I always thought that adb and fastboot was way too advanced for me (and it probably still is), but at least I got the basics down. Thank you all again.

HELP: Rooting Essential PH-1 on android 9

Guys, I'm at my wits end here. I don't know what to do. And it's driving me crazy.
After saving for 3 months, I got a used Essential Ph-1 from craigslist (for sprint). It came with Android 9, and a February 5, 2019 security patch.
All I want to do is to root the phone. And I have tried everything in my power to get it to work. It just does not. I have unlocked the bootloader, I'm seeing the device in adb and fastboot, but unable to sideload, or flash anything. I've been following different threads on here and youtube looking for directions, but my phone will just not do it.
Can someone please help me? I will send my phone over to you and pay you to have it done. I've tried almost everything to do it, and nothing works. I've even tried to flash android 8 and 7, it still doesn't do it. Someone please help me. I don't know what more i can do. Any guidance is appreciated.

Can someone please help me? I don't know what more to do. Please.

Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?

goofball2k said:
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
Click to expand...
Click to collapse
No. I can't sideload or boot into anything other than the android 9

I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...

kt-Froggy said:
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
Click to expand...
Click to collapse
I tried that too. But it kept saying unable to unpack boot image | installation failed.
I tried it with the stock images from the Essential website, both the OTA and fastboot versions. I'm getting the error for both files.

I would suggest checking out the PH1 Dev telegram group https://t.me/EssentialPH1DEV . not only will you find pre rooted stock boot images along with ones with TWRP as well you will also find help flashing them if you need it. Hope this helps you out.

Thank you everyone for all your help. Special thanks to kt-Froggy. I got it to work. I had to change my usb port from 3 to 2 and i was able to get it to work!