Related
Applying now...
Xda need an update too lol
Are touch screen issues present on the latest October build when using TWRP? I know hyp and rpm were updated last month, just curious if that touch issues remains on this newer build in TWRP?
Does magisk work after this Update?
Sorry guys can't answer ur questions cause I'm on stock locked bootloader not planning on modifying my phone.
All i can say for now that the phone feel faster and scrolling is better.
Did you ever have bluetooth issues and if so, did the patch happen to address the issue?
Alexis96312 said:
Does magisk work after this Update?
Click to expand...
Click to collapse
Yes, no issues with Magisk. But, I came from a clean fastboot flash and redid twrp and Magisk.
Topdroid01 said:
Did you ever have bluetooth issues and if so, did the patch happen to address the issue?
Click to expand...
Click to collapse
I would lose connection to my car after a few minutes but other devices worked fine. With the October update I connected to my car no problem and it held for well over an hour a reconnected just fine after getting out and back in. So I would say yes, the patched helped my Bluetooth issues.
how do you apply the normal image through the other or through twrp or through what? Sorry
Enviado desde mi PH-1 mediante Tapatalk
Notch settings are back under developer settings
garywojdan81 said:
Notch settings are back under developer settings
Click to expand...
Click to collapse
How to use full screen with Youtube? I see no difference on different options.
mcdull said:
How to use full screen with Youtube? I see no difference on different options.
Click to expand...
Click to collapse
pinch zoom out
I don't know how this feature worked in Oreo because I bought the phone when Pie was released. But on Pie and Firefox I don't get any difference with the notch settings.
Edit: Same for Chrome.
Pinch to zoom
resaik said:
Pinch to zoom
Click to expand...
Click to collapse
Maybe I'm blind and just don't see it, but what shall happen? Notch area has same color than the app, that's all what I notice. I believed e. g. the box where to enter the URL will be "behind" the notch or similar?
Edit: Maps works as my expectation: additional screen where the map is shown.
mcdull said:
How to use full screen with Youtube? I see no difference on different options.
Click to expand...
Click to collapse
That's a separate thing with the YouTube app. Just expand the screen by stretching it with multitouch during video play.
I'm rooted with Magisk but keep saying "Stock Backup does not exist". How can I fix this??
Yup, "Use Notch" doesn't work like it did on Oreo, and now I cant go back to Oreo from Pie. I fastboot flash Orea and after booting to the setup screen touch is unresponsive. UGH..
elinca247 said:
Yup, "Use Notch" doesn't work like it did on Oreo, and now I cant go back to Oreo from Pie. I fastboot flash Orea and after booting to the setup screen touch is unresponsive. UGH..
Click to expand...
Click to collapse
You have to unlock critical partitions then reflash the fastboot files. The critical partitions house the touchscreen firmware.
Alexis96312 said:
I'm rooted with Magisk but keep saying "Stock Backup does not exist". How can I fix this??
Click to expand...
Click to collapse
just flash back to stock and reapply twrp and magisk. remember to use the twrp-sept.img as temp image.
Fastboot command
Ascertion said:
You have to unlock critical partitions then reflash the fastboot files. The critical partitions house the touchscreen firmware.
Click to expand...
Click to collapse
Can you please provide the fastboot command to unlock the critical partions?
disregard found command. thanks for the reply.
Well, they're on the Google site. Now...to figure out which one is which ??
Sweet!!
Check here: https://support.google.com/pixelphone/thread/18553639?hl=en
Wish we would get more details. Improvement on smooth display and camera doesn't give us much. Maybe they fixed some of the yellow tinted pictures in the camera.
I'll probably just keep mine on force 90hz anyways. My battery life has been just fine. Even running white theme all the time.
spencer92a said:
Check here: https://support.google.com/pixelphone/thread/18553639?hl=en
Click to expand...
Click to collapse
-14 looks like for me
spencer92a said:
Check here: https://support.google.com/pixelphone/thread/18553639?hl=en
Click to expand...
Click to collapse
So nothing for QD1A.190821.011?
StrangerWeather said:
So nothing for QD1A.190821.011?
Click to expand...
Click to collapse
That's oct patch, you need to flash nov patch
Mr Patchy Patch said:
I'll probably just keep mine on force 90hz anyways. My battery life has been just fine. Even running white theme all the time.
Click to expand...
Click to collapse
I have mine forced 90hz all the time. I always have a charger available and like the extra speed.
update without losing root ?
Jiggs82 said:
That's oct patch, you need to flash nov patch
Click to expand...
Click to collapse
I don't think so tbh, it's one of three variants: 014, 007, 011 based on this and this.
TheUndertaker21 said:
update without losing root ?
Click to expand...
Click to collapse
Not really. You'll need to flash the November update with the -w removed, let it boot up, then put a copy of the November boot.img on your internal storage, then patch it with magisk. Then you'll need to fastboot your patched boot.img, and you should be good to go :good:
Badger50 said:
Not really. You'll need to flash the November update with the -w removed, let it boot up, then put a copy of the November boot.img on your internal storage, then patch it with magisk. Then you'll need to fastboot your patched boot.img, and you should be good to go :good:
Click to expand...
Click to collapse
Thanks figured as much
From my previous pixels
TheUndertaker21 said:
update without losing root ?
Click to expand...
Click to collapse
If you receive the OTA, you can just try this method from pixel 3 xl thread a while back as i did before on my pixel 3 xl too :
S8rooted&tooted said:
Just took the OTA.
Uninstall restore images
Download OTA and DONT REBOOT
reinstall magisk to inactive slot.
Blammo up and running.
Click to expand...
Click to collapse
So .011 Variants have to wait? No Update available yet.
I noticed that they show one of the downloads available are specifically for Verizon and ATT. I have a Google Unlocked Device - but I am on ATT. Does anyone know what happens if I flash the firmware intended for ATT? If my bootloader is locked when I flash it - will my bootloader be locked after flashing ? Just curious.....
Geekser said:
I noticed that they show one of the downloads available are specifically for Verizon and ATT. I have a Google Unlocked Device - but I am on ATT. Does anyone know what happens if I flash the firmware intended for ATT? If my bootloader is locked when I flash it - will my bootloader be locked after flashing ? Just curious.....
Click to expand...
Click to collapse
No, it won't lock your bootloader. Only you can do that manually. I just updated mine to November, and all is well :good:
Badger50 said:
No, it won't lock your bootloader. Only you can do that manually. I just updated mine to November, and all is well :good:
Click to expand...
Click to collapse
I usually would have had my ota by now. Still nothing for me. Kinda weird.
Mr Patchy Patch said:
I usually would have had my ota by now. Still nothing for me. Kinda weird.
Click to expand...
Click to collapse
Nothing for me yet either
Msan2000 said:
Nothing for me yet either
Click to expand...
Click to collapse
It's weird. I wonder what's up with that.
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.
the update of June 2020 is online
https://developers.google.com/android/images
https://dl.google.com/dl/android/aosp/coral-qq3a.200605.001-factory-dbd8ce20.zip
It fixed the face id finally.
Magisk root still working with June update.
gm007 said:
It fixed the face id finally.
Click to expand...
Click to collapse
What was wrong with it?
Personal safety is not available on mine.
pilotgav said:
What was wrong with it?
Click to expand...
Click to collapse
It was broken when downgrading from Android 11.
This include the Covid tracker?
Sent from my Pixel 4 XL using Tapatalk
MicroMod777 said:
This include the Covid tracker?
Click to expand...
Click to collapse
Doesn't give me an option to turn it on but it's there
MicroMod777 said:
This include the Covid tracker?
Click to expand...
Click to collapse
Do you mean an application or the service? The service was there before the update.
gm007 said:
It fixed the face id finally.
Click to expand...
Click to collapse
You might want to state which version of the Face Unlock issue you're talking about, the one from the DP4 and subsequent downgrade is still there.
Tried to update with magisk via OTA method
Phone boots to black screen, only thing I can do is access the power menu...
dragynbane222 said:
You might want to state which version of the Face Unlock issue you're talking about, the one from the DP4 and subsequent downgrade is still there.
Click to expand...
Click to collapse
Yes I'm talking about the downgrade from dp4 to 10.
Let me tell you what I did,it was by mistake that I fix it.
I was on May build with face id broken,I downloaded the June ota yesterday but by mistake I choose Telstra ota the one that end with 002.A1 and face id work.
Then I realized that the build number is wrong for my phone so I tried to flash the full June build the one that end with 001 and again face id stopped working so I decided to stay with Telstra build
Hey guys after flashing magisk image tje touchscreen doest react so i cant log in. After flashing stock image everything works fine again. Anyone else experiencing this??
xdidnothingwrongx said:
Hey guys after flashing magisk image tje touchscreen doest react so i cant log in. After flashing stock image everything works fine again. Anyone else experiencing this??
Click to expand...
Click to collapse
Best advice I could give is to first patch the boot.img when all your magisk modules have either been disabled, or removed. Then dirty fastboot, (-w removed) the factory image to your inactive slot, let it boot up, then fastboot the magisk_patched.img to both slots. Also make sure your platform-tools are up to date. Best of luck to ya :good:
gm007 said:
Do you mean an application or the service? The service was there before the update.
Click to expand...
Click to collapse
Since when?
Sent from my Pixel 4 XL using Tapatalk
MicroMod777 said:
Since when?
Click to expand...
Click to collapse
If you mean the covid exposure notification i got it 2 weeks ago, it's in the google setting in the system settings.
Updates to Telstra and worked. Hope they release an update for the regular software soon. Thank you for the tip.
Worse battery performance on June patch than may
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