Related
Hi everyone
I recently acquired a galaxy s6 smartphone
It soon had an OTA update that upgraded it to Android N(7.0)
I have researched on some topics relating to its root process but most people have complaint of some errors, ranging from failed root to brick, from bootloop to sudden crashing and then restarting normally.
If anyone has successfully rooted this model on Android 7.0 ,please reply.
I would quite the comment up here
Thanks in advance
up this thread, same problem here, cant root, my SM-G920i 7.0
kushfighter2 said:
If anyone has successfully rooted this model on Android 7.0 ,please reply.
Click to expand...
Click to collapse
dashand said:
up this thread, same problem here, cant root, my SM-G920i 7.0
Click to expand...
Click to collapse
@sasabo79 If u didn't root your phone yet
Follow the steps in this video https://youtu.be/BV1ELmu8T0I & that's it.
DO NOT USE supersu. USE & flash Magisk v14.0 (stable) from here https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 Download latest Magisk Manager as well
So the steps are:
From the links in the video, download the specific twrp for g920f/i (g920i is basically g920f except for a network band. So everything compatible for g920f will be compatible for g920i). This one https://eu.dl.twrp.me/zeroflte/twrp-3.1.1-0-zeroflte.img.tar The first file.
Install the Samsung drivers from the link in the video on your pc.
Download & extract Odin.exe.
Enable usb debugging on your phone.
Put your phone to download mode
Start odin. Follow the steps in the video to install twrp
When install is complete, immediately reboot to twrp to flash Magisk v14.0. Wipe Dalvik.
Reboot. Install latest Magisk Manager
Check status in the Magisk Manager.
Done.
If not rooted, flash magisk.zip again in twrp
SuperSu gave problems to some users. Magisk was successfully installed in the first shot!
No need to wipe data etc. Only wipe Dalvik after flashing Magisk. U won't lose any data
Fullmetal Jun said:
@sasabo79 If u didn't root your phone yet
Follow the steps in this video https://youtu.be/BV1ELmu8T0I & that's it.
DO NOT USE supersu. USE & flash Magisk v14.0 (stable) from here https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 Download latest Magisk Manager as well
So the steps are:
From the links in the video, download the specific twrp for g920f/i (g920i is basically g920f except for a network band. So everything compatible for g920f will be compatible for g920i). This one https://eu.dl.twrp.me/zeroflte/twrp-3.1.1-0-zeroflte.img.tar The first file.
Install the Samsung drivers from the link in the video on your pc.
Download & extract Odin.exe.
Enable usb debugging on your phone.
Put your phone to download mode
Start odin. Follow the steps in the video to install twrp
When install is complete, immediately reboot to twrp to flash Magisk v14.0. Wipe Dalvik.
Reboot. Install latest Magisk Manager
Check status in the Magisk Manager.
Done.
If not rooted, flash magisk.zip again in twrp
SuperSu gave problems to some users. Magisk was successfully installed in the first shot!
No need to wipe data etc. Only wipe Dalvik after flashing Magisk. U won't lose any data
Click to expand...
Click to collapse
Is this method safe for my phone
sasabo79 said:
Is this method safe for my phone
Click to expand...
Click to collapse
Yes
So I'm currently using Honor 8 FRD-L09432 on B394 build. I have unlocked bootloader and am rooted with SuperSU. I wish to remove SuperSU root and switch to Magisk. From Magisk thread instructions I'm supposed have unrooted device and intact boot image.
When I try to unroot with SuperSU I'm greeted with "Uninstallation failed!" window. As an alternative to unroot I decided to just use Huawei Firmware Finder and download latest(B394) update.zip and extract stock boot.img from that. After successfully managing the extraction I tried to flash the newly extracted boot.img via TWRP. My device fails to boot with said boot.img so I had to restore the back up.
So my question is what am I missing here? Or is there some other alternate way to switch to Magisk without rollbacking to stock packages and having all my data wiped. Thanks for your assistance.
Osmosis' unsupersu script should work to remove it, then reboot, then flash magisk.
Hi,
I have the FRD-L04 with the B389 update. I am currently root with SuperSU, and I would like to change to Magisk. I have been reading some guides and posts but I want to be sure before proceeding. I found this guide for the Pixel and I would like to know the opinion from the experts if this would work for my honor 8. Thanks!
juanboja said:
Hi,
I have the FRD-L04 with the B389 update. I am currently root with SuperSU, and I would like to change to Magisk. I have been reading some guides and posts but I want to be sure before proceeding. I found this guide for the Pixel and I would like to know the opinion from the experts if this would work for my honor 8. Thanks!
Click to expand...
Click to collapse
You will need stock boot image, that's pretty much all. So you can try to restore the stock boot image via unroot from SuperSU which is a bad idea and I would highly discourage it. So you either extract the stock boot image for B389 from UPDATE.zip or you restore stock boot image from your own backup if you have it.
After obtaining and flashing stock boot image, flash the Magisk zip from main Magisk thread. I can not verify that latest version works (16.0), I havent tried it. I'm personally on 15.3 and if you really want it I can test 16.0 for you.
After flashing Magisk install Magisk manager which you can obtain again from main Magisk thread. Ofc unistall SuperSU app as well.
You can't brick your device in any way as long as you make a full TWRP backup before attempting any of the above. If you run into any of the errors just restore it and ask for further instructions.
Thanks for the set of instructions, I did as instructed and it worked as a charm! Thanks for everything. I'm in B389 with Magisk now!
Sent from my FRD-L04 using Tapatalk
juanboja said:
Thanks for the set of instructions, I did as instructed and it worked as a charm! Thanks for everything. I'm in B389 with Magisk now!
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
Hide function works well with apps that don't work with root, like Google Pay or home banking?
zinko_pt said:
Hide function works well with apps that don't work with root, like Google Pay or home banking?
Click to expand...
Click to collapse
Sorry but I don't use those apps... maybe somebody else can give you feedback.
Most Nexus phones users use magisk in order to be able to have root and xposed and also be able to easily pass safetynet check tests in order to be able to get OTA updates.
Well now magisk 14.4 works on our device and OTA updates should work just fine according to this https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Of course when Android Oreo rom comes out we should wait before applying it just to be sure that magisk and twrp will work on that rom so that we wont be left without root after updating (or brick the device.
I wrote a guide for installing magisk 14.4 on our device having 2nd october OTA installed, i copy it here so that more people can see it.
DISCLAIMER - USE AT YOUR OWN RISK! Bellow steps worked for my device but they might brick yours, you might lose warranty etc.!!!!!!
I am not a developer, I am just a user that wants to have the new phone setup like the older phones in my possession before using it as the main everyday phone.
All below packages are here due to the hard work of the people who made them. If you use them, give them the appropriate credits. This is also the reason that I don't attach any files in this post, I only give links to download the packages on the the forum threads/ sites I also found them.
Here I just show a combination of packages/ programs that worked.
PREREQUISITES:
1) Read the whole guide before starting. Make sure you are familiar with all the terms used and you understand what you are doing in each step.
2) I advise you to firstly download all the needed packages and have them in a folder in your computer and also make a copy of them in your phone and then start with the steps of this guide.
3) In this guide I use a windows pc. Fastboot commands are written in cmd. If you use a pc with another operating system, just make sure you can use adb/ fastboot commands and that you can also use miflash or another tool to flash the rom to your phone.
4) Make sure you have correct adb drivers installed in your pc. For this guide I have used adb-setup-1.4.3.exe from this thread.
So this is the step by step procedure with links:
Flash official rom with miflash
rom image: Here is the latest rom. (tissot_images_7.10.14_20171014.0000.00_7.1_d791bf99f4.tgz is the image I used while writing this guide)
miflash: MiFlash2017-7-20-0.zip
Boot to freshly flashed rom,
Install second october OTA update (75mb),
Do reboot and wait a few minutes until the update is installed.
If you have not done any changes to your device (other root like supersu, old magisk verision etc) you can ignore above step.
From settings-->developer options:
Usb debuging on
OEM unlocking on
Just to be on the safe side for magisk manager app also go to Settings --> Security and enable Unknown sources.
Then shutdown phone, boot phone to fastboot with Vol- & power button,
send the command "fastboot oem unlock" in order to unlock bootloader.
Phone reboots by it self if I remember correctly.
Boot to rom, now being unlocked, and see the splash screen to see if it says "Unlocked" to be sure that it is unlocked.
Then shut down the phone.
Again boot phone to fastboot with Vol- & power button,
boot twrp (just boot, not flash) with command "fastboot boot recovery.img"
recovery-3.1.1-1
From twrp, install Magisk-v14.4-20171103-073038
It installs magisk 14.4 but magisk manager apk version installed with this is 14.0.
So, in order to have magisk 14.4, reboot to rom, uninstall magisk manager and then install Magisk Manager 5.4.0 (as suggested by matcho13579) MagiskManager-v5.0-20170513.apk
The problem now with this version of magisk manager is that it installs modules correctly and they work just fine, but the installed modules are not listed in magisk manager modules page (they work but they cannot be seen). That means that you cannot disable a single module, you have to enable magisk core mode to disable all of them or normal mode to have all modules enabled - I hope this will be fixed in a newer version. Magisk-v14.4-20171103-073038 zip file as I said installs magisk manager 14.0 which also appears to be working, but I did all tests on my device with MagiskManager-v5.0-20170513.apk installed.
Next, inside magisk manager downloads, search and install xposed framework sdk 25 systemless by topjohnwu.
After installation is completed reboot phone (phone boot takes some time at this step).
Then install this Xposed installer apk -material design XposedInstaller_by_dvdandroid_31_10_17.apk.
Now you have October 2nd update rom in your device, magisk 14.4 & xposed framework.
If you select magisk core only mode (which disables magisk modules), have enabled magisk hide and hide it form all apps except the ones you want to have root access, the device passes safetynet and theoretically you can install OTA updates (xposed framework -systemless or not- does not pass safetynet, but being installed systemlessly through magisk, it can be disabled), according to this link
Inside magisk manager you can also install this MiA1Plus_V1.01 module in order to enable camera2api & EIS, to be able to use google camera application.
Finally, i installed gravitybox using gravitybox non-fbe 7.0.4 - 29/10/2017 and it also appears to be working, I have not tested it thoroughly though:
https://forum.xda-developers.com/showpost.php?p=73340439&postcount=2
https://forum.xda-developers.com/attachment.php?attachmentid=4317286&d=1509267532
After installing xposed... Safety net goes fail
Sent from my Mi A1 using Tapatalk
How do I flash stock recovery. I flashed twrp earlier and cannot find stock recovery. There is no recovery.img in the tissot system image.
Aman301582 said:
How do I flash stock recovery. I flashed twrp earlier and cannot find stock recovery. There is no recovery.img in the tissot system image.
Click to expand...
Click to collapse
Recovery is included in boot.img
tidschi said:
Recovery is included in boot.img
Click to expand...
Click to collapse
Which means I'll lose root after flashing ?
Aman301582 said:
Which means I'll lose root after flashing
Click to expand...
Click to collapse
Yes, but it takes 1min to boot to TWRP, flash TWRP and Magisk?
blackyz01 said:
After installing xposed... Safety net goes fail
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
As I have written in the first post "xposed framework -systemless or not- does not pass safetynet, but being installed systemlessly through magisk, it can be disabled"
This means that if you enable magisk core mode which disables all modules or if you disable xposed framework module, it passes safetynet.
tidschi said:
Yes, but it takes 1min to boot to TWRP, flash TWRP and Magisk?
Click to expand...
Click to collapse
Okay, managed to get stock recovery back. But 2nd ota is not installing. Always fails
Why install old Magisk Manager? New one seems like it works, unless I am missing something..
ilpanos said:
Finally, i installed gravitybox using gravitybox non-fbe 7.0.4 - 29/10/2017 and it also appears to be working
Click to expand...
Click to collapse
Only one question about this: why did you choose NON-FBE version instead of the normal one?
Thank you :good::good::good:
this is worked for me
but i have a qu. how we will update next OTA?
matcho13579 said:
Only one question about this: why did you choose NON-FBE version instead of the normal one?
Click to expand...
Click to collapse
Just because unfortunately it seems that FBE is not currently supported on our device and it is using FDE.
Perhaps the normal version also works, but I didn't want to be in a situation where I find out in the future that something doesn't work correctly and I have to uninstall it.
suryaabadsar said:
Thank you :good::good::good:
this is worked for me
but i have a qu. how we will update next OTA?
Click to expand...
Click to collapse
First we have to make sure that magisk works correctly in the new OTA. Then and only then, enable magisk core mode to disable modules and pass safetynet and update according to the instructions in the link I have on the first post.
Will we lose root after an OTA update?
You have to do the procedure as described in the link I have provided in the first post. I am putting it again here:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
ilpanos said:
Just because unfortunately it seems that FBE is not currently supported on our device and it is using FDE.
Perhaps the normal version also works, but I didn't want to be in a situation where I find out in the future that something doesn't work correctly and I have to uninstall it.
Click to expand...
Click to collapse
I'm currently using the normal version and everything is working as intended.
That's why I ask, because it might not work the same way with Magisk (I used CF-Root + SuperSU + standard Xposed method)
ilpanos said:
First we have to make sure that magisk works correctly in the new OTA. Then and only then, enable magisk core mode to disable modules and pass safetynet and update according to the instructions in the link I have on the first post.
Click to expand...
Click to collapse
I HAVE UNROOT PHONE WITH THE SAME METHOD AND RE-LOCK BOOTLOADER WITH FASTBOOT COMMAND fastboot oem lock
NOW OTA WILL WORK PROPERLY ON MY PHONE.?
Thanks for the perfect guide.
One side note: official ROM on the provided link is already version .30, so no need to boot into the ROM and install the updates, the update is already merged in
@ilpanos hello mate! I just ordered my A1 from Trading Shenzhen. I have an clear conception what to do with my A1 when it has arrived. So therefore I am collecting some knowledge about flashing and modding (I am not a beginner, but not familiar with A/B partitions). Your thread is very useful here, many thanks.
I have still one question and maybe you can answer it: i would like to remove the google apps from the system, but I don't know if this works just like usual (to remove it from /system/app or priv-app). The reason is that I am using microG instead gapps.
Or will removing files and folders screw up something?
Thanks in advance!
Cheers!
Well, the thing is that by even mounting system partition as read-write ,and of course doing any change - even adding a line in build.prop - disables the ability to do OTA updates. You will have to reflash the new rom for each update. This is the purpose of this thread, to show that there is a way to mod root etc systemlessly without loosing the ability to update (of course under certain conditions).
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
rcbjr2 said:
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
Click to expand...
Click to collapse
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Qnorsten said:
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Click to expand...
Click to collapse
I seem to have the Canary Update channel set already (I thought it was set to Stable, but I guess not). Doesn't that mean I already have the latest Canary build? Manager shows that latest is 6951d926 (21402) (16) but Installed shows 658d74e0 (21402) (16). I assume this means they are different? Install doesn't seem to update it. Maybe grab the latest APK from Github? Thanks.
Later: Can I install it on my phone by download Magisk v21.4 zip and changing extension to APK and installing it? I thought I read everything is now in the zip/apk? Thanks.
FINAL UPDATE: OK, I downloaded the latest MagiskManager, not the one from Canary. I was then able to patch the boot file. The phone rebooted, but it's not working just right yet. None of my icons show up on my home screen, although if I press the recent apps list, it shows a bunch of apps, although selecting one doesn't do anything. I might have to put the original boot image back on just to get it to boot and worry about rooting later. Sigh. It's always something.
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
You did not have to uninstall Magisk. When you would complete the OTA, instead of rebooting you should go into Magisk and select install to inactive slot. As you uninstalled magisk, you're not getting this option. Uninstalling magisk is different from disabling the modules.
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
alanzaki073 said:
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
Click to expand...
Click to collapse
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Qnorsten said:
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
Click to expand...
Click to collapse
I was looking at a different guide, but will try the one you recommend. I'm aware there is no TWRP for the 8T. I did use that method for my prior OP6. I did patch and flash the patched boot image, but none of my apps appeared on my home page so I flashed the unrooted boot image so I could at least use the phone. Thanks.
rcbjr2 said:
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Click to expand...
Click to collapse
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Kollachi said:
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Click to expand...
Click to collapse
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
rcbjr2 said:
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
Click to expand...
Click to collapse
Nope i mean "fastboot boot xxxxx.img"
Kollachi said:
Nope i mean "fastboot boot xxxxx.img"
Click to expand...
Click to collapse
I figured out that's what you meant when I followed the instructions linked in another message. I had never booted that way previously. Thanks!
I am about to root my 8t using the guide someone linked above. My question is.. I'm on ver. 11.0.5.6.KB05AA will I still be able to root if I update or will it take away the ability to root.. also, will it affect the quality of the root ? Thanks in Advance.
Hey everyone so I have my OnePlus8T all unlocked and ready to be rooted via Magisk. This includes both OEM unlocking turned on and I have successfully gone through the SIM unlock process with T-Mobile.
However....how can I root with Magisk by doing the step of payload dumper without being able to obtain the latest firmware online? I've looked everywhere but looks like T-Mobile keeps it on a tight leash.
Thanks in advance.
kevinco1 said:
Hey everyone so I have my OnePlus8T all unlocked and ready to be rooted via Magisk. This includes both OEM unlocking turned on and I have successfully gone through the SIM unlock process with T-Mobile.
However....how can I root with Magisk by doing the step of payload dumper without being able to obtain the latest firmware online? I've looked everywhere but looks like T-Mobile keeps it on a tight leash.
Thanks in advance.
Click to expand...
Click to collapse
Hello!
As you haven't specified what firmware is installed on your phone at the moment, i see several variants:
1. You can find patched boot.img here on xda for your firmware and boot it, after install Magisk app as usual (Magisk -> Magisk Install -> "Direct Install (Recommended)")
2. If you're unable to find patched boot for your firmware version, you can temporary boot twrp recovery, and install magisk apk with it.
Sorry should have indicated my firmware which is the latest:
11.0.16.18.KB09CB
After doing another search I find no links through Google or XDA
It's possible to use TWRP temporarily even without root?
kevinco1 said:
Sorry should have indicated my firmware which is the latest:
11.0.16.18.KB09CB
After doing another search I find no links through Google or XDA
It's possible to use TWRP temporarily even without root?
Click to expand...
Click to collapse
Yes you can. Follow the process in A.2 of https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
BillGoss said:
Yes you can. Follow the process in A.2 of https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
Click to expand...
Click to collapse
Those instructions apply to the KB2007? I'm not seeing the model discussed anywhere in that thread and don't wanna brick my phone.
If so, when I go through the process to patch the IMG file through Magisk will it wipe the phone like it did when I unlocked the bootloader?
kevinco1 said:
Those instructions apply to the KB2007? I'm not seeing the model discussed anywhere in that thread and don't wanna brick my phone.
If so, when I go through the process to patch the IMG file through Magisk will it wipe the phone like it did when I unlocked the bootloader?
Click to expand...
Click to collapse
The rooting process isn't device specific. And it doesn't wipe your phone.
Also, if you are going to use TWRP, you could take a backup of your phone (see https://forum.xda-developers.com/t/...ect-8t-kebab-2022-03-09.4302449/post-85292199) which you could use to restore your system.
But, as always, there are no guarantees and you do this entirely at your own risk.
And, yes, I understand how scary it is to do these things the first time.