Hello all!
Glad I can report that the towelroot exploit worked successfully on my Verizon Samsung Galaxy S5 phone.
I'm a noob to Android devices, but I think they are awesome
I've spent most the day reading up on Android backup and recovery, differences between rooting and unlocking the bootloader, and I have a couple of questions relating to these topics:
1) I've rooted my Samsung Galaxy S5, and, in the event that I accidentally loaded a virus on my phone, or seriously messed something up with my root access, I'd like to have a way out of it. I've been reading up on the Android Recovery Mode: Wipe Data/factory reset. My question is this: Is it still okay to use this feature after I've rooted my ROM using towelroot? Also, if I use this feature, will it also completely re-install system software (like a Win 7 Reinstall)? Or is this just deleting some user data and leaving the once upon a time read only folders alone?
If method one mentioned above isn't a full OS restore, I think this is my other option...
2) Since I've rooted my phone with towelroot, I know that my bootloader is still locked. I know that another backup option is to use CWM to do a custom backup/recovery, however, I know that unlocking the bootloader right now may not be possible. I can't find any already existing threads relevant to Verizon Galaxy S5 bootloader unlocking since towelroot has been released released, however, I have stumbled upon this website which mentions my phone in the list: (I can't post links yet, please google "samsung galaxy s5 cwm phizl", and click on the second link. What do you guys think of this guide, do you think this will actually work for the unlocked Verizon Galaxy S5?
Thank's for any help with this.
Does this question stump everyone?
If you do a wipe it goes back to how it was when you first installed the rom/ first boot.
shredfast said:
I'd like to have a way out of it. I've been reading up on the Android Recovery Mode: Wipe Data/factory reset.
Click to expand...
Click to collapse
This is oversimplified, but the files on your phone are more or less organized like this -
1. User settings, installed apps (data partition) - this is what a factory data reset would erase.
2. System files (most of them) - these read only files don't normally change unless you get an OTA firmware update. If you accidentally delete or somehow corrupt system files, you can reinstall the firmware to fix these. A custom ROM (if your bootloader was unlocked) would replace the files here.
3. Cache. These are temporary files. Some problems can be fixed by deleting these. If deleted, your phone will rebuild the cache when it boots.
4. SDcard. Built in, internal storage space for user files, downloads, etc. If you have a physical SD card, that is seperate and referred to as the external or secondary SD card.
5. Other stuff e.g. the bootloader, modem, etc.
A 100% backup is often referred to as a "Nandroid". Meaning that you backup the entire memory (NAND). You can only do that properly with a custom recovery like TWRP or CWM. The next closest thing would be an app like Titanium Pro.
The system data reset will only default the user settings (data partition). It won't remove most user files (internal SD card) or touch the read only system files (system partition).
I don't know what your second question really pertains to. You should have described it fully, rather than try to get us to replicate your Google search. I'll just say that it's highly unlikely that anyone will figure out how to unlock the Verizon bootloader anytime soon.
Verizon has an unlocked Developer model phone, but it is handicapped by poor firmware updates. If you want the advantages of an unlocked bootloader, change carriers. Most carriers do not lock the S5 bootloader. Just ATT, Verizon and a few US CDMA carriers.
Because your bootloader is locked, you can't use a real custom kernel or recovery. But they can be emulated with Safestrap.
.
Related
Hi,
I bought the Samsung Galaxy S5 and the fingerprint reader works reasonably well (as in it works, nothing in comparison to apple though, so don't buy it for the fingerprint reader ) for unlocking the screen...
However its a work requirement that my phone has full device encryption, as phones are regularly stolen where I travel.... it seems when I enable encryption I lose the ability to use the fingerprint reader to unlock the phone .... I bought this hoping that I could avoid having to type in my complex password just to unlock the screen, as I got so tired of doing that with my S2
Is there any mods to enable finger print reader screen unlock + full device encryption at boot time for the Galaxy S5 yet? ... I saw some references to pattern unlock / pin with device encryption... but I would think the fingerprint reader is different...
Thanks!
S5 Full disk encryption with fingerprint unlock
I also have this question. I believe on the Nexus 5 it at leasts lets you use face unlock with full device encryption. And I read on one article that you should be able to do this but i do not think the author actually tried this. I will say from my own personal experience that you can infact decrypt the device after encrypting it without doing a complete wipe of the device and you can restore the use of fingerprints to unlock your phone. It seems like for security minded people this would be a great feature but if it is unable to be used with full device encryption it seems a little pointless to me. Being forced to use a PIN or password to use encryption is a big pain point for android users who want some type of security.
Yes I can't believe that no one has really complained about this yet - but I guess encryption isn't' that important to people as I imagined
androidpleb said:
Yes I can't believe that no one has really complained about this yet - but I guess encryption isn't' that important to people as I imagined
Click to expand...
Click to collapse
I am having the same pain, as I use my S5 for BYOD.
It makes no sense when you can use fingerprint to make payments with paypal but not unlocking the phone when it is encrypted.
Hope Samsung can enable this feature in next update.
I'd like this too.. as well as, the iPhone has a cydia app (that a friend of mine showed me), that you can basically disable the power button from turning off the phone while it is fingerprint locked. That would definately be nice to have on the S5 (since it's done through an app). That would have stopped the person who stole my wife's S4 from turning it off when it was blasting the locator ring at them!
sorphin said:
I'd like this too.. as well as, the iPhone has a cydia app (that a friend of mine showed me), that you can basically disable the power button from turning off the phone while it is fingerprint locked. That would definately be nice to have on the S5 (since it's done through an app). That would have stopped the person who stole my wife's S4 from turning it off when it was blasting the locator ring at them!
Click to expand...
Click to collapse
I can't believe that the fingerprint sensor can't be used if encryption is enabled whatsoever. I could understand the iPhone model, requiring a pin before a fingerprint can be used, but by disabling fingerprint lockscreen, boot unlock, and SD unlock, the fingerprint sensor is now wholly useless for convenience.
It's too trivial to extract data from an unencrypted Android. By not supporting encryption with a measure of covenieve, I don't see the point in including a fingerprint sensor whatsoever given the current software limitations.
Please, someone, figure out what sqlite/settings need to be changed so we can make decent use of our phones fingerprint sensor.
After some experiments, i found out a procedure to enable FDE and fingerprint lockscreen. Root is required (or at least I guess, I didn't try with a non-rooted system...).
These are the steps:
1) set up fingerprint lockscreen
2) with a root explorer, go to /data/system folder, and backup locksettings.db, locksettings.db-shm and locksettings.db-wal to sd card
3) set up password lockscreen
4) encrypt the device
5) when encryption is done, restore the backed-up files to /data/system: you should have fingerprint lockscreen again (no reboot needed, just turn the screen off, and magically the password should be vanished )
CAVEAT 1: with my system configuration, I wasn't able to encrypt the device directly: the encryption procedure started, but after reboot nothing happened, the device just booted normally. I don't know the exact reason, in some forums they suppose that it happens on kitkat when the device is rooted. I was able to bypass the problem only adding these steps to the procedure:
...
3b) with TWRP, backup the /system partition, and restore the stock non-rooted /system
4) encrypt the device
4b) restore the original rooted /system partition
...
I don't know if steps 3b) and 4b) are always necessary, let me know...
If you need these steps, don't worry if before restoring your custom /system partition the encryption password isn't recognized, just restore the partition and all will work fine
CAVEAT 2: once encrypted, I didn't find a way to unencrypt the device, because the unencrypt ion procedure starts, but after reboot the device is still encrypted, similar to what described in caveat 1. I tried to replace the /system partition with the stock one, but the encryption password was no longer recognized.
CAVEAT 3: the current TWRP (2.7.1) isn't able to mount S5 encrypted data partition, and restoring an image made with online nandroid backup doesn't seem to work either. So, if you want to make an image of your phone (and I suggest to do it ), do it before encryption
Boot Loop
fabiokino said:
After some experiments, i found out a procedure to enable FDE and fingerprint lockscreen. Root is required (or at least I guess, I didn't try with a non-rooted system...).
These are the steps:
1) set up fingerprint lockscreen
2) with a root explorer, go to /data/system folder, and backup locksettings.db, locksettings.db-shm and locksettings.db-wal to sd card
3) set up password lockscreen
4) encrypt the device
5) when encryption is done, restore the backed-up files to /data/system: you should have fingerprint lockscreen again (no reboot needed, just turn the screen off, and magically the password should be vanished )
CAVEAT 1: with my system configuration, I wasn't able to encrypt the device directly: the encryption procedure started, but after reboot nothing happened, the device just booted normally. I don't know the exact reason, in some forums they suppose that it happens on kitkat when the device is rooted. I was able to bypass the problem only adding these steps to the procedure:
...
3b) with TWRP, backup the /system partition, and restore the stock non-rooted /system
4) encrypt the device
4b) restore the original rooted /system partition
...
I don't know if steps 3b) and 4b) are always necessary, let me know...
If you need these steps, don't worry if before restoring your custom /system partition the encryption password isn't recognized, just restore the partition and all will work fine
CAVEAT 2: once encrypted, I didn't find a way to unencrypt the device, because the unencrypt ion procedure starts, but after reboot the device is still encrypted, similar to what described in caveat 1. I tried to replace the /system partition with the stock one, but the encryption password was no longer recognized.
CAVEAT 3: the current TWRP (2.7.1) isn't able to mount S5 encrypted data partition, and restoring an image made with online nandroid backup doesn't seem to work either. So, if you want to make an image of your phone (and I suggest to do it ), do it before encryption
Click to expand...
Click to collapse
I get samsung boot loop using the above instructions
Pierreseoul said:
I get samsung boot loop using the above instructions
Click to expand...
Click to collapse
Hi guys! Did someone try this solution? I unfortunately have the same issue and unlock my device each time make me crazy!
Thanks in advance.
Same problem
I purchased a Galaxy S5 and I have the same problem, unfortunately I cannot root my phone due to security policies in my company. :crying:
I hope Samsung will solve the issue. :fingers-crossed:
Have anyone contacted to Samsung Support Center?
Pierreseoul said:
I get samsung boot loop using the above instructions
Click to expand...
Click to collapse
What is the consequence of boot loop if you are using stock boot loader? Odin mode required to recover? Something less drastic? What device model are you using?
I found a possible solution that involves deactivating SuperSU and running encryption from there. Still investigating. I am thinking that the solution from @fabiokino will work in this case too.
I'm curious about this aswell.
Doesn't anyone know a working solution?...
It is really frustrating the very least. I can't believe there isn't a way (or if there is, a guide) to do this (with or without root access).
I have also heard it is doable on the Note 4. See this post for example http://forum.xda-developers.com/showpost.php?p=57103664&postcount=7.
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
How?
healpowah said:
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
Click to expand...
Click to collapse
Can you explain how please? I'm on stock lollipop as well and cannot use fingerprint scanner with FDE. Wondering if there's a process to it?
Thanks!
healpowah said:
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
Click to expand...
Click to collapse
Nice to see this, hope it will work on my Galaxy tab S too
Did you see this?
https://www.jethrocarr.com/2013/12/29/encrypting-disk-on-android-4/
GermanDoerksen said:
Can you explain how please? I'm on stock lollipop as well and cannot use fingerprint scanner with FDE. Wondering if there's a process to it?
Thanks!
Click to expand...
Click to collapse
Unluckily the trick showed in the previous link only encrytps the main device and not the micro SD
Joker87 said:
Unluckily the trick showed in the previous link only encrytps the main device and not the micro SD
Click to expand...
Click to collapse
Well for me that really wouldn't be a problem. I don't have an SD card so I'm okay with just FDE. Thing is I really really don't want to root my phone... No particular reason other than every older android device I've done it on always ends up slow and buggy after a few months use until I reflash with stock ROM. I would like my phone to stay buttery smooth for once..
GermanDoerksen said:
Well for me that really wouldn't be a problem. I don't have an SD card so I'm okay with just FDE. Thing is I really really don't want to root my phone... No particular reason other than every older android device I've done it on always ends up slow and buggy after a few months use until I reflash with stock ROM. I would like my phone to stay buttery smooth for once..
Click to expand...
Click to collapse
You could root then unroot it after you have encrypted it
Joker87 said:
You could root then unroot it after you have encrypted it
Click to expand...
Click to collapse
you're right... plus it's not really the "rooting" process that makes it slow, it's installing another ROM. Having a rooted phone doesn't necessarily have any performance impact... just opens up a few things for me. Interesting. Thanks! Unfortunately I've already encrypted so now I have to find that thread about how to decrypt lol.
Thanks!
OK so I recently got my hands on an S4 (GT-I9505). This is an upgrade from my previous phone that was stolen; I had an S3 with CM11 installed. So as I have enjoyed CM11 previously I would like to use it on my new S4. I have a few questions:
Is the default boot-loader locked? What alternatives exist for this device?
If I root and install a custom boot-loader, would I be able to replace it later if I wanted to?
Broad question, but what security features does Cyanogenmod come with?
Is there a stock CM phone location service built in to the OS, i.e. like a tracker?
Can I encrypt the device storage with CM11 without installing apps to do this?
Can I encrypt the removable storage without installing apps to do this?
How do I restrict USB mounting of the media folders on the phone/removable media to a specific machine?
Can I restrict access to the ADB via USB to a specific machine only?
The stock recovery menu states CTC code applied "BTU" (I'm in the UK). Does the bootloader apply this setting so the phone knows which region to operate in and if so does the CWM boot-loader also apply this code too (I don't want to run into problems after where the phone won't associate to a network due to some issue with CTC, or maybe I've misunderstood this concept...) ?
I know, dumb questions eh.
You have more than a few questions there. :lol:
The only S4 devices that have locked bootloaders are ones purchased from the United States cellular carriers AT&T and Verizon. Current bootloader code includes Knox security software, which is not found on the SIII.
You don't install a custom bootloader. Custom kernels and recoveries can be easily restored to stock using Odin.
Your questions regarding CyanogenMod I can't answer, as I don't use CyanogenMod.
Encrypting the removable storage may be possible, but it varies from ROM to ROM. You'll have to read up on the ROM you choose to use.
AFAIK, you can't restrict mounting of media folders.
You cannot restrict access to ADB to one specific machine.
The bootloader has nothing to do with the CSC code. Where you're planning on installing a custom ROM it won't matter anyway.
The only stupid questions are the ones that aren't asked. But, most of this information applies to the SIII as well. Surely you had to have been aware of some of it, as the two devices really aren't that different when you get right down to it.
Thanks for your feedback.
Hello everyone I have a problem which requires some help.
My parents accidentally did a factory reset and lost all her contacts and phonebook, so I am trying to recover it. I tried to use Tenorshare android recovery but found out it won't work without root so I have a few questions regarding that.
I found a guide on how to root here without the knox counter going up and voiding the warranty.
http: androidxda.net/how-to-root-galaxy-s4-gt-i9505-on-android-5-0-1-lollipop-without-tripping-knox
and these are my details and also I am on 5.01 GTI9505 Galaxy Samsung 4
AP: I9505XXUH0B8
CP: I9505XXUH0B8
CSC: I9505VFRHOC1
Firstly regarding the bootloader can I use this bootloader
I9505XXUHOB7 bootloader
md5:1e02a99ed0a26a9acf5b12bdb1778c18
Since my CP and AP is I9505XXUH0B8 and the bootloader is I9505XXUHOB7, the last digit is one less and does not match so I would like to confirm if it will work.
My final question is since the storage is similar to a PC in that if something gets deleted and as long as that part of the sector is not overwritten, there is a high chance of recovery I am trying to limit over writing the storage as much as possible.
So I would like to ask can I skip parts of the guide
http: androidxda.net/how-to-root-galaxy-s4-gt-i9505-on-android-5-0-1-lollipop-without-tripping-knox
For example skipping steps 1 to 9 as I am already on 5.01 offical firmware and all those steps seem to do is reinstall 5.01 or is the enable everRoot setting essential to rooting the device.
I mean if I have to put 2.6 + gigs of data on the device then there is a high chance that the data will be overwritten.
Oh one more thing I would like to ask is can I root using an external SDCARD.
Alternatively would it be better to downgrade to 4.4.2 firmware then root?
Or is it too late and the chances of recovery is slim in which case there is no point to losing the warranty as well.
I would like to know what my options are.
Thank you very much for taking the time to read this thread and for any assistance you can provide.
Kind Regards
Changing the bootloader will trip knox.
Downgrading the bootloader will trip knox.
I don't think stuff can be recovered from the internal storage due to something called trimming. I don't know exactly what it does, but somebody had a similar issue (with photos) and another user mentioned they couldn't be recovered with such "deleted files recovery software" due to that "trimming" thing.
Anyway, if there was a registered google account on the phone, chances are that there is a backup on the account. Google syncs the data automatically (if not disabled), meaning it backs up your numbers to your/their gmail.
As of Android 4.3 Google enabled Trim. Data recovery is impossible. So it's gone.
Thank you for the quick response, GDReaper and Lennyz1988. I tried restoring from google but it doesn't work, the account itself while checking online is entirely empty, nothing in the contacts folder. I think either all the numbers were linked with whatapps or either they were saved to the phone directly.
Anyway now I know that data recovery is impossible I will stop looking into rooting the phone.
Once again thanks
Dear esteemed experts,
I’m hoping you can assist in my hour of need: My partner has a stock unrooted European G900F S5, which unfortunately had a massive software glitch causing it to crash on start up. Long story short we managed to get to the factory reset options and do a full reset, which cured the problem, however my partner’s data has now been lost.
She regularly backed up and had all the autobackups enabled so contacts, sms, mms, pics, videos, settings, etc were all restored with relative ease, but it appears the most valuable thing to her, her WhatsApp conversation backups were stored by Whatsapp on the internal memory rather than the SD card (brilliant piece of software design going on there) so they are gone. Smart Switch restored all of the other WhatsApp data on the internal memory as part of its “data” backup but not the backup files…
I’d like to run a data recovery program to see if they can be recovered, but am hitting dead ends at every turn: none of the specialist android recovery programs (such as dr fone) appear to work on a lollipop S5 unless it is rooted; none of the usual PC recovery suites can work on MTP or PTP modes and a mass storage connection is no longer possible (at least without root); and the only way to permanently root is to downgrade the stock rom (which will likely overwrite the data I am trying to recover) and use something like towel root on KitKat. In any event, she’s very happy with an unrooted phone with OTA updates and so wouldn’t wish to end up with a rooted phone anyway, so I’d have no real interest in a custom bootloader install, etc: I just want temporary access for dr fone!
To that end, I wondered if there was by any chance a crafty way of obtaining a temporary root in lollipop (a re-root after restart is absolutely fine by me) just so I can run a recovery program and see if we get any luck? If it came to it I think she’d be prepared to sacrifice a knox trip if she got her conversations back….
Apologies if this has been asked before, but I could only fish out advice on permanent rooting for s5 in my searches (both here and on google).
Many thanks for your assistance!
Dav
No way to root lollipop without tripping KNOX if you are not willing to downgrade to KitKat first, which would defeat the object as you could root with towelroot then anyway
Only way to root Lollipop is to flash CF Auto Root with ODIN, which WILL trip KNOX, and it is permanent unless you choose to unroot / flash stock again
This is the file you need to flash with ODIN (Extract and add it to the AP or PDA section of ODIN with the phone in download mode)
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
PS: Questions go here
http://forum.xda-developers.com/galaxy-s5/help
(SOLVED)
Hi,
Ive been searching around all week now trying to find a way to do the above, root my note 4 without a factory reset.
As far as i can gather, my bootloader is unlocked.
I suspect it has had somekind of non-t-mobile standard wizardry performed upon it prior to my ownership (2nd hand). The reason i think this (naive?) is as i understand it, these, in the UK, were locked to t-mobile sims new, however, mine can use any sim. also, since my ownership (couple years +), maybe 3 or 4 times it has randomly rebooted and gone into some kind of anti-"fiddling" mode stating something along the lines of "this phone has none genuine blah blah and is now locked. take it into a t-mobile shop to get fixed". A simple battery pull has "fixed" the issue each and every time.
Now, the actual main reason i want to root this, apart from the obvious other advantages, is to be able to perform a complete backup (including all the backup locked out apps). i have a few apps ive paid for, but have since been pulled from the play store, thus, should this phone die, i have no way of restoring them.
it seems that, the only way to backup these apps is to root the phone. i can only find ways in which to root my phone that involve a factory reset. hence im stuck in a catch 22.
According to posts i've read, fastboot doesn't work with my phone. I have been reticent to actually follow through with any method which may reset/factory wipe my phone (as, if i understand it correctly, changing the bootloader/recovery will?).
even though i have found apk's for some of these apps, they are only for the trial versions, and not what i have previously paid for. furthermore, some of these companies have either gone bust, or simply refuse to respond to my emails. losing their cache i can live with, losing the full apps i "can't".
i use a laptop with arch installed. i have occassional access to a windows10 pc.
please please tell me it is possible to root this phone without losing these apps. Or at the very least, a way of pulling/backing up these apps.
ive not found a browser that can see into the data\app folder. adb can see into the data\app folder and pull apps, but not the apps i want to backup which have been pulled from the play store that ive paid for.
phone details:
model sm-n910t
android 6.0.1
baseband n910tuvu2eqi2
kernel 3.10.40 - 9385989
[email protected]#1
build no mmb29m.n910tuvu2eqi2
Hrafnblod said:
Hi,
Ive been searching around all week now trying to find a way to do the above, root my note 4 without a factory reset.
As far as i can gather, my bootloader is unlocked.
I suspect it has had somekind of non-t-mobile standard wizardry performed upon it prior to my ownership (2nd hand). The reason i think this (naive?) is as i understand it, these, in the UK, were locked to t-mobile sims new, however, mine can use any sim. also, since my ownership (couple years +), maybe 3 or 4 times it has randomly rebooted and gone into some kind of anti-"fiddling" mode stating something along the lines of "this phone has none genuine blah blah and is now locked. take it into a t-mobile shop to get fixed". A simple battery pull has "fixed" the issue each and every time.
Now, the actual main reason i want to root this, apart from the obvious other advantages, is to be able to perform a complete backup (including all the backup locked out apps). i have a few apps ive paid for, but have since been pulled from the play store, thus, should this phone die, i have no way of restoring them.
it seems that, the only way to backup these apps is to root the phone. i can only find ways in which to root my phone that involve a factory reset. hence im stuck in a catch 22.
According to posts i've read, fastboot doesn't work with my phone. I have been reticent to actually follow through with any method which may reset/factory wipe my phone (as, if i understand it correctly, changing the bootloader/recovery will?).
even though i have found apk's for some of these apps, they are only for the trial versions, and not what i have previously paid for. furthermore, some of these companies have either gone bust, or simply refuse to respond to my emails. losing their cache i can live with, losing the full apps i "can't".
i use a laptop with arch installed. i have occassional access to a windows10 pc.
please please tell me it is possible to root this phone without losing these apps. Or at the very least, a way of pulling/backing up these apps.
ive not found a browser that can see into the data\app folder. adb can see into the data\app folder and pull apps, but not the apps i want to backup which have been pulled from the play store that ive paid for.
phone details:
model sm-n910t
android 6.0.1
baseband n910tuvu2eqi2
kernel 3.10.40 - 9385989
[email protected]#1
build no mmb29m.n910tuvu2eqi2
Click to expand...
Click to collapse
Have you tried Odin? Samsung phones don't use fastboot but have their own flashing tool.
QuoPrimum said:
Have you tried Odin? Samsung phones don't use fastboot but have their own flashing tool.
Click to expand...
Click to collapse
I'm now rooted, cheers
I used ODIN on windows and CF_Auto Root.
I was just incredibly worried about getting a phone wipe/reset. I think, with having read through so many different guides and discussions, and having first tried to find a linux only solution, I'd ended up confusing myself. It just seemed that, when I thought I understood the process enough to actually physically start the rooting, all I could see was boot loop, bricking and factory reset issues in the guides.
Awesome forum.
Any apps you buy on the play store don't just disappear.
Check your actual purchase list for your Google account, it'll force a cached page.
Which is how I found out Activision pushed a (paid) mobile version of Zombies, removed it, then pushed the same game to the market which they continued to update.