Database Users

Yoga Tab 2 (830,1050,1380) - TWRP 2.8.7.0(6)

'what? lol'

1050F - All Good!
Thanks!

YamYam

ionioni said:
you tried to flash a partition from dnx mode
Click to expand...
Click to collapse
Doh... Been so confused lately....

workdowg said:
Doh...
Click to expand...
Click to collapse
maybe you should put that SMT AoL on a break... the YT2 one is almost forgotten.

ionioni said:
maybe you should put that SMT AoL on a break... the YT2 one is almost forgotten.
Click to expand...
Click to collapse
Probably... I had 3 or 4 more people interested... I posted the working MicroSD install files... But I do feel lonely...

Thanks brother, I will test in upcoming Saturday and will revert back.

a beginner's guide....tnx[emoji1] [emoji1]

@workdowg now that we have a permanent recovery does this mean we can start building cm and kernels? I am almost setup with my machine (just configuring Ubuntu). From what I have read on lenovo website is they messed something up with the charging and battery life in the last update

pug1 said:
@workdowg now that we have a permanent recovery does this mean we can start building cm and kernels? I am almost setup with my machine (just configuring Ubuntu). From what I have read on lenovo website is they messed something up with the charging and battery life in the last update
Click to expand...
Click to collapse
Since the bootloader is unlocked you may do what you wish. Permanent TWRP will make the job easier. Have at it!
As far as the current ROM from Lenovo.... It is really stable for me. I froze the usual suspects and I get about 3-4 days with 8-9hrs SOT. I don't game on this tablet and keep the brightness down to about 1/3.

updated: added compilation from 6.0 sources - TWRP 2.8.7.0(6)

ionioni said:
updated: added compilation from 6.0 sources - TWRP 2.8.7.6
Click to expand...
Click to collapse
Pretty... all good on the 1050F.

1050F (Latest LP OTA): I am able to flash it (bl is unlocked), but cannot access it after that. Stock recovery is still present... am I missing sth??

dtrail1 said:
1050F (Latest LP OTA): I am able to flash it (bl is unlocked), but cannot access it after that. Stock recovery is still present... am I missing sth??
Click to expand...
Click to collapse
it works in the 'live' mode? from dnx (PwrOn with both Vol pressed, screen shows 'fastboot starting...' message):
fastboot flash osloader bootx64.efi
fastboot boot twrp-1050f-b.img
you should also try to boot in the recovery right AFTER you flash it and if it goes twrp means that recovery from boot is still active on your build (and will write the recovery partition with a fresh image that he builds from the boot partition on each normal android start)
what is the OTA you're on?

ionioni said:
it works in the 'live' mode? from dnx (PwrOn with both Vol pressed, screen shows 'fastboot starting...' message):
fastboot flash osloader bootx64.efi
fastboot boot twrp-1050f-b.img
you should also try to boot in the recovery right AFTER you flash it and if it goes twrp means that recovery from boot is still active on your build (and will write the recovery partition with a fresh image that he builds from the boot partition on each normal android start)
Click to expand...
Click to collapse
Already figured it, but thx!! I forgot to FIRST boot it from DNX mode once, and then flash it permanently from fb mode. thx

I have followed each steps mentioned to flash perm. twrp recovery on my YOGA Tablet 2-830LC lollipop, unlocked bootloader; the process of flashing completes successfully yet I am unable to enter into recovery... When ever I try to enter into recovery it simply boots up normally... I have tried entering recovery by both hardware and software modes, but it fails... Kindly help me out of this mess...
Thank you

QuazIqbal said:
I have followed each steps mentioned to flash perm. twrp recovery on my YOGA Tablet 2-830LC lollipop, unlocked bootloader; the process of flashing completes successfully yet I am unable to enter into recovery... When ever I try to enter into recovery it simply boots up normally... I have tried entering recovery by both hardware and software modes, but it fails... Kindly help me out of this mess...
Thank you
Click to expand...
Click to collapse
while i don't know 100% whether it is working or not on your model and since those who download the files don't give their feedback...
try rebooting in recovery, when in normal android, send a adb reboot recovery or boot in fastboot mode and chose the RECOVERY as target with Volkeys and activate with Power button
check also that you flashed the correct img file (you did unzipped the file before flashing no? ) fastboot flash recovery twrp....img

ionioni said:
while i don't know 100% whether it is working or not on your model and since those who download the files don't give their feedback...
try rebooting in recovery, when in normal android, send a adb reboot recovery or boot in fastboot mode and chose the RECOVERY as target with Volkeys and activate with Power button
check also that you flashed the correct img file (you did unzipped the file before flashing no? ) fastboot flash recovery twrp....img
Click to expand...
Click to collapse
I tried all the ways including 'adb reboot recovery and also tried to enter recovery through droidboot but each time it simply rebooted without going into recovery.... I also tried the temp recovery, by these commands "fastboot flash osloader bootx64.efi" & "fastboot boot twrp-830f-b.img" in this case also it simply rebooted in to android os.
P. S. I am able to enter twrp recovery through social design recovery.

any 830 owner can confirm if it is working or not on his device?

QuazIqbal said:
I tried all the ways including 'adb reboot recovery and also tried to enter recovery through droidboot but each time it simply rebooted without going into recovery.... I also tried the temp recovery, by these commands "fastboot flash osloader bootx64.efi" & "fastboot boot twrp-830f-b.img" in this case also it simply rebooted in to android os.
P. S. I am able to enter twrp recovery through social design recovery.
Click to expand...
Click to collapse
1. when you are entering the above two commands are you in DNX mode? ('fastboot starting' on screen)
2. when you upgraded to Lollipop did you used the OTA update process or you just flashed a stock Lollipop rom?
3. boot to your normal Android OS and open Contacts and in the search contacts box enter ####0000# it will open a VersionInfo window, tell me what it says under BIOS version line
by these commands "fastboot flash osloader bootx64.efi" & "fastboot boot twrp-830f-b.img" in this case also it simply rebooted in to android os.
Click to expand...
Click to collapse
4. right after you entered the commands it rebooted (ie you heard the tab buzzing as if you power on from off state) or just continued and booted t Android?

Hard/soft brick

I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum

jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/

That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.

https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed

SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed

jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.

wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc

Was finally able to get into recovery, so all is well. Thanks for the help yall

OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?

gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc

My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!

katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?

I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.

katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.

Nokia 5 unable to install Recovery

So I gave my IMEI, serial number and $5 to someone on the internet, and in return I got an email attachment to flash to my phone. So I did, and it unlocked the bootloader. Strangely enough, now I'm getting a stupid yellow message that my device is unlocked and can't be trusted, and it's a bit of a roundabout way to get into bootloader or recovery. One ONLY works with buttons, the other ONLY with adb.
Ok, never mind, so I tried installing both the 3.1.1. and 3.2.1 of TWRP custom recovery, but I am unable to boot into it to make it stick. On top of that, my phone now says "encrypted"? WTF?
Clearly this latest incarnation of Nokia is a bunch of asswipes, offering us Sophie's choice instead of just unlocking the damn things from the start, so there's no point in asking them for help, but I'd expect members here would be able to help?
Any ideas how to proceed? Is there a factory ROM somewhere? This is 7.1.2. by the way, I'm not interested in updating. Come to think of it, I hate this so-called "progress" with convoluted "security" and whatnot. Just give me the damn phone and go away, Google+Nokia. Stick your "features" up ya clacker.

1. Okk first you jeed to go this link and download official recovery for nokia 5 running android 8.1 oreo
https://drive.google.com/file/d/1Cl1...w?usp=drivesdk
2. Rename it to twrp and give the command to flash the recovery.
3. After give command fastboot flash recovery twrp.img. Give the command fastboot boot twrp.img
And boooom you enter in official twrp

Jitender Baloda said:
1. Okk first you jeed to go this link and download official recovery for nokia 5 running android 8.1 oreo
https://drive.google.com/file/d/1Cl1...w?usp=drivesdk
2. Rename it to twrp and give the command to flash the recovery.
3. After give command fastboot flash recovery twrp.img. Give the command fastboot boot twrp.img
And boooom you enter in official twrp
Click to expand...
Click to collapse
Link broken. File doesn't exist

Try this
https://drive.google.com/file/d/1Cl1yV7tV_VsIC3XIWlCIJXmFfdDZGUbG/view?usp=drivesdk

Err... no, not quite.
1. Your link is (was) dead, but in any case I'd be wary of installing something stashed in a private Google drive folder... Thanks, but no thanks.
2. I have several versions of TWRP, that's not a problem.
3. I know the correct commands (yours are not), that's not a problem.
And boom - no, you don't end up in TWRP. You end up in system, because it overwrites the TWRP automatically UNLESS you reboot to it immediately after flashing, and THIS is the problem.
It turns out that Nokia needs to be plugged into CHARGER, not the PC, then holding Vol+ and Power button combination will do it. It took me more than a dozen tries, but it worked in the end.

Hi, I had the same problem. I've unlocked bootloader and I successfully installed TWRP and I can go to recovery but the problem is I can't boot the system as it stucks on download mode. Can you help?

Press volume up+volume down+power button at the same time for 7-8 second.

Google Pixel 3a (sargo) brick - error boot prepare

Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.

GioPan_ said:
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
Click to expand...
Click to collapse
Do you have tryied to run the official google tool in Windows to try to rescue it?

Estebiu said:
Do you have tryied to run the official google tool in Windows to try to rescue it?
Click to expand...
Click to collapse
Yes, I wrote in the post, I tried both the command line tool and the chrome version. Btw i'm on linux

Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)

GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
I'll try this...

GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
Does this work if adb not working? I only have fastboot.

WriteLovey said:
Does this work if adb not working? I only have fastboot.
Click to expand...
Click to collapse
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.

GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.

WriteLovey said:
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
Click to expand...
Click to collapse
All is well. I'm back on my Pixel, yeah!

GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I just had an encounter with this. I was rooting my device (Pixel 3A) and messed up my partitions through accidentally attempting a downgrade which broke all my ****. I was unable to easily reset this device to factory, so it took me several days to figure out and root. I'm getting better though as a hacker, because a year ago this would have taken me a month.
I was able to enter recovery mode (lying down Android, NO COMMAND). From this recovery mode, adb devices -l recognized my device, although I was unable to get a shell.
At first, ADB was telling me the device was authorized, but I messed with a bunch of other stuff (tried to flash a bunch of different partitions and monkey around in general trying to install Magisk) and then ADB started telling me it wasn't authorized when I used devices -l.
Once it said unauthorized, I was unable to issue the device any commands with ADB, so I just used hardware keys to get into recovery mode. From there, I selected OTA update, and it got into sideload mode. At that point, I used adb sideload with the OTA package that I downloaded here https://developers.google.com/android/ota
^^^ That operation did successfully restore my device to factory
This following guide here describes the details of how to use hard keys to enter recovery on this phone (don't download anything from there tho, and make sure your adblock is on)
How to Hard Reset your new Google Pixel 3a [Tutorial]
In this article, you will learn how to start your Google Pixel 3a up into the Recovery Mode and perform the Hard Reset to make it work perfectly again.
thedroidguy.com

I just wanted to say, I've been wrestling this hardbrick for a couple of days with my Pixel 3a.
I've finally overcome it by sideloading the most recent OTA update after using a hard key combo to get into recovery mode. The hard key combo is hold Power Button, tap Volume Up, then release both. Then, all you need is to use the command:
adb sideload <OTA.zip>
^^^OTA wasn't the actual filename though, you can download OTA packages for Pixel 3A here: https://developers.google.com/android/ota
the OTA binaries are NOT the same as the factory images, which is here
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Sideloading the OTA package brought my phone back from only having fastboot and recovery mode, even when flash-all.sh from the official downloaded firmware failed. Now I know how to undo damage that I cause by rooting this thing. Since I sideloaded newest firmware, it was also like applying an update. I easily got root after that, and I've logged the process. I'll make it into a guide soon

I'll just note that if you accidentally flashed the TWRP boot image instead of simply booting into it, I believe all you have to do is flash the stock boot.img to fix the problem. Obviously you can sideload the entire rom image, but that shouldn't be necessary.
Using the Windows computer (or whatever computer you are sending ADB commands from), download the full stock image directly from Google. Unzip it and then upzip the folder inside. You should find the boot.img file inside that folder. Take that file and then flash it to the phone using the normal ADB command: fastboot flash boot boot.img
While I haven't tried this myself recently, it should work in theory. The command "fastboot flash boot twrp.img" flashes the boot partition with a non-working twrp image, so replacing the faulty image with the stock boot.img should fix the problem.

If I did the same I would first attempt to manually put device in bootloader/aka fastboot mode then fastboot flash the stock boot.img , sudo fastboot flash boot boot.img --slot all
I only read the op (first post here);but I betcha that would have worked. Then sudo ./flash-all.sh and let it do it's thing.

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