Related
Hey guys, I've been trying out ROMs for the past couple weeks and finally decided I wanted to replace my stock ROM with the energy rom to save space. I wiped all files from my stock ROM and then tried to flash the energy rom. I got an error so decided just to leave it for another day and created a second partition for the energy rom. Forgetting to flash my recovery back to my stock slot, I booted in to the energy rom. Now my recovery buttons don't work, probably due to the fact that they were installed on the stock rom. I don't have any way of getting in to the recovery and that kind of worries me. I've been reading up on fastboot, but don't know were to be begin or get ahold of rsdlite since all of the links send me to spam. Any help would be greatly appreciated!
I am currently using Safestrap 3.1.2 and do have a backup image of my stock ROM on my external SD card (at least I was smart enough to remember that).
Figured it out
Figured it out! Just in case anybody else has this problem, use RSD to fastboot the stock image to your phone. I know everything I read was talking about this, but I couldn't find detailed instructions anywhere. Most time consuming part for me was editing the xml file due to "oem" command lines that weren't recongnizable. There is a fixed xml file on droidrazr forums for those who need it!
Please help same issue
bgregs514 said:
Figured it out! Just in case anybody else has this problem, use RSD to fastboot the stock image to your phone. I know everything I read was talking about this, but I couldn't find detailed instructions anywhere. Most time consuming part for me was editing the xml file due to "oem" command lines that weren't recongnizable. There is a fixed xml file on droidrazr forums for those who need it!
Click to expand...
Click to collapse
PLEASE HELP ME
I am in the same trouble you were in here is my thread.
Hi all, i'm new to Android Phones, so i started a few days with this phone. But now i think i've done a big mistake, i tried to erase everything from the phone, in a hope to "restore" to the factory state. Instead, i think i've deleted everything from the phone, and now, it only says "Your device is booting now..." and it doesn't boot. It's unlocked and rooted, i've deleted it from the TWRP menu.
So, is there anything that i can do, to restore it back? The model i think it's the VNS-L31, i'm downloading a firmware from the L21, can it be replaced or something like that? Thankx in advance.
*Edit* I found stock rom for my phone here in the fórum, but it says i need to have stock recovery but i have the TWRP recovery. Is there any way that i can do it, with that recovery?
*Edit 2* In Erecovery, when i try to download it says "Getting package info failed"
First of all... Why don't you have a backup in TWRP? ALWAYS back up your stuff before doing ANYTHING in TWRP.
Second: there is an option for factory reset within the EMUI system itself. Absolutely no need to mess around in TWRP for something like that. Of course you can "factory reset" in TWRP but this can also wipe your system which then requires you to flash something.
To your problem:
Since I luckily was not forced to flash a stock firmware yet, some more information would be nice.
In which format does the firmware come (link to where you downloaded it)? TWRP can handle .zip files. So if it comes as a .zip file, you can try flashing it through TWRP (really depends on what you downloaded!)
If you only need stock recovery, try accessing TWRP with your phone plugged into a PC.
This way it normally fires up the stock eRecovery.
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
iDeadSmack said:
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
Click to expand...
Click to collapse
Hmm maybe best way is to send the user that made it work a PM and maybe he can provide you a guide on how to do it.
And maybe he or you can then provide a guide here on how to do it.
This device is rather new and the forum is building up so there is a lot of work to do and a lot of things have to be worked around.
Hope you can fix it, like I said, I cannot really help you properly since I never had the problem and therefore do not really understand what's happening on your device.
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
iDeadSmack said:
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
Click to expand...
Click to collapse
Could you help me with this problem i have the same problem on Huawei l-21 ??
Always have a backup of your fresh system on TWRP. Then whatever happen just restore it whenever you think you messed up your device and you should be fine ALWAYS.
Preamble
Hello, all.
Soooo I've never posted on this forum before. I've mainly leeched the invaluable info for my personal gain. I'm sure many a googler has come here trying to figure out how to root their phone. And I'm sure many a "swimmer" in Schitz Creek has come here via Google to figure out how to save their device from what had been perceived as an upgrade. I'm speaking, of course, of trying to root/unlock a phone and finding said phone "bricked".
Well, it’s time to give back.
Because yesterday, I was neck deep in Schitz Creek. After a series of dumb decisions and a lack of knowledge, I bricked the phone I’d bought for my wife’s birthday. I was just trying to be able to delete the Asus bloatware and install titanium backup and greenify. By the way, since when did Facebook become a system app? How is this a thing? Anyways, my wife deserves better battery life. And it’s fun to feel like Cyber MacGuyver by rooting a phone. But the situation went awry. My wife kept telling me that everything was going to be alright, but I know the limitations of my knowledge.
Brief aside: I'm decently computer/phone savvy, but I would, in no way, consider myself an advanced user. Sure, to my family, I'm a computer wizard. But that doesn't mean a whole lot. To them, opening up a command prompt in Windows is seen as an act of magic. And I haven't had my planeswalker spark yet. However, I have successfully rooted, and in most cases unlocked the bootloader, for several phones (HTC desire, Galaxy S3 [three different models over three years], Asus Zenfone 5, LG G4 [once pre-motherboard-death and once post (after a downgrade)], and now the ZE552KL). So I know how to at least fumble my way around adb, fastboot, odin, and various recoveries. As long as you’re at this level, or willing to learn, then you should be able to follow these instructions. End aside.
Mistakes not to make
Let’s get down to brass tacks. I made two big mistakes that you shouldn’t make. Both mistakes stemmed from the basic mistake of using a root method other than this one: https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524
The problem with not using this EXACT method is that some of the files/programs which you need to use have specific versions which will ensure an easypeasy root. Honestly, if you properly follow the instructions in the above post, you will most likely not run into any problems. The only addition I can make is that instead of steps 6 and 7, you might find it easier to install SuperSU.zip through TWRP instead of pushing and sideloading.
Mistake 1: Not using the proper TWRP file and SuperSU file
For some reason, there are multiple versions of these files. Your SuperSU file should be 4.8MB. Using the wrong SuperSU will break the dm-verity. Your TWRP should NOT be the latest experimental version. It should be the one from November or earlier of 2016. Using the wrong TWRP will leave you unable to use the touchscreen. Trust me. I know from experience.
Mistake 2: KEEP TWRP READ ONLY
Disabling read only has no current benefits. It will just break the dm-verity. Your device will still be able to be written to if you keep TWRP read only. I have no idea why it’s called “read only”.
How to unbrick the phone
I’m sure some of you skipped straight to here. While I can’t blame you, please at least read the above paragraph. It will help you.
First I will describe the situation the phone was in, and then I will explain how I saved it. Before I continue, I want to give a big shout out to Niemer. Without their helpful post, I would’ve had no idea what to do. Thanks!
Situation the phone was in
--TWRP could not be used because the touchscreen wasn’t working.
--The dm-verity was messed up (i.e. “not started in enforcing mode").
Before you look at the solutions, make sure that your phone shows up in the windows device manager as an ADB device/ASUS ADB device/ADB composite device/etc. no matter which step you’re in. Google it to figure out how if you don’t already know.
The solution
Part 1 - Create and flash a system image which will restore your dm-verity
step 1. download the latest system “update” from the asus drivers website. I have a WW version of the phone, so I downloaded “WW_V13.20.10.152”. It’s a 1.76GB file, so be patient. I haven’t tested this method with other versions of the phone, but they should work in theory.
step 2. go into the updater script file (META_INF → com → google → android → updater-script). Open it with notepad ++.
step 3. delete from the beginning of the file up until the line “ui_print("Target: asus/WW_Phone/ASUS_Z012D:6.0.1/MMB29P/13.20.10.152-20161222:user/release-keys");”
The code that you are deleting checks to make sure that your phone is the proper model. But there is a good chance that it will mistakenly identify your phone as a phony. So we need to get rid of this code.
step 4. save the updater-script file
step 5. create a copy of the modified system update zip file. You should now have two 1.76GB files (or maybe slightly different if your phone is a CN, JP, or other model. Once again, I have a WW version of the phone). Name one of the files “realupdate.zip” and name the other “dmsaver.zip”. The names aren’t actually important.
step 6. enter dmsaver.zip. delete these four files: file_contexts, system.new.dat, system.patch.dat, and system.transfer.list. Exit out of the file. It should now be about 60MB.
step 7. turn on your ZE552KL and enter fastboot mode
step 8. in a cmd screen from your main folder (i.e. the one with adb, fastboot, and all the other files, including the ones you just created), type in the command “fastboot flash system dmsaver.zip”
step 9. if successful, you have just restored the dm-verity. You should now no longer get that sinister red text which has been ruining all your fun.
Part 2 - Install a proper version of TWRP
(This is only important if your version of TWRP won’t let you do anything because you can’t use your touch screen)
Download the version of TWRP that is included in the how-to-root post I linked to above. Also, you can download the oldest version (NOT the newest) from a sharing website which is linked to in a post on the ASUS website. It’s not in english though. Flash it to your phone in fastboot mode using the “fastboot flash recovery” command. Make sure you turn your phone off before turning it back on, or your recovery might not activate correctly.
Part 3 - Install a new version of your system.
Go into TWRP and install the zip file “realupdate.zip” that you created in Part 1 - step 5.
Part 4 - Root your phone
Follow the instructions in the link I posted earlier. It comes from this website, so you know it’s good. This time, though, you probably don’t need to unlock the bootloader
Part 5 - Breathe a sigh of relief
Parting words
I really hope this guide can be of assistance to you. The full procedure for fixing “my” phone wasn’t really recorded anywhere (although once again, big shout out to Niemer for their post). I went through hundreds of iterations of seemingly random fastboot, recovery, and adb actions before everything worked out. Because of this, I feel quite fortunate to have saved the phone, and I really wanted to give back. This community has been super helpful to me over the last seven years, and this is my chance to reciprocate. I sincerely hope that this post will help you.
I hope I didn’t forget anything. I have a sneaking suspicion that I did. In any event, if you have any questions, please post them, and I’ll try to be of assistance. Happy rooting!
thank you man but i start Part1 step8 "fastboot flash system dmsaver.zip" it's successful then i go into TWRP and install the zip file “realupdate.zip” dm-verity show again.
Thank again.
Raw firmware
I have the same issue. My phone was branded "tim italy". When i bought it, I flashed the WW version via asus flash tool, and I'm currently able to update till the last M version, which is the ......152.
If i try to update to Android N, my phone will not boot, giving me the corruption message and shutting down after 10 seconds. I also tried to perform the dm restore procedure; the dm error disappeared but the system is stuck on the Asus boot screen
I believe that the only solution is to flash a Nougat RAW firmware via asus Flash tool. Does Anyone have a download link for the N version ?
thank you, you helped me, now im on N
I guess the version matters then. So be careful with which firmware you download/install. If anyone has success with other versions, please share how you did it
I am stuck on Step 8. i put the 2 zips in where my adb and fastboot is located, and then proceed to type 'fastboot flash system...' and then it wont let me flash, any help?
Device Locked
When I flash the dmsaver.zip, receive the error "FAILED (remote: not allowed in locked state)". Apparently this with the bootloader locked, but I already unlocked before. Someone can help me unlock the bootloader again?
Further hyperlinks & solution ideas
Check out my solution and Ideas in those in links I posted in this thread at 4th of septembre 2017:
https://forum.xda-developers.com/ze...-zenfone-3-zoom-ze553kl-t3657239#post73661437
The hyperlinks in my post might also be useful, I hope.
Would be glad about your feedback, if it helped! :good:
how do you update the script file ..can u just post the file that u made somehow or email it or attach it to a message?
cant get it to work followed the instructions still getinf error code 7 trying to install lineage os
If you have lineage OS version not is a zip file but all the images (boot.img, system.img, ...) then you could try to flash the images through ADB...
if someone have the no verity issue, can you try a method for me please?
it consists on:
re-flash the rom kernel via fastboot
and run:
Code:
fastboot oem reset-dm-verity
Followed all the steps and twrp still has no touch function.
Tried all different twrp versions.
OS Version is a key
Hi everybody that has the same issue, I hope you read that so you can fix your problem.
So what I did was downloading old version of OS that autor mentioned "WW-13.20.10.152". It is necessary to download this version even if there are more newer versions. Then follow tutorial and you should be fine.
So again, thanks OP for posting this. You helped me a lot!
Hi there. I am a a bit of a root-moron and have bricked my brand new Oneplus 6T while rooting it. Now I am stuck in a bootloop that ONLY cycles through the fastboot.
I can no longer enter into recovery mode from fastboot.
I can not use the MSM Download tool because the phone will not go into MSM Mode. Whenever I connect to the USB the phone automatically “wakes up” and immediately goes into fastboot.
When I hold the power button + volume up it just cycles through all the fastboot options and when it does eventually power down / screen goes black, it immediately powers back up and does the exact same thing.
So I simply cant get into MSM mode or recovery mode. I don’t know what to do and fear that the phone may be totally f#cked.
I welcome assistance from anyone here who actually knows what they are doing vs me who knows close to nothing. Help please!
OP6TNewb said:
Hi there. I am a a bit of a root-moron and have bricked my brand new Oneplus 6T while rooting it. Now I am stuck in a bootloop that ONLY cycles through the fastboot.
I can no longer enter into recovery mode from fastboot.
I can not use the MSM Download tool because the phone will not go into MSM Mode. Whenever I connect to the USB the phone automatically “wakes up” and immediately goes into fastboot.
When I hold the power button + volume up it just cycles through all the fastboot options and when it does eventually power down / screen goes black, it immediately powers back up and does the exact same thing.
So I simply cant get into MSM mode or recovery mode. I don’t know what to do and fear that the phone may be totally f#cked.
I welcome assistance from anyone here who actually knows what they are doing vs me who knows close to nothing. Help please!
Click to expand...
Click to collapse
First question, what exactly did you try to flash so we can get you the correct help on what to do from here.
Problem SOLVED!!!
justibasa said:
First question, what exactly did you try to flash so we can get you the correct help on what to do from here.
Click to expand...
Click to collapse
Thanks for your follow up.
Just want to let you now that I fixed it using the Stock Fastboot tool posted here
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
I just did exactly as instructed; my phone was already stuck in fastboot so I plugged to my PC and ran the flash-all.bat file. I really didn't think it would work because the phone did not seem to respond or do anything. I went to the toilet, came back and it was reset to factory!!!! Amazing.
Thank you so much @mauronofrio for posting this amazing tool. You saved my bricked phone! I sent you a donation for your assistance. Thanks again.
Just for future reference, as long as you can get this phone into fastboot, you should be fine. For now that's where all the flashing happens until we get a custom recovery.
But I'm glad to hear you fixed it lol
Can I just point out how bad*** of a "newb" the OP is. Dude signs up to XDA, literally makes his account name "OP6TNewb" then proceeds to give zero f**** and immediately jumps into flashing his brand new phone (as we all did once!). THEN he fixes the issue on his own using a tool he found by SEARCHING and THEN HE DONATED TO THE DEV WHO CREATED THE TOOL!!!!!
Kudos to you @OP6TNewb. All "newbs" should aspire to be like you.
Pain-N-Panic said:
Can I just point out how bad*** of a "newb" the OP is. Dude signs up to XDA, literally makes his account name "OP6TNewb" then proceeds to give zero f**** and immediately jumps into flashing his brand new phone (as we all did once!). THEN he fixes the issue on his own using a tool he found by SEARCHING and THEN HE DONATED TO THE DEV WHO CREATED THE TOOL!!!!!
Kudos to you @OP6TNewb. All "newbs" should aspire to be like you.
Click to expand...
Click to collapse
Thank you for the kind words. Donating was an easy choice because the tool saved me $650. If a guy in my situation doesn't stand up and donate to rewards you guys then who will???
Thanks again to @mauronofrio for the amazing tool and thank you to this community for allowing newbs like me to somewhat safely explore the world of android rooting & modifications.
OP6TNewb said:
Thank you for the kind words. Donating was an easy choice because the tool saved me $650. If a guy in my situation doesn't stand up and donate to rewards you guys then who will???
Thanks again to @mauronofrio for the amazing tool and thank you to this community for allowing newbs like me to somewhat safely explore the world of android rooting & modifications.
Click to expand...
Click to collapse
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Pain-N-Panic said:
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Click to expand...
Click to collapse
They probably have gone off to brag to their friends about what happened. Lol
I, too, am curious about what he did. It's been so long since I first began tinkering, but certainly remember some times I goofed.
Sent from my ONEPLUS A6013 using Tapatalk
Pain-N-Panic said:
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Click to expand...
Click to collapse
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
OP6TNewb said:
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
Click to expand...
Click to collapse
I forgot to mention one thing which may also be the reason. Initially, before using Adam Conways instructions, I started with the steps on High on Android (Max Lee) for the OP6 but on their download page, I mistakenly downloaded the twrp zip for the 5T and I flashed it. This initially cause the device to brick but I got it back into fastboot and into recovery and thats when I flashed the OTHER twrp file above. After I did this, I could no longer get into recover and was stuck in fastboot only.
So you can see that I made multiple errrors and I am not sure which one lead to what. Thank goodness OnePlus is friendly to rooting so I could save the phone!
OP6TNewb said:
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
Click to expand...
Click to collapse
Ah, I see. Looks like you flashed a kernel zip instead.
Im not a noob, but have been so out of practice with the latest Android ROMS and flashing and the changes in the partition arrangements. I managed to soft brick my phone as well and this post totally saved the day! Mauronofrio totally deserves a donation and I also gave one.
Thanks XDA! This place has saved me many times and helped me get the most of all my Android devices!
Hey guys. i am also no noob in flashing/rooting my devices.
Don thishundres of times.
Today my OP6T has shown an Magisk update (before it was 21.4 + Magisk Manager) and now it showed the popup to update -> done and error "bad image format" (i think for the kernel). Rebooted and now i am stuck in the same fastboot bootloop.
Tried to boot up TWRP with "fastboot boot tmrp.img" sadly it doesnt boot.
Any hints how i can recover my phone without wiping everything?
maybe @mauronofrio has an idea?
thx a lot
Other users facing the same issue with magisk 22, see here: https://forum.xda-developers.com/t/...oot-roms-for-oneplus-6t.3862516/post-84553217
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!