Related
I rooted my phone to prevent KitKat from installing, because I didn't want to lose access to FoxFi. I forze the SDM file so it wouldnt look for updates. Today FoxFi has fixed the problem, so I no longer fell the need to be rooted, and I would very much like a taste of that KitKat. If I understand correctly I should not unfreeze the the SDM file and take the OTA update, because it could "brick my phone". Is that the case?
Do I need to unroot first, and is there a thread without a hundred pages that explains how to unroot. I am on Build VRUEMK2.
Thoughts?
Under the settings in the Superuser app is an option to "Full Unroot" Will this really work for unrooting the device, or do i need to do the odin thing i keep reading about? Why would odin even be necessary if this is an option. It seems to easy.
You will need to return your phone to stock, root will prevent the OTA. You can try to unfreeze SDM and take the update, it won't brick your phone, it will just fail to install because root will cause it to fail.
There are threads about using Odin and no-wipe MK2 or MJ7 files to return your phone to stock without losing data. That is the best way to roll your phone back to take the update. Alternatively, you could just do a factory reset from the stock recovery, but you'll lose all your data on the phone. Otherwise, you can just update using the Odin tars that are available now, but since it seems like you don't want to do the research on how to do that, you'd probably better not try.
Paramemetic said:
There are threads about using Odin and no-wipe MK2 or MJ7 files to return your phone to stock without losing data. That is the best way to roll your phone back to take the update. Alternatively, you could just do a factory reset from the stock recovery, but you'll lose all your data on the phone. Otherwise, you can just update using the Odin tars that are available now, but since it seems like you don't want to do the research on how to do that, you'd probably better not try.
Click to expand...
Click to collapse
Thanks,
So you do not recommend or know about the "Full Unroot" option in the Superuser settings.
I do not mid a factory reset, as this is phone is only a month old. If it is that easy, I will probably go that route.
I am currently downloading a file called VRUAMDK_NoWipe.tar.zip which I understand to be a stock image of my android before i rooted that is supposed to take me back to pre-root. But if factory resetting will accomplish the same goal, then that seems like an easier way to go.
I do like the openness of being rooted, but My concern about updating with the root, is that some functions may not work like they are supposed to. I haven't been involved in rooting since the days of playing with my HTC Eris, and Droid X. Maybe things a re different today, but most roms I played with were found to have issues with thinks not functioning correctly. Do the 4.4 "tars" that you are referring to have all the functions?
I'd sit tight and see what comes from the latest tar files of NC5. Maybe nothing, but can't hurt to wait.
Sent from my SCH-I545 using XDA Free mobile app
Rageboardr said:
Thanks,
So you do not recommend or know about the "Full Unroot" option in the Superuser settings.
I do not mid a factory reset, as this is phone is only a month old. If it is that easy, I will probably go that route.
I am currently downloading a file called VRUAMDK_NoWipe.tar.zip which I understand to be a stock image of my android before i rooted that is supposed to take me back to pre-root. But if factory resetting will accomplish the same goal, then that seems like an easier way to go.
I do like the openness of being rooted, but My concern about updating with the root, is that some functions may not work like they are supposed to. I haven't been involved in rooting since the days of playing with my HTC Eris, and Droid X. Maybe things a re different today, but most roms I played with were found to have issues with thinks not functioning correctly. Do the 4.4 "tars" that you are referring to have all the functions?
Click to expand...
Click to collapse
The no wipe image you are downloading is probably not the correct version for your phone unless you are still on the MDK firmware.
Sent from my SCH-I545 using Tapatalk
jmgib said:
The no wipe image you are downloading is probably not the correct version for your phone unless you are still on the MDK firmware.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Bummer, I was wondering about that after i started looking at different image names. I started seeing the common theme, and no I am not on MDK, I am on MK2. Bummer because that file took along time to download here at work.
kude87 said:
I'd sit tight and see what comes from the latest tar files of NC5. Maybe nothing, but can't hurt to wait.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
What is the difference between a tar file, and ROMing. Are TAR files more reliable?
I am in no real hurry, but as this is my daily phone, I need everything to work correctly, and no reason to wait if its like ROMs, and there seem to always be things that are quirky in a ROM.
Rageboardr said:
What is the difference between a tar file, and ROMing. Are TAR files more reliable?
I am in no real hurry, but as this is my daily phone, I need everything to work correctly, and no reason to wait if its like ROMs, and there seem to always be things that are quirky in a ROM.
Click to expand...
Click to collapse
If it is your daily and you aren't in any hurry, I strongly suggest waiting it out. Read some forums and get a better feel about rooting and romming.
A tar file is flashed through Odin, and depending which one you download, could lock your bootloader (I forget which firmware you're on). I'd personally wait for/if NC5 is rooted and proceed then.
"Romming" is a broad term used to define flashing custom roms. Predominantly, this means you have an unlocked bootloader and are flashing zip files through a custom recovery.
Sent from my SCH-I545 using XDA Free mobile app
Rageboardr said:
I rooted my phone to prevent KitKat from installing, because I didn't want to lose access to FoxFi. I forze the SDM file so it wouldnt look for updates. Today FoxFi has fixed the problem, so I no longer fell the need to be rooted, and I would very much like a taste of that KitKat. If I understand correctly I should not unfreeze the the SDM file and take the OTA update, because it could "brick my phone". Is that the case?
Do I need to unroot first, and is there a thread without a hundred pages that explains how to unroot. I am on Build VRUEMK2.
Thoughts?
Click to expand...
Click to collapse
Hi I had the same issue. mk2, rooted, wanted to take the ota update and didn't mind losing root.
You won't brick trying to take the update it will just fail with error 402. I wrote out my steps below to guide you thru the process I used and were successful for me.
1. Unroot using SuperSU.
2. Use Kies to update/restore firmware on your PC.
3. Once rebooted search for system update.
4. Download and install the update. I did the whole process using only data no WiFi (not sure if it makes a difference but that's what I did).
5. Once your phone reboots you will be greeted by a lovely red Verizon splash screen.
Hope this helps you and others!
Sent from my Hp Touchpad Android 4.4.2 using Tapatalk Pro
Hey everyone, I have a question...so I rooted my phone a couple of months ago and never got around to installing a custom rom. So as of right now I have the stock 4.3 (sch-i545), I never done anything besides rooting it. I just received an update for the stock rom and my question is, could I just update it while my phone is rooted without voiding the warranty and or bricking it? Much obliged for your time
http://forum.xda-developers.com/showthread.php?t=2726868
Sent from my SCH-I545 using XDA Premium 4 mobile app
If all you did was rooted, and didn't delete any apps, make any changes to files, etc., it should work. It won't brick your phone if it doesn't work, it will just reboot and tell you it failed.
Sir_Eagle said:
If all you did was rooted, and didn't delete any apps, make any changes to files, etc., it should work. It won't brick your phone if it doesn't work, it will just reboot and tell you it failed.
Click to expand...
Click to collapse
My understanding was that you need to be absolute stock to take an OTA. Have you seen anyone say they've been able to OTA a rooted phone?
Sent from my SCH-I545 using XDA Premium 4 mobile app
joshm.1219 said:
My understanding was that you need to be absolute stock to take an OTA. Have you seen anyone say they've been able to OTA a rooted phone?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can't say for sure if I have. Never heard of anyone that rooted and didn't make any kind of change either.
Sir_Eagle said:
Can't say for sure if I have. Never heard of anyone that rooted and didn't make any kind of change either.
Click to expand...
Click to collapse
If all you did was root the phone, you will be able to OTA... BUT,
This OTA update will install NC5 on your phone and add the lovely Knox warranty void as well.
As far as I can tell, at this time, therd is NO way of rooting the Verizon S4 after updating to NC5.
If you look under "About Phone, Status.. Device Status, if it says OFFICIAL, you'll be good to go for OTA.
But remember... no Rooting under the new OTA with verizon, until one of the XDA Genius finds a solution for us zombies.
Pow35 said:
If all you did was root the phone, you will be able to OTA... BUT,
This OTA update will install NC5 on your phone and add the lovely Knox warranty void as well.
As far as I can tell, at this time, therd is NO way of rooting the Verizon S4 after updating to NC5.
If you look under "About Phone, Status.. Device Status, if it says OFFICIAL, you'll be good to go for OTA.
But remember... no Rooting under the new OTA with verizon, until one of the XDA Genius finds a solution for us zombies.
Click to expand...
Click to collapse
I tried to OTA on rooted phone and it failed.
Don't like to do a factory reset, so I basically only want an OTA update. Cant stick anymore as my phone is driving me nuts, my phone screen keeps on going black and locking every few seconds when I wake the screen from sleep
ch.ch1 said:
I tried to OTA on rooted phone and it failed.
Don't like to do a factory reset, so I basically only want an OTA update. Cant stick anymore as my phone is driving me nuts, my phone screen keeps on going black and locking every few seconds when I wake the screen from sleep
Click to expand...
Click to collapse
Go here:
http://forum.xda-developers.com/showthread.php?t=2578209
You can go to MK2; the latest version of Jellybean.
You can then either root and stay there.
You can root, install safestrap then go to a rooted KitKat (NC5) and keep the MK2 bootloader.
You can ignore all rooting and mods and take the OTA and go to a crippled NC5 with no root.
Hope that helps.
yupp
joshm.1219 said:
My understanding was that you need to be absolute stock to take an OTA. Have you seen anyone say they've been able to OTA a rooted phone?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I used the OTA update and my phone was rooted. Also every time I turn(ed) on my phone it says samsung custom with an unlock this is on 4.4.2 and on 4.3 before. I checked to see if I have root, but I don't. Also superuser is still installed, says I don't have root (obviously). Except the weird thing is, that it says samsung custom still, and on the isis mobile wallet it says I cant use it because my device is rooted. I also used root checker to see if I was to double check and it says I'm not. I'm really confused... but hey at least the OTA update worked, i just cant wait to get root again because I will miss all my rooted apps. I didn't check to make sure they developed root either. which sucks but whatever.
After two and a half hours of frustration, I eventually gave up.
I downgraded from NG6 to NC5, and then from NC5 to both NC2 and MK2 (separately) after MUCH Googling and forum searching.
For the longest time I couldn't get anything to work, until I realized that my USB extension cable was the cause of my problems. I finally got down to NC5 rooted. I tried to install Liquid Smooth and Cyanogenmod through Odin, and it wouldn't work. I got Liquid Smooth to install through Safestrap, but it just got stuck at the loading image forever.
I eventually got frustrated and let the Samsung software put NG6 back on, and left it alone. That's where I'm at now.
I assure you I've read absolutely every thing ever written on every subject by every person ever born in the history of mankind while trying to figure this out. Can someone PLEASE give me a walkthrough SUMMARY of how to get custom ROMs on this phone, beginning with NG6? I'm not a newbie. I've rooted and installed custom ROMs on numerous phones and tablets. But I can't keep playing with this phone, trying to get it to work. I'm going to end up becoming a serial killer if I get one more error message. I am now desperate, and asking for help.
Serial killer might be in your future. Unless you are MDK, safestrap is what you are limited to and it has only a few ROMs it can function with. Cyanogenmod is not supported with safestrap, AOSP/AOKP and such can soft-brick the phone.
Sent from my SCH-I545 using XDA Free mobile app
sponix2ipfw said:
Serial killer might be in your future. Unless you are MDK, safestrap is what you are limited to and it has only a few ROMs it can function with. Cyanogenmod is not supported with safestrap, AOSP/AOKP and such can soft-brick the phone.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
"Serial killer might be in your future" lololololol.
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
zQueal said:
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
Click to expand...
Click to collapse
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
scrillakev said:
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
Click to expand...
Click to collapse
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
zQueal said:
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
Click to expand...
Click to collapse
I never used SafeStrap so I doubt I will be much help. But once you rebooted your stock ROM is no longer there? Might have to just flash a stock image via ODIN and try again. Verizon isn't going to help you either with modding your phone, XDA is the place to be.
Has there been anything new since this thread was posted or is it impossible still?
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Sorry buddy you're SOL
Sent from my SCH-I545 using XDA Free mobile app
If you are rooted use a terminal editor app and type:
getprop ro.bootloader
If it says anything other than I545VRUAMDK your only choice is SafeStrap.
That means if you bought an S4 and it came with MK1, NC5, NK1, or anything other than MDK you cannot flash a custom recovery. The same applies if you took an OTA from VZW. This has been stated 1000's of times here.
Hint:
Look on the box that your S4 came in and read the last three characters where it says what build the phone has.
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
safestrap version
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.[/QUOTE]
***Make sure you are using the correct version of safestrap for your current baseband
another good app from the google play store to download is samsung info
I have used safestrap in the past as I was in the same scenario as you. I currently now have a MDK phone
Illogi.xbone said:
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
Click to expand...
Click to collapse
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
mcbeat257 said:
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
Click to expand...
Click to collapse
The exploit was weeded out after MDK
Sent from my SCH-I545 using XDA Free mobile app
The bootloader was never "unlocked" on MDK, there was just an exploit available that allowed the installation of a custom recovery. That exploit was closed in the first update from MDK and a new one has not been discovered. The bootloader itself has some pretty strong encryption so it may never be unlocked.
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