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.
I'm about to get an XZ1 Compact and I'm interested in exploring its files. I understand Windows, but Android's terminology is new to me. I'm unsure whether I understand correctly how Android works. Is this right?:
(1) When turned on, a small OS (the "bootloader") powers on, and its objects call
(2) objects in the "recovery partition," which in turn
(3) call the files and objects in the main partition which power the actual Android OS.
To change files in the main partition ("flashing ROM") either the new files' API's must match those in the previous OS or else files in the recovery partition also need to change ("be customized"). Similarly, changing the recovery partition requires either the same API calls from the bootloader or else changing the bootloader ("unlocking" it).
Is all that right? Does this mean doing something like installing TWRP (from the command line on my desktop, where I already have Android Studio and the Android SDK tools) means I have to "unlock" the bootloader too? [Is there a suggested web site or reference, besides this forum, with good info to teach me what I need to know to understand bootloaders, recovery partitions, custom ROMs, etc.?}
Thanks!
Al C.
acolburn3 said:
Is all that right? Does this mean doing something like installing TWRP (from the command line on my desktop, where I already have Android Studio and the Android SDK tools) means I have to "unlock" the bootloader too? [Is there a suggested web site or reference, besides this forum, with good info to teach me what I need to know to understand bootloaders, recovery partitions, custom ROMs, etc.?}
Thanks!
Al C.
Click to expand...
Click to collapse
Hi AI C,
What you described is basically how it works, although the bootloader decides what partition to load the operating system from. The recovery is located in the recovery partition and the bootloader can start it up the same way as an operating system and it allows users control over certain aspects of the phone such as wiping partitions and modifying the currently installed Android.
Here is a site that describes some of the terms:
https://trendblog.net/guide-to-android-rooting-custom-roms-apps/
In order to modify your Android operating system and flash a custom ROM you need to unlock the bootloader as the locked bootloader will only boot your stock firmware (Android OS) that came with your phone.
---------- Post added at 05:28 PM ---------- Previous post was at 05:22 PM ----------
The XZ1 compact is not the easiest device to learn these things with as Sony has locked certain parts of the OS using DRM (digital rights management) which requires a couple extra steps when unlocking the bootloader. Without these DRM keys the camera does not work.
Additionally not all XZ1 compacts bootloader's can be unlocked.
Check this PDF for instructions to unlocking the bootloader and backing up DRM keys:
https://forum.xda-developers.com/xp...-exploits-temp-root-to-backup-t3795510/page39
If you have any specific questions I'm happy to help.
Your explanation makes perfect sense, and those look like really useful links. Thank you for taking the time to respond so thoughtfully. I'd read about the camera issues. Although some folks describe solutions (XperiFix?), I don't think I need Android 10 enough to want to risk flashing it yet. In the meantime, do installing a different recovery (TWRP?) or rooting the device require unlocking the bootloader, too?
p.s. If the answers to those questions are in the links you gave me, I'm perfectly OK being told "go read them!"
acolburn3 said:
Your explanation makes perfect sense, and those look like really useful links. Thank you for taking the time to respond so thoughtfully. I'd read about the camera issues. Although some folks describe solutions (XperiFix?), I don't think I need Android 10 enough to want to risk flashing it yet. In the meantime, do installing a different recovery (TWRP?) or rooting the device require unlocking the bootloader, too?
p.s. If the answers to those questions are in the links you gave me, I'm perfectly OK being told "go read them!"
Click to expand...
Click to collapse
The short answer is yes. You need to unlock the bootloader in order to root and install a custom recovery.
The long answer is that there is a workaround using the Temp-Root solution provided by J4nn: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
that is used to root the phone temporarily so that the DRM keys can be backed up. When you use the magisk version version of the exploit that is linked in the first post you have root access until you reboot the phone.
If you want to get root back you need to connect it to your computer using ADB (android debugging bridge) and send the commands again. Additionally it only works with a few certain android oreo based stock firmwares.
So it is not exactly a workable solution.
I have not heard of XperiFix before. The thread I linked by J4nn and the previous PDF I mentioned is the way that I bootloader unlocked my device and made sure I still have a working camera, although other methods might exist.
I'm glad I could help.
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
Hello,
I have problems rooting in this regard. I made an attempt with Magisk (patched boot.img, as well as flashed these files as well as vbmeta.img in my phone), which seems to have worked, because the program 'Root Checker' shows that I now have root access. Previously hidden system files are also shown to me.
But every time I want to change system files (rename, delete etc.), in the short term the changes are probably shown, but when I restart the phone, changes are gone, and everything is back to the old state, like before the rooting process.
Can anyone help me with this problem. It should also be said, that I am relatively new to this area: So if the answer is a bit more extensive, detailed and understandable step-by-step instructions are very welcome.
I don't know if there has been this problem before; haven't found anything on this exact problem via the search-function now.
If something does exist, please point it out.
Thanks in Advance!
Regards
Gearth-3000
Gearth-3000 said:
Hello,
I have problems rooting in this regard. I made an attempt with Magisk (patched boot.img, as well as flashed these files as well as vbmeta.img in my phone), which seems to have worked, because the program 'Root Checker' shows that I now have root access. Previously hidden system files are also shown to me.
But every time I want to change system files (rename, delete etc.), in the short term the changes are probably shown, but when I restart the phone, changes are gone, and everything is back to the old state, like before the rooting process.
Can anyone help me with this problem. It should also be said, that I am relatively new to this area: So if the answer is a bit more extensive, detailed and understandable step-by-step instructions are very welcome.
I don't know if there has been this problem before; haven't found anything on this exact problem via the search-function now.
If something does exist, please point it out.
Thanks in Advance!
Regards
Gearth-3000
Click to expand...
Click to collapse
Android 10 is locked at read only.
So you can't make changes to system.
Try to use magisk modules according to your desire needs.