Device rebooting sometimes on system startup (with kernel message). - Android Q&A, Help & Troubleshooting

It not happens always, but when it happens, it's always when the system is starting, when the apps are starting and being granted root permissions, etc. If I don't do anything, is fine, but If I unlock my screen while the apps are loading on startup and start to open some apps, it reboots(not always). I don't know If it overloads or something, but aLogcat doesn't record anything after the system reboots. I've already used Boot Manager to disable some apps from starting, but the problem persists. It's a Moto X 4.4.4 Stock and I never had this problem before. I belive t's a Xposed Module, but I want to know which one is. I've already did a factory reset, then rooted again, but the problem persists.(before I rooted I wasn't having this problem, this is why I believe it has to do with some Xposed Module or something related to root.)
PS: I will pay you 5 dollars(via Paypal) If you help me and find the problem (what's causing it) via these 2 logs. I know it isn't much, but I want to show some appreciation for helping me.
Here's the kernel message:
https://www.dropbox.com/s/5v9bcbsbqk3z3sq/kernel.pdf
Here's another one that I got right after the reboot happened.(I've waited for the device to start, connected my device to USB, then went to adb and wrote # adb shell dmesg.
https://www.dropbox.com/s/l2ghokfk2w97yv4/Kerneldef.pdf
Thanks.

Xposed Module
I belive t's a Xposed Module, but I want to know which one is.
Click to expand...
Click to collapse
Try to uninstall the modules one by one and see which one is causing the problem. What are the modules that you installed as of this moment?
PS: If you're rooted try wiping cache + delvik cache in case you didn't do that.

I've already tried cleaning the cache. Xposed modules: ActivityForceNewTask, Complete Action Plus, GravityBox, Smooth System Progress Bar, Statusbar Scroll to Top, Statusbar Volume, TintedStatusBar, XBlast Tools.

Just happened again. Uploaded another kernel log .

alex91s said:
I've already tried cleaning the cache. Xposed modules: ActivityForceNewTask, Complete Action Plus, GravityBox, Smooth System Progress Bar, Statusbar Scroll to Top, Statusbar Volume, TintedStatusBar, XBlast Tools.
Click to expand...
Click to collapse
Try uninstalling them all first and see what happens. Then install them one by one and check which one coincides with the others in order to see which one causes the problem.

Related

[Q] No service for 5 minutes?

I rooted my MD7 GS4, and Recently (re)discovered Xposed Modules. I figured, hey why not. I wanted as much of a stock experience as possible, but stupid little things like the Text Messages on the lockscreen bothered me.
After downloading and installing Xposed and Wanam, and rebooting, my phone seems to not get any service for a few minutes before finally getting cell service. while searching, at times it will even ask me to switch to global mode? and if I press cancel, sometimes "Sorry, com.android.phone has stopped" and it will freeze. sometimes it wont force stop and then my cell data FINALLY comes on.
I have since deleted and uninstalled Wanam, Xposed, removed the framework, and still having the issue. I just cant figure out what it may be.
I had the same issue. When you install wanam, it makes a backup of the features.xml file and removes most of the original text from thr file in /system/csc. Go there, see if there is a backup (will be called features.xml.bak and should be about 15 KB or so) and rename it to features.xml after deleting the current features.xml. Reboot. Voila. Profit.
Sent from my SCH-I545 using Tapatalk 4
roboots21 said:
I had the same issue. When you install wanam, it makes a backup of the features.xml file and removes most of the original text from thr file in /system/csc. Go there, see if there is a backup (will be called features.xml.bak and should be about 15 KB or so) and rename it to features.xml after deleting the current features.xml. Reboot. Voila. Profit.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Thanks,
Unfortunately, it still does not work. I deleted the new and renamed the .bak and now I'm still stuck on no service, and process stopped.
took about 6 minutes for cell service to come on.
I am having same problem since installing framework and related modules. Not having same length of delay but it's long enough to get attention. Sometimes it asks for SIM card to be installed. Still reading and searching for solution. Wiki check back later.
Thanks.
Sent from my SCH-I545 using xda app-developers app
I am finding this with the latest update 1.4.5. I TiBU back to 1.4.3 and don't see the problem. Then I used TiBU to not allow Wanam to auto update and all is well.
I found the same problem with Wanam or xTheme whenever I make changes with it and I just reboot and service comes right back. Or just don't use a soft reboot
justinisloco said:
I rooted my MD7 GS4, and Recently (re)discovered Xposed Modules. I figured, hey why not. I wanted as much of a stock experience as possible, but stupid little things like the Text Messages on the lockscreen bothered me.
After downloading and installing Xposed and Wanam, and rebooting, my phone seems to not get any service for a few minutes before finally getting cell service. while searching, at times it will even ask me to switch to global mode? and if I press cancel, sometimes "Sorry, com.android.phone has stopped" and it will freeze. sometimes it wont force stop and then my cell data FINALLY comes on.
I have since deleted and uninstalled Wanam, Xposed, removed the framework, and still having the issue. I just cant figure out what it may be.
Click to expand...
Click to collapse
I have the same device, with the same issues after installing Xposed and Wanam. None of the suggestions here worked for me. However, for me, normal operation resumed after deleting Wanam and the Xposed framework. I'd love to find a solution to this, so I could use the Xposed & Wanam.
kenkamm said:
I have the same device, with the same issues after installing Xposed and Wanam. None of the suggestions here worked for me. However, for me, normal operation resumed after deleting Wanam and the Xposed framework. I'd love to find a solution to this, so I could use the Xposed & Wanam.
Click to expand...
Click to collapse
Even deleting it didn't fix it for me. I ended up unrooting and going back to stock. Since then move stayed stock unrooted. If I can't get a ROM then I might as well stay safe
Sent from my SCH-I545 using Tapatalk 4
NilsP said:
I found the same problem with Wanam or xTheme whenever I make changes with it and I just reboot and service comes right back. Or just don't use a soft reboot
Click to expand...
Click to collapse
I know I am repeating myself but if you follow these steps you will be fine.
1) Apply whatever you want.
2) Exit out of whatever you are applying to home screen
3) Use the power button reboot option - Do Not use the reboot options in the xPosed modules
4) If you don't have signal bars in a few seconds when the lock screen come up just reboot with power again
Side note: Do not install or activate any more than 1 thing at a time. For example, install xPosed, reboot, install, Wanam, reboot, make selections in Wanam, then reboot. All reboots from the power button.
NilsP said:
I know I am repeating myself but if you follow these steps you will be fine.
1) Apply whatever you want.
2) Exit out of whatever you are applying to home screen
3) Use the power button reboot option - Do Not use the reboot options in the xPosed modules
4) If you don't have signal bars in a few seconds when the lock screen come up just reboot with power again
Side note: Do not install or activate any more than 1 thing at a time. For example, install xPosed, reboot, install, Wanam, reboot, make selections in Wanam, then reboot. All reboots from the power button.
Click to expand...
Click to collapse
I followed all your rules as I tried this again today, and still not having any luck. I have narrowed my problem down to the installation of Wanam. I did a reboot between each step of installing the Xposed framework, and had no issues there. Yet, after installing Wanam (and before activating the Wanam module) upon reboot, the phone cannot find cell service for at least a few minutes after booting up. Rebooting again (and again and again) makes no difference.

[Q] Moto X randomly reboot on system startup. How to log it??

It not happens always, but when it happens, it's always when the system is starting, when the apps are starting and being granted root permissions, etc. If I don't do anything, is fine, but If I unlock my screen while the apps are loading on startup and start to open some apps, it reboots(not always). I don't know If it overloads or something, but aLogcat doesn't record anything after the system reboots. I've already used Boot Manager to disable some apps from starting, but the problem persists. It's a Moto X 4.4.3 Stock and I never had this problem before. I'm almost sure it's a Xposed Module, but I want to know which one is.
Thanks.
No one knows?
Yeah
Yeah its mainly due to xposed module or you didnt root correctly . Better unroot by installing stock rom from motorola website and root it again .
Sounds like a kernel panic try and grab kmsg if you want to trouble shoot or wipe clean and start fresh if this seems like to much

HDC Note 3 for Xolo Q900

HDC NOTE 3 for XOLO Q900
Compatibility
Can be flashed on Xolo Q900.
Highlights
Note 3 UI & features
4.2.1 rom (Please ignore 4.3 shown in about phone, its hardcoded and wrongly left over by mistake. will be removed later. sorry for that)
Invisible SUPERUSER (No prompt)Cameras 13MP Rare and 5MP front Camera (5mp Front Camera Results)
Face Detection perfect in both Cameras, even in Front Cam working fine
Dual Sim, Dual Standby
Swipe to Call and Swipe to Message
Fully Deodexed & Zipaligned
Init.d support
Busybox
Pre-Rooted
Heavy Games working perfect
No air gestures
No smart scroll
Added working Multi Window feature
Added Air Command feature
Clear photo and video capture
New lockscreen effect
New and clean quick setting buttons
Messaging counter notification
Added GREENIFY
and many more ROM Tools.
Disclaimer
I will not be responsible if you brick your device or any problems whatsoever..... Flash at your own risk.
Instructions to flash via CWM/TWRP (FLASH AT YOUR OWN RISK)
1. Download zip file and Put into external/internal sd card
3. Open Recovery mode (TWRP/CWM)
4. Format System Partition (cwm>mount storage>format system)
5. Wipe with Data/factory Reset
6. Wipe Cache Partition and Dalvik Cache.
7. Flash the rom zip file
Download Links -https://docs.google.com/uc?id=0B2dTg0ax0GR_SUxmenBUNllWUVE&export=download
PORTED BY AMARJEET PAUL
Full Credits to © REMZEJ. for Full Rom and Research & CMahendra & if i forgets anyones name please dont mind
FREQUENTLY ASKED QUESTIONS
I randomly get error message "SystemUI stopped working".
.
(Solution 1) SystemUI FC Error comes due to Xposed. If you dotn install it, this error does not appear. This error happens due to conflict of home key in XposedFW +GravityBox. Thanks to a user adityagulavani, who hinted a quick-tip to solve this problem. Setup this option in GravityBox and error is gone. .
GravityBox>>>Navigation_Keys-Actions >>> HomeKey+LongPressActions >>> Show_Recent_App.
.
After this setup the error does not appear again.
.
(Solution 2) Most probably this is due to Xposed Module. Remove modules one by one and reboot each time to check. There are hundreds o Xposed modules for same task, you can try another. Also Clear Dalvik Cache and Fix Permissions from recovery mode when you reboot..
I dont have Xposed installed but still getting error message "SystemUI stopped working".
(Solution) Clear Dalvik Cache from recovery mode. It will vanish. If possible try "Fix Permissions" in TWRP. This option works for most roms. If you are on CWM, better change to TWRP 2.5.0.0, the total perfect stable version.
.
How to get rid of this Play app . It automatically installs uc broweser, candy games etc. There is no option in this app to stop automatic installation. I didnt disable this app because it may affect some other apps..so plz tell me what do.
(Solution) You did great job by not installing PlayApp. We have installed it for SideBar to work. Do not uninstall PlayApp. There is one App called "Disable Service" specially given to disable PlayApp. Once disabled from this app, it will not bother again and rom features will keep functioning well. After disbling, you can uninstall UC Browser and Candi Bar game. And please, do not uninstall or disable Playapp from System Setting> app manager.
Why PlayApp is included?
(Solution) @remzej said there is some association of this app with SideBar, hence it cannot be avoided. Just disable it with method mentioned above and forget it.
.
Recent app bar it not working correctly. When i close a app it appears after 10 sec or later in recent app bar. Or i have to open some other app to clear it instantly. Hence last opened app doesnt appear in recent bar instantly after exit. (Solution) Recent app works perfectly. Just wipe dalvik cache from recovery
.
Cant see SuperUser/SU? Should I install SuperSU? What do you mean by Hidden SuperSU?
.
(Info) SuperSU is installed inside rom and is already enabled. You will not be prompted for SuperSU permission of any application while installing. Just leave it and do not try to install it to avoid conflicts
Hit Thanks if you liked my work
Thanks for keeping Q900 thread active! I really thank you!
bro hav u tried dis rom or not ??????
need help
Problem resolved
bluetooth disturbance
I've installed this rom and everything is working but bluetooth is not working properly.....i tried to transfer some files via bluetooth and there it goes ,,it couldnt send or receive bluetooth transferd data...Can u located why dis happened,,,.and 1 more thing....it is not charging//everytime while charging ..the charging level indicator is at same point...for instance 27% charged...and though it is charging the battery level percentage is at same point .i.e. 27%....and the device gets frequent heating..
no wae its wrong , what should i do...

Need help troubleshooting why my wifi won't turn on

Hello, I have a Samsung Galaxy A5 2017 running AOSP Extended 4.6 rom. I'm using TWRP recovery and have it rooted with SuperSU. I'm having a problem where my wifi won't turn on. The button is grey, and when I try to switch it on it says "turning on wifi" but the button never switches to blue, and it never finds any wifi. It's totally broken.
It's an old phone, so I thought it might be a hardware issue, so I did a backup then a clean wipe, and whattaya know, the wifi worked fine. So it's something gone wrong particularly in the "data" segment of the backup, since restoring the backup without the data block selected acts just like a clean wipe. When I do a full backup with all apps and settings, that's when the problem happens.
I tried to just start from scratch, but for some reason titanium backup is hanging on restoring all my apps and settings and won't do it, so it's a major pain in the ass, and I'd rather just figure out what the problem is on the full backup and fix it so I can keep my phone nice and familiar.
Okay, so I ruled out any user apps as being the problem, as I completely uninstalled every user app, without any change. I can't uninstall most system apps without breaking the OS, so I hope the problem is in some internet configuration setting or something that I can easily change.
Does anybodoy know how I can fix my wifi?
Thanks!
0
Hello, thanks for the response! I haven't had an opportunity to try this but I will when I get a chance and I'll post the log. And yeah I've been trying to swap to magisk, but it doesn't like the modded boot.img of my custom rom, it won't do it. I'm trying to figure it out. >.<
Seppppx said:
You can run logcat in adb
See : https://developer.android.com/studio/command-line/logcat
Also you can install a logcat app like MatLog to get logs without a computer (requires root).
That might give you a hint to why the wifi doesn't work. If the logcat doesn't show anything that would indicate the problem in detail try obtaining the kernel logs with dmesg or kmsg
See : https://forum.xda-developers.com/showthread.php?t=2185929
I also recommend using Magisk insteaf of SuperSu as chainfire sold it to a random sketchy Chinese comapany.
Click to expand...
Click to collapse

[Pixel 4a, Android 11] Installing cloned Discord app somehow soft bricked my phone?

So far what happened:
1. Launched app cloner - cloned Discord with a lot of tweaks like disable networking
2. Launched it - INSTANT soft reboot
3. I get into the Android OS and SystemUI isn't even loaded or attempts to load. Power menu is the old one from Android 10 now. Everything works fine though.
4. I reboot fully and this time see the bootloader unlocked warning - nothing changes
5. Again full reboot - nothing changes
6. Reboot into safe mode and I just see a black screen with safe mode in the bottom left. SystemUI doesnt even load.
7. Then I reboot normally.
8. Now whenever the phone tries to load into the OS, just after the boot screen ends, I get "Shutting down" (again in Android 10 style) and it just blinks off immediatley.
9. After that it just shows the "Cannot load Android system" screen offering to factory reset
One thing I noticed - I think the clone messed up somehow and installed a severely corrupted app - because after I installed it - I saw THREE discords in the app launcher: Discord, Discord, and Discord 2 (as I named the clone).
How the hell do I get into my phone and uninstall all versions of Discord so I can boot in? Or did this somehow manage to corrupt my phone that bad? I didn't know an app could do this!!!
Can I do this if i boot in via TWRP?
I've tried the adb wait-for-device shell magisk -remove-modules incase its conflicting with one of my modules via SystemUI and it worked briefly but has had no effect.
How can I access any logs that tell me whats causing this??
EDIT:
Booted into TWRP succesfully, cannot find any trace of a related app in /data/data or /data/app. I found the stock discord and got rid of that but I can't see the cloned one!
I did uninstall the cloned discord in the brief moment I was able to boot into the phone but its not helped. I guess it's already uninstalled. Its a mystery what has caused my phone to get this bad!
_sjain said:
...
How can I access any logs that tell me whats causing this??
...
Click to expand...
Click to collapse
Do a LOGCAT
jwoegerbauer said:
Do a LOGCAT
Click to expand...
Click to collapse
Managed to get it with TWRP but it's not showing anything useful or related to the cloned Discord app anywhere... no clue what to do
ok i just wiped the phone, was able to get internal storage with adb pull via twrp tho

Categories

Resources