Root? (Solved) - Sony Xperia XZs Guides, News, & Discussion

As the title asks, is there?
If you google all you get are these fake articles with one-click-root, kingeroot etc but afaik you HAVE to unlock bootloader to get root with Sony.
While it's not the end of the world since I got this while I wait for XZ Premium it would still be nice...
Flashed TWRP and then Magisk and now have root.

I unlocked my bootloader and rooted via magisk last night. So far so good

pikeylfc said:
I unlocked my bootloader and rooted via magisk last night. So far so good
Click to expand...
Click to collapse
That's awesome, thanks!

However just realized my camera don't work taking pictures. It's just a green. It only works when I take a picture while recording a video lol

pikeylfc said:
However just realized my camera don't work taking pictures. It's just a green. It only works when I take a picture while recording a video lol
Click to expand...
Click to collapse
Huh really? Also, how exactly did you install Magisk? Did you unlock bootloader, flash TWRP via adb, flashed Magisk via TWRP or how did you install it?
I thought you simply had to flash Magisk in TWRP to get MagiskSU? But apparently not, I have to flash SuperSU and then Magisk to get root.

I just flashed the magisk zip in twrp. That's how I got root

pikeylfc said:
I just flashed the magisk zip in twrp. That's how I got root
Click to expand...
Click to collapse
Thats odd. When I flash it and start the phone I have to update the manager app and then it just say not rooted and that I can download.
Are you on the newest fw? I flashed .235 before but I doubt that makes any difference.
Anything I'm missing? I mean it's not the end of the world since I can just flash supersu, magisk to get root but I want MagiskSU.

Flash this also https://forum.xda-developers.com/crossdevice-dev/sony/patched-magisk-v12-sony-devices-t3582331

pikeylfc said:
Flash this also https://forum.xda-developers.com/crossdevice-dev/sony/patched-magisk-v12-sony-devices-t3582331
Click to expand...
Click to collapse
Sigh, I remember this but totally forgot about it. Thank you so much, it works perfectly now and safetynet passed.

Where did you find twrp for xzs? Or did you flash twrp for xz...?

HellFish23 said:
Where did you find twrp for xzs? Or did you flash twrp for xz...?
Click to expand...
Click to collapse
Yea, TWRP-3.0.2-4-kagura.img works great.

One more little question, there is no need to wipe anything during bootloader unlock, flashing twrp and magisk right?

HellFish23 said:
One more little question, there is no need to wipe anything during bootloader unlock, flashing twrp and magisk right?
Click to expand...
Click to collapse
The phone wipes itself when you unlock bootloader, unavoidable sadly.
So what i did was unlock, flash the newest firmware (.335), flashed twrp and then magiskv12sonyfix (superimportant its the sonyfix, otherwise MagiskSU wont install).

That's a shame... Thanks for the help

pikeylfc said:
However just realized my camera don't work taking pictures. It's just a green. It only works when I take a picture while recording a video lol
Click to expand...
Click to collapse
Hi, I'm new here.
I managed to flash magisk (unlocked bootloader, flashed twrp, then flashed magisk v12 sony fix).
Everything works perfect but both cameras turn green when the photos were taken (not videos).
I tried supersu once before I realized that its not maintained by chainfire anymore. However, I didn't test camera then I started from stock image and use magisk.
I wonder unlocking bootloader (possibly loss of drm key) or rooting causes this issue.
Any workaround or anyone trying camera after unlock?
Also tried Open Camera and it produced same result.
Thanks!
Edit:
I just installed kernel from this thread and camera works now!
I guess its about drm key or RIC protection when bootloader is unlocked.

FartyParty said:
Yea, TWRP-3.0.2-4-kagura.img works great.
Click to expand...
Click to collapse
twrp-3.1.1-0-kagura also works well
Link

Related

Root on Android 7.1 beta

Hey guys, so I installed twrp and formatted data, rebooted, installed super su (sr version), and now my phone is decrypted and rooted on 7.1.1 Just passing this along if anyone needs it
Xdevillived666 said:
Hey guys, so I installed twrp and formatted data, rebooted, installed super su (sr version), and now my phone is decrypted and rooted on 7.1.1 Just passing this along if anyone needs it
Click to expand...
Click to collapse
Screenshots guys
I can confirm CF-Autoroot works without flaws!
I used the Nexus Root Toolkit and that worked a charm, got recovery and root installed easily.
What recovery are you guys using? latest 3.0.2-3?
Krenol said:
What recovery are you guys using? latest 3.0.2-3?
Click to expand...
Click to collapse
I'm using 3.0.2-1 but I have heard people say 3.0.2-2 works as well. Hope that helps
does formatting the data is really needed? I tried to flash twrp with everything on stock (encrypted), it works on first boot of twrp but whenever I boot to system then try to boot to twrp, it gives 'No Command' and I have to reflash twrp again :silly:
RonnellTapawan said:
does formatting the data is really needed? I tried to flash twrp with everything on stock (encrypted), it works on first boot of twrp but whenever I boot to system then try to boot to twrp, it gives 'No Command' and I have to reflash twrp again :silly:
Click to expand...
Click to collapse
It would seem so. Until I decrypted, I wasn't able to keep it permanently installed.
I can also say that Nexus Root Toolkit worked for me. That's a great app - I suggest using it and helping the developer!
Razeer123 said:
I can also say that Nexus Root Toolkit worked for me. That's a great app - I suggest using it and helping the developer!
Click to expand...
Click to collapse
Yeah, it is nice . I just like doing it myself ,though I used the app to flash stock recovery and get the ota.... Speaking of the ota , does anyone else have "android 7.1.1" under about phone ???
I rooted at first with PHH suhide and the only thing I couldn't do was change system files, as expected. Flashed back to stock, updated to dev preview again (clean slate) and installed magisk v8 and root. Everything is working fine and dandy.
Xdevillived666 said:
Yeah, it is nice . I just like doing it myself ,though I used the app to flash stock recovery and get the ota.... Speaking of the ota , does anyone else have "android 7.1.1" under about phone ???
Click to expand...
Click to collapse
Yeah, I think everyone have this number. I suppose the x.x.1 means Security Patch number, but I'm not sure.
I'm new to the beta program. What happens if I root and install a custom recovery in this beta version 7.1.1? I assume that I will no longer be able to get future incremental OTA beta updates?
ToothTooth said:
I'm new to the beta program. What happens if I root and install a custom recovery in this beta version 7.1.1? I assume that I will no longer be able to get future incremental OTA beta updates?
Click to expand...
Click to collapse
You can. Just before installing , reinstall stock recovery and then install ota or use flash fire
Have any of you been able to use SuHide?
Im just getting a constant bootlogo and no further.
Morning all
Just checking in to say I've been running this 7.1.1 preview for over 24 hours, without so much as a slight hiccup. It's very smooth and fluid. I haven't bothered rooting or anything yet as the phone runs beautifully as is, but no doubt I will tinker when I get back from a short break. Only disappointing thing is android pay not working due to unlocked bootloader
Anyone has no-force decrypt boot img, coz seems like device is encrypted, as Im stuck with TWRP(3.0.2-1) logo
odunke01 said:
Have any of you been able to use SuHide?
Im just getting a constant bootlogo and no further.
Click to expand...
Click to collapse
My bad, didnt wait long enough.
Problem is though that we cant seem to keep changes to the /system file on the preview
https://www.reddit.com/r/Android/comments/58npsl/71_appears_to_aggressively_fix_errors_to_the/
odunke01 said:
My bad, didnt wait long enough.
Problem is though that we cant seem to keep changes to the /system file on the preview
https://www.reddit.com/r/Android/comments/58npsl/71_appears_to_aggressively_fix_errors_to_the/
Click to expand...
Click to collapse
What are you using su hide for?
It was for pokemon go.
Although I have reverted to PN on 7.0 as I was having other issues. Root (edit:and recovery) wasn't holding after reboot and my hosts file kept disappearing.
I also missed the night light.

Supersu abort on 7.1.1

Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Guitarboarder28 said:
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Click to expand...
Click to collapse
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
ohlin5 said:
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
Click to expand...
Click to collapse
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Mgrev said:
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Click to expand...
Click to collapse
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Guitarboarder28 said:
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Click to expand...
Click to collapse
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Mgrev said:
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Click to expand...
Click to collapse
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Guitarboarder28 said:
you sound like you need a hug!
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
Click to expand...
Click to collapse
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
ohlin5 said:
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
Click to expand...
Click to collapse
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
dratsablive said:
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
Click to expand...
Click to collapse
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Guitarboarder28 said:
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Click to expand...
Click to collapse
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
dratsablive said:
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
Click to expand...
Click to collapse
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Guitarboarder28 said:
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Click to expand...
Click to collapse
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Guitarboarder28 said:
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Click to expand...
Click to collapse
I didn't think you meant to express hate either!
I seemed to forget to mention that i backed up my data with titanium backup, flashed, then wiped, and then restored it. So in the end, you probably need to wipe (just like you did)
dratsablive said:
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Click to expand...
Click to collapse
Magisk hide just hides Magisk itself... it doesn't do anything for root. As for PoGo, right now the only way to do that on 7.1.1 is to NOT be rooted.
Once the kernel sources for the 7.1.1 are released, this patch will make its way onto custom kernels, which means you'll still be able to edit /system while rooted, unroot, and keep the changes via the patched kernel, as well as bypassing the SafetyNet bootloader check.
A kernel does exist now with that patch (francokernel), but it is based on the 7.0 kernel sources, so some things are broken if used on 7.1.1.
In re: to the superSU ramdisk install failure, this will happen if there are old files left over in /data from a previous magisk install and/or patched boot images. The SuperSU installer script will detect those and step into code branches that it doesn't need to be in, and thus fail. The solution is deleting the offending files from TWRP w/ adb, and installing SuperSU zip again.
/thread
Thread cleaned a bit, please stay on topic.
Have a good day!
Forum moderator,
Matt
Works fine for me flashed 7.1.1 OTA then flashed SuperSU zip

{Guide} How to Root ONEPLUS 3T (Unlock bootloader, TWRP Recovery, SuperSu)

Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting.
1. Download the ADB For Windows from here :-
https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k/view
2. TWRP: https://mega.nz/#!v9MmGQ5C!i5VroRopCVz2_Uoc6Mi2U6N4oDa0HK1SxCrkDrc4mwQ
3. SuperSu: https://mega.nz/#!eh13yLiC!3tkx_RkLg-D8T6mi35zDUB8AYEPLliBsL8yO1dmZbI8
Steps:
1.Backup Data
2.Unlock boot loader
3.Flash Recovery
4.Flash SuperSU
ENJOY
Video:
https://youtu.be/wwd31NU7VC0
Rooting OOS 4.0.3 ONEPLUS 3T
https://youtu.be/0QYp5tkBaao
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Simply flash the full ROM.zip manually in recovery, typically 1.4GB.
That means not installing the incremental mini zips. And not installing from the settings menu.
It's up to you whether you want to wipe data or cache.
Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Download complete zip file n flash using two.
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
yes if u follow the steps you wont have DM verity issuse.
uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
Dm verity zip is not needed when you flash SuperSu.
*winces* Ooh, all the files on file hosts? Why not just link to the legit sites?
Very easy to download the required files. Very simple step-by-step video guide. A+
Thanks for putting this together you made my night!
Thanks, I have unlocked bootloader, Installed TWRP, and Super Su.
one question though, when after setting my account going for nandroid backup there I found SYSTEM as well SYSTEM IMAGE.
what is difference between them, What thing should I backup.
Also there is showing your system is Unmounted, so when I should have to mount it.
Thanks to all Once again.
Hello guys, thanks for the guide!
I was wondering if anyone has faced the same problem as me - while trying to root the Oneplus 3T I constantly get a bootloop after flashing SuperSU. The latest TWRP (3.0.4.0) is installed without any problems in fastboot, the system is mounted as r/w, and I don't see any problems during flashing SuperSU package...
I've tried it before and after OOS 4.0.2, I've tried old and new, stable and beta versions of SuperSU, but either way the phone is stuck on bootscreen after flashing.
P. S. If I flash the official ROM after that - it boots up instantly without any errors... And with no root :/
I'm having the same problem
respectableafrican said:
I'm having the same problem
Click to expand...
Click to collapse
So nice to know I'm not alone!
Did you find a way to root your phone?
Try this SuperSU
I heard only SuperSU SR3 works
Just tried both versions (2.79 and the SR3 beta) - unfortunately, the same bootloop happens.
I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help
nishant.roy24 said:
I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help
Click to expand...
Click to collapse
Power off and boot instead of selecting reboot from twrp
hrsa said:
So nice to know I'm not alone!
Did you find a way to root your phone?
Click to expand...
Click to collapse
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)
respectableafrican said:
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)
Click to expand...
Click to collapse
Oh, finally - thank you so much!
Followed the guide on reddit page, and got the Magisk root, with Android Pay compatibility!
I wonder why it was so hard to find

Video Recording Problem - Audio, but not image

Hi,
I have an A2017U on B29 - Unlocked BL - Root and Xposed
When I record any video, the camera appears to work OK, but when I try to view that video (or if I send the video to someone), I get an start still image, then blank screen for all the video. Audio is OK.
Any ideas?
Thanks!
Are you using a custom kernel?
No, original Kernel.
As soon as I boot (restart the phone), I can take a normal video, but after a few minutes the problem is there again.
gkri said:
No, original Kernel.
As soon as I boot (restart the phone), I can take a normal video, but after a few minutes the problem is there again.
Click to expand...
Click to collapse
I had *exactly* this problem - I believe the only way I could fix it was to reflash the system files totally. Granted, I just had unlocked bootloader (no root or Xposed) so I'm not sure if it's the same issue but yeah I'd suggest just a dirty flash of the B29 system files again and hopefully that'll fix it.
flyer_andy said:
I had *exactly* this problem - I believe the only way I could fix it was to reflash the system files totally. Granted, I just had unlocked bootloader (no root or Xposed) so I'm not sure if it's the same issue but yeah I'd suggest just a dirty flash of the B29 system files again and hopefully that'll fix it.
Click to expand...
Click to collapse
Do you have a link to the files you flashed?
I'm having this issue now and so is @xxosynrgoxx
Thanks!
pOLLYpOCKET said:
Do you have a link to the files you flashed?
I'm having this issue now and so is @xxosynrgoxx
Thanks!
Click to expand...
Click to collapse
Hi - I used the stock System ZIP file from developer DrakenFX. I don't believe I flashed the bootstack...just the stock System ZIP.
You're on B29 right? If so, I'd suggest trying the B29 system links in the following post:
https://forum.xda-developers.com/showpost.php?p=69402127&postcount=113
If you're on B15 Nougat, then the System file in the below post may help:
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Of course, you'll lose root and [if on B29/Xposed] Xposed with the flash of these and you may have to apply a dm-verify disable patch if you're using the B15 ones without root (mine got stuck on the bootloader without that when I manually flashed the B15 file without flashing SuperSU...I believe a flash of SuperSU will resolve this issue though...plus, I could have done something which caused this...not sure).
Good luck! I hope this helps!
Thank you very much. I don't want to lose root though. I'll have to see what else we can do.
pOLLYpOCKET said:
Thank you very much. I don't want to lose root though. I'll have to see what else we can do.
Click to expand...
Click to collapse
Oh you just would have to re-flash SuperSU and [as applicable] Xposed.
Alright, I'll try it and let you know.
Thanks for your help.
OK,
I found the problem (at least my problem).
I rooted, xposed and Safetynet following this treath:
https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
After about 12 flash with different roms Original and ZADMix, and after test different configurations. Is THIS file: SafetyNet-KCAL Kernel patch, that broken the camera (Video):
Finaly I do a clean instal of ZADMix 0.2 ROM, update SuperSU and Install Exposed. I DO NOT PATCH the Kernel and the video recording is working 100%.
Of course, now my phone do not pass the SafetyNet verification.
Anyone are using a Custom Kernel Patched for Safety net on B29??

How to install Root and TWRP (Unofficial) in Android 10 for the OnePlus 6T

I've been stressing all day to fix my 6T. I wiped my phone countless of times and every time I flash TWRP and magisk after, I lose WIFI. I don't know how to fix this, it never happened before. I tried resetting it in settings, nothing happened. I really need WIFI as my data is literally finished. This was after I clean installed 10.3.0. I literally have nothing in my phone and my data is backed up thankfully.
I have found a fix for this. If you have updated to 10.3.0 or new update or going to. Install it via download or local upgrade. and follow this method. Once I followed this method, my WIFI was fixed.
Quote:
Originally Posted by jp0469
Here's the simplest way to upgrade:
1. Flash latest full OTA via Local Updater [DON'T REBOOT]
2. In Magisk Manager, flash latest TWRP installer zip (the one called unofficial installer) from mauronofrio [DON'T REBOOT]
3. Still in Magisk Manager, Install (next to "Magisk is up to date") > Install > Install to inactive slot
4. Reboot
As an update: This method worked when I updated from 10.3.0 to 10.3.1. Everything was working fine.
There is an issue I have found. This method will make your system to boot into slot b, it still works as normal.
But if it bothers you that its slot b and not a, just redo the method again. It worked for me
Hey, thanks for crediting my post. I didn't know this would help with anyone's WiFi issue but I'm glad it did.
jp0469 said:
Hey, thanks for crediting my post. I didn't know this would help with anyone's WiFi issue but I'm glad it did.
Click to expand...
Click to collapse
Yeah, I literally been trying for hours to find a solution online to no provail. Luckily I found your post and I used it as a last resort. I was about to give up at that point. Your method is quite good actually, I can install a new android 10 update, TWRP and magisk at the same time. and reboot with everything there. No more repeated reboots for TWRP and magisk
Same problem
Could not turn my wifi on, couldnt place calls, snap pictures, set alarm. Im so glad i found this post, because it did help me and I didnt lose any data. I was already rooted.
chicoman21 said:
Could not turn my wifi on, couldnt place calls, snap pictures, set alarm. Im so glad i found this post, because it did help me and I didnt lose any data. I was already rooted.
Click to expand...
Click to collapse
Yeah, I honestly haven't found any posts about this. I just used the method as a last resort, I was honestly planning to give up and move to IOS ?.
Installing the 10.3.0 again via local upgrade will just remove TWRP and magisk, but if you follow the method you'll get TWRP and Magisk installed with WIFI working . I thought that using the old method from Nougat, Oreo to Pie would work with Q/10. Nope, now we have found a way to have root with verything working
raghu46j said:
Flashing Custom Kernels will fix the wifi issues,
I'm using BluSpark Kernel.
Click to expand...
Click to collapse
Ok, I didn't know that. But I don't use custom kernels tbh, I like to keep my device close to stock. I just have root, magisk modules, swift black stuff, TWRP, rooted apps which just improve the device and that's fine for me. I'm glad that it worked for you
raghu46j said:
Flashing Custom Kernels will fix the wifi issues,
I'm using BluSpark Kernel.
Click to expand...
Click to collapse
But BT keep disconnected and connected
Extreme_Ninja2099 said:
2. In Magisk Manager, flash latest TWRP installer zip (the one called unofficial installer) from mauronofrio [DON'T REBOOT]
Click to expand...
Click to collapse
I'm confused, how are you flashing from Magisk Manager?
OMGLOLetcetc said:
I'm confused, how are you flashing from Magisk Manager?
Click to expand...
Click to collapse
You can flash TWRP zip in modules. You press on modules, click on the plus button, find your TWRP zip file and press it. Then magisk will flash the zip, but don't reboot
Extreme_Ninja2099 said:
You can flash TWRP zip in modules. You press on modules, click on the plus button, find your TWRP zip file and press it. Then magisk will flash the zip, but don't reboot
Click to expand...
Click to collapse
Ah, that's the issue, I don't have the Modules option.
could anyone be kind enough to lead me to the zip? all i can find is the img for the unofficial twrp
TacTieTee said:
could anyone be kind enough to lead me to the zip? all i can find is the img for the unofficial twrp
Click to expand...
Click to collapse
Its in the download section of the recovery thread. Its called TWRP 3.3.1-30 Unofficial Installer by mauronofrio. Its not hard to find
https://androidfilehost.com/?fid=4349826312261677893
Hello everyone. I'm back. I'm gonna install 10.3.1 on my 6T. I'll try the method and let you guys know
@Extreme_Ninja2099 - How did you get on?
Cam we go straight from a rooted 9.0.17 to rooted 10.3.1 using the above mentioned method?
Static-Noise said:
@Extreme_Ninja2099 - How did you get on?
Click to expand...
Click to collapse
Its at the start of the thread. The method worked from 10.3.0 to 10.3.1. But my slot changed to B. I changed it back to A by re-doing the method again. Everything is fine with 10.3.1.
Goormeetsingh said:
Cam we go straight from a rooted 9.0.17 to rooted 10.3.1 using the above mentioned method?
Click to expand...
Click to collapse
I'm not sure tbh

Categories

Resources