Confusion about the official 4.4 update coming soon - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Is the OFFICAL 4.4 KitKat ATT update TW? Also, as silly as it sounds, can you just run the one-click leaked 4.4 right over a rooted SG4 running a AOSP ROM?
Sent from my GT-I9505G using xda app-developers app

Yes. Samsung is not likely to give up TW anytime soon unfortunately. Someone out there must actually like it.
No. Well, you could but then you can kiss AOSP goodbye forever.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

Also depends on if your on a locked boot loader with Knox like mf3 or mk2. I don't know if you could flash the leak. But I do know as stated above if your boot loader isn't locked it will be after flashing it. If your not on safe stap there are plenty of ROMs built off the 4.4 leak like shostock that won't lock your boot loader

SelfElevated2 said:
Also depends on if your on a locked boot loader with Knox like mf3 or mk2. I don't know if you could flash the leak. But I do know as stated above if your boot loader isn't locked it will be after flashing it. If your not on safe stap there are plenty of ROMs built off the 4.4 leak like shostock that won't lock your boot loader
Click to expand...
Click to collapse
Thanks, I'm on MDL but I didn't know ShoShock was 4.4 TW, I'll just use that!
Sent from my GT-I9505G using xda app-developers app

http://forum.xda-developers.com/showthread.php?t=2468860

Related

[Q] Noob Q about OTA's.

So as I've gathered I can't update OTA when one is available if I have a custom recovery (CWM, TWRP). My question however is if I will be able to apply the update using my custom recovery, and if so, will I retain root and all my frozen bloat from TiBa? Thanks.
If you're talking about stock ota, then no if you have a custom recovery
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
blyndfyre said:
So as I've gathered I can't update OTA when one is available if I have a custom recovery (CWM, TWRP). My question however is if I will be able to apply the update using my custom recovery, and if so, will I retain root and all my frozen bloat from TiBa? Thanks.
Click to expand...
Click to collapse
Will get custom updates that you can flash through recovery long before the carrier releases the same update..
Sent from my FoxHounded AT&T S4
rcklss1 said:
Will get custom updates that you can flash through recovery long before the carrier releases the same update..
Sent from my FoxHounded AT&T S4
Click to expand...
Click to collapse
You are referring to custom ROM's correct? I was hoping to remain stock and root and still be able to apply updates.
Maybe I should be the bullet and flash a custom ROM that still incorporates TW (want the gestures).
Sent from my SGH-I337M using xda premium
blyndfyre said:
You are referring to custom ROM's correct? I was hoping to remain stock and root and still be able to apply updates.
Maybe I should be the bullet and flash a custom ROM that still incorporates TW (want the gestures).
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
thats what i am doing.

AT&T Samsung Galaxy S4 Bootloader

Hey, I have the Samsung galaxy s4 and I have been rooted for about 3 months. I heard the Bootloader for the att variant is locked, but every time I boot my phone up, it shows samsung logo and under that it shows a lock which is unlocked and under it it says custom. Does this mean my Bootloader is unlocked or is this for everyone? My baseband version is I337UCUAMDB.
Sent from my SGH-I337 using xda app-developers app
mahmud_yusuf44 said:
Hey, I have the Samsung galaxy s4 and I have been rooted for about 3 months. I heard the Bootloader for the att variant is locked, but every time I boot my phone up, it shows samsung logo and under that it shows a lock which is unlocked and under it it says custom. Does this mean my Bootloader is unlocked or is this for everyone? My baseband version is I337UCUAMDB.
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
It does it for everyone that is rooted the bootloader is still locked but there is a way to remove that.Here is how http://androidtechy.com/index.php/v...icon-after-rooting-the-samsung-galaxy-s4.html and before someone else tells you so you know questions have to go in Q/A section.
An easier way IMO, flash a stock att mf3 ROM that has stock kernal then use triangle away.
This ROM works, just Loki doki after flashing.
http://forum.xda-developers.com/showthread.php?t=2364635
Then use triangle away.
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
REDFOCZ said:
An easier way IMO, flash a stock att mf3 ROM that has stock kernal then use triangle away.
This ROM works, just Loki doki after flashing.
http://forum.xda-developers.com/showthread.php?t=2364635
Then use triangle away.
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Click to expand...
Click to collapse
But if you do that, you won't be able to install custom ROMs without safestrap, so if you have any interest in CM/AOSP Roms, leave it alone...
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
You just flash the ROM through cwm or twrp does not flash boot loaders there for you can still use aosp Roms. The ROM I linked is safe to flash and keep root and custom recovery.
---------- Post added at 05:28 PM ---------- Previous post was at 05:22 PM ----------
Only thing is to do what I posted he would have to be on MDL bootloaders not MDB.
I'm rooted with Philz CWM Touch and running GoldenEye with Faux13. I don't have that splash screen....
Sent from my GT-I9505 using XDA Premium HD app
guitarpunk8403 said:
But if you do that, you won't be able to install custom ROMs without safestrap, so if you have any interest in CM/AOSP Roms, leave it alone...
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've got the unlock customs logo as well, does that mean my boot loader isnt locked? I thought it was.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
No it means you've flashed a kernel or ROM that tripped the custom firmware counter. The use of triangle away is that it resets that counter back to zero and give you the standard Galaxy S4 splash screen
I found this fix in one of the threads. Not sure if it will work for you, but it did for me and I'm on MF3.
1. Update SuperSU app
2. Launch app and update binary
3. Reboot
4. Download and launch Root Explorer (or another file manager that can access system files)
5. Navigate to a folder called "/system/xbin"
4. Delete ONLY files in that folder with the word "busybox" within its filename or symlink path. You should end up with three files left.
5. Reboot
(Probably don't have to Reboot on Step 3, but I did it to see if custom boot screen was gone... it wasn't... so I included it in my steps.)
Found it. Credit goes to ou812bkewl. Here was the post... http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM
REDFOCZ said:
No it means you've flashed a kernel or ROM that tripped the custom firmware counter. The use of triangle away is that it resets that counter back to zero and give you the standard Galaxy S4 splash screen
Click to expand...
Click to collapse
The reason why I asked if I'm locked down is because, one of the replies said if the op uses one of the methods to remove the padlock screen than he'd than be forced to use SS to flash roms. Don't we need to anyway?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
The only time you would run that risk is if you Odin back to stock MDL and took the MF3 ota. Flashing a ROM is safe with no risk of bootloaders or basebands locking anything.

Upgrading to 4.4 kit Kat

Hey guys quick question my n4 is rooted and running cm10.1.3. I never bothered to upgrade to 4.3, so my radio, kernel and bootloader are stock 4.2.2. Is it better to get the ota update and be up on things or flash stock kernel, boot loader and radio for 4.4 when ever there available? Or maybe factory image?
Sent from my Nexus 4 using xda app-developers app
Just flash the stock images for kit Kat when they are available, right now back up all your data
Sent from my Nexus 4 using xda app-developers app
sacramento458 said:
Hey guys quick question my n4 is rooted and running cm10.1.3. I never bothered to upgrade to 4.3, so my radio, kernel and bootloader are stock 4.2.2. Is it better to get the ota update and be up on things or flash stock kernel, boot loader and radio for 4.4 when ever there available? Or maybe factory image?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
my friend as this will pop up all over the forum the best thing to do is just wait for a rooted version to show up. I did not upgrade my bootloader and I have not had any issues with 4.3 which mind you is a great running OS you should try it.
I dont understand having root then unrooting to flash stock which you obviously dont like since you run cm and then wait to root it all over again to back an upgraded rooted version of cm...
aanonymoushuman said:
Just flash the stock images for kit Kat when they are available, right now back up all your data
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Alright thanks will do
Sent from my Nexus 4 using xda app-developers app
Question on the way for the custom recovery+kernel guys on 4.3 what is the best to upgrade besides wiping your entire phone and flashing the stock images entirely?.
I think i know 2 ways just not sure they are recommended, 1st is flashing stock kernel + returning recovery to stock (should get OTA)
2nd is flashing only the system.img and the bootloader me thinks.
Feel free to verify this.
:good:
playya said:
my friend as this will pop up all over the forum the best thing to do is just wait for a rooted version to show up. I did not upgrade my bootloader and I have not had any issues with 4.3 which mind you is a great running OS you should try it.
I dont understand having root then unrooting to flash stock which you obviously dont like since you run cm and then wait to root it all over again to back an upgraded rooted version of cm...
Click to expand...
Click to collapse
You make a lot of sense ,its more of curiosity and so I won't brick my nexus. So I can get away with not upgrading my bootloader for 4.4?
What about kernel, do I need to update that for 4.4 or is that judgement call?
Sent from my Nexus 4 using xda app-developers app
sacramento458 said:
You make a lot of sense ,its more of curiosity and so I won't brick my nexus. So I can get away with not upgrading my bootloader for 4.4?
What about kernel, do I need to update that for 4.4 or is that judgement call?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
you are asking questions that trial and error are going to figure out for us. Kernels of course if you are on a 4.4 rom you would use a 4.4 kernel. Upgrading your bootloader may or may not be needed but we wont know until kitkat starts popping. everyone said you needed to upgrade bootloader for 4.3 but I have never had any issue at all.... Just wait it out and read read read
Tricepz said:
Question on the way for the custom recovery+kernel guys on 4.3 what is the best to upgrade besides wiping your entire phone and flashing the stock images entirely?.
I think i know 2 ways just not sure they are recommended, 1st is flashing stock kernel + returning recovery to stock (should get OTA)
2nd is flashing only the system.img and the bootloader me thinks.
Feel free to verify this.
:good:
Click to expand...
Click to collapse
Not to sure but as long as you're on stock ROM and stock kernel you should be fine although I don't know if custom recovery keeps you from getting update.
Sent from my Nexus 4 using xda app-developers app
playya said:
you are asking questions that trial and error are going to figure out for us. Kernels of course if you are on a 4.4 rom you would use a 4.4 kernel. Upgrading your bootloader may or may not be needed but we wont know until kitkat starts popping. everyone said you needed to upgrade bootloader for 4.3 but I have never had any issue at all.... Just wait it out and read read read
Click to expand...
Click to collapse
Thanks for the clarification, appreciate the support.
Sent from my Nexus 4 using xda app-developers app
sacramento458 said:
Thanks for the clarification, appreciate the support.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
no problem hopefully you can pass it on to others like you who may be unsure of what to do...
playya said:
no problem hopefully you can pass it on to others like you who may be unsure of what to do...
Click to expand...
Click to collapse
Absolutely bro
You do have to be on stock recovery, stock bootloader for the update to go thru properly otherwise it'll fail.
Tricepz said:
Question on the way for the custom recovery+kernel guys on 4.3 what is the best to upgrade besides wiping your entire phone and flashing the stock images entirely?.
I think i know 2 ways just not sure they are recommended, 1st is flashing stock kernel + returning recovery to stock (should get OTA)
2nd is flashing only the system.img and the bootloader me thinks.
Feel free to verify this.
:good:
Click to expand...
Click to collapse
If you are still on stock rom and you just have custom kernel+recovery, U could do the following for not using any current apps or files.
- Wait till your favorite Toolkit (e.g Wug) get updated for 4.4 and then download the official factory rom.
- Extract it and keep all separate zips, like radio, bootloader,system etc.
- Unroot and flash stock kernel
- Flash all previous zips, EXCEPT user.img which will delete everything
- Reroot and U r ready to flash again custom kernel
Maybe a noob question but my n4 is rooted. Will this cause any problems withe the update?
Sent from my Nexus 4 using xda app-developers app
RASTAVIPER said:
If you are still on stock rom and you just have custom kernel+recovery, U could do the following for not using any current apps or files.
- Wait till your favorite Toolkit (e.g Wug) get updated for 4.4 and then download the official factory rom.
- Extract it and keep all separate zips, like radio, bootloader,system etc.
- Unroot and flash stock kernel
- Flash all previous zips, EXCEPT user.img which will delete everything
- Reroot and U r ready to flash again custom kernel
Click to expand...
Click to collapse
The original stock kernel of 4.3 is on the bootloader.img on the google source code aye?
Thanks, now we just need to wait for the official 4.4 on google's developers.
Tricepz said:
The original stock kernel of 4.3 is on the bootloader.img on the google source code aye?
Thanks, now we just need to wait for the official 4.4 on google's developers.
Click to expand...
Click to collapse
Here a direct link for stock kernel 0.84 from JWR66V factory image
http://d-h.st/cIJ
Hello,
My phone has already had the radio upgraded to latest so it can run 4.3. I am rooted, have TWRP 2.6.3.0, will I be ok to flash the PA 4.4 and gapps? I keep posts about folks losing their sdcard data and their custom recovery being removed (not sure how!).
Thanks.
Schur1k said:
Maybe a noob question but my n4 is rooted. Will this cause any problems withe the update?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Do you have a custom recover?
Sent from my Nexus 4 using xda app-developers app
Schur1k said:
Maybe a noob question but my n4 is rooted. Will this cause any problems withe the update?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Do you have a custom recovery?
Sent from my Nexus 4 using xda app-developers app
maritimesbob said:
Hello,
My phone has already had the radio upgraded to latest so it can run 4.3. I am rooted, have TWRP 2.6.3.0, will I be ok to flash the PA 4.4 and gapps? I keep posts about folks losing their sdcard data and their custom recovery being removed (not sure how!).
Thanks.
Click to expand...
Click to collapse
I'm sure that radio doesn't affect your ability to flash certain ROMs so you shouldn't have a problem flashing 4.4. As far as losing SD data not sure how that's happening.
Sent from my Nexus 4 using xda app-developers app

Can I flash nc4, nc8, nc9, etc. Roms over a nb1 ROM?

In the Att all thing mk2 nb1 section it has all this ROMs that are all 4.4.2 based but I wasn't sure if they would work and could be flashed over a nb1 ROM in another slot
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
jsimsfour said:
In the Att all thing mk2 nb1 section it has all this ROMs that are all 4.4.2 based but I wasn't sure if they would work and could be flashed over a nb1 ROM in another slot
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
To be on this forum and understand your phone you got to do some reading. This question has been made hundred of times. When i join this forum they would be really nasty for asking the same question over and over.
I will give you an answer anyway.
Since you have one of the latest builds. AT&T has locked the bootloader which makes very hard the process of rooting and installing custom roms. In other words you can only flash TW roms.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
netomel said:
To be on this forum and understand your phone you got to do some reading. This question has been made hundred of times. When i join this forum they would be really nasty for asking the same question over and over.
I will give you an answer anyway.
Since you have one of the latest builds. AT&T has locked the bootloader which makes very hard the process of rooting and installing custom roms. In other words you can only flash TW roms.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes i knew that nb1, mk2, and mf3, all have lock bootloaders which mean i can only flash tw based roms. I was asking if the others like nc8 nc9 build numbers are like variants of nb1 or something like that since they are listed under 4.4.2 tw based roms. now im thinking that those are for people who had what ever build came before mf3 that can use loki to flash the latest roms.lease tell me if im wrong.
jsimsfour said:
Yes i knew that nb1, mk2, and mf3, all have lock bootloaders which mean i can only flash tw based roms. I was asking if the others like nc8 nc9 build numbers are like variants of nb1 or something like that since they are listed under 4.4.2 tw based roms. now im thinking that those are for people who had what ever build came before mf3 that can use loki to flash the latest roms.lease tell me if im wrong.
Click to expand...
Click to collapse
You can flash any build that is the same android version. The only thing that people with Loki get are AOSP ROMs. Other bases like nc9 and others are still Touchwiz.
Sent from my SGH-I337 running BlackBox 3.0
DeadlySin9 said:
You can flash any build that is the same android version. The only thing that people with Loki get are AOSP ROMs. Other bases like nc9 and others are still Touchwiz.
Sent from my SGH-I337 running BlackBox 3.0
Click to expand...
Click to collapse
OK and if a rom has I9505 for the model of the s4 I can flash that from as long as it to based and I flash the 1337 kernel ?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
jsimsfour said:
OK and if a rom has I9505 for the model of the s4 I can flash that from as long as it to based and I flash the 1337 kernel ?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yes. Any Touchwiz ROM from any S4 except the 8 core I9500 will work.

WiFi patch for NC1 4.4.3 bootloader

I have spent some weeks with a new NC1 GS4 bootloader. Are developers working on a way to fix the issue with Knox preventing WiFi driver from loading?
I see patches for 4.3 floating around but not 4.4.
This is a real issue. Just wanted to know if developers are aware of it and if anyone is working on a patch we can flash via Odin?
I have another gs4 with mdj boot loader and I have no issues at all with WiFi not loading on boot.
cantenna said:
I have spent some weeks with a new NC1 GS4 bootloader. Are developers working on a way to fix the issue with Knox preventing WiFi driver from loading?
I see patches for 4.3 floating around but not 4.4.
This is a real issue. Just wanted to know if developers are aware of it and if anyone is working on a patch we can flash via Odin?
I have another gs4 with mdj boot loader and I have no issues at all with WiFi not loading on boot.
Click to expand...
Click to collapse
What exactly are you having issues with? If you mean getting Wi-Fi on a 4.4.2 ROM with the NC1 bootloader, all you need to do is flash the kernel modules for whatever kernel you're on in Safestrap. Other than that I don't know what other issue you'd have.
Sent from my SGH-I337 running GPE
Thanks for reaching out, im currently not using safestrap
Sent from my GT-I9505G using XDA Premium 4 mobile app
Can you help me with your suggestion?
Sent from my GT-I9505G using XDA Premium 4 mobile app
The phone I'm having issues with is an unlocked booootloader but is Knox 0x1
Sent from my GT-I9505G using XDA Premium 4 mobile app
It looks like safe strap on works on at&t and Verizon. Do you experience any WiFi issues on you setup with safe strap?
Sent from my GT-I9505G using XDA Premium 4 mobile app
cantenna said:
It looks like safe strap on works on at&t and Verizon. Do you experience any WiFi issues on you setup with safe strap?
Sent from my GT-I9505G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, I haven't had any issues unless it was broken in the ROM itself. For you I'd recommend using ODIN to flash NB1 first though, and hopefully that would fix your problem. Then you can OTA back to NC1 or downgrade to MK2 for root.
I have a Canadian unlocked boot loader fw are different for me. Unfortunately I can only downgrade to NC1 ATM which comes with 4.4.2. I did try upgrading to NE1 but issue was still there once I rooted and custom so I decided to downgrade back to NE1.
Sent from my GT-I9505G using XDA Premium 4 mobile app
So I found solution to my problem. If you have a new boot loader 4.4.2 and you want a stable custom ROM with WiFi, then a custom touch wiz ROM is what you need to install preferably a custom ROM based off of the same fw as installed bootloader. I guess the issue is Asop and GE ROMs were never designed to work with a unlocked Knox bootloader ? I find that this these pure android roms have wifi issue not working intermittently.
Buyer beware: intermittent WiFi issue on Knox boot loader is solved by flashing a custom touch wiz ROM based on boot loader fw.
If your thinking about buying a new gs4 with knox boot oader be sure that your okay with living with touch wiz custom ROMs but if you don't care about working WiFi then your still free to flash pure android.
Hopefully this changes in the future
Sent from my GT-I9505G using Tapatalk

Resources