I bought a SGS4 about a month and a half ago and I flashed it the moment djrbliss released "loki" for modifying the boot.img files that are found in roms/kernels. I rooted using motochopper, I have the newest version of TeamWin Recovery Project installed, and I'm running SlimBean 4.2.2 (Build 6 "JDQ39E") with the Ktoonsez kernel (linux 3.4.47, built June 6th).
Ever since flashing SlimBean (I kept the stock kernel the first time, never installed custom modules or anything), I have had what appears to be persistent signal loss. I have tried MANY different configurations with my APN settings, Network Modes, Network operators.
I have re-flashed the rom, the kernel, other roms, and other kernels. I also accidentally put my phone into a soft-brick boot-loop a few times and have had to restore from the TWRP Backup(s) I make periodically.
Yes, I did wipe cache, dalvik-cache, data, and system. (and manual format on /system)
Yes, I did search the XDA Developers forums for countless hours, tried many different troubleshooting techniques, but still the weak signal problems persist.
Yes, this is the first thread I've posted on xda-developers.com, cut me a little slack please
Thank you for your patience!
- Justin
Related
Unable to post in developer section, have been using custom roms since February.
Sorry if this is in the wrong section, merge it and delete this paragraph if you must with http://forum.xda-developers.com/showthread.php?t=911364&page=1278
Had wolfbreaks rom running previous to installing FXP030 and unlocking bootloader, had issues with wolfbreaks rom. FXP030 seemed great and worked well, aside from the odd glitch. Had ran it for 2 days. Tried to update to FXP030b to test out new fixes (use the camcorder often) and upon flashing new kernel FTF file, phone booted, wiped cache, factory reset, wiped batt stats, wiped dalvik cache. loaded up the custom zips, for FXP030b + gapps, booted fine, couldn't get wifi working, couldn't connect with 3g. Tried to crash system server inside bad behavior in the dev tools as per instructions from collosus. upon crashing system service, phone hung hard for over 20 mins stayed on same screen, did not boot again till i flashed stock kernel. Not even FXP030 worked at that point. Hope I was not close to bricking my device.
quanium said:
Unable to post in developer section, have been using custom roms since February.
Sorry if this is in the wrong section, merge it and delete this paragraph if you must with http://forum.xda-developers.com/showthread.php?t=911364&page=1278
Had wolfbreaks rom running previous to installing FXP030 and unlocking bootloader, had issues with wolfbreaks rom. FXP030 seemed great and worked well, aside from the odd glitch. Had ran it for 2 days. Tried to update to FXP030b to test out new fixes (use the camcorder often) and upon flashing new kernel FTF file, phone booted, wiped cache, factory reset, wiped batt stats, wiped dalvik cache. loaded up the custom zips, for FXP030b + gapps, booted fine, couldn't get wifi working, couldn't connect with 3g. Tried to crash system server inside bad behavior in the dev tools as per instructions from collosus. upon crashing system service, phone hung hard for over 20 mins stayed on same screen, did not boot again till i flashed stock kernel. Not even FXP030 worked at that point. Hope I was not close to bricking my device.
Click to expand...
Click to collapse
Hi Buddy,
What you should have done when your phone froze after crashing the system server is to have taken your battery out and then just re-booted your phone, all would have been good.
If you are still at the same stage now from when you posted just flash the fxp kernel in the flashtool provided by J, your phone will now boot with FXP030b.
You was never close to bricking your phone so do not worry.
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.
Hi all,
After a looong night flashing and downloading again and again trying different methods, I'm out of ideas.
I have a uk n9005 (btu) that was happily running out of the box 4.3 stock until yesterday night. No root, no flash attempts before.
I started by flashing german 4.4 (dbt) without wiping before (big mistake, maybe) and without pit file and no repartition nor bootloader update checked. The error came out and I flashed again with the pit file. I let the phone reboot, but it didn't go further than the boot animation. I take out the battery and boot in the recovery. That is when I saw the can't mount \data error for the first time.
I tried to wipe, although it was impossible since the data was not mounted. However I could (and still can) wipe cache. I restarted the phone, and again the same situation, stuck in boot animation. From this moment I've tried many things:
- Flashing the bootloader separately and then the rom. no results (data not mounted and stuck in boot animation)
- Flashing custom recovery and after, official cm11 nightly and another cm11 based rom. no results (data not mounted and stuck in boot animation)
- Downgrading to 4.3. Not possible. Thank you Samsung!
- Firmware recovery with kies 3.0. no results since 4.4 has not been released for my region (maybe waiting for if to come out would be a solution)
- Flashing Polish and german (againg) 4.4 with and without pit file. no results (data not mounted and stuck in boot animation)
The only thing I can think of that I haven't tried yet is flashing a custom kernel, but I can't see any advantage in doing that. Next approach is taking it to the technical service to see if they can solve this situation. I'm afraid they're going to ask for almost as much money as a new note 3 costs...
P.D: I know I haven't taken part a lot in this forum, but I've been reading it for years, since I started playing with my SGS back in 2011. This is the first time I'm really lost after spending the night searching the forum (not only the note 3 section). This really pisses me off, with my previous phones I could always find a way to bring them back to life, but with SGS4 and SGN3 things are totally different thanks to samsung. (sorry for this looong post)
Thank you in advance
wrong place, sorry
move to q&a or delete please
Contruk27 said:
Hi all,
After a looong night flashing and downloading again and again trying different methods, I'm out of ideas.
I have a uk n9005 (btu) that was happily running out of the box 4.3 stock until yesterday night. No root, no flash attempts before.
I started by flashing german 4.4 (dbt) without wiping before (big mistake, maybe) and without pit file and no repartition nor bootloader update checked. The error came out and I flashed again with the pit file. I let the phone reboot, but it didn't go further than the boot animation. I take out the battery and boot in the recovery. That is when I saw the can't mount \data error for the first time.
I tried to wipe, although it was impossible since the data was not mounted. However I could (and still can) wipe cache. I restarted the phone, and again the same situation, stuck in boot animation. From this moment I've tried many things:
- Flashing the bootloader separately and then the rom. no results (data not mounted and stuck in boot animation)
- Flashing custom recovery and after, official cm11 nightly and another cm11 based rom. no results (data not mounted and stuck in boot animation)
- Downgrading to 4.3. Not possible. Thank you Samsung!
- Firmware recovery with kies 3.0. no results since 4.4 has not been released for my region (maybe waiting for if to come out would be a solution)
- Flashing Polish and german (againg) 4.4 with and without pit file. no results (data not mounted and stuck in boot animation)
The only thing I can think of that I haven't tried yet is flashing a custom kernel, but I can't see any advantage in doing that. Next approach is taking it to the technical service to see if they can solve this situation. I'm afraid they're going to ask for almost as much money as a new note 3 costs...
P.D: I know I haven't taken part a lot in this forum, but I've been reading it for years, since I started playing with my SGS back in 2011. This is the first time I'm really lost after spending the night searching the forum (not only the note 3 section). This really pisses me off, with my previous phones I could always find a way to bring them back to life, but with SGS4 and SGN3 things are totally different thanks to samsung. (sorry for this looong post)
Thank you in advance
wrong place, sorry
move to q&a or delete please
Click to expand...
Click to collapse
You might also be able to get it working by flashing the sweetrom like people with the HongKong note 3 had to do to go to KK rom...
Worth a shot if you try everything else and aren't getting anywhere but you will need to be rooted to flash a custom rom...
Hi,
coming from samsung stock 4.2.2 I patched my device with autopatcher for obtaining root and flashed cwm 6.0.4.4.
I tried several roms, but I have a strange issue.
After rebooting my device it is showing a random timestamp and a random date. Restarting it several times I have dates in November, January, etc.
Timesync is only functional via ntp (internet time sync).
I tried different custom roms (cm 10.2, cm 11, aosp 4.3). Always the same behaviour.
I had this issue before but suddenly it went away but I didn't know what I have done.
But after installing my device new the problem stays - regardless which custom rom. I admit I have not tried the stock rom again.
Any ideas?
BTW:
I currently made a new backup in twrp. The timestamp of the backup is ok. (I rebooted from cm 10.2.1 directly to recovery). But after boot the timestamp correct timetamp is gone.
Thanks, butch
when using the stock firmware the problem does not exist. Still using the old bootloader without knox.
Does anyone have an idea?
Hello, I have a huge problem with my Tab 4. As you can see in the video, my Tab 4 will not go to the start screen. I have tried booting into recovery mode and tried the options in there. I installed the stock ROM, but it didn't help. Please someone help me:crying:
sly742 said:
Hello, I have a huge problem with my Tab 4. As you can see in the video, my Tab 4 will not go to the start screen. I have tried booting into recovery mode and tried the options in there. I installed the stock ROM, but it didn't help. Please someone help me:crying:
Click to expand...
Click to collapse
Try samsung kies or download stock firmware and flash with odin
I have the exact same thing. I deleted android off of mine because I rooted it. I fd up after i rooted it doing something wrong. now I'm trying to get it to work again. I wiped mine (you may have to also) now I'm trying to find android 5.0.1 to load on it. I need help too. But I know some stuff about our tablet.
T530NU - Bootloop Freeze
Resurrecting this thread after over a year hoping someone is paying attention...
I have the same problem as well. I have downgraded from 5.0.2 to 4.4.2 hoping that would work. I have the exact same issue as seen in the video above. I flashed PACMAN custom ROM and GAPPS 6.0 nano last night and was able to get in and through setup, but the wifi will not work nor does it detect any nearby networks.
Looking for answers here... Corrupted partitions maybe? I have stable stock ROM's
Maybe sideload APK's to evaluate/fix the issue from the ui side - if any apps exist?
megamb11 said:
Resurrecting this thread after over a year hoping someone is paying attention...
I have the same problem as well. I have downgraded from 5.0.2 to 4.4.2 hoping that would work. I have the exact same issue as seen in the video above. I flashed PACMAN custom ROM and GAPPS 6.0 nano last night and was able to get in and through setup, but the wifi will not work nor does it detect any nearby networks.
Looking for answers here... Corrupted partitions maybe? I have stable stock ROM's
Maybe sideload APK's to evaluate/fix the issue from the ui side - if any apps exist?
Click to expand...
Click to collapse
Update:
Been working on this throughout the day. I have CM14.1 installed with GAPPS 7.1.
Ran system, data, and cache partitions through change (ext4 to exFAT to ext4) and repair in TWRP 3.1.0.
I am able to run through the boot up, but now the interface is crashing about 3 minutes in and rebooting with no variances in this process.
Still no wifi and no networks showing where I know they should be...
Corrupt Data and Cache Partitions Cannot be Fixed with e2fsck
Update:
Partition repair, while working, is not fully fixing the cache and data partitions, which I believe to be the issues. I am beginning to learn the Linux environment even more now as I learn how to fix this issue
# e2fsck /dev/block/platform/msm_sdcc.1/by-name/cache is returning a percentage that is non-contiguous for the cache partition
fdisk /dev/block/mmcblk0p24 did not seem to work
This may move beyond just this thread and into its own thread as it involves troubleshooting the Android OS in general.
To any devs out there that may view this, I am looking for some direction on how best to proceed. Next step would be to re-partition manually. If there are additional tools available to be able to further investigate the partitions then I would be happy to know what they are.
Thanks in advance for any help!
Update:
Cache and data do not seem to be the issue...
I am beginning to find a lot more info on this issue and wonder if the OTA update to the tab from KK to LP caused the issues that I am seeing - no wifi or BT. Still no stock firmware bootup though I am able to get in to the interface via custom ROM's.
Now dumping modem, efs, modemst1, modemst2, fsc, fsg, and backup partitions to view information in the files.
Update:
I hate problems that fix themselves!
I pulled APNHLOS, modem, efs, modemst1, modemst2, and boot partitions for further evaluation yesterday using the dd if= of= command - no results yet. However this morning I Odin-flashed stock 4.4.2 KK to see if I could pull something from logcat before it crashed. For whatever reason, I am now running stable stock ROM with TWRP and no SU binary installed - one problem just fixed itself. Still no wifi and BT yet, though.