Related
Again, sorry if this is in the wrong place but i dont know who else to ask but you guys.
I originally got my galaxy s4 (AT&T) when it first came out and couldnt wait to root and flash. A couple months later i had to do a warranty exchange just to figure out that it came preinstalled with MF3 (damn mf3) i ended up rooting and like most of you guy who arent/wouldnt be able to flash probably are bored. I then had to do another warranty exchange and when i powered the phone on i went to the more tab in settings and the "about device" was blue not yellow. I knew the phone was on an older firmware and i did confirm it to be on MDL (Sigh of relief) right away i started to root and downloading roms. i havent flashed any yet. My question is, on my stock rom (i am rooted) i keep getting a message. the the red and blue arrows for a new software (its that damn mf3) I DONT WANT IT!!! lol is there any way to stop it from asking me. i keep postponing it but i rerad somewhere u can only do that so much, im all nervous that im gonna wake up one morning and see MF3 took over my phone again lol.
sorry for the essay, if anyone has any info on how to stop it from asking that would be very much appreciated!!!
Thanks,
Dave
This should got in the QA forum. You can download a custom rom to get rid of the message or a freeze a few apps. If I were you, I'd get a custom rom, otherwise why would you care about not having MF3.
ddix585 said:
Again, sorry if this is in the wrong place but i dont know who else to ask but you guys.
sorry for the essay, if anyone has any info on how to stop it from asking that would be very much appreciated!!!
Thanks,
Dave
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2268946
Good luck
And for future, please post in Q & A section.
Or do this.
http://forum.xda-developers.com/showpost.php?p=41424569&postcount=4
And i would freeze those apps right away like the 2 links that were post it on top if not MF3 will automatically update you phone so you need to hurry and do this Good Luck!
Custom ROM and MF3
visuelz said:
This should got in the QA forum. You can download a custom rom to get rid of the message or a freeze a few apps. If I were you, I'd get a custom rom, otherwise why would you care about not having MF3.
Click to expand...
Click to collapse
So if i do flash a custom rom i dont need to worry about it asking or updating on its own. i just flashed vision x ROM TW with Ktoones Kernel and i am loving the rom so far. But if i just keep a custom rom i dont have to worry about the update doing it by itself or freezing it?
Thanks to all the answers,
David
ddix585 said:
So if i do flash a custom rom i dont need to worry about it asking or updating on its own. i just flashed vision x ROM TW with Ktoones Kernel and i am loving the rom so far. But if i just keep a custom rom i dont have to worry about the update doing it by itself or freezing it?
Thanks to all the answers,
David
Click to expand...
Click to collapse
That is correct, good sir. If you froze the update apps/apks you will not be prompt for an update.
However, if you do end up odin'ing your phone for some reason, be sure to quickly block the update by rooting your phone and freeze once again. Odin removes root
Enjoy your custom rom as you are one of the lucky ones still on the old MDL update :good:
Hi everyone,
I am sure this has been covered...but I cannot seem to find the thread. Perhaps your search-foo is better than mine.
Anyways, I have a new AT&T S4 on MDL right now. I am trying to update to MF3 (I337UCUAMF3) but cannot. Via OTA the update downloads, restarts, and gets to 30% then fails. It is on the ATT logo, 30%, says UPDATE FAILED, then restarts. No matter what. I have tried multiple times but it still fails. OTA just fails and fails and will not let me get onto MF3.
I found a supposedly untouched stock MF3 zip and put it on the SD card and tried to update via the stock recovery, but that failed too.
Can anyone help me figure this out?
Thanks!!!
Why update do u not like flashing Roms and such
Sent from my GT-I9505 using xda premium
jball said:
Why update do u not like flashing Roms and such
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Think I should root and ROM? Do they include the LTE bands and what not?
Guess you are right. I was trying to find a ROM that was similar to Hyperdrive (ran it on my S3) but was overwhelmed. Guess I need to read more.
Need the n00bs guide to rooting the att s4 Off i go...and i you have suggestions, let me know!
Thanks!
Don't do it! The update has been out for a while and no one has found a way to unlock or go around the bootloader and doesn't sound like there's much hope.
One click tool: http://forum.xda-developers.com/showthread.php?p=41870561
Awesome ROM!: http://forum.xda-developers.com/showthread.php?p=43748942
solidforce said:
Think I should root and ROM? Do they include the LTE bands and what not?
Guess you are right. I was trying to find a ROM that was similar to Hyperdrive (ran it on my S3) but was overwhelmed. Guess I need to read more.
Need the n00bs guide to rooting the att s4 Off i go...and i you have suggestions, let me know!
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2314494
xBeerdroiDx said:
http://forum.xda-developers.com/showthread.php?t=2314494
Click to expand...
Click to collapse
Where was that 30 min ago!
Thank you all! Phone is rooted and loki'd. Now to pick a rom....any suggestions? Like I said, loved Hyperdrive on my S3.
Thank you all so much! Love this community!
-SF
solidforce said:
Where was that 30 min ago!
Thank you all! Phone is rooted and loki'd. Now to pick a rom....any suggestions? Like I said, loved Hyperdrive on my S3.
Thank you all so much! Love this community!
-SF
Click to expand...
Click to collapse
Congrats! You are one of the few who is still on MDL lol.
As for rom suggestions....I'm sorry, the answer isn't gonna be pretty as it goes with the forum rules.
You have to decide your own rom as it's more of a personal choice. t's all about experimenting + trial & error to suit your taste of needs. Good luck in finding one. :good: :cyclops: They're all in S4 Android development sections
haremmon said:
Congrats! You are one of the few who is still on MDL lol.
As for rom suggestions....I'm sorry, the answer isn't gonna be pretty as it goes with the forum rules.
You have to decide your own rom as it's more of a personal choice. t's all about experimenting + trial & error to suit your taste of needs. Good luck in finding one. :good: :cyclops: They're all in S4 Android development sections
Click to expand...
Click to collapse
Thanks!
Went with the Pac-Man rom. Unfortunately, I had to figure out how to adp a new keyboard apk due to the ASOP keyboard crashing. That was not fun.
Looks great though!!!
Thanks again for all the help!
I am currently running grievous rom on d800 and want to get to KitKat rooted. What method should I take for this? Can I flash rooted 10o and or 10d and go from there with the ota?
muffinflesh said:
I am currently running grievous rom on d800 and want to get to KitKat rooted. What method should I take for this? Can I flash rooted 10o and or 10d and go from there with the ota?
Click to expand...
Click to collapse
from what ive read, if im not mistaken, you need to go back to stock
how to go back to stock
http://forum.xda-developers.com/showthread.php?t=2432476
and you need to wait for the OTA, i heard some people contact att to get the ota pushed faster.
im personally waiting for a custom rom that removes all the att bloat, and ill just flash it on twrp, not sure how long that wait will be couple days perhaps or maybe hours. wish we had better dev support =(
HRodMusic said:
from what ive read, if im not mistaken, you need to go back to stock
how to go back to stock
http://forum.xda-developers.com/showthread.php?t=2432476
and you need to wait for the OTA, i heard some people contact att to get the ota pushed faster.
im personally waiting for a custom rom that removes all the att bloat, and ill just flash it on twrp, not sure how long that wait will be couple days perhaps or maybe hours. wish we had better dev support =(
Click to expand...
Click to collapse
Yeah that might be the best option since I don't want The bloatware either.
$20 donation to the first dev that makes a stock debloated KitKat!
muffinflesh said:
Yeah that might be the best option since I don't want The bloatware either.
$20 donation to the first dev that makes a stock debloated KitKat!
Click to expand...
Click to collapse
you're a generous man!
muffinflesh said:
Yeah that might be the best option since I don't want The bloatware either.
$20 donation to the first dev that makes a stock debloated KitKat!
Click to expand...
Click to collapse
I'll throw in $5!
Sent from my Nexus 7 using Tapatalk
Ghstudent said:
I'll throw in $5!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
the dev support here is practically dead now, we need to contact a dev from another forum to help us, im sure we could get it to happen if we start a decent bounty.
I've tried this two times and both I had the same result. I downgraded back to 4.2.2 with the D80110g_00.kdz for the tmobile g2. Then I rerooted it and added philz touch recovery. I flashed with the kitkat baseband in the cloudystock 1.1 fourm, then the rom with the patched 801 kernel after. Everything boot's up ok, and the phone works. But when I turn off the screen and back on its all grayed out with yellow lines. I have the reboot the phone for the screen to show up again. Can someone tell me what I am doing wrong?
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
JPrinceStar said:
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
Click to expand...
Click to collapse
baseband stays the same when flashing other roms. Pretty sure the rom zips don't touch baseband unless specified otherwise. Glad it worked for ya btw
Sent from my LG-D801 using xda app-developers app
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
JPrinceStar said:
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
Click to expand...
Click to collapse
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
v2.2v said:
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
batmanonastick said:
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
Click to expand...
Click to collapse
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Did anyone out there figure this out?
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
I think you hit the nail on the head with G build comment. I got my phone about a month ago from TMO and it came pre-installed. I wonder if something in the actual hardware is ever so slightly different with the latest G2s...
I flashed with the C build and it didn't fix it also, guess I'll stay on 4.2.2 till there is a official kitkat root.
Anyone around in this thread with the line problem willing to test a kernel?
mackster248 said:
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
Click to expand...
Click to collapse
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
sam298 said:
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
Click to expand...
Click to collapse
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
v2.2v said:
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
KennyJive said:
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Click to expand...
Click to collapse
JPrinceStar said:
Did anyone out there figure this out?
Click to expand...
Click to collapse
SeVIIn said:
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
Click to expand...
Click to collapse
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
dr87 said:
Anyone around in this thread with the line problem willing to test a kernel?
Click to expand...
Click to collapse
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
mackster248 said:
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
Click to expand...
Click to collapse
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
frettfreak said:
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
Click to expand...
Click to collapse
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
yeah it did ship with KK. pretty sure i have seen the thread regarding the autorec app. But will let you know! Thanks!
mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
Mackster I'm on 4.2.2 which is rooted, is there anyway I could use a custom kitkat rom without getting the white lines? I dont want to keep downgrading everytime it happens.
I posted the same thread a week ago and got no help. My moto x has a problem that whatever rom i flash it just stays open for a few minutes then restarts so it's unusable. Please any suggestion is needed as this is my daily driver
Philo0o said:
I posted the same thread a week ago and got no help. My moto x has a problem that whatever rom i flash it just stays open for a few minutes then restarts so it's unusable. Please any suggestion is needed as this is my daily driver
Click to expand...
Click to collapse
What do you mean by it just stays open. Do you mean it never boots? Like a bootloop? If so, search 7.0 ROMs bootloop, you'll find the solution, tons of threads on the help and q&a here. But if you don't mean what I just explained then could you clarify?
Sorry for not being clear, i dont think it is bootloop. It boots into the rom no issues and i can use it normally and doesn't restart till a few minutes no matter what rom i flash.
Philo0o said:
Sorry for not being clear, i dont think it is bootloop. It boots into the rom no issues and i can use it normally and doesn't restart till a few minutes no matter what rom i flash.
Click to expand...
Click to collapse
If I were you I would flash back to stock and make sure you you don't have a hardware problem, If nothing else it's a chance to start over. I haven't gone to custom roms for these reasons, mine is my daily driver to and I can't afford to get caught without it.
Philo0o said:
Sorry for not being clear, i dont think it is bootloop. It boots into the rom no issues and i can use it normally and doesn't restart till a few minutes no matter what rom i flash.
Click to expand...
Click to collapse
No worries. Yeah I don't know what the issue could be, could be a ROM issue, it's weird though, but like the poster above me, it could be hardware failure and flashing stock would be a good way to find out.
I would love to go back to stock but how? All the tutorials are very hard for me to follow can you guide me to an easy one or tell me how?
Philo0o said:
I would love to go back to stock but how? All the tutorials are very hard for me to follow can you guide me to an easy one or tell me how?
Click to expand...
Click to collapse
I agree that they are a little hard to follow, I looked at them myself and it looks like the quickest way would be to go back to 6.0 and upgrade back to 7. But someone else could correct me on that.
For future reference, it's best to always twrp backup your stock rom before doing any kind of major changes especially custom roms. That way you can always fall back to original if something goes wrong.
tbkrazeey said:
I agree that they are a little hard to follow, I looked at them myself and it looks like the quickest way would be to go back to 6.0 and upgrade back to 7. But someone else could correct me on that.
For future reference, it's best to always twrp backup your stock rom before doing any kind of major changes especially custom roms. That way you can always fall back to original if something goes wrong.
Click to expand...
Click to collapse
I would go back to stock 6.0, if he hasn't upgraded to 7.0, I'll do some digging, find good guides, and post them here in a bit @Philo0o!
Yeh before i started flashing roms i was on stock 6.0, thank you so much
Spencervb256 said:
I would go back to stock 6.0, if he hasn't upgraded to 7.0, I'll do some digging, find good guides, and post them here in a bit @Philo0o!
Click to expand...
Click to collapse
I think I might also do a twrp backup of my 7.0 and make it public, but it will take me a couple of days before I can factory reset. There doesn't seem to be any stock 7.0 backups around on xda.
Philo0o said:
Yeh before i started flashing roms i was on stock 6.0, thank you so much
Click to expand...
Click to collapse
That's good news actually, there's a lot more stuff around for 6.0.
Philo0o said:
Yeh before i started flashing roms i was on stock 6.0, thank you so much
Click to expand...
Click to collapse
Alright if you wanna go the custom ROM route, don't update to stock 7.0, not many custom ROMs work with it's new firmware. I'll get you a guide to go back to stock 6.0 then!
Edit: Alright @Philo0o, here's a good page with all the firmware links for your phone, and the commands to flash the firmware are there for you. Let me know if you have any questions about that.
Also, when your ROMs aren't working, what are you doing to try again? what I mean is you could try a full data format in twrp. Not just a wipe of data, system, etc.. A full format isn't quite like going back to stock, but it may help if there are leftovers somewhere causing issues if that makes sense.
so if you wanna try a full format, backup your internal storage to a computer, or to an sd card, and then format, and then you will have a clean slate, move what you need back over to your phone and voila!
Ill look through that tutorial, and whenever i flash a rom i do a full a wipe
Philo0o said:
Ill look through that tutorial, and whenever i flash a rom i do a full a wipe
Click to expand...
Click to collapse
Alright, then yeah look through that tutorial. If the issue isn't there on stock, but is on custom ROMs, try asking in those threads