Database Info

[Q] How to determine the reason for hot-reboots using logcat?

Hi, I'm have an HTC EVO 3D with Sense 3.6 ICS 4.0.3 rom/ custom kernel, unlocked bootloader...
here is the sequence of my problem
superwipe
Install rom
install kernel
boot
rom works perfectly fine
restore user apps ONLY using TiBackup
system still works fine
reboot for any reason
continuous hot-reboots for ever
I'm sure some app or setting is cause that
but I want to know which by using a logcat
I know how to view logcats
but what should I look for?
there are too many values..
any help would be appreciated
thanks

Do you have fast boot checked under the Settings, Power? Try unchecking it before rebooting.

mf2112 said:
Do you have fast boot checked under the Settings, Power? Try unchecking it before rebooting.
Click to expand...
Click to collapse
never used fastboot before..
I always uncheck it because its usless
I just want to know what does an error causing a hot reboot looks like in logcat?

s_superman said:
never used fastboot before..
I always uncheck it because its usless
I just want to know what does an error causing a hot reboot looks like in logcat?
Click to expand...
Click to collapse
I understand, sorry I don't know how to read logcats better. The fast boot being turned seemed like the logical cause of the problem based on what you described. You might try posting in your devices Q&A forum instead of the General Q&A forum to get more device specific replies. Or you could try posting in the link in my sig for how to logcat and someone there may be able to help further.

typicaly in logcats (Eclipse for example) errors text is red color.
Try to see the lines before the reboot and target at the red ones
these lines will give you info about which app gives the error(if this is an app error) and what type of error it is.
even if you dont know how to handle the errors you see , try to unistall the app that gives the error , and see if the problem stops

[Q] Options for CROMi-Xenogenesis 4.4 ODEX

I'm running CROMi-Xenogenesis 4.4 ODEX and have not posted enough to post in the actual development thread...so posting in General. This is a fresh install and the main application I am running after install is Waze (gps location type app for driving/navigation). Running this application results in random system reboots. So I am wondering what options should I select or not select in order to ensure stability? I'm basically tried all the kernel patches with this install. I'm not sure what I should turn off. Any advice appreciated. Thank you.

What options did you select when you installed (other than default ones) and how long does it work before rebooting? Does the back of your tablet get warm while using this app? I know my tablet has had issues in the past when it gets too hot. You could try making sure your tablet is not in performance mode and see if that helps at all.
I just installed it and it hasn't crashed for me yet, although my tablet did get warm (probably because my tablet is overclocked in performance mode at the moment).

bmlarson said:
What options did you select when you installed (other than default ones) and how long does it work before rebooting? Does the back of your tablet get warm while using this app? I know my tablet has had issues in the past when it gets too hot. You could try making sure your tablet is not in performance mode and see if that helps at all.
I just installed it and it hasn't crashed for me yet, although my tablet did get warm (probably because my tablet is overclocked in performance mode at the moment).
Click to expand...
Click to collapse
I remember the Cross Breeder Optimization Patch with virtually everything else enabled as well. Perhaps I'll go back through and bit a more restrictive on my options. I didn't check the back for heat but I'm running in balanced mode and there kernel is not an OC'd one. If anyone has additional suggestions please let me know. I'll probably wait for 4.5 to try again.

I don't understand why you didn't post this in the Q&A section or the cromi-x thread it's self.. You would get a lot more feed back.

FrostByghte said:
Running this application results in random system reboots.
Click to expand...
Click to collapse
After a random reboot, save the file /proc/last_kmsg and post it. It may contain relevant error messages.

Good advice from _that. Also reflash without cross breeder first.

_that said:
After a random reboot, save the file /proc/last_kmsg and post it. It may contain relevant error messages.
Click to expand...
Click to collapse
Great advice -- got it from sbdags bbefoe -- but after most if not all random reboots, somehow, my 700 won't boot into the OS, and hangs at the very first screen with "ASUS" and a lot of smaller white lettering. At that point, I will have to reboot it manually, losing the last_kmsg in the process. Frustrating.

ronniereiff said:
I don't understand why you didn't post this in the Q&A section or the cromi-x thread it's self.. You would get a lot more feed back.
Click to expand...
Click to collapse
The forum software won't allow me to post in the thread I do understand that but I don't have permission until I post 10 posts or some such. Once I'm there I will definitely take part and move my questions to the development thread.

sbdags said:
Good advice from _that. Also reflash without cross breeder first.
Click to expand...
Click to collapse
Thanks for the advice. I'll look at trying this as well. Excellent ROM btw...I'm running the older 3.4.7 on my wife's tf700t. Like night and day speed wise.

FrostByghte said:
The forum software won't allow me to post in the thread I do understand that but I don't have permission until I post 10 posts or some such. Once I'm there I will definitely take part and move my questions to the development thread.
Click to expand...
Click to collapse
Ah ic ic

data2sd
_that said:
After a random reboot, save the file /proc/last_kmsg and post it. It may contain relevant error messages.
Click to expand...
Click to collapse
sbdags said:
Good advice from _that. Also reflash without cross breeder first.
Click to expand...
Click to collapse
I also don't have enough street cred to post in the developers forum, so I thought I'd highjack this.
I just wanted to confirm what a few other people have said in the CROMi-X thread. The odex data2sd mod doesn't work. You have to flash the _that data2sd mod over the top to get it going. I've tried a few times to no avail. I tested write speeds and looked in the root and it definitely wasn't happening. The files are there in /system/boot but no-ones home. I don't understand anything about the inner workings so I can't be of much further help.
Awesome rom and kernel though guys. Seriously, love it!

CiaronDarcOne said:
I also don't have enough street cred to post in the developers forum, so I thought I'd highjack this.
I just wanted to confirm what a few other people have said in the CROMi-X thread. The odex data2sd mod doesn't work. You have to flash the _that data2sd mod over the top to get it going. I've tried a few times to no avail. I tested write speeds and looked in the root and it definitely wasn't happening. The files are there in /system/boot but no-ones home. I don't understand anything about the inner workings so I can't be of much further help.
Awesome rom and kernel though guys. Seriously, love it!
Click to expand...
Click to collapse
That's one of the few things that I didn't attempt to load was the data2sd mod. I have a 64gig device so w00t. Looking back now though, if I had it to do over again I would NOT have purchased the TF700t. I really thought it would be a better device. One thing I look for now is 2 gigs of physical memory. My Note 2 simply runs rings around the TF700t. I still haven't had any reason to put a ROM on the Note2. TF700t doesn't even function properly without something like CROMi.

gallery apk wont work, always stops by turning on. How to fix this ?

hemeyus said:
gallery apk wont work, always stops by turning on. How to fix this ?
Click to expand...
Click to collapse
Clear data and cache on the gallery app

[Q] Strange bootloop issues

Kinda new to this so forgive me if i miss something somewhere and if i need to give more information somewhere just let me know.
With that out of the way I'd like to start with the fact that this is my first rooted device. Currently on C-spire (cellular south) if that matters.
A few days ago before the phone was rooted or even unlocked i went to make a phone call and the screen blacked out and a few seconds later went into a reboot loop where it would get to the Motorola Logo for about 6 seconds or so then shut off and try again ad nauseam until the battery died. After letting the battery die and connecting it to the charger it continued the loop so after a quick gogle search I began fiddling with buttons and realized i could boot into fastboot and recovery modes. I decided i might as well root since it couldnt get a whole lot worse and after a quick look around the forums and a trip to motorola to unlock my phone i was able to flash TWRP recovery, after which i accidentaly wiped the os, managed to find any number of replacement roms none of which solved the boot issue. I eventually found the stock Sprint roms which allowed the phone to boot and work for the most part, but it wont send media messages and has trouble picking up 4g service. I am also forced into using the sprint updater among other things which include having sprint plastered everywhere I have tried flashing several custom roms (pacman, paranoidandroid, and cyanogen) all of which get hung up booting just like the phone did before but the sprint stock rom will reload and work just as before. I'm not sure what would be causing this or if there is a way to fix it and i apologize for the wall of text. If any more info is needed let me know and ill provide ot to the best of my knowledge. Thanks in advance :fingers-crossed:

So all ROM's fail to boot?
Are you doing a factory reset in TWRP before you boot?
Are you flashing gapps? Although that shouldn't cause the phone to fail at booting...

Correct. All roms except the stock sprint rom fail to boot.
Now that i have everything backed up on my external sd I've tried factory reset using twrp as well as wiping everything prior to flashing a ROM as well as after but
Before booting. And the many combinations thereof
And yes i am flashing gapps.

You don't get any errors when it flashes?
Did you check the md5sums?
I flash around a lot, and just got another Q - latest ROM's are not a problem here.

arrrghhh said:
You don't get any errors when it flashes?
Did you check the md5sums?
I flash around a lot, and just got another Q - latest ROM's are not a problem here.
Click to expand...
Click to collapse
I haven't gotten any errors while flashing. Not quite sure how to check the the md5 sums though

AMerexican said:
I haven't gotten any errors while flashing. Not quite sure how to check the the md5 sums though
Click to expand...
Click to collapse
Every ROM should include a md5sum with it. If you're on Windoze, use a program like WinMD5 - check the md5sum locally, and compare it to what is on the server. If they match, the download is probably good.

So after checking the pacman rom matched up (it's the most recent one I've tried), the cyanogen didnt
but i recently redownloaded it and its better now (haven't tried flashing yet), and I can't seem to find the MD5sum for
the paranoid android rom on here.
Anything else i should try?

AMerexican said:
So after checking the pacman rom matched up (it's the most recent one I've tried), the cyanogen didnt
but i recently redownloaded it and its better now (haven't tried flashing yet), and I can't seem to find the MD5sum for
the paranoid android rom on here.
Anything else i should try?
Click to expand...
Click to collapse
The PA build I think is "blind", I don't know if anyone has tried it - additionally, the individual who built it does not own this device... So it's double blind? Haha
The CyanogenMod ROM's, however, are official and work great - many others have confirmed this.
If you had a bad download, that would explain it.

arrrghhh said:
The PA build I think is "blind", I don't know if anyone has tried it - additionally, the individual who built it does not own this device... So it's double blind? Haha
The CyanogenMod ROM's, however, are official and work great - many others have confirmed this.
If you had a bad download, that would explain it.
Click to expand...
Click to collapse
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?

AMerexican said:
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?
Click to expand...
Click to collapse
I suppose some sort of hardware issue. Like I said, I've flashed most of the newest ROM's here for the Q - all work fine. Hell, some I even ported myself...
I'm kind of at a loss. Can you get adb? Not even sure what to check for next... if you are wiping properly in recovery, that should be sufficient.
Hm, I guess that brings up a good point. Have you tried wiping system, flashing, doing a factory reset, then booting? Most, if not all of the ROM's should wipe /system before flashing... So it probably won't do anything different.

AMerexican said:
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?
Click to expand...
Click to collapse
After the crash during CM bootanimation, boot to recovery and
Code:
adb pull /data/dontpanic/apanic_console
apanic_console should contain the log of the kernel panic, post it here.

kabaldan said:
After the crash during CM bootanimation, boot to recovery and
Code:
adb pull /data/dontpanic/apanic_console
apanic_console should contain the log of the kernel panic, post it here.
Click to expand...
Click to collapse
For my own personal edification, /proc/last_kmsg would work in this instance as well?
Just curious why you went for the apanic_console instead

arrrghhh said:
For my own personal edification, /proc/last_kmsg would work in this instance as well?
Just curious why you went for the apanic_console instead
Click to expand...
Click to collapse
Yes, /proc/last_kmsg would work as well.
Though there's a scenario were it wouldn't be the same - if the user would miss the right time to hold 'volume up' (to get to the recovery after crash) and pressed "power+volume down" to force reboot and try to enter recovery again. In such case, /proc/last_kmsg would not contain the panic from previous boot, the panic would be only in /data/dontpanic/apanic_console.
/proc/last_kmsg - log from the last boot
/data/dontpanic/apanic_console - log from the last crashed boot

kabaldan said:
Yes, /proc/last_kmsg would work as well.
Though there's a scenario were it wouldn't be the same - if the user would miss the right time to hold 'volume up' (to get to the recovery after crash) and pressed "power+volume down" to force reboot and try to enter recovery again. In such case, /proc/last_kmsg would not contain the panic from previous boot, the panic would be only in /data/dontpanic/apanic_console.
/proc/last_kmsg - log from the last boot
/data/dontpanic/apanic_console - log from the last crashed boot
Click to expand...
Click to collapse
Ah, that makes sense - I was not aware of this apanic_console
Thank you!

arrrghhh said:
Ah, that makes sense - I was not aware of this apanic_console
Thank you!
Click to expand...
Click to collapse
I'm getting an error from the forums saying the text is too long. any way around that? or do i need to divide into multiple posts?

AMerexican said:
I'm getting an error from the forums saying the text is too long. any way around that? or do i need to divide into multiple posts?
Click to expand...
Click to collapse
Pastebin.com, hastebin.com, pastebin.ca, heck even put the file in .txt format and attach to this post, upload it dropbox...
Thanks!

arrrghhh said:
Pastebin.com, hastebin.com, pastebin.ca, heck even put the file in .txt format and attach to this post, upload it dropbox...
Thanks!
Click to expand...
Click to collapse
Thanks wasnt sure of the forums rules as far as that was concerned
http://pastebin.com/QFq1naK0

Any ideas?
Or anything else i need to do?

[Q&A] ★ ☆ [ROM][4.4.4] UnSenseSIX v1.01 | Sense/GPE/L | Hybrid | EYE | 1

[Q&A] ★ ☆ [ROM][4.4.4] UnSenseSIX v1.01 | Sense/GPE/L | Hybrid | EYE | 1
Q&A for ★ ☆ [ROM][4.4.4] UnSenseSIX v1.01 | Sense/GPE/L | Hybrid | EYE | 10-30-14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for ★ ☆ [ROM][4.4.4] UnSenseSIX v1.01 | Sense/GPE/L | Hybrid | EYE | 10-30-14. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

I'm having a force close problem with Phone making the entire device inoperable. I'm not sure if it's a firmware problem because I don't know if I'm on the newest firmware. Can someone send me a link to the new firmware for fastboot flashing?

hk170 said:
I'm having a force close problem with Phone making the entire device inoperable. I'm not sure if it's a firmware problem because I don't know if I'm on the newest firmware. Can someone send me a link to the new firmware for fastboot flashing?
Click to expand...
Click to collapse
All error fixing info was posted by OP. It's the first post. You might be experiencing a simple problem of having to fix permissions in recovery through TWRP. Also, newest firmware is also listed wherever you downloaded it from, or use search to find it in another thread.
Sent via Tapatalk on my Big Red M8

hk170 said:
I'm having a force close problem with Phone making the entire device inoperable. I'm not sure if it's a firmware problem because I don't know if I'm on the newest firmware. Can someone send me a link to the new firmware for fastboot flashing?
Click to expand...
Click to collapse
Link to the latest firmware is in the OP.
It's the 3.28.605.4 (4.4.4) firmware.

I've confirmed that I have the updated firmware and the problem still persists. I flashed the insecure kernel to make it turn on. Fixing permissions did not solve anything. I am using twrp. Since that may be the issue, which recovery do you expect to have the best results?

Not really a question, more of an observation. I have done all the instructions from your inital post. I only get systemui FCs when my phone isnt on vibrate/silent. If i have volume up and receive an email or text then i get the fc. Not sure if you care, just something i noticed. Really like the look and feel.

If you wiped system, data, cache and dalvik before flashing, you should be able to fix the ui force closes using the method posted in my OP and post 3.
Boot to recovery, fix perms, wipe cache and dalvik, fix perms once more for good measure, reboot...
I don't need symptoms or causes.
Thanks.
The ROM can be run without that recurring annoyance, or it wouldn't have been worth my time posting.
Try what was said, if it doesn't work, try again, reflash, etc..
Still doesn't work, I can't help. Sorry

Appears to be a lost cause for the time being then which is unfortunate. Thanks for the response. Good luck with the development.

So I'm pretty sure I followed all directions properly but wifi is broken. I'm on Verizon and my h.boot is 3.19.0, my radio is 1.09.20.0702, firmware is 3.28.605.4.
Boots up normally fast, I've cleared cache and dalvik after fixing permissions. Dunno where I screwed up at.

rcanderson232 said:
Not really a question, more of an observation. I have done all the instructions from your inital post. I only get systemui FCs when my phone isnt on vibrate/silent. If i have volume up and receive an email or text then i get the fc. Not sure if you care, just something i noticed. Really like the look and feel.
Click to expand...
Click to collapse
Just posting to confirm that this did indeed work for me. I followed all of Santods instructions to a T and still had systemui FC's whenever i received a hangouts notification. Flipped my ringer mode to silent/vibrate and all of the sudden no systemui FC. Thanks for your post. hopefully more people can see this and try it out. Other than that one problem I was having, this ROM has been absolutely amazing. Best of both worlds!

Same.. Force close after following all the directions
Sent from my HTCM8

I'm having trouble booting into recovery. Since there is no APM, I power off and hold volume down and power and I just get a normal boot sequence, trying to boot into recovery from an app also does not work. I'm using TWRP 2.7.1.

mbtags said:
I'm having trouble booting into recovery. Since there is no APM, I power off and hold volume down and power and I just get a normal boot sequence, trying to boot into recovery from an app also does not work. I'm using TWRP 2.7.1.
Click to expand...
Click to collapse
Hold down the volume button and do a restart instead. Works better that way.

mbtags said:
I'm having trouble booting into recovery. Since there is no APM, I power off and hold volume down and power and I just get a normal boot sequence, trying to boot into recovery from an app also does not work. I'm using TWRP 2.7.1.
Click to expand...
Click to collapse
As soon as you hit restart..... And see the htc logo come on.... Hold volume down and power... Should take you to HBOOT screen... Then choose recovery

Has anyone been able to fix the notification FC's besides setting alerts to mute/vibrate?

detr0yt said:
As soon as you hit restart..... And see the htc logo come on.... Hold volume down and power... Should take you to HBOOT screen... Then choose recovery
Click to expand...
Click to collapse
As the post above you states, just volume down works fine and is simpler.
So as you said, wait to see HTC logo after hitting restart, then just press and hold volume down until hboot menu appears..
That is the simplest way to get to hboot/recovery.

ludeboy said:
Has anyone been able to fix the notification FC's besides setting alerts to mute/vibrate?
Click to expand...
Click to collapse
Quite a few folks have posted that they were able to fix them using my instructions.
And others have posted that the rom is running well for them, no force close issues.
So I would say yes, someone definitely has.

ludeboy said:
Has anyone been able to fix the notification FC's besides setting alerts to mute/vibrate?
Click to expand...
Click to collapse
We must be part of the unlucky few. Followed all of his instructions in the OP and still get the FC when im not on silent/vibrate. I have flashed several ROMs before and never had a problem with "following directions". Honestly, I never need to have my phone on sound, so I dont really care about the FC. It would just be nice to figure out what we are doing wrong. ROM is great and I think im definitely going to stay with this one for a while.

I literally have been trying for hours to get this to work... I have followed this to a 100% T and still no luck... Im clueless... After i had everything set up.. I removed my gmail account.. And all my text messages were perfect... I re added my gmail account and it started doing the forced closes all over again... So discouraged

santod040 said:
Quite a few folks have posted that they were able to fix them using my instructions.
And others have posted that the rom is running well for them, no force close issues.
So I would say yes, someone definitely has.
Click to expand...
Click to collapse
You're like seriously an angry dev or something dude. I'm trying to get help from others since you don't seem to want to help other than snapping and telling people to move along. You got a cool thing going and I'm just trying to make it work.
I tried doing what you said a million times and wiped my phone a million times. So I'm trying to see if those that have gotten to work have actually gotten it to work or just thought they did like I did by putting the phone on vibrate. And maybe if they got it to work, they have something specific like that they might want to share to help others out. Much like I did when I said you have to wipe the system partition. I realize now that you put that in your instructions, but most people don't wipe system when they flash ROMs. Was I stupid? Yes. Should I have followed instructions to a T? Yes. But after flashing ROMs for a while, you start to assume things.
---------- Post added at 10:47 PM ---------- Previous post was at 10:43 PM ----------
detr0yt said:
I literally have been trying for hours to get this to work... I have followed this to a 100% T and still no luck... Im clueless... After i had everything set up.. I removed my gmail account.. And all my text messages were perfect... I re added my gmail account and it started doing the forced closes all over again... So discouraged
Click to expand...
Click to collapse
Did you reboot after you removed your gmail account? I just tried removing mine and still getting FC.

Question A bit of problem......

I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?

Hi,
Can you boot into bootloader?
Press power button until phone reboots while keeping volume down pressed.
From there you can install a factory image.
What version are you actually on?
Good luck,
Sébastien.

niftyXD said:
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Click to expand...
Click to collapse
Flash the stock kernel (partitions) via Fastboot.

most users having issues like this end up getting it up and running using Google's official Android Flash Tool . It takes a lot of guesswork and/or misfires that a lot of users end up hitting the wall at...
I suggest making sure to check "don't wipe" or "keep data" (sorry, I've only used it twice, so going off of memory is foggy) so it doesn't return the device to stock...

niftyXD said:
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Click to expand...
Click to collapse
did you disable Verity and verification before flashing the kernel?

It's frustrating when someone posts a problem then never follows up

HipKat said:
It's frustrating when someone posts a problem then never follows up
Click to expand...
Click to collapse
It's why I've relegated myself to editing the title "SOLVED" for members on their threads, as a service for those of us who roam around here assisting and helping...
it's not much, but it's sometimes helpful to be able to see in the title and/or be able to tell from a glance if/when someone followed up...

simplepinoi177 said:
It's why I've relegated myself to editing the title "SOLVED" for members, as a service for those of us who roam around here assisting and helping...
it's not much, but it's sometimes helpful to be able to see in the title and/or be able to tell from a glance if/when someone followed up...
Click to expand...
Click to collapse
Hey,
Most likely solved it by himself, since he didn't show up since 5 minutes after his post
Anyways, hopefully, people's experiencing the same issue will find this thread with possible solutions (before opening a new thread).
Cheers,
Sébastien.