Related
So, today I upgraded to 6.0 and had a hell of a time (took me 7 hours) and the problem was that when I installed su from twrp it'd soft brick my phone, anyway, that's not the problem, the problem is everything is saving to /storage/emulated and I can't access it without root. I noticed this when I was on OGInsta and I wanted to download a picture, it gave me an error code about how it couldn't find the directory, so I went to my file manager, everything was fine but I accidentally hit up instead of home and it brought me to an empty page. I started messing with the settings of my file manager assuming something went wrong with it, new version etc, and I found it had a root option. I clicked it and gave it root access and went back and I could see the files where I was previously. To make sure I tried to save something on kik, didn't work. I tried accessing my storage from the rar app and it wouldn't. I don't know what's going on or how it even got this way.
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
scryan said:
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
Click to expand...
Click to collapse
Also, to clearly, I have 2 storage paths. One is "sdcard/" and the other is "storage/emulated/0" I'm not sure if the "storage" folder is new in 6.0, I know 4.+ and 5.+ used "sdcard/". Too see "storage/emulated/0" I need to grant root access to the file manager. And any app the does not have root, cannot access that directory.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
Click to expand...
Click to collapse
you might have knowledge in making apps, but you are missing lots of knowledge when modding your phone. you are going to have to use an app like root explorer, and find where your storage was placed, then move it to the right location. or you can reflash the factory image. ive always just moved my storage back when its happened to me. anyways, flash the factory image the right way, not through a toolkit. then flash any custom kernel(if flashing marshmallow), and supersu.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat.
Click to expand...
Click to collapse
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
YoureVexing said:
So then I used adb, flashed boot.img and then recovery.
Click to expand...
Click to collapse
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
scryan said:
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
Click to expand...
Click to collapse
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
YoureVexing said:
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Click to expand...
Click to collapse
/sdcard is a simlink, its the same folder.
internetpilot said:
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
Click to expand...
Click to collapse
The rootkit wasn't working for me, it's been a charm for my nexus 5 and from 4.+ and nexus 6 on 5.+, on 6.0 it wasn't working so I tried to flash it on fastboot and I still got the same thing. I'll try it once more I suppose, thank you.
Hello everyone,
I have to say I am completely lost regarding the whole rooting process for the XZ1C. I usually manage to get where I want just by carefully reading the forums, but with this device, I feel overwhelmed by information. And I sometimes feel like what I am reading contradicts what I though I understood from previous reads...
I will try to sum up what I know so far.
First of all, I have a just-out-of-the-box Sony model G8441 with firmware 47.1.A.12.179 / Oreo 8.0.0 (never been connected to the outside world yet), and I want to properly root the device and install TWRP with no loss of feature.
What I think I understand:
To root, I first need to unlock the bootloader, which seems to be a trivial operation. However, this will break some functionalities due to DRM keys being erased. Once it is done, there is no way, ever, to get them back. There are however ways to "trick" DRM-related functionalities into believing DRM keys are still there.
Alternatively, there seems to be a way to backup the DRM keys prior to unlocking the BL, and this backup can somehow be reused and injected back into the unlocked device. If true, then this would certainly be a preferable method than the previous one, which would then be obsolete. However, it obviously doesn't look obsolete when I read the related topics, so I must be missing something...
Another thing I noted (but do not quite understand): There are ROMs for this device that "include" a DRM fix.
Last important thing I read: there is a paid "do-it-all" tool which takes my locked device and, with one click, makes it unlocked - rooted - DRM-fixed - TWRP-enabled. Now that sounds really good! Maybe too good?
As far as i know (but I learn new stuff every day on this topic) this DRM stuff is the main difficulty here. I understand that the rest of the process (root + TWRP) will be much simpler (although I'm old-school and completly missed all this magisk trend...!)
What I don't understand:
I read that some people downgrade to Oreo to be able to root properly, and at the same time, I read that Pie removed the restrictions on unlocked bootloader. So I still have no idea if I should connect and receive Sony updates, or avoid them.
Another thing I don't get, is how many ways do we have to root this thing? In the past, I was used to see, for a specific device, always one major and widly used rooting method. Here I fail to identify it...
What I think I will do:
1. Backup TA partition with j4nn's tool. This will probably imply flashing an older firmware right? Is there any link that could help me with this flashing process? (I only know Odin - did I mention old-school?) I saw this page for generic sony Z devices, but the thread is from 2013 and now closed. Is it still up-to-date or is there a newer thread?
2. Unlock bootloader and restore TA partition.
3. Wait for Sony updates? Or should I first hide unlock status?
3bis. Alternaltively to waiting for updates, maybe I can just flash the latest build? (47.2.A.8.24 if I am not mistaken)
4. Flash modpunk's TWRP.
5. Flash janjan's Boot.img to get root functionalities?
Alternaltively to all the above (except maybe step 1 that I will probably do in any case), buy the paid all-in-one tool (Xperifix), plug, click and wait... But will I really end up the same as with the manual way?
I saw a few other methods in the forums but it seems my brain is currently refusing to bring them back...
That's all I have right now. I would really appreciate if you guys could share some insight and tell me what you think about this, whether there are missing steps, useless steps, incorrectly ordered steps, silly steps, or if I'm just completely wrong about the whole thing.
Feel free also to correct me on the assumptions I made at the beginning.
Thank you very much for reading this repulsive piece of text.
SunJu22 said:
I would really appreciate if you guys could share some insight and tell me what you think about this
Click to expand...
Click to collapse
By the looks of it you have done a great deal of research on the project.
Yes, go down the route of backing up your TA partition first, but that is not a small step in itself, it's pretty complicated and if you get that working then the rest of the project will be a breeze.
You don't say what version of firmware you want to end up on. If you want to end up on Pie then forget the DRMfix . But if you're staying on Oreo and can't be bothered with lots of files & flashing, then this is the easy way out, I bought the paid version and can verify it works.
More recently I ended up janjan's kernel (Oreo build). Hidden root (Google Pay works), lots of performance tweaks, DRM completely working.
It's unlikely that anyone will bother making a DRM fix for Pie as the camera works and there are only a couple of other features that get disabled.
It sounds like you're not the sort of person who's only going to read the first couple of pages of a thread (or the last) flash the xxxxxx and then complain when it's broken.
The people on the forum here are very helpful and if you go into any of the threads you mentioned in your post with a question, you'll get a reply.
Good luck.
I agree, there is a lot of information out there and different methods of achieving what you want - very confusing if you have not been following the threads since the beginning.
In my opinion, the preferred method is j4nn's method outlined here: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Use that post as your main guide (the final step in that guide, #13, is how you will achieve root). You will use Newflasher to flash the various firmwares along the way (this is linked from j4nn's procedure in step #2). User munted made a very detailed pdf file that fills in some of the details on j4nn's procedure - see the following post and download the pdf attached: https://forum.xda-developers.com/showpost.php?p=78255334&postcount=382
Most of the other methods out there came before j4nn's work - they didn't include DRM backup/restore.
If you follow j4nn's procedure, you won't need to use the janjan kernel as you assumed - janjan method is different and does not overlap with j4nn.
SunJu22 said:
Feel free also to correct me on the assumptions I made at the beginning.
Click to expand...
Click to collapse
Sorry, I didn't point out that I was one of the early 'jumpers' who unlocked their bootloader without any backups, so I have been forced into always using fixes and all the information I have is based on having to fix your phone for it to work, but that's all changed now. I'm so out of date :-/
@camaro322hp is right, if you follow j4nn's method correctly you'll be rooted with no DRM loss. All of the other stuff is not required.
Thank you Digesteve and camaro322hp for your help.
From what I understand the XZ1C didn't get as much love as other devices, thus there was a long period of tinkering before a "do-it-all guide" could be considered "the" solution. That could explain all these different approaches that are proposed. Like you said camaro322hp it's rather difficult to jump on this train, and I can only guess how interesting this ride has been.
Anyway, I didn't see that the TA backup thread from j4nn also encompassed all the information I needed; I am glad to finally know that there is indeed a centralized "do-it-all guide" . To make it easier for XZ1C newcomers, I think j4nn should update his opening post to make this clearer.
Since I managed to grab the attention of 2 XZ1C power users, I would like to ask you: Did you keep stock? Did you try alternative ROMs? Do you like some of them? Do you prefer Oreo or Pie?
For information, the most up-to-date experience I have on a Android phone is my LG90 with CyanogenMod 11 (KitKat 4.4.4! Yes sir!). I heard that it's becoming less and less useful to flash a custom ROM due to major OS improvements, but I would still enjoy the simplest and lightest Android possible.
SunJu22 said:
Did you keep stock? Did you try alternative ROMs?
Click to expand...
Click to collapse
I've always been on stock, the camera is an important part of what I want from my phone and although there's lots of alternative camera apps, there's no competition to the stock camera app. Then I theme it black with swift installer and just uninstall or freeze any apps I don't want with Titanium Backup. I have stuck with Oreo, everything works perfect and I remember seeing so many people jumping to 9 then wanting to go back to 8 because they didn't like it. Something about changing the way the drop down menu works, among other things, but having never installed it, I'm not the person to comment on if it's any good or not.
I have been watching the XZ1c thread and Lineage is gaining ground, it even has a stock camera now. I would have thought something like that with miniGapps is going to be pretty lightweight and very similar to your carbon rom of before. At the moment this is based on 8, but is working well. Depends how keen you are to move to Pie.
Thank you Digesteve.
One thing I still don't understand. Part of the process is to hide unlock status. If I do this, FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
@SunJu22 I've stuck with the Sony ROM. A rooted stock ROM meets all my needs, so I've never felt the need to experiment with custom ROMs. There are some custom options out there that people seem fairly happy with, so if that's your thing, I'd encourage it.
Without going into too much detail, I'm still on Oreo for the moment, for a variety of reasons, but I don't know of anything that would keep me from recommending Pie.
One thing you should note is that once you unlock, there is no going back. AFAIK there is no known or working method to relock the bootloader.
SunJu22 said:
FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
Click to expand...
Click to collapse
Yes, I'm not entirely sure why having your rooted phone try and update itself is an advantage, but something I'd recomend avoiding.
Stock camera is the Sony camera, yes.
Thank you everyone, I believe I now have enough information to jump into this with confidence. The adventure begins, and will be reported in this thread for future reference, in the hope that it will help others like me!
Well, I am a bit sad... I wanted to report my "adventure" here in detail, but I'm afraid I have nothing to say.
Indeed, following the procedure from j4nn with a printed copy of munted's awesome guide, I managed to do all I wanted on the first attempt.
I don't have anything to add to this guide, everyone wanting to root their XZ1C can do it just by reading the opening post from j4nn and the mentioned guide. It takes a bit of time but nothing complicated thanks to the clear and detailed explanations.
I now have a fully functional rooted XZ1C (including camera) on Pie with Magisk root and TWRP.
Thank you all again from pointing me to the right direction.
I however have a slight disappointment. I wanted to start with Oreo and make an Nandroid backup before moving to Pie, but I didn't find Oreo builds on Xperifirm. So I jumped straight to Pie.
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea?
Last but not least: I looked for the latest Oreo build version number but couldn't find it. Do you guys know what it is and where I can download it?
I guess this will be all for this thread after this. Although it is very convenient to have my own thread to ask questions rather than finding the relevant page for each one, I don't want to annoy you too much...
EDIT: Please ignore the last question. I found out last Oreo build is 47.1.A.16.20, and I found the files via the download link in the opening post of the Lineage thread.
SunJu22 said:
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea? Lineage thread.
Click to expand...
Click to collapse
There is an easy solution to downgrade:
Newflasher
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
mEREHAIGE said:
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
Click to expand...
Click to collapse
No, you can flash a kernel to hide the bootloader unlock flag, this will mean that you will receive OTA updates, although depending on how you're rooted an update will most likely break your phone, so not that useful.
*made a thread*
Thanks--rooted withOUT adventure too
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
kirkzp said:
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
Click to expand...
Click to collapse
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
kernel with hide-unlock
T_Tank said:
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
Click to expand...
Click to collapse
Full disclosure: I don't use Google pay or too many banking apps, so YMMV. But, I am using j4nn's kernel with unlock hidden. (See link in my note 6.) You can flash this, or you can leave in your stock kernel and merely fastboot to this. From what I have seen, it hides most - if not all -- indicators that the phone is rooted and the BL in unlocked.
Does somebody has :
G8441_1310-7123_47.1.A.16.20-R7B_Customized_CE1.ftf ?
Only backup i did not make, and its gone from XperiFirm.
Still have the feeling battery life was better in Oreo, and would be nice for experimenting.
Would be nice.
Thanks in advance.
this is mosty a copy and past cuz i didnt find this part of the forums when i had to remake my acc. if u watch the video u'll see what i did and what i should cuz the how-to for install magisk is broken to say the least
i have a sony xperia z3v and before u ask yes i did follow when was on the xda but NOTHING works as u see in this video here - https://www.youtube.com/watch?v=Jaga6MUcTdc&feature=youtu.be.
so first thing i need is a Custom Recovery. so i follow what that page here - https://www.xda-developers.com/how-to-flash-install-custom-recovery/ says...
first thing it is say i need Android SDK but never once talks about needing it ONE TIME.
2nd, both links given on that page for the custom recoverys 404! - https://imgur.com/bV9egdH
so what do i do next? i follow whats given and BOTH SITE R DEAD! also that page doesnt ONCE going into how to set up a custom recovery at all.
how is that u guys can help me out when it comes to flashing my sony xperia z3v back to stock after i F-ed up on a root and yet not have a set by set for geting Magisk to work install and work on your phone?
You don't need a custom recovery to install Magisk. I'm not gonna sit and watch some video about what you have and haven't done, so I'm not sure what how-to you've been following.
But, I can tell you what instructions you should be following (the official Magisk docs):
https://topjohnwu.github.io/Magisk/install.html
Didgeridoohan said:
You don't need a custom recovery to install Magisk. I'm not gonna sit and watch some video about what you have and haven't done, so I'm not sure what how-to you've been following.
But, I can tell you what instructions you should be following (the official Magisk docs):
https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
yes u do need a custom recovery as said on this page here - https://www.xda-developers.com/how-to-install-magisk/
"What You’ll Need:
A device running Android 4.2+
Custom Recovery (how to install)
We’ll be using TWRP in this guide"
i have the magisk manager already install as is my phone it rooted as u can see in this SS from the phone here - https://imgur.com/a/Kq1EChq but as u see magisk has a red X since its not installed so i go to install it but it give a .zip so i use that and it errors out EVERY ****ING TIME as see here - https://imgur.com/a/VyAslvt
if u toke a few mins of your day to watching the video instead of being a ass and commenting that knowning full well u could have watched the video to see i did everthing that the pages sad u wouldnt be most the comment u just did. u just make yours look like a ass. i want ppl the help me not say "u dont need a custom recovery" when the page on the how to install SAYS U ****ING NEED ONE.
No need to swear or scream at me... I am actually trying to help.
I did not need to watch that video (and didn't feel like spending 12 minutes doing it, would have been better to just link that how-to from the start), since from your post I knew you had not been following the official Magisk docs (that I linked you). If you took a moment to read those you would have seen that you don't need a custom recovery to install Magisk (it can be useful, but you don't need one).
The guide you've been following is outdated (but unfortunately doesn't have a date, so that's hard to know). Take a look at the link I posted above and see if you can figure things out from there.
If you need further help it's just too ask (but without the swearing and screaming, please). It's also possible that you can find some information in my Magisk guide:
https://didgeridoohan.com/magisk/HomePage
You might run into some troubles since you're already rooted with some other root solution, but there's a section about that as well in my guide (if you're using a systemless root that is):
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU
Didgeridoohan said:
No need to swear or scream at me... I am actually trying to help.
I did not need to watch that video (and didn't feel like spending 12 minutes doing it, would have been better to just link that how-to from the start), since from your post I knew you had not been following the official Magisk docs (that I linked you). If you took a moment to read those you would have seen that you don't need a custom recovery to install Magisk (it can be useful, but you don't need one).
The guide you've been following is outdated (but unfortunately doesn't have a date, so that's hard to know). Take a look at the link I posted above and see if you can figure things out from there.
If you need further help it's just too ask (but without the swearing and screaming, please). It's also possible that you can find some information in my Magisk guide:
https://didgeridoohan.com/magisk/HomePage
You might run into some troubles since you're already rooted with some other root solution, but there's a section about that as well in my guide (if you're using a systemless root that is):
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU
Click to expand...
Click to collapse
i saw that page and it makes no since to me. it still says i need a custom recovery also. i dont understand a single think. why cant they make it set-by-set?
let me make it as simple to understand what im looking for. i want to use my Sony Xperia Z3v to game assets dumps for Uta-Macross so i can have pull the 3D models and cards (very nice photos) from the game. to do this i need to have my sony phone rooted and i need to have Magisk so i can hide the root from Uta-Macross so i launch into the game to download the assests to do a dumb. everthing up to this point i have YET to understand what do at all. that link u give - https://topjohnwu.github.io/Magisk/install.html says to this then go here then go here and do this over and over again never saying just do this, this, and this, and your done.
tankball said:
i saw that page and it makes no since to me. it still says i need a custom recovery also. i dont understand a single think. why cant they make it set-by-set?
Click to expand...
Click to collapse
The instructions by @topjohnwu are pretty complete... They do assume that you are somewhat familiar with things like fastboot, but that is information that can easily be found by searching the big ol' interwebz.
Using a custom recovery is one of the ways of installing Magisk. If this is the route you really want to go I suggest you take a look in your device's forum here on XDA:
https://forum.xda-developers.com/z3
That's usually a good first step since you'll likely find others discussing the same device specific topics.
But if you take a look again in the linked docs, you'll find that you can also use something called boot image patching (which doesn't require a custom recovery at all):
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Rooting and tinkering with your device does require a certain level of knowledge about what you're doing. If you can't follow/understand the instructions available there's a good chance you might mess up your device. If you have your data backed up somewhere off the phone (which you should always have when playing with this stuff) you should be good since a complete and catastrophic failure is very unlikely. It's really annoying to have to set everything up from scratch though...
But if you take a look again in the linked docs said:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching[/url]
Click to expand...
Click to collapse
i did see this. witch is want im thinking of doing. by "boot/recovery image" does it mean the stock rom for the phone? if so does this work sice my Xperia Z3v is on 5.1.1? - https://xperiastockrom.com/sony-xperia-z3v-d6708
also right now i went and removed everything from the phone when it comes to rooting, but kingroot (what a stupid name. i also unrooted the phone) and Magisk manager. i cuz i need to reroot my phone and get magisk manager back on my phone?
tankball said:
i did see this. witch is want im thinking of doing. by "boot/recovery image" does it mean the stock rom for the phone? if so does this work sice my Xperia Z3v is on 5.1.1? - https://xperiastockrom.com/sony-xperia-z3v-d6708
also right now i went and removed everything from the phone when it comes to rooting, but kingroot (what a stupid name. i also unrooted the phone) and Magisk manager. i cuz i need to reroot my phone and get magisk manager back on my phone?
Click to expand...
Click to collapse
You'll need the boot image that corresponds to your currently installed firmware/ROM. If that is the firmware you have, then that should work.
You'll need to install the Manager again so that it can patch the image.
A small warning as you progress further: I've seen reports of old Sony devices having issues installing Magisk. Therefore it might be a good idea to visit the Z3 forums (linked in my previous post) and see if there's any information available on this before you continue. Doing proper research before committing always helps in the long run.
Didgeridoohan said:
You'll need the boot image that corresponds to your currently installed firmware/ROM. If that is the firmware you have, then that should work.
You'll need to install the Manager again so that it can patch the image.
A small warning as you progress further: I've seen reports of old Sony devices having issues installing Magisk. Therefore it might be a good idea to visit the Z3 forums (linked in my previous post) and see if there's any information available on this before you continue. Doing proper research before committing always helps in the long run.
Click to expand...
Click to collapse
i should also root the phone again also?
tankball said:
i should also root the phone again also?
Click to expand...
Click to collapse
No. If you want to install Magisk you should not install any other root solution.
Install the Manager.
Patch the boot image.
Flash the patched boot image to your device.
Those are the basics...
Didgeridoohan said:
No. If you want to install Magisk you should not install any other root solution.
Install the Manager.
Patch the boot image.
Flash the patched boot image to your device.
Those are the basics...
Click to expand...
Click to collapse
ok now im lost again. to do date dumps for Uta-Macross i need a rooted phone so i can pull the files without windows again tard and saying "unknow error" when i go to copy the files from my phone. but to play this game i need to hide the root from Uta-Macross so i need to use Magisk. is Masgisk a root itself? im really lost again
Magisk provides a way to do systemless modifications to your device, it is a root solution in itself, and it has the ability to hide itself and it's components from most apps and services that look for a rooted or modded device.
This is kind of the basics, so I reallly suggest you do more research before continuing. The best source for information is the Magisk GitHub page:
https://github.com/topjohnwu/Magisk
Start there, take a look at the readme and the documentation available and continue searching for whatever other information you might need.
I'm not going to be available for further assistance for the next 8 to 9 hours (I hope, but that's entierly up to my little one). G'night.
nothing i did worked. the .zip fail or the D6708_23.4.B.0.319_1288-1477_R30C.ftf file in the .zip witch in the rom from the phone, it will ALWAYS say failed, unsupported/unknow image format.
Morning. Like I posted previously, old (and new) Sony devices have been known to have issues installing Magisk. Search your device's forum for Magisk related posts and you'll likely find the info you need.
Good luck.
This is the first time I've needed to do something like this, so I'm a little confused. I've downloaded the latest firmware update for the Tab S8+ and have patched the AP file with Magisk. However, I'm not sure what to do in order to keep all of my data after flashing it. Is there something I need to change to make this happen? We don't have TWRP yet, so I want to be extra careful in doing this, so I won't have to painstakingly reinstall and reconfigure everything all over again.
From my understanding of this post's step 3, sub-step 9:
If your tablet was already rooted, and you're just updating:
Click CSC and select the HOME_CSC_XXX_XXX.tar.md5
Click to expand...
Click to collapse
Whereas the first time you root you'd use CSC, which would wipe the device. HOME_CSC doesn't wipe the device. I'd go as far as deleting or moving the normal CSC file so that there's less chance you'll accidentally flash it.
Did you have any luck with it? I had successfully rooted with a magisk patched AP. Then I tried to flash an updated firmware, where I also magisk patched the AP file, and I also flashed the HOME_CSC because I wanted to keep my data. This however has somehow resulted in a soft brick. Reflashing to the previous firmware is also not possible as the bootloader had updated from U1 to U2.
Now it seems like my only way out seems to be to reflash the stock AP. Any idea if this would wipe my internalSD?
emko7 said:
Did you have any luck with it? I had successfully rooted with a magisk patched AP. Then I tried to flash an updated firmware, where I also magisk patched the AP file, and I also flashed the HOME_CSC because I wanted to keep my data. This however has somehow resulted in a soft brick. Reflashing to the previous firmware is also not possible as the bootloader had updated from U1 to U2.
Now it seems like my only way out seems to be to reflash the stock AP. Any idea if this would wipe my internalSD?
Click to expand...
Click to collapse
Strange. I've updated twice (after already being rooted) with no issue so far (following the steps here closely). Had you disabled (and updated) any Magisk Modules you had installed before updating, in case there were compatibility issues?
As far as I'm aware, flashing any AP file will not wipe your internal storage, and only flashing the (non-home) CSC will wipe your internal storage. The answer to that question might also depend on what is actually the issue that caused your soft brick if it wasn't just some weird fluke.
Edit: @SavXL answered this question better here. (I was mistaken)
Good luck to you, I hope you salvage your information. I still haven't done this, but I plan on using SyncThing to sync my internal storage with my computer once a day when it's on Wi-Fi. I use Google Photos for pictures and video, but just for anything else, I'd like the extra backup. Of course, I use Swift Backup also, although I back up to the cloud only so it doesn't take up any internal storage space, nor abuse my Micro SD card with heavy file writing.
@emko7 I see now that you posted about this in I believe four threads. I know you are or were in a tough situation - we've all been there before (or a lot of us have), but please don't post looking for help on the same thing in multiple places. PIck an existing thread if appropriate, or create a new Question thread if an existing thread doesn't make sense, and stick with it.
Besides being against XDA Developers Forum Rules , it also created the situation where multiple users are helping you in multiple places, which may be duplicative of each other or at cross-purposes.
Thank you, and still good luck to you!
Rule 5:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
roirraW edor ehT said:
@emko7 I see now that you posted about this in I believe four threads. I know you are or were in a tough situation - we've all been there before (or a lot of us have), but please don't post looking for help on the same thing in multiple places. PIck an existing thread if appropriate, or create a new Question thread if an existing thread doesn't make sense, and stick with it.
Besides being against XDA Developers Forum Rules , it also created the situation where multiple users are helping you in multiple places, which may be duplicative of each other or at cross-purposes.
Thank you, and still good luck to you!
Rule 5:
Click to expand...
Click to collapse
Sorry about that, was just looking for relevant information wherever I could find it.
The only thing I done differently from the guide is that I also flashed the CP file when updating. It displayed PASS. But it just wouldn't boot. I didn't disable any Magisk modules beforehand, didn't occur to me to do that.
I had syncthing setup on my Download folder, and I did make a TitaniumBackup of all of my apps. What I didn't do is backup all of my videos and photos. Had some screen recordings on there that I still needed also.
I was under the impression that flashing a stock rom, or going from root to unrooted would wipe data. It may not, but I'm not willing to test it yet. I also don't really want to wait around for a TWRP release because who knows how long that will take.
The only other thing I've come across that may help is this script that I can flash from recovery. It may need some tweaking to make it compatible with my device and to actually backup the correct partitions. So I'm still trying to figure out if it's a viable option as it's made for a fairly old samsung model originally. This is where I found it.
How to Copy and Delete files in Android Using Recovery Mode?
After rooting my SCH-i589, I did several experiments with my cell phone and several times I faced problems like auto restart due to inadequate or missing
www.isrgrajan.com
emko7 said:
Sorry about that, was just looking for relevant information wherever I could find it.
The only thing I done differently from the guide is that I also flashed the CP file when updating. It displayed PASS. But it just wouldn't boot. I didn't disable any Magisk modules beforehand, didn't occur to me to do that.
Click to expand...
Click to collapse
Would you mind if I ask why you were flashing the CP file?
emko7 said:
I had syncthing setup on my Download folder, and I did make a TitaniumBackup of all of my apps. What I didn't do is backup all of my videos and photos. Had some screen recordings on there that I still needed also.
Click to expand...
Click to collapse
That sucks. When I had SyncThing set up on a different device before, I ended up just syncing the whole root level (and everything below) of internal storage. It was definitely more than I needed to but I knew I didn't only want my Download folder and I didn't have to want to remember to add new folders as my use of the device progressed.
emko7 said:
I was under the impression that flashing a stock rom, or going from root to unrooted would wipe data. It may not, but I'm not willing to test it yet. I also don't really want to wait around for a TWRP release because who knows how long that will take.
Click to expand...
Click to collapse
My experience with newer Samsung devices is definitely lacking. This was the first (rootable) Samsung device I've had since my Galaxy S3 although, from memory, a lot has stayed the same, and I've been used to the Google Pixel process for everything for the last 5 1/2 years.
I would definitely go by how @SavXL answered your question regarding what would wipe your device, as they're definitely more experienced with recent Samsung devices than I am.
emko7 said:
The only other thing I've come across that may help is this script that I can flash from recovery. It may need some tweaking to make it compatible with my device and to actually backup the correct partitions. So I'm still trying to figure out if it's a viable option as it's made for a fairly old samsung model originally. This is where I found it.
How to Copy and Delete files in Android Using Recovery Mode?
After rooting my SCH-i589, I did several experiments with my cell phone and several times I faced problems like auto restart due to inadequate or missing
www.isrgrajan.com
Click to expand...
Click to collapse
Unfortunately, I'm no help in this area. I hope you find a solution that works for you.
roirraW edor ehT said:
Would you mind if I ask why you were flashing the CP file?
That sucks. When I had SyncThing set up on a different device before, I ended up just syncing the whole root level (and everything below) of internal storage. It was definitely more than I needed to but I knew I didn't only want my Download folder and I didn't have to want to remember to add new folders as my use of the device progressed.
My experience with newer Samsung devices is definitely lacking. This was the first (rootable) Samsung device I've had since my Galaxy S3 although, from memory, a lot has stayed the same, and I've been used to the Google Pixel process for everything for the last 5 1/2 years.
I would definitely go by how @SavXL answered your question regarding what would wipe your device, as they're definitely more experienced with recent Samsung devices than I am.
Unfortunately, I'm no help in this area. I hope you find a solution that works for you.
Click to expand...
Click to collapse
I suppose I was just going through the firmware and adding every file, didn't realise I could skip that one.
Yeah not a bad idea using SyncThing on the whole root level. I might do that once I eventually regain access to my tablet.
Thanks for your help
Hi all,
I'm hoping someone here can give me advice on how (or if!) I can recover from a bootloop after a failed Magisk update attempt, without losing the data on my tablet...
My Tab S8 was boot-looping constantly after I tried a Magisk update; trying the plugged-in-volume-up+volume-down trick from this thread gives me the screen with options for Continue, Device Unlock Mode, or Cancel. Before I go any further, I really want to make sure I don't do something that will accidentally wipe all my data!
I'm a long-time Android user and generally just competent enough to follow instructions (like the incredibly helpful howto guide in this forum!) and root my various phones and tablets, but tbh I don't have a full understanding of the various modes and what does / doesn't wipe the data on the device. I have a handful of documents on it that I would really like not to lose, so I don't want to screw this up by choosing options I don't fully understand... Any suggestions will be greatly appreciated!
(Or if someone with actual clue is willing to jump on a web meeting and help me recover it without losing data, I'll gladly compensate you for your time...)
Thank you in advance,
Lisa
Have you tried the Root How-To's instructions to update your firmware without wiping, only using the same version of the firmware your were on already?
Apologies if you already tried that.
Good luck!
roirraW edor ehT said:
Have you tried the Root How-To's instructions to update your firmware without wiping, only using the same version of the firmware your were on already?
Apologies if you already tried that.
Good luck!
Click to expand...
Click to collapse
Thank you! I looked at that, but haven't tried it yet - my concern is that I don't know why the Magisk update failed, so I don't know whether trying the Root How-To's update would run into the same problem. The bootloop is incredibly difficult to interrupt - I had to try the volume up + volume down multiple times before getting the timing right.
If that's the best way to proceed, though, I can certainly give it a shot!
lorenzin said:
Thank you! I looked at that, but haven't tried it yet - my concern is that I don't know why the Magisk update failed, so I don't know whether trying the Root How-To's update would run into the same problem. The bootloop is incredibly difficult to interrupt - I had to try the volume up + volume down multiple times before getting the timing right.
If that's the best way to proceed, though, I can certainly give it a shot!
Click to expand...
Click to collapse
I do believe it's the best option since Magisk needs to be updated in the AP file. You likely need to dirty flash to stock first, if possible (not rooted, without wiping), so that you can have a working system to use the Magisk app to manually patch the AP file, copy the AP file back to the computer as the instructions say, then flash again.
roirraW edor ehT said:
I do believe it's the best option since Magisk needs to be updated in the AP file. You likely need to dirty flash to stock first, if possible (not rooted, without wiping), so that you can have a working system to use the Magisk app to manually patch the AP file, copy the AP file back to the computer as the instructions say, then flash again.
Click to expand...
Click to collapse
THANK YOU for your advice here! I was just able to restore it to the original firmware simply by following the Root How-To's update-without-wiping instructions. Currently debating whether I really want to update it and risk further problems, or just stick with the working firmware... But either way, I was able to recover the documents I need and it's great to have the tablet working again. I really appreciate your help!
Be well,
Lisa
lorenzin said:
THANK YOU for your advice here! I was just able to restore it to the original firmware simply by following the Root How-To's update-without-wiping instructions. Currently debating whether I really want to update it and risk further problems, or just stick with the working firmware... But either way, I was able to recover the documents I need and it's great to have the tablet working again. I really appreciate your help!
Be well,
Lisa
Click to expand...
Click to collapse
You're welcome, glad that helped! I know I was nervous the first time I updated Magisk, but I did it at the same time I updated the firmware. That is, I would've had to update the Magisk app first, so that I could apply that updated Magisk to the new AP file.