Database Users

[HELP] Freezes and Reboots w/Custom Kernels

Hi there,
Ok, here is my last try to get a fix before I quit. I have a problem only related with Custom ROMs so I expose it in the Dev zone. Sorry if it is not correct.
For those who haven't follow the Perfect Recovery topic, I have one of the so called X5 Black Sheep. Initially these X5's appeared in Portugal and the synthom was stuck forever on IDEOS screen when enter in CWMv4.0.0.5 from genokolar. Finally stockwell have modified the CWMv4 with the kernel from MIUI and we can now enter in and flash the new Custom ROMs.
The thing is, my X5 keeps freezing and restarting in ALL custom ROMS. I have tried Oxygen, CM7, void and MIUI. ALL with same result. Even the ClockWorkModv4 from stockwell freezes and restarts sometimes when making or restoring backups.
I think it is something related with I/O SDcard as the reboots/freezes happens 90% when making something with it (mounting SDcard in PC through USB, or in Antutu when testing SDcard) but I have tried without SDcard and also with 3 different SDcards. All with same result.
I have absolutely no problem with Official and stock B137 ROM. Only with custom kernels (except SuperBoot from Paul fo Modaco that works 100% stable). Another example is I am absolutely stable with B137 stock but, if I put the boot.img from franciscofranco kernel for void, I can boot but again I have freezes and restarts.
What do you think the problem is? Do I have a faulty X5? Although is strange that with official kernel or SuperBoot everything works stable.
Any help, please?

I have exactly same problem!
I bought a x5 2 days ago. Catched up to the rom scene and tried to root the phone.
The phone was also stuck on ideos logo when trying to boot recovery 4.
Tried the recovery for the black sheeps and worked! Installed the rom and was amazed by the speed and usability.
Downloaded a lot of apps's and it started crashing. So I tried to remove app by app and the problem remains!
The first time it crashed I had problem turning the phone again (even after taking the battery out!).
Now sometimes crashes on standby and turns off.
Most frequently crashes during phone calls.
In one afternoon more then 8 crashes!
Tried to remove the SD card and now i'm waiting to see if the problem is solved.
So the problem is real. I must have a black sheep. And the cure for the black sheep is partially working since it must have some bugs in it..

maxusz, are you portuguese? Because I only have knowledge of Black sheeps in Portugal. At least here in xda never saw anyone complaining from any other country except Portugal, which is odd.
Regarding your problem, it is a bit different than mine. When I flash a custom ROM or put a different boot.img (except SuperBoot), I get freezes and restarts right off the boot. Sometimes I have time to complete a Antutu, but that is rare. Most of the time it hangs within 2 or 3 minutes after booting.
And, as I said, even in stockwell's CWMv4 I have freezes and restarts because it uses MIUI's kernel.
It seems that I have a different hardware from other X5's but... on the other side, I have no issue at all running B136 and B137 ROMs. I really can't understand what is the problem and I am very sad as I bought this model because it was getting a very good development community and now... I'm stuck with stock firmware.

Go to TMN and demand to change the device for a new one.. tell them that it doesn't boot.. if you are in those famous 15days after buy.. if it goes to warrantly you may not have lucky.
Or demand you money and wait for the new remittance of ideos x5, once TMN x5 is out of stock, at least at Lisbon. good luck m8

Been there, done that and I got another black sheep... I am still in that 15 days period although I don' t want to spend my life doing this until I got a normal one.
I would rather prefer to understand and fix whatever is wrong with these X5.
Sent from my u8800 using XDA App

Go there get your money back and wait for brand new X5s in a couple of weeks. Much better than waiting for ever for a working fix which might never happen, since not everyone has the same issue.
best of lucks Royal ;(

If I have to guess - and watching the differences in consistency of the product - I would say there's some difference in HW and thus missing a driver for something. unfortunately, this is just a guess that need proper investigation if this is plausible.

I might do that. I just hope that TMN have stock again very soon.
I am no dev nor programmer but I really like to know the technical difference between these models and the normal ones.

lourenzo said:
If I have to guess - and watching the differences in consistency of the product - I would say there's some difference in HW and thus missing a driver for something. unfortunately, this is just a guess that need proper investigation if this plausible.
Click to expand...
Click to collapse
Anything I can do to check that?

Probably the easiest way to do this is find out why/when it is rebooting... noein already tried to help you, right? try to catch is attention: is examinations must be all done by now
I'm no expert - just guessing...

RoyaL said:
Anything I can do to check that?
Click to expand...
Click to collapse
After a restart, use an app like Root Explorer or ES File Explorer (or adb) to grab the /proc/last_kmsg file and post it here. That should help the devs to find out what is different with your phone.

I am from Portugal!
Bought mine from TMN Aveiro!
Mine also got stuck when installing recovery. I had to try differente boot.img and then the one it worked was the one for the black sheeps

atiatinini said:
After a restart, use an app like Root Explorer or ES File Explorer (or adb) to grab the /proc/last_kmsg file and post it here. That should help the devs to find out what is different with your phone.
Click to expand...
Click to collapse
Before testing I was checking and I can confirm that I do not have any file or folder inside /proc named "last_kmsg".
Any clue?
I was thinking... Could this be caused by I have upgraded to B137SP04 Official ROM and this changes anything in the system that is used by any custom kernels?! Does this makes any sense?
Because the B137SP04 is later than any custom ROMs. For example, void was first created based on FLB (I think) that was based on first B137 ROMs. SP04 came after.
Just a shot in a dark.

nope - I also cheked and couldn't find that file (unless it's hidden).

RoyaL said:
I was thinking... Could this be caused by I have upgraded to B137SP04 Official ROM and this changes anything in the system that is used by any custom kernels?! Does this makes any sense?
Because the B137SP04 is later than any custom ROMs. For example, void was first created based on FLB (I think) that was based on first B137 ROMs. SP04 came after.
Just a shot in a dark.
Click to expand...
Click to collapse
I don't think so... I had the same problem... CWM 4.0. I upgraded from TMN ROM to B137 (Czech Omitel) and afterwords I've instaled MIUI custom ROM (with CWM 3...) and upgraded to CWM 4 after stockwell update.

can't find that file either! did a search of it and it's nowhere to be found!

rimsilva said:
I don't think so... I had the same problem... CWM 4.0. I upgraded from TMN ROM to B137 (Czech Omitel) and afterwords I've instaled MIUI custom ROM (with CWM 3...) and upgraded to CWM 4 after stockwell update.
Click to expand...
Click to collapse
And you have no problem, right?

no problems!

RoyaL said:
Before testing I was checking and I can confirm that I do not have any file or folder inside /proc named "last_kmsg".
Any clue?
Click to expand...
Click to collapse
That's odd... Try to do an adb logcat until your phone restarts and post it here. Or you can do it directly from your phone: install the 'Terminal Emulator' app, open it and enter 'su', and then 'logcat > /data/logcat.txt' commands. Wait until your phone restarts. Then use Root Explorer or ES File Manager to grab that file (/data/logcat.txt) and post it here.

Hmm... This sounds a bit like the issue I am having with custom kernels on my X5, bought in Sweden in April or so.
I tried a couple of overclocked kernels on top of the stock ROM a while back and they all crashed my phone in less than an hour so I gave up on those. I am still on the original ROM (no OTA updates here in Sweden) and have not tried or moved to recovery v4 yet.
Which custom ports and ROMs actually work well on the black sheeps?
Need I say I am little disappointed in Huawei...

Strange problems after insalling a customer ROM

The last time I've updated my SGS1 to ICS, it started after about 1 to 2 weeks, to slow down and it always ended in a bootloop. It just start to restart more and more often. I tried different ROM's, none worked. I tried to flash a Kernel after it starts to reboot - nope. Then I installed the original Samsung ROM, since it works.
Does anyone have any idea why the original ROM does and the costumer ROM does not?
Root? The kernel? Or maybe a hardware problem?
For about 2 years I use customer ROM's and have not had such problems. And you know, it is kind of hard to get back to GB... really...
Thanks for your ideas!

luxamman said:
The last time I've updated my SGS1 to ICS, it started after about 1 to 2 weeks, to slow down and it always ended in a bootloop. It just start to restart more and more often. I tried different ROM's, none worked. I tried to flash a Kernel after it starts to reboot - nope. Then I installed the original Samsung ROM, since it works.
Does anyone have any idea why the original ROM does and the costumer ROM does not?
Root? The kernel? Or maybe a hardware problem?
For about 2 years I use customer ROM's and have not had such problems. And you know, it is kind of hard to get back to GB... really...
Thanks for your ideas!
Click to expand...
Click to collapse
At a guess this is the datadata problem, usually caused when you have more than approx 150 apps installed, do a search for the various solutions

slaphead20 said:
At a guess this is the datadata problem, usually caused when you have more than approx 150 apps installed, do a search for the various solutions
Click to expand...
Click to collapse
I had about 25-35 programms / games installed, less when the problem has started... i had no problem with the "memory full" error

Stable Baseband Firmware
Have you tried to use Odin to flash it with stable Baseband rom like XXJVS for Gingerbread Rom, after that try to Flash the new ICS ROM like The Nyx Rom, cuz it's stable and I'm using their Rom since they start the Beta.

Fastlink85 said:
Have you tried to use Odin to flash it with stable Baseband rom like XXJVS for Gingerbread Rom, after that try to Flash the new ICS ROM like The Nyx Rom, cuz it's stable and I'm using their Rom since they start the Beta.
Click to expand...
Click to collapse
Now iam on XXDJV1 - it should be the latest version of the original Samsung ROM's. I did flash it with Odin, after that i deletet everything on the phone, flashed a CWM, cleared caches, flash with the zip files (Clean AOKP was the latest).... but do you think it could be different when i start it from the edge? Is there something i can do in a different way?
I really was thinking about Hardware defects, viruses or problems with the root/kernel...

[Q] galaxy S4 random reboots

Anyone else had this / any ideas - my s4 randomly reboots. Can sometimes be when I'm using it or other times when it is sitting idle.
Sent from my GT-I9505 using xda premium

if you can go to download mode flash a new stock rom using odin . before it try with a factory reset too :laugh::laugh:

quibble8 said:
Anyone else had this / any ideas - my s4 randomly reboots. Can sometimes be when I'm using it or other times when it is sitting idle.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
yup, i had this after running a custom rom for a few days. i'm sure it wasn't the rom though, i restored back to stock last night just in case, we'll see.

However, in the future, please also post your ROM, kernel, etc.
For example, having your phone OC might result in such random reboots...

okty2k said:
However, in the future, please also post your ROM, kernel, etc.
For example, having your phone OC might result in such random reboots...
Click to expand...
Click to collapse
I didn't change the kernel and I don't want to name the ROM because I'm sure it's not its fault - it was fine for a few days with plenty of reboots and activity/usage. Sounds like others on stock have the same problem (not necessarily related to the camera issue), so I've gone back to my stock backup and will see what transpires.

ch0use said:
I didn't change the kernel and I don't want to name the ROM because I'm sure it's not its fault - it was fine for a few days with plenty of reboots and activity/usage. Sounds like others on stock have the same problem (not necessarily related to the camera issue), so I've gone back to my stock backup and will see what transpires.
Click to expand...
Click to collapse
I understand you, but it is not like blaming the ROM creator. Is that you might have discovered a bug, and you can help to get it solved.
personally, the first thing I would do is to make a factory reset. This is not the case for you any more... but however.
Good luck and please tell us got things go on...

Fair enough, it was slim bean build 6 on Verizon. I reverted to my stock twrp backup last night (10hrs ago) and been fine so far...

When waking up device, gets black screen, hangs for few secs, then reboots

When attempting to wake up device (SPH-L720) from sleep using power or home button, it doesn't wake up, gets blank screen, the menu and back soft buttons LED lights come on, hangs for few secs on the black screen, then reboots by itself. Issue happens randomly and sometimes once a day or multiple times an hour. It seems like the problem existed before rooting and installing custom ROM but I've just noticed it.
I'm using TriForce 3.0 ROM (Android 4.2.2) w/ baseband L720VPUAMDL and kernel 3.4.0-KT-SGS4-ga23d84c. I've tried wiping/reinstall ROM, reflashing back stock ROM, removing microSD card. Nothing helped. The battery charges properly and is usually fully charged. No wear and tear or damage of any kind. Device is 1 month old.
Any ideas what might be causing the problem and suggestions for possible fix?

its because of the kernal, mine does this aswell..

kyledb said:
its because of the kernal, mine does this aswell..
Click to expand...
Click to collapse
Did you find a fix? Does changing the kernel fix the problem? If so, which kernel did you go with? It's driving me crazy lol. Thanks!

I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.

beerindex said:
I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.
Click to expand...
Click to collapse
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.

verto8 said:
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.
Click to expand...
Click to collapse
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.

I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying

There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading

beerindex said:
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.
Click to expand...
Click to collapse
Same situation here. I rooted and flash a custom ROM on mine right after I got it. I believe it had the issue pre-root on stock ROM/kernel, but I'm not a 100% sure. I had same issue w/ the Cyanogenmod ROM, not sure what kernel it was using.
kyledb said:
I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying
Click to expand...
Click to collapse
Do you remember if you had the issue on stock ROM before rooting? I believe mine has always existed and might be a hardware problem because I tried different ROMs/kernels and issue persisted with all of them.
ParkerParker said:
There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading
Click to expand...
Click to collapse
Is there a comparison thread of different kernels? I'm wondering what the pros/cons of each and maybe some user experience feedback. I believe mine was rebooting as well when it was on stock before rooting. This seems like it might be a hardware problem rather than software (ROM/kernel). Do you think everyone w/ a Sprint Galaxy S4 (SPH-L720) is having this issue? If so, Samsung should do something about it because it's super annoying!

Update: I've been using latest version of KT-SGS4 kernel 3.4.59 (Aug 25 build) for over a day and it's been pretty stable w/ no occurrence of the problem. I'll keep this thread posted w/ updates if I run into any problem. Thanks to everyone for their help!
2nd Update: it still has the problem.

It's still happening but at a slightly lower frequency with the latest KT-SGS4 kernel. For those who have tried a different kernel, did it fix the problem? I'm trying to narrow down the source and convince myself for certain that it's a software rather than a hardware issue.

Same issues
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.

grnerd said:
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.
Click to expand...
Click to collapse
Try that and odin back to stock mf9 not mdl. Tri-force is mf9 based so maybe thats why you get those issues because you need firmware kernel modem and such. Also it could be that kt kernel had been reported to cause some of those issues.

i went to a new rom and new kernal and this is still happening to me, i have no idea what it is now.... any solutions from anyone?
UPDATE: BAD MICRO SD CARD!!!!!!!!!!! REMOVED MY SD CARD AND NO ISSUES IN THE PAST 2 DAYS
NEW UPDATE: SPOKE TO SOON..

Wifi is disconnecting on screen off

So I tried 3 differents roms and all of them had the same issue and I can't fix it.
I tested with stock rom, stock kernel or blu spark kernel. I tried bliss rom and now I am using Codename Phoenix rom.
But I always have the same issue after going to Android Pie, my wifi get disconnected after a few minutes of screen off. My global wifi_sleep_policy is to always enabled but it is not working.
Does anyone have a fix for it?

archraziel said:
So I tried 3 differents roms and all of them had the same issue and I can't fix it.
I tested with stock rom, stock kernel or blu spark kernel. I tried bliss rom and now I am using Codename Phoenix rom.
But I always have the same issue after going to Android Pie, my wifi get disconnected after a few minutes of screen off. My global wifi_sleep_policy is to always enabled but it is not working.
Does anyone have a fix for it?
Click to expand...
Click to collapse
For Pie custom roms you need pie firmware too, checked that?

strongst said:
For Pie custom roms you need pie firmware too, checked that?
Click to expand...
Click to collapse
I was using stock 9.0.4 before trying the custom ROMs. Wouldn't the firmware be automatically updated ?
I will have a look into that, maybe reflash the firmware.

archraziel said:
I was using stock 9.0.4 before trying the custom ROMs. Wouldn't the firmware be automatically updated ?
I will have a look into that, maybe reflash the firmware.
Click to expand...
Click to collapse
The you have 9.0.4 firmware, but try to flash again. Also make sure it's not a custom kernel issue.

strongst said:
The you have 9.0.4 firmware, but try to flash again. Also make sure it's not a custom kernel issue.
Click to expand...
Click to collapse
My current rom is Codename Phoenix, I tried about 3 different kernel to make sure is not a kernel related.
My current baseband is mpsss.at.2.0.c4.7-00070-8998_gen_pack-2.132073.1.179387.1
If I flash the firmware/modem from OOS 9.0.5, will it break something?

archraziel said:
My current rom is Codename Phoenix, I tried about 3 different kernel to make sure is not a kernel related.
My current baseband is mpsss.at.2.0.c4.7-00070-8998_gen_pack-2.132073.1.179387.1
If I flash the firmware/modem from OOS 9.0.5, will it break something?
Click to expand...
Click to collapse
No it won't break something, you can try to update it, maybe it's running then for CNP rom

strongst said:
No it won't break something, you can try to update it, maybe it's running then for CNP rom
Click to expand...
Click to collapse
So I reflash the firmware+modem form this page
https://forum.xda-developers.com/showpost.php?p=76943628&postcount=8
I flashed the 9.0.5 version, but the problem persist, after a few minutes of screen off the wifi just disconnect and I have to unlock and enter the app to receive the notifications.

I realized the problem is that for some reason whatsapp is being killed in the background even after I put it to not be battery optimized.
Will try to make it a sysapp to see if works

archraziel said:
I realized the problem is that for some reason whatsapp is being killed in the background even after I put it to not be battery optimized.
Will try to make it a sysapp to see if works
Click to expand...
Click to collapse
Your wifi disconnects cause YouTube gets killed in the background

strongst said:
Your wifi disconnects cause YouTube gets killed in the background
Click to expand...
Click to collapse
I fixed my wifi , it was caused by some new firmware installed in the router that had a bug that caused all my devices to disconnect when idle.
The new problem now is that my apps are being closed/killed after the screen is off for a few minutes I tried to turn off Baterry Optimization but it did not work.
If I put my phone to charge this behavior does not happen my phone does not kill the apps.

archraziel said:
I fixed my wifi , it was caused by some new firmware installed in the router that had a bug that caused all my devices to disconnect when idle.
The new problem now is that my apps are being closed/killed after the screen is off for a few minutes I tried to turn off Baterry Optimization but it did not work.
If I put my phone to charge this behavior does not happen my phone does not kill the apps.
Click to expand...
Click to collapse
Thanks for the information. To help others you can mark the thread as [SOLVED] and add an info to the first post that it was your routers firmware and not the smartphone

After some time and a lot more of test I find out it wasnt my router firmware problem
The only thing that really solved the problem was installing this mod:
https://forum.xda-developers.com/oneplus-5/themes/magisk-pixel-2-wifi-mod-t3752321
Thanks and this thread can be closed now.