Database Users

Slimbean 4.2.2 Build - media issues

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

[Q] Phone will not start after first restart from a fresh flash

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.

Back to stock rom, hanging when placing call, no sound etc.

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!

[Help!] N910T3 Strange Crashing/Bootloop - Crashes even while in Recovery

Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).

[G900F][RR7.0.2|Pie]Sudden issue with Custom Kernels

Hello together,
I'm using official RR ROM 7.0.2 on my G900F, until recently with latest tuned kernel. I suddenly got some random freezes with reboots without knowing the reason. Then after some crashes it resulted in a bootloop, meaning that the RR bootscreen is loading forever (already tested for hours).
Flashing RR ROM again fixed the issue completely, but when I flash tuned kernel again I immediately end in bootloop. Flashing boot.img of RR ROM once again fixes the problem. Then I tried Intelli-Kernel and it boots, however the first unlock screen is very laggy, system ui takes long time to load after unlock (after that it works normal) and I get here and then sudden reboots. After some crashes/reboots I end up with bootloop with Intelli-Kernel.
Once again: flashing boot.img of RR fixes all the problems.
It's unlikely that the kernels itself are at fault, as they are working for many others and also worked for my device until recently.
So why am I unable to use custom kernels suddenly and how can I fix it?
I'm grateful for any hints you can give to pinpoint the reason. I already asked in the kernel Telegram group but sadly they weren't able to help me.
- I'm clearing dalvik/cache every time,
- tried TWRP repair feature for /data partition
- and as far as I can say I removed all remands of boeffla config app, but even if there are some they should load after system boot so obviously kernel settings aren't applied when I stuck on boot screen.
I don't overclock but for the same reason it shouldn't matter even if I do.
If possible, I would like to avoid a full wipe.
Thanks in advance.

Have you tried backing up your entire phone, wiping and installing RR, letting it boot etc before rebooting to recovery and installing a custom kernel again? If that fails, then either the version of RR you are using is incompatible, or you have some sort of hardware failure somewhere.