Database Users

[RECOVERY]14/07/14[UNLOCK BL][ROOT][TWRPv2.7.1.0 V4 RELEASED!!][NVIDIA OTA SUPPORTED]

****DISCLAIMER****
I am not responsible if you device decides to soft brick/ hardbrick or flys out the window
Recovery Installation Instructions:
1. unlock bootloader. (Hold volume up and power button, using terminal type in 'fastboot oem unlock', follow on screen instructions, (***WARNING THIS WILL WIPE DATA PARTITION***)
2. While in bootloader type 'fastboot flash recovery recovery.img'
3. select boot into recovery!!
Recovery Access:
Access recovery in pc via terminal/cmd
Adb reboot recovery
Or within the device...
Terminal emulator
Su
Reboot recovery
Or download an app from playstore that will do the work and reboot into recovery...
TWRP Version 2.7.1.0 Released:
Fully Working
Current issues list:
0 Issues
How to report an issue:
Message me with the a detailed description of the issue.
Provide a log.
Issues reported without a log will be ignored.
Download Link: http://d-h.st/cqQ
Source: https://github.com/omnirom/android_bootable_recovery
Release Changelog:
V1:
- TWRP booting
- graphics fixed but touchscreen not working
V2:
- Touchscreen fixed
- USB Mounts fixed
- software keys fixed.
V3:
- Improve read and write speeds on both internal and external storage. (TWRP method of calculating backup, MB/s seems inaccurate, jumps around way too much) but backup is very very fast!
- Improve graphical user interface speed, very very smooth!
- When not using TWRP, lp-core (super battery saving core) will be active and used as its suppose to.
- Drastically reduce TWRP loading times.
V4:
- TWRP Updated to latest source, includes better method of calculating backup and restore (now shows files and percentage complete, also supports colour text etc etc)
- Updated recovery kernel so backup and restore shall be faster
- Fixed 180 degree upside down recovery, now shows correctly
- TWRP now supports Nvidia OTA (NOTE: Installing nvidias OTA on a modified system may provide FC, DO NOT INSTALL IF YOU HAVE XPOSED INSTALLED)
CWM has been discontinued as it is not fully functioning while TWRP is and has much more, advanced features.

Unlocking Bootloader & Rooting
the new rom 4.3 should not be difficult... Now that we have recovery...
Unlocking bootloader
1. Unlock the bootloader
Access bootloader by either from poweroff holding volume down and power keys... Or enable USB debugging via pc enter adb shell reboot bootloader
Once at bootloader type in terminal/cmd fastboot oem unlock and follow intructions till the end...
WARNING DEVICE WILL WIPE USERDATA(EVERYTHING)
Device is now unlocked
2. install recovery - steps above
3. Download supersu.zip from chainfires website
Install via recovery... (Android terminal, su, reboot recovery)
Navigate to Supersu.zip via volume up, down keys and powerbutton - http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Root achieved yay
More indepth tutorial incoming

Shaky156 said:
would really help if everyone could but high level moderators for tegra note device thread
Click to expand...
Click to collapse
Thanks Shaky for the efforts.
I agree with Tegra having its own thread, especially since so many OEM outlets will be selling this tablet and other iterations, like the coming Phone version of the Tegra 114i SoC.

e8hffff said:
Thanks Shaky for the efforts.
I agree with Tegra having its own thread, especially since so many OEM outlets will be selling this tablet and other iterations, like the coming Phone version of the Tegra 114i SoC.
Click to expand...
Click to collapse
Pm'd a high mod, has put the device on internal request list so dudes pls do pm mods and request, if you dont ask you dont get
V2 is compiling right now will test and upload after breakfast inshallah and CWM shall be functioning normal as in Image wont be flipped upside down anymore

Link to OTA 4.3 Tegra Note 4
http://forum.xda-developers.com/showthread.php?p=48866058#post48866058

Dpuble post delete pls

OP Updated with link to v2, although image is flipped so its sitting correctly, the device resolution is somewhat not set correctly so the CWM recovery looks out of shape a little but this doesnt affect the functionality of CWM
Also OP updated with link to OTA in zip file format fully factory... ENjoy

Double post delete pls

Bricked my device so cannot continue any further yet...

do you have the source for your CWM recovery. would love to have it so that development can continue. Thanks

Tomsgt said:
do you have the source for your CWM recovery. would love to have it so that development can continue. Thanks
Click to expand...
Click to collapse
Switching from CWM to TWRP for alot of reasons so will release source for TWRP, CWM source can be found in Cyanogenmod github. Also replied to your PM

http://d-h.st/eU9 TWRP v1 Recovery test

Shaky156 said:
http://d-h.st/eU9 TWRP v1 Recovery test
Click to expand...
Click to collapse
this is still CWM recovery you must have linked the wrong file. LOL

Tomsgt said:
this is still CWM recovery you must have linked the wrong file. LOL
Click to expand...
Click to collapse
That is weird...
fresh compile test here is another TWRP test: http://d-h.st/Y9u
fastboot flash recovery recovery.img
allot it to boot into your Android OS
adb reboot recovery, (TWRP should boot)

Shaky156 said:
That is weird...
fresh compile test here is another TWRP test: http://d-h.st/Y9u
fastboot flash recovery recovery.img
allot it to boot into your Android OS
adb reboot recovery, (TWRP should boot)
Click to expand...
Click to collapse
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot fl
ash recovery TWRP-2-recovery.img
target reported max download size of 641728512 bytes
sending 'recovery' (8384 KB)...
OKAY [ 0.311s]
writing 'recovery'...
FAILED (remote: (InvalidSize))
finished. total time: 0.335s
FAILED (remote: (InvalidSize)) looks like the recovery partition is pretty small. didnt notice it the first time I flashed it. witch is probably why I am still on CWM. Note Stock recovery is 8192KB but this one fails every time.

Tomsgt said:
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot fl
ash recovery TWRP-2-recovery.img
target reported max download size of 641728512 bytes
sending 'recovery' (8384 KB)...
OKAY [ 0.311s]
writing 'recovery'...
FAILED (remote: (InvalidSize))
finished. total time: 0.335s
FAILED (remote: (InvalidSize)) looks like the recovery partition is pretty small. didnt notice it the first time I flashed it. witch is probably why I am still on CWM. Note Stock recovery is 8192KB but this one fails every time.
Click to expand...
Click to collapse
I knew something wasnt right on your end since i did compile TWRP and was 100% sure I did. Will upload something soon

Shaky156 said:
I knew something wasnt right on your end since i did compile TWRP and was 100% sure I did. Will upload something soon
Click to expand...
Click to collapse
Yeah ut took me a couple tries to finally notice that LOL

Tomsgt said:
Yeah ut took me a couple tries to finally notice that LOL
Click to expand...
Click to collapse
Something isnt right, I need more than 1 tester to test TWRP on their device as it could be a user error,

Shaky156 said:
Something isnt right, I need more than 1 tester to test TWRP on their device as it could be a user error,
Click to expand...
Click to collapse
Guess i can be your second tester. Ill try this when i get home today. My bootloader is already unlocked and im rooted.
Edit: I dont even have CWM loaded so this will be fresh attempt strait to TWRP

BKO Overdrive said:
Guess i can be your second tester. Ill try this when i get home today. My bootloader is already unlocked and im rooted.
Edit: I dont even have CWM loaded so this will be fresh attempt strait to TWRP
Click to expand...
Click to collapse
Dont attempt yet... wait for another release of TWRP

Warning - XT1060 Blur_Version.212.55.26 blocks custom recoveries

Exactly as the title says ... after flashing this update, even if unlocked, you can no longer flash a custom recovery.
Fastboot will show a successful flash, e.g. :
mfastboot.exe flash recovery twrp-2.8.6.0-ghost.img
sending 'recovery' (9488 KB)...
OKAY [ 0.849s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.819s
Click to expand...
Click to collapse
But when you try to boot recovery, it's stock recovery.
This makes any attempt to flash a rom, regain root, etc. impossible.

And you are booting straight to recovery after flashing via volume down and then volume up to select not the power button?

_litz said:
Exactly as the title says ... after flashing this update, even if unlocked, you can no longer flash a custom recovery.
Fastboot will show a successful flash, e.g. :
But when you try to boot recovery, it's stock recovery.
This makes any attempt to flash a rom, regain root, etc. impossible.
Click to expand...
Click to collapse
After you flash TWRP, at the command prompt type:
fastboot reboot-bootloader
I can't remember where I read it but some people said they had to do that to get the custom recovery to stick.
THEN unplug your device from your computer and reboot into recovery by scrolling down with the volume down button to highlight recovery and then hitting the volume up button to select recovery.

Ok, figured this out ...
(was able to back down to the original 4.4.4 w/rsd-lite and regain TWRP ... to develop this process)
So ... the following can be done to upgrade to this new version, and retain TWRP (plus you have the new recovery later on for 5.1 when it comes along ...)
First, the presumption here is you are unlocked. If you are not, none of this will work.
Also, you will need RSD-Lite installed and operational.
Download :
https://dl.dropboxusercontent.com/u...RIZON_4.4.4_KXA21.12-L1.26-3_cid2_1FF.xml.zip
https://dl.dropboxusercontent.com/u...4.4.4_KXA21.12-L1.26-3/twrp-2.8.6.0-ghost.img
https://dl.dropboxusercontent.com/u/22067374/GHOST_VERIZON_4.4.4_KXA21.12-L1.26-3/servicefile.xml
Unpack the GHOST zip file, and overwrite the "servicefile.xml" in the unpacked folder w/the one you downloaded, then copy the twrp .img in there.
Fire up RSD-Lite, put your phone in fastboot, and apply this update by loading the servicefile.xml as the update.
It will update everything, installing the TWRP instead of the new stock recovery.
Note: you can delete the twrp line in servicefile.xml if you wish to retain your existing custom recovery.
When done, you should reboot, update, and be up and running with the new 4.4.4 and TWRP ... so easy path back to root via TWRP.

_litz said:
Ok, figured this out ...
Click to expand...
Click to collapse
I think all that needs to happen is after you flash TWRP - you don't boot into recovery. Instead, reboot into bootloader mode. This has been a problem from the beginning for some people with their MX13's and not a new thing. I don't think it has anything to do with the update. Some people have to reboot into bootloader after flashing TWRP in order to get it to stick for some reason.

@_litz Please understand that @JulesJam is correct... the proper way to flash a recovery is as follows...
Start the phone to the Fastboot AP/Bootoader menu
using moto's fastboot (aka mfastboot) exectue the following...
mfastboot flash recovery RecoveryYouWishToFlash.img
mfastboot reboot-bootloader
Then use the volume/power keys to enter recovery.
Once in the recovery, it is safe to Reboot the phone normally.
that mfastboot reboot-bootloader step has been crucial for getting the newly flashed recovery (3rd party OR Stock!) to "stick" on the phone.
Flashing with RSDLite is over kill.

You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.

_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
And you used volume up to enter recovery after flashing twrp? That is the most common problem I see.

_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
That is because you are pressing the power button when you should be pressing the volume up button.

Yep ... ain't my first rodeo ....
It flat out refused to take recovery.
I had to back it back down to the old 4.4.4 version, reflash TWRP, then I simply applied the whole RSD package (sans recovery) to re-upgrade it to the new 4.4.4.
Worked like a charm.
(Plus it gave me a chance to extract the fxz from the moto manager app)

Travisdroidx2 said:
And you used volume up to enter recovery after flashing twrp? That is the most common problem I see.
Click to expand...
Click to collapse
yes, that is what is happening.

See above ... this isn't my first time at this. Was not working as described.

_litz said:
See above ... this isn't my first time at this. Was not working as described.
Click to expand...
Click to collapse
Was not trying to insult your knowledge. That is a very common problem that many do. So I had to ask.

_litz said:
See above ... this isn't my first time at this. Was not working as described.
Click to expand...
Click to collapse
You needed to reboot into bootloader by typing fastboot reboot-bootloader after your flashed TWRP. THEN disconnect your phone from your computer and boot into recovery by using the volume down to highlight recovery and volume up to select recovery.
If you follow those instructions, you will flash TWRP fine. No need to go through that long drawn out process you came up with.

Probably should rename or delete this thread, since its fairly misleading.

Check in the /system partition for a file named recovery-from-boot.p or something similar. If that file is there it will reflash the stock recovery when you reboot, and I've seen it reflash when booting into recovery.

I just used the TWRP manager app from the Play store after reverting to stock recovery and installing the OTA. It worked perfectly the first time.
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager

_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
I'm curious as to what is different.. because the other day after flashing stock recovery back on my phone, taking the update to 212.166.3 KXA21.12-L1.26-3 which Verizon just pushed, I used those EXACT STEPS to put TWRP back on my phone and had no problems.

Beats me ... for me, it didn't work ...
So after I got things back onto the old 4.4.4 version, I put together the FXZ with the modified xml file, and simply re-updated, applying both the update, and TWRP, all in one go.
anyone else on old 4.4.4 can do the same thing if they wish, which was why I posted the links and the instructions.

not to bump this thread, but I had zero issues going from stock with 212.55.26 ota update installed and flashing twrp. it just worked like normal.
i would agree with @superkeest seems like this thread should get renamed.

Safe to reboot? axon7toolkit boot.img remote: unknown command

Hey everyone,
I am in the process of rooting my axon7 (B10) and need some quick advice
I unlocked the bootloader using this method: https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595
Then went on to install twrp using the axon7toolkit. steps 1 and 2 reported to be working correctly but during the twrp install this came up. (see attached)
okay so recovery flashed successfully, but something went wrong with reboot? why, how, there is no indication that the tool wrote anything to boot.img so I should be fine? Can I just boot to recovery manually and continue normally? Or should I be worried that something went wrong?
the phone is currently still in fastboot mode and responding. however I am super cautious and don't want to brick the phone because I didn't ask so I am keeping it in this state for now.
any help is much appreciated
Checking ADB\Fastboot Connectivity...
ADB device connected!
Rebooting to bootloader...
Checking Fastboot Connectivity...
Fastboot device connected!
Flashing TWRP...
target reported max download size of 536870912 bytes
sending 'recovery' (14452 KB)...
OKAY [ 0.484s]
writing 'recovery'...
OKAY [ 0.113s]
finished. total time: 0.601s
Booting TWRP...
downloading 'boot.img'...
OKAY [ 0.475s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.497s
Tap 'Keep read-only'" on startup!
Checking ADB Recovery Connectivity...
Checking ADB Recovery Connectivity...
Click to expand...
Click to collapse

fleity said:
Hey everyone,
I am in the process of rooting my axon7 (B10) and need some quick advice
I unlocked the bootloader using this method: https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595
Then went on to install twrp using the axon7toolkit. steps 1 and 2 reported to be working correctly but during the twrp install this came up. (see attached)
okay so recovery flashed successfully, but something went wrong with reboot? why, how, there is no indication that the tool wrote anything to boot.img so I should be fine? Can I just boot to recovery manually and continue normally? Or should I be worried that something went wrong?
the phone is currently still in fastboot mode and responding. however I am super cautious and don't want to brick the phone because I didn't ask so I am keeping it in this state for now.
any help is much appreciated
Click to expand...
Click to collapse
Why do you even use axon7toolkit? Use "fastboot flash recovery recovery.img" and you'll be able to avoid using the toolkit. It's finicky as hell.
Otherwise at least use EDL Tool...
Your boot image is untouched. Seemingly axon7toolkit does "fastboot boot recovery.img" which basically sends the recovery to RAM or something and makes the phone boot into that file instead of the actual boot.img.
If you are on Fastboot select "Recovery" from it and hit power. It will enter the recovery directly. This is important because if the phone boots, it will reinstall the stock one.
After you get into TWRP, FLASH MAGISK. This will let you retain TWRP.

Choose an username... said:
Why do you even use axon7toolkit? Use "fastboot flash recovery recovery.img" and you'll be able to avoid using the toolkit. It's finicky as hell.
Otherwise at least use EDL Tool...
Your boot image is untouched. Seemingly axon7toolkit does "fastboot boot recovery.img" which basically sends the recovery to RAM or something and makes the phone boot into that file instead of the actual boot.img.
If you are on Fastboot select "Recovery" from it and hit power. It will enter the recovery directly. This is important because if the phone boots, it will reinstall the stock one.
After you get into TWRP, FLASH MAGISK. This will let you retain TWRP.
Click to expand...
Click to collapse
yeah I don't know why it seemed like a good idea, it's a sticky post in the rom section... It's how I started and then wanted to stick to it somehow.
indeed booting into recovery works like a charm which is already pretty reassuring.
flashed magisk, twrp is not up to date (3.1.1.0), but system boots. thanks a bunch
I guess I'll update / flash the most current version of twrp via fastboot and then go on to flash lineage
again, thank you very much

fleity said:
yeah I don't know why it seemed like a good idea, it's a sticky post in the rom section... It's how I started and then wanted to stick to it somehow.
indeed booting into recovery works like a charm which is already pretty reassuring.
flashed magisk, twrp is not up to date (3.1.1.0), but system boots. thanks a bunch
I guess I'll update / flash the most current version of twrp via fastboot and then go on to flash lineage
again, thank you very much
Click to expand...
Click to collapse
Is your twrp installed as "Keep Read Only" or did you select "Swipe to Allow Modifications"?
After giving flash in the Magisk you gave wipe?
Thanks if you can respond.
Enviado de meu ZTE A2017 usando o Tapatalk

EwertonR19 said:
Is your twrp installed as "Keep Read Only" or did you select "Swipe to Allow Modifications"?
After giving flash in the Magisk you gave wipe?
Thanks if you can respond.
Enviado de meu ZTE A2017 usando o Tapatalk
Click to expand...
Click to collapse
If you're asking because you want to know:
-swipe to allow modifications is okay
-If you want to get rid of encryption, you have to FORMAT data (not wipe). You'll lose the internal storage. After that, flash magisk.
You can just flash it without formatting , but your storage will be encrypted, and you'll lose the internal storage if you ever change ROMs.

I swiped to allow modifications
I backed up everything I needed from the phone. I actually planned for removing everything to get a fresh setup.

Choose an username... said:
If you're asking because you want to know:
-swipe to allow modifications is okay
-If you want to get rid of encryption, you have to FORMAT data (not wipe). You'll lose the internal storage. After that, flash magisk.
You can just flash it without formatting , but your storage will be encrypted, and you'll lose the internal storage if you ever change ROMs.
Click to expand...
Click to collapse
So after installing twrp I format the Data partition and give flash in Magisk, correct?
I am afraid to enter bootloop because I have already done several procedures and in all the same thing happened. I hope everything will work out this time.

EwertonR19 said:
So after installing twrp I format the Data partition and give flash in Magisk, correct?
I am afraid to enter bootloop because I have already done several procedures and in all the same thing happened. I hope everything will work out this time.
Click to expand...
Click to collapse
yes

[SOLVED]Tried to update Magisk from app, stuck at Fastboot screen, TWRP may be gone

I fixed the problem by just booting into the LG Factory Reset menu, in order to get into TWRP. I hesitated to do that for a while because I had no way to verify TWRP was still on my device. After running out of options, I decided to just go for it. To my (and probably no one elses) surprise, it went straight into TWRP, where I was able to flash H91820s and Magisk 16.0 in the same TWRP session. Rebooted, everything was how it was except on a new version of Android. Root was retained.
Tried to update Magisk on my TMobile H918 from Magisk version 16.x using the app, and selected Direct Installation. The device is now stuck at the fastboot screen, and I cannot boot into recovery from adb.
Is there a way I can repair things? I am unsure exactly what got deleted/corrupted in the process of the update.
EDIT: When I try to boot into TWRP, I get this error:
fastboot: error: cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
and when I try to re-flash TWRP, I get this error:
fastboot flash recovery twrp.img
Sending 'recovery' (28928 KB) OKAY [ 0.764s]
Writing 'recovery' FAILED (remote: 'unknown command')
Finished. Total time: 0.827s
Click to expand...
Click to collapse

Can you get in Twrp with button combo? For me its while boot hold vol down and power then at lg logo release the power for a sec and re hold until the while screen and then select yes twice.
There is also download mode and reflashing twrp that way I believe...
Dont 100% me on that .

Mysticblaze347 said:
Can you get in Twrp with button combo? For me its while boot hold vol down and power then at lg logo release the power for a sec and re hold until the while screen and then select yes twice.
There is also download mode and reflashing twrp that way I believe...
Dont 100% me on that .
Click to expand...
Click to collapse
I tried to boot into recovery, but adb detected no recoveries on the system.
I don't want to do the System Format Yes Twice thing because I believe TWRP is gone. And I am unable to re-flash due to "no such command."
The recovery is unable to be written to the device.

124112 said:
I tried to boot into recovery, but adb detected no recoveries on the system.
I don't want to do the System Format Yes Twice thing because I believe TWRP is gone. And I am unable to re-flash due to "no such command."
The recovery is unable to be written to the device.
Click to expand...
Click to collapse
Is the phone in download mode ?
adb doesn't work in download mode
What does the command fastboot devices return?
Sent from my PH-1 using Tapatalk

Mysticblaze347 said:
Can you get in Twrp with button combo? For me its while boot hold vol down and power then at lg logo release the power for a sec and re hold until the while screen and then select yes twice.
There is also download mode and reflashing twrp that way I believe...
Dont 100% me on that .
Click to expand...
Click to collapse
clsA said:
Is the phone in download mode ?
adb doesn't work in download mode
What does the command fastboot devices return?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I fixed the problem by just booting into the LG Factory Reset menu, in order to get into TWRP. I hesitated to do that for a while because I had no way to verify TWRP was still on my device. After running out of options, I decided to just go for it. To my (and probably no one elses) surprise, it went straight into TWRP, where I was able to flash H91820s and Magisk 16.0 in the same TWRP session. Rebooted, everything was how it was except on a new version of Android. Root was retained.

124112 said:
I fixed the problem by just booting into the LG Factory Reset menu, in order to get into TWRP. I hesitated to do that for a while because I had no way to verify TWRP was still on my device. After running out of options, I decided to just go for it. To my (and probably no one elses) surprise, it went straight into TWRP, where I was able to flash H91820s and Magisk 16.0 in the same TWRP session. Rebooted, everything was how it was except on a new version of Android. Root was retained.
Click to expand...
Click to collapse
Glad it worked...happy new year

Trying to flash TWRP but no success (stuck on Fastboot mode)

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