Database Users

A Safestrap question.

So i have just rooted, unlock bootloader, and flashed TWRP 2.3. Im thinking about installing a rom and i heard of this safetrap recovery thing. I downloaded the razr m safestrap apk, should i install the recovery over TWRP. and also what is the difference, what does it do?

Here is all the info you should need.
I haven't tried safestrap, but my understanding is that it lets you install a rom without needing to unlock your bootloader. Since you are unlocked, safestrap isn't necessary, but it might be still something you want to use. If you feel like playing around with your custom rom, safestrap is probably a good idea, because it will keep your stock rom intact in case something goes wrong.
Unless I'm mistaken, it will let you partition your internal memory and install other roms alongside your stock rom. When you start up, you can boot into safestrap where you can set up a new rom installation and choose which you want to boot into.
I don't use safestrap for a few reasons. Mainly, I install a rom and don't mess with it. If something goes wrong, I have recovery and backups to get everything back to normal. Secondly, the Razr M has pretty limited internal memory, only 4.5GB that you can use. Each rom can easily take up 1GB or more(you set the amount of space given to each rom through safestrap), so installing 2-3 roms doesn't leave you with a lot of space for extra data. Lastly, I have no real need to keep my stock rom intact, I have a twrp backup of it that I can restore to get the same effect. I could keep backups of all the roms I would want to install, and restore to them, getting basically the same effect of using safestrap to have them side by side(although with the added time it takes to wipe/restore). I can also keep my backups on my much larger external SD, keeping my internal memory free for as many apps and data as I could possibly think of. I'm not 100% sure, but I don't think you can use safestrap to set up a new rom running off of your external sd.

stesaint said:
Here is all the info you should need.
I haven't tried safestrap, but my understanding is that it lets you install a rom without needing to unlock your bootloader. Since you are unlocked, safestrap isn't necessary, but it might be still something you want to use. If you feel like playing around with your custom rom, safestrap is probably a good idea, because it will keep your stock rom intact in case something goes wrong.
Unless I'm mistaken, it will let you partition your internal memory and install other roms alongside your stock rom. When you start up, you can boot into safestrap where you can set up a new rom installation and choose which you want to boot into.
I don't use safestrap for a few reasons. Mainly, I install a rom and don't mess with it. If something goes wrong, I have recovery and backups to get everything back to normal. Secondly, the Razr M has pretty limited internal memory, only 4.5GB that you can use. Each rom can easily take up 1GB or more(you set the amount of space given to each rom through safestrap), so installing 2-3 roms doesn't leave you with a lot of space for extra data. Lastly, I have no real need to keep my stock rom intact, I have a twrp backup of it that I can restore to get the same effect. I could keep backups of all the roms I would want to install, and restore to them, getting basically the same effect of using safestrap to have them side by side(although with the added time it takes to wipe/restore). I can also keep my backups on my much larger external SD, keeping my internal memory free for as many apps and data as I could possibly think of. I'm not 100% sure, but I don't think you can use safestrap to set up a new rom running off of your external sd.
Click to expand...
Click to collapse
Thanks for the info! I'm going to stuck to flashing and making backups with TWRP
Sent from my XT907 using xda premium

Some questions about Galaxy Tab 2 7.0 and root/ROMs, etc.

Just got a GTab 2 7.0 a few days ago. A P3113, so only 8GB of storage, about half of which is the ROM and crap apps. I've rooted before (had a KF 1st gen when it came out), and just wondering about a few things with the GTab:
Right now, I don't mind the stock ROM so much. There are problem things that would be "nice to have", but right now, would like to generally stay as "stock" as possible. That being said, I'd still like to "de-crap" the ROM to free up some storage space, and I assume that might lead to it running a bit better, since so much seems to just pop-in while running other apps. So:
I know I need to root first, so my first question - how reliable is that? I'm on a Mac, but have access to a netbook running Win7, so could run Odin to "get things done". I'd hate to brick the thing, still having 51 weeks of warranty left. (I also understand that I might want to install something else to keep the flash count from showing it's been flashed).
Once root'ed, is it better to use one of the "de-crapped" ROMs floating around? And if so, which seems "best" (yeah, I know the moderators hate the "which is best" - I'm looking for stock - and STABLE)
Or, is it better to eliminate the apps myself? (Not sure if this is a wholesale "rm" to remove certain apps from a terminal app, using adb, or if they have some uninstallers embedded somewhere, or...) - so better to use one of the ROMs floating around?
Is the GTab 2 "stable", so even if you trash a ROM, you can still get into the ROM manager to restore a previously working, or stock, ROM?
I'll probably come up with a couple more questions, especially depending on the replies... TIA

Hi..
I can answer some of your questions. I hope that helps!
1- Rooting is easy and reliable. you may use "CF-Auto-Root" tool (search for it in XDA forum).
But you need to remember that rooting and custom ROMs void your warranty.
2- If you just need to free some storage space, you may use an app such as "Clean Master" to uninstall system apps and get rid of temp and junk files.
3- If you opt to use a custom ROM make sure it is very well supported and maintained.

aisais said:
Hi..
I can answer some of your questions. I hope that helps!
1- Rooting is easy and reliable. you may use "CF-Auto-Root" tool (search for it in XDA forum).
But you need to remember that rooting and custom ROMs void your warranty.
2- If you just need to free some storage space, you may use an app such as "Clean Master" to uninstall system apps and get rid of temp and junk files.
3- If you opt to use a custom ROM make sure it is very well supported and maintained.
Click to expand...
Click to collapse
Thanks - but prior to using Clean Master I assume I better either get a stock image to reload, or use CWM so I can make a backup of the ROM before messing something up?

tundrwd said:
Thanks - but prior to using Clean Master I assume I better either get a stock image to reload, or use CWM so I can make a backup of the ROM before messing something up?
Click to expand...
Click to collapse
Taking a backup is always good thing to do. I suggest you try clean master to know how it works and what does it do.

aisais said:
Taking a backup is always good thing to do. I suggest you try clean master to know how it works and what does it do.
Click to expand...
Click to collapse
Thanks - I plan to use Clean Master. Allows me to be selective about what I remove/move, instead of getting a ROM from someone and they removed the ONE THING I really wanted.

Ok, got it rooted and CWM installed.
HOWEVER, when I boot into CWM, I DON'T see an option to backup my ROM (I've used TWRP before on my KF, so the menu is different).
What I've got on my screen in CWM:
Android system recover <3e>
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache​
That's it. Where's the option to do a ROM backup? Oh, used file P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip Had CWM and Root all in one. I do have GT-P3113_ClockworkMod-Recovery_6.0.1.0.tar as well. Should I just go through procedure again to flash this CWM? Will it still retain SU?

nandroid backup ok to use? Seems it's just a wrapper for a backup script...

Ok - I'll reply to myself.
I don't know what was wrong with the CWM I installed via the aforementioned file (P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip), but I went to the CWM site, D/L'ed the latest touch enabled CWM for the P3113 (6.0.2.3, I believe), and installed it over the existing recovery image on the device (I had to create my own .tar.md5 - easy with *nix).
Anyway, I now have access to the backup options by scrolling down. The image from P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip, simply wouldn't scroll beyond what I listed earlier. Now can scroll down, make backups, etc.
Haven't tried yet to re-install the image I made with nandroid - I'm a bit leery of that - so I'll just get the stock 4.1.1 ROM from sammobile, and keep it around....

tundrwd said:
Ok - I'll reply to myself.
I don't know what was wrong with the CWM I installed via the aforementioned file (P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip), but I went to the CWM site, D/L'ed the latest touch enabled CWM for the P3113 (6.0.2.3, I believe), and installed it over the existing recovery image on the device (I had to create my own .tar.md5 - easy with *nix).
Anyway, I now have access to the backup options by scrolling down. The image from P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip, simply wouldn't scroll beyond what I listed earlier. Now can scroll down, make backups, etc.
Haven't tried yet to re-install the image I made with nandroid - I'm a bit leery of that - so I'll just get the stock 4.1.1 ROM from sammobile, and keep it around....
Click to expand...
Click to collapse
That's exactly what I did today, grabbed the stock image for a backup, rooted with Odin and CWM then flashed a CM based 4.3 ROM. Piece of cake.

[Q] Simplified Root Instructions?

This is the first time I've ever rooted an Android device. The process has been fraught with uncertainty and misinformation from around the internet. I'd like to describe what I have come to understand is the current preferred method, and ask a few questions to hopefully get my S5 where I want it to be.
I don't want to do anything to crazy (yet, anyway). I just want to remove some bloat and get the notification panel as close to vanilla Android as possible.
So far, I have ran towelroot, which was incredibly simple.
I installed SuperSU from the Play Store. During installation, it got stuck at "Disabling KNOX...". I have since learned that this is common and a reboot usually fixes it. However, I have also learned that I probably don't want to disable KNOX yet anyway, since I am not going to flash a custom ROM until there is one that is known to be stable and is able to create the vanilla Android experience that I want. Some people said that I should have installed SuperSU from chainfire's page instead of the Play Store, but I think that was old information.
Edit: I'm editing these steps as I go along:
1. Install busybox and the Safestrap APK
2. Use Safestrap to set up a new ROM slot and use that slot from now on (consider the italics a strikethrough)
^Even though the instruction video on the Safestrap page said this, apparently that's not what most people do. They use Safestrap to make a nandroid backup, and then use only one slot, the stock ROM slot, to experiment or flash a new ROM.
3. Install Titanium Backup
Edit: I also had to install SD KitKat Fixer and then reboot afterward to allow TB to write to the SD card...
4. Use Titanium Backup to backup all apps and data to SD card
5. Use Titanium to freeze processes that I carefully choose
Edit: I froze everything from the list here.
6. Install Xposed framework
7. Find the modules to customize Android how I want
Does that sound right? Any tips/advice?

ergalthema said:
So far, I have ran towelroot, which was incredibly simple.
Click to expand...
Click to collapse
By doing this, you are rooted.
Even if you are not going to flash a custom rom, you can and probably should disable KNOX. Doing so will not trip the counter.
Install busybox and the Safestrap APK - This is indeed necessary if you want to install another ROM to customize. The whole point of safestrap is to flash ROMs and is not related to rooting itself. The other use of Safestrap is to create a complete backup of your current system so that if you mess something up, you can restore to a known, working state.
Use Safestrap to set up a new ROM slot and use that slot from now on - This is fine if you want to switch between ROMs. I know some people like to do this, but I am not one of them.
Install Titanium Backup - absolutely
Use Titanium to freeze processes that I carefully choose - correct and there are threads with lists of APKs to freeze. You will also want to make sure you freeze SDM so that it doesn't prompt for security updates.
Use Titanium as a backup? (not sure about this) - this is to backup your apps, texts, things like that but NOT your ROM
Install Xposed framework
Find the modules to customize Android how I want

jcollier said:
Install busybox and the Safestrap APK - This is indeed necessary if you want to install another ROM to customize. The whole point of safestrap is to flash ROMs and is not related to rooting itself. The other use of Safestrap is to create a complete backup of your current system so that if you mess something up, you can restore to a known, working state.
Use Safestrap to set up a new ROM slot and use that slot from now on - This is fine if you want to switch between ROMs. I know some people like to do this, but I am not one of them.
Click to expand...
Click to collapse
The first step in installing Xposed in this thread is to do a nandroid backup. I'm not totally sure what that is, but someone in another thread said implied that Safestrap essentially does the same thing. That is why I was planning to use Safestrap.

ergalthema said:
The first step in installing Xposed in this thread is to do a nandroid backup. I'm not totally sure what that is, but someone in another thread said implied that Safestrap essentially does the same thing. That is why I was planning to use Safestrap.
Click to expand...
Click to collapse
That is what I meant by this: "The other use of Safestrap is to create a complete backup of your current system so that if you mess something up, you can restore to a known, working state."
A nandroid is a backup image of your system so that you can restore it if you screw something up. Safestrap isn't "essentially" doing the same thing, it is doing exactly that thing. Safestrap is a way to make a custom recovery work on our phone without an unlocked bootloader.

Good advice up to here, but you might want to hold off on using Exposed. As I understand it, Exposed lets you tinker with the existing stock ROM. I don't think I would want to do that, and I have rooted and ROM flashed several Android devices over the years. But its up to you.
With your being new to rooting, I'll offer this advice:
Titanium Backup (a.k.a. "TIBU") is a good way to back up all your apps. Here are some suggestions in using it:
--Buy the PRO version. It has more features, is not very expensive, and helps support a really cool app that is very handy.
--Set the Preferences/Backup folder to your REAL external SD Card. It will default to internal storage (also called "sd card"....don't get me started lol) which is IMO totally useless. If you lose internal storage due to corruption or whatever, you would lose all your backups. Having them on the REAL SD card you can also archive them to your PC.
--Set your Max Backup History to some number larger than the default "1". I use 7. Why? Well, have you ever seen the developer of one of your favorite apps suddenly screw it completely up in some update? Or, worse yet, sell out to some other vendor who now made it a PAY SUBSCRIPTION app?? I have. By keeping multiple backups you can roll back in time to previous versions that you know WORKED when those things happen. I have several apps I will never update, especially on the Store, for various reasons. (TIBU used to be able to disconnect the link to the Store so apps didn't try to update, but Google broke their ability to do that).
--When you do make TIBU backups, select "app and system data" which is IMO incorrectly worded and causes confusion. It should read "app and APP data". Because that is what it really does. Backs up the data IN your system that is associated ONLY with the APP. NOT any "system files". When you restore a backup, restore "app and system data" and you not only get the app installed, you get all your data it created, as well as all your customized settings restored! It is a real time saver. And you can "usually" even do this with a new device, using the TIBU backup folder on an SD card you had in some previous Android device. I've done it many times.
Safestrap installs a custom version of TWRP recovery. From that you can make the aforementioned "nandroid" backups of your complete system. (You won't see the word "nandroid" in TWRP while you are doing this. It just calls them backups). Couple of caveats with TWRP (and the Safestrap version):
--The date/time stamp used in both TWRP and its alternative, Clockworkmod Recovery (CW) will always be wrong. I've read (in short) there is no way for them to fix it. BUT........you most certainly CAN edit the backup file name to be whatever you like while setting it up to make the backup. So I recommend deleting the portion of the name that is the screwed up date it will generate, and putting in a date you can read, like my preferred format of 2014-07-10-1727 which is today at 5:27 PM, or whatever format you like.
--By default, TWRP recovery uses (in the Advanced settings) an inane "power saving" feature of the display, which will maddeningly keep turning it off and making you think the phone died while it is in the middle of making your backup. A - ALWAYS keep your phone on the charger when working in Recovery!! Don't even start unless it has at least 40% charge. B- Turn OFF the inane "power saving feature" and get some peace of mind. The screen will stay lit forever, until you reboot system when you are done.
--By default, TWRP will be set to use INTERNAL STORAGE as the place to keep your nandroids. Again, I consider that a very bad idea. Use a REAL External SD card and keep them there. And make regular backups to your PC of the SD card. I've seen a great many SD cards suddenly fail without warning. Your device will pop up and tell you the SD card is corrupt, and you need to format it. Usually, there is no way to recover the lost data on the card when that happens.
--On my Galaxy S5, making a nandroid of the stock OS via Safestrap took up over 4GB! That is almost 4 x what I normally see making a nandroid of a custom ROM on some previous device. So make sure you have plenty of room on whatever SD card you choose to use.

jcollier said:
Even if you are not going to flash a custom rom, you can and probably should disable KNOX. Doing so will not trip the counter.
Click to expand...
Click to collapse
I didn't know it wouldn't trip the counter. I'm curious why I should disable it though.

I followed the video exactly and when I get to the point of the first Restore (around 9:00), it says "Restore Complete - Failed". There is a button to Reboot System. When I tap that, the phone won't turn on. I have to pull the batter to get it back on. I guess I'll be uninstalling Safestrap. If I "Uninstall Recovery" from the stock ROM slot, will the space be freed up again and the phone be returned to the same state as before I tried using Safestrap?

ergalthema said:
I followed the video exactly and when I get to the point of the first Restore (around 9:00), it says "Restore Complete - Failed". There is a button to Reboot System. When I tap that, the phone won't turn on. I have to pull the batter to get it back on. I guess I'll be uninstalling Safestrap. If I "Uninstall Recovery" from the stock ROM slot, will the space be freed up again and the phone be returned to the same state as before I tried using Safestrap?
Click to expand...
Click to collapse
May I ask what it is that you are restoring? Have you already made a (nandroid) backup? That's what the restore function is made to restore. If you tried to use Restore on some other kind of file, then it would try to overwrite your ROM (OS) with it, and make the phone unusable. If that happens, I think your only fix would be to Odin back to stock and start over from scratch. I believe there is a link to do that in the thread telling how to root the S5.

Zoandroid said:
May I ask what it is that you are restoring? Have you already made a (nandroid) backup?
Click to expand...
Click to collapse
The video at 9:00 explains it. I think it is basically flashing the backup I made of the stock ROM to the newly created ROM slot in order to begin running from the new ROM slot.

ergalthema said:
The video at 9:00 explains it. I think it is basically flashing the backup I made of the stock ROM to the newly created ROM slot in order to begin running from the new ROM slot.
Click to expand...
Click to collapse
Oh, OK. Since there aren't any ROMs available yet, I did not pursue that aspect of Safestrap. So you have stepped outside my range of experience with it. Hopefully someone else can help you.
If you get to a point in your endeavors where you find a solution to apply ad-blocking to the S5, please let me know in a PM. I've had no luck so far. It appears this will be yet another issue that will only be solved with some creative developer work. Google has done something in KitKat to block not only apps like Ad-Aware and Adblock Plus from working, they also seem to have some kind of snooper utility that, if you try to search online with the S5 for ad blocking, will pop up a browser page saying Google "cannot access" the page! Pages which my PCs can see easily. Crafty little PITAs for sure! I thought it might just be Chrome doing this, so when I tried to get Firefox from the Store, I was stuck in an endless downloading loop. I had to kill that and restore a copy from TIBU. They are doing everything they can think of to lock down a smartphone and spoon feed us only what THEY want us to see. Including copious advertisements.
There was a time when Android meant "freedom". I guess that time has passed. Now it is time for someone else with very deep pockets to re-kindle a hassle-free smartphone OS. It is a shame. Android has so much potential.

ergalthema said:
The video at 9:00 explains it. I think it is basically flashing the backup I made of the stock ROM to the newly created ROM slot in order to begin running from the new ROM slot.
Click to expand...
Click to collapse
Why flash the stock ROM in a newly created ROM slot? You should only create a ROM slot if you decide to run a custom ROM. If not, you can use safestrap to create the backup (nandroid) and save it to your SD card so you always have a "safe" restore point essentially. I run a custom ROM in my stock slot. And for the record... There are several ROMs in the development section which are quite stable. Also, you can check out the Safestrap thread there as well. If you read through the thread you'll have a better understanding of how it works and what bugs there are right now.
The thing that I find great about XDA is that folks will always try to help each other out. Good luck!
Sent from my SM-G900V using XDA Premium 4 mobile app

Do we have a thread where folks are reporting having tried various versions of the available ROMs for the Verizon S5, and can make a simple statement about what works and what doesn't? I think that would be a really good idea. Without something like that, the only way to really know which ones are trouble free is to slog through and read each and every post on every ROM thread, most of which will usually be outdated information anyway.
Maybe it could be done as a Poll so it doesn't grow into something just as long to read as the above.

Zoandroid said:
Do we have a thread where folks are reporting having tried various versions of the available ROMs for the Verizon S5, and can make a simple statement about what works and what doesn't? I think that would be a really good idea. Without something like that, the only way to really know which ones are trouble free is to slog through and read each and every post on every ROM thread, most of which will usually be outdated information anyway.
Maybe it could be done as a Poll so it doesn't grow into something just as long to read as the above.
Click to expand...
Click to collapse
That would be great - especially for the people who aren't on this site all day and don't know what is good and current.
shoresteve626 said:
Why flash the stock ROM in a newly created ROM slot? You should only create a ROM slot if you decide to run a custom ROM. If not, you can use safestrap to create the backup (nandroid) and save it to your SD card so you always have a "safe" restore point essentially. I run a custom ROM in my stock slot. And for the record... There are several ROMs in the development section which are quite stable.
Click to expand...
Click to collapse
I'm realizing that's probably what most people do. In the instructional video posted on the main Safestrap OP, it instructed to keep the original stock slot intact, and use a new slot for experimenting with another ROM. I would love to know a stable ROM that gives the most vanilla Android.

AllianceRom Issues Verizon GS5 4.4.2

After searching for a fair while i've come to the conclusion that there aren't any threads that pose my set of issues. I've tried installing AllianceRom several times, i follow their instructions to the letter, and everytime i end up with a failed extraction, i've re-downloaded the ROM twice now and am simply unsure of how to continue, i would LOVE to see their rom in action and how it functions i'm just at a loss for how to continue, steps i take with safestrap as such.
1. Reboot into recovery
2. switch to rom-slot 1 (also tried the other numbers.. just in case)
3. create the slot, wipe it
4. install zip file ( tried from different folders, on both internal and sd storage)
5. facepalm i'm not sure what to do now i'm slightly sad because it's the seemingly coolest looking rom, there's so much customization options to it.. i just want it hopefully someone out there has an answer, and if not i'll let the subject die for now, thanks for your time to anyone whom reads this.
-brando

brando5055 said:
After searching for a fair while i've come to the conclusion that there aren't any threads that pose my set of issues. I've tried installing AllianceRom several times, i follow their instructions to the letter, and everytime i end up with a failed extraction, i've re-downloaded the ROM twice now and am simply unsure of how to continue, i would LOVE to see their rom in action and how it functions i'm just at a loss for how to continue, steps i take with safestrap as such.
1. Reboot into recovery
2. switch to rom-slot 1 (also tried the other numbers.. just in case)
3. create the slot, wipe it
4. install zip file ( tried from different folders, on both internal and sd storage)
5. facepalm i'm not sure what to do now i'm slightly sad because it's the seemingly coolest looking rom, there's so much customization options to it.. i just want it hopefully someone out there has an answer, and if not i'll let the subject die for now, thanks for your time to anyone whom reads this.
-brando
Click to expand...
Click to collapse
Have you tried flashing to stock slot yet? rom slots have many known bugs as of now and most ROM devs recommend flashing to stock slot and avoiding rom slots.

MrHyde03 said:
Have you tried flashing to stock slot yet? rom slots have many known bugs as of now and most ROM devs recommend flashing to stock slot and avoiding rom slots.
Click to expand...
Click to collapse
I have not, all honesty i'm super new to the entire process and thus far I haven't done that because i still use my stock rom on occasion flipping back and forth between the two and I'm primarily terrified of bricking my phone. What process would i go through to get my stock rom backed up and assuredly not going to be screwed out of it not existing before i tried flashing to the stock slot? I know i sound paranoid because i really am especially after it not working =/

Possibly figured it out
If i'm correct, i now know the issue. the file site dropped some people's network connections, and i'm guessing since my file size was only ~650 mb that was my issue, if not i'll inform you otherwise i'll be deleting the thread, thank you mr. hyde

brando5055 said:
I have not, all honesty i'm super new to the entire process and thus far I haven't done that because i still use my stock rom on occasion flipping back and forth between the two and I'm primarily terrified of bricking my phone. What process would i go through to get my stock rom backed up and assuredly not going to be screwed out of it not existing before i tried flashing to the stock slot? I know i sound paranoid because i really am especially after it not working =/
Click to expand...
Click to collapse
1. Reboot to safestrap
2. Activate stock slot
3. backup -> data and system should be checked only
4. Wipe data/factory reset option
5. Install -> romfile.zip
6. Reboot.
If you want to be safer, after step 3 backup, reboot back to your system and copy the backup folder from external sd/ TWRP/######/backup folder. This way you'll have a backup on your computer in case something breaks. The nice thing is, safestrap is safe and won't (shouldn't..) brick your phone.
EDIT: just saw your recent post. yes, the alliance rom zip file should be 1gb or greater.

MrHyde03 said:
1. Reboot to safestrap
2. Activate stock slot
3. backup -> data and system should be checked only
4. Wipe data/factory reset option
5. Install -> romfile.zip
6. Reboot.
If you want to be safer, after step 3 backup, reboot back to your system and copy the backup folder from external sd/ TWRP/######/backup folder. This way you'll have a backup on your computer in case something breaks. The nice thing is, safestrap is safe and won't (shouldn't..) brick your phone.
EDIT: just saw your recent post. yes, the alliance rom zip file should be 1gb or greater.
Click to expand...
Click to collapse
Well, it worked (go figure i feel like a dumbass), however after all of it i realized looking at oyur name that you seemed familiar for some reason. The first ROM i flashed, was yours. Thanks for that, it's very well made.

Need help/overwhelmed! Noob flashing to GPE 5.0.1?

Hi,
I want to install the ROM here on my Samsung Galaxy S4 (GT-I9505). I rooted and installed CM on it about 4 months ago, but since have forgotten anything about the process except for towelroot lol. My phone is currently running jflte snapshot M10 ROM for CM. Unfortunately, I have grown quite sick of it as I find I have to restart my phone once, maybe twice a day for everything to run smoothly. I run into problems where the WiFi likes to get stuck saying 'Turning on..'. Ive also been having problems with Google Maps and GPS lately and havent been able to rely on it, possibly its an issue its having with CM. I want to have the fresh Lollipop feel on my phone without any problems if possible. The only trouble is I dont know how to get there. Can anyone help me? Ive completely forgotten the process needed and when I try to look for it on here I am overwhelmed with things I need to do, which version I need to use etc etc. If anyone would be able to help me achieve this it would be greatly appreciated. In the end I just want a nice Lollipop android phone that doesn't have problems on my current S4 (Id rather not have to get a new phone at least until December ) I'm pretty sure I dont have a custom kernel or anything like that as it mentioned in some pages that I will need to get one I think? I also have philz CWM installed.

You have Philz installed, so you don't need to root again. Download the ROM and follow the instructions on the page.

Strephon Alkhalikoi said:
You have Philz installed, so you don't need to root again. Download the ROM and follow the instructions on the page.
Click to expand...
Click to collapse
It also mentioned to make sure I have the latest modem for my variant, how do I check/update that?
In regards to the kernel (which has a link on the same page), what do I do with that?

I don't have the latest modem for my I9505 and that ROM works perfectly fine. Where you've been on a custom ROM for a while finding out which modem you're supposed to use may be difficult. That's also why I recommend not worrying about it, unless you need to.

Strephon Alkhalikoi said:
I don't have the latest modem for my I9505 and that ROM works perfectly fine. Where you've been on a custom ROM for a while finding out which modem you're supposed to use may be difficult. That's also why I recommend not worrying about it, unless you need to.
Click to expand...
Click to collapse
Ok thanks. In regards to the kernel that is linked on the page, I guess I would be at an advantage if I downloaded and installed that too. How do I install it?

If' we're talking the same GPE ROM, and I think we are, the kernel is included in the ROM download. You'll be prompted to select a kernel when you run the install through the recovery.

Strephon Alkhalikoi said:
If' we're talking the same GPE ROM, and I think we are, the kernel is included in the ROM download. You'll be prompted to select a kernel when you run the install through the recovery.
Click to expand...
Click to collapse
Ok thanks a lot!
So process:
Backup data/photos etc
Nandroid backup
Full wipe using philz?
Flash ROM
Done?

You've got it.
When you are prompted to select the kernel, use the Googy Max kernel. The stock kernel sometimes causes random reboots. Also, on first boot the S4 will sit for a fair amount of time before prompting you to set a language. THIS IS NORMAL. It's because Android 5.0.x uses Art instead of Dalvik, and has to compile the apps the first time around.
In other words, after rebooting, just be patient.

Strephon Alkhalikoi said:
You've got it.
When you are prompted to select the kernel, use the Googy Max kernel. The stock kernel sometimes causes random reboots. Also, on first boot the S4 will sit for a fair amount of time before prompting you to set a language. THIS IS NORMAL. It's because Android 5.0.x uses Art instead of Dalvik, and has to compile the apps the first time around.
In other words, after rebooting, just be patient.
Click to expand...
Click to collapse
Ok, thanks a lot for the help! Greatly appreciated. Hope I dont run into any problems

I installed that ROM on Sunday, so what I did is still fresh in my mind. If you have problems, just use this thread and quote me. I'll do my best to help.

Strephon Alkhalikoi said:
I installed that ROM on Sunday, so what I did is still fresh in my mind. If you have problems, just use this thread and quote me. I'll do my best to help.
Click to expand...
Click to collapse
All installed, was quite easy! Looks bloody beautiful, love it already. Thanks a heap!

Strephon Alkhalikoi said:
I installed that ROM on Sunday, so what I did is still fresh in my mind. If you have problems, just use this thread and quote me. I'll do my best to help.
Click to expand...
Click to collapse
I made and error when backing up and didnt back up my photos onto a computer Is there any way that my nandroid recovery or titanium backup have saved my photos and how could I recover them?

jc258 said:
I made and error when backing up and didnt back up my photos onto a computer Is there any way that my nandroid recovery or titanium backup have saved my photos and how could I recover them?
Click to expand...
Click to collapse
No, they are gone forever.
How is that even possible that you wiped them? Wiping in the custom recovery never touches your internal storage by default. So you have done it yourself. You probably did a factory reset from within android itself. Never do that again. Use the custom recovery for wiping only and you never will have this problem again.

Lennyz1988 said:
No, they are gone forever.
How is that even possible that you wiped them? Wiping in the custom recovery never touches your internal storage by default. So you have done it yourself. You probably did a factory reset from within android itself. NEVER DO THAT AGAIN. Use the custom recovery for wiping only and you never will have this problem again.
Click to expand...
Click to collapse
Are you sure about that? It happened the first time I flashed a ROM. Wiped cache, wiped Dalvik through CWM. Never did a factory reset. No need for caps.

jc258 said:
Are you sure about that? It happened the first time I flashed a ROM. Wiped cache, wiped Dalvik through CWM. Never did a factory reset. No need for caps.
Click to expand...
Click to collapse
No it's not possible for it to happen without you doing so. Unless you encrypted your phone or something.
ps removed the caps

The rom he installed has an aroma installer which offers the option to do a simple wipe (Dalvik, cache and data), no wipe (Dirty flash) and a factory reset (which also wipes the internal storage).
By default it is set on factory reset option.
It also says in red letters that this option is recommended.
So maybe he left it on factory reset (since it was also recommended) , instead of changing it to simple wipe, and that wiped the whole phone, including the internal storage.
Will a software that recovers deleted files not work? Since the phone wasn't encrypted.

It would if Windows saw the internal storage as a drive. Due to MTP it doesn't. He'll have to do a search, but there was another S4 owner who lost his photos and was trying to get them back. I don't know if a solution was ever found.

GDReaper said:
The rom he installed has an aroma installer which offers the option to do a simple wipe (Dalvik, cache and data), no wipe (Dirty flash) and a factory reset (which also wipes the internal storage).
By default it is set on factory reset option.
It also says in red letters that this option is recommended.
So maybe he left it on factory reset (since it was also recommended) , instead of changing it to simple wipe, and that wiped the whole phone, including the internal storage.
Will a software that recovers deleted files not work? Since the phone wasn't encrypted.
Click to expand...
Click to collapse
If that's the case then shame on the developer. A factory reset in a custom recovery should leave the internal storage intact.
Strephon Alkhalikoi said:
It would if Windows saw the internal storage as a drive. Due to MTP it doesn't. He'll have to do a search, but there was another S4 owner who lost his photos and was trying to get them back. I don't know if a solution was ever found.
Click to expand...
Click to collapse
No it's impossible. Once it's gone the files are permanently gone. Not even a professional company can restore them. That's because of TRIM that Android has from version 4.3.

Lennyz1988 said:
If that's the case then shame on the developer. A factory reset in a custom recovery should leave the internal storage intact.
Click to expand...
Click to collapse
It's not in the recovery. It's in the aroma installer. Those are 2 different things.
Besides, there is a description, under each setting, of what each one does.

@Lennyz1988: Perhaps you should bring this up with the developers of the ROM and see what they say. I suspect they have a very good reason for wiping the internal storage, and my gut instinct tells me it has to do with the Android folder on there.
On the flip side, thanks for the homework you gave me. I have to look into what TRIM is all about, as my last device was powered by Gingerbread.