I'm trying to install TWRP recovery on my essential phone. this is the guide i am using, though pretty much every guide i found follows the same commands:
https://android.gadgethacks.com/how-to/install-twrp-recovery-essential-ph-1-0187660/
The command to determine my current slot returned that i am on slot_b, and when i try to flash the twrp img to slot_a, it sits trying to write. it never crashes but doesn't get anywhere. nothing is happening either in the command prompt window or on the phone screen.
I'm not sure what the issue is. I've updated the android sdk to the newest version and confirmed that I'm using that version of fastboot. I've also updated essential's windows drivers for the device, and rebooted the bootloader several times.
EDIT: I have noticed that on the phone screen when in the bootloader, it says "SECURE BOOT - yes". i don't know if this is important, but when i ran "fastboot oem device-info" it said true for unlocked and unlocked-critical.
Ricx94 said:
I'm trying to install TWRP recovery on my essential phone. this is the guide i am using, though pretty much every guide i found follows the same commands:
https://android.gadgethacks.com/how-to/install-twrp-recovery-essential-ph-1-0187660/
The command to determine my current slot returned that i am on slot_b, and when i try to flash the twrp img to slot_a, it sits trying to write. it never crashes but doesn't get anywhere. nothing is happening either in the command prompt window or on the phone screen.
I'm not sure what the issue is. I've updated the android sdk to the newest version and confirmed that I'm using that version of fastboot. I've also updated essential's windows drivers for the device, and rebooted the bootloader several times.
EDIT: I have noticed that on the phone screen when in the bootloader, it says "SECURE BOOT - yes". i don't know if this is important, but when i ran "fastboot oem device-info" it said true for unlocked and unlocked-critical.
Click to expand...
Click to collapse
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
dirtyreturn said:
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
Click to expand...
Click to collapse
i do have the newest file. i even tried redownloading it thinking the file might have been corrupted.
i haven't gotten to the part where i would need a usb otg keyboard yet, though i have one for when i make it that far.
I would check out the PH1 Development Telegram Channel as if your on stock they have boot images with TWRP and root already added and then all you have to do is fastboot flash the patched image and you will have TWRP with working touch and root as well. Here is the link to the channel if your interested https://t.me/EssentialPH1DEV
dirtyreturn said:
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
Click to expand...
Click to collapse
robertbarber said:
I would check out the PH1 Development Telegram Channel as if your on stock they have boot images with TWRP and root already added and then all you have to do is fastboot flash the patched image and you will have TWRP with working touch and root as well. Here is the link to the channel if your interested https://t.me/EssentialPH1DEV
Click to expand...
Click to collapse
I'm not having issues with touch yet. haven't even made it far enough to know if I'm having an issue with touch in twrp...
I can't flash anything for some reason.
I'm stuck at "Sending 'boot_b' (48712 KB)" and nothing happens. every post I've seen says this should take less than 2 seconds but I've waited up to 10 minutes some tries and nothing happens. i need to restart the bootloader after trying this each time before it will let me try again.
Ricx94 said:
I'm not having issues with touch yet. haven't even made it far enough to know if I'm having an issue with touch in twrp...
I can't flash anything for some reason.
I'm stuck at "Sending 'boot_b' (48712 KB)" and nothing happens. every post I've seen says this should take less than 2 seconds but I've waited up to 10 minutes some tries and nothing happens. i need to restart the bootloader after trying this each time before it will let me try again.
Click to expand...
Click to collapse
Did you do the two unlock commands via fastboot? Firstly.?(not intending to dumb you down or anything)
Did you try with just - fastboot flash boot twrp.img ?
P.S. !! Definitely check out the posted telegram channel! Super helpful group of people.
dirtyreturn said:
Did you do the two unlock commands via fastboot? Firstly.?(not intending to dumb you down or anything)
Did you try with just - fastboot flash boot twrp.img ?
P.S. !! Definitely check out the posted telegram channel! Super helpful group of people.
Click to expand...
Click to collapse
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Ricx94 said:
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
Ricx94 said:
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Click to expand...
Click to collapse
Are you using cmd or power shell for Windows. What ports are you using,2.0 or 3.0 and which type of cord. A-c or c-c
Sent from my PH-1 using Tapatalk
dazeone said:
Are you using cmd or power shell for Windows. What ports are you using,2.0 or 3.0 and which type of cord. A-c or c-c
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I've tried both CMD and Powershell
my computer only has USB 3.0 and 3.1 ports, all type A, so I'm using USB A-C cables. the cables are both only USB 2.0.
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Ricx94 said:
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Click to expand...
Click to collapse
Sorry... I didn't read...
When you are stuck at waiting for device .. if you unplug... Run the command... And then plug in... It will sometimes take...
Why... I don't know
Sent from my PH-1 using Tapatalk
Ricx94 said:
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Click to expand...
Click to collapse
Nice to hear! Be sure to have the twrpinstaller.zip handy to flash after the ROM!! This preserves twrp.
rignfool said:
Sorry... I didn't read...
When you are stuck at waiting for device .. if you unplug... Run the command... And then plug in... It will sometimes take...
Why... I don't know
Click to expand...
Click to collapse
I need to send the command while the bootloader is restarting. It works consistently for me. Unplugging and repluging won't do it; only restarting bootloader. I honestly can't explain it but it's working great.
Ricx94 said:
I need to send the command while the bootloader is restarting. It works consistently for me. Unplugging and repluging won't do it; only restarting bootloader. I honestly can't explain it but it's working great.
Click to expand...
Click to collapse
HOLY CRAP THANK YOU
I've been going insane and this worked for whatever reason. You are awesome!
Zach Alt said:
HOLY CRAP THANK YOU
I've been going insane and this worked for whatever reason. You are awesome!
Click to expand...
Click to collapse
Glad i could be of service
Related
Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "ADB reboot loader" or ..."fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!
Rovon said:
Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!
Click to expand...
Click to collapse
Use Wugfresh's toolkit and press "return to stock"
rohan32 said:
Use Wugfresh's toolkit and press "return to stock"
Click to expand...
Click to collapse
"I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen. "
Here's an update:
I think I've made it worse ...
Nothing will boot now and it's currently locked. Any time I hit "Start" it says "Booting Failed"
My CMD now says; Error: Cannot Load "Bootloader Grouper-3.34.img"
I'm seriously lost. I've been working on this for about 6 hours now ....
Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??
markj338 said:
Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??
Click to expand...
Click to collapse
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"
Rovon said:
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"
Click to expand...
Click to collapse
Where does it say boot failed? On the device?
markj338 said:
Where does it say boot failed? On the device?
Click to expand...
Click to collapse
Yes. Top left hand corner.
Rovon said:
Yes. Top left hand corner.
Click to expand...
Click to collapse
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?
markj338 said:
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?
Click to expand...
Click to collapse
No I can't get into the recovery at all. When I turn on the device I don't even need to use the rocker keys to get into bootloader either. Actually my bootloader is a bit different now too. I have the 'Google' logo and at the top the regular options for Start, Recovery, Power Off, etc.
In simple terms: I can't even get to the animated splash screen anymore
Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.
Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app
Alkaloid said:
Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response.
I've followed the instructions in the file. From previous research, I've had these files. My device does communicate with Fastboot. When I give the command for Devices it gives me my serial. Also, when I ask it to reboot-bootloader in CMD it does.
My issue is when I get to "Fastboot flash bootloader-grouper-3.34.img". CMD states "Error: Cannot load bootloader-grouper-3.34.img"
I've followed the commands previous to that. (Erase boot, cache, recovery, system, userdata)
Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.
Click to expand...
Click to collapse
Yes my device is unlocked again, but I still can't get into recovery mode. It just tells me "Recovery Failed" in small text in the upper left hand corner of my N7.
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
For the love of God..stop using the toolkit from here on out.. learn how to use ADB and Fastboot so you can avoid these issues.
Sent from my Galaxy Nexus using Tapatalk 2
So you erased the recovery then wonder why you could not boot into recovery....
You flashed or tried to flash the bootloader. You already had the same bootloader installed and there was no need to do so to try and fix your issue.
You still don't know what you're doing and are back using the tool that lead you to this issues. A toolkit. Learn what you're doing and you wont face this type of silly issue again.
Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
I think you should reread this post and hit the thanks button of everyone who took the time to help you out of this mess - its good manners. Oh, and learn how to use adb & fastboot
Sent from my Nexus 7 using xda premium
Inaccessible boot loader :/
If you try to fastboot flash all you get nothing?
Sent from my Nexus 7 using xda app-developers app
---------
nvm you fixed it, good job
Don't use toolkits. Most people don't have a clue what the toolkit is actually doing so if something goes wrong they aren't in a good position
Its always nice to see threads like these where the N7 in the face of death but in the end with cutting edge medical technology it is brought back to life and healthy.
Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??
Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.
oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html
I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.
I have now spent the entire day trying to get this thing to work, and having used up all the help from xda, I am asking you guys for help. Here's my situation:
I am trying to install TWRP on my Zenfone Max Pro M1. So I followed all the guides available, and downloaded the drivers, unlock.bat, TWRP img etc and did what I have always done on all my phones.
My computer also recognizes the device when I try fastboot devices. But the second I try to fastboot flash recovery twrp.img, the phone goes onto a black screen with "Press any key to shut down" written on it. I have tried every combination out there, and I don't know what to do now.
Please help.
Did you unlock boot loader? After that press volume up and power button,then you can enter fastboot screen. After that use fastboot flash recovery twrp.img
I have same problem plz help
1. boot into fastboot.
2. make sure fastboot can see the device 'fastboot devices'
3. fastboot flash recovery twrp-xxx.img
4. boot into twrp.
Did that work?
chr0 said:
I have now spent the entire day trying to get this thing to work, and having used up all the help from xda, I am asking you guys for help. Here's my situation:
I am trying to install TWRP on my Zenfone Max Pro M1. So I followed all the guides available, and downloaded the drivers, unlock.bat, TWRP img etc and did what I have always done on all my phones.
My computer also recognizes the device when I try fastboot devices. But the second I try to fastboot flash recovery twrp.img, the phone goes onto a black screen with "Press any key to shut down" written on it. I have tried every combination out there, and I don't know what to do now.
Please help.
Click to expand...
Click to collapse
Did you find any solution to this problem?
Utsav_vats said:
Did you find any solution to this problem?
Click to expand...
Click to collapse
Yes. Use Powershell instead of the normal cmd
chr0 said:
Yes. Use Powershell instead of the normal cmd
Click to expand...
Click to collapse
No, you must have done something else too. I'm trying to use fastboot mode to flash the fastboot firmware using Asus Flash Tool but as soon as AFT detects the device, it goes all black with the screen saying" press any key to shut down". Did you installed any other drivers or used any other system to do it?
Utsav_vats said:
Did you find any solution to this problem?
Click to expand...
Click to collapse
Utsav_vats said:
No, you must have done something else too. I'm trying to use fastboot mode to flash the fastboot firmware using Asus Flash Tool but as soon as AFT detects the device, it goes all black with the screen saying" press any key to shut down". Did you installed any other drivers or used any other system to do it?
Click to expand...
Click to collapse
Nope. Just used Powershell to execute the bat file and then push TWRP.
CMD wasn't working for me.
So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?
Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
emiljano539 said:
Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
Click to expand...
Click to collapse
I can't boot into recovery, the error message pops up on the screen
lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
You have to boot to twrp from the bootloder screen.
Use this recovery to boot from pc and never Flash twrp on pie.
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
lvnatic said:
So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?
Click to expand...
Click to collapse
Again unlock boot loader.
lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"
emiljano539 said:
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"
Click to expand...
Click to collapse
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.
lvnatic said:
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.
Click to expand...
Click to collapse
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?
emiljano539 said:
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?
Click to expand...
Click to collapse
Yes, I also have a redmi note 5 Pro and a mipad 4 and both work well with ADB.
Try flashint stock on EDL mode.
Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!
Thanks for the Solution
Inferi0r said:
Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!
Click to expand...
Click to collapse
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.
yagya said:
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.
Click to expand...
Click to collapse
Thanks for this. This happened to me two weeks ago, had to completely flash stock rom and begin from zero. Hopefully others will see this and avoid starting fresh.
I have been on a journey trying to go back to my T-Mobile OnePlus 6T back as my daily driver but the official updates killed the device for me. I have been successful in flashing it to the international version and now the device is on A9. I am trying to get it updated to A10 but in order do that (does not take OTA updates or can not flash within the updates app) I have to flash in recovery. Right now it is on stock recovery so I am trying to flash TWRP.
The problem is now that everytime I run the command " fastboot boot IMAGENAME.img" the phone restarts (as expected) and boots into fastboot but stays stuck in the Fastboot Mode screen.
I tried different TWRP images (older and the most current version per https://dl.twrp.me/fajita/ ) but I keep getting stuck in the Fastboot Mode screen. The last thing I was able to do without issues was unlock bootloader using fastboot.
I just need to be able to flash TWRP on the phone so I can still the final stock image so I can go back to using it as my DD.
EDIT: Disregard everything I fixed it. mods, please delete thread.
EDITR 2: Disregard that last edit lol Yeah I still need help. I am now tryingto flash twrp on a second 6T and the issue described above still applies.
You can try this version. Also try unplugging the USB after it reboots. You aren't getting any crash dump screen? So it should be working.
Brettroth said:
You can try this version. Also try unplugging the USB after it reboots. You aren't getting any crash dump screen? So it should be working.
Click to expand...
Click to collapse
Tried your image and still same result. I am running following command
Code:
fastboot boot TWRP-3.6.1_11-OP6xT.img
The command window outputs the following
Code:
Sending 'boot.img' (34964 KB) OKAY [ 0.747s]
Booting OKAY [ 0.092s]
Finished. Total time: 0.860s
The phone then reboots into Fastboot Mode logo and stays stuck there. I even tried unplugging the USB after it reboots as well.
I even tried using the flash command instead of boot but no success.
How about fastboot boot recovery? Should be able to get into recovery somehow. Doing fastboot flash of twrp will mess up your boot partition but either way you still should be able to get into recovery somehow. There is the msm recovery tool you can use as last resort but it will relock your bootloader
Actually fastboot doesn't let you use boot recovery command I don't think. Only adb. But once you are in fastboot can't you choose to reboot recovery with volume keys?
Brettroth said:
How about fastboot boot recovery? Should be able to get into recovery somehow. Doing fastboot flash of twrp will mess up your boot partition but either way you still should be able to get into recovery somehow. There is the msm recovery tool you can use as last resort but it will relock your bootloader
Click to expand...
Click to collapse
I tried doing fastboot boot recovery but i get following error
Code:
fastboot: error: cannot load 'recovery': No such file or directory
Brettroth said:
Actually fastboot doesn't let you use boot recovery command I don't think. Only adb. But once you are in fastboot can't you choose to reboot recovery with volume keys?
Click to expand...
Click to collapse
When I am in fastboot mode, yes I can choose recovery but it takes me to the stock recovery. I do not have a option to flash any zip files there
Maybe you need a twrp for Android 9 since that's what you are on. But fastboot boot twrp should just take you there. Either have to find one that works or go msm route. Maybe windows not reading it correctly also. You using CMD or PowerShell?
Brettroth said:
Maybe you need a twrp for Android 9 since that's what you are on. But fastboot boot twrp should just take you there. Either have to find one that works or go msm route. Maybe windows not reading it correctly also. You using CMD or PowerShell?
Click to expand...
Click to collapse
I tried both CMD and PowerShell. I am going to try a A9 version of twrp
EDIT: I am using twrp-3.6.1_9-0-fajita.img (which I assume is for A9) and still get the same result. Even tried a different usb port.. not sure what i could be missing. I also did the instructions as advised straight from twrp's website.
smartinez832 said:
I tried both CMD and PowerShell. I am going to try a A9 version of twrp
EDIT: I am using twrp-3.6.1_9-0-fajita.img (which I assume is for A9) and still get the same result. Even tried a different usb port.. not sure what i could be missing. I also did the instructions as advised straight from twrp's website.
Click to expand...
Click to collapse
I don't know bud. I guess msm tool is the way to go then
Curious did you have the twrp file in same folder as adb and fastboot?
smartinez832 said:
I have been on a journey trying to go back to my T-Mobile OnePlus 6T back as my daily driver but the official updates killed the device for me. I have been successful in flashing it to the international version and now the device is on A9. I am trying to get it updated to A10 but in order do that (does not take OTA updates or can not flash within the updates app) I have to flash in recovery. Right now it is on stock recovery so I am trying to flash TWRP.
The problem is now that everytime I run the command " fastboot boot IMAGENAME.img" the phone restarts (as expected) and boots into fastboot but stays stuck in the Fastboot Mode screen.
I tried different TWRP images (older and the most current version per https://dl.twrp.me/fajita/ ) but I keep getting stuck in the Fastboot Mode screen. The last thing I was able to do without issues was unlock bootloader using fastboot.
I just need to be able to flash TWRP on the phone so I can still the final stock image so I can go back to using it as my DD.
EDIT: Disregard everything I fixed it. mods, please delete thread.
EDITR 2: Disregard that last edit lol Yeah I still need help. I am now tryingto flash twrp on a second 6T and the issue described above still applies.
Click to expand...
Click to collapse
I'm having same issue with fajita (OnePlus 6T) you found any solution if yes then please give some reply