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.
.
Is anyone here knowledgeable about how to flash OTA updates without wiping out data? I've read that AT&T prevents software updates on phones that aren't using an active AT&T sim card, via the regular process. I've been doing the flashes manually and each time I need to completely reset the phone. Google backup and Samsung Smartswitch somewhat help with the process, but it's nowhere as robust as an iTunes iPhone backup. I still have to spend a good amount of time re-configuring apps.
FYI - my phone is not rooted.
TaTaTaing said:
Is anyone here knowledgeable about how to flash OTA updates without wiping out data? I've read that AT&T prevents software updates on phones that aren't using an active AT&T sim card, via the regular process. I've been doing the flashes manually and each time I need to completely reset the phone. Google backup and Samsung Smartswitch somewhat help with the process, but it's nowhere as robust as an iTunes iPhone backup. I still have to spend a good amount of time re-configuring apps.
FYI - my phone is not rooted.
Click to expand...
Click to collapse
I don't believe that's possible.
muniz_ri said:
I don't believe that's possible.
Click to expand...
Click to collapse
Thanks for the reply. I had a feeling this was the case but wanted to double check on here anyways.
I have an AT&T S7 Edge that I am using with a Cricket SIM card. I can't get the OTA updates, and so wasn't able to update to Android 7. But the OTA update was posted here in the S7 Edge forum. I put the file on an SD card, booted into recovery and updated from the SD card. It worked just like an OTA... kept all my data intact. I don't know what's available for the S7, but I do know that it was possible to do on my S7 Edge.
Hope that helps!
TaTaTaing said:
Is anyone here knowledgeable about how to flash OTA updates without wiping out data? I've read that AT&T prevents software updates on phones that aren't using an active AT&T sim card, via the regular process. I've been doing the flashes manually and each time I need to completely reset the phone. Google backup and Samsung Smartswitch somewhat help with the process, but it's nowhere as robust as an iTunes iPhone backup. I still have to spend a good amount of time re-configuring apps.
FYI - my phone is not rooted.
Click to expand...
Click to collapse
cliemonster said:
I have an AT&T S7 Edge that I am using with a Cricket SIM card. I can't get the OTA updates, and so wasn't able to update to Android 7. But the OTA update was posted here in the S7 Edge forum. I put the file on an SD card, booted into recovery and updated from the SD card. It worked just like an OTA... kept all my data intact. I don't know what's available for the S7, but I do know that it was possible to do on my S7 Edge.
Hope that helps!
Click to expand...
Click to collapse
I wonder if it's different for the Edge version. I did exactly what you did for last month's security update. Someone here posted the OTA file, I put it on a SD Card, then booted into recovery to apply it. After the reboot, everything was gone and I had to setup my phone again.
The other day I swapped my batteries an upon reboot, got a splash screen indicating an update was being installed. I had been rooted for over two years and I had SDM frozen via Titanium Backup. There was no confirmation prompt or ability to defer the update offered. After boot, SU had been uninstalled and Titanium Backup wouldn't run at all.
Has anyone else had this happen? Verizon pushing past disabled SDM to pwn a phone?
Sent from my SM-T520 using Tapatalk
Danzdroid said:
The other day I swapped my batteries an upon reboot, got a splash screen indicating an update was being installed. I had been rooted for over two years and I had SDM frozen via Titanium Backup. There was no confirmation prompt or ability to defer the update offered. After boot, SU had been uninstalled and Titanium Backup wouldn't run at all.
Has anyone else had this happen? Verizon pushing past disabled SDM to pwn a phone?
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse
this is a serious problem , since for the vzw the bootloader unlocking usually take place on bpb1's and it would make sense that they would aim there first. I think it might be time for you to update your bootloader or switch over to custom roms instead of staying on samsung's firmware , and also this post just saved me from thinking of switching back to stock for the time being so now im def staying on nougat and hope android can be brought to the S5 as well.
I'm surprised there isn't anyone else reporting this. It seems VZW has a secondary backdoor into the stock firmware that isn't SDM or Knox. I didn't have the Verizon app installed either. On a different build on another S5 phone, the Verizon app asked for root from SU, and I shut it down immediately, figuring it wss trying to insert a backdoor.
It's just strange after two years of zero updates to my image, it suddenly allows VZW in to perform non-consentual sodomy on my phone...
Sent from my SM-G900V using Tapatalk
Danzdroid said:
I'm surprised there isn't anyone else reporting this. It seems VZW has a secondary backdoor into the stock firmware that isn't SDM or Knox. I didn't have the Verizon app installed either. On a different build on another S5 phone, the Verizon app asked for root from SU, and I shut it down immediately, figuring it wss trying to insert a backdoor.
It's just strange after two years of zero updates to my image, it suddenly allows VZW in to perform non-consentual sodomy on my phone...
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
its because the s5 is still widely used all over the world , its just another tactic for them to screw up older samsung devices to get users to upgrade to the latest ones. which is why using samsung software is not always a good thing. Injecting micro-codes are not UN-common for companies
I wanna know how they did that so it can be prevented.
I purchased 2 Essential phones from Sprint. In order to get them fully unlocked, they need to be active on Sprint for a minimum of 50 days.
This isn't a huge deal, since I am an active Sprint customer. I currently setup the first phone exactly as I like it, rooted, and restored all my apps with Titanium Backup. Currently running Android 7.1.1 NMJ32F, since I wasn't ready to flash the Oreo beta.
My plan is to use the first phone for 50 days, get it unlocked, wipe it, relock the bootloader, and give it to a relative to use on Verizon.
I will then start using the 2nd Essential phone on my Sprint line, unlock it after 50 days, and keep it for my personal use.
Question: Is there any possible issue that may arise if I use TWRP to make a full backup of Phone #1 and then restore that backup on Phone #2?
I am hoping TWRP would create phones that were identical in terms of apps, home screens, settings etc. Doing this would save me the time of having to setup two phones.
If this will work, does it even matter if the 2nd device is running the same software build version of Android, prior to me restoring the TWRP backup from the first device?
As long as you don't backup and restore EFS, you should be fine. I've done this in the past with no issues
Do US carrier lock unlocked phones??? I bought mine outright from Telus in Canada and popped my Bell Sim in and it was fine. I thought the Nexus, Pixel and now Essential lineups were unlocked out the box?
Turbojugend said:
Do US carrier lock unlocked phones??? I bought mine outright from Telus in Canada and popped my Bell Sim in and it was fine. I thought the Nexus, Pixel and now Essential lineups were unlocked out the box?
Click to expand...
Click to collapse
Pretty much every time, particularly if they're the 'exclusive' carrier for it :
Pixels with Verizon are locked
PH-1s from Sprint are locked
HTC U11 from Sprint are locked
It even used to be that you more or less got an unlocked GSM phone when you bought from T-Mobile, now you get them locked as well.
Seamonkey79 said:
Pretty much every time, particularly if they're the 'exclusive' carrier for it :
Pixels with Verizon are locked
PH-1s from Sprint are locked
HTC U11 from Sprint are locked
It even used to be that you more or less got an unlocked GSM phone when you bought from T-Mobile, now you get them locked as well.
Click to expand...
Click to collapse
That's really crappy. As of Dec 1st in Canada all devices will be unlocked and older locked ones will be unlocked free of charge.
Turbojugend said:
That's really crappy. As of Dec 1st in Canada all devices will be unlocked and older locked ones will be unlocked free of charge.
Click to expand...
Click to collapse
It is, but that's okay because so are the carriers. They're required to offer unlocks once the phone's contracted time is up and/or it's paid in full, but like Sprint with their 50 days, they just add other criteria so that you have to stick with them. They're all pretty predatory.
Seamonkey79 said:
Pretty much every time, particularly if they're the 'exclusive' carrier for it :
Pixels with Verizon are locked
PH-1s from Sprint are locked
HTC U11 from Sprint are locked
It even used to be that you more or less got an unlocked GSM phone when you bought from T-Mobile, now you get them locked as well.
Click to expand...
Click to collapse
Verizon pixels are not locked. Verizon does not carrier lock any lte phones.
Sent from my PH-1 using Tapatalk
bricky23 said:
Verizon pixels are not locked. Verizon does not carrier lock any lte phones.
Click to expand...
Click to collapse
Oh yes, that's right. Pixels just get the bootloader lock on Verizon.
Do they still disallow APN changes, though? My Droid Turbo wasn't carrier locked, but the Globe SIM I tried to use when I was in the Philippines wouldn't work because it needed APN adjustments to function.
diesteldorf said:
I purchased 2 Essential phones from Sprint. In order to get them fully unlocked, they need to be active on Sprint for a minimum of 50 days.
This isn't a huge deal, since I am an active Sprint customer. I currently setup the first phone exactly as I like it, rooted, and restored all my apps with Titanium Backup. Currently running Android 7.1.1 NMJ32F, since I wasn't ready to flash the Oreo beta.
My plan is to use the first phone for 50 days, get it unlocked, wipe it, relock the bootloader, and give it to a relative to use on Verizon.
I will then start using the 2nd Essential phone on my Sprint line, unlock it after 50 days, and keep it for my personal use.
Question: Is there any possible issue that may arise if I use TWRP to make a full backup of Phone #1 and then restore that backup on Phone #2?
I am hoping TWRP would create phones that were identical in terms of apps, home screens, settings etc. Doing this would save me the time of having to setup two phones.
If this will work, does it even matter if the 2nd device is running the same software build version of Android, prior to me restoring the TWRP backup from the first device?
Click to expand...
Click to collapse
Should be no issue.
I would do a data and app restore and leave the OS alone.
But even if you restore everything as long as it is not EFS you should be fine.
That is exactly what I did when I got replacement phones.
qbanlinxx said:
As long as you don't backup and restore EFS, you should be fine. I've done this in the past with no issues
Click to expand...
Click to collapse
Do you (or anyone) have a link to a guide on this? I'm getting a replacement PH-1 tomorrow and it would be nice to just dupe my current phone.
GospelNerd said:
Do you (or anyone) have a link to a guide on this? I'm getting a replacement PH-1 tomorrow and it would be nice to just dupe my current phone.
Click to expand...
Click to collapse
No guide, but do a backup throu twrp minus efs. Transfer the backup to the PC. Unlock bootloader on the new phone, install twrp. Transfer backup to phone and restore backup and you should be golden.
qbanlinxx said:
No guide, but do a backup throu twrp minus efs. Transfer the backup to the PC. Unlock bootloader on the new phone, install twrp. Transfer backup to phone and restore backup and you should be golden.
Click to expand...
Click to collapse
Do you mean using TWRP from boot, like we do when flashing magisk, etc? I don't recall offhand the options presented as I haven't done it in a while, but I assume it'll be pretty obvious how to exclude EFS? Do I flash the correct boot.img before doing the backup? Thanks!
GospelNerd said:
Do you mean using TWRP from boot, like we do when flashing magisk, etc? I don't recall offhand the options presented as I haven't done it in a while, but I assume it'll be pretty obvious how to exclude EFS? Do I flash the correct boot.img before doing the backup? Thanks!
Click to expand...
Click to collapse
I haven't had the essential in a while, but yes boot into twrp. Once there you should see an option for backup. Honestly not sure about flashing the boot image. If the phone is in the same build you were on previously, I don't think it would be needed. My apologies, I've been using an s8+ and haven't used twrp in a while
i can confirm that cloning via twrp is working. i moved from a black moon ph-1 to a halo gray one. both where unlocked and rooted on oreo beta 8.1.
i made a backup of data partition via twrp and copied the content of /data/media manually (whilst in twrp). you have to boot once after flashing oreo and wiping.
my push tan app noticed the new hardware and stopped working so i had to receive new login crdentials from my bank. also signal stopped working and needed a new setup. i have to confirm every existing bluetooth connection for one time. that's all.
M!tch said:
i can confirm that cloning via twrp is working. i moved from a black moon ph-1 to a halo gray one. both where unlocked and rooted on oreo beta 8.1.
i made a backup of data partition via twrp and copied the content of /data/media manually (whilst in twrp). you have to boot once after flashing oreo and wiping.
Click to expand...
Click to collapse
Did TWRP ask you for a password? Mine did, but I don't know why. I assumed it had something to do w/ 8.1, but you're on it. So...
Also, to clarify, you're saying that you didn't clone the system, you just did the data partition? But you flashed and rooted 8.1 separately?
yes, i flashed full stock to make sure erverything is updated. maybe backup and restore system partition has the same effect.
you have to deactivate fingerprint and pin/pattern security to make sure twrp is able to show data.
I tried to do this with a replacement and overall it worked but it broke the fingerprint reader had to wipe it it fix it. I don't remember what I ended up doing or if I just restored from Google.
M!tch said:
yes, i flashed full stock to make sure erverything is updated. maybe backup and restore system partition has the same effect.
you have to deactivate fingerprint and pin/pattern security to make sure twrp is able to show data.
Click to expand...
Click to collapse
Worked for me taking the same path.
-Flashing up to the same version (I'm on 8.1 beta 1 [rooted]) was necessary to get on the same firmware build.
-adb push/pull is real handy for manually copying /data/media/ (/sdcard; including the TWRP backup) up to PC, then down to new phone
gk1984 said:
I tried to do this with a replacement and overall it worked but it broke the fingerprint reader had to wipe it it fix it. I don't remember what I ended up doing or if I just restored from Google.
Click to expand...
Click to collapse
Once I got it all restored including /data/media, my fingerprint reader wasn't working either. But, the Googs pulled up this beautiful doc some fine folks here put together ( @bmg1001 ?): https://media.readthedocs.org/pdf/mata/latest/mata.pdf which states...
If you move data between devices or change encryption and after restoring data from a twrp backup, you end up without a working fingerprint reader, delete /data/system/users/0/fpdata and /data/system/
users/0/settings_fingerprint.xml then you should be able to re-enroll fingerprints
Click to expand...
Click to collapse
^ I booted back into TWRP to do this, and it worked for me. Now all is good. New cloned phone is just like the old one w/broken screen which is going in the mailbox back to Essential.
my finperprint reader also wasn't working.
i've found the following solution in another thread.
konzi said:
[..]
Solution for fingerprinter:
Boot into TWRP
Go to advanced>filemanager to acces the files in your phone.
Enter the folder /data/system/user/0
Delete following files: ./fpdata/user.db, settings_fingerprint.xml
Reboot to system and set up new fingerprints with the fingerprint wizard
Everything should work normal
Hope it helps
Click to expand...
Click to collapse
Hi all, I thought I'd shout into the void to see if anyone can answer:
I broke the screen on my non-Sprint, unlocked, Magisk-rooted Ph-1. I bought a Sprint unlocked Ph-1 and have tried to clone from one to the other, but I am failing. I know I can just replace the screen, but I'd prefer to have a backup phone w/broken screen since the cost of the used Ph-1 was little more than the cost for the screen.
I've tried a bunch of different things, but the procedure has basically been:
Boot to bootloader
Install TWRP img
Install TWRP .zip
Wipe
Install LineageOS+MicroG zip, TWRP zip
Successfully boot to LineageOS
Reboot to TWRP
Restore data partition, restore /sdcard/ data manually, flash Magisk zip
Fail to boot, it'll then boot to TWRP
It also fails if I take a full image backup of the broken-screen phone with TWRP and attempt to restore that. I'm wondering if there's some sort of ID codes I need to wipe out, or if the Sprint and non-Sprint versions are sufficiently different that this won't work...can anyone solve this problem? I really like the Ph-1, it's got great build quality (have a look inside!), it's pretty, specs are plenty good enough for me. I'd like to get a backup / restore system going so that I can seamlessly switch between these two.