Database Info

Samsung "Custom Lock" icon on boot

Not sure if this has been answered already (maybe I'm bad at searching) or if it has to do with the Flash Counter, but anyone know how to get rid of the Custom Lock icon that appears on the boot up screen?

Young War said:
Not sure if this has been answered already (maybe I'm bad at searching) or if it has to do with the Flash Counter, but anyone know how to get rid of the Custom Lock icon that appears on the boot up screen?
Click to expand...
Click to collapse
Yep been answered before.
You get it when you flash a non 100% original Odin package. So like route 66.
To make it go away you have to flash the completely stock Samsung image and do the non Odin root in the dev section.
Sent from my SCH-I535 using xda app-developers app

nosympathy said:
Yep been answered before.
You get it when you flash a non 100% original Odin package. So like route 66.
To make it go away you have to flash the completely stock Samsung image and do the non Odin root in the dev section.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thank you. Is there currently any known reasons if this should cause concern? I should be good with leaving it as is atm, right?
Hoping eventually there's a flashable zip to clear that...

It also happens if you do the non ODIN root and then you freeze or remove systems apps

Will the USB Jig from the SGS2 do anything for this Device?
Sent from my SPH-D710 using Tapatalk 2

pyrostic said:
Will the USB Jig from the SGS2 do anything for this Device?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Not sure but from what I have read it doesn't appear to be compatible. Pins are in different places.
Sent from my SCH-I535 using xda premium

pyrostic said:
Will the USB Jig from the SGS2 do anything for this Device?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Yes. The jig from the s2 works and will reset the counter and eliminate the lock image.
Sent from my SCH-I535 using xda premium

wpbear said:
It also happens if you do the non ODIN root and then you freeze or remove systems apps
Click to expand...
Click to collapse
It does not ... if you disable the SysScope.apk immediately after rooting.

I like the unlock custom display. Shows that I am enjoying my custom phone!

AdamHLG said:
I like the unlock custom display. Shows that I am enjoying my custom phone!
Click to expand...
Click to collapse
+1 I love your comment. Unless bringing in for warranty, who cares.
Sent from my SCH-I535 using xda premium

AdamHLG said:
I like the unlock custom display. Shows that I am enjoying my custom phone!
Click to expand...
Click to collapse
^ this!
Sent from my SCH-I535

lowg said:
It does not ... if you disable the SysScope.apk immediately after rooting.
Click to expand...
Click to collapse
Can you go into more detail? Wouldn't you have to boot after root, so can disable SysScope be done anytime? What other uses did SysScope have?

wpbear said:
Can you go into more detail? Wouldn't you have to boot after root, so can disable SysScope be done anytime? What other uses did SysScope have?
Click to expand...
Click to collapse
If you use the "debugfs" exploit, once you obtain root, the first thing you should do is rename /system/app/SysScope.apk and you should be good.
My method was based off analysis done by Ralekdev, which according to him there is a process scanner as part of SysScope.apk that will look for apps running as root outside a list of 'whitelisted' apps.
To your question, yes it is a bit of what came first the chicken or the egg -- but I'm assuming this process scanner is not constantly running so if you just do it right away before running other apps as super user regularly there is little chance it will be tripped.

I used the odin way to root my device and the GPS does not work so I received my CLN device and need to get rid of the custom boot. Is there any other way to get rid of it?

Custom recoveries are what triggers the unlock icon. If you flash the stock recovery, the unlock icon should disappear.

There are actually other ways to get the padlock notification than custom recoveries. I've got it from modifying my framework-res.apk file, and you can get it from deleting and modifying system apps, changing ROMS through Odin and so on. It's really not a big deal unless you need to clear it for warranty related purposes. If you do, follow the guide on development, or get a jig for 3 bucks on ebay.

I just followed the guide in the development sections. Everything is A-OK and I'm ready to send back in the old one. The CLN device seems to be in pretty good shape.

ilkevinli said:
Custom recoveries are what triggers the unlock icon. If you flash the stock recovery, the unlock icon should disappear.
Click to expand...
Click to collapse
For what it's worth I flashed TWRP using dd and did not trip the counter after disabling the apk (and shared lib it uses to be sure).
Sent from my Galaxy S3

I had the unlocked lock image when I rooted with Odin and flashed bean rom, the flashed cm10 and it disappeared. I kind of like it too. It shows I'm not a square... or am I
Sent from my SCH-I535 using xda premium

Young War said:
Thank you. Is there currently any known reasons if this should cause concern? I should be good with leaving it as is atm, right?
Hoping eventually there's a flashable zip to clear that...
Click to expand...
Click to collapse
Leave it and display it like a badge of honor. A big fu to vzw if you will.

Unlocked bootloader

So if i unlock my bootloader will i be able to take the JB OTA when it arrives? If not how do i restore the locked bootloader? Also what if my phone has issues.. Would vzw notice i have this?
Sorry if these r dumb questions. I am not 100% on unlocking it.
Sent from my SCH-I535 using Tapatalk 2

Adam outler specifically stated to not do any ota's after unlocking the bootloader...besides the devs will bring us updates faster than ota anyways. Im not 100% but Adam has a stock bootloader.tar posted in the op of his thread. I believe you would flash that in the bootloader function of odin and that will relock your bootloader...now I am not 100% on this, hopefully others will confirm!

The stock bootloader and firmware flash should do the trick to take updates according to Adam himself in the unlock bootloader post. No guarantee you will ever be able to get it unlocked again though.
Also, CyanogenMod team have already switched to working on the CM10 (jellybean) non-kexec version for Verizon now according to the project status page. I wouldn't take Verizon OTA anyway, don't really want the dumbed down no local search that Apple is forcing on us with their patents.

So I should be able to flash any rom i want now? Also what recovery should I use? Stock/CWM/or TWRP? At least for the CM10s
manaox2 said:
The stock bootloader and firmware flash should do the trick to take updates according to Adam himself in the unlock bootloader post. No guarantee you will ever be able to get it unlocked again though.
Also, CyanogenMod team have already switched to working on the CM10 (jellybean) non-kexec version for Verizon now according to the project status page. I wouldn't take Verizon OTA anyway, don't really want the dumbed down no local search that Apple is forcing on us with their patents.
Click to expand...
Click to collapse

llama555 said:
So I should be able to flash any rom i want now? Also what recovery should I use? Stock/CWM/or TWRP? At least for the CM10s
Click to expand...
Click to collapse
First you should wait until Devs start releasing Roms and kernels that take advantage of the unlocked bootloader. If you are this unfamiliar with things, just relax and wait for some new/updated Roms to come out that have clear instructions for you. Don't rush into things and brick your phone because you don't fully understand what you are doing.
Sent from my SGS3 on Synergy Nightlies

Schaweet said:
First you should wait until Devs start releasing Roms and kernels that take advantage of the unlocked bootloader. If you are this unfamiliar with things, just relax and wait for some new/updated Roms to come out that have clear instructions for you. Don't rush into things and brick your phone because you don't fully understand what you are doing.
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
I love you
Sent from my SCH-I535 using xda app-developers app

Schaweet said:
First you should wait until Devs start releasing Roms and kernels that take advantage of the unlocked bootloader. If you are this unfamiliar with things, just relax and wait for some new/updated Roms to come out that have clear instructions for you. Don't rush into things and brick your phone because you don't fully understand what you are doing.
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
I mean I knew exactly how to do things on my DX I just am not as sure with my S3. What recovery would you recommend?

llama555 said:
I mean I knew exactly how to do things on my DX I just am not as sure with my S3. What recovery would you recommend?
Click to expand...
Click to collapse
At this point it's not the recovery but the lack of unlocked bootloader roms (non kexec) for vzws3. I've used rom manager and ez recovery with the s3 with great success.
Sent from my SCH-I535 using Tapatalk 2

voodoomanx said:
At this point it's not the recovery but the lack of unlocked bootloader roms (non kexec) for vzws3. I've used rom manager and ez recovery with the s3 with great success.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The only big difference between cwm 6 and previous versions is its support for kexec, but otherwise does the same thing and can be used for any of the Roms we already have (from what I understand. I tried finding the original thread i read that on but came up short so if I'm wrong someone please correct me as I don't want to spread false information).
And honestly I'm sure almost every rom will be updated within 24 hours to reflect this if not sooner and development will be full steam ahead! Just beware of an OTA cause you know Verizon is not gonna be happy we broke out of their sphere of influence. You can prolly guarantee this "issue" will be towards the top of their to-do list.
Sent from my SCH-I535 using xda app-developers app

Otas cannot be forced though right?
We always have to accept it on our end correct?

asmallchild said:
Otas cannot be forced though right?
We always have to accept it on our end correct?
Click to expand...
Click to collapse
That's not always the case anymore. I've noticed Rezound users have been forced OTA's (update installs without your explicit approval) which means we very well could see the same as well.
Sent from my SCH-I535 using xda app-developers app

asmallchild said:
Otas cannot be forced though right?
We always have to accept it on our end correct?
Click to expand...
Click to collapse
If you are on a custom ROM most devs will have the OTAs killed off anyways. If you are not on a custom ROM there is really no point in unlocking it.

Sccrluk9 said:
If you are on a custom ROM most devs will have the OTAs killed off anyways. If you are not on a custom ROM there is really no point in unlocking it.
Click to expand...
Click to collapse
Phew good, I'm on Synergy, I think they've blocked OTAs

Sccrluk9 said:
If you are on a custom ROM most devs will have the OTAs killed off anyways. If you are not on a custom ROM there is really no point in unlocking it.
Click to expand...
Click to collapse
even if you unlock the bootloader and are worried about OTA's just install clockwork mod or team win. the custom recovery will stop the installation of the files. last line of defense as some phones will download and OTA and install it regardless of what you do (rezound, thunderbolt, etc)

droidstyle said:
besides the devs will bring us updates faster than ota anyways.
Click to expand...
Click to collapse
Always, +1. I've never understood the desire to get OTAs afteryou start modding your phone.
llama555 said:
Also what recovery should I use? Stock/CWM/or TWRP? At least for the CM10s
Click to expand...
Click to collapse
As long as there are still kexec roms out there, you'll still need a kexec recovery to flash them. If you know for sure you won't be using kexec, use whatever you want except for stock. Don't ever flash the stock recovery unless you're mailing it off to Verizon.
drbobmd said:
The only big difference between cwm 6 and previous versions is its support for kexec, but otherwise does the same thing and can be used for any of the Roms we already have (from what I understand.
Click to expand...
Click to collapse
That isn't strictly true. CWM 6.x has a couple of nice features that CWM 5.8.x doesn't, like the deduplication technique to save you space when you have multiple backups. You're right though, in that if you're happy with CWM, there's no reason to switch after unlocking.

SFniner415 said:
I love you
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Off topic, sorry, but GO NINERS!!!
Sent from my SCH-I535 using Tapatalk 2

lazarus2405 said:
Always, +1. I've never understood the desire to get OTAs afteryou start modding your phone.
As long as there are still kexec roms out there, you'll still need a kexec recovery to flash them. If you know for sure you won't be using kexec, use whatever you want except for stock. Don't ever flash the stock recovery unless you're mailing it off to Verizon.
That isn't strictly true. CWM 6.x has a couple of nice features that CWM 5.8.x doesn't, like the deduplication technique to save you space when you have multiple backups. You're right though, in that if you're happy with CWM, there's no reason to switch after unlocking.
Click to expand...
Click to collapse
Good to know thank you
Sent from my SCH-I535 using xda app-developers app

so what if your rooted and don't wanna
Flash a Rom is there anything, esle to do to stop an ota?
Sent from my SCH-I535 using xda premium

Hulk0069 said:
so what if your rooted and don't wanna
Flash a Rom is there anything, esle to do to stop an ota?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
My best guess would be to find out what files are responsible for it and see if they are safe to remove via root explorer or something.
Sent from my SCH-I535 using xda premium

Sccrluk9 said:
If you are on a custom ROM most devs will have the OTAs killed off anyways. If you are not on a custom ROM there is really no point in unlocking it.
Click to expand...
Click to collapse
The OTA's also fail once they boot into recovery if the stock recovery isn't there. So it's not likely you'll get a forced OTA that works.

Any reason to unlock the bootloader?

If I'm not big on flashing roms at the moment, is there any good reason to unlock the bootloader? The only benefit I've read so far is that booting up is a bit faster.
Also, seeing as how rooting and unrooting is pretty easy without the use of odin/flashing, is there a way to re-lock the bootloader without odin (in case an OTA update comes along the way)?

Any OTAs that come along are likely to break the insecure bootloader.
If you ever intend to use custom ROMs I would suggest not accepting any OTAs regardless.

Download ez unlock from the market to lock and re-lock.

dunderball said:
If I'm not big on flashing roms at the moment, is there any good reason to unlock the bootloader? The only benefit I've read so far is that booting up is a bit faster.
Also, seeing as how rooting and unrooting is pretty easy without the use of odin/flashing, is there a way to re-lock the bootloader without odin (in case an OTA update comes along the way)?
Click to expand...
Click to collapse
To answer your question, there is no reason unless you want to flash a ROM with a custom kernel (eg CM or AOKP).
You can backup your bootloader and restore using terminal / dd, and I think some of 'one click' tools also are doing this now sounds like.
Sent from my Galaxy S3

So bootloader needs to be unlock more for kernel, right?
Sent from my SCH-I535 using Tapatalk 2

From here on out, i would think that 90% of kernel and rom development will be aimed towards unlocked bootloaders.

download app from market to unlock. One click. Easy!
Sent from my SCH-I535 using Tapatalk 2

djisia87 said:
download app from market to unlock. One click. Easy!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It even says "that was easy" lol

that was easy

If for no other reason but to tell Verizon FU Icehole's.
Power to the People.:highfive:

ImgBurn said:
If for no other reason but to tell Verizon FU Icehole's.
Power to the People.:highfive:
Click to expand...
Click to collapse
This.
Sent from my SCH-I535 using xda premium

ExodusC said:
Any OTAs that come along are likely to break the insecure bootloader.
If you ever intend to use custom ROMs I would suggest not accepting any OTAs regardless.
Click to expand...
Click to collapse
Wouldn't a person be able to Odin the stock .tar that we have now to overwrite any **** Verizon tries to push on us?
Sent from my SCH-I535 using Tapatalk 2

pyrostic said:
Wouldn't a person be able to Odin the stock .tar that we have now to overwrite any **** Verizon tries to push on us?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Where is this .tar located?

You have to unlock the bootloader to change boot images... right?

Root checker

I see the synergy rom blocks this but what if you root only or use a rom that doesn't block it? How is your phone checked for root? Only if sent in or do they monitor this remotely? Any way to block it on stock?
Sent from my SCH-I535 using xda premium

I dont think it matters...The root blocker just helps keep Samsungs nose out of you business on what you do with your phone.. Im not sure if you can block it with stock but most custom roms automatically block it.

The program that checks on a number of things including what's running as root is called SysScope.apk
You can disable it in stock rooted.

Bleelas said:
The program that checks on a number of things including what's running as root is called SysScope.apk
You can disable it in stock rooted.
Click to expand...
Click to collapse
Does it matter to Samsung if we root and install custom roms on these phones?

It will matter to VzW if you go in to file a claim on a broken phone. No idea on samsung. But VZW cares.
--Sent from GlaDos baked potato

Legato Bluesummers said:
It will matter to VzW if you go in to file a claim on a broken phone. No idea on samsung. But VZW cares.
--Sent from GlaDos baked potato
Click to expand...
Click to collapse
Is this something that can still be checked if you flash back to stock using Odin? I can't imagine they are checking this remotely? My concern is that when you root your phone sends something to verizon letting them know.... If they can't figure it out unless they have my phone in hand I'm not going to worry about it.
Sent from my SCH-I535 using xda premium

Ryno77 said:
Is this something that can still be checked if you flash back to stock using Odin? I can't imagine they are checking this remotely? My concern is that when you root your phone sends something to verizon letting them know.... If they can't figure it out unless they have my phone in hand I'm not going to worry about it.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
a fresh odin back to stock with a data wipe/factory reset will remove all traces of being modded.

That's what I wanted to know.. Thanks.
Sent from my SCH-I535 using xda premium

nighthawk34691 said:
Does it matter to Samsung if we root and install custom roms on these phones?
Click to expand...
Click to collapse
You don't have to worry about Samsung, they don't care period. On the other hand, Verizon is the one you should...if you want to exchange your phone. In reality, the chance that they're going to check your phone for root is slim, but just to be on the safe side, just flash back factory stock rom and do a factory reset, you should be fine. If you did install some custom rom, make sure you clear the "custom rom counter" if it has been triggered.

Legato Bluesummers said:
It will matter to VzW if you go in to file a claim on a broken phone. No idea on samsung. But VZW cares.
--Sent from GlaDos baked potato
Click to expand...
Click to collapse
Oh yeah...I know VZW cares because they are the 1st ones to void your warranty on ur device if they find you tampered with it in any way.

how long before someone figures out how to root this phone?

how long before someone figures out how to root this phone? I can't buy it unless it's rooted. thanks!

youphone said:
how long before someone figures out how to root this phone? I can't buy it unless it's rooted. thanks!
Click to expand...
Click to collapse
I think the real question is how long before someone finds a software exploit that allows S-Off.
I honestly think we have a long, long wait, if we ever see it.
Just my opinion.

Mike02z said:
I think the real question is how long before someone finds a software exploit that allows S-Off.
I honestly think we have a long, long wait, if we ever see it.
Just my opinion.
Click to expand...
Click to collapse
I think I read somewhere that it will be nearly impossible to root this phone....
GPE or developer's edition isn't for Verizon, so I guess this means no HTC One M8 for me.

It's never nearly impossible to root
Sent from my SM-N900V using Tapatalk

Who knows. Silly question.
Hopefully someone will
Sent from my VS980 4G using XDA Premium 4 mobile app

Im pretty content with stock ATM. Actually enjoying blinkfeed now and sense 6 ain't too shabby. That being said I'd love a good rom like viper.
Sent from my HTC6525LVW using Tapatalk

wtoj34 said:
Im pretty content with stock ATM. Actually enjoying blinkfeed now and sense 6 ain't too shabby. That being said I'd love a good rom like viper.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I sent the Viper team a System dump the day of release. Once we have a method of unlock, I doubt Verizon support will be far behind. (And I'll be beta testing it...)
Sent from my HTC6525LVW using XDA Premium 4 mobile app

I'm kind of wondering how long it will take and if it will get done? I'm coming from the Note3, which had terrible developer support because of the boot loader, and I don't want the same thing to happen here. I paid full retail, but I'm thinking of returning;
I feel like two days in if we don't have root yet, this thing is going to be tough to crack.
Every other phone I had, had root pretty much in the first day.
I'm not sure what to do.
Sent from my HTC6525LVW using xda app-developers app

PhilPan said:
I'm kind of wondering how long it will take and if it will get done? I'm coming from the Note3, which had terrible developer support because of the boot loader, and I don't want the same thing to happen here. I paid full retail, but I'm thinking of returning;
I feel like two days in if we don't have root yet, this thing is going to be tough to crack.
Every other phone I had, had root pretty much in the first day.
I'm not sure what to do.
Sent from my HTC6525LVW using xda app-developers app
Click to expand...
Click to collapse
Are you kidding? Two days for a phone chipset that had like 10 iterations of security? I will bet that no one will get a root exploit unless it comes in the form of s-off because its silly to have root without s-off on HTC phones. Beups,jcase or whoever is working on the phone likely have root exploits already (and they always save one or two for a rainy day) and are not going to release it on it's own. Be patient, stop asking for ETAs.

How is root only different on HTC devices vs other OEMs?
Sent from my HTC One M8 using XDA Premium 4 mobile app

Crooke356 said:
How is root only different on HTC devices vs other OEMs?
Sent from my HTC One M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'd like to be know too. Coming from Samsung Note2
Sent from my GT-N7105 using XDA Premium 4 mobile app

Androider4Life said:
I'd like to be know too. Coming from Samsung Note2
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well for one root only won't allow us an insecure kernel to be flashed. That means /system write protection will still be in place.
Unlock allows you to flash custom recovery and kernels.
S-off let's you do all (even firmware downgrades)
Sent from my HTC6600LVW using Tapatalk

dottat said:
Well for one root only won't allow us an insecure kernel to be flashed. That means /system write protection will still be in place.
Unlock allows you to flash custom recovery and kernels.
S-off let's you do all (even firmware downgrades)
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
So then what is "root only" able to do? Especially the type we know have available that only roots after a minute after a reboot so that first minute on reboot you are not rooted. Makes me think rooted apps/tweaks won't work right since after boot they can't go into effect since root hasn't kicked in yet???

deeznuts said:
So then what is "root only" able to do? Especially the type we know have available that only roots after a minute after a reboot so that first minute on reboot you are not rooted. Makes me think rooted apps/tweaks won't work right since after boot they can't go into effect since root hasn't kicked in yet???
Click to expand...
Click to collapse
A lot won't work right. Write protection will revert most changes back after a reboot. Root can be effective for some changes that don't need to persist a reboot. Just all depends on what you use root for. Non-system app data back-up/restore is a good example.
Sent from my HTC6600LVW using Tapatalk

dottat said:
A lot won't work right. Write protection will revert most changes back after a reboot. Root can be effective for some changes that don't need to persist a reboot. Just all depends on what you use root for. Non-system app data back-up/restore is a good example.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
So basically anything that needs root at startup won't work. So basically this method of root is only good to maybe copy internal files to external sd card bypassing that kit Kat crap?

deeznuts said:
So basically anything that needs root at startup won't work. So basically this method of root is only good to maybe copy internal files to external sd card bypassing that kit Kat crap?
Click to expand...
Click to collapse
Until we figure out a method to disable write protection that's pretty much gonna be it. Write protection on this phone is just as much a pain in the ass as it was on the one and one max.
It will happen though. That's the only thing we know for certain.
Sent from my HTC6600LVW using Tapatalk

dottat said:
Until we figure out a method to disable write protection that's pretty much gonna be it. Write protection on this phone is just as much a pain in the ass as it was on the one and one max.
It will happen though. That's the only thing we know for certain.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
Ok. Thank you for explaining. I was always spoiled before and HTC devices I had were simple s-Off or everything but s-Off so could still do just about anything. Just gotta be patient but honestly surprised how fast we got this temp root only already! In sure the development will start kicking in.

deeznuts said:
Ok. Thank you for explaining. I was always spoiled before and HTC devices I had were simple s-Off or everything but s-Off so could still do just about anything. Just gotta be patient but honestly surprised how fast we got this temp root only already! In sure the development will start kicking in.
Click to expand...
Click to collapse
The biggest hurdle for us is the fact we cannot even use HTC dev to boot loader unlock. That's why we now have to wait to get a working s-off method. Its only a matter of time.
Sent from my HTC6600LVW using Tapatalk

I'd think you should be able to HTCdev unlock the bootloader and do what I did on my old EVO 3D which was to flash the boot.img separately through fastboot. What am I saying though? It's been a while since I have had a HTC device besides my sister's media-only EVO running CM7.
Sent from my Amazon Kindle Fire using XDA Premium 4 mobile app

yattaro said:
I'd think you should be able to HTCdev unlock the bootloader and do what I did on my old EVO 3D which was to flash the boot.img separately through fastboot. What am I saying though? It's been a while since I have had a HTC device besides my sister's media-only EVO running CM7.
Sent from my Amazon Kindle Fire using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My Adaway works again now...when you haven't seen an AD in an app in years they are HUGELY annoying....
and I was able to move my app data from my DNA to the M8 from MyBackup Pro..so there are some huge perks with this root.
And conversely being able to back up APK + DATA and your sense home screen layouts will come in handy when the inevitable S-OFF comes and we need to wipe our devices