Originally Posted by newbieornah
Yes I have s-off with eng hboot
And I'm not at all familiar with capturing logs, after researching on google the best I was able to do is this https://github.com/newbieornah/bootl...0last_kmsg.txt
I've tried capturing logs during boot but adb wouldn't recognize my device unless it was in recovery
Sorry if it's not what you asked for but I have little experience past rooting and flashing stuff to this phone
First, thanks for the feedback. I apologize for the delay as I have not had much time to look into this.
If there is a kernel panic before the USB/adb driver is loaded, you wont be able to pull a dmesg that way. Pulling the /proc/last_kmsg off of the phone may be the only way to get the kernel log. Pulling the battery will wipe or corrupt the last_kmsg so its a little tricky to get it if you have a kernel panic and the phone reboots a few seconds into boot. You can try this trick that works for me.
This assumes the phone does a full reboot (screen goes black then "T-Mobile Mytouch 4G" logo appears) when it crashes:
1. Disconnect phone from computer.
2. Reboot phone.
3. Hold the volume down & power button when the phone powers down for a reboot in order to reboot into recovery without pulling the battery. (This is tricky as you have to hold both buttons before the phone boots again (Mytouch 4g logo) but after phone loses power.
If you see a bootsplash when the phone boots the kernel panic will cause the bootspash to freeze momentarily. After a few moments have passed you should see the bootsplash move a few more frames before the screen goes black. Hold both buttons when the screen goes black.
If you see the Mytouch 4g logo and then the screen goes black and stays that way for several seconds, you may have to hold the phone at an angle to see if the backlight is on and when it turns off. When you see the backlight shut off, hold both buttons.
3rd scenario is the Mytouch 4g logo stays up for a longer than normal amount of time then screen goes black for a second before the system boots again. Hold both buttons when screen goes black.
This can take several attempts to work.
4. Once you are in recovery mode, do this: adb pull /proc/last_kmsg
If you are unable to get this to work, try to get another log the same way you got the last one. Last one was partially corrupted and I wanted to validate one particular section that stood out to me.
Also if you could post a dmesg from the recovery and/or a dmesg from a boot using a 1.0.4 or 1.0.5 kernel.
Lastly, what recovery and version are you using?