Related
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
S.Phrenic said:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
Click to expand...
Click to collapse
Can you get into bootloader? Recovery?
Lethargy said:
Can you get into bootloader? Recovery?
Click to expand...
Click to collapse
Currently, nope... I'm trying.. I see that sometimes the screen is on... sometimes I see the Google Logo... but Can't fully figure out when that happens
[EDIT]YES!!!!!!!!! Got in.!!!!!!... *pfieuw*.. now what do i do?
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Please don't use toolkits.
Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
S.Phrenic said:
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
Click to expand...
Click to collapse
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Lethargy said:
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Click to expand...
Click to collapse
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
S.Phrenic said:
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
Click to expand...
Click to collapse
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Could somebody not just make a flashable zip with the correct build.prop?
Failing that, just reflash the ROM.
Lethargy said:
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Click to expand...
Click to collapse
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it worked out
S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it sorted but, unless you couldn't boot into recovery, you didn't need to go back to stock.
Flashing the correct build.prop or ROM you were using should have sorted it out, without losing any data (you would have lost any system mods if you flashed the ROM again, though).
I'm only mentioning this in case somebody else searches and finds this thread for the same problem.
I've changed the build.prop loads of times on many devices and only once it went into a bootloop. Flashing a build.prop zip sorted it.
Hello.
Im not sure if someone else also found the fix for app conflicts and errors when u mannualy update system apps. But I found a working fix.
When I was testing something to fix my led cover but find out this will resolve the annoying conflicts when manually updating system apps.
So this will work for as I tested so far for 10 minuts or when u reboot. After that u need to do this again.
1. Go to device security.
2. Go to safe or secure start up. Im not English so.
3. If secure start up is disabled turn it on and reboot.
3. If secure start up is enabled turn it off and reboot.
I was able to update all apps I had conflicts before. But when I reboot again u will need to redo step 3. Only this time it will be turning on or off instead of off or on. So bassicly when it was turned off then u will turn it on instead.
Hope this will help for u guys aswell.
I just tried this workaround, and I can confirm it WORKS!:good:
Alf0903 said:
I just tried this workaround, and I can confirm it WORKS!:good:
Click to expand...
Click to collapse
Glad to hear. Thanks for the thanks sir. U took my thanks vurginity haha.
Wow
Works amazing just now i updated touchWiz Home to latest version
Thank you so much
الفلسطيني said:
Wow
Works amazing just now i updated touchWiz Home to latest version
Thank you so much
Click to expand...
Click to collapse
Glad it works for multiple users now. Thanks
I can confirm this works , thanks for the tip though
Thanks. It works great!
It is working on mine also. Thank you so much
iskelrdayisi said:
It is working on mine also. Thank you so much
Click to expand...
Click to collapse
kenshinchai said:
Thanks. It works great!
Click to expand...
Click to collapse
shah22 said:
I can confirm this works , thanks for the tip though
Click to expand...
Click to collapse
Glad to hear. Im wondering what it has to do with it.
It worked for me too. Thanks.
Tapatalkkal küldve az én SM-G935F eszközömről
Help
I can't find the option on security settings. Could you please guide me how to get there?
i cant find the setting either
search for secure start up
It works for me to install the latest Touchwiz home. I also installed Camera 6.5.98 on my shop edge. Thanks.
Sent from my SM-G935W8 using Tapatalk
---------- Post added at 07:30 PM ---------- Previous post was at 07:22 PM ----------
ma678 said:
It works for me to install the latest Touchwiz home. I also installed Camera 6.5.98 on my shop edge. Thanks.
Sent from my SM-G935W8 using Tapatalk
Click to expand...
Click to collapse
Edit: 6.5.95.
Sent from my SM-G935W8 using Tapatalk
Thank you, it actually worked!
Not working for my
AllSmokeEm said:
Hello.
Im not sure if someone else also found the fix for app conflicts and errors when u mannualy update system apps. But I found a working fix.
When I was testing something to fix my led cover but find out this will resolve the annoying conflicts when manually updating system apps.
So this will work for as I tested so far for 10 minuts or when u reboot. After that u need to do this again.
1. Go to device security.
2. Go to safe or secure start up. Im not English so.
3. If secure start up is disabled turn it on and reboot.
3. If secure start up is enabled turn it off and reboot.
I was able to update all apps I had conflicts before. But when I reboot again u will need to redo step 3. Only this time it will be turning on or off instead of off or on. So bassicly when it was turned off then u will turn it on instead.
Hope this will help for u guys aswell.
Click to expand...
Click to collapse
So basically u CANT just turn it off and reboot but
1. turn off&reboot
2. turn on reboot
3. turn off again and reboot one last time??
Because I still get the error when I just turn it off and reboot
Im trying to install 3 apks to get Note 8 Live messages. Im still not sure it works but cant confirm because I can't install it.
shorty76 said:
Not working for my
Click to expand...
Click to collapse
KLit75 said:
So basically u CANT just turn it off and reboot but
1. turn off&reboot
2. turn on reboot
3. turn off again and reboot one last time??
Because I still get the error when I just turn it off and reboot
Im trying to install 3 apks to get Note 8 Live messages. Im still not sure it works but cant confirm because I can't install it.
Click to expand...
Click to collapse
Hello.
Sorry for late reaction. Real busy at work. Friday im a day off and come with a proper response. Also I have to chec if they hotfixed it. I also can confirm the new galaxy 8 and note this method wont work. Since i dont own them i cant help with that part.
Does fingerprint security have to be disabled first?
I don't have it either. Latest Batman rom
Thanks to @cameljockey1, and the solution is located #4 post.
Hi,
Newbie to Android 7+ and Magisk, I'm sorry if it is an common thing but I still didn't get any clue after some search.
I found that after installing Magisk, I'm prompted to do the pattern unlock everytime when it reboots before Android booting is ready.
I would like to know if there is a way to get rid of the thing and keep my phone encrypted.
Thank you.
etann said:
Hi,
Newbie to Android 7+ and Magisk, I'm sorry if it is an common thing but I still didn't get any clue after some search.
I found that after installing Magisk, I'm prompted to do the pattern unlock everytime when it reboots before Android booting is ready.
I would like to know if there is a way to get rid of the thing and keep my phone encrypted.
Thank you.
Click to expand...
Click to collapse
My phone is not rooted and each time I reboot I need to do the pattern unlock. It's due to encryption not to root.
I don't think you can get rid of this.
etann said:
Hi,
Newbie to Android 7+ and Magisk, I'm sorry if it is an common thing but I still didn't get any clue after some search.
I found that after installing Magisk, I'm prompted to do the pattern unlock everytime when it reboots before Android booting is ready.
I would like to know if there is a way to get rid of the thing and keep my phone encrypted.
Thank you.
Click to expand...
Click to collapse
You sure you get Android 7 from U11+ ?
Setting- security and location- screen lock and change your pattern and it will ask if you want to have it for device reboot. Click no.
bnwg said:
You sure you get Android 7 from U11+ ?
Click to expand...
Click to collapse
ok let me make it clear. I mean it is the first android 7+ device for me, since I had <= android 6 devices before. so compares to that fact, I wrote it is my first Android 7+.
cameljockey1 said:
Setting- security and location- screen lock and change your pattern and it will ask if you want to have it for device reboot. Click no.
Click to expand...
Click to collapse
Thank you, I thought turning on that option was about to keep locked after rebooting, which I was wrong.
Kidy973 said:
My phone is not rooted and each time I reboot I need to do the pattern unlock. It's due to encryption not to root.
I don't think you can get rid of this.
Click to expand...
Click to collapse
Thank you, but you may refer to @cameljockey1 from #4 of this thread, I finally got rid of this by following his method.
OnePlus 7 stuck in "Your device is corrupt it can't be trusted" after locking the boo
Help. I've made a big mistake. I can only access the Bootloader. Recovery mode is not accessible.
As with the 7 Pro, I didn't like the standard 7 and decided to return it. Thought it would be a good idea to lock the bootloader before doing so.
OnePlus support won't help me and they are telling me that I can't return the device anymore. "Repair is the only option now" even though I'm in the 30 days return window.
GoToNap said:
Help. I've made a big mistake. I can only access the Bootloader. Recovery mode is not accessible.
As with the 7 Pro, I didn't like the standard 7 and decided to return it. Thought it would be a good idea to lock the bootloader before doing so.
OnePlus support won't help me and they are telling me that I can't return the device anymore. "Repair is the only option now" even though I'm in the 30 days return window.
Click to expand...
Click to collapse
Try this one.
https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
If thats not working because of locked bootloader, you can try the MSMTool.
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
Note: Never lock the bootloader if system isn't Stock!
Kollachi said:
Try this one.
https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
If thats not working because of locked bootloader, you can try the MSMTool.
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
Note: Never lock the bootloader if system isn't Stock!
Click to expand...
Click to collapse
I keep trying the MSMTool method but nothing happens when I keep both volume buttons pressed...
GoToNap said:
I keep trying the MSMTool method but nothing happens when I keep both volume buttons pressed...
Click to expand...
Click to collapse
Be sure device is off and try to hold the buttons while connecting phone to your computer.
Kollachi said:
Be sure device is off and try to hold the buttons while connecting phone to your computer.
Click to expand...
Click to collapse
OMG it worked. Thank you so much. You saved my life man!
GoToNap said:
OMG it worked. Thank you so much. You saved my life man!
Click to expand...
Click to collapse
Np dude. Good to know if I could help you.
Kollachi said:
Np dude. Good to know if I could help you.
Click to expand...
Click to collapse
Sorry to be a pain in the ass, but I can't really figure out how to get back to OxygenOS now. Everything is in Chinese...
Also, will this procedure mess with anything on my device?
GoToNap said:
Sorry to be a pain in the ass, but I can't really figure out how to get back to OxygenOS now. Everything is in Chinese...
Also, will this procedure mess with anything on my device?
Click to expand...
Click to collapse
Read the unbrick thread. There is all you need.:good:
Kollachi said:
Read the unbrick thread. There is all you need.:good:
Click to expand...
Click to collapse
I've looked through it but couldn't find anything. Sorry, I am extremely stressed out as tomorrow I am supposed to return this phone and I want to make sure that it passes inspection.
So, I did the following:
- Used the unbrick tool which lead me to HydrogenOS
- Installed the latest OxygenOS version on top of it
- Did a factory reset, and so far everything looks to be in working order.
Am I missing anything here? Are there any possible changes done to the device so that it won't pass inspection?
Sorry again for being so annoying...
GoToNap said:
I've looked through it but couldn't find anything. Sorry, I am extremely stressed out as tomorrow I am supposed to return this phone and I want to make sure that it passes inspection.
So, I did the following:
- Used the unbrick tool which lead me to HydrogenOS
- Installed the latest OxygenOS version on top of it
- Did a factory reset, and so far everything looks to be in working order.
Am I missing anything here? Are there any possible changes done to the device so that it won't pass inspection?
Sorry again for being so annoying...
Click to expand...
Click to collapse
So if OxygenOS works and you also did a factory reset, your device should be fine. Check bootloader status. But it should be locked.
Kollachi said:
So if OxygenOS works and you also did a factory reset, your device should be fine. Check bootloader status. But it should be locked.
Click to expand...
Click to collapse
Yes, I'm on the latest OxygenOS version after a factory reset and the bootloader is locked.
Thank you so much man! You are my hero
GoToNap said:
Yes, I'm on the latest OxygenOS version after a factory reset and the bootloader is locked.
Thank you so much man! You are my hero
Click to expand...
Click to collapse
Great. you could report your experience at the other thread. Maybe it helps other people too.:good:
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