Database Develop

Vulnerability to open S5 (Verizon) bootloader released

the guy who unlocked the bootloader on Verizon's s5 variant has released a document detailing what I believe is the procedure. Could this open the door for ATT's variant to be unlocked?
https://twitter.com/firewaterdevs/status/713906161834192896
http://theroot.ninja/disclosures/SAMDUNK_1.0-03262016.pdf

sensei22 said:
the guy who unlocked the bootloader on Verizon's s5 variant has released a document detailing what I believe is the procedure. Could this open the door for ATT's variant to be unlocked?
https://twitter.com/firewaterdevs/status/713906161834192896
http://theroot.ninja/disclosures/SAMDUNK_1.0-03262016.pdf
Click to expand...
Click to collapse
Possibly, based on what I read from it though it needs the string from the dev-edition device, they have that with the Verizon version so it's easy to get, we only have the one, so I think(speculation) it would be trivial at best to repeat this in our model since we don't even know what to set the CID to to make it reflect that of the 'dev edition', I don't think we're getting a towelroot from this at least[emoji14]
Sent from my SAMSUNG-SM-G900A using Tapatalk

I'm going to take a guess that the Verizon and AT&T phones are both unlockable via the same method. I don't even know how to run Samdunk.. Phone or PC? (Can't be Phone if we have no root access :/)

this really seems promising, i still love my s5 and would like to have the bootloader unlocked at some point.

I wouldn't get your hopes up. That unlock requires root which means anyone on 5.0 or above already is SOL, even IF that method worked on AT&T.

You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.

Guicrith said:
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Click to expand...
Click to collapse
My att s5 has 15 for the first 2 digits of the Cid.

Guicrith said:
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Click to expand...
Click to collapse
Mine is 15, I may be willing to be the guinea pig for this as long as it's not a 100% brick. I'm not entirely sure about the tmo s5 simply having the same hardware will make it work, if something like that was the case why did Verizon folks have to wait for someone with the dev Verizon s5 to upload their aboot?
Sent from my SAMSUNG-SM-G900A using Tapatalk

Anyone here willing to risk bricking their device with a 15 series chip pm me!

I saw on a thread maybe the Verizon s5 bootloader unlocking thread a post about copying your original boot chain to an SD card so incase you brick you can still boot the original boot chain off of your SD. Apparently your SD has to be class 10. Just more food for thought.

How do I check my cid? I'm tempted to test as I have the S7 now. But if this works, I may very well return the S7 due to locked bootloader.

TehPirate_ said:
How do I check my cid? I'm tempted to test as I have the S7 now. But if this works, I may very well return the S7 due to locked bootloader.
Click to expand...
Click to collapse
Brickbug emmc from play store. Still not clear if we can make it work, it should and can, but I think we're missing the att 'dev edition'(maybe factory has it with this?) aboot as just using the Verizon one doesn't seem to work.
Sent from my SAMSUNG-SM-G900A using Tapatalk

Rakuu said:
Brickbug emmc from play store. Still not clear if we can make it work, it should and can, but I think we're missing the att 'dev edition'(maybe factory has it with this?) aboot as just using the Verizon one doesn't seem to work.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Shame, mines Toshiba (11)

I just want to let everyone know that I've been involved with the thread over at Verizon and guinea pigged for us. I do have an active, however that shouldn't matter. At the moment, you can run both methods and it will appear to be successful, even changing the Cid, but it doesn't unlock the bootloader.
So for now, we're out of luck.

N4styN1ghtm4r3 said:
I just want to let everyone know that I've been involved with the thread over at Verizon and guinea pigged for us. I do have an active, however that shouldn't matter. At the moment, you can run both methods and it will appear to be successful, even changing the Cid, but it doesn't unlock the bootloader.
So for now, we're out of luck.
Click to expand...
Click to collapse
Damn, I was hoping this would pan out as I have a CID that starts with 15. Checked yesterday when advised in the TMS5 3.0 thread. I got this s5 from Samsung insights so I was hoping that'd help but it's At&t branded with locked bootloader. Waiting patiently for an option to unlock bootloader as I don't plan to get a new phone anytime soon.
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme

joshua14 said:
Damn, I was hoping this would pan out as I have a CID that starts with 15. Checked yesterday when advised in the TMS5 3.0 thread. I got this s5 from Samsung insights so I was hoping that'd help but it's At&t branded with locked bootloader. Waiting patiently for an option to unlock bootloader as I don't plan to get a new phone anytime soon.
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
Click to expand...
Click to collapse
If you're comfortable doing this kind of stuff, then you can try without risking anything. Nobody with an original s5 has tried it, only me, but again, mine is an active. That may or may not be the reason it didn't work for me, but if somebody with an original s5 wants to try, that would give us a definitive answer.
I did both methods and everything went fine, with no errors. It simply didn't unlock. So feel free to give it a shot, you'll just have to restore your old Cid if it fails, which is no big deal. The only thing I'd give a heads up on, is both methods erase your SD card, so use a spare SD card or back up your files from it somewhere else.
Good luck if you try!!

N4styN1ghtm4r3 said:
If you're comfortable doing this kind of stuff, then you can try without risking anything. Nobody with an original s5 has tried it, only me, but again, mine is an active. That may or may not be the reason it didn't work for me, but if somebody with an original s5 wants to try, that would give us a definitive answer.
I did both methods and everything went fine, with no errors. It simply didn't unlock. So feel free to give it a shot, you'll just have to restore your old Cid if it fails, which is no big deal. The only thing I'd give a heads up on, is both methods erase your SD card, so use a spare SD card or back up your files from it somewhere else.
Good luck if you try!!
Click to expand...
Click to collapse
This will be something to try for the weekend. I have backups for both SS and FF so as long as I don't risk full bricking then I'm game. I have a few spare sd cards too. I never took any OTA updates, the first one that tried getting pushed on me while still within the 6 month insights program I rooted with TowelRoot and froze with TB. Other than that I didn't do much else until more recently to go to Muniz_ri 5.0 keeproot and then to TMS5-3.0-TMBUILD. I was hoping of convincing At&t to unlock the bootloader along with the sim unlock since they don't have any rights to this phone. I still have my Next plan s5 thru them so I can toy with this one, just don't want to end up completely bricking either. I have 2 S3 that I put full custom CM builds on for the kids to play with, just turned off root. Lol
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme

joshua14 said:
This will be something to try for the weekend. I have backups for both SS and FF so as long as I don't risk full bricking then I'm game. I have a few spare sd cards too. I never took any OTA updates, the first one that tried getting pushed on me while still within the 6 month insights program I rooted with TowelRoot and froze with TB. Other than that I didn't do much else until more recently to go to Muniz_ri 5.0 keeproot and then to TMS5-3.0-TMBUILD. I was hoping of convincing At&t to unlock the bootloader along with the sim unlock since they don't have any rights to this phone. I still have my Next plan s5 thru them so I can toy with this one, just don't want to end up completely bricking either. I have 2 S3 that I put full custom CM builds on for the kids to play with, just turned off root. Lol
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
Click to expand...
Click to collapse
Yea like I said, as long as you follow the steps closely, there isn't a chance of bricking, it just won't unlock. Let us know when you give it a shot!

Still don't work as of yet...maybe never. The main thread on this is here:
http://forum.xda-developers.com/ver...locking-galaxys-s5-bootloader-t3337909/page77

samccfl99 said:
Still don't work as of yet...maybe never. The main thread on this is here:
http://forum.xda-developers.com/ver...locking-galaxys-s5-bootloader-t3337909/page77
Click to expand...
Click to collapse
It's likely to be never unless we get the proper CID, which as about a needle in a haystack to guess as the bootloader key.
Sent from my SAMSUNG-SM-G900A using Tapatalk

Root and Android Pay

I really want to root my Droid Turbo, but I use Android Pay pretty frequently. I read once the phone is rooted, Android Pay will no longer work. I've read a few different things on the site and I'm just looking for some clarity. What exactly causes it to stop working? Is it rooting, unlocking the bootloader, both?
Since you have to unlock the bootloader for the Turbo root, and it sounds like once I unlock it there's no way to safely re-lock it, if I go through with the root, there's really no going back to Android Pay ever again because unlocking the bootloader.
Is there no shot of this working if I root my Droid Turbo? If this has explicitly been discussed and defined, I apologize, but I couldn't find an definitive answer to it.

hyphy88 said:
I really want to root my Droid Turbo, but I use Android Pay pretty frequently. I read once the phone is rooted, Android Pay will no longer work. I've read a few different things on the site and I'm just looking for some clarity. What exactly causes it to stop working? Is it rooting, unlocking the bootloader, both?
Since you have to unlock the bootloader for the Turbo root, and it sounds like once I unlock it there's no way to safely re-lock it, if I go through with the root, there's really no going back to Android Pay ever again because unlocking the bootloader.
Is there no shot of this working if I root my Droid Turbo? If this has explicitly been discussed and defined, I apologize, but I couldn't find an definitive answer to it.
Click to expand...
Click to collapse
Getting Android Pay to work on a modified device is a constant cat and mouse game. A few workarounds were found and promptly patched by Google in Android Pay/Google Play Services/ Google App updates. If you use it frequently, unlocking is a bad idea. Android Pay might still work on an unlocked device, but any change that you make to any system files will cause it to not work, so there's no point in unlocking.
Even if you managed to root without unlocking (via moforoot or through the terrible kingroot method), you would break Android Pay because root is one of the first things that it looks for, and none of the apps/xposed modules designed to fool it are successful at doing so.

TheSt33v said:
Getting Android Pay to work on a modified device is a constant cat and mouse game. A few workarounds were found and promptly patched by Google in Android Pay/Google Play Services/ Google App updates. If you use it frequently, unlocking is a bad idea. Android Pay might still work on an unlocked device, but any change that you make to any system files will cause it to not work, so there's no point in unlocking.
Even if you managed to root without unlocking (via moforoot or through the terrible kingroot method), you would break Android Pay because root is one of the first things that it looks for, and none of the apps/xposed modules designed to fool it are successful at doing so.
Click to expand...
Click to collapse
Thank you, I rooted, it doesn't work. Now I'm free to flash custom roms and make modifications without the worry of breaking Android Pay. Whatever, small loss to gain so much. Thanks again for your reply.

TheSt33v said:
...any change that you make to any system files will cause it to not work, so there's no point in unlocking.
Click to expand...
Click to collapse
I have an unlocked bootloader, TWRP recovery, and even flashed an emoji mod and the volume boost mods and haven't lost Android Pay.
Just earlier today, I used Sunshine for temp root and used AdAway to modify the hosts file and block ads. Once I rebooted (to disable the Sunshine temp root), Android Pay worked just fine.
Sent from my XT1254 using XDA-Developers mobile app

syphix said:
I have an unlocked bootloader, TWRP recovery, and even flashed an emoji mod and the volume boost mods and haven't lost Android Pay.
Just earlier today, I used Sunshine for temp root and used AdAway to modify the hosts file and block ads. Once I rebooted (to disable the Sunshine temp root), Android Pay worked just fine.
Sent from my XT1254 using XDA-Developers mobile app
Click to expand...
Click to collapse
Makes sense. You didn't add any additional files to the system partition. I think as long as that's the case, Android Pay will work.

syphix said:
I have an unlocked bootloader, TWRP recovery, and even flashed an emoji mod and the volume boost mods and haven't lost Android Pay.
Just earlier today, I used Sunshine for temp root and used AdAway to modify the hosts file and block ads. Once I rebooted (to disable the Sunshine temp root), Android Pay worked just fine.
Sent from my XT1254 using XDA-Developers mobile app
Click to expand...
Click to collapse
did you have android pay PRIOR to root/unlock? I've read somewhere that a work-around is to disable root, reboot, setup android pay, then re-establish root.
thanks...

jco23 said:
did you have android pay PRIOR to root/unlock? I've read somewhere that a work-around is to disable root, reboot, setup android pay, then re-establish root.
thanks...
Click to expand...
Click to collapse
That workaround will allow you to add cards, but paying will fail if you try to use them.

TheSt33v said:
That workaround will allow you to add cards, but paying will fail if you try to use them.
Click to expand...
Click to collapse
I think that changing the system is the only act preventing Android Pay to work properly. Neither unlocking bootloader nor rooting (as long as it is the systemless) does that. I believe that method used by GPS is just checking system hash (MD5 signature). Every system change brakes it. Safetynet test shows you authentically whether Android Pay could work or not. To date I haven't seen a single proof otherwise.

Jj

Has anyone done the systemless root for the turbo? I tried but either missed a step or it didn't work for my device
Sent from my XT1254 using XDA-Developers mobile app

Is it worth it to root the device??

As the title suggests the question is it wise to root the tab now like what is scenario of custom roms and kernels??
Please reply soon.....

depend on your device since the development of custom rom are less for tab s2. i dont event root any of my device nowadays.

edan1979 said:
depend on your device since the development of custom rom are less for tab s2. i dont event root any of my device nowadays.
Click to expand...
Click to collapse
So what do you say ultimately should I root with Magisk or wait..

Androbots said:
So what do you say ultimately should I root with Magisk or wait..
Click to expand...
Click to collapse
Not a big fan of Magisk but I believe it is worth it to root any device. Granted, you are voiding your warranty and risking losing out if your device gets bricked or fails for some reason. But I like having the control and added access that rooting gives me. Plus the custom ROMs usually provide less bloat and added features that make them preferable over stock.
In the end it is a matter of personal preference.

pastorbob62 said:
Not a big fan of Magisk but I believe it is worth it to root any device. Granted, you are voiding your warranty and risking losing out if your device gets bricked or fails for some reason. But I like having the control and added access that rooting gives me. Plus the custom ROMs usually provide less bloat and added features that make them preferable over stock.
In the end it is a matter of personal preference.
Click to expand...
Click to collapse
Actually i am a bit confused.... My warranty has gone since March 17 and I am just thinking if the device will get any more updates like the update to 7.1 official ohh... Btw i am using a tab s2 T710 (2015).. Thanks for the tips... ?
Will knox create any probs when I root?

Androbots said:
Actually i am a bit confused.... My warranty has gone since March 17 and I am just thinking if the device will get any more updates like the update to 7.1 official ohh... Btw i am using a tab s2 T710 (2015).. Thanks for the tips...
Will knox create any probs when I root?
Click to expand...
Click to collapse
It will detect the root but it doesn't cause any issues. However if Samsung does release another update (don't hold your breath waiting for it), you might not be able to apply it through OTA. Also, be sure to search for and use the correct method of rooting for your device. Trying to root incorrectly will give you nothing but problems and may brick your device. I have the T813 9.7" so I can't direct you to the procedure for your device.
Bottom line - read, read and read some more and be certain you understand the procedure and risks before you take the next step.

pastorbob62 said:
It will detect the root but it doesn't cause any issues. However if Samsung does release another update (don't hold your breath waiting for it), you might not be able to apply it through OTA. Also, be sure to search for and use the correct method of rooting for your device. Trying to root incorrectly will give you nothing but problems and may brick your device. I have the T813 9.7" so I can't direct you to the procedure for your device.
Bottom line - read, read and read some more and be certain you understand the procedure and risks before you take the next step.
Click to expand...
Click to collapse
I just rooted my tab today.. With Magisk.. Works well

Androbots said:
I just rooted my tab today.. With Magisk.. Works well
Click to expand...
Click to collapse
Awesome! Glad to hear it. :good::good::good::good::good:

Rooting the Moto E4 Plus (Boost Mobile)

I have a moto E4 Plus that I bought from my carrier Boost Mobile and I was wondering, once my warranty is up and over with I was going to root it and get the full experience of android but I don't know if I can do that for my phone.
My phones model is: Moto E4 Plus (I couldn't find anything in settings about it other than this)
Bought from Boost Mobile
Has 2GB of RAM, Storage or (ROM) is 16 GB, Display is 1280x720 HD, Version is PVTB, SKU XT1776, Camera is Back 13 MP & Front is 5 MP.
Build Number: NCRS26.58-44-6
Security Patch Level: March 1,2018 (I actually just updated it to this)
Android Version is 7.1.1
Thats all but I want to do this with root
1. Have TWRP or ClockworkMod (prefer TWRP)
2. Have a custom ROM LineageOS or Cyanogen Mod
3. Have access to root apps

Absolutely! I'm running one as well..
Sent from my Moto E (4) Plus using Tapatalk

I've done it three times. I suggest you get your unlock code from Motorolla now. You don't have to unlock your phone yet if you are concerned about the warranty. However, it might be a good idea to get it now in case Boost decides to make their prepaid phones ineligible to be unlocked. I believe Verizon prepaid Moto E4 Plus phones cannot receive the unlock code.
Follow this guide here. It's pretty easy. Only wrinkle was wiping the phone after first booting with TWRP. You need to reboot back into TWRP a second time in order to successfully wipe.

Doesn't getting your unlock code from Motorola void your warranty if you use it or not?

As @imneveral0ne mentioned, getting your unlock code voids warranty. I'd hold off until your ready

That warning is toothless. It's illegal for a company to void your warranty due to the 1975 Magnuson-Moss Warranty Act. They cannot force you to waive your rights if you modify your device if it's over $15. This has come up before and the response from Motorolla is basically this:
Unlocking the bootloader will show your warranty as void.
However, if an unrelated physical material failure should occur, such as a bad volume rocker or a failed speaker, it will be covered if the phone shows no signs of physical abuse. The key is that the problem can't be traced to software or abuse.
These same principles apply to Extended Warranty.
Click to expand...
Click to collapse
If the phone is damaged due to you unlocking it, you're screwed. If the issue is unrelated to the phone being unlocked, then they will honor the warranty. That's what the law says basically.

Sizzlechest said:
That warning is toothless. It's illegal for a company to void your warranty due to the 1975 Magnuson-Moss Warranty Act. They cannot force you to waive your rights if you modify your device if it's over $15. This has come up before and the response from Motorola is basically this:
If the phone is damaged due to you unlocking it, you're screwed. If the issue is unrelated to the phone being unlocked, then they will honor the warranty. That's what the law says basically.
Click to expand...
Click to collapse
What I got from that was that Motorola will be happy to help with a hardware issue (like pwr & vols) but that anything related to software is all on us. So if you don't like the way something works, flash another ROM or go "Completely Back to Stock)

bcrichster said:
What I got from that was that Motorola will be happy to help with a hardware issue (like pwr & vols) but that anything related to software is all on us. So if you don't like the way something works, flash another ROM or go "Completely Back to Stock)
Click to expand...
Click to collapse
Yes. Also, if your mobile carrier or Google decides to ban your phone because it's unlocked, don't come crying to Motorola.

Sizzlechest said:
Yes. Also, if your mobile carrier or Google decides to ban your phone because it's unlocked, don't come crying to Motorola.
Click to expand...
Click to collapse
Meh..
1. - Not stressing Google, I'm working on an F-Droid build anyways. Heck, PAOSP has F-Droid (I think).
2. - This was just a $70 phone, I'll get something else if I have to. But I prefer Root and Custom ROMs to stock almost any day.
Sent from my Moto E (4) Plus using Tapatalk

Don't get me wrong. None of those things will happen. It's just Motorola covering their asses with legalese.

is there a bloteware list for the e4plus i want to earease all i can!

sinr764 said:
is there a bloteware list for the e4plus i want to earease all i can!
Click to expand...
Click to collapse
All the bloatware is in the oem partition. You can't access it through the OS without having the partition mounted r/w which you have to modify the fstab.qcom in the kernel to do. To do that, tou need to unpack, modify and repack the kernel. Only other way is to do it through the file manager in TWRP. I can give you a debloated oem.img you can flash if I knew what firmware version your phone is running.

SM-S781B to SM-781U Crossflash?

Hello,
As there is no autopatch firmware currently available for SM-781B.
I want to know can we cross flash the S781B International Variant with S781U?
Also i want to use the below autopatch firmware after rebranding it with S781U. Is it really possible? anyone tested before?
[S20_FE SM-G781U/U1_Snapdragon]-[Upgrade Easily Firmware Using Odin]-[Automatically Root Remove Forceencrypt Patch Bluetooth And Fix Safetynet]
Must Have An Unlocked Bootloader To Do This! This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install...
forum.xda-developers.com

the idea of flashing to U firmware just so you can use something to save you some time is crazy. why mess up your csc over something so dumb ? I'm pretty sure that file is completely out of date now anyway regarding the twrp version it has.

Actually i bought this phone from someone and after a month it is blocked by networks. Now the charges to reopen the networks from our telecommunication authority is $360 which are too much high to pay such a tax.
That is why looking for an alternative solution by which this can be bypassed even i am ready to pay the fee but not that much.

you've bought a stolen phone or one sold off by someone who hasn't finished paying for it.
leave the seller some terrible feedback. flashing different firmware won't get around the IMEI number being blocked. pay the fee or if possible demand a refund if you did it thru a site that will support it.