I recently got a new S4 at the store, and of course, it came with MF3.
My question is, if I choose to root it, which I would really like to, would this potentially block my ability to utilize a future exploit in the bootloader or otherwise negatively impact the phone?
I know I can't un-root the phone for the time being, which is fine, but I would like to root it if there won't be any future issues.
Why would you think there would be issues with a future bootloader exploit?
Root has nothing to do with the bootloaders. If there were ever to be issues, it would be addressed and fixed before it goes public.
Sent from my SAMSUNG-SGH-I337 using xda premium
just remember that if you root, and your device takes a poop, you wont have odin as option to fix it nor will you have a backup to restore it since you wont have a custom recovery. dont root if you dont think you'd know how to get it back up and going again. read up. cheers.
graydiggy said:
Why would you think there would be issues with a future bootloader exploit?
Root has nothing to do with the bootloaders. If there were ever to be issues, it would be addressed and fixed before it goes public.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Yeah, as you can see I'm not very knowledgeable about the way the phones work and how these exploits deal with the phone software. But I appreciate the info that rooting won't mess with that kind of thing.
xBeerdroiDx said:
just remember that if you root, and your device takes a poop, you wont have odin as option to fix it nor will you have a backup to restore it since you wont have a custom recovery. dont root if you dont think you'd know how to get it back up and going again. read up. cheers.
Click to expand...
Click to collapse
I guess I'm wondering what could cause my device to take a poop if I simply root it and install Titanium Backup and some other root apps. Yeah, I've been trying to read up ever since I became a member a couple days ago.
I appreciate the advice, guys. Thanks!
there's a hundred threads spread out over the last couple weeks of people asking what they can do to fix their devices. people that were on MF3, rooted, and suddenly there was a glitch somewhere. whether they deleted something they shouldnt have, installed something they shouldnt have, some random misc unforeseen error, etc.
if i were a user that had a very introductory-level of android knowledge, it would be a no brainer for me: having no root on my device vs having no way to backup/restore via a custom recovery and no odin. i choose stock/unrooted. just keep your eyes peeled. when there is finally an exploit, you'll see it here on xda.
Related
is this happening to everyone? Wasn't going to install or even acknowledge that there was an update, because of the boot loader. But i plug it into a charger and 5 minutes later, it is like the phone is giving me the middle finger and accepting the update on it's own, without any question on if i want to or not.
My phone feels violated.
:thumbup:
Sent from my Transformer Prime TF201 using xda app-developers app
Same thing happened to me. O well not ready just yet to brick my s4 lol
Sent from my SAMSUNG-SGH-I337 using xda premium
tried everything i could to stop it, even removed battery as it started the update. was hoping for a brick, don't know why. lol, also not to worried about bricking mine, i am fairly confident in my ability to read, unless the thread is in some language other than english, but then again, now i got s translate!
Sent from my Transformer Prime TF201 using xda app-developers app
You would of had to freeze the ota update apps before hand not to be forced to get it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Could you please let me know which services to freez with TB on At&t S4 as to avoid forced updates, is it At&T Software Update V 42_1_1303_5_1?
Alos please excuse my noobiness, this is my first android and coming from apple jailbreaks, I of coarse was not happy with closed phone policy so i was researching root options (which i know very little about since its my first android platform). Anyways long story short I rooted using motochopper exploit and got superuser. My questions are:
1. Is motochopper a real root or just tricks the phone into thinking its root?
2. Read about a bootloader hack soon to be released...what exactly is that and what will it give us? also what would be the difference between the motochopper "root" i have on my S4 now and the bootloader hack to be released?
3. Got Ram Manager but was unable to create backup recovery since clockwork mod is not yet released for S4, is that true or is there other ways to use Rom manager?
4. And the last but not least, what should a noob user like myself do, or how can we avoid bricking our phones now that we rooted (with motochopper) or will use the boot-loader hack?
5. is Samsung.Cloud Data Relay 2.1.4 responsible in anyways for forced updates?
Please if you can answer any or all questions I would be so grateful, as im sure many other noobs like myself would be. Please don't think I don't research the subject, its just when you are new to something, you always want to be sure. I am sure logic is to be used and common sense also as to not mess with software service or delete stuff you don't know as to avoid bricking but is there something else to watch out for?
Thnks a million guys
Stokem
unlocking the bootloader will allow us to flash an alternate recovery such as clockwork or twrp and then flash a rom. best bet to avoid a brick is to read everything you can about what you want to do. make sure you read any instructions several times before doing anything to make sure you understand.
sent from my black at&t sgs4
p1gp3n said:
unlocking the bootloader will allow us to flash an alternate recovery such as clockwork or twrp and then flash a rom. best bet to avoid a brick is to read everything you can about what you want to do. make sure you read any instructions several times before doing anything to make sure you understand.
sent from my black at&t sgs4
Click to expand...
Click to collapse
thank you, will there be some custom roms developed for S4 once the bootloader is unlocked or is there some good once already?
also, i read that since AtT can force updates it might patch the bootloader unlock in the future, which processes do we have to freeze in order to avoid it on Att S4. I couldn't find any SDM processes as explained for other S4 carriers. Is it At&T Software Update V 42_1_1303_5_1, do you know by any chance?
I would imagine that roms will be developed & released, but can not say they definitely will.
sent from my black at&t sgs4
Once the bootloader is unlocked Roms will come fast and furious.
To avoid future updates freeze in TB:
AT&T software update
FWUpgrade
LocalFOTA
thank you for your replies. much appreciated
I noticed the new OTA updated on my phone today and decided not to install it. Once I got home, I plugged my phone into my computer to charge it and it installed the OTA update without even asking. So with that being said, what do I have to do now to get back to where I was which was stock with root access?
I did a backup this morning with Titanium, could I do a factory reset and restore with Titanium?
Nick James said:
I noticed the new OTA updated on my phone today and decided not to install it. Once I got home, I plugged my phone into my computer to charge it and it installed the OTA update without even asking. So with that being said, what do I have to do now to get back to where I was which was stock with root access?
I did a backup this morning with Titanium, could I do a factory reset and restore with Titanium?
Click to expand...
Click to collapse
I believe you are stuck like me! I was using a jailbroken iphone which would block any update from apple and I got used to that. I forgot to freeze the updater and it automatically updated my brand new s4 that I had just rooted and tweaked to my liking just a few days ago :crying::crying::crying:
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
You guys are on hold right now.
I don't understand how you guys are getting OTA updates with a rotted phone. When mine was rooted, it said updating was disabled because my device was modified.
scream_clarity said:
I don't understand how you guys are getting OTA updates with a rotted phone. When mine was rooted, it said updating was disabled because my device was modified.
Click to expand...
Click to collapse
some are seeing, even if they are rooted, it will say official and do the update, lose root after, but it has been seen.
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
Avoid all updates by flashing custom roms. You can always go back to factory stock, unrooted and untouched. But this way, you can see what updates do what, and then decide.
The Ax says, just a helpful tip.
I tried to avoid the update but lost the battle when I plugged my phone in to charge and walked away! I should have froze those services listed in another thread. I had no idea. Its only time... Hopefully
Sent from my SAMSUNG-SGH-I337 using xda premium
I don't mean to make matters worse for you, but stories like these are really depressing. I sincerely hope that some of our advanced Devs will find a solution for MF3 root soon.
And now for the potentially helpful part: AT&T typically has a 14 "buyers remorse" policy. They'll take back the handset (so long as it is in perfect condition) for ANY reason and exchange it for another (or same one, as far as I know). Two caveats:
You will likely be forced to pay a $35 re-stocking fee. Might be worth it for root/ROMs though!
You can only do this once per purchase.
Otherwise, you'll need to wait until a solid root is found for MF3. Even still, keep in mind that your "aboot" has been patched, and now Loki will not work for you (it means no custom roms/kernels, and no custom recovery). This might be permanent, as the bootloaders are locked-down TIGHT. The Loki exploit was just a workaround, but even it is gone in MF3.
I just posted this in another thread, so here you go again:
For future reference, or for someone else, you could have avoided this easily!
1) When it tries to update, don't hit "remind me later"! You can only do that so many times before it forces the update automatically. INSTEAD, you can just hit the home button and force your way out, not making any decision. You can do this indefinitely...but it's annoying so you should just 2) Get Titanium Backup and freeze the OTA update apps so they don't bother you! It's right at the top of the sticky beginner's info aka noob helper thread:
http://forum.xda-developers.com/showthread.php?t=2301762
You probably already knew this but maybe it will help someone else who's not prepared to avoid this OTA!
jeffreii said:
I just posted this in another thread, so here you go again:
For future reference, or for someone else, you could have avoided this easily!
1) When it tries to update, don't hit "remind me later"! You can only do that so many times before it forces the update automatically. INSTEAD, you can just hit the home button and force your way out, not making any decision. You can do this indefinitely...but it's annoying so you should just 2) Get Titanium Backup and freeze the OTA update apps so they don't bother you! It's right at the top of the sticky beginner's info aka noob helper thread:
http://forum.xda-developers.com/showthread.php?t=2301762
You probably already knew this but maybe it will help someone else who's not prepared to avoid this OTA!
Click to expand...
Click to collapse
I did that exactly. I just ignored it. I have no idea what triggered my phone to do the update. I checked just now and even when I plug my phone in, Kies doesn't even open. I'm not sure what I did... Its really annoying though.
I'll keep my fingers crossed.
I'm hearing sim unlock will not work now? Is that true?
Sent from my SAMSUNG-SGH-I337 using xda premium
xamadeix said:
I'm hearing sim unlock will not work now? Is that true?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I'm not sure but if I had to guess I would think not.
I rooted my device a few weeks ago, and 4.3 released earlier, so I completely uninstalled root, through my superuser app. 4.3 downloads, and when it came time to install, it went through the install process in about five seconds, and booted up normally. I have an unlocked bootloader, I need help changing it back to normal? Is there a way?
Can we at XDA know what phone model you have and if your
MDL or MF3
Sent from my ATT S4 MF3 using Tapatalk
Please can some one help I'm rooted stock kernal cwm recovery on mdb there is a update that started to download I quick stopped it by shutting off WiFi. How do I no what update this is ? I don't want to mess up by DL mf3 and locking bootloader . but maybe it new update 4.3. What should I do ??
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
jball said:
Can we at XDA know what phone model you have and if your
MDL or MF3
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
MF3.
How do you have an unlocked bootloader. ? and what leads you to believe its unlocked ?
Sent from my SGH-I337 using Xparent Skyblue Tapatalk 2
Oh he thinks it's unlocked because of the icon on the Samsung splash screen. Lol.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Lol if you have mf3 the bootloader is NOT unlocked.
Sent from my SGH-I337 using Tapatalk
ralphie1267 said:
Please can some one help I'm rooted stock kernal cwm recovery on mdb there is a update that started to download I quick stopped it by shutting off WiFi. How do I no what update this is ? I don't want to mess up by DL mf3 and locking bootloader . but maybe it new update 4.3. What should I do ??
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
If you are currently fully rooted and wish to stay that way then you NEVER want to update through your carrier! If you do take the update, your phone will be permanently un-rooted! You should always wait for the developer community to take a look at it and determine what the pit-falls may be and to produce alternatives (update based rooted roms).
And before everyone starts jumping on me for using the word permanently; My feeling is that until proven otherwise, it should always be presumed that the affect will be permanent to emphasize the potential severity of the action. I would be happy to be proven wrong!
We all know he either wants the padlock gone or back to completely stock rite.
Sent from my ATT S4 MF3 using Tapatalk
drichter12 said:
If you are currently fully rooted and wish to stay that way then you NEVER want to update through your carrier! If you do take the update, your phone will be permanently un-rooted! You should always wait for the developer community to take a look at it and determine what the pit-falls may be and to produce alternatives (update based rooted roms).
And before everyone starts jumping on me for using the word permanently; My feeling is that until proven otherwise, it should always be presumed that the affect will be permanent to emphasize the potential severity of the action. I would be happy to be proven wrong!
Click to expand...
Click to collapse
Im afraid your statement has already been proven to be wrong. He said he is MDB and the update he is getting would be to MF3 and there is already a root method for that firmware. Permanent is a strong word, especially given the abilities of the developers on XDA, Temporarily is a much more adequate word to use, which would the case for 4.3 MJ9, TEMPORARILY, there isn't a proven SAFE root method....as of yet.
gj23 said:
Im afraid your statement has already been proven to be wrong. He said he is MDB and the update he is getting would be to MF3 and there is already a root method for that firmware. Permanent is a strong word, especially given the abilities of the developers on XDA, Temporarily is a much more adequate word to use, which would the case for 4.3 MJ9, TEMPORARILY, there isn't a proven SAFE root method....as of yet.
Click to expand...
Click to collapse
I think you missed my point. Yes, there is a a way to root MF3 but not a clean bootloader/recovery replacement. The reason for using the word permanent was to emphasize that there are NO guarantees of root for those who choose to update from the carrier as soon as an update becomes available. I agree that there is a high likelihood that some form of root will be made available but until that method is discovered the user should assume he/she will be stuck with what they have. An excellent example of such is exactly the MF3 release he is talking about. If you receive the MF3 OTA you no longer have an unlocked bootloader available and if you desire running another rom you are stuck with a kludge solution, not a clean one.
drichter12 said:
I think you missed my point. Yes, there is a a way to root MF3 but not a clean bootloader/recovery replacement. The reason for using the word permanent was to emphasize that there are NO guarantees of root for those who choose to update from the carrier as soon as an update becomes available. I agree that there is a high likelihood that some form of root will be made available but until that method is discovered the user should assume he/she will be stuck with what they have. An excellent example of such is exactly the MF3 release he is talking about. If you receive the MF3 OTA you no longer have an unlocked bootloader available and if you desire running another rom you are stuck with a kludge solution, not a clean one.
Click to expand...
Click to collapse
I'm not real sure what you mean by a "kludge solution", but I'm on MF3 with Safestrap and there are quite a few ROMS available to flash and some of them are as good as any I've run before (excluding none). I would be willing to bet that 4.3 will have root and ROMS available in a very short time. Im quite certian that Hashcode will have Safestrapup and running on 4.3 before ya know it and if not, I'm happy with the device and options I have with it as it is now. I do agree that anyone who chooses to take the update right away, and then expect all the development options, are wishful thinking, and/or not doing their research
MDB,MDL,MF3,MJ9
The above list has always been bootloader locked.yes rooted minus the new MJ9 and a "work around" to flashing roms.
I have faith that one day someone will crack the lock,just not before I switch to a Nexus 5
Sent from my ATT S4 MF3 using Tapatalk
Hello everyone,
So, I've been looking into the status of unlocking the bootloader for MF3 updates (I downloaded it and read too late that they locked the bootloader in the update, sneaky bastards) and it appears this issue still hasn't been fixed. From what I understand, Dan Rosenberg waited until the Verizon update was released before he revealed the Loki exploit but, from what I've read, this exploit does not work on the MF3 update.
My question is now what is it that stops this from working with the MF3 version? Wasn't that the initial point of the release was to solve this particular issue?
I'm trying to understand some of the specifics as I've read a number of articles and links (both in XDA as well as others) and I'm still a bit confused as to where we're at with this. From what I can see, it doesn't appear there is any workaround in sight if the Loki exploit doesn't fix it. Am I more than likely stuck with a locked bootloader for the life of this phone?
Realistically, I am still able to get root access, so it's really not the end of the world but I'd definitely like to be able to flash custom roms if I wanted to. It sounds like I can indirectly do that via Safestrap (does it basically just protect all the crucial stuff that can break the fuse on the device and allow you just use TW based roms, just not custom kernals, is that correct?). But as of now, I believe that's my only option, if I understand correctly.
I realize a number of these issues have been addressed probably a number of times but, due to the amount of details and updates that seem to be changing, I just want to make sure I have a good understanding of everything so I know what my options are. If anyone wants to address this, I'd appreciate it but if these have all been answered a million times in one form or another, I understand that as well.
Thanks for your help!
(I put my questions in bold just to draw attention to them so anyone reading it doesn't have to search through my message to find them to address them, I'm not trying to come off like I'm yelling).
jbrookley said:
Hello everyone,
So, I've been looking into the status of unlocking the bootloader for MF3 updates (I downloaded it and read too late that they locked the bootloader in the update, sneaky bastards) and it appears this issue still hasn't been fixed. From what I understand, Dan Rosenberg waited until the Verizon update was released before he revealed the Loki exploit but, from what I've read, this exploit does not work on the MF3 update.
My question is now what is it that stops this from working with the MF3 version? Wasn't that the initial point of the release was to solve this particular issue?
I'm trying to understand some of the specifics as I've read a number of articles and links (both in XDA as well as others) and I'm still a bit confused as to where we're at with this. From what I can see, it doesn't appear there is any workaround in sight if the Loki exploit doesn't fix it. Am I more than likely stuck with a locked bootloader for the life of this phone?
Realistically, I am still able to get root access, so it's really not the end of the world but I'd definitely like to be able to flash custom roms if I wanted to. It sounds like I can indirectly do that via Safestrap (does it basically just protect all the crucial stuff that can break the fuse on the device and allow you just use TW based roms, just not custom kernals, is that correct?). But as of now, I believe that's my only option, if I understand correctly.
I realize a number of these issues have been addressed probably a number of times but, due to the amount of details and updates that seem to be changing, I just want to make sure I have a good understanding of everything so I know what my options are. If anyone wants to address this, I'd appreciate it but if these have all been answered a million times in one form or another, I understand that as well.
Thanks for your help!
(I put my questions in bold just to draw attention to them so anyone reading it doesn't have to search through my message to find them to address them, I'm not trying to come off like I'm yelling).
Click to expand...
Click to collapse
When Samsung released the MF3 update they used a two-prong attack to close the Loki exploit... those being
1. Closing the exploit in the code itself.
2. Blowing a qFuse on the board to prevent us from flashing any firmware lower then MF3.
I don't really want to get into the technical aspects of how this happened... I'll let someone else answer it if they wish.
jbrookley said:
Hello everyone,
what is it that stops this from working with the MF3 version? Wasn't that the initial point of the release was to solve this particular issue?
Am I more than likely stuck with a locked bootloader for the life of this phone?
does it basically just protect all the crucial stuff that can break the fuse on the device and allow you just use TW based roms, just not custom kernals, is that correct?
Click to expand...
Click to collapse
Nighthawk gave the short answer for the first two. Also, it's possible the update mentioned may have been the MDB>MDL update or verizon equivalent.
Technically even MDL people are stuck with a locked bootloader, but they have an exploit. People are working on an exploit for MF3+, but I can't say how likely it is one will be found.
Safestrap lets you do anything a normal recovery can except flash kernels. This is why you can only flash TW ROMs, as the AOSP and TW kernels are not compatible. Kernels would trip the bootloader checks. However, to add a bit to this and the last answer, something called kexec is in progress of being implemented into Safestrap. The exploit found allows loading unsigned modules, which in turn allows loading a kexec module, which would then load a kernel over the stock kernel while in the boot process. So if this works, it would be the next best thing to a bootloader exploit in that it would give us the same result, though I don't know if kernels will require tweaks to load in kexec.
DeadlySin9 said:
Nighthawk gave the short answer for the first two. Also, it's possible the update mentioned may have been the MDB>MDL update or verizon equivalent.
Technically even MDL people are stuck with a locked bootloader, but they have an exploit. People are working on an exploit for MF3+, but I can't say how likely it is one will be found.
Safestrap lets you do anything a normal recovery can except flash kernels. This is why you can only flash TW ROMs, as the AOSP and TW kernels are not compatible. Kernels would trip the bootloader checks. However, to add a bit to this and the last answer, something called kexec is in progress of being implemented into Safestrap. The exploit found allows loading unsigned modules, which in turn allows loading a kexec module, which would then load a kernel over the stock kernel while in the boot process. So if this works, it would be the next best thing to a bootloader exploit in that it would give us the same result, though I don't know if kernels will require tweaks to load in kexec.
Click to expand...
Click to collapse
Thanks for taking the time to explain that!
A somewhat related question, if my S4 ever gets an OTA update for 4.3, should I deny the update in case they create more obstructions for updates or should I take it since that's the only way my phone will get 4.3 at this point?
jbrookley said:
Thanks for taking the time to explain that!
A somewhat related question, if my S4 ever gets an OTA update for 4.3, should I deny the update in case they create more obstructions for updates or should I take it since that's the only way my phone will get 4.3 at this point?
Click to expand...
Click to collapse
I believe the kexec exploit is being worked on for mk2? But I'm not too sure you will have to review the threads.
Sent from my GT-I9505 using xda premium
jbrookley said:
Thanks for taking the time to explain that!
A somewhat related question, if my S4 ever gets an OTA update for 4.3, should I deny the update in case they create more obstructions for updates or should I take it since that's the only way my phone will get 4.3 at this point?
Click to expand...
Click to collapse
[email protected] said:
I believe the kexec exploit is being worked on for mk2? But I'm not too sure you will have to review the threads.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
It is MK2 exclusive since the MK2 root method gives access to kernel memory and allows it. However, once on MK2 you should definitely not take any and I'm not sure whether the security policy updates are safe or not.
I've read in a couple places of people having success taking the the NC4 OTA on their stock rooted device with SU Survival Mode on and being able to keep root after the update.
I was just wondering if any has tried that and if they were successful or not, thanks!
I know some people just want root, but really what other point is there to doing this?? This sounds just like what happened over in the S3 forum when people who wanted 4.3 ota so desperately they ended up getting hard bricks and relocked bootloaders.
Taking the OTA, you are giving up kernel modules on NC2 and the ability to go back to MJE if you need. For anyone that missed it, read this thread about why NC2 is unique. Just flash NC4 baseband (http://forum.xda-developers.com/showpost.php?p=52633373&postcount=391), and stay on NC2 til devs cook up a safe NC4 to use. What Im doing if you ever want to use kexec in the future for aosp roms when it comes
I successfully did this.
I had to Odin back to stock 4.3 because OTA would fail, but once that finished and re-rooted with Kingo I took the update in survival mode retaining root.
I'm one of those just wanting root.
Sent from my SM-N900V using XDA Premium 4 mobile app
NeoMagus said:
I know some people just want root, but really what other point is there to doing this?? This sounds just like what happened over in the S3 forum when people who wanted 4.3 ota so desperately they ended up getting hard bricks and relocked bootloaders.
Taking the OTA, you are giving up kernel modules on NC2 and the ability to go back to MJE if you need. Just flash NC4 baseband, and stay on NC2 til devs cook up a safe NC4 to use. What Im doing if you ever want to use kexec in the future for aosp roms when it comes
Click to expand...
Click to collapse
Well, I'm one of the people that only care about simple root access, so that's why I'm curious.
NeoMagus said:
I know some people just want root, but really what other point is there to doing this?? This sounds just like what happened over in the S3 forum when people who wanted 4.3 ota so desperately they ended up getting hard bricks and relocked bootloaders.
Taking the OTA, you are giving up kernel modules on NC2 and the ability to go back to MJE if you need. Just flash NC4 baseband (http://forum.xda-developers.com/showpost.php?p=52633373&postcount=391), and stay on NC2 til devs cook up a safe NC4 to use. What Im doing if you ever want to use kexec in the future for aosp roms when it comes
Click to expand...
Click to collapse
Jeez I shouldnt have even said anything about being able to take the OTA w/survival mode.
Theres nothing wrong with taking it if you guys have no issue with not being able to change kernels in the future or downgrade with Odin. If you screw up the survival process though and lose root, beans has already said it will probably be a very long time til there will be an exploit
http://forum.xda-developers.com/showpost.php?p=52603311&postcount=12
http://forum.xda-developers.com/showpost.php?p=52609797&postcount=42
Theres nothing on NC4 coming from NC2 worth losing that imo it shouldnt be long til you see NC4 roms in the dev section pre rooted. But its your phone, and we all take our own risks.
matt_1224 said:
Jeez I shouldnt have even said anything about being able to take the OTA w/survival mode.
Click to expand...
Click to collapse
Thank you for doing so - it is appreciated by many. Sometimes people get caught up in their own circumstances and cannot appreciate that not everything is so black and white.
Sent from my SM-N900V using XDA Premium 4 mobile app
Like I said, it worked for me after doing some pre-maintenance.
My thought process was that being it'll probably be close to a year before Verizon releases another update... I plan to jump ship before I see another OTA.
That, or the awesome Devs here that give Big Red the finger and find ways to do the impossible.
Sent from my SM-N900V using XDA Premium 4 mobile app
Reilly1812 said:
Sometimes people get caught up in their own circumstances and cannot appreciate that not everything is so black and white.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You mean some people rush to have the newest things, that they dont realize what they are giving up for it.
http://forum.xda-developers.com/showthread.php?t=2750875
This thread already exists in Q&A and was simply trying to save some headaches now as well as down the road for those who don't know...
again if all you care about is root on your phone... nobody is stopping you from the attempt
There is already a thread for this:http://forum.xda-developers.com/showthread.php?t=2750875
Thread closed and moved to Q and A like its supposed to be.