Database Info

Alcatel OneTouch Flint TWRP

So i was finally able to install TWRP after rooting using this guide from @Casey Campanile
http://forum.xda-developers.com/android/development/alcatel-onetouch-flint-root-t3440088
**You must have ROOT first**
So it is actually pretty simple,
*Download the file i uploaded
*Unzip the TWRP file
*Download FlashFire
Now I did have OEM Unlock in Developer Settings and BusyBox installed when I did this, not sure if it makes a difference.
*Make sure BusyBox is up to date
1. I suggest doing a backup
2. Flash the TWRP file that you unzipped as Firmware Package
3. Done
DO NOT ATTEMPT TO WIPE DEVICE THROUGH THE OPTION IN SETTINGS!!!
P.S. all this is done at your own risk. im not responsible for any bricked devices.
Thanks for the edit suggestions @Casey Campanile

jsowen321 said:
So i was finally able to install TWRP after rooting using this guide from @Casey Campanile
http://forum.xda-developers.com/android/development/alcatel-onetouch-flint-root-t3440088
**You must have ROOT first**
So it is actually pretty simple,
*Download the file i uploaded
*Unzip the TWRP file
*Download FlashFire
Now I did have OEM Unlock in Developer Settings and BusyBox installed when I did this, not sure if it makes a difference.
*Make sure BusyBox is up to date
1. I suggest doing a backup
2. Flash the TWRP file that you unzipped as Firmware Package
3. Done
P.S. all this is done at your own risk. im not responsible for any bricked devices.
Thanks for the edit suggestions @Casey Campanile
Click to expand...
Click to collapse
I can't believe no one has thanked you or at least said good going on this.I've had my Flint for about 6 months and used it as a backup mostly.I was sitting at work tonight waiting on the boss and I decided to look up and see if anyone had did anything with the Flint yet.I was floored when I came across your post. Everything is working great with TWRP but if I let it timeout and screen go dark it won't allow me to swipe to unlock.Not a big deal to me but I wanted to report it to you since no one else seems to be commenting on this.I appreciate your hard work and taking the time to do it. Great job!!! ? ??

jsowen321 said:
So i was finally able to install TWRP after rooting using this guide from @Casey Campanile
http://forum.xda-developers.com/android/development/alcatel-onetouch-flint-root-t3440088
**You must have ROOT first**
So it is actually pretty simple,
*Download the file i uploaded
*Unzip the TWRP file
*Download FlashFire
Now I did have OEM Unlock in Developer Settings and BusyBox installed when I did this, not sure if it makes a difference.
*Make sure BusyBox is up to date
1. I suggest doing a backup
2. Flash the TWRP file that you unzipped as Firmware Package
3. Done
P.S. all this is done at your own risk. im not responsible for any bricked devices.
Thanks for the edit suggestions @Casey Campanile
Click to expand...
Click to collapse
I've got an issue with TWRP I can't seem to find anything on.Wanted to see if you could help me figure it out.Initially after installing all was well.Made a backup and rebooted.Today,a month later I wanted to do a factory reset and Initially tried via settings/backup/device reset.It just rebooted back to home screen.I then rebooted into TWRP and tried via wipe but nothing will mount.My SD card won't even mount and everything shows all 0's.Any ideas?I'm not a noob by any means but I can't figure this one out.

bob24260 said:
I've got an issue with TWRP I can't seem to find anything on.Wanted to see if you could help me figure it out.Initially after installing all was well.Made a backup and rebooted.Today,a month later I wanted to do a factory reset and Initially tried via settings/backup/device reset.It just rebooted back to home screen.I then rebooted into TWRP and tried via wipe but nothing will mount.My SD card won't even mount and everything shows all 0's.Any ideas?I'm not a noob by any means but I can't figure this one out.
Click to expand...
Click to collapse
Hmm, that's seems weird haven't experienced that before. I haven't tried to do a full swipe yet on this phone. Did it complete the wipe?

jsowen321 said:
Hmm, that's seems weird haven't experienced that before. I haven't tried to do a full swipe yet on this phone. Did it complete the wipe?
Click to expand...
Click to collapse
No it didn't.I couldn't get anything to mount in recovery to complete a wipe.I think perhaps that we should do a warning about trying to wipe from backup/reset in settings.At least until we figure this out.I was finally able to do a reset via Flash fire but nothing will mount in recovery still.

bob24260 said:
No it didn't.I couldn't get anything to mount in recovery to complete a wipe.I think perhaps that we should do a warning about trying to wipe from backup/reset in settings.At least until we figure this out.I was finally able to do a reset via Flash fire but nothing will mount in recovery still.
Click to expand...
Click to collapse
That sounds like a good idea only thing I would try is to try and restore the backup you did and try and reflash TWRP see if that does anything I have yet to try and reset this phone considering its my daily phone currently my lg g3 suffered the fading screen and I couldn't get it fixed

jsowen321 said:
That sounds like a good idea only thing I would try is to try and restore the backup you did and try and reflash TWRP see if that does anything I have yet to try and reset this phone considering its my daily phone currently my lg g3 suffered the fading screen and I couldn't get it fixed
Click to expand...
Click to collapse
I can't restore anything. Can't mount anything in recovery.Here in next couple weeks I'll be glad to send you my Flint.I'm getting a One Plus 3.

bob24260 said:
I can't restore anything. Can't mount anything in recovery.Here in next couple weeks I'll be glad to send you my Flint.I'm getting a One Plus 3.
Click to expand...
Click to collapse
Lol I'm actually looking into one of those too or I was looking at the honor line too but OnePlus seems better

jsowen321 said:
Lol I'm actually looking into one of those too or I was looking at the honor line too but OnePlus seems better
Click to expand...
Click to collapse
I highly recommend the Honor 5x if youre budget inclined and the Mate 8 if you have a few extra $$.I had the 5x and it actually is a damn nice device.I beat the Nexus 6 in Antutu scores with it.

bob24260 said:
I highly recommend the Honor 5x if youre budget inclined and the Mate 8 if you have a few extra $$.I had the 5x and it actually is a damn nice device.I beat the Nexus 6 in Antutu scores with it.
Click to expand...
Click to collapse
That's pretty impressive I'm gonna look into that one, one thought just crossed my mind you try flashing your recovery through the fastboot commands on the bootloader?

I tried reflashing every way possible.Still nothing will mount.I think you may want to add a warning to the OP not to try and factory reset via settings.Maybe we can figure it out.

I added it to the OP. Something that might help is when I was digging thru this phone I found out it's the same as the Alcatel pop 3 5.5 looks like they just renamed it

OMG, this has been great. Im all rooted and TWRPd with my Flint now. It is a great feeling, but Im not sure what to do next Are there any benefits to this now? I can't find any custom roms for it...is there a way to get something newer than Android 5.1.1 installed?

molebrain said:
OMG, this has been great. Im all rooted and TWRPd with my Flint now. It is a great feeling, but Im not sure what to do next Are there any benefits to this now? I can't find any custom roms for it...is there a way to get something newer than Android 5.1.1 installed?
Click to expand...
Click to collapse
No custom ROMs rn but u can install Xposed for lollipop and u can remove bloatware with titanium backup

Cool, so, I'm not clear what Xposed gives me though. Is it worth it?

Hey Xposed has different modules you can install, my favorite are YouTube background play and YouTube ad blocker but they have various ones, just take a look on the downloads section in xposed

jsowen321 said:
Hey Xposed has different modules you can install, my favorite are YouTube background play and YouTube ad blocker but they have various ones, just take a look on the downloads section in xposed
Click to expand...
Click to collapse
Wow, my day is complete. This is great. Going to install soon. Ive been looking for a YouTube ad blocker! :good:

Just wanted to follow up again and say thanks for pointing me to this. I've got the framework installed and now im going through the modules, picking what looks good to me. This is pretty much all I needed I dont care if we never get a custom rom at this point.

Your welcome, there's a lot of modules, I would say just be careful which ones you install and use. Ive had some that gave me problems

CyanogenMod a possibility?

[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!

has Android 11 been rooted?

Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?

Wait for the beta's
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
Hi,
from what I have read, no, its not a daily driver, yet. I'd wait till the beta's are available in`May, to give it a try.
Though you could always just flash the update & see if it is OK for you. If not revert back to 10.

ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
Not rootable yet. Lots of changes to it that Mr. Wu is going to have to work on. He said he knows what to do, just going to take a bit of time.

ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
I am on it and it is definitely stable enough to use as a DD but unfortunately no root yet

I'm using it from the first day release. Stable as a rock, i didn't have any issue. I have a question, what I must do to switch from the last developer to the first beta?

atembleque said:
I'm using it from the first day release. Stable as a rock, i didn't have any issue. I have a question, what I must do to switch from the last developer to the first beta?
Click to expand...
Click to collapse
Usually, you can either sideload the ota or flash the new image in fastboot after removing the -w. Who knows with google though, they might decide to change that procedure somehow, too Best bet is to just wait for it to be released and follow whatever instructions are given at that point.

wangdaning said:
Usually, you can either sideload the ota or flash the new image in fastboot after removing the -w. Who knows with google though, they might decide to change that procedure somehow, too Best bet is to just wait for it to be released and follow whatever instructions are given at that point.
Click to expand...
Click to collapse
Thanks!

Can anyone upload me an android 10 rooted boot.img for march update? I can't seem to patch it using canary magisk.

Vanschtezla said:
Can anyone upload me an android 10 rooted boot.img for march update? I can't seem to patch it using canary magisk.
Click to expand...
Click to collapse
The canary Magisk is buggy to say the least. After removing it from my P3XL a while ago, I had to revert to stable on my wife's P3 because attempted patching just results in the app closing. It patched fine with stable.

sliding_billy said:
The canary Magisk is buggy to say the least. After removing it from my P3XL a while ago, I had to revert to stable on my wife's P3 because attempted patching just results in the app closing. It patched fine with stable.
Click to expand...
Click to collapse
I tried patching it with stable but my phone won't boot after flashing. Was your wife's booted fine?

Vanschtezla said:
I tried patching it with stable but my phone won't boot after flashing. Was your wife's booted fine?
Click to expand...
Click to collapse
Yeah, no issues. Been running it for over 12 hours now with multiple reboots and EX kernel install. Flashed factory image without -w. Attempted to patch boot. On failure (app closing), I force closed canary MM, cleared cache and data from app and then uninstalled it. Installed the stable APK and patched boot. Flashed magisk_patched to both slots, and it booted fine. Then installed EX (old one). This morning , updated EX to the new one. Not a single issue since the canary app closure (which others have reported when patching on various devices for days on the canary thread).

sliding_billy said:
Yeah, no issues. Been running it for over 12 hours now with multiple reboots and EX kernel install. Flashed factory image without -w. Attempted to patch boot. On failure (app closing), I force closed canary MM, cleared cache and data from app and then uninstalled it. Installed the stable APK and patched boot. Flashed magisk_patched to both slots, and it booted fine. Then installed EX (old one). This morning , updated EX to the new one. Not a single issue since the canary app closure (which others have reported when patching on various devices for days on the canary thread).
Click to expand...
Click to collapse
I only use the fastboot flash boot magisk_patched.img command. That ought to flash the patched boot.img on both slots now wouldn't it?
Edit: Nevermind I flashed to both slots but to no avail. If you don't mind can you share me your magisk_patched.img?

Vanschtezla said:
I only use the fastboot flash boot magisk_patched.img command. That ought to flash the patched boot.img on both slots now wouldn't it?
Edit: Nevermind I flashed to both slots but to no avail. If you don't mind can you share me your magisk_patched.img?
Click to expand...
Click to collapse
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img

sliding_billy said:
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Same result. After booting sequence it just ended up with "powering off" and went to recovery after rebooting. Must have missed something. Thank you. I'll wait for your patched file then.
Edit: I found the culprit. It's my magisk modules. I removed everything and managed to get it to boot. Now just need to figure out which one is causing the bootloop. Thanks!

Vanschtezla said:
Same result. After booting sequence it just ended up with "powering off" and went to recovery after rebooting. Must have missed something. Thank you. I'll wait for your patched file then.
Edit: I found the culprit. It's my magisk modules. I removed everything and managed to get it to boot. Now just need to figure out which one is causing the bootloop. Thanks!
Click to expand...
Click to collapse
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
---------- Post added at 05:34 AM ---------- Previous post was at 05:31 AM ----------
sliding_billy said:
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
Click to expand...
Click to collapse
Just saw your edit. Do you have the Edge Sense Plus module installed? It normally takes J a day or so update the module for the new build. You pretty much need to disable that every month until he posts an update.

sliding_billy said:
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
---------- Post added at 05:34 AM ---------- Previous post was at 05:31 AM ----------
Just saw your edit. Do you have the Edge Sense Plus module installed? It normally takes J a day or so update the module for the new build. You pretty much need to disable that every month until he posts an update.
Click to expand...
Click to collapse
No I don't use Edge Sense Plus. But I did use the Centre Clock module. I think it's related to the system UI crashing hence the powering off immediately after booting. Which might also explain why the animation was kind of laggy. I'm guessing something to do with the feature drop which affected the system UI which leads to incompatibility between the ui and the module. But yeah just a guess.

Vanschtezla said:
No I don't use Edge Sense Plus. But I did use the Centre Clock module. I think it's related to the system UI crashing hence the powering off immediately after booting. Which might also explain why the animation was kind of laggy. I'm guessing something to do with the feature drop which affected the system UI which leads to incompatibility between the ui and the module. But yeah just a guess.
Click to expand...
Click to collapse
I do not use that module, but it definitely sounds like it could be an issue since you weren't actually boot looped and were able to remove it. I try to keep my module use minimal (and use well vetted ones only) to avoid wondering whether they are the root cause of issues when they happen. Best of luck. Just glad you are up and running.

sliding_billy said:
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Are you on Android 11 and have root?

Zehlek said:
Are you on Android 11 and have root?
Click to expand...
Click to collapse
No, this was OT from the original thread title when the question was asked about 10.

sliding_billy said:
No, this was OT from the original thread title when the question was asked about 10.
Click to expand...
Click to collapse
Sorry to stay OT, but since you mentioned EX kernel, does using it also not hide the unlocked bootloader in our "new and improved" SafetyNet world? I'm one of those for whom everything is still working so far--Pay, banking apps, device is certified, etc. I'd hate to lose all that, though, because I'm not going to unroot. I guess if I have to I can use Pay on my watch and use the banks' Web sites instead of their apps.

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

Could swapping Boot Partitions to run Door Dash Dasher app be possible?

Hello I have a question. I have a OnePlus 7 Pro rooted with Magisk and of course the Dasher app wont work properly. Could I simply flash back and forth from a Magisk boot partition to a non rooted boot partition in order for Dasher to work? I wanted to get some insight before I start flashing things..
Thank you

ben_deez said:
Hello I have a question. I have a OnePlus 7 Pro rooted with Magisk and of course the Dasher app wont work properly. Could I simply flash back and forth from a Magisk boot partition to a non rooted boot partition in order for Dasher to work? I wanted to get some insight before I start flashing things..
Thank you
Click to expand...
Click to collapse
Does the Door Dash app detect root? Chances are you just need to make sure you're passing Play Integrity BASIC and DEVICE verdicts. More information here
It's generally inadvisable to try swapping back and forth between the slots on A/B devices. They aren't meant to be swapped at will; the purpose of A/B slots is for seamless system updates, and you could very well render both slots unbootable by attempting to do so.

So I installed the above Integrity Checker and I failed all three. What if I leave the other slot alone and flash back and forth TWRP backups of the boot partition on my current slot? What would you recommend at this point?
Thanks again

V0latyle said:
Does the Door Dash app detect root? Chances are you just need to make sure you're passing Play Integrity BASIC and DEVICE verdicts. More information here
It's generally inadvisable to try swapping back and forth between the slots on A/B devices. They aren't meant to be swapped at will; the purpose of A/B slots is for seamless system updates, and you could very well render both slots unbootable by attempting to do so.
Click to expand...
Click to collapse
Are you a Marine? Me too. Former Marine that is. Ooh-Rah.... I understand if you need to delete this reply since it is off topic.. But I had to shout out.

ben_deez said:
So I installed the above Integrity Checker and I failed all three. What if I leave the other slot alone and flash back and forth TWRP backups of the boot partition on my current slot? What would you recommend at this point?
Thanks again
Click to expand...
Click to collapse
Read the post, please. The answers to your questions are there. Changing your boot image won't matter because your bootloader is unlocked, and that alone means you're going to fail all Play Integrity verdicts without using USNF.
ben_deez said:
Are you a Marine? Me too. Former Marine that is. Ooh-Rah.... I understand if you need to delete this reply since it is off topic.. But I had to shout out.
Click to expand...
Click to collapse
There's no such thing as a former Marine, you should know better, knucklehead! 2007-2016, 2844/2841/2862/8411
We have several other mods who are Marines: @Az Biker, @Clark Joseph Kent for example, we even have a few veterans from other countries.

V0latyle said:
Read the post, please. The answers to your questions are there. Changing your boot image won't matter because your bootloader is unlocked, and that alone means you're going to fail all Play Integrity verdicts without using USNF.
There's no such thing as a former Marine, you should know better, knucklehead! 2007-2016, 2844/2841/2862/8411
We have several other mods who are Marines: @Az Biker, @Clark Joseph Kent for example, we even have a few veterans from other countries.
Click to expand...
Click to collapse
We were told to use the term Former Marine in bootcamp... and never use the term "X Marine" Former means "The same but at a different time" 1993-1997 1391... I'm from the "old Corps"....
But yes I did read everything on the post.. Good info thank you. I'm just trying to find a solution to this without having to lock the bootloader.

ben_deez said:
We were told to use the term Former Marine in bootcamp... and never use the term "X Marine" Former means "The same but at a different time" 1993-1997 1391... I'm from the "old Corps"....
Click to expand...
Click to collapse
One of my younger brothers was a bulk fuel specialist in Okinawa, he just got out a few months ago
ben_deez said:
But yes I did read everything on the post.. Good info thank you. I'm just trying to find a solution to this without having to lock the bootloader.
Click to expand...
Click to collapse
Well, as mentioned in that thread, you should be able to pass BASIC and DEVICE integrity by installing USNF 2.4.0, which forces Play Integrity to use basic evaluation instead of hardware methods. Don't worry about STRONG integrity, I am not aware of any apps that require that attestation. The vast majority of Play Store apps only use the DEVICE label as this indicates that the device (and software) has been tested via Android CTS; those which require additional security use the BASIC label as well. There are a few apps that use their own root detection techniques such as the presence of a SU binary or the Magisk app, but these are few and far between, and I highly doubt that the Dash app would be one of these. I would think it's a safe assumption that it simply uses the DEVICE label, maybe the BASIC label as well. Since you were failing all 3 labels, this would make sense.
Install the Magisk module mentioned in the thread and reboot, then use Integrity Checker to verify you're passing BASIC and DEVICE labels. If Dash still doesn't work, force stop and clear app data.

I installed USNF 2.4.0 rebooted and still failed all 3 integrity checks including BASIC and DEVICE. The Dasher app will install and seems to work fine until I select "Go Dash" to start accepting deliveries. It just loops back to the sign in page. I've cleared the data and cache and uninstalled and installed many times.... I even tried using older versions of the app with no success. I've tried using Magisk Hide and Zygist to no avail. appreciate you taking the time for my questions.. Much appreciation

ben_deez said:
I installed USNF 2.4.0 rebooted and still failed all 3 integrity checks including BASIC and DEVICE. The Dasher app will install and seems to work fine until I select "Go Dash" to start accepting deliveries. It just loops back to the sign in page. I've cleared the data and cache and uninstalled and installed many times.... I even tried using older versions of the app with no success. I've tried using Magisk Hide and Zygist to no avail. appreciate you taking the time for my questions.. Much appreciation
Click to expand...
Click to collapse
What version of Magisk are you using?
I believe that since you're using a Chinese device you may still need to use MagiskHide Props Config to spoof a valid fingerprint.

V0latyle said:
What version of Magisk are you using?
I believe that since you're using a Chinese device you may still need to use MagiskHide Props Config to spoof a valid fingerprint.
Click to expand...
Click to collapse
25.2

ben_deez said:
25.2
Click to expand...
Click to collapse
I installed MagiskHide Props Config but I'm not sure which fingerprint to use.. Many selections... I selected the TMobile fingerprint since I have a GM1915 . I'm also still on 10.0.3.GM21AA So far it hasn't fixed the problem.

What about a Dual Boot system? Is it possible to have dual boot systems with one rooted and one thats not rooted? It still wouldn't hide that the bootloader is unlocked tho right? Because I got the app to work on my old LG V20. Apparently once the bootloader was unlocked on the v20 it couldn't ever be locked again because of using Dirty Santa to unlock it. My v20 was vs995 and I converted it to un996.. all I did to make the app work was do a factory reset. I didn't have to flash the original vs995 firmware. But I think the bootloader should still be unlocked on the v20 even after the factory reset... The app didn't work on my OnePlus 7 pro even after I did a factory reset. frustrating.

V0latyle said:
One of my younger brothers was a bulk fuel specialist in Okinawa, he just got out a few months ago
No Kidding? How cool is that? I was at Camp Hansen 9th ESB Bulk Fuel Co.. Before that I was Station Fuels at MCAS El Toro in 1996 running the Hot Pits. Small world
Click to expand...
Click to collapse