Related
So, I rooted my Zenfone 2 with LineageOs Android 7.1. I could login to Snapchat, it was all cool even though my phone got slower. Then I installed a 3rd party Snapchat app, ''Casper.io'' and logged in to that with my Snapchat ID and password which got me logged out on the official Snapchat app. I uninstalled the 3rd party app, did whatever Snapchat told me to, I reinstalled the official app too. I couldn't login, it's failed. Then I tried to login to my account in a different device. It was successfull. And I don't know what to do now. Read some posts about Xposed Framework etc. There's no Xposed Framework for Android 7. Anybody can help please? It'll be much appreciated.
Thank you.
You need to temporarily disable root to log in to Snapchat. Once you're logged in you're OK.
Same !! did u resolve the issue?
Remove root, clear data on SC, login to SC and verify, re-root phone, create backup of SC so you can restore the logged in version in the future.
Use titanium backup to backup once ur into snapchat and u can restore the backup without logging in, even if you dont pass the safety net.
Snapchat has implemented SafetyNet to its app, which need a special root to access Snapchat, so to access Snapchat:
**WARNING** Your warranty is now void when rooting your phone/tablet! Backup your everything using TWRP cause I am not responsible for anything wrong happens to your device!
* Download your device stock/custom boot.img (kernel) without SuperSU mod and download UnSU.zip from the amazing @osm0sis
* Flash UnSu.zip and Flash stock boot.img in TWRP
* Flash Magisk
* Uninstall Xposed Temporary and Login to Snapchat and install Xposed again OR use Root Switch APK from amazing Corner23 to turn off Xposed with a soft reboot and enable it again with another soft reboot (You Shouldn't use Systemless Xposed, you should use the official one from amazing @rovo89 or the custom one for samsung devices from the amazing @wanam) [Note for Geeks: Wanam Custom Xposed can work on all devices whether Odexed or DeOdexed while Rovo's Official Xposed can work only on AOSP DeOdexed ROMs.]
* To know if you can login to Snapchat, download any SafetyNet Checker from Play Store and you should pass SafetyNet if everything was done correctly else you might have some residual files that detect that you used root before so you might need to start from beginning with stock ROM.
Hope it helps!
Method A
1. Unroot
2. Reinstall Snapchat
3. Login
Method B
1. Grab another rooted device
2. Install Titanium Backup on said device
3. Install Snapchat and login, on said device
4. Use either a MicroSD card or upload a zip file of your 'TitaniumBackup' folder
5. Put folder in root of internal SD card on rooted device
6. Restore backup
7. Launch and enjoy
I actually keep a copy of that zip file both on my computer and my Dropbox. Useful for any future phone and/or tablet!
LexignisOfficial said:
Method A
1. Unroot
2. Reinstall Snapchat
3. Login
Method B
1. Grab another rooted device
2. Install Titanium Backup on said device
3. Install Snapchat and login, on said device
4. Use either a MicroSD card or upload a zip file of your 'TitaniumBackup' folder
5. Put folder in root of internal SD card on rooted device
6. Restore backup
7. Launch and enjoy
I actually keep a copy of that zip file both on my computer and my Dropbox. Useful for any future phone and/or tablet!
Click to expand...
Click to collapse
Amazing!!!!!!!!!!!!!!! life saver, thank you!
Use Magisk root and enable Magisk hide to Snapchat, it should work, works for my sister on here Galaxy S5 (klte)
If coming from SuperSU you'll have to fully unroot before installing MagiskSU
LukeyWolf said:
Use Magisk root and enable Magisk hide to Snapchat, it should work, works for my sister on here Galaxy S5 (klte)
If coming from SuperSU you'll have to fully unroot before installing MagiskSU
Click to expand...
Click to collapse
This is more-or-less time sensitive, Magisk always has to stay updated to bypass Safetynet checks, and Safetynet has to update to bypass Magisk, my method is a lot more usable, and with the Uninstall feature from both Magisk, and with the Uninstall zip for your respected xposed variation, this method should always work, at least until they can start sensing more things like history, and file differences in the system between OTAs.
---------- Post added at 02:01 AM ---------- Previous post was at 02:00 AM ----------
rulezzy said:
Amazing!!!!!!!!!!!!!!! life saver, thank you!
Click to expand...
Click to collapse
Glad to see I could help, I like offering straightforward instructions because I always look for 'em, have fun with your rooted device!
I wasn't able to log in after uninstalling root and several times uninstalling Snapchat and phone restarts. Help
Aemyiam said:
Same !! did u resolve the issue?
Click to expand...
Click to collapse
Login with no root no xposed and make a backup of data with titanium backup
Now you can restore the data and login (with the backup) on all rooted device you want :good:
z300muser said:
Login with no root no xposed and make a backup of data with titanium backup
Now you can restore the data and login (with the backup) on all rooted device you want :good:
Click to expand...
Click to collapse
Titanium backup cannot run on a device without root access.
flamery said:
Titanium backup cannot run on a device without root access.
Click to expand...
Click to collapse
Humm of course ??
Login with no root no xposed than you're logged in snapchat root and make a backup with titanium backup with the save you can login multiple device with root and xposed ?
nothing works anymore for me
it looks like root switch is not doing its job anymore
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
nothing works anymore for me
it looks like root switch is not doing its job anymore
gsm0607455890 said:
nothing works anymore for me
it looks like root switch is not doing its job anymore
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
nothing works anymore for me
it looks like root switch is not doing its job anymore
Click to expand...
Click to collapse
Read solutions in this thread. So many ways to fix it
No one works for me. Otherwise I would not have posted. It worked before yesterday now it does not work anymore with any options
Hi all, none of this is needed. I found it really easy on my Galaxy S4 running the latest Lineage ROM. This looks like a lot of steps, but they're all very simple. and minimal risk.
1. Delete Snapchat.
2. By all means make a full backup just in case.
3. Disable root access in Developer options.
4. Boot to Recovery & wipe Cache & Dalvik cache, but NOT data or system (I use TWRP)
5. Re-flash the current or latest version of your ROM
6. Re-boot - everything will still be there just as it was before.
7. Install Snapchat and log in - you should now have no problem.
7. Restore Root access (if you need it)
Done.
Mavidica said:
Hi all, none of this is needed. I found it really easy on my Galaxy S4 running the latest Lineage ROM. This looks like a lot of steps, but they're all very simple. and minimal risk.
1. Delete Snapchat.
2. By all means make a full backup just in case.
3. Disable root access in Developer options.
4. Boot to Recovery & wipe Cache & Dalvik cache, but NOT data or system (I use TWRP)
5. Re-flash the current or latest version of your ROM
6. Re-boot - everything will still be there just as it was before.
7. Install Snapchat and log in - you should now have no problem.
7. Restore Root access (if you need it)
Done.
Click to expand...
Click to collapse
Instead of dirty flashing your rom, you can just uninstall root or Xposed, login, and reroot/install Xposed. What you're doing takes up far more time.
Actually, you can't do either of those things on a Galaxy S4 running the latest Lineage ROM (or at least I can't). I found this simple, without needing to be a serious android geek, and it worked straight up
I've been all over the OP3T forums looking for current information about the correct versions of TWRP and (Magisk or SuperSU) to use with stock OOS 4.1.6. I kept my old TWRP 3.0.4-1 and when I tried to apply SuperSU 2.79 SR3 I got an unusable system and had to restore from nandroid backup. I updated to TWRP 3.1.1-2 as per the Official TWRP app and now every time I try to reboot to system from TWRP it warns "No OS installed", but the reboot works fine. I have Magisk 13.2 ready to install but I'm reluctant until I know I have the right combination - the TWRP 3.1.1-2 backup is missing some partitions and I want to make sure I can at least recover my system if Magisk screws things up.
I've been all over the forums and all the relevant threads were closed months ago, or are written about OOS 4.0.3 or 4.1.1, or describes some hideous way someone turned their 3T into a pile of molten lava. Is there any current information about what combination of TWRP and a root zip will work with the latest OOS 4.1.6? Everything is stock except the unlocked bootloader. I don't want to flash a different ROM, I don't care about passing SafetyNet, I just want to root and go on with my life.
A couple of numbers is all I ask. I can't be the only one. Please - I've been without root for a week and it's bugging me.
TWRP 3.1.1-2 has got at least one major bug where it reports the OP3T as a OP3. That'll mess up your OP3T specific installations... Don't know if there are any other bugs, since I'm staying on 3.1.1-0 until they fix that bug. You also have the option of using blu_spark's TWRP. I've never tried it, but many users swears by it.
What works for me:
OOS 4.1.6
Franco Kernel r25
TWRP 3.1.1-0 (official)
Magisk v13.2
Magisk Manager 5.0.6
No issues whatsoever (for me)...
Thanks for that. I'd rather not change kernels, though. How likely is it that the same combination works with the stock kernel? Does anyone have that running?
OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."
So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.
Advice?
OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."
So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.
Advice?
Scratch that request. Things seem to be turning around - su works in terminal emulator, lets me ls privileged directories like /data. Root Explorer is working again. The only thing that isn't is AdAway, which can't write the hosts file. Otherwise the system seems to be rooted and working OK.
I'm still nervous that TWRP can't see that there's an OS on the phone, and I haven't seen any other reports of this.
It looks like Magisk can't mount /system read-write. Adaway won't install, and neither will Busybox. Titanium Backup also reports problems. I tried installing Busybox and the installation failed when it tried to remount system /rw.
Will look for solutions to this problem and report back here.
I've found many solutions to this problem, like installing busybox (Stericson Busybox apparently doesn't work in OOS 4.1.6, tried two others. Problem is, busybox will only install into a partition on /system, which requires that /system be read/write.
When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...
JMB2K said:
When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...
Click to expand...
Click to collapse
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.
mobilityguy said:
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.
Click to expand...
Click to collapse
I seem to remember having that problem once before.... Can't recall what I did, I think it involved something with the terminal... I'm not at my desk right now, I'll look into it shortly and see if I can remember
Problem solved. The more I looked at the symptoms, the more I realized that the OTA I took after unrooting with SuperSU corrupted the system partition somehow. The first time I tried applying the OTA with the stock recovery it failed, but I was able to reboot and apply 4.1.6. That's when the trouble began - I was unable to reapply SuperSU. Fortunately I had done a nandroid backup between the upgrade and the attempt to re-root, and after the SuperSU script failed I was able to restore the backup (made and restored using TWRP 3.0.4-1) and continue working. It was either at that point or earlier, during the OTA itself, that /system was damaged - not badly enough to prevent the phone from working perfectly well, but enough to keep TWRP from mounting /system read/write. From that point on I was doomed. None of my other attempts to fix the problem had a chance as long as TWRP was restricted to mounting /system read-only. Then it got worse.
After a semi-failed attempt to install Magisk (rooted applications worked as long as they didn't try writing to /system) I restored my pre-root 4.1.6 backup one more time. After that, TWRP wouldn't mount /system at all, which prevented me from making any more nandroid backups.
It was time to act. I could keep using the phone unrooted, but the longer I went on the more work would be required to put things completely right. The risk would increase because I couldn't take any more snapshots of the phone to fall back to if I munged the device again. I also had a positive reason to fix things - during the two days the phone was rooted but couldn't access /system, Titanium Backup kicked in and did a full backup of all my software and settings.
With a damaged file system and full backups, there was no reason for halfway measures. I copied all my user data off the phone and used LloydSmallwood's unbrick tool to flash the phone back to its original OOS 3.5.4 state. That took care of rebuilding all file structures. As soon as I rebooted, OOS upgraded to 4.1.6 in one step, taking care of the system upgrade. Unlocked the bootloader, installed TWRP 3.1.1-0 (not 3.1.1-2, which has a serious bug for the 3T as someone posted above). I was able to mount and unmount /system from TWRP's mount screen, no problem. Ran Magisk 13.3 script without a problem, installed Titanium Backup, and tested an app restore. No problem. I'm now in the midst of copying all my stuff back onto the phone, after which I'll restore all missing apps and be back in business (I hope).
It's possible I could have done something tricky like reformatting /system and restoring the partition from my last good nandroid backup. But I always would have been concerned that problems would have popped up later, maybe during the Android O upgrade, when it would be way too late to recover my then-current setup. After seeing virtually every combination of working and non-working features, it just made sense to build from a clean system.
So thanks have been given to LloydSmallwood for his absolutely indispensable unbrick tool (this is the second time it has saved my phone). I should also thank my Galaxy S3, running the current build of LineageOS, which has gotten me through the two days it took to set my OnePlus straight. The Galaxy has performed better than a five year old phone running brand-new software should ever be expected to - if it supported LTE I could consider using it as a daily driver. This has been an education, and a reminder of how important it is to keep good backups at every step throughout an upgrade - and routinely during production use.
Thanks to all who gave advice in this thread.
Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?
niko26 said:
Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?
Click to expand...
Click to collapse
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Restoring the stock boot image through the Manager is instantaneous...
Hi @Didgeridoohan,
thank you very much for the quick answers!
Didgeridoohan said:
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
Click to expand...
Click to collapse
Thanks - I didn't know that.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Click to expand...
Click to collapse
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?
niko26 said:
Hi @Didgeridoohan,
thank you very much for the quick answers!
Thanks - I didn't know that.
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?
Click to expand...
Click to collapse
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though. Do you have TWRP installed? That'd be an issue as well...
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.
* DELETED *
Didgeridoohan said:
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though.
Click to expand...
Click to collapse
Yeah, I've been using Magisk's systemless hosts-file.
. Do you have TWRP installed? That'd be an issue as well...
Click to expand...
Click to collapse
TWRP has not been installed permanently.
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.
Click to expand...
Click to collapse
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.
niko26 said:
Yeah, I've been using Magisk's systemless hosts-file.
TWRP has not been installed permanently.
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.
Click to expand...
Click to collapse
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...
Didgeridoohan said:
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...
Click to expand...
Click to collapse
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.
niko26 said:
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.
Click to expand...
Click to collapse
TWRP doesn't mount system as rw unless you let it.
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
For a while there I also flashed the system.img and boot.img files in TWRP. If that months security update only had anything to do with those files it was just a matter of downloading the factory image and unpack those two files and flash them directly in TWRP. No computer needed (unless there was an update to the bootloader and/or radio). No idea if this is viable on a Pixel...
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.
Didgeridoohan said:
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
Click to expand...
Click to collapse
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.
Click to expand...
Click to collapse
What settings are you referring to?
niko26 said:
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
Click to expand...
Click to collapse
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
What settings are you referring to?
Click to expand...
Click to collapse
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.
Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
Click to expand...
Click to collapse
Well, TWRP is gone after an update - I can't boot into it.
[/quote]I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.[/QUOTE]
Hm, I am not sure if I get you right. If it is about apps, I use Titanium Backup to recover my old apps+settings.
system files
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.
Click to expand...
Click to collapse
automattic said:
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Click to expand...
Click to collapse
Since all of the things I mentioned are done with Magisk, none of them will cause an OTA to fail...
Reinstalling system apps will not work, since nowadays an OTA will fail just by mounting /system as rw.
Hi guys, trying to install latest OTA patch for Pixel 2. I am assuming process would be the same. I tried to follow the guide but hit the bump immediately. I can't see "Restore Stock Boot" when pressing uninstall. But there is restore images option. Hitting it does nothing, I receive the message that there are no backups. Where does the backup go so I can put the original file for it to be reinstalled?
I want to do a backup of my android before restoring OOS on the phone (for a test). Was planing to use titanium backup but it seems like the app isn't very good anymore (the reviews are really bad now). Any other ideas? ADB didn't really create that a good backup and I lost WhatsApp and other stuff.
Current setup: lineage 17.1, twerp (latest version) and magisk 20.4.
Just realised I can use twrp for this ??
Eggstones said:
I want to do a backup of my android before restoring OOS on the phone (for a test). Was planing to use titanium backup but it seems like the app isn't very good anymore (the reviews are really bad now). Any other ideas? ADB didn't really create that a good backup and I lost WhatsApp and other stuff.
Current setup: lineage 17.1, twerp (latest version) and magisk 20.4.
Just realised I can use twrp for this ??
Click to expand...
Click to collapse
Two options:
1. Use TB to backup and restore app data and non-bundled/not split apks. Use SAI https://play.google.com/store/apps/details?id=com.aefyr.sai to backup/restore bundled/split apks.
2. Use Migrate https://forum.xda-developers.com/an...stom-rom-migration-tool-t3862763/post78060823
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Two options:
1. Use TB to backup and restore app data and non-bundled/not split apks. Use SAI https://play.google.com/store/apps/details?id=com.aefyr.sai to backup/restore bundled/split apks.
2. Use Migrate https://forum.xda-developers.com/an...stom-rom-migration-tool-t3862763/post78060823
Click to expand...
Click to collapse
I actually don't understand option one but two sounds just the ticket. Thank you.
Eggstones said:
I want to do a backup of my android before restoring OOS on the phone (for a test). Was planing to use titanium backup but it seems like the app isn't very good anymore (the reviews are really bad now). Any other ideas? ADB didn't really create that a good backup and I lost WhatsApp and other stuff.
Current setup: lineage 17.1, twerp (latest version) and magisk 20.4.
Just realised I can use twrp for this ??
Click to expand...
Click to collapse
If you have TWRP, then indeed, adb backup --twrp data should be your friend.
However, extracting TWRP backups on your computer is not that trivial. To do that you need twrpabx, specifically prudy's fixed version. On a Linux computer, it is quick and easy to compile. I haven't tried on Windows.
Else, TWRP backups can only be restored on the same phone (or maybe also on another phone of the same model)
yahya69 said:
If you have TWRP, then indeed, adb backup --twrp data should be your friend.
However, extracting TWRP backups on your computer is not that trivial. To do that you need twrpabx, specifically prudy's fixed version. On a Linux computer, it is quick and easy to compile. I haven't tried on Windows.
Else, TWRP backups can only be restored on the same phone (or maybe also on another phone of the same model)
Click to expand...
Click to collapse
That should be then fine. I just want to try a thing on OOS so no switching of phones intended.
ADB backup I don't think restored the apps data when I tried it which was the main reason for doing the backup
Eggstones said:
That should be then fine. I just want to try a thing on OOS so no switching of phones intended.
ADB backup I don't think restored the apps data when I tried it which was the main reason for doing the backup
Click to expand...
Click to collapse
When you do adb backup --trwp you can add which partitions you want to have backup up:
adb backup --trwp data system boot recovery (haven't checked the names, but data and system should be the most important ones)
Just be mindful that when you do an adb backup --twrp, the backup does not include Internal Files, so make sure to back them up separately or not to wipe them in the first place. I would recommend that after backing up your precious data, you go to "advanced wipe" and there select system, data, cache and dalvik cache. After that, happy flashing..
yahya69 said:
When you do adb backup --trwp you can add which partitions you want to have backup up:
adb backup --trwp data system boot recovery (haven't checked the names, but data and system should be the most important ones)
Just be mindful that when you do an adb backup --twrp, the backup does not include Internal Files, so make sure to back them up separately or not to wipe them in the first place. I would recommend that after backing up your precious data, you go to "advanced wipe" and there select system, data, cache and dalvik cache. After that, happy flashing..
Click to expand...
Click to collapse
I'm doing this with very basic understanding of what I'm doing/being recommended to do. Is adb backup --twrp a command or twice different things as in 'adb backup' to computer and twrp is done on the phone?
My plan is to copy the important data like audio files and photos to my laptop, then use use migrate to make a copy plus twrp backup. I should be fine after that I think.
I'm just hoping my root and magisk doesn't go when I reinstal OOS 9.0.6 as I want to try to edit my system to see if I can force vowife to work.
Eggstones said:
I'm doing this with very basic understanding of what I'm doing/being recommended to do. Is adb backup --twrp a command or twice different things as in 'adb backup' to computer and twrp is done on the phone?
Click to expand...
Click to collapse
That would be a command you have to run in a command line window on your computer. Again, after the --twrp parameter, you can pass the names of the partitions you want to have backed up, which would probably be data, system, recovery and boot.
First, of course, you have to install adb, if you haven't already. But if that's too complicated, it might be easier to make a full backup in TWRP and then copy it over to your computer. adb backup --twrp basically saves a step and you don't have to have sufficient space on your phone for a full backup
My plan is to copy the important data like audio files and photos to my laptop, then use use migrate to make a copy plus twrp backup. I should be fine after that I think.
Click to expand...
Click to collapse
That's always a good idea, even though wiping data in TWRP should not touch your internal files.
I'm just hoping my root and magisk doesn't go when I reinstal OOS 9.0.6 as I want to try to edit my system to see if I can force vowife to work.
Click to expand...
Click to collapse
I don't know, I never used it. I'm happy with LineageOS. I guess you can re-flash Magisk trough twrp and then in your running system, you can re-install the MagiskManager apk. But I haven't tried it.
I would like to keep everything else the same on my phone.
- I don't know if that means I'll have to backup/reinstall everything, if that happens automatically, or what.
- I have the following installed: TWRP 3.4.0.0, Titanium Backup Pro, Frija, Odin, ADB (?)
I currently have "ALEXNDR.N960FXXU6FTJ5" that I got here (based on Android 10)
I think it was from this thread: https://forum.xda-developers.com/t/...ase-v7-4-dex-gear-encryption-support.3847061/
If I want to follow those instructions, should I:
1) do a complete TWRP backup *first*?
2) follow the instructions to update the ROM
3) then restore from Titanium Backup?
As I understand it, the TWRP backup is *ONLY* if I want to restore the entire "disk image" and revert back to the ROM I have now, right?
You can use TWRP restore only if you mess something while flashing kernels, magisk modules, Xposed modules, etc .. it is also useful in your first OEM unlock to preserve vendor and ODM images so that you won't have to flash stock ROM again if something go wrong.
If you are asking about restoring apps, SMS and call logs, I highly recommend swift backup. Not for settings though. Personally, I stopped using titanium backup years ago since it is deprecated and last update was in 2019.