This has been a giant pain in the donkey. My wife has upgraded to GS5, so I took her old GS4 and decided to update to KitKat. I flashed a completely stock Samsung 4.4.2 ROM through ODIN. Since then I have not been able to turn on WiFi. The little thumb slider jumps back as soon as I try to enable it.
I've searched the web, and a few people reported this issue, but so far none of the remedies have worked.
Anyone know of a fix?
Reflash the firmware
Sent from my SGH-M919 using Tapatalk
serio22 said:
Reflash the firmware
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Tried that multiple times. No go.
The firmware I was using is from Fenny's KK thread:
[ROM][STOCK][4.4.2][TMO Base][[ODEX]/[DEODEX+DEBLOAT-v1.3]]KitKat 3-29-2014
The one at the bottom of the OP, rebuilt, stock, with bootloader.
Fenny's rebuilt COMPLETELY STOCK ODIN compatible firmware that actually works, lol
Flashing it again now, for sh..ts and giggles...
UPDATE: Reflashing for sh..ts and giggles actually worked. Problem solved, not sure why or how.
6uPMAH said:
Tried that multiple times. No go.
The firmware I was using is from Fenny's KK thread:
[ROM][STOCK][4.4.2][TMO Base][[ODEX]/[DEODEX+DEBLOAT-v1.3]]KitKat 3-29-2014
The one at the bottom of the OP, rebuilt, stock, with bootloader.
Fenny's rebuilt COMPLETELY STOCK ODIN compatible firmware that actually works, lol
Flashing it again now, for sh..ts and giggles...
UPDATE: Reflashing for sh..ts and giggles actually worked. Problem solved, not sure why or how.
Click to expand...
Click to collapse
I have same issue , both bluetooth and wifi not working. How you make it work, can you explain little bit more please?
If you flashed via odin , did you try to root it again??
Sent from my GT-N8013 using XDA Premium 4 mobile app
Well, after flashing the stock KitKat ODIN twice, and no WiFi, I decided to go back to Jelly 4.3, since everything was working there. Unfortunately, flashing the KiKat odin image replaces the bootloader, so technically speaking there's no going back, and I knew that. Since I had nothing to lose, I went ahead with it. As expected, Jelly did not boot, it got stuck at the T-Mo logo animation. After about 10 minutes of looking at the logo, I pulled the battery. Then, for sh..ts a giggles, I decided to reflash the KitKat for the 3rd time, and voila, WiFi started working.
I don't know if trying to flash Jelly had anything to do with it, or if it was a coincidence, and the 3rd time flashing KitKat was the charm, but that's how I got it working for me.
6uPMAH said:
Well, after flashing the stock KitKat ODIN twice, and no WiFi, I decided to go back to Jelly 4.3, since everything was working there. Unfortunately, flashing the KiKat odin image replaces the bootloader, so technically speaking there's no going back, and I knew that. Since I had nothing to lose, I went ahead with it. As expected, Jelly did not boot, it got stuck at the T-Mo logo animation. After about 10 minutes of looking at the logo, I pulled the battery. Then, for sh..ts a giggles, I decided to reflash the KitKat for the 3rd time, and voila, WiFi started working.
I don't know if trying to flash Jelly had anything to do with it, or if it was a coincidence, and the 3rd time flashing KitKat was the charm, but that's how I got it working for me.
Click to expand...
Click to collapse
I guess you use fennys tar , didnt you ??
Sent from my SGH-M919 using XDA Premium 4 mobile app
Yes, I used Fenny's ODIN file. I have a link to it in the OP.
Re-flashing Fenny's file in Odin works.
Related
I've rooted my S3 once so far, flashed a few CM mods n' ROM's and such, but my phone crapped out and I had to flash back to stock ICS. Since then, I haven't been able to root, flash CWM, or anything. All I can do with ODIN is flash stock. Everything else I flash soft-bricks my phone, or on start-up, android.process.acore and touchwiz.home crash repeatedly. After that, I factory restore through stock recovery and all works. Why can't I root? I've tried everything, including the no flash trip way. I've tried several guides, including the one that I first rooted with. Anyone have the same issues at some point in time?
powerfries said:
I've rooted my S3 once so far, flashed a few CM mods n' ROM's and such, but my phone crapped out and I had to flash back to stock ICS. Since then, I haven't been able to root, flash CWM, or anything. All I can do with ODIN is flash stock. Everything else I flash soft-bricks my phone, or on start-up, android.process.acore and touchwiz.home crash repeatedly. After that, I factory restore through stock recovery and all works. Why can't I root? I've tried everything, including the no flash trip way. I've tried several guides, including the one that I first rooted with. Anyone have the same issues at some point in time?
Click to expand...
Click to collapse
Sounds like you need to factory reset after you flash the stock root.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
abteer said:
Sounds like you need to factory reset after you flash the stock root.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Will try. Hope it works.
Found out that the drivers weren't installed on my laptop. Installed those and the S3 version of Odin and flashed the rooted stock 4.1.1. Thanks for the help.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I'm fairly new to custom roms, but I'm fairly comfortable using Odin and CWM. I think I got stuck in a bad spot and would like some help.
I had a stock 4.1.2 L900 (with root access) last night. Decided to install the 4.3 OTA update via stock recovery, and everything booted into 4.3 just fine. Had an issue where my wifi wouldn't turn on at all. I decided to reroot on 4.3 via Odin, which did not fix the issue.
Then I installed CWM 6.0.1.4 using Odin and tried a few roms to see if they would fix the wifi. I installed the Illusion Rom (http://forum.xda-developers.com/showthread.php?t=2361476) and got stuck at boot animation. I then tried a few other ROMs, and even the 4.3 OTA update again, and get stuck at "Error 7", which from my understanding means I'm trying to install on the wrong device.
So, now I have CWM, a ROM that gets stuck at boot animation, and I can't install another ROM. Can anyone help me on where to go from here?
Use Odin to return to MK4 stock with the MD5 file.
Sent from my SPH-L900 using xda app-developers app
ecs87 said:
Use Odin to return to MK4 stock with the MD5 file.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help! Used Odin after a little playing around to get the .md5 extension.
Well I give up... I have finally done something that I can not fix. I can normally google and find my own answers and I never have to ask anyone but this time is different.
I have the I317 Note 2, Everything was fine, I was running a stock rom earlier this week and the phone started acting funny. So I though screw it, Ill just go back to stock. So i downloaded.KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar and used Odin to flash the stock firmware. I DID do a full wipe before I went back to stock. It worked fine for 2 days. It kept wanting to download an update. So it did. When it restarted from the update that the phone downloaded it got stuck on the Samsung screen.
I thought no big deal, I will just reflash the stock firmware and start again... FAIL same thing happened. It wont get past the Samsung screen even after leaving it on that screen for a hour. So then I tried to get into recovery... it wont let me.Then I reinstalled the stock rom and waited for boot, then I flashed CWM and tried to get in to recovery that way. No luck.
I feel like I need to do a wipe and start all over but I cant figure out how to do a full wipe without recovery. There has got to be something easy that I am missing but I cant figure it out. I will keep on searching with hope that someone tells me what I am doing wrong or what to do.
THANKS
If its still able to go into download mode and odin recognizes the device your good just be patient and download the correct firmware.
Sent from my SAMSUNG-SGH-I317 using xda premium
There are some issues with the OTA update from LJ2 to MH3, which it appears you still have sitting on your phone. You can try booting recovery and clearing cache - that should get rid of the OTA file.
The thread below has some information on how to update from LJ2 up through MH3 and then MK6. It's intended for those who already have the MK6 bootloader - if you don't already have that or want that, you'll want to stop at MH3 and consider your options.
http://forum.xda-developers.com/showthread.php?t=2618447
Do you know did I use the correct firmware? I have had to run Odin a couple of times before but its a no go this time... I can not get into recovery. Even if I run Odin now with TWRP and restart it still wont let me into recovery... Can I use Odin to to a full wipe?
Were you on 4.3 previously? Via OTA?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
yes I did upgrade to 4.3 when it came available then I went to a custom rom. Then full wiped and downloaded what I thought was a stock rom and here I am.
Are you saying I need to download the 4.3 stock firmware and that is my issue. What i downloaded was from September 2013
For a (hopefully) quick solution, see post #2 here, specifically the param/tz file:
http://forum.xda-developers.com/showthread.php?t=2618447
That should get your access to recovery back and allow the mh3 ota to complete.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Trust in Odin it never fails.
Sent from my SAMSUNG-SGH-I317 using xda premium
Zen Arcade said:
For a (hopefully) quick solution, see post #2 here, specifically the param/tz file:
http://forum.xda-developers.com/showthread.php?t=2618447
That should get your access to recovery back and allow the mh3 ota to complete.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
WOW that worked!! I just got my phone into Recovery for the first time in over 24hrs now! I did a full wipe and now I am going to try and reinstall the factory rom that I have. Unless you tell me something different...
Thank you very much, I dont understand it but so happy to have a different screen!
Which factory rom? Where are you ultimately looking to get to?
100% back up and running! Thank you again
Zen Arcade said:
Which factory rom? Where are you ultimately looking to get to?
Click to expand...
Click to collapse
One that would work.... LOL I really dont have a preference other then I did not care for 4.3 I ended up with 4.1.1 and I couldn't be more happy. If they ever get 4.4 I would try that.
Its funny 4yrs ago I had the Sprint Evo. I changed roms more often then I changed shirts it seamed. I never had the issues or anything like what I ran into yesterday. I was so careless just trying every rom that was released. Because of that I will always remember the EVO as my favorite phone.
Those were simpler times...
I assume you want root and know how to get it.
Since you have the mk6 bootloader you will need to avoid odin flashing any packages that contain bootloaders in the future. See my mk6 thread for details.
If you want to get to 4.1.2 there are rooted cwm packages for ma4, mc3, and mh3 available. Wherever you end up, I recommend freezing the AT&T Software Update apk from within Titanium Backup or equivalent to ensure that you don't get a forced ota update at some point in the future.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Hi xda, I hope your Friday is going well.
EDIT: My calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody? I don't even hear a dial tone if I am the one dialing out, the call still goes through though.
Everything below was my original post which has been resolved, didn't want to start a new thread though.
-----------------------------------------------------------------------------------------
TL;DR: My T-Mobile Samsung Galaxy S 4 (SGH-M919) is unable to boot stock rom, and I am unable to enter recovery. I get seandroid messages trying to do either. Fortunately, the phone can enter download mode. What do I need to do or flash to get this phone booting again? Thank you in advance for taking the time to read and help out.
Below is the long story with details:
1. The phone was given to me running stock Android/TouchWiz. Unfortunately, I do not know what version but I assume it was whatever was the latest version as of late April.
2. I rooted the phone using Odin and CF Auto Root.
3. I created a backup of this newly rooted stock rom.
4. I flashed Cyanogenmod 11
5. After a while I discovered that I could answer calls but I could not hear nor be heard during the call.
6. I restored to the stock rom using the backup I made in step 3.
7. The calling issue continued, so I figured I would just unroot and go back to like-new factory settings. This way I could take the phone in to be repaired or whatever.
8. Following this thread: http://forum.xda-developers.com/showthread.php?t=2336392, I attempted to flash k0nane's UVUAMDL Official Tar
9. Odin got stuck connecting to my device, I believe it was because I did not run Odin as admin. I pulled the battery and repeated this step while running Odin as admin.
10. The flash was successful, however during the phone's first boot it got stuck on the T-Mobile splash screen for about 30 minutes or so. I pulled the battery again.
11. Anytime I put the battery back in the phone, it will attempt to boot and hang at the T-Mobile screen, I believe this is a boot loop?
Looking online, people suggest going into recovery and wiping but I cannot enter recovery. I just get the seandroid not enforcing messages. I'm very hesitant to keep looking through the forums and trying things because I feel like I'm on the edge of bricking the phone if I haven't already.
I don't think the flash was successful because it wouldn't give you those messages, and you would need to flash either 4.3 or 4.4.2 not 4.2.2 (MDL) Try flashing a newer firmware version.. If it was updated to the newest then I would try 4.4.2
Sent from my SGH-M919 using Tapatalk
serio22 said:
I don't think the flash was successful because it wouldn't give you those messages, and you would need to flash either 4.3 or 4.4.2 not 4.2.2 (MDL) Try flashing a newer firmware version.. If it was updated to the newest then I would try 4.4.2
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Ok so I flashed the wrong rom then. I hate to ask but where could I find a 4.4.2 stock rom? I just found a rom I believe will work but the file is titled "M919UVUFNB4_M919TMBFNB4_TMB" not sure if this is 4.4.2 or newer?
You download the stock 4.4.2 ROM from sammobile:
http://www.sammobile.com/firmwares/
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
You download the stock 4.4.2 ROM from sammobile:
[link removed]
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is where I obtained the rom above that I wasn't sure was the newest.
I flashed this rom and everything worked, thank you both.
Any ideas on what happened with the phone call issue? My friend that gave me the phone said it was working just fine when she had it, so I assume somehow the rooting or CM11 screwed something up? Weirdly, calling through WiFi works just fine.
THVRSDAY said:
This is where I obtained the rom above that I wasn't sure was the newest.
I flashed this rom and everything worked, thank you both.
Any ideas on what happened with the phone call issue? My friend that gave me the phone said it was working just fine when she had it, so I assume somehow the rooting or CM11 screwed something up? Weirdly, calling through WiFi works just fine.
Click to expand...
Click to collapse
The only thing that can foul up your phone like that would be a bad cm flash or preflash, it's super important to read and read again, check the thread for support from members and resolutions to problems before you consider the build for your phone. Ask questions and double check everything before you take the plunge.
I assume that the calling problem is fixed, a corrupt modem may cause that and re flashing the modem will correct this.
Pp.
sent from my bluetooth controlled toaster that also takes pictures.
PanchoPlanet said:
The only thing that can foul up your phone like that would be a bad cm flash or preflash, it's super important to read and read again, check the thread for support from members and resolutions to problems before you consider the build for your phone. Ask questions and double check everything before you take the plunge.
I assume that the calling problem is fixed, a corrupt modem may cause that and re flashing the modem will correct this.
Pp.
sent from my bluetooth controlled toaster that also takes pictures.
Click to expand...
Click to collapse
The calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody?
THVRSDAY said:
The calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody?
Click to expand...
Click to collapse
Did you flash the NB4 firmware twice? Firmware, not modem
Sent from my SGH-M919 using Tapatalk
serio22 said:
Did you flash the NB4 firmware twice? Firmware, not modem
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
No, I only flashed the NB4 modem bin found here: http://forum.xda-developers.com/showthread.php?t=2678774. I need to flash the whole NB4 tar twice as well?
THVRSDAY said:
No, I only flashed the NB4 modem bin found here: http://forum.xda-developers.com/showthread.php?t=2678774. I need to flash the whole NB4 tar twice as well?
Click to expand...
Click to collapse
Well modem didn't work so try the firmware
Sent from my SGH-M919 using Tapatalk
serio22 said:
Well modem didn't work so try the firmware
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I flashed the NB4 tar from sammobile twice, calls still not working. I feel like I'm not flashing the correct thing or something.
Using the Android System Info app, every entry has something in it except for Radio. It just says "Radio: unknown". Does this have anything to do with anything?
THVRSDAY said:
I flashed the NB4 tar from sammobile twice, calls still not working. I feel like I'm not flashing the correct thing or something.
Using the Android System Info app, every entry has something in it except for Radio. It just says "Radio: unknown". Does this have anything to do with anything?
Click to expand...
Click to collapse
That is a problem.. How did you get this device?
Sent from my SGH-M919 using Tapatalk
serio22 said:
That is a problem.. How did you get this device?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
My friend gave the phone to me. She got an S5 and didn't want to bother with selling this S4 so she just gave it to me. It was completely pure and stock, with calls working. Something screwed up during the CM11 flash I guess.
WiFi calls still work, everything works except calls.
Maybe I'm doing something wrong? I flashed the sammobile NB4 tar twice via PDA in Odin as usual. For the modem, I flashed the modem bin via Phone in Odin twice. Thank you for your help, by the way.
New term for CM, "complicated maneuver" ,.
Reflashing firmware may do it. Can't hurt either.
Pp.
Sent from my SGH-M919 using XDA Premium 4 mobile app
THVRSDAY said:
My friend gave the phone to me. She got an S5 and didn't want to bother with selling this S4 so she just gave it to me. It was completely pure and stock, with calls working. Something screwed up during the CM11 flash I guess.
WiFi calls still work, everything works except calls.
Maybe I'm doing something wrong? I flashed the sammobile NB4 tar twice via PDA in Odin as usual. For the modem, I flashed the modem bin via Phone in Odin twice. Thank you for your help, by the way.
Click to expand...
Click to collapse
I think something definitely went wrong.. Try flashing this firmware, it flashes better for most people http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip after that, factory reset and if that still doesn't work then you have a bigger problem.. Good luck!
Sent from my SGH-M919 using Tapatalk
serio22 said:
I think something definitely went wrong.. Try flashing this firmware, it flashes better for most people http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip after that, factory reset and if that still doesn't work then you have a bigger problem.. Good luck!
Click to expand...
Click to collapse
I flashed both Fenny's firmware and a baseband he also provided. Did both twice, and calls are still not working.
I was doing some research on this whole "Radio: Unknown" thing and I started seeing threads talking about flashes corrupting the phone's EFS partition. I never made a backup of mine, so I have nothing to restore to. Is it possible that I could use someone else's EFS backup and then use it to restore my phone's EFS partition? Does it work like that?
THVRSDAY said:
I flashed both Fenny's firmware and a baseband he also provided. Did both twice, and calls are still not working.
I was doing some research on this whole "Radio: Unknown" thing and I started seeing threads talking about flashes corrupting the phone's EFS partition. I never made a backup of mine, so I have nothing to restore to. Is it possible that I could use someone else's EFS backup and then use it to restore my phone's EFS partition? Does it work like that?
Click to expand...
Click to collapse
No it will not work, this is device specific afaik.. Like I said earlier, I recommend you call T-Mobile for a replacement
Sent from my SGH-M919 using Tapatalk
Flashing modems and such with a custom rom installed often fails. Did you try doing a restore to full stock using Odin?
It sounds like the phoen has Android 4.4 on it already so you will need to flash the full 4.4 package (can't go back to 4.3 or 4.2)
Try and, boot hte phoen without modifying it, and see if calls work then.
The EFS thing is about the IMEI number. Does your device show an IMEI number in settings? If it does, your EFS isn't the problem. If it doesn't....well then yeah. Problem is pretty much narrowed down.
Skipjacks said:
Flashing modems and such with a custom rom installed often fails. Did you try doing a restore to full stock using Odin?
It sounds like the phoen has Android 4.4 on it already so you will need to flash the full 4.4 package (can't go back to 4.3 or 4.2)
Try and, boot hte phoen without modifying it, and see if calls work then.
The EFS thing is about the IMEI number. Does your device show an IMEI number in settings? If it does, your EFS isn't the problem. If it doesn't....well then yeah. Problem is pretty much narrowed down.
Click to expand...
Click to collapse
I have restored the phone to full stock and have been using it that way since I started this thread. Everything is just like fresh from the factory (except for the knox counter being tripped obviously). Calls still didn't work. An IMEI number still shows up the phone's settings. Using WiFi calling hasn't been that bad at all, but I'm screwed in the case of a real emergency with this thing.
So usually after letting my phone sit for a while, I go to use it and the screen doesn't come on. Usually when I'm using my hotspot. I've tried different roms, kernels, etc. Can't figure it out. It just stays black until I pull the battery and restart it. Anyone know of a fix?
Bump
Cant seem to find where i read it but if i recall correctly thats a problem with kt kernel.....Ive occasionally had that same issue. Recently flashed a new rom and it must play nicer with the kernel because ive not had that issue. BTW im on Hyperdrive rom
I'm just on a stock 4.4.4 rom
Anybody?
Have you flashing to stock with Odin? Is the phone on but just doesn't respond or does it shut off?
It stays on, usually happens during my over night charging. Haven't been back up stock with Odin.
Nickdroid86 said:
Haven't been back up stock with Odin.
Click to expand...
Click to collapse
What does this mean exactly?
No clue what that was suppose to say, no I haven't odin'd lol.
You may need to odin your firmware whatever it is, if you want to stay stock ShinySide has links in the general section.
Pp.
I'm running the stock rom currently, just rooted.
Nickdroid86 said:
I'm running the stock rom currently, just rooted.
Click to expand...
Click to collapse
ROM is not enough, you should flash the full firmware if you keep having this issue
Sent from my SGH-T999 using Tapatalk