Hi all,
I recently installed the newest build of Slimbean. I am having a few issues: I am unable to play any media... Music, videos (youtube). My phone app does not work. I cannot receive nor send any calls. And my phone produces no sounds at all.
I tried installing build 7 to see if it was an issue with the build I was using... didn't help.
Internet and wifi work without any problems.
Galaxy S4 i337m
Baseband: I337MUMUAMDL
Version: Slim-4.2.2.build.7-OFFICIAL
Build #: slim_jfltecan-userdebug 4.2.2 JDQ39E eng.blk_jack.20130706.15730 test-keys
Any ideas?
Thanks in advance
Update: Any ROM I install... Phone and sounds do not work.
Talabis said:
Update: Any ROM I install... Phone and sounds do not work.
Click to expand...
Click to collapse
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
jd1639 said:
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
Click to expand...
Click to collapse
I did just that... But it's a bit of a story.
I had just fixed another problem I was having yesterday. Was getting stuck at the S4 splash screen right after powering on the phone. The problem was caused by TWRP 2.6 and formatting /data partition. Long story short, I installed CWM and used it to do a full wipe/format of partitions and then was able to install ROMs, restore backups without issue.
So today, since everything was working, I decided to flash a new custom ROM (which I installed) and the MG1 radio. Wasn't having any luck with the radio. Finally, I was able to flash a radio via mobile odin, but then I soft bricked my phone. Got stuck at the S4 splash screen (same issue I had yesterday, but this time, a different cause). So was troubleshooting it all day. Tried to go back to stock, no luck. Tried to restore the stock backup I had, no luck. Only thing I could do was install custom ROMs at this point to get into my phone (i.e. Slimbean, FoxHound, etc...). But, at this point, although I could boot into Android, I had no sound at all and couldn't play video. So after hours of trial and error, I installed CWM again (replacing TWRP 2.5.0.2), did a full wipe/format and tried to install a stock ROM. No luck. Still was hanging at the S4 splash screen. Then I tried to install this ROM again which I had luck with in the past; |ROM| |★VLUAMG1★| |CANADIAN||i337M||STOCK||ROOTED||July.26.13|. But his instructions said to install a wifi fix or fear soft bricking my phone. So I installed the wifi fix, but selected the wrong file (I know, stupid. Done a lot of stupid **** in the past couple days with this phone). Now, after the phone rebooted, I would see the S4 splash screen for a split second, and it would auto load into download (odin) mode. Couldn't get into recovery at all. So then I decided to flash one of the stock ROMs I tried earlier that didn't work, but this time, SUCCESS!!!!! Phone was booting and all sounds worked. I could make/receive phone calls as well... Everything seems to be working fine now. I find it funny that flashing a wifi fix that I shouldn't have seems to have fixed my issue in a sense. Since it allowed me to successfully flash a stock ROM. So I am making a backup of the stock ROM and will decide what I'm going to do from here.
Holy goalie!!! It's been a very vexing couple of days.
Nice that you got it all worked out, I've found out that if your "status" is custom, it will sometimes give you problems when flashing a "stock" rom via odin.
So what I always do when reverting back to the stock rom, I use triangle away to clear the flash count and make my phone back to "Official". If you want the steps to do this, let me know, it's not hard, but there are crucial steps to get this right!
JP
Related
Just got a brand new i9505 and the Wi-Fi won't turn on.
When I hit the Wi-Fi toggle it goes on for 1 sec then back off. I have tried a factory reset etc but just can't turn it on. I can't believe it's actually faulty. This is my 2nd faulty S4 out of the box. I brought a i9500 about a month ago and it keeps freezing & rebooting after a minute of use. Unfortunately I can't send that one back as it has a custom Rom & there is no way to reset the counter. I gave up on it and through it in the draw.
I decided to get a new one but went with the i9505 this time. How can I have so much bad luck. Is the S4 that unreliable?
KTM690 said:
Just got a brand new i9505 and the Wi-Fi won't turn on.
When I hit the Wi-Fi toggle it goes on for 1 sec then back off. I have tried a factory reset etc but just can't turn it on. I can't believe it's actually faulty. This is my 2nd faulty S4 out of the box. I brought a i9500 about a month ago and it keeps freezing & rebooting after a minute of use. Unfortunately I can't send that one back as it has a custom Rom & there is no way to reset the counter. I gave up on it and through it in the draw.
I decided to get a new one but went with the i9505 this time. How can I have so much bad luck. Is the S4 that unreliable?
Click to expand...
Click to collapse
I had the same problem with a custom rom wifi won't turn. All i did was change the kernel.
Hope this will solve your problem.
KTM690 said:
Just got a brand new i9505 and the Wi-Fi won't turn on.
When I hit the Wi-Fi toggle it goes on for 1 sec then back off. I have tried a factory reset etc but just can't turn it on. I can't believe it's actually faulty. This is my 2nd faulty S4 out of the box. I brought a i9500 about a month ago and it keeps freezing & rebooting after a minute of use. Unfortunately I can't send that one back as it has a custom Rom & there is no way to reset the counter. I gave up on it and through it in the draw.
I decided to get a new one but went with the i9505 this time. How can I have so much bad luck. Is the S4 that unreliable?
Click to expand...
Click to collapse
Instead of clicking the wifi toggle, why not try to go into settings and mobile networks
and turn it on there.
Good luck!
daveve said:
I had the same problem with a custom rom wifi won't turn. All i did was change the kernel.
Hope this will solve your problem.
Click to expand...
Click to collapse
Thanks for the reply daveve.
Im Running the latest Omega ROM. What Kernel did you flash?
KTM690 said:
Thanks for the reply daveve.
Im Running the latest Omega ROM. What Kernel did you flash?
Click to expand...
Click to collapse
I,m using KERNEL][INT'L][AOSP/TW][6/10/2013B] KT-SGS4 - MDM - KTweaker
You can try booting into recovery and clearing the Cache and Dalvik Cache to fix the wifi. It's worked for me and other people on this forum.
i also have the same problem on my S4, basically the wifi wont turn on, i already did flashing firmware, wipe cache and dalvik cache but still the same thing
yeah same here. I've been researchin and flashin almost a month now and nobody seriously nobody could fix this issue. shame. i hate that it happened suddenly and without a warning.
Happened to me also...This is how I fixed it (accidentally of-course ):-
---First mistakenly dirty flashed stock ROM via odin v 10...That was an honest mistake
---Couldn't start my phone due to it...FC messages were appearing again and again...
---went to download mode...directly flashed CF-Auto Root and TWRP from ODIN again...
1) Wiped everything from TWRP
2) Went to download mode and flashed Stock ROM via Odin.
3) WiFi didn't turn on even in Stock ROM (came as a shock to me)
4) went to download mode...directly flashed CF-Auto Root and TWRP from ODIN again
5) Flashed "Doctors-Amputated-V3" and "CWM-Modem-I9500ZCUJOH2_2" via TWRP.
voila !! WiFi working again in the new ROM :laugh:
Hi mate,
Could you please explain what "Doctors-Amputated-V3" is? A custom ROM?
Basically, I have flashed the stock Samsung image and a previous backup, and still have issues having used PryFi. I'm trying to get my WiFi back to stock and probably flash a kernel or revert to whatever is most compatible, so as to stop my device rebooting...
Could you please recommend a kernel or modem to flash, and then the best kernel or modem to flash afterwards, in order for maximum compatibility. My S4 has always been stock rom, just with Root.
Appreciate your time Prateekgupta!
Cheers,
prateekgupta128 said:
Happened to me also...This is how I fixed it (accidentally of-course ):-
---First mistakenly dirty flashed stock ROM via odin v 10...That was an honest mistake
---Couldn't start my phone due to it...FC messages were appearing again and again...
---went to download mode...directly flashed CF-Auto Root and TWRP from ODIN again...
1) Wiped everything from TWRP
2) Went to download mode and flashed Stock ROM via Odin.
3) WiFi didn't turn on even in Stock ROM (came as a shock to me)
4) went to download mode...directly flashed CF-Auto Root and TWRP from ODIN again
5) Flashed "Doctors-Amputated-V3" and "CWM-Modem-I9500ZCUJOH2_2" via TWRP.
voila !! WiFi working again in the new ROM :laugh:
Click to expand...
Click to collapse
flipmode_11 said:
Hi mate,
Could you please explain what "Doctors-Amputated-V3" is? A custom ROM?
Basically, I have flashed the stock Samsung image and a previous backup, and still have issues having used PryFi. I'm trying to get my WiFi back to stock and probably flash a kernel or revert to whatever is most compatible, so as to stop my device rebooting...
Could you please recommend a kernel or modem to flash, and then the best kernel or modem to flash afterwards, in order for maximum compatibility. My S4 has always been stock rom, just with Root.
Appreciate your time Prateekgupta!
Cheers,
Click to expand...
Click to collapse
---Yes its a custom ROM...
---PryFi breaks phone's Wifi every time you use it...I've given up and uninstalled that app....Flash stock rom again through ODIN...
---The process I described didn't solve my problem...My wifi worked only for 20 minutes...After that it went back to grey...
---No software trick can help if your Wifi and Bluetooth both are not working...Its basically the Wifi antenna/IC that needs to be fixed...Its a hardware issue...
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
zuuus said:
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
Click to expand...
Click to collapse
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.
ultramag69 said:
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.
Click to expand...
Click to collapse
Hey mate, last version of firmware was the Stock Telstra SM-N9005 / TEL ROM I found on www . sammobile . com/firmwares/2/
I have tried at least 10 different ROMs with no luck, every single one does the same thing.
I did send it off to Telstra to try for a repair, they sent it back to me unrepaired due to nothing to do with the software but a 1/4mm scratch my keys made in the chrome plastic around the edge with the words "unable to be repaired due to physical damage" with a little sticker pointing to the scratch. ****ing ridiculous if you ask me.
Honestly I don't know all that much to do with the modems and csc's so it might be that causing my problems but I have tried a bunch of different ones without any change.
At my wits end here, phone is just over 30 days old and I can't use the damn thing.
try odin back to stock, then use kies to "emergency firmware restoore" Kies can be a life saver in some situation, make sure you use beta 3 version
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
schmidty455 said:
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
Click to expand...
Click to collapse
Omni clearly states that it is an alpha, so you mileage may vary considerably.
Sounds kernel related. Have you tried just reflashing the kernel and seeing if it'll boot after that. Or trying a different kernel?
Thanks for the reply! I actually just fixed the problem on my own. I used Odin to flash a newer version of TWRP and then flashed omni, and it looks like everything is working just fine. I read a few people saying that they were having issues flashing kit kat roms with older versions of recovery, so I figured it was worth a shot.
Long story short (I can go into more detail if needed):
Had a stock rooted rom with a zv8 radio/modem on sprint. I successfully flashed the Optimus 2.2 rom with the new ZVA (Sprint Spark) modem and everything was fine and dandy and working perfectly for a few hours. Then i was a dummy and restored apps from my previous roms using mybackup and one of those apps was the xposed installer with a few different modules.
Phone froze, rebooted and would no longer attatch to a network. No signal, just a red x. No radios work, not even wifi or bluetooth. If the screen goes blank the phone will freeze and bootcycle. Or if it is on for more then a minute, it will freeze and turn off and get stuck in a bootloop.
Recovery worked. I tried everything. Flashing other roms, with the appropriate radios of course, and restoring my backup with the appropriate radio. Nothing works, and ive had the same issue with each and every rom and radio.
I finally whipped out lgflashtool and returned to stock unrooted to no avail. Same issue, except now my touchscreen is not responsive, which means no adb to reroot and the pc doesn't recognize the phone while booted. Now im aware of a method using Ubuntu to get a custom recovery on these when all else fails, but is it worth my time if there is no fixing my issue?
Also, how much can you do with the lgflashtool? Can i flash different radios or root using it?
Worst case scenario i will take my phone to sprint and get a warranty replacement. The only issue with that is, while the rootchecker in download mode shows "unrooted" , the boot animation on the stock .tot image is an lg one, not the Sprint logo one and i feel like the service person would catch on. Any idea on how to change that as well?
Thanks in advance guys! Im kind of freaking out that im running out of options.
Bump
dantheman9703 said:
Long story short (I can go into more detail if needed):
Had a stock rooted rom with a zv8 radio/modem on sprint. I successfully flashed the Optimus 2.2 rom with the new ZVA (Sprint Spark) modem and everything was fine and dandy and working perfectly for a few hours. Then i was a dummy and restored apps from my previous roms using mybackup and one of those apps was the xposed installer with a few different modules.
Phone froze, rebooted and would no longer attatch to a network. No signal, just a red x. No radios work, not even wifi or bluetooth. If the screen goes blank the phone will freeze and bootcycle. Or if it is on for more then a minute, it will freeze and turn off and get stuck in a bootloop.
Recovery worked. I tried everything. Flashing other roms, with the appropriate radios of course, and restoring my backup with the appropriate radio. Nothing works, and ive had the same issue with each and every rom and radio.
I finally whipped out lgflashtool and returned to stock unrooted to no avail. Same issue, except now my touchscreen is not responsive, which means no adb to reroot and the pc doesn't recognize the phone while booted. Now im aware of a method using Ubuntu to get a custom recovery on these when all else fails, but is it worth my time if there is no fixing my issue?
Also, how much can you do with the lgflashtool? Can i flash different radios or root using it?
Worst case scenario i will take my phone to sprint and get a warranty replacement. The only issue with that is, while the rootchecker in download mode shows "unrooted" , the boot animation on the stock .tot image is an lg one, not the Sprint logo one and i feel like the service person would catch on. Any idea on how to change that as well?
Thanks in advance guys! Im kind of freaking out that im running out of options.
Click to expand...
Click to collapse
try to flash kdz via flash tools
gembo said:
try to flash kdz via flash tools
Click to expand...
Click to collapse
I've done this. But I found one from a new source and I'll try it again. Would I need to flash the radio again? Thank Thank you for the help.
Hi there
I have recently picked up my old S4 since my OPO screen broke. I was annoyed with the buggy CM 12 nightly it was running and tried installing the newest CM 13 nightly. It gave me no signal and I decided to try to revert to stock, following the guide Unroot/Unbrick, Flash official stock firmware on S4. Applying the I9505XXUAMDE_I9505OXXAMD8_NEE 4.2.2 stock rom through ODIN was a breeze but after booting i realized it had no sound.
Also placing or receiving calls makes the phone hang, even occasionally reboot, and sometimes a window with "android.phone.. app" or "process system is not answering" appears. For example also not possible to record video.
I did both factory reset and wipe cache in bootloader, but when wiping cache I get the lying down android with red exclamation mark for a few seconds then reboot.
I then tried to reflash above stock rom with repartition (pit file) and the problem remains.
I dont suppose it is a hardware problem since it started after I flashed new rom. It seems like some audio related software issue that I cant seem to get rid of - can anyone help or should I just give up and get another phone?
Thanks in advance, sorry for the long post
Try flashing a newer ROM.
The guide used is pretty old I guess and should be used only as reference.
What was the initial stock ROM your device had?
Pwnycorn said:
Try flashing a newer ROM.
The guide used is pretty old I guess and should be used only as reference.
What was the initial stock ROM your device had?
Click to expand...
Click to collapse
I already tried rerooting and flashing back to both CM 10.2 and newest CM 13 nightly from philz touch recovery. Both with the same problem when placing or receiving a call. But sound was working..
I don't know the exact stock rom the phone came with but seem to recall it was 4.2.2 as I have installed now.
Is there anything else that can be flashed back to original? I read several posts talking about a modem reflash for fixing audio issues but I suppose the stock rom should contain the modem info already..?
I specifically went for the oldest rom, since the guide said that once stock 4.3 is flashed you cant revert due to new bootloader. And I was hoping to revert to being able to use OTA updates since I plan on gifting the phone to an even more tech illiterate than myself.. Is that going to be a problem if I just flash for example the newest 5.0.1 stock rom?
fiedes said:
I already tried rerooting and flashing back to both CM 10.2 and newest CM 13 nightly from philz touch recovery. Both with the same problem when placing or receiving a call. But sound was working..
I don't know the exact stock rom the phone came with but seem to recall it was 4.2.2 as I have installed now.
Is there anything else that can be flashed back to original? I read several posts talking about a modem reflash for fixing audio issues but I suppose the stock rom should contain the modem info already..?
I specifically went for the oldest rom, since the guide said that once stock 4.3 is flashed you cant revert due to new bootloader. And I was hoping to revert to being able to use OTA updates since I plan on gifting the phone to an even more tech illiterate than myself.. Is that going to be a problem if I just flash for example the newest 5.0.1 stock rom?
Click to expand...
Click to collapse
Downgrading causes problems in the first place, that is why it is recommended to flash the same software as it originally had.
As long as your status says "official" in download mode, you should be able to still get updates. Although who knows for how long.
I also recommend using the latest TWRP recovery. PhilZ and CWM are outdated and can cause problems with newer ROMs.
Pwnycorn said:
Downgrading causes problems in the first place, that is why it is recommended to flash the same software as it originally had.
As long as your status says "official" in download mode, you should be able to still get updates. Although who knows for how long.
I also recommend using the latest TWRP recovery. PhilZ and CWM are outdated and can cause problems with newer ROMs.
Click to expand...
Click to collapse
I will try to install TWRP and the newest stock firmware and see what happens. Thanks
Ok, upgraded to latest stock rom and everything works!
No idea what was wrong specifically though.. Thanks for the help!