Database Users

Chainfire 3D on SGH-I337 problem

I rooted my galaxy s4, OTA MF3 updated, I accidently installed Chainfire 3d and tapped 'install CF3D driver', and instantly the device reboots and stuck at at&t logo. i tried latest stock firmware to flash with Odin 3.07, but it says
<NAND write start>
<FAIL(Auth)>
.
also did factory reset but it stuck at the at&t logo every time.
what should i do!!
I sent my device to MobileTechVideos for JTAG brick repair and ROM/root upgrade.
do you think they can fix it with JTAG?

Please tell me this isn't the same guy from a few days ago with a different username.
If not. You did not accidentally install it! You have to click install and accept in the play store then install the drivers through the app. You intentionally installed it but you were too busy NOT reading anything that says that it is only compatible on specific hardware. Now you are screwed and have no way to fix it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Way too coincidental...
http://forum.xda-developers.com/showthread.php?t=2419863
If it's not you, please read that thread so we don't have to keep cluttering the board up with the same stuff over and over again. Any help you will find for your issue has been posted in that thread.
If it is you, I hope you are banned for multiple accounts.

OH NO
graydiggy said:
Please tell me this isn't the same guy from a few days ago with a different username.
If not. You did not accidentally install it! You have to click install and accept in the play store. You intentionally installed it but you were too busy NOT reading anything that says that it is only compatible on specific hardware. Now you are screwed and have no way to fix it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
it can't be fixed ANYWAY? by the way, why do you think the Odin doesn't work? i want to know why my device can't be fixed. explain to me please, why can't it be fixed and what is the problem that make it unable to fix.

You are on MF3. Thee is no custom recovery on MF3. There is no ODIN flashable MF3 ROMs, there is no MF3 on Kies.
If you would read the stickies and most MF3 related threads, you would know that there is no way to come back from messing up on MF3.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Nope i'm not that guy
graydiggy said:
Please tell me this isn't the same guy from a few days ago with a different username.
If not. You did not accidentally install it! You have to click install and accept in the play store then install the drivers through the app. You intentionally installed it but you were too busy NOT reading anything that says that it is only compatible on specific hardware. Now you are screwed and have no way to fix it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you mean the guy who posted same problem few days ago?

Yep... Created multiple threads on it too.. scott14719 posted a link.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

.
graydiggy said:
You are on MF3. Thee is no custom recovery on MF3. There is no ODIN flashable MF3 ROMs, there is no MF3 on Kies.
If you would read the stickies and most MF3 related threads, you would know that there is no way to come back from messing up on MF3.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I installed Clockworkmod recovery and did the factory reset. isn't Clockworkmod recovery a custom recovery? so that means, i have to collect 400 dollars and switch the mainboard at at&t or should i wait until odin flashable MF3 comes out? i just bought galaxy s4 a week ago.
anyway i'll find my way to solve this even if that means i have to switch mainboard. thanks for replying.

If you are truly on MF3,you would not be able to install CWM.
It means that you have a $650 paperweight for the time being until you
A: Get it replaced
B: Get a new motherboard
C: learn ADB and can fix it with that
D: Try a J-Tag repair
E: Wait until the bootloader gets unlocked. If it is even possible.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

graydiggy said:
If you are truly on MF3,you would not be able to install CWM.
It means that you have a $650 paperweight for the time being until you
A: Get it replaced
B: Get a new motherboard
C: learn ADB and can fix it with that
D: Try a J-Tag repair
E: Wait until the bootloader gets unlocked. If it is even possible.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
A: Yep
B: Would be better off getting another phone. I'm not sure if the NV memory is located on the Motherboard or not?
C: ADB might not be able to connect if he can't get the phone booted.
D: So far JTAG is a no-go on MF3.
C: Yep, but hopefully Samsung will release the full MF3 firmware (hopefully through KIES as well) that will be able to reflash the firmware to the phone.
I would say replace it or be screwed until MF3 firmware drops.

Noooooooooooo
scott14719 said:
A: Yep
B: Would be better off getting another phone. I'm not sure if the NV memory is located on the Motherboard or not?
C: ADB might not be able to connect if he can't get the phone booted.
D: So far JTAG is a no-go on MF3.
C: Yep, but hopefully Samsung will release the full MF3 firmware (hopefully through KIES as well) that will be able to reflash the firmware to the phone.
I would say replace it or be screwed until MF3 firmware drops.
Click to expand...
Click to collapse
Why did AT&T updated to MF3!!!!!!!!!! do if MF3 comes out, does that mean i can flash that with Odin?
i should say MF3 stands for Mother+F word times 3. anyway thanks for replying.
I sent my device for JTAG yesterday. they might not fix it

ryujeff said:
Why did AT&T updated to MF3!!!!!!!!!! do if MF3 comes out, does that mean i can flash that with Odin?
i should say MF3 stands for Mother+F word times 3. anyway thanks for replying.
I sent my device for JTAG yesterday. they might not fix it
Click to expand...
Click to collapse
I'm sure AT&T views MF3 as a complete success. It's just the people interested in customizing and modding their phones (XDA minded people) that hate it.
When Samsung releases the full MF3 firmware, you should be able to use ODIN to flash back to stock. However, no one will know for sure until it is released. It has been a while since the MF3 OTA started to roll out, so if Samsung is going to release the full MF3 firmware, it should be soon.
As far as JTAG goes, I haven't seen a successful flash yet. I think the JTAG people are waiting for the firmware release as well.

I thought J-Tag works for flashing MF3 but doesn't work for downgrade. It doesn't work for both?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

scott14719 said:
I'm sure AT&T views MF3 as a complete success. It's just the people interested in customizing and modding their phones (XDA minded people) that hate it.
When Samsung releases the full MF3 firmware, you should be able to use ODIN to flash back to stock. However, no one will know for sure until it is released. It has been a while since the MF3 OTA started to roll out, so if Samsung is going to release the full MF3 firmware, it should be soon.
As far as JTAG goes, I haven't seen a successful flash yet. I think the JTAG people are waiting for the firmware release as well.
Click to expand...
Click to collapse
Yay! thank you so much for at least giving me hope to fix my device. i was very experienced developer of galaxy a, you may never heard of galaxy a. it was released only in Korea. i thought galaxy s4 might be similar to galaxy a. i should've studied more. in Korea, we used to make custom roms flashable by Odin. XDA doesn't seem to have roms that are flashable with Odin. i used to make my own roms. please could you help me fixing my phone when MF3 releases? i don't know a lot about galaxy s4. again, thank you.

XDA is full of ODIN flashable Stuff. MF3 is just locked tight. We are working on some stuff to make it better for now until there is a bootloader unlock.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

graydiggy said:
XDA is full of ODIN flashable Stuff. MF3 is just locked tight. We are working on some stuff to make it better for now until there is a bootloader unlock.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't know that! thanks!

graydiggy said:
I thought J-Tag works for flashing MF3 but doesn't work for downgrade. It doesn't work for both?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is from the thread when Aou was trying to JTAG his device...
well i finally got in touch with mobile tech and got a refund/explanation of our problem it seems the qfuse being blown is the main reason this is happening..
Unfortunately, we were not able to repair your device. The device's onboard EMMC controller was in a non-responsive state. It is advised to try out warranty replacement if possible or to search for a parts device and use it's mainboard for the swap.
The blown fuse is the reason JTAG (or ODIN / KIES) for that matter) can not revert the device to a previous firmware.
Once the full MF3 firmware is available, it will probably be possible to restore the device via JTAG to MF3, but as we know, the MF3 firmware is not yet available. Therefore, it can not be done (yet). And once / if it is released, there is no guarantee it will work until it is tried.
The quote from Mobile Tech above mentions swapping mainboards, but I don't think it will work due to the NV memory I mentioned before (but maybe it can?).
Anyway, the key seems to be wait until the full MF3 firmware is released or wait until / if the bootloader is unlocked. I think the firmware is the better bet and it isn't guaranteed.

Switching out motherboards should be no issue. All that is being done is dropping it into the back of the screen, plugging in some flex cables, slap it back together and booting it up. I know why we can't downgrade, just didn't realize that a full system dump of MF3 was not enough for J-Tag.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

ryujeff said:
Didn't know that! thanks!
Click to expand...
Click to collapse
Well, be careful. The SGH-I337 (AT&T S4) has a locked bootloader, so only official firmware (signed by Samsung's encrypted key) can be flashed via ODIN. To complicate things, the MF3 update (which you have) made the previous firmwares unflashable via ODIN. Phones that did not update to MF3 (still on MDB or MDL firmware) have the ability to flash Custom recoveries and Roms because of an exploit called "LOKI". LOKI was patched when the MF3 OTA was released. So any phone on MF3 can not flash recoveries or ROMs at this point. ODIN is basically useless for the time being.
I highly suggest you read the "pinned" threads in the "general" and Q & A sections. Alsor ead the threads that have "MF3" in the titles. This will give you a good understanding of what your options are if / when you can repair your phone. There is a method being developed that would allow several custom Roms to exist on the phone (MF3), but it hasn't been tested or released yet. The thread about it is in the "general" section as well. However, again, it will do you no good unless you get your phone repaired / replaced.
---------- Post added at 12:14 AM ---------- Previous post was at 12:09 AM ----------
graydiggy said:
Switching out motherboards should be no issue. All that is being done is dropping it into the back of the screen, plugging in some flex cables, slap it back together and booting it up. I know why we can't downgrade, just didn't realize that a full system dump of MF3 was not enough for J-Tag.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I realize the physical action of switching motherboards isn't an issue, I was just wondering if it would do any good? If the NV memory remains in another area of the circuitry, or other memory remains that still has a part of the MF3 bootloader structure intact, switching the motherboard by itself won't do any good. If all structures of the MF3 bootloader are included on the motherboard, maybe it would work.
Also, last I knew, bootloaders can't be pulled via system dump. They have to be obtained via official firmware release. In the case of MF3, the bootloader parts from the OTA can't be combined with a system dump from a post OTA MF3 device because of signing issues. It just doesn't work. It's been tried. I know there are a couple of MF3 Tar balls floating around but they are only good for parting out. Aou has tried a bunch of this stuff. Honestly, I do not know 100% of the technical reasons why it won't work. I have a pretty good understanding but that is it. Truly, the MF3 Bootloader is the problem and until the full, official, MF3 firmware is released from Samsung (or a signing key is released / leaked) I don't see much happening in the area of repairing / restoring bricked MF3 devices.

It shouldn't remain. The only other parts that are separate from the motherboard and screen assembly. Are the charging port assembly/flex,the camera, the softkeys/home button assembly and the back housing that just holds antennas. None of that should have anything on it that would hold any residual MF3 data. Even if something did, it would have to hold the whole update to possibly do any kind of damage in eras of installation and blowing the Qfuse. If it did not and it blew the fuse without updating, it would instantly render the device useless if the motherboard had MDL on it.
All data is stored in the motherboard.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

[Q] Getting my S4 on Tues, have some questions to rom/root it.

So I am upgrading from my beloved S3 to the Red S4 now, getting it in on Tues. Thank you employee line deals.. So anyways, I saw some stickies about to avoid the OTA otherwise can not flash a diff kernel, correct? That there are no odin files of the new update.
That being said, How will I know when I get my device in, if they already gave it to me updated or if its where I can custom rom it. Would figure its a certain thing in the status menu part for a version. Dont wanna mess this up, so doing my research now.
Also any custom roms that are super worth it? I know on my S3, I use a nice one with the multi window and floating windows. So if there is a super good one to use, IF I can use one, what is it?
Also does the toolbox program we used for the S3 work for S4? (Havent checked on updates in awhile) cause I need to least root this sucker if I wanna restore my titanium backups.
Anyways thanks for any points in the right direction, this is the part I always hated.. working with a new phone then sitting with it till I study up on all the roms and tweaking of it.

When you get your device got to settings>more>about device and if the the last three characters of the baseband is MF3 then you can only use stock kernels with safestrap recovery and if it is MDL or MDB you can have custom recovery, custom roms with motochopper root. There are some pretty good roms out there. Unfortunately i'm on MF3 cause i got the OTA and it updated overnight.

Also when you first get your box with the phone inside. Look on the outside of the box and it will show which firmware is on it. It will have the last three letters of mdb, MDL, or MF3. All I can say is HOPE for MDL which may or may not be possible. But the red colored ones do not seem to go as fast so HOPEFULLY it is MDL.
Next course of action IF it is MDL is DO NOT connect to WiFi, and I would also suggest NOT putting in the Sim card yet. Download Motochopper by Jbliss and or Casual+motochopper by Adam Outler which will root and install tarp recovery. Then read up from there and flash a ROM.
If it comes with MF3 then you will need to flash SafeStrap to be able to out "some Roms" onto your phone and have root. But safestrap is more limited than what you are used to/what I posted in the paragraph above.
I am GUESSING you are buying it from ATT? Then chances may be slim of anything other than mf3. But I did get a MDL from Walmart (they had black and white if I remember correctly, not sure about red). I got a black one with MDL about a month ago and they had two others in stock. So places like that MAY be a better bet for you.
Now this is MY opinion and take it for what it is worth. I will NEVER be buying another ATT phone due to how hard they are locking the boitloaders down. NEVER... So my next suggestion is get a T-Mobile S4 and you can use it on ATT and it does not have locked bootloaders at this time and hopefully never.
Read all the sticky threads about MF3 and prepare yourself in case you want to keep it. Good luck to you
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337

You will have to try out different roms and see for yourself what they have to offer.if it turns out to be MF3 take the most important advice "!!READ!!"
Sent from my GT-I9505 using XDA Premium 4 mobile app

Before you get your phone read a whole lot about it. Read all the pinned (stickies) threads first. Then keep reading before you do anything with it. Good luck!

RockRatt said:
Also when you first get your box with the phone inside. Look on the outside of the box and it will show which firmware is on it. It will have the last three letters of mdb, MDL, or MF3. All I can say is HOPE for MDL which may or may not be possible. But the red colored ones do not seem to go as fast so HOPEFULLY it is MDL.
Next course of action IF it is MDL is DO NOT connect to WiFi, and I would also suggest NOT putting in the Sim card yet. Download Motochopper by Jbliss and or Casual+motochopper by Adam Outler which will root and install tarp recovery. Then read up from there and flash a ROM.
If it comes with MF3 then you will need to flash SafeStrap to be able to out "some Roms" onto your phone and have root. But safestrap is more limited than what you are used to/what I posted in the paragraph above.
I am GUESSING you are buying it from ATT?
Click to expand...
Click to collapse
Yes, getting from ATT dealer accounts, while I know I can use T-Mobiles stuff, I wouldnt have the "LTE" ability, which is what is happening now with my TMO S3, I have 4G, yes, but not LTE. So giving that phone to my friend for her upgrade, so she can get LTE with TMO while upgrading myself. Now if I am MDL, then woot, I take it its almost business as usual with the way I worked my roms and so of the past?
Then lets say I am MF3, now that in itself. may not be "as bad" since honestly, the S3's rom was pretty solid out of the box, just root it and go. Could I assume if I dont wanna put a diff rom on MF3, I could least root the stock rom easy enough and move on? (Plus could use titanium backup to remove the bloat) Seems abit crazy on MF3 and safe strap, sounds like its using the internal storage space to run the rom off of.
Now in regards to if I am MDL, I assume you mean download motochopper for the pc, then hook up and let it run. Now after that point, is my phone safe from OTA? Do I need to install a new rom right then and there or can I use stock rom and know that I am safe from it updating to MF3. Just making sure I got my notes right for tm morning when it comes in by fedex heh.
Qbeezy24 said:
When you get your device got to settings>more>about device and if the the last three characters of the baseband is MF3 then you can only use stock kernels with safestrap recovery and if it is MDL or MDB you can have custom recovery, custom roms with motochopper root. There are some pretty good roms out there. Unfortunately i'm on MF3 cause i got the OTA and it updated overnight.
Click to expand...
Click to collapse
So there is no difference in MDL and MDB? Or was MDL still better? Sounds like really the next couple days are gonna be research and testing.. thats after I put my screen protector on it heh.

Mysticales said:
Now if I am MDL, then woot, I take it its almost business as usual with the way I worked my roms and so of the past?
Click to expand...
Click to collapse
Yes it would be almost exactly business as usual. Of course READ any Roms HOW TO INSTALL section. About the only difference from the S3 flashing is if you are flashing kernels/Roms make sure the are loki'd or use Loki doki during flashing. Again read up on this.
Mysticales said:
Then lets say I am MF3, now that in itself. may not be "as bad" since honestly, the S3's rom was pretty solid out of the box, just root it and go. Could I assume if I dont wanna put a diff rom on MF3, I could least root the stock rom easy enough and move on? (Plus could use titanium backup to remove the bloat) Seems abit crazy on MF3 and safe strap, sounds like its using the internal storage space to run the rom off of.
Click to expand...
Click to collapse
Yes you can flash some Roms (4.2.2 based Roms) with Safestrap. Read all about safestrap as I do not have it and don't know many if the answers since I cannot test. But the one thing is be VERY CAREFUL removing bloat with tibu, once it is gone you will NOT be able to get it back. Read many horror stories if debloating gone wrong and phone not working.
Mysticales said:
Now in regards to if I am MDL, I assume you mean download motochopper for the pc, then hook up and let it run. Now after that point, is my phone safe from OTA? Do I need to install a new rom right then and there or can I use stock rom and know that I am safe from it updating to MF3. Just making sure I got my notes right for tm morning when it comes in by fedex heh.
Click to expand...
Click to collapse
Yes download either Motochopper or I like "Casual+Motochopper" as it gives you a recovery as well. Either cwm or twrp.
No at that point it is NOT safe from OTA updates, you will need to FREEZE certain apps with tibu.
Check out the Roms section. I haven't used it but I believe there is a "neutered mf3 stock firmware" that has the ota updating parts removed already. If you do NOT freeze the apps ATT set up mf3 to Auto Download and INSTALL mf3. Most users got it while they were sleeping, even if they were only stock and rooted. But IF you have a custom recovery and a ROM on it you will not get the auto update and install.
Mysticales said:
So there is no difference in MDL and MDB? Or was MDL still better? Sounds like really the next couple days are gonna be research and testing.. thats after I put my screen protector on it heh.
Click to expand...
Click to collapse
MDB was what came with the phone and MDL was updated within a few weeks if I remember correctly. I believe I still have the mdb bootloaders on my phone and my wife's came with MDL and has those bootloaders. I have seen NO DIFFERENCE as far as flashing or things working differently in my case.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337

So, being on MF3 will not allow us to flash kernals and we are limited to specific Roms? Are those the major differences? Also, should we stay away from the OTA...I keep hearing about it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

nash2000 said:
So, being on MF3 will not allow us to flash kernals and we are limited to specific Roms? Are those the major differences? Also, should we stay away from the OTA...I keep hearing about it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I believe you cannot flash kernels with safestrap. And only 4.2.2 based Roms will work and possibly on tw Roms, but there might be one cm variant that would work. Just check out the safestrap thread for more info on all if this. I think they even have a list if tested working Roms there.
No one knows FOR SURE but I believe the new 4.3 update blows a second qfuse, this will make it so you cannot downgrade to anything lower than MJ6.
MF3 blows the first qfuse which is why you cannot downgrade to MDL bases.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337

Well I have a mf3 gs4 :/ sooo now then. I don't "mind" stock really too much.. ill miss my drop down toggles I thing more from my gs3. I saw one post that explains using terminal to get root access which is something I know I need for sure. So now then those on mf3 are you too staying on stock and just rooting?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Mysticales said:
Well I have a mf3 gs4 :/ sooo now then. I don't "mind" stock really too much.. ill miss my drop down toggles I thing more from my gs3. I saw one post that explains using terminal to get root access which is something I know I need for sure. So now then those on mf3 are you too staying on stock and just rooting?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Kingo root method is an easy one click method that works also. Why stay stock when you can root easily? I was rooted but now on 4.3.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

I just got my phone!!!! I got mine at Costco which I normally get my phone through best buy but there insurance plan stinks now.
Anyways, My phone had the MDF!! So get your phone at Costco!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[email protected] said:
Kingo root method is an easy one click method that works also. Why stay stock when you can root easily? I was rooted but now on 4.3.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Of course I am rooted... you think after being a pioneer with a beloved Htc G1, that I would EVER be on a device without root. =p (Man.. the reinstalling of a 100 apps manually alone without titanium backup along with its prefs, config and data would take a week to get right) I used that exFat method.
But yea, even tho I am rooted, I wouldnt "mind" a diff rom.. or least debloat this sucker. Half tempted to see which ATT apps I could get rid of, issue is... no odin to restore to if something messes up. I am sure someone will do a mf3 recovery sometime eh?
Oh... btw, how would I disable any auto OTA that could come in the future?

[Q] What will happen if I update to 4.4 while still rooted?

I am currently on system version 9.30.1 and I am rooted. My boot loader isn't unlocked and I don't have a custom recovery installed. I am wondering if being rooted will cause issues once the 4.4 update is released. And if so how do I remove root?
Sent from my XT907 using XDA Premium 4 mobile app

Well, since you are rooted, chances are you have probably removed some of the bloat that was installed on your phone by your provider. If this is so, you won't even be able to update to 4.4 unless you first return your phone completely to stock, ie add all the bloat back in. If your phone is not stock, you can remove updater.apk and you won't even be prompted for the update.
If you are completely stock and rooted, when you accept the update to 4.4, once the upgrade completes, you simply will not be rooted anymore. This is true whether you have a locked or an unlocked bootloader. With the unlocked bootloader and a custom recovery, it may be possible to have root if the one in the recovery works with 4.4 Otherwise, we will all have to wait until if/when root becomes available for Android 4.4 and our phone. This is why it is often recommended that you wait to update until the devs have a chance to tear the update apart and look for usable exploits.

Some what on the same topic... I made a back up after unlocking before doing anything... Could I restore said back up flash stock recovery voodoo my root and ota... Or would I still have to rsd then ota?
Sent from my XT907 using xda app-developers app

ezknives said:
Some what on the same topic... I made a back up after unlocking before doing anything... Could I restore said back up flash stock recovery voodoo my root and ota... Or would I still have to rsd then ota?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Yes, you can flash your backup and then take the OTA, but you don't need voodoo if you're unlocked. Re-flash recovery and then flash root.

netizenmt said:
Well, since you are rooted, chances are you have probably removed some of the bloat that was installed on your phone by your provider. If this is so, you won't even be able to update to 4.4 unless you first return your phone completely to stock, ie add all the bloat back in. If your phone is not stock, you can remove updater.apk and you won't even be prompted for the update.
If you are completely stock and rooted, when you accept the update to 4.4, once the upgrade completes, you simply will not be rooted anymore. This is true whether you have a locked or an unlocked bootloader. With the unlocked bootloader and a custom recovery, it may be possible to have root if the one in the recovery works with 4.4 Otherwise, we will all have to wait until if/when root becomes available for Android 4.4 and our phone. This is why it is often recommended that you wait to update until the devs have a chance to tear the update apart and look for usable exploits.
Click to expand...
Click to collapse
Thanks, I am rooted and didnt touch any of the bloatware. I bought the phone in an non-unlockable state, 9.30.1, so I just want some form of kit-kat on this. In an un-xda like fashion im probably going to just take the update ASAP.

AKShotgun said:
Thanks, I am rooted and didnt touch any of the bloatware. I bought the phone in an non-unlockable state, 9.30.1, so I just want some form of kit-kat on this. In an un-xda like fashion im probably going to just take the update ASAP.
Click to expand...
Click to collapse
Being locked & rooted you will lose root perhaps forever.

aviwdoowks said:
Being locked & rooted you will lose root perhaps forever.
Click to expand...
Click to collapse
A lot of guess work.. considering first off that 4.4 hasn't been provided. If it was provided will you be the first to jump?

theemaster said:
A lot of guess work.. considering first off that 4.4 hasn't been provided. If it was provided will you be the first to jump?
Click to expand...
Click to collapse
I have 442 already and boy is it fast!
---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------
But I cannot root on the X that is.

aviwdoowks said:
I have 442 already and boy is it fast!
---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------
But I cannot root on the X that is.
Click to expand...
Click to collapse
You don't say....

theemaster said:
A lot of guess work.. considering first off that 4.4 hasn't been provided. If it was provided will you be the first to jump?
Click to expand...
Click to collapse
Take a look in the S5 and X forums to get the proof you need about KK being hard to root.
AK, I would seriously wait until the devs get hold of the update. Let the devs take the OTA and pull it apart so they can start providing ROMs for SafeStrap. Then, update to KK via SS.

My plan is to go all stock and accept the update IF it ever actually gets released. As my bootloader is unlocked, I always have the option of reflashing recovery on it, make a backup of 4.4, and then run it or some other rom backup as I choose. Also, I'm curious to know, if there is supposed to be superuser built into TWRP, will that allow 4.4 to be rooted anyway, or not?
As you can see, I know just enough to be dangerous, lol, but as long as I can make calls, it's all good.

netizenmt said:
My plan is to go all stock and accept the update IF it ever actually gets released. As my bootloader is unlocked, I always have the option of reflashing recovery on it, make a backup of 4.4, and then run it or some other rom backup as I choose. Also, I'm curious to know, if there is supposed to be superuser built into TWRP, will that allow 4.4 to be rooted anyway, or not?
As you can see, I know just enough to be dangerous, lol, but as long as I can make calls, it's all good.
Click to expand...
Click to collapse
As long as your bootloader is unlocked, all you need to do after you update to the OTA is re-flash recovery and then superuser to regain root.

netizenmt said:
My plan is to go all stock and accept the update IF it ever actually gets released. As my bootloader is unlocked, I always have the option of reflashing recovery on it, make a backup of 4.4, and then run it or some other rom backup as I choose. Also, I'm curious to know, if there is supposed to be superuser built into TWRP, will that allow 4.4 to be rooted anyway, or not?
As you can see, I know just enough to be dangerous, lol, but as long as I can make calls, it's all good.
Click to expand...
Click to collapse
I don't think there is an "if" in it. The executive posted on google+ about receiving the update in the next couple weeks.
Sent from my XT907 using XDA Premium 4 mobile app

AKShotgun said:
I don't think there is an "if" in it. The executive posted on google+ about receiving the update in the next couple weeks.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well its been a few weeks since he said that. Having had a similar situation with Sony and the Xperia Play and ICS, I can tell you the average executive's word isn't worth spit. And then there's the whole Verizon involvement which always adds another level of delay. I'm hoping I'm wrong, but I would be surprised if we get KK in a few Months, never mind weeks.
Sent from my DROID RAZR M using Tapatalk

netizenmt said:
Well its been a few weeks since he said that. Having had a similar situation with Sony and the Xperia Play and ICS, I can tell you the average executive's word isn't worth spit. And then there's the whole Verizon involvement which always adds another level of delay. I'm hoping I'm wrong, but I would be surprised if we get KK in a few Months, never mind weeks.
Sent from my DROID RAZR M using Tapatalk
Click to expand...
Click to collapse
Sorry if it seems like it im not trying to fight you here but he commented on his google+ post saying Razr M and HD KitKat is already at Verizon labs. So im guessing about a month.

I look forward to being wrong. I really hope we get it in the next few months. I've noticed that each revision of Android has made the need to develop custom ROMs less necessary for many phones. Of course that won't lessen our desire or enthusiasm to push the envelope. But when I think how far we have come from my first Android, the LG Ally and Eclair... There was a phone that was crap stock, but once unlocked and customized, it was a very decent phone for its time and price point. Today, its harder to see the need or difference between stock and custom ROMs, other than removal of bloat and occasionally some new bell or whistle. Still, I can't seem to resist their siren's call any more than the rest of you. Which is why I'm running CM11. Lol!
Sent from my DROID RAZR M using Tapatalk

[Q] KitKat OTA (NC4) and SU Survival Mode

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.

[Q] Will an OTA remove root access?

Hello there,
I've had an AT&T Galaxy S4 for about a year now and I've been on custom ROMs since January of this year. When I was last on Stock, I had Android 4.2.2 Jellybean. Recently, I've been running into a lot of problems with my ROM so I tried installing other ROMs only to find more issues that were bothering me. I decided to just go back to stock but I was curious as to whether taking an OTA update will ruin my root? I do apologize for asking this but I'm still rather new at this. I was also curious if taking the OTA will remove my custom recovery as well as re-lock my bootloader? If I'm not supplying enough information for someone to determine the answer, please let me know and I'll provide that information.

BrokeEven said:
Hello there,
I've had an AT&T Galaxy S4 for about a year now and I've been on custom ROMs since January of this year. When I was last on Stock, I had Android 4.2.2 Jellybean. Recently, I've been running into a lot of problems with my ROM so I tried installing other ROMs only to find more issues that were bothering me. I decided to just go back to stock but I was curious as to whether taking an OTA update will ruin my root? I do apologize for asking this but I'm still rather new at this. I was also curious if taking the OTA will remove my custom recovery as well as re-lock my bootloader? If I'm not supplying enough information for someone to determine the answer, please let me know and I'll provide that information.
Click to expand...
Click to collapse
One question my bro, what galaxy s4 do you have?
Sent from my SGH-I337 using XDA Free mobile app

I don't know the specific model name but I know it's the Galaxy S4 for AT&T

BrokeEven said:
I don't know the specific model name but I know it's the Galaxy S4 for AT&T
Click to expand...
Click to collapse
If you don't know what model you're on you shouldn't be rooted. The at&t version is the i337, and yes if the ota works you'll lose root.
And questions go in the q&a forum, not general
Sent from my Nexus 5 using XDA Free mobile app

you need to know your build first, so you can install right .tar
odin will replace everything. except sdcards. best to back up cards anyway and/or pull ext card.
use terminal emulator and type in
SU
getprop ro.bootloader
it will give you your build--:good:
btw your bootloader was never unlocked on an i337.
EDIT: Beat me jd

Oh really? Cuz whenever I turn my phone on it shows a pad lock unlocked. The same animation appeared on my Galaxy Nexus when I had it so I just assumed the bootloader was unlocked

No, that comes up in the rooting process. The i337 has not been unlocked. There is an exploit called loki-doki for pre MF3 builds that bypasses Sammy's security checks. It allows those of us on early build to flash custom recoveries/kernels. Otherwise you need to use SafeStrap and only TW roms. If you are not familiar with SafeStrap then you are probably on a pre MF3 build.
Some people refer to the exploit as unlocking the phone. That's incorrect though--

You should get the ota root keeper, it backs up the root, then after ota update, you can restore back.
Sent from my XT1031 using XDA Free mobile app