After installing a new kernel (faux 005 u) sometimes my device turns off when it's lock. It sometimes doesn't even reboot unless I plug it in. Does anyone have any idea what's wrong? Rooted, on carbon, latest nightly.
Fixed. Flashed m instead of u.
Related
Hi there,
I'm coming here, because I cannot find the answer to my questions, and you guys can always help
I'm using custom ROM on my Desire, LeeDroid HD V3.3.3 GB R5. Everything is superb, except one little thing. Whenever I switch on WiFi, 3G or GPS it reboots after a while. And it always goes into bootloop, so I have to take the battery out. It only happens when phone is working hard - it's getting hot, that's what i've noticed too. I thought it might be the temperature, so i downclocked the CPU to 900 MHz, but it didn't worked either.
Kernel ver: 2.6.35.10 -g3f43272
If u need any other info, just write it down here.
Any ideas how can i work it out? I don't wanna change ROM, but i need GPS sometimes (that's when it reboots most often...)
newly installed ROM
I've reinstalled ROM. Now it only reboots in gps nav. Any clues? Btw. when revolting, it does not go in to bootloop.
did you try another radio (what about radio recommended by lee)?
Mato_K said:
did you try another radio (what about radio recommended by lee)?
Click to expand...
Click to collapse
That one i use is the latest i guess...
Im having exactly the same problems, though currently my Desire is still running it's original unrooted Froyo OS.
Whenever the phone puts any load on 3G, GPS or the cpu it shuts down and gets stuck in a reboot loop.
MissStabby said:
Im having exactly the same problems, though currently my Desire is still running it's original unrooted Froyo OS.
Whenever the phone puts any load on 3G, GPS or the cpu it shuts down and gets stuck in a reboot loop.
Click to expand...
Click to collapse
If it's not rooted, send it to HTC. (ofc if u still have warranty).
Hi, I recently tried to install a nightly build from CyanogenMod, after a bit of messing around (because im not totally great at doing stuff like this) i managed to install the right kernel but quickly realised some glitches so decided to revert back to the stable 9.1 anzu build. but now all of a sudden today my kernel changed all by itself back to the nightly 10.x build kernel after i turned my phone off and back on which causes the screen to shake constantly on the 9.1 build. Ive tried using the flashtool and entered into fastboot mode via ADB but my phone just remains in the same state and wont go into fastboot mode.
My phone still works fine for receiving calls etc but obviously its very hard to see the screen with it shaking violently, as im pretty much a noob can anyone tell me how i can flash the right kernel back onto my phone and maybe delete the unstable kernel so it wont happen again?
I have tried my hardest to explain my problem so sorry if i'm making very little sense but any help/ideas would be very much appreciated
Thanks
Sem
Well my suggestion is to flash stock firmware and then try to flash cm9 again.
Sent from my GT-I9305 using Tapatalk 2
Hi Guys really need help on this one.
As a brief background on the problem, from stock I have flashed a few custom roms mainly paranoid android, carbon, android revolution hd. Flashing was always successful. No problem with odin flash as well. My concern is this. I noticed that I was getting SODs after flashing a few custom roms. So in order to fix it, I tried to flash stock rom. No problem with flashing however SODs continue to exits. Have tried flashing quite a few stock roms but basically SOD problem still exists. By the way when flashing through ODIN I always just flashed with the PDA option never with the others. Getting really frustrated about this. I can get rid of the SODs temporarily by using SoftLocker. However, I wish to get back to a stable rom base before I try any new customizations. Hope you can help me. Thanks.
On an added note, when I connect my phone to the PC the phone is not automatically detected. I still have to input *#7284# change modem to pda in order for it to be detected. I think this is somehow related because this happened during my encounters with SODs.
Your help would be greatly appreciated.
By the way, I have already checked for the SDS chip and happily my phone doesn't use the insane chip.
Just wondering about this SOD thing.
Should it be enough that I flash into stock (PDA only) to get factory stock?
Should mention that original ROM of phone did NOT have SODs.
So I'm guessing the culprit is flashing the customized ROMs.
However, I cant get stability back even when flashing back to stock.
I can still see some residual effects of previous roms in my current stock rom (like the usb connection not detected).
Just looking for some clues and glad if someone could help.
t3kn1ks said:
By the way, I have already checked for the SDS chip and happily my phone doesn't use the insane chip.
Just wondering about this SOD thing.
Should it be enough that I flash into stock (PDA only) to get factory stock?
Should mention that original ROM of phone did NOT have SODs.
So I'm guessing the culprit is flashing the customized ROMs.
However, I cant get stability back even when flashing back to stock.
I can still see some residual effects of previous roms in my current stock rom (like the usb connection not detected).
Just looking for some clues and glad if someone could help.
Click to expand...
Click to collapse
HI Guys,
Just an update on this, in case someone is experiencing the same problems, it seems I got the SOD fix. I found it out by switching back to an AOKP rom. Suddenly, no more SOD. After a bit more experimenting, I found out that it had something to do with the kernel (stock kernel even!). My basic fix is this: install a stock rom then switch kernel to Note2Core. It seems certain "configuration updates" within the kernel prevents the device from going into sleep of death. (Note that my device now can "sleep" properly ... saw this using cpu spy ... deep sleep is still attained with NO SOD). Hope this helps people out there with the frustrating SOD problem.
Incidentally, if someone could point out how the kernel change fixed the SOD problem it would be a great help.
By the way, usb connection is still not detected by default but fixed by doing *#7248" and then choosing pda for usb.
Fixed! and Solved!
t3kn1ks said:
HI Guys,
Just an update on this, in case someone is experiencing the same problems, it seems I got the SOD fix. I found it out by switching back to an AOKP rom. Suddenly, no more SOD. After a bit more experimenting, I found out that it had something to do with the kernel (stock kernel even!). My basic fix is this: install a stock rom then switch kernel to Note2Core. It seems certain "configuration updates" within the kernel prevents the device from going into sleep of death. (Note that my device now can "sleep" properly ... saw this using cpu spy ... deep sleep is still attained with NO SOD). Hope this helps people out there with the frustrating SOD problem.
Incidentally, if someone could point out how the kernel change fixed the SOD problem it would be a great help.
By the way, usb connection is still not detected by default but fixed by doing *#7248" and then choosing pda for usb.
Click to expand...
Click to collapse
As an end note, I was able to bring back the ROM to stable state.
I believe my mistake was that I accidentally flashed an S3 ROM to my Note 2.
Probably corrupted some files.
The fix seems to be this:
Flash N7100_OXA_N7100XXDLJ2.
It will fail at sboot.bin.
Flash another stable rom (I did it with stock rom Stock_Deodex_Rooted_N7100XXDMC3_N7100OLBDMD1_N7100DXDLK5_THL)
Finish up.
Test for SODs.
CPU spy is the best way to check for it.
If deep sleep occurs without SOD then your phone is back to stable state.
USB connection is working properly as well as bluetooth (which I failed to notice was defective as well).
Hope this helps someone as it took me almost 5 months to get the phone stable. Cheers.
t3kn1ks said:
As an end note, I was able to bring back the ROM to stable state.
I believe my mistake was that I accidentally flashed an S3 ROM to my Note 2.
Probably corrupted some files.
The fix seems to be this:
Flash N7100_OXA_N7100XXDLJ2.
It will fail at sboot.bin.
Flash another stable rom (I did it with stock rom Stock_Deodex_Rooted_N7100XXDMC3_N7100OLBDMD1_N7100DXDLK5_THL)
Finish up.
Test for SODs.
CPU spy is the best way to check for it.
If deep sleep occurs without SOD then your phone is back to stable state.
USB connection is working properly as well as bluetooth (which I failed to notice was defective as well).
Hope this helps someone as it took me almost 5 months to get the phone stable. Cheers.
Click to expand...
Click to collapse
Thanks man i thumbs up ur account....i was changing my dead screen to a new one and i thought it was the new screen that kept turning off even after trying stock kernels and even pegasus but because of ur note2core recommendation and worked like a charm ....thanks man
Hello. I'm running Cyanogenmod 10.1.0-RC5 on my maguro device, and franco-kernel r378. I've been experiencing random reboots, sometimes as often as 2-3 per hour. The phone doesn't even feel warm when it happens. Sometimes I'm using it, but sometimes it's just sitting there doing nothing and it reboots anyway. I've uploaded the last lines of my last_kmsg here, to see if any of you can help me figure out how to solve this annoying issue.
Thank you very much in advance!
Ivan.
I have the same setup no reboots. Do a clean install. Fix per,missions after installing Franco kernel. I have on demand and bfq. Stock speed' and don't use trickster mod
I did a clean install. I'm running the on-demand governor too, and 'deadline' instead of 'bfq' scheduler. I fixed permissions as well, I didn't change the CPU speeds, and I have no idea what the trickster mod is
I might add that i was having this same random reboot problem even with the CM stock kernel.
Any info from the last_kmsg file uploaded?
Thank you!
Best regards,
Ivan.
Small update: I did a fresh ROM install, again. I'm running the stock CM kernel, with the default parameters for CPU speed, scheduler and governor. The problem remains.
Please see an updated version of last_kmsg here.
Try to reflash stock. If the problem remains I am afraid it can even go worse. I mean reboots can become more frequent.
Did u changed your radio?
Had the same problem when I was on AOKP+Franco combo. Actually it was the radio for me which caused the problem.
Reflash everything, including radio, while returning to stock, it worked for me.
good luck :good:
Hello people! I have strange problem.
Yesterday my phone freezes and rebooted, SIM was not working. I was on 30.3. 2106 cm nightly.
From that time, my phone randomly freezes and then immediately rebooted.
Before that, I was playing with CPU governor values, can that damage hardware? (No heat or something like that, but SIM)
Tried many cm13 builds, aosp's, fulmics, cloudy, another kernels, reflahed modem, another battery..
Every ROM was after clean install, apps installed from play store, few with restored data, tried with and without them, same with Xposed, doesn't matter anything.
Anyone know what is it? My phone leaving?
Sorry for bad English. Thanks David.
Tell us, which baseband version you have.
Only 21c on cm13 works. So this one.
OK, I had the same problem too.
I fixed it by removing Kernel Adiutor (yeah, Kernel Adiutor). Then I installed V21C (13.2-00002) modem and rpm/tz partitions (V21C too) posted by @Step-han right here.
I don't know how it works on cm but I'm using stock mm and it works good
Let's try it! I will post results
@jaro1221 It works! Thank you man! Maybe it was caused by installing Fulmics, which reflahed modem.
Thanks!
Having this same problem,first the sim not detected,then from a couple of days apparently random freezes and reboots that persist across stock based and aosp/cm Roms. But I noticed that the freezes and reboots occur only when the device is warm. Not hot,warm as in if the CPU temp is above 60�° C. If it is below 60, the phone can be used for hours without a problem. Any ideas? Could it be hardware related? I've used for months my g3 , and it rarely crossed the 70�° , and did not have this problem. I'm using a d855 16 GB if that matters.
Update: Just in case this could be useful for someone. First,my device got worse,it couldn't boot at all even while cold. it could not get past the lg logo,not in rom,not in recovery. I fixed my problem, maybe temporary, by using some folded aluminium foil. I opened the phone, and put some of it between the mother board and the display, in the same place where you can apply the thermal mod,and then some other between the board and the back case, under the place where the power and volume buttons are. I closed the phone and it booted up, I'm using it for half a day now, installed some games, played while monitoring the CPU temperature. It can go up to 70 degrees and it did not freeze,nor reboot as far. I rebooted some times myself to test if it would detect the sim card,and it had no problem so far,but maybe it is to soon to tell. So... I will update if something happens.