Database Info

[Recovery] TWRP 3.1.1 for Xperia X Compact

Greetings!
I'd like to present a TWRP recovery for the Xperia X Compact. This release should work on Xperia X single and dual-SIM variant of the device. I am an owner of Xperia X, but some users reported that my recovery works just fine on its smaller brother.
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-kugo-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds, you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee

it works perfectly! well can't say I tried all functions yet, but it certainly seems so.
thank you so much. finally a proper lastest version of twrp for XC that supports encryption on nougat.
btw. you have to flash it over fotakernel as described in OP. (hotbooting did not work. blank screen.)
I did try other regular X twrp versions with the same result in the past in hopes of finding something better, so the issue was likely the same since I hotbooted them too for a fast test. I guess that's what you get for being lazy. doh.
thanks again for posting it here.
/tuxen

Thank you for sharing.

thanks
Thanks for sharing brother
Working ⚒ perfectly on stock 7.0
no problem

Perfect, thanks. Only annoyance is that I can only reboot the system or power off now.

XperienceD said:
Perfect, thanks. Only annoyance is that I can only reboot the system or power off now.
Click to expand...
Click to collapse
That shouldn't work anyway. I can enable these flags if you want.

eagleeyetom said:
That shouldn't work anyway. I can enable these flags if you want.
Click to expand...
Click to collapse
For all I use the other options there's no need to go out of your way, but if you do make another for whatever reason having the options would be nice.

XperienceD said:
For all I use the other options there's no need to go out of your way, but if you do make another for whatever reason having the options would be nice.
Click to expand...
Click to collapse
It didn't work for me on X. I can enable them in the next version.

realtuxen said:
it works perfectly! well can't say I tried all functions yet, but it certainly seems so.
thank you so much. finally a proper lastest version of twrp for XC that supports encryption on nougat.
btw. you have to flash it over fotakernel as described in OP. (hotbooting did not work. blank screen.)
I did try other regular X twrp versions with the same result in the past in hopes of finding something better, so the issue was likely the same since I hotbooted them too for a fast test. I guess that's what you get for being lazy. doh.
thanks again for posting it here.
/tuxen
Click to expand...
Click to collapse
What do you mean by hot booting? I did this to boot to twrp without installing and have no problem
Code:
fastboot boot twrp.img
Thanks for the twrp, with this I can make full backup before trying to update to 7.1 or 8.0 later :good:

MTP is not working in this version. Everything else is top notch, will test backup/restore a bit later and report back.

trewelu said:
What do you mean by hot booting? I did this to boot to twrp without installing and have no problem
Code:
fastboot boot twrp.img
Thanks for the twrp, with this I can make full backup before trying to update to 7.1 or 8.0 later :good:
Click to expand...
Click to collapse
Exactly. I know hotbooting is not the best description, but you understood anyway.
Strange, I am not a flashophile so I usually just booted twrp this way after a upgrade with flashtool. When the phone was connected to the pc anyway.
But it only works for me with the androplus version, oshmoun's version won't boot that way either. It's not the first time I have talked odd twrp behaviour though, as another guy could not get the androplus one to work at all. I have no reason to doubt him, as this is pretty casual stuff.
I see you are still on MM, I have been on N since it came out and if I remember correctly I backed up ta just before N came out (exploit and N came out very close to each other), took the ota, and unlocked BL. So I performed all the 'fastboots' (better word? heh) on that and 7.1.1. Perhaps the bootloader changed someway? I have no idea.
Edit: if I learned to read properly the first time, you are NOT on MM (doh) but 7.0. Sorry and even more strange. Does MTP work for you? (see below)
---------- Post added at 20:00 ---------- Previous post was at 19:58 ----------
kekistaneerefugee said:
MTP is not working in this version. Everything else is top notch, will test backup/restore a bit later and report back.
Click to expand...
Click to collapse
MTP works absolutely fine here..

This version uses Sony init, so you can see the Sony screen and led indicator while entering the recovery mode. I'm not planning to change it before creating an official TWRP.

eagleeyetom said:
This version uses Sony init, so you can see the Sony screen and led indicator while entering the recovery mode. I'm not planning to change it before creating an official TWRP.
Click to expand...
Click to collapse
Is this in response to something functional, or just general cosmetics info? Doesn't the sony screen origin from the bootloader? How should a official twrp look while booting it? I get the sony boot and led then the TWRP boot image, isn't that normal when booting fotakernel replaced by TWRP? ie. the bootloader handles it when turning the phone on while holding vol down.
An official version would sure be nice. I more than appreciate what you already done. So just take your time.

realtuxen said:
But it only works for me with the androplus version, oshmoun's version won't boot that way either. It's not the first time I have talked odd twrp behaviour though, as another guy could not get the androplus one to work at all. I have no reason to doubt him, as this is pretty casual stuff.
Edit: if I learned to read properly the first time, you are NOT on MM (doh) but 7.0. Sorry and even more strange. Does MTP work for you? (see below)
Click to expand...
Click to collapse
Strange, I don't have problem booting twrp without installing for either of twrp.
I'm on 7.0. I tried to update to 7.1, but I don't get signal if I do the ta_poc + tobias drm fix method, and the drm is still marked as broken.
I really hate mtp and avoid it. I don't think I even have mtp working properly on my pc. I can't help you test that one. Sorry.

trewelu said:
Strange, I don't have problem booting twrp without installing for either of twrp.
I'm on 7.0. I tried to update to 7.1, but I don't get signal if I do the ta_poc + tobias drm fix method, and the drm is still marked as broken.
Click to expand...
Click to collapse
Why are you running it through both ta_poc and Tobias rootkernel with drm fix?
Either you use ta_poc to mount your ta backup from before the bootloader was unlocked thereby bringing the whole trim area back including drm.
Or you use Tobias rootkernel to fix or 'emulate" drm.
Both tools can disable dm verity, sony ric, etc. there is no reason (other than likely creating trouble) to run the kernel image though both tools?!
If you for example run a boot.img with drm fix through ta_poc it will remove the drm fix first. So I imagine things could go wrong of you apply drm fix again (if that is what you're doing) after using ta_poc.
I really hate mtp and avoid it. I don't think I even have mtp working properly on my pc. I can't help you test that one. Sorry.
Click to expand...
Click to collapse
Lol I hate it general too, it can come in handy when only twrp is booted though. I am not sure I have any drivers installed either. Regardless I can access a drive resembling my phone labeled 'mtp device' in 'my computer' when I boot twrp.
Edit: sorry for sidetracking the thread a bit.

eagleeyetom said:
NEEDS TESTING
USB-OTG
Click to expand...
Click to collapse
Thanks! and i can confirm that USB OTG works well.

Working on Sony Nougat
This is the only TWRP I can decrypt my data with on Sony Nougat Stock ROM, Thanks !

realtuxen said:
Both tools can disable dm verity, sony ric, etc. there is no reason (other than likely creating trouble) to run the kernel image though both tools?!
Click to expand...
Click to collapse
Using both tools stems from users reporting they had to to get Magisk to work.

XperienceD said:
Using both tools stems from users reporting they had to to get Magisk to work.
Click to expand...
Click to collapse
There was an info in one of threads, that you should get the stock kernel first through TA_POC and then through kernel repack tool. If you did not, it would work, but occassionally reboots. I am now on 7.1.1 build 206 with Genesis Kernel 1.05 (no_DRM patch version) and it works ok.
As for TWRP, thanks for this! It works ok. Can not fastboot it, must be flashed in recovery parition, but no deal for me. Only thing that I wonder, there are options to backup system, data etc, but not Internal SD (/data/data). Why?

Hi I have a question, I have N 7.1.1, and i want to root it, so i need the twrp, if I flash this twrp, its okay? Ty!

[GUIDE] How to Flash the Pixel Experience ROM on Nokia 7 Plus & Nokia 7

Hey guys i know the Pixel Experience rom has been released for a long time, more information about this Pixel Experience rom https://forum.xda-developers.com/project-treble/trebleenabled-device-development/8-1-0-pixel-experience-t3796011
but unfortunately we could not boot on nokia devices after we flashed this rom
Congratulations that bootloop problem has been solved right now, we are not tired to flash roms
DOWNLOAD TWRP https://drive.google.com/open?id=1-e7zNrXp_mi468h-Zu1X5gbwQtgE17I6
follow these steps
1: unlock your bootloader
thank for @hikari_calyx
2: erase data/factory reset
3: connect your computer with adb and flash any roms based on project preble ( AOSP or RR )(why this step ? my friend told me that this twrp has a bug which can't boot recovery on official firmware)
Code:
fastboot flash system system.img
4: flash this TWRP supported project treble with
Code:
fastboot flash boot_a TWRP.img
Code:
fastboot flash boot_b TWRP.img
5: boot into the twrp
6: extract rom image from PE zip and download Magisk-v16.6.zip, after that move them to Internal Storage
7: format data and flash the Pixel Experience image, choose "System image" Notice: Don't do a reboot before flash Magisk.zip
8: flash the magisk.zip
9: wipe all data and reboot. Done !
Notice: you may see Your Device Is Uncertified when you intend to login Google on this device
Just Do This
Download and install Device ID.apk
copy your Google Service Framework ID
fill your GSF ID on this web and Clink on REGISTER
reboot some times you will be able to use google apps
btw all project treble roms do not include Adaptive brightness and Ambient display
fix them at here https://forum.xda-developers.com/project-treble/trebleenabled-device-development/overlay-enable-night-light-adaptive-t3741965
I'm on this rom for three days and every things go fine unless fingerprint control bug (that means you can control your phone easily with fingerprint)
thanks for viewing, sorry for my english is poor but I've been improving it, I wrote this GUIDE without translate tool
thanks for every member which develop the project treble rom and TWRP and something else

some amazing screenshots

The image does not load

12345wxj said:
The image does not load
Click to expand...
Click to collapse
什么？哪一个镜像不加载？

1452686579 said:
什么？哪一个镜像不加载？
Click to expand...
Click to collapse
我這邊圖片一個都加載不出來

I have a Little problem at step one ._.
No way to unlock BL?

Why is the TWRP upload locked behind a google drive link that you need to request access for?

pitt93 said:
I have a Little problem at step one ._.
No way to unlock BL?
Click to expand...
Click to collapse
there is a way. but you need to pay.

donjamal said:
there is a way. but you need to pay.
Click to expand...
Click to collapse
Do they accept ETH/BTC?

shubham412302 said:
Do they accept ETH/BTC?
Click to expand...
Click to collapse
i have no idea. i don't think so, you need to ask them. it's 5 dollars, they for sure accept paypal

Has anyone flashed this yet? This thread was the straw that broke the camel's back for me and I unlocked my bootloader today.
Now just waiting to hear if anyone other than the op has been successful with this guide.

Doktaphex said:
Why is the TWRP upload locked behind a google drive link that you need to request access for?
Click to expand...
Click to collapse
I don't know why. ? Maybe it is shared right now

Doktaphex said:
Has anyone flashed this yet? This thread was the straw that broke the camel's back for me and I unlocked my bootloader today.
Now just waiting to hear if anyone other than the op has been successful with this guide.
Click to expand...
Click to collapse
Trust me dude ,it works fine I and my Chinese friends tested this guide on Nokia 7 plus and Nokia 7
And there is anotber guide to flash pixel experience rom, but that mode is complex and sometimes does not work

1452686579 said:
Trust me dude ,it works fine I and my Chinese friends tested this guide on Nokia 7 plus and Nokia 7
And there is anotber guide to flash pixel experience rom, but that mode is complex and sometimes does not work
Click to expand...
Click to collapse
It might take me a couple of days as I am quite busy at the moment.

Thank you for your development for the Nokia 7 plus. Really appreciated.

Well, I installed the system image, but now my SIM is not recognized.
I will go through setup and see if the SIM works afterwards?
EDIT: No IMEI on SIM slot 1, there is an IMEI on slot 2 but this slot also does not work.
And of course, I did not do a backup of my working system. (You'd think I would have learned by now, but NO )

Doktaphex said:
Well, I installed the system image, but now my SIM is not recognized.
I will go through setup and see if the SIM works afterwards?
EDIT: No IMEI on SIM slot 1, there is an IMEI on slot 2 but this slot also does not work.
And of course, I did not do a backup of my working system. (You'd think I would have learned by now, but NO )
Click to expand...
Click to collapse
LOL always do backup man, i learned the hard way Please update if you got sim 1 to work!

sublimeace said:
LOL always do backup man, i learned the hard way Please update if you got sim 1 to work!
Click to expand...
Click to collapse
I got my entire system back up and running using the July patched boot image flashed into boot a and b and then sideloaded rollback zip etc, etc....
In general I have found that when I get my self into these situations, if I actually have a back up it ends up failing anyway.
It's always more fun walking the tightrope.
Anyway, both SIM slots are fine on stock ROM rooted with magisk, xposed etc.
I won't be flashing any treble images until I hear more success stories in that respect, I feel that our twrp still has some kinks that need to be ironed out.

9: wipe all data and reboot. Done ! you mean factory reset?

donjamal said:
there is a way. but you need to pay.
Click to expand...
Click to collapse
so, no way

Issue with OOS flashing in TWRP

Hello,
I did a factory reset of OnePlus 8, and I also wiped the system partition. Now the only thing left on my phone is TWRP. I'd like to flash OxygenOS, so I downloaded a signed flashable zip on this thread https://forum.xda-developers.com/oneplus-8/how-to/oneplus-8-repo-oxygen-os-builds-t4084233
But when I flash it with TWRP, it says (in blue)
"flashing A/B zip to inactive slot : A"
Step 1/2
and it's been like this for quite some time now. I wonder if I've done something wrong ? Or should I wait ?
Thanks !

up

LucasDupuis32 said:
Hello,
I did a factory reset of OnePlus 8, and I also wiped the system partition. Now the only thing left on my phone is TWRP. I'd like to flash OxygenOS, so I downloaded a signed flashable zip on this thread https://forum.xda-developers.com/oneplus-8/how-to/oneplus-8-repo-oxygen-os-builds-t4084233
But when I flash it with TWRP, it says (in blue)
"flashing A/B zip to inactive slot : A"
Step 1/2
and it's been like this for quite some time now. I wonder if I've done something wrong ? Or should I wait ?
Thanks !
Click to expand...
Click to collapse
It should take since time but I would say no more than ten to fifteen minutes to complete. Unfortunately I don't want you to stop the process now that it's started that could definitely render it inoperable.
If it does come out of it with an error then just try again but be careful and make sure your can MSM your phone to previous version. I did my TMO to Global flash through zip file with the run all bat. That was pretty damn easy. Happy modding!

Nathan.7118391 said:
It should take since time but I would say no more than ten to fifteen minutes to complete. Unfortunately I don't want you to stop the process now that it's started that could definitely render it inoperable.
If it does come out of it with an error then just try again but be careful and make sure your can MSM your phone to previous version. I did my TMO to Global flash through zip file with the run all bat. That was pretty damn easy. Happy modding!
Click to expand...
Click to collapse
Thanks for your reply.
I left it for more than an hour and it was still on step 1/2. So I stopped the process by rebooting with ADB. When I did that it wiped my /sdcard. I tried to flash OOS again but same result ... I've never heard of MSM before. I just googled it and I see that's it's an unbrick tool only available for Windows but I'm using a Mac. I can still use my brother's laptop which runs Windows 10 but I'd like to know if there's any alternative before doing that.
I really just want to get OOS back Not crossflashing or downgrading
Thanks !

I had a same problem few days ago.
I managed to save my phone with this restore tool: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4085877
Now everything works fine.

miimaa said:
I had a same problem few days ago.
I managed to save my phone with this restore tool: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4085877
Now everything works fine.
Click to expand...
Click to collapse
Thank you for your answer.
I'm trying to run MSM tool but I can't boot in EDL mode and the link for the Qualcomm drivers appears to be dead ...

LucasDupuis32 said:
Thank you for your answer.
I'm trying to run MSM tool but I can't boot in EDL mode and the link for the Qualcomm drivers appears to be dead ...
Click to expand...
Click to collapse
I followed this video and it helped me to solve the problem.
I had problems with EDL-mode too. Try the EDL-mode by just pressing the volume up button and use the phones own cable.
Here's link for drivers: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043

miimaa said:
I followed this video and it helped me to solve the problem.
I had problems with EDL-mode too. Try the EDL-mode by just pressing the volume up button and use the phones own cable.
Here's link for drivers: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
Click to expand...
Click to collapse
Could you also give me the link for the video ? Thanks !

LucasDupuis32 said:
Could you also give me the link for the video ? Thanks !
Click to expand...
Click to collapse
Oops, sorry, here's the link: https://www.youtube.com/watch?v=jtc7EhNsfPA

Moto One 5G Ace Rooted with TWRP using stock Firmware

First of all, I am not a dev and this write up contains steps used by various devs to achieve fulll root. For some, these steps have worked out well. But, not for me. I had issues with some of the steps not fully working as they should, so I did some research until I could piece together something that worked for me. Here's what I did and managed to get fully rooted using the boot.img from the stock firmware after doing all the steps from this link Articul8Madness's Rooting Guide and couldn't get full root access even after using the steps from this link Articul8Madness's Guide for R/W Access. As I have said, these steps worked for most people. I wasn't one of them.
I followed the steps up to the step where the boot.img is modded by Magisk. This is where I omitted using the modded boot.img and used the original boot.img from the stock firmware and I then ran the flashfile script as mentioned in the steps. After everything was applied I then, rebooted the phone, started setup, disabled System Updates, and I then proceeded to install TWRP using the steps from this link https://drive.google.com/drive/folders/1KZ0xhstQ9V_7TYt3xs7P5XdroYX61CEA after opening Minimal ADB and Fastboot applying these scripts
adb reboot fastboot
then apply this
fastboot flash recovery twrp-3.5.2_10-kiev.img
I then rebooted into recovery and installed TWRP to all available partitions. I then installed Magisk, enabled Systemless Hosts in settings, and rebooted. Afterwards, I used the steps here Munjeni's RW in Super Partition Tool to get RW in super partitions after downloading and using superrepack. I had omitted the ./superrepack /dev/block/bootdevice/by-name/super system_a in order to have it applied to all available partitions. Everything worked out great. I then rebooted, updated Magisk, installed Root Checker and Root Explorer with Superuser root access. I then installed Adaway from https://github.com/AdAway/AdAway and clicking on the Get It On AdAway image. Anything that requires root access here on out, can now be installed. As for the SafetyNet issue, I have not had any problem with it at all even though the check had failed. All is now working well and I sincerely hope that this guide will help others as it have helped me. I may have done this write up but, all credits goes to the true devs.
Time for devs to start making custom Roms now that TWRP can be installed.

Your first link doesn't work for me. The Adaway link works. FYI.

RETIEF said:
Your first link doesn't work for me. The Adaway link works. FYI.
Click to expand...
Click to collapse
WOW!!! I see what I did wrong. All links are now working.

Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?

eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Sorry, but you will have to ask one of the Devs in the links that I've provided in the OP. Perhaps they are more suited to help with that.

eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Linux will work fine. All the commands required are done thru a terminal session. Use a text editor to get the long unlock code from the phone.
Good luck.

Ok about terminal. I used cmd , but bootloader cannot be unlocked official way nor at&t unlockable coz i don't live in usa.I will try 3rd party helpers.

iceman19631 said:
First of all, I am not a dev...
Click to expand...
Click to collapse
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.

egalambos said:
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.
Click to expand...
Click to collapse
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.

iceman19631 said:
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.
Click to expand...
Click to collapse
Any plans for an update to 3.6.0 for Android 11??

egalambos said:
Any plans for an update to 3.6.0 for Android 11??
Click to expand...
Click to collapse
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.

iceman19631 said:
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.
Click to expand...
Click to collapse
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.

egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I don't have an answer for that at this time since I'm still on 10. That'd be too much like a blind man in a desert looking for shade and telling another which way to go.

Greetings, I have a few questions. re the Moto G 5G (One 5G Ace)
I've not found a TWRP for this phone yet which were you using?
In other phones it was important to backup the IMEI (EFS ) and 'persistent' partitions. Do we not do that with this phone as well?
Thx in advance

Sorry for the late reply. I used this version of TWRP twrp-3.5.2_10-kiev.img. As far as the IMEI (EFS) question, it wasn't required when using this root process. However, you can back those up if you like.

ADB and 8T

Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R

Try nother USB C cable. Some not able to handle data.

rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!

Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/

BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!

Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R

Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.

BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??

Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.

BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!

Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...

Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11

BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,

Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".

BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,

Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!

Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R

Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.

BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..

Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone