[Q] Safestrap issue; Can't backup - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

Trying to figure this one out and have done some searching..appreciate the help.
Been saving the Backups to my SD CARD on Safestrap and suddenly I can't - I have over 50 gig of space...When I pick a Slot (Stock or Slot 1) using the new Safestrap..(Thank you!!) and try to BACKUP the screen goes blank for a few seconds and them returns to the same screen. When I reboot and check under my TWRP folder it shows the file name generated but nothing was saved. This happened on the 3.75 a few days before the new apk was released..
Any suggestions are greatly appreciated....
C

Fixed..thanks. .

Related

Problem with nand restore

I had to restore a backup because my G1 was stuck on the G1 screen. I've done restore before and it all worked fine. This time, I got an error...
1. First, I am running CM5.0.8 with 1.0.7 recovery.
2. Went into recovery and tried nand restore and got the following error telling me to running recovery via console using 'nandroid-mobile.sh restore'
3. Went into console and ran it and got the following error:
error: unable to mount /data, aborting
I've tried to use a copy of my backup files that I had on my computer by moving it to the sd card and still get the same errors.
I'm a complete noob and seem to have messed things up trying to learn more!
Any help would be greatly appreciated.
Thanks
It sounds like you might be having a problem with the SD card, take it out and see if the phone boots up. SD cards die all the time and give you various symptoms. If that doesn't work, put 5.0.8 on the card and re-flash it. Sometimes my nandroid restore gives me a error if I have too many backups saved, I just have to mount SD card go to nandroid folder -> (device id) folder -> and there will be a folder for each back-up you have made, get rid of all but the last 2 and run it again. This always works for me.
Sounds more like something happened to the userdata partition.. otherwise the error would indicate /sdcard or a md5sum error. (Not sure what I've seen such things but they where entirely my fault.)
From fastboot screen try running 'fastboot erase system -w' from your computer, booting recovery and trying again.
Thank you for the replies.
I think I messed something up due to user error. I was playing with turning swap on and off via a script I had installed (a great script by a member steveo I think). I turned it on correctly by using swapon30 from the terminal but I didn't turn it off correctly (used swapoff instead of swap-off I think). When the blue led wouldnt turn off, I tried rebooting and got stuck on the G1 screen. (I really have no clue if that's where I messed up but that was what I was doing when it got stuck on reboot).
Anyway, I did a wipe/factory reset then it started up fine. I then went back into recovery and restored my last backup from last night which went fine as well. Only kind of weird thing I noticed was that I had to reinstall Google Maps from the market and now it's showing as installed in "system" whereas before it was showing as "internal".
When I did a factory reset and then ran a recovery, perhaps I needed to reflash the google apps that is part of the original CM5 install?
Appreciate the replies guys!

S5 ATT Active System Help Needed.

Okay Ill Give you the cliff notes to start.
1. I Have The ATT S5 Active, love it.
2. I Rooted it using the method here (HERE
3. Everything was perfect etc, had safestrap, have an sd card etc.
4. Was just using the stock rom slot but messed with the Rom Slots alittle, and an error kept popping up with I would get into the home screen.
5. Wanted to fix it so factory reset etc, BUT
**Problem**
Now I have a phone that boots to to the stock home screen (as if its brand new/ which is completely fine, I can re-root etc.) (so i do not have safestrap or anything)
But as soon as I boot up it shows the error "Unfornatueltly, the process com.android.phone has stopped" and then it will restart. It does does this no matter what
-Ive tried no sim card and/or SD card and it makes no differnece.
I have about 11 seconds from when it boots to when the error appears and restarts.
Any Ideas? PLease. Any kernal I can Odin?
I will paypal someone $5. Im desperate.
Thanks.

[Q] Strange Reboots

Hello!
I have a problem with my Galaxy Note 3:
On a monthly basis, I do a Online Nandroid Backup to my SD-Card.
After encountering a problem with the PlayStore, I booted into Recovery and recovered to my last "good" backup.
Since starting I had weird problems on my phone and I tracked them down to being a problem with the root access.
I used TowelRoot to gain root access again, but the SuperSU app didn't work. I then upgraded the SuperSU app, by deleting the old and installing the new version from the play store.
(After trying the uninstall function within SuperSU which did exactly nothing)
Since then everything kept working fine, but I encounter serious reboot problems.
With no clear time frame, my Note 3 Screen just freezes for 5 sec, and then the phone reboots. Sometimes I can use the phone 1 hour, sometimes 20 min until it happens again.
I have tried to narrow down the problem over christmas, and have the following points:
When I boot up, I have a SD-Card symbol in the notification bar which shows a sd card with a cog wheel in it. As soon as I enter my password it vanishes. Without the SD Card inserted I haven't encountered a problem, and it runs faster. So I reformated the SD Card in my PC to exfat, then reformated it again in my Note 3 and copied all the Data back (over my PC). After using it for 10 min, it rebooted again. I would really like to use my SD Card. 128 GB can't be the problem because it worked beforehand just fine.
In SuperSU I have set the root access to "allow always without questioning". This didn't change anything. I have fixed the Error from KitKat which blocks write/read access to the SD Card. So no problem there.
The problem still persists. And I have no clue what to do.
Tech Details:
Rooted: Yes (with Towelroot), SuperSU installed/working
Branding: None (International Version)
Micro SD-Card: SanDisk 128 GB
Android: KitKat 4.4.2 (Stock)
Recovery: ClockWork Mod 6.1ish (newest)
XPosed Framework installed
1. Factory reset your phone and flash the latest firmware official for your device.
2. Replace the SDCard for other and make some tests.
Joku1981 said:
1. Factory reset your phone and flash the latest firmware official for your device.
2. Replace the SDCard for other and make some tests.
Click to expand...
Click to collapse
Thanks for your fast answer.
As I mentioned above, the SD Card can't be damaged because it worked beforehand. So I think it is not a hardware issue.
As I have recovered from a working Backup it has something to do with the rights/root access and the SD Card.
Factory Reset is not an option for me, because I spent so much time costumizing this thing that it isn't worth doing it all again.
On the other hand:
I am thinking of Flashing CM 11 and doing a Titanium Backup Restore.
Do you think CM 11 would solve my problem?

[Q] note 4 restoring after root help!

Hello! I have a note 4 sm n910f build number n910fxxuanj4.
Recently, I have rooted it, installed twrp and flashed the infamous rom. It does not recognize my Italian sim card, so I decided to restore the phone with twrp from the backup I had previously done ( with twrp) . Then, I tried flashing cm12 with twrp, but it gave me an error, saying that my device was different from the one that should've been used, so it stopped before even trying. I went back to touch wiz after that, and now, I have the following issues: I can't download images / videos or audios from whatsapp , telegram , dropbox or facebook ( they are the only ones I have tried) I can't even send any of those in fact. Also, I can't save any python script with the app
"Qpython" as it either sais that the place where I want to save it is unwritable, or that he can't save it in the temp file ( no idea what the second means...). I though that there was some problem with my sd card...I fact there is: I went to do an sd card data a wipe with twrp, but it would always fail. I then tried to format the sd card from the phone's settings, and that worked, but I still have the same problems I had before. I tried restoring again with my twrp backup, but I every time, the problems remain. I am starting to get a little worried and scared...I don't mind losing all the data, or having to format the entire phone or things like that....I just want to get it working like before... will flashing the stock firmware with odin do any good? Or would that risk bricking the phone ( maybe it tries to wipe the sd and it fails...I don't know)? Is there any other way? Someone please help me! Thanks a lot!

[Q] Restore TWRP Backup - Now Get Incorrect PIN on Lock Screen

Background details:
- I had a good working Galaxy S4 running Stock 4.4.4, with Root/Safestrap/TWRP (Phone was not encrypted)
- I rebooted into Safestrap and did a full TWRP backup to my ext SD card [fat32]
- I tried to install CM-12 zip via Recovery Mode, but I think I missed a step and something didn't work out. So I,
- Rebooted back into Safestrap and selected "Restore" from the options. Restore ran for a while, rebooted and restarted successfully.
Now here's the strange part. Restore appears to have completed successfully because I can now see my original wall paper and the unlock screen. BUT my 4-digit numeric PIN doesn't work to unlock the screen. And it looks like wifi and cell phone service aren't connecting. So I"m stuck. I've tried the known-good PIN multiple times, but same results.
I guess I could Odin back to stock and go through the process of installing all my app's and setting them up, but I really don't want to do that.
Any idea why my PIN would not work or would have changed?
Which Version of TWRp do you use?
I remember that it's a known problem with some Version and the only way to prevent it, is to reset the PIN before backuping.
But you could try to delete the /data/sytem/locksettings.db to reset your PIN
If that not works try to delete the .key files in /system/data and create a new PIN after rebooting

Categories

Resources