Hi,
Is there a current way to use snapchat on my rooted pixel? I tried unrooting to log in and re-root, but it didn't work as well.
I don't have another rooted device to do titanium back up and I am on android Nougat so I can't install xposed frameworks.
any suggestions people?
unrooting, logging in, and rerooting always works for me....is the app data being deleted somehow when you unroot/root?
Unrooting, logging in and rerooting also worked perfectly for me a couple of times. I don't know any other working method yet.
Don't forget to make a backup of Snapchat with Titanium Backup just after rerooting, so next time you face that issue you can just restore from TiBu.
Hey I just wrote a guide on this. No need to unroot! https://forum.xda-developers.com/pixel/how-to/guide-log-to-snapchat-stock-rooted-rom-t3590473
I'll copy and paste the steps from my thread to here so people can see it. You have to be on stock firmware for this to work.
1. Download the full system image for your device + build (https://developers.google.com/android/images)
This worked on my Pixel, it should work for other Nexus/Pixel/Pixel XL devices as well though.
2. Unzip the file
3. Unzip the image-sailfish-XXXXXX.zip inside the new folder
4. Connect your device to your computer with ADB and reboot to bootloader
5. fastboot boot path/to/boot.img (inside the folder from step 3.)
NOTE: Please make sure to fastboot BOOT, NOT fastboot FLASH.
6. Once booted, log in to Snapchat. It should work.
7. Reboot.
8. Backup Snapchat in Titanium Backup so you don't have to do this again.
Related
how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.
Latest TWRP has MTP mode.
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
You'll need to give us more information.
Why did it fail? Why did your phone stop booting?
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.
how can you copy using twrp while in recovery? are you able to access your PC from recovery?
gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.
ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??
Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty
No. Do a full flash of userdata.img
Please explain
What would I achieve by flashing it?
gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup
Hello,
XT1032 CM 12 latest nightly (I think)
I flashed TWRP v2.8.6.0 using their manager app. I entered recovery mode and everything seemed to work fine. I made a NANDroid backup then rebooted. Unfortunately the device was then stuck at the bootlogo and kept looping. I can still access recovery and fastboot but for some reason adb doesn't see the device, nor can my device's data be access under Windows 7. I don't recall if I had USB debugging on or not. I would like to try to backup a few files to my computer (the backup for instance) but I am unable to since I can't use adb as the device is not recognized. MTP through TWRP doesn't seem to work either. I do have the Universal drive pack installed already on Windows.
Any help would be greatly appreciated. Thanks for your time.
To start with, let's make sure the files you want still exist.
1. Boot into TWRP recovery
2. Go to "Mount" and check that your "Data" partition is selected
3. Go back and then go to "Advanced" and then to "File Manager"
4. Navigate around (maybe /sdcard/ ? Depends what you're looking for) and find the files you need
If you can't find your file, you'll need some more help. Let's say you do see your file. Do you have a USB-OTG cable? You could plug a USB drive into your phone and mount that. Then you could copy your file to that drive. If you don't have the cable you do have some other options, but let us know how far you get.
EDIT: I know I haven't addressed the problem of the bootloop at all. Many of those solutions involve wiping so we need to make sure you've backed up all the files you need first.
First of all thanks for the help. :good:
I've been trying to find a solution and in fact flashing CWM worked. I was able to adb pull all the files and make a backup.
I backed up the content of the sdcard. I tried restoring the CWM nandroid with data only so it did reinstall the apps but unfortunately all their data and settings are gone. Making a full restore just goes back to bricking. So I have the nandroid and the data manually backed up to a computer but no idea how to restore it.
I've tried pushing the nandroid back to /mnt/shell/emulated/clockworkmod/backup after an unsuccessful restore but now it doesn't even work. (protocol failure, the push command fails)
honestly at this point I think the best solution is just to make a clean install. In fact it would be a good idea to just reset the whole phone and start with a clean slate with CM13 including wiping system files and maybe manually restore some key files and configuration (I've got all the .com files of relevant apps)
Do you know how to do that? :laugh:
frustratedwhiteman said:
First of all thanks for the help. :good:
I've been trying to find a solution and in fact flashing CWM worked. I was able to adb pull all the files and make a backup.
I backed up the content of the sdcard. I tried restoring the CWM nandroid with data only so it did reinstall the apps but unfortunately all their data and settings are gone. Making a full restore just goes back to bricking. So I have the nandroid and the data manually backed up to a computer but no idea how to restore it.
I've tried pushing the nandroid back to /mnt/shell/emulated/clockworkmod/backup after an unsuccessful restore but now it doesn't even work. (protocol failure, the push command fails)
honestly at this point I think the best solution is just to make a clean install. In fact it would be a good idea to just reset the whole phone and start with a clean slate with CM13 including wiping system files and maybe manually restore some key files and configuration (I've got all the .com files of relevant apps)
Do you know how to do that? :laugh:
Click to expand...
Click to collapse
I'm not really a Nandroid expert, but I can take a few shots in the dark. When you did your backup you got a TAR file for System and one for Data, etc., right? Then you convert those to IMGs? If you upgraded and then restored the system backup I can see why that would result in a boot loop. Restoring the data image shouldn't cause such problems though. Is this what you've tried so far? You're right, though. The safest method is to manually restore the data of just the apps where you need that data, and do it one at a time. This would allow you to pinpoint what is causing the issue. Of course, I may have no idea what I'm talking about. I've never actually needed to restore a Nandroid backup! Hopefully someone with more experience there will chime in.
I thought to hell with it I went and solved the issue by installing CM13
Thanks for taking the time to help and see you next time
Hey guys! I managed to successfully run Snapchat (9.31.1.0) on my rooted Galaxy S6 6.0.1 MM. I've not yet tested on any other devices, but you're free to try. This is what I did;
1. If you have a secondary android device that's rooted, that'll be good. If not, you can still do this on your primary device.
2. You then go ahead and uninstall xposed framework (make sure you have the files stored somewhere to re-install later on)
3. Download and Install Snapchat from the play store, then log in (you should be able to log in successfully)
4. Create a backup of Snapchat using Titanium Backup. If you're doing this on your secondary phone, transfer the backup files (3 files) into your primary phone (/sdcard/TitaniumBackup/)
5. Re-install xposed framework and reboot your phone.
6. While using Titanium Backup, find Snapchat and select restore -> App + Data
7. Go ahead and open Snapchat. You'll see that you don't need to log in.
Just restore the data in case you accidentally logged out. Feel free to ask me any question if in doubt. Thanks
https://www.youtube.com/watch?v=a-PtwtQFBWg
I made a video on how to increase your snap score. Hope you enjoy it!
Hi there
I always used to have a rooted phone, and most of the time with LineageOS/Cyanogenmod. Rooting is usually the very first thing I do. But since the Mi Note has stupid unlock limitations, I could not do that right when I bought the phone 1.5 years ago. And I let that be til now since there weren't any ROMs for a long time anyway, and I was always scared to lose data since restoring my data without my root backup was kinda scary (as I never did that before). Now it's time and I wanted to ask for the best way to unlock the phone without losing anything.
Is this the way I should proceed? Any suggestion and improvements are very welcome.
1. Copy all internal storage to my computer
Backup all data using the system backup tool to my computer.
Also backup using the google backup.
To be sure create a backup of contacts, phone log etc with "super backup".
2a. download Xiaomi Drivers http://pcsuite.mi.com/
2.b Download the unlock tool from Xiaomi, and unlock it using https://en.miui.com/unlock/download_en.html
3. Install TWRP(+OF_avb_patcher_mauronofrio.zip) & Magisk (after booting into system rename the magisk zip to apk and install it again)
NOTE: to install avb patch I had to start adb and "adb sideload OF_avb_patcher_mauronofrio.zip"
4. Restore everything (whats the best to start with? the google one can only be restored on a fresh install, right? So use that, if anything is missing, use the system backup tool?)
I then might decide to install LineageOS 18.1 (is it the most stable custom rom out there?)
5. Backup again everything a) with nandroid and b) with a root backup tool (is Titanium Backup still recommended? it's the one I used for many years). "Migrate"
6a. Flash latest (21.4.14) Firmware
6b. Flash LinageOS & NikGapps
7. Restore backup and enjoy finally a good rom
If anything goes wrong I can restore original rom with this guide if nandroid restore fails? https://c.mi.com/oc/miuidownload/detail?guide=2
Personally i don't do nandroids so no advice there, but i'd use Migrate instead of TIBU. TIBU is old now. Also when flashing magisk just flash the zip, then after booting into system rename the magisk zip to apk and install it again that way. Their readme will tell you to do it in a more complicated way but in my experience they way i described works just fine.
Also, if it's your first time installing twrp don't forget to flash OF_avb_patcher_mauronofrio.zip afterwards. You can download it in the twrp thread. You will have bootloop or be stuck on logo if you don't.
Thank you very much for this valuable feedback.
Did update the post to reflect that, for anyone finding this topic helpful too.
To see the device in the unlock tool I had to install pcsuite.
I had to sideload the avb patch and magisk in TWRP as the device on windows was mounted but showed a lot of strange folders (98sdjbdpa089j89we) and copy files over did not work.
But now I have TWRP and Magisk on it
I might still did something wrong Used magisk from magisk.me (damn duckduckgo) instead from github. It works but I'm a little scared now. (At least is has the same checksum)
Also SafetyNet does not work (I know the current check does not work but also apps relying on it don't work).
Should I reflash TWRP and install the renamed .apk (as .zip) again?
Edit: just did it, used the canary version with the hope that SafetyNet works, but that didn't change.
And is there that TWRP does not show my internal storage correctly (it works without problems after boot)?
Edit: "fastboot oem reboot-recovery" does not ask for encryption password, "fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img" does and shows the sdcard
dedors said:
I might still did something wrong Used magisk from magisk.me (damn duckduckgo) instead from github. It works but I'm a little scared now. (At least is has the same checksum)
Also SafetyNet does not work (I know the current check does not work but also apps relying on it don't work).
Should I reflash TWRP and install the renamed .apk (as .zip) again?
Edit: just did it, used the canary version with the hope that SafetyNet works, but that didn't change.
And is there that TWRP does not show my internal storage correctly (it works without problems after boot)?
Edit: "fastboot oem reboot-recovery" does not ask for encryption password, "fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img" does and shows the sdcard
Click to expand...
Click to collapse
For safetynet test this
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
I couldn't resist and went ahead with LineageOS, so that problem got solved
I could be mistaken, but it seems as though my G100 has returned to a non-rooted state.
Yesterday morning I was finally able to move the slider for OEM-unlock under Developer Settings.
So I installed Magisk on my device, downloaded a stock firmware using the RSA tool from Lenovo, patched the boot.img using Magisk on my phone, and was able to write that to my phone using the [fastboot flash boot boot.img] command.
And all seemed to be well. I even had my carrier and everything working on it last night and had begun restoring my apps and data with Titanium Backup.
And then suddenly Titanium Backup is reporting it is unable to gain root access. Magisk seems to still believe that the phone is rooted, and Titanium Backup still shows up in it's list. I still see the notification pop up when Titanium Backup launches, saying that it was granted Superuser access. But Titanium Backup has it's own internal popup that says it couldn't acquire root using /system/bin/su
I've tried re-writing my boot.img via fastboot as before, and there is no change in the symptom.
Anyone have any ideas?
I've performed a factory reset on my device, and the command [fastboot flash boot boot.img] again, and it seems to be working.
Titanium Backup is working, but seems to be unable to restore some things. I've reached out to them to see if anything can be done.
After further investigation, it seems the "root" I have obtained so far with the stock ROM is not really root at all. It does allow some root operations, but many are simply blocked on Android 11 by default.
I suspect my only path forward is to install a custom ROM.
Looked into this a bit more and found that disabling the option:
Verify apps over usb
Under developer settings allows Titanium Backup to proceed for most of my restores.
Also, it seems Titanium Backup is deprecated, so that's fun. Edit: Titanium Backup was able to restore most of my applications after the above change, but many of the restored applications simply don't work.
Going to try out Swift Backup.