My Captivate is 100% factory, never rooted, never flashed, etc. Some day I will want root and will want to unlock it.
Should I do these things today, prior to Froyo or will it really matter?
I've read about rooting and saving a copy of the folder containing the lock files. Should I do this today?
Will the official Froyo be just as easy to root and to unlock the phone?
Did I post this in the wrong forum? Should it be in General?
There is already a couple roms built on the upcoming froyo. My point is the devs know how to root and enable sideloading. Does not matter, although most custom roms are already more advanced then the froyo being released
if you're planning on unlocking, I suggest doing it before Froyo. Froyo introduced some tricks to prevent finding the unlock code on the phone, so the current method requires you to replace your EFS files with "blank" ones that have the potential for trashing your IMEI/connection (though EXTREMELY unlikely, but very troublesome)
If you root you may not be able to update. Unlocking is not rooting. Unlocking should survive an update, rooting will not. I wouldn't do anything to the phone prior to the Foryo update. If something goes wrong you can blame AT$T/Samsung and get a replacement. If something goes wrong because of something you did before the update, you'll be SOL.
Related
Since being interested in rooting my N1 I've been googling a lot but it's still somewhat confusing. One of the things that's making me hesitent is the idea of permanently (as of the date of this post) unlocking the phone and thus clearly/visibly voiding the warranty.
I've recently stumbled upon instructions for rooting without unlocking the bootloader? Am I correct in assuming this would make the phone appear (no unlock icon) to be unmodified? Also, does this mean one could fully reverse the rooting process and go back to fully stock google signed roms with OTA updates etc (essentially reverting it back as if it were never modified)?
It would seem this would be preferable to any method involving the unlocking of the bootloader. Are there any disadvantages of this? Any increased risks by NOT unlocking the bootloader? Is there a reason why most people have gone the rout of unlocking the bootloader?
My plan is simply to have root access to run setcpu on the stock FRF91 rom. As of now, I'm not interested in other ROMs (baby steps).
ellesshoo said:
Since being interested in rooting my N1 I've been googling a lot but it's still somewhat confusing. One of the things that's making me hesitent is the idea of permanently (as of the date of this post) unlocking the phone and thus clearly/visibly voiding the warranty.
I've recently stumbled upon instructions for rooting without unlocking the bootloader? Am I correct in assuming this would make the phone appear (no unlock icon) to be unmodified? Also, does this mean one could fully reverse the rooting process and go back to fully stock google signed roms with OTA updates etc (essentially reverting it back as if it were never modified)?
It would seem this would be preferable to any method involving the unlocking of the bootloader. Are there any disadvantages of this? Any increased risks by NOT unlocking the bootloader? Is there a reason why most people have gone the rout of unlocking the bootloader?
My plan is simply to have root access to run setcpu on the stock FRF91 rom. As of now, I'm not interested in other ROMs (baby steps).
Click to expand...
Click to collapse
there really is no measurable risk. the only difference is that you cant use fastboot but you can use alternatives to that (you dont need to worry about this)
most people unlocked the bootloader because the method to root without unlocking was just discovered recently.
I did the root without unlock a few days ago, as far as I can tell I can do it all and I do not get the unlocked icon. I have custom recovery, custom ROM, using root only apps like metamorph, titanium backup, etc. Best decision I have made. This phone is amazing.
Sent from my Nexus One using XDA App
Where are the instructions for doing so? I am an Android noob and just got the Nexus after the iPhone. I am kinda worried about bricking it if I root. Plus the only reason I want to root is because I hear that after that you are able to save all your apps to the SD card instead of the phone. If i was able to do that without rooting, I would be happy, but that's the only reason why i would like to do that.
phone_fanatic said:
Where are the instructions for doing so? I am an Android noob and just got the Nexus after the iPhone. I am kinda worried about bricking it if I root. Plus the only reason I want to root is because I hear that after that you are able to save all your apps to the SD card instead of the phone. If i was able to do that without rooting, I would be happy, but that's the only reason why i would like to do that.
Click to expand...
Click to collapse
froyo lets you do this....but it still takes up a lot of space on the phone (i was full after only 200 total apps)
the tutorial is stickied in the android development section of this forum
That's the thing though, I do have Froyo. However not all apps allow me to select that 'Move to SD card' setting for some reason. Some of the apps it's just greyed out and it isn't clickable. Out of say 10-11 apps, only 3 had that option available and I was able to move them to the SD card.
phone_fanatic said:
That's the thing though, I do have Froyo. However not all apps allow me to select that 'Move to SD card' setting for some reason. Some of the apps it's just greyed out and it isn't clickable. Out of say 10-11 apps, only 3 had that option available and I was able to move them to the SD card.
Click to expand...
Click to collapse
its because app devs have to allow to install it that way. if you want to force it, use adb to do the following
adb shell
pm setInstallLocation 2
So if the developers will be implementing it soon enough then why rush it right? I mean I don't mind waiting....as long as all the app developers will be doing it sooner or later?
I am N1 newbie but not Android newbie - have been using rooted Droid Incredible as my "main" phone for several months.
I just purchased officially unlocked N1 that is currently activated on prepaid T-Mobile account in USA and in future it will be used on my vacation in Europe.
Phone came with OS v. 2.2
I read a lot and things are sure different for N1 comparing to DInc. For DInc there was just one OS update and just one way to root it. For N1 its almost too much of a good thing for someone who hasn't followed it until now - 3 or 4 official OS updates and gazillion ways to root .
At this time I would like to root the phone (definitely, so that I can use third-party apps that require root access) and upgrade OS (possibly). I am not planning to use custom ROMs at this time but would like to try them in the future if rollback to stock ROM is possible.
As I already mentioned - my phone currently uses OS 2.2 and when I checked for an update via phone menu no updates were found. I was connected to internet at the time.
Questions:
1) From what I read some of the official ROMs between 2.2 and 2.3.4 (latest version) had problems. Are these versions even worth considering now that 2.3.4 is out?
2) Are there any known issues in 2.3.4 that are not present in 2.2?
3) What are advantages of going from 2.2 to 2.3.4?
4) Can I upgrade from 2.2 to 2.3.4 directly? All guides I found usually describe 2.2->2.2.1 etc - that is ROMs are updated consequently as they were released.
5) Should I a) update ROM to the latest and then root or b) first root 2.2 and then update ROM?
6) What are advantages of rooting with unlocking bootloader as opposed to rooting without unlocking bootloader?
Read the wiki. It is there to answer most of your ?s. Or use the search function.
If anything is still unclear ask about it and you will get help.
Sent from my Nexus One using XDA App
albundy2010 said:
Read the wiki. It is there to answer most of your ?s. Or use the search function.
If anything is still unclear ask about it and you will get help.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I read the WIKI and searched and it is still unclear.
1. 2.3.4 is the only version that currently has a fix for the recently found security hole that affects every version of Android other than 2.3.4. But this only affects non-https logins over an open wifi network, and people have to be scanning it.
2. I think the only major issue (depending on who you talk to) is the 2-3 second delay when you first answer a call before your microphone works. It has never really been a bother to me, and doesn't seem to affect everyone (maybe some just take longer to talk after they swipe, IDK).
3. There are a lot. Bugfixes, better UI, faster, support for video calling with GTalk (although obviously, only the back camera works, but you can still receive fine).
4. Almost, you can upgrade directly to 2.3.3. I don't think I have enough posts to add links, but a quick google search of "nexus one full gingerbread update" (without quotes) showed some results and the second one for me is how to manually update to Gingerbread. From there, you have to root the phone, because there are no hacks known to root 2.3.4 yet. This is where it gets a bit tricky because flashing a new update will kill your root. There are a number of guides on xda which can walk you through this part, because it is pretty detailed.
5. Kinda touched on with the above. Don't wait until you get to 2.3.4 until you root.
6. An unlocked bootloader makes things a lot easier. You can actually root your phone if it is running 2.3.4, because this allows you to load a custom recovery, which will give you access to the system partition of your phone. From there, you can add the files needed for root and remove the ones that will replace the recovery. The only benefit to keeping your bootloader unlocked is that it will keep its warranty through HTC, although HTC has been really good about replacing defective phones even if the bootloader is unlocked.
I'm hoping to get some eyes on this plan I've made for hacking my new Droid so I can avoid bricking it at all costs.
I bricked my old Bionic 2 days ago due a combination of problems with Clockword Recovery Mod and the leaked ICS update, as well as my battery frying for some reason. Thankfully Verizon was none the wiser and they are sending me a new phone and battery in a few days. Although I'm cautious about hacking now, I still plan on rooting the new phone so I can recover my apps and data from the old phone's SD card.
Here are my plans for the new phone. If anyone could tell me if it makes sense or if they see any issues that will arise from following these steps, please let me know:
1. Root new Bionic with Motofail.exe root
2. Restore apps and such with Titanium Backup (restoring individual apps so I don't get any old clockwork garbage or other random stuff)
3. Download Voodoo Root OTA Rootkeeper.
4. Wait for official ICS OTA (don't want to mess around with the leaks anymore) and backup root with voodoo
5. Unroot with voodoo, install ICS and re-root after update (I've read on some posts that Voodoo works with the ICS OTA but I'm not 100% sure)
I'm more concerned with the OTA installing properly than keeping the root after ICS, though while it would be simpler just to not root, I really want to restore the TiBu backup from my old phone.
If anyone sees any flaws with this plan or if you think it sounds like there won't be any problems, please respond! I really don't want to brick a second phone so any help would be invaluable.
No one can say for sure if this will work since no one has the official OTA yet.
That sounds like a plan that may work. Even if OTA Root keeper fails I see a thread with a root method that is working on ICS leaks so it should
[should being the operative word here as stated this is all subjective reasoning from my time and use of Android and many different devices there is NEVER 100% certainty EVEN IF we had access to the OTA and had a method there is no accounting for any errors caused by a multitude of things [download corruption, bad blocks in memory during flash, you missing a step and borking the whole process, etc.] so no one will ever be able to say with 100% certainty that you will not have some rare issue and have a problem even with a tested method [and if someone does try to tell you something is 100% they have not dealt with technology and computers long enough to realize nothing is ever guaranteed even fully certified OTAs have caused bugs not accounted for and been stopped, recalled, or otherwise modified when users try to apply them and have issues ]
Anyways, I did read where you flashed the ICS leak via CWM recovery and everything I have been reading about flashing ICS on a Bionic involves the STOCK recovery and not CWM [most postings even SPECIFICALLY state to NOT USE CWM AND ONLY USE STOCK Recovery [but then again I read a lot] so if I had to trace the issue you had the with the limited information you have provided about your specific experience I would prolly point to that as prolly causing the problem. See the ICS with files thread here and that is again specified as part of procedure [basically format EVERYTHING restore it back to out of the box 902 then using STOCK recoveries to apply .905 then the ICS leak THEN after ICS is running they have a rooting batch file in there as well [so no worries about rooting in .902 and using OTA Rootkeeper to sustain it in .905 and on just get stock .905 unrooted to the phone then flash ICS with stock and root once it is fully completed and drivers and all on computer side are good [dont forget to enable USB Debugging [and in ICS there is an option to allow SU to apps only OR APPS AND ADB and after rooting you may need to enable the ADB side for any super user root checks if checking via ADB] but dunno if that is CM9 only option, but seems to be stock ICS setting in developer [it protects you if you use and leave enabled the ADB over the network function from others who may find your device over a network and getting SU access].
Sorry, I digress, all to say sorry to here you had the issue, but I think you may have missed something in the install process and here's how to address it, and your methodology seems sound in theory, but there is other information already available to augment your procedure and make it easier on you, my bad.
Hope all the info helps....
Here is that thread mentioned above that seems to distill what I have read on numerous boards in to one easy to download pack with instructions that has users replying that they have had great success with it: [Guide} Bionic to ICS w/Files
I have an ATT S5 (SM-G900A), completely stock, unrooted, updated to the latest 5.0 OTA update. My requirements for my phone are that it be able to pass Airwatch checks and that it be able to be encrypted (Personal device used at work). Some background first:
Last time I tried to play around with rooting, other mods, and whatnot was on my ATT S3 (I think I747?) and I discovered that an unspecified combination of rooting, installing a custom loader (CWM in my case) and installing a custom mod (Cyanogenmod at the time) made my phone unable to encrypt. At the time I was not required to use Airwatch, but encryption was required for my phone to connect to work, so I gave up on the whole lot.
I have now discovered that ATT, in their infinite wisdom, has replaced the S Voice drive mode with their own "ATT Drive Mode", and it's been verified they went so far as to remove the related APKs from the phone entirely. For those unaware, S Voice Drive mode is an feature of S Voice that (when turned on) reads out all callers and text messages, and then verbally prompts you for actions; reply, answer, ignore, etc. It allows fully hands free functionality. ATT Drive Mode, on the other hand, automatically kicks in whenever speeds of 20 MPH are detected (even if you're a passenger), rejects all calls and texts excluding a user-defined 5 person list, and essentially makes your phone useless anytime you're in a car. The goal is to "reduce texting and distracted driving", but as I'm on-call as part of my job and need to at least be aware of texts that come in within 10 minutes of receipt, it actually makes my drive much more dangerous. ATT Drive mode is a good idea for teens, perhaps, but i'm not a teen.
This brings me to my question: What are my options?
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
Honestly, the ideal solution would be something like the stock rom from the international version that would run on my ATT version...but I don't know if such a thing exists or is possible. I don't mind Samsung's cruft, but I do dislike ATT's lobotomizing of my phone to push their own little product that treats me like a kid. I know that I am less safe as a driver without the S Voice drive mode than I was with it.
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
sheaiden said:
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Waiting4MyAndroid said:
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Click to expand...
Click to collapse
Actually, while I greatly appreciate the fact that you took the time to reply (seriously! at least you took the time!), this is neither easy nor related to the questions I asked. If you look at my post, I'm not asking "how can I root", I'm asking three rather different questions:
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
In fact, I am unable to remain rooted (Airwatch; it's part of the post title), and the whole point and thrust of my question lies in the fact that I am looking to find out what affects encryption and what options I have as far as getting S Voice Drive mode on my phone while staying Airwatch compliant (not rooted). In addition, "if you can find the s voice drive app" is part of the problem too, as evidenced by the third question I asked above; I don't know where to find said app.
Does anyone know anything regarding what I was actually asking?
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
https://www.dropbox.com/s/oe7i2g81iuhjv38/S-Voice_Android_phone_J.apk?dl=0
Waiting4MyAndroid said:
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
Click to expand...
Click to collapse
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
sheaiden said:
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
Click to expand...
Click to collapse
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
OPOfreak said:
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
Click to expand...
Click to collapse
Interesting. I had been under the impression that I had seen people referring to installing clockworkmod or some similar thing on an S5, but I think I may be getting caught up in terminology; those are recoveries, aren't they? not bootloaders? Or perhaps people were posting about the other S5s with unlocked bootloaders. 15 different versions of S5, and I get stuck with the most apple-like of all the carriers....(in the sense of "you take what we give you and don't play with it!")
So, assuming I don't manage to get it installed via the link Waiting4MyAndroid was kind enough to post, I think that rules out anything other than the method of:
--wait for a root method to be established for the new OTA
--root, install the drive apk
--unroot, so I can encrypt and pass airwatch
Does anyone know if the old method of rooting broke encryption? and whether encryption was able to be performed after unrooting again?
Edit: Attempted to Sideload. Sadly, it is telling me "App not installed" (other sideloads do work; it's not the unknown sources setting). I'm thinking either the apk is marked for s4, and it's not compatible, or it's trying to overwrite files from the established svoice system, and that's not allowed. I suppose if someone has the drive apks from a tmobile S5 image or some such thing (same model, different carrier), then I could try again, but unfortunately this apk doesn't work. Thanks for the attempt, Waiting4MyAndroid!
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
jsmithfms said:
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
Click to expand...
Click to collapse
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
KennyG123 said:
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
Click to expand...
Click to collapse
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Honestly for the time being I wouldn't bother with ROMS for that Device and carrier at the moment. Especially being that its someone elses device. Towelroot should be a good start. If Im not mistaken I don't think its supposed to trip knox.
Sent from my HTCEVODesign4G using XDA Free mobile app
jsmithfms said:
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Click to expand...
Click to collapse
This is the riddle of the Sphinx my friend. I am sure the super devs have tried their best so far to crack it. It has been an ongoing effort to make phones more and more secure, not against the amateur developers and rooters, but against the hackers. These smartphones are now our personal computers, diaries, personal assistants, financial operator, and more. They basically are a person's (and business's) life. AT&T and Verizon have taken the big steps to appeal to the Exchange clients, corporate, government and military contracts. Even the general public want to know their phone is secure. This is what keeps me stuck on the Sprint network.
Have you tried Kingroot?
I successfully rooted my wife's AT&T S4 on OC3 lollipop (supposedly unrootable) with the desktop version. Mobile version didn't work but desktop did without a hiccup. Maybe it'll work on the S5.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
S5 on lollipop has a new nasty boot loader.... it was a miracle on its own that they ever came up with safestrap to duck the boot loader on earlier versions of android