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.
Related
Has any one worked out a way of encrypting your note and still be able to run a custom ROM? The warning about this on the safestrap thread has been up for a long time (since KitKat?) and I was hoping that someone might have made some headway into this...
If not, how do I re-root post encryption? I don't even really know what limitations to expect after this process either.
Any help, advice, links, karma loans, anything really would be appreciated!
Cheers
brisinger08 said:
Has any one worked out a way of encrypting your note and still be able to run a custom ROM? The warning about this on the safestrap thread has been up for a long time (since KitKat?) and I was hoping that someone might have made some headway into this...
If not, how do I re-root post encryption? I don't even really know what limitations to expect after this process either.
Any help, advice, links, karma loans, anything really would be appreciated!
Cheers
Click to expand...
Click to collapse
This is what worked for me...
I just flashed my NC2 backup to stock slot, uninstalled safestrap, busybox, unrooted with supersu and rebooted. I ran "quick encryption" with no problems (I didn't try full device) and towelroot worked as usual. Full root access probably defeats the purpose of encryption but that wasn't my call
Boot screen is clean, no custom triangle and I did not run triangleaway
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
LordGrahf said:
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
Click to expand...
Click to collapse
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Thank you sir!
obsanity said:
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Click to expand...
Click to collapse
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
I'm kinda curious myself. I had no idea root killed OTA's. Maybe I wouldn't have done that if I knew that. I'm very new to the Nexus device. It's my 1st. I unlocked the bootloader and rooted already.
Sent from Mark's Nexus 6
crowbarman said:
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
LordGrahf said:
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
Click to expand...
Click to collapse
not sure what you mean by GI, but according to some others, after uninstalling root via SuperSU an OTA will still not install. This should not be the case unless the boot or recovery images are modified. Easily fixed by following the procedures above to fastboot the stock images on your phone.
kjnangre said:
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
Click to expand...
Click to collapse
Yes, it behaves exactly the same.
crowbarman said:
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
obsanity said:
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
Click to expand...
Click to collapse
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
crowbarman said:
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
Click to expand...
Click to collapse
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
obsanity said:
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
Click to expand...
Click to collapse
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
obsanity said:
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
Click to expand...
Click to collapse
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
LordGrahf said:
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
Click to expand...
Click to collapse
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
obsanity said:
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
Click to expand...
Click to collapse
There is an argument that publishing the method would allow Google to close it that much quicker, I suppose.
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
I assume that the encryption doesn't get in the way of being able to flash the images?
When I went from 5.0 to 5.0.1 on my old Nexus 5 all I did was flash the two new 5.0.1 images I extracted from the full factory image, then re-rooted. This is far cleaner than reverting back to the previous image then doing an OTA. I've not had to update my N6 yet so I don't know if my method will work still, but I hope it does.
Chainfire said:
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
Click to expand...
Click to collapse
Thanks for the additional information.
I did spend a fair amount of time reading your documentation but failed to utilize a hex editor. I am not 'whining' about the lack of open source, rather, simply mildly surprised, but your website aptly describes the challenges with 5.0. Many are used to various root methods being available.
Your solution is fine with me.. I love your work.
Edit: I thought I'd add that the discussion has devolved from the OP, which was whether an OTA can be applied after uninstalling root. The answer was no, due to the unknowns about what still might be modified following the uninstall via SuperSU.
Hi All,
When I soft-bricked (long night and stupid choices of tweaking system files), I was unable to boot. Stuck at the Asus logo, at times not even the Asus logo would show. I took a few days but I finally figured it out.
After numerous methods tried and numerous failed attempts, I have narrowed down a successful process for recovering, downgrading and installing Lollipop. Please keep in mind that all cases are unique and this may not work for everyone. The zip folder contains all the tools and firmware builds needed to recover, downgrade, update your tablet.
Please note that this method was only tested on the non-LTE version of the tablet. This method may work if you substitute the firmware files. You can find links to these in the zip.
Another Note. To unbrick, follow the downgrade process. This should unbrick you.
By Clicking Download you agree that I in no way take any responsibility, liability either legally, morally, financially or any other way you could blame me for what you do or these applications do to your tablet or the opposite end of the spectrum, the amount of success to expect. This is at your own risk. I am only providing what I did to resolve my issue in hopes that it may help others.
IMPORTANT: You will lose all you data on the internal memory.
If you agree to the above please feel free to Download (1.87GB)
Key to Download:
!lZ51WKctjkd2v_mUGYz-TacrIResxm45yO5Ztl7k9-I
MD5 Hash
0722035687A42E0F3201147AAF238160
SHA-512 Hash to 100% verify it hasn't been tampered with since MD5 can be easily broken
FBF9C0B7CD88ABAB91B85C2E21B7694FD035D9E92ECE2FC54C6839C07D3FCDB1FAF9FE532920D9B63091412CE13DA9F50F507CC55B7206F516F8DFC8BC021DB5
A lot can go wrong if you don't know what you are doing. If you don't know what you are doing, stop to ask in a forum. You look dumber making a mistake by assuming than asking the most basic of question. So please don't feel embarrassed to ask what may seem obvious or simple. There is also a FAQ below which I will update as needed.
Unfortunately I have to throw this in here:Questions regarding the LTE version will not be answered as I do not have this device.
Huge Credit goes to 4pda members for creating some of these tools that helped me create this all in one zip.
FAQ
Q: Will this void my warranty?
Absolutely
Q: Can you upload only certain files? I don't want to download the large 1.87GB zip.
Sorry, I don't have time to dig through and upload specific folders/files on an individual basis. Someone else however may do so if you ask nicely.
Q: Do I have to install Lollipop or Xposed**?
No, once you are on KitKat, you can stay on KitKat. **Do not install xposed unless you are on Lollipop, won't work anyway since the KitKat image isn't rooted.
Q: Can I take OTA updates?
A: I would advise against it and it will most likely not work or corrupt the device. You should disable/freeze (do not remove) the FOTA Update apk and update apks to make sure you don't receive them by accident.
Q: Can I use this method to install a non-rooted Lollipop firmware image?
A: Untested. Since you can't take the OTA anyway, root shouldn't hurt anything. Just open the SuperSU APK and set it to Deny All if root makes you paranoid.
Q: Will this work for the LTE version?
A: As it is zipped, no. The tools however should work. When I was researching the tools seemed to be device unbiased (except for the firmware). Included in the zip are the original links I used for research. There you can find the LTE version of the firmware images.
Q: Can I share this on other forums?
Sure, just please be sure to keep the zip unmodified and not take credit. The guys on 4pda took a lot of time developing and posting these tools. It took me some time as well to create instructions and gather the required files.
Reserved.
For what I don't know, but just in case.
Successfully downloaded. Thx for the work.
Hello SyCoREAPER, where did you get the firmware and recovery files? I was thinking of using your method for ME176C but I don't have the necessary files. If you can provide some links on where you obtained the files I will search from there. Thanks
NoblyUntruthful said:
Hello SyCoREAPER, where did you get the firmware and recovery files? I was thinking of using your method for ME176C but I don't have the necessary files. If you can provide some links on where you obtained the files I will search from there. Thanks
Click to expand...
Click to collapse
I was debating answering or not. If you bothered reading the above or downloading the files you'd see where they came from.
will give this a go when mine arrives in next day or two
just one question...
is this on the VERY LATEST LP firmware???
Hello. The key to download is not workin. I enter the key exectly as u have it and when I hit OK, it keeps popin back up askin for it again. Is there something I'm doin wrong?
Thank you !
Thank you !!! I've just bought this model ME572c a few days ago. My tablet was bricked (black screen) after OTA update to WW_V12.14.1.12. I've managed to flash with your instructions, but when i try again to OTA update to WW_V12.14.1.12, just after finishing the update, tablet reboots and remains with black screen. I ve tryed to update from SD card (with official firmware and your lollipop firmware) and the same thing happens. Do you have any ideea why is this happening. Thank you very much !!
File download link?
Hello,
Came across this thread as I was planning to revive my old ME572C (5.0.1, getting laggy). Download links no longer work. Any chance you'd reupload the files?
Thanks!
I am super new to rooting I mainly use it for PokemonGo. I am following this video on YouTube.
Basically when I flashed via Odin, I then install Magisk. Then everything is working and rooted BUT when I restart my phone my Magisk is then magically unrooted (I dont know if this is the right term) it says 'Magisk is not installed' and underneath that is says 'Magisk Manager is up to date'
So why does it keep doing this? Everytime this happens I need to Flash again via Odin and do the whole procedure again. This only happens when I restart the phone. Why does it keep doing this and how do I fix this? I will pay someone who can fix this for me. Ive been trying to figure out for the past day and Im going insane. I have no knowledge about rooting etc like i said i just want to play Pokemongo location spoofing.
Appreciate everyones help.
What did that guide say on how to boot up your device? On devices like yours, that matters...
Here's what the official docs/instructions have on that:
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Didgeridoohan said:
What did that guide say on how to boot up your device? On devices like yours, that matters...
Here's what the official docs/instructions have on that:
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Click to expand...
Click to collapse
Hi it says bixy, power and volume up I believe.
littlepuppies said:
Hi it says bixy, power and volume up I believe.
Click to expand...
Click to collapse
You mean from the guide? Yes, as far as I understand that's the combo that you'd need on an s10 (I don't do Samsung). If you look at John's instructions he's covered that prety well.
Are you sure that you are doing the button combo properly? Because if you don't you'll just end up with Magisk not loading during boot and the system will seem to be unrooted.
But, as I wrote above I don't do Samsung so I'm not the best person to give advice about this... You might be better of asking for advice in your devices forum (because there you'll find people who knows the ins and outs):
https://forum.xda-developers.com/s10-plus
Thread closed as duplicate of https://forum.xda-developers.com/s10-plus/help/samsung-s10-plus-everytime-restart-t4099659
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