I had a few questions about rootign and the SGS3.
1. Do i need to root to use launchers like nova and apex?
2. If I launch and mandatory updates come out will I be able to download them if I root?
3. Is it worth it?
Thanks in advance. Ive only rooted older phones that didnt regularly receive updates and my knowledge is extremely limited.
ddurandSGS3 said:
I had a few questions about rootign and the SGS3.
1. Do i need to root to use launchers like nova and apex?
2. If I launch and mandatory updates come out will I be able to download them if I root?
3. Is it worth it?
Thanks in advance. Ive only rooted older phones that didnt regularly receive updates and my knowledge is extremely limited.
Click to expand...
Click to collapse
1. No.. those launchers will work without root
2. Not sure about this..
3. Up to you and what apps you use or like to use. There are some really great apps out there that require root. Think of having root the same as being an administrator on your PC. Lets you have TOTAL control of your device. I think its well worth it.. for me.. for someone who likes to use root apps!
sent from my Galaxy S III
I hesitated to root to ! I did it just to be adfree et to use Titanium Backup
Having rooted mine, I received notification OTA of the update yesterday but was unable to install OTA but no trouble updating via kies on the PC, just had to re-root again after the update.
It is ALWAYS worth it to root, lol. Who doesn't want root apps, custom ROMs and kernels, and the ability to remove bloatware??
Usually I will keep my smartphones untouched for several months until I got bored or I hit the limits of the phone.
I decided to root my old Desire because I was short of memory all the time, this can be solved only by having A2Sd+, EXT2SD, etc. ROMs which needs rooting for flashing.
I hit the limit for my Desire only after several weeks...so...I rooted it only after a few weeks. (I am still keeping this device )
I rooted my Sensation after 3 months...just got bored with the stock one...
(This baby is sold after 7 months (unrooted before selling)...I dunno, I do not like this device without any special reason...)
I dunno if I want to root my SGSIII at the moment...perhaps after several months..
I am currently still enjoying my stock SGSIII Hey! It is only a couple of days since I received this device
I managed to wait an entire 24 hours before rooting my S3. I felt that this demonstrated tremendous will power and self control.
Sent from my GT-I9300 using Tapatalk 2
I rooted to get rid of Samsung bloatware and to be able to use cwm. Really easy using the Toolkit (listed in the Dev section), and I was mighty pleased that Samsung chose to ship the phone with an unlocked bootloader.
aaa said:
Usually I will keep my smartphones untouched for several months until I got bored or I hit the limits of the phone.
I decided to root my old Desire because I was short of memory all the time, this can be solved only by having A2Sd+, EXT2SD, etc. ROMs which needs rooting for flashing.
I hit the limit for my Desire only after several weeks...so...I rooted it only after a few weeks. (I am still keeping this device )
Click to expand...
Click to collapse
I was exactly the same with my desire
As for whether to root or not i know everybody says it but it really is just a case of looking at why you would want to root vs the risks. I personally am waiting for a bit because I haven't seen a custom ROM i like enough or another reason to root (battery fix or Google wallet working for example)
However that being said rooting is always worth it because of all the extra apps and capabilities! And as far as I'm aware getting back to stock if it becomes faulty is as simple as flashing some stock firmware through Odin and using chainfires tiangleaway (someone correct me of i'm wrong please because not absolutely 100% on this)
Related
I just ordered my Sprint Hero online and it should be here by Monday. I have read all the Tutorials on how to root and how to Flash the custom ROMs. But I have two questions which I may have missed in all that reading.
1) Is there a possibility where further down the road an official update will not allow anyone to root their phone?
2) Can I root and do a nandroid backup. And not install any ROM for a while?
My goal is to play with the Stock Sprint Hero for atleast a month or so before I feel the need to try Custom ROMs.
- DroidD
Answers below!
1) If you update via an RUU, there is always a chance that HTC will replace the SPL with something that is uncrackable (or at least currently uncrackable). This occurred with later RUUs, and this is why the Goldcard method is often needed in order to root the phone.
When I had my G1 and received push updates, you needed to effectively "switch off" the auto-update routines to avoid getting a stock update that could prevent rooting further down the line. Since Sprint seem to push OTA updates out to CDMA Hero's so it is always possible that this could cause an issue for rooted ROMs, but I'd have though most custom ROMs would've switched off OTA updates anyway.
2) Yes
Regards,
Dave
Thanks Dave.
Dave,
I rooted my Sprint Hero, not necessarily for speed, more so I dont have to look at those horrible apps that Sprint doesnt want to let anyone remove.
I successfully rooted, nandroid backed up and removed the Sprint ware and installed THIS OPTIMIZER FILE (love the lockscreen) but have not decided whether I'm going to take the plunge into custom ROM world. I am actually impressed with how this phone runs (for now) and dont yet need to free up internal drive space.
My question is this: Essentially having the stock rom, is the fact my phone is rooted likely to cause a problem with future Sprint updates?
If so, can you unroot and leave the Sprint-crap out or do you have to go back to 100% absolute stock?
Thanks
Hi all!
So after alot of thinking i've finally decided to take the plunge and upgrade my phone to an android phone. Im liking the atrix and i really wanna go for it, i just got a couple of questions.
The one im planning on getting in unlocked, and rooted, though i can have him unroot it for me. Now my current phone is my 4 year old nokia 5530, running a custom rom i flashed a while back, so i know abit about flashing. Now rooting, this is the 1st time i've heard off it.
Im new to all this, and I get the advantages, but really at the moment all i really need from it is the ability to install non-market apps, but from what i've gathered so far, it seems i cant update OTA to ICS (when its released) without bricking my phone if its rooted?
Isnt there any way to be able to install non-market apps without rooting? Or rather a way to have it rooted and still be able to update when the official ics release is out?
Cheers for the help guys
Oh and btw its running the official 2.3.4 GB
You have a few options, but what you choose is all really up to you.
First, I recall there being a way to sideload (run non-market applications) in Froyo via a script on the computer, but it required being at the computer every time you wanted to load one. But since it's running the official Gingerbread update, you should just be able to change an option to sideload, no hacks and no rooting required.
If you're still interested in rooting, there's a simple root method that could likely be undone, if the device is still new enough to be under warranty. See this thread. http://forum.xda-developers.com/showthread.php?t=1255548
And finally, if you want to unlock your bootloader and try your hand at custom ROMs (and lose much hope of any carrier/manufacturer support), go here: http://forum.xda-developers.com/sho... have a simple way to use it via other means.
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
TheKog said:
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
Click to expand...
Click to collapse
I do believe it's because of the latest OTA update. I know the OTA for Verizon patched our bootloader hack that we previously had and I think the same may have happened for AT&T. You might want to check through the AT&T forums section as you have an AT&T S4 and this is the Verizon section. Hope you find what your looking for!
TheKog said:
Any advice is much appreciated.
Click to expand...
Click to collapse
I'd begin with posting in the forum applicable to your device. That being said, in about sure at&t's update was on par with ours
Sent from my Nexus 7 using Tapatalk HD
Just wanted to see if everyone is diving in and rooting their devices or not. As of right now, I'm still running stock. Haven't found much of a reason to root but would be to nice to have wifi tether and adblock. With one click root, I'm so tempted but still holding off in case any updates. So, have you gone ahead and rooted your new G3 yet?
I rooted mine specifically to disable updates. I'm not so much afraid of root exploits getting patched as I am any potential bootloader exploits being patched. I came from the galaxy s3, which got a bootloader update mid way through that was never cracked, so I'm little worried about that if I wait to long I can never unlock the bootloader. So far I've installed titanium backup, root explorer, and the kit kat sd card fix (no need for hotspot hack since I don't have unlimited data). I'm holding off on anything too major until the bootloader is unlocked and I can do a nandroid first.
I rooted the day I got my g3. I rooted and installed custom roms on my g2 and can't wait to do the same on my g3
Sent from my LG G3
I actually got a demo model from VZW, rooted that one, just to see how hard it was going to be, When I got my permanent one a few days later I rooted it out of the box, before installing anything else.
rooted and uninstalled what I could installed xposed tweaked to my liking and waiting for bootloader recovery and roms
Sent from my VS985 4G using Tapatalk
I rooted mine before I even set it up.
Had my G3 a couple of days before I rooted it. It was so simple to do. one of the 1st things I did was get it setup as a hotspot.
As with most of my phones, my G3 was rooted as soon as the battery was charged, and usually before being activated. Now if we could just get a bootloader unlock. :fingers-crossed:
bkhorn said:
Had my G3 a couple of days before I rooted it. It was so simple to do. one of the 1st things I did was get it setup as a hotspot.
Click to expand...
Click to collapse
which method are you using for the hotspot? That's a main reason I'd want to root but I believe the method in the dev. section, based on reading peoples comments, it's still not that reliable and requires extra steps to get it working.
I want to root just don't want to screw up my brand new phone. I've always rooted my phones but past couple phones I didn't cause they were locked down so I'm weary to jump back into it lol Everyone using stump root? Seems pretty straightforward with that method for us Verizon guys.
tu3218 said:
Just wanted to see if everyone is diving in and rooting their devices or not. As of right now, I'm still running stock. Haven't found much of a reason to root but would be to nice to have wifi tether and adblock. With one click root, I'm so tempted but still holding off in case any updates. So, have you gone ahead and rooted your new G3 yet?
Click to expand...
Click to collapse
You honestly asked that on XDA???
The question is not "who rooted", but who didn't root?
Me?
1. Out of the box.
2. Activated enough with no SIM to get to ADB
3. Root.
4. Turn off and remove bloat (includes de-activating OTA).
5. Now activate normally and use phone.
My phones go from box to root in under 5 minutes.
tu3218 said:
which method are you using for the hotspot? That's a main reason I'd want to root but I believe the method in the dev. section, based on reading peoples comments, it's still not that reliable and requires extra steps to get it working.
I want to root just don't want to screw up my brand new phone. I've always rooted my phones but past couple phones I didn't cause they were locked down so I'm weary to jump back into it lol Everyone using stump root? Seems pretty straightforward with that method for us Verizon guys.
Click to expand...
Click to collapse
I went off of this: http://forum.xda-developers.com/verizon-lg-g3/development/mod-verizon-g3-hotspotmod-g2-apk-t2852152 but with a twist after I read the directions. I used Root Explorer to change the names and copy files. Post #15 helped me a lot.
1, download HotspotProvisionVsG3Mod.apk from 1st post and rename to HotspotProvision.apk
2, search for HotspotProvision.apk and HotspotProvision.odex in /system/app. I added .bak to both of them.
3, now copy HotspotProvision.apk that you remaned to /system/app. Change permission's to rw-r-r-
4, reboot
5, JOY
tech_head said:
You honestly asked that on XDA???
The question is not "who rooted", but who didn't root?
Me?
1. Out of the box.
2. Activated enough with no SIM to get to ADB
3. Root.
4. Turn off and remove bloat (includes de-activating OTA).
5. Now activate normally and use phone.
My phones go from box to root in under 5 minutes.
Click to expand...
Click to collapse
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
bkhorn said:
I went off of this: http://forum.xda-developers.com/verizon-lg-g3/development/mod-verizon-g3-hotspotmod-g2-apk-t2852152 but with a twist after I read the directions. I used Root Explorer to change the names and copy files. Post #15 helped me a lot.
1, download HotspotProvisionVsG3Mod.apk from 1st post and rename to HotspotProvision.apk
2, search for HotspotProvision.apk and HotspotProvision.odex in /system/app. I added .bak to both of them.
3, now copy HotspotProvision.apk that you remaned to /system/app. Change permission's to rw-r-r-
4, reboot
5, JOY
Click to expand...
Click to collapse
Great thanks! If I root, I'll be sure to follow your instructions.
tu3218 said:
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
Great thanks! If I root, I'll be sure to follow your instructions.
Click to expand...
Click to collapse
I used "ioroot". Stump root did not exist when I got my phone.
tu3218 said:
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
Great thanks! If I root, I'll be sure to follow your instructions.
Click to expand...
Click to collapse
I also used IORoot and it's very easy, Stump wasn't out when I rooted mine but from what I've read Stump is super easy and reliable.
I walked out of Best But, phone activated and Battery at like 70% and hopped on my laptop which I had with me and rooted the phone right there in the parking lot so that I could freeze System Updates right away.
Although Verizon is so slow with OTA updates anyways I really could have waited lol
Root that thing then remove all the Verizon junk and use Greenify... You'll be even more happy with how your G3 runs after doing that and it's quite easy to do.
- Tapatalked from the G3
nrage23 said:
I rooted mine before I even set it up.
Click to expand...
Click to collapse
yup me too
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
tu3218 said:
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
Click to expand...
Click to collapse
The flip side of that is the first update could lock out all root methods and any potential bootloader exploits. There are a lot of smart people on this board, so I'd wager someone will find a safe way to update if no bootloader unlock is discovered by the time it's released.
tu3218 said:
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
Click to expand...
Click to collapse
You could always flash back to stock.
http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488
bobcat987 said:
The flip side of that is the first update could lock out all root methods and any potential bootloader exploits. There are a lot of smart people on this board, so I'd wager someone will find a safe way to update if no bootloader unlock is discovered by the time it's released.
Click to expand...
Click to collapse
Yeah I've seen some remarkable things done my fellow members.
spotmark said:
You could always flash back to stock.
http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488
Click to expand...
Click to collapse
Very true. Thanks for that link. I'm just afraid of my screwing up my brand new toy haha Not sure why though, it seems stump root is really straight foward. I just know once I do it, I'll start messing with xposed a lot. I know when I had my S3, I was flashing roms like once a day. My gf thought I was crazy.
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Nope, by taking the latest OTA (or in this case Kies) you've locked yourself into the latest version, for which there is currently no Root
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
52brandon said:
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
Click to expand...
Click to collapse
Nope. Locked Bootloader sucks.
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Charlie115 said:
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Click to expand...
Click to collapse
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
52brandon said:
I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed.
Click to expand...
Click to collapse
If you're ever in this situation again, give up on retaining your current root, flash back to true stock (with a re-partition .pit file as well), and re-root. If you had flashed the nc5 full-wipe with the .pit file and just restored root from a clean system, you would have been fine.
52brandon said:
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
Click to expand...
Click to collapse
Well, you should have known better than to use kies...
Sent from my SCH-I545 using XDA Free mobile app
Honestly I don't even think that devlopers will make much effort to even find out how to root this version as its says that this is one of two updates before getting lollypop.
Development Forums are for developers to share their work and post their Roms and Mods.
Questions belong in the Q&A section.
Thread has been moved to correct section, please pay attention to XDA rules.
Root
52brandon said:
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Click to expand...
Click to collapse
KingRoot 4.1 rooted my galaxy s4 on oc1....and try flashing an nc5 tar in flashfire
You cannot flash anything with flashfire. If you flash that tar, you WILL brick.
Question
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Epiphany^ said:
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Click to expand...
Click to collapse
You can't downgrade from OC1.
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
kingroot does work
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Munk3ybones said:
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Click to expand...
Click to collapse
You have root. But you have a much lower chance of getting an unlocked Bootloader than anyone on NC5/NK1/NK4. They have root, module loading, and a potential for kexec to run custom kernels.
Don't upgrade to OC1 via OTA if you haven't already everyone! Use Muniz_ri's keeproot upgrade method!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 12:53 AM ---------- Previous post was at 12:53 AM ----------
bigg6987 said:
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
Click to expand...
Click to collapse
Even then you're stuck. Rollback has little to do with the BL. Rollback is set at a much lower level (physically).
Sent from my Nexus 6 using Tapatalk