No dice. Also trying to grab a logcat during the boot loop is impossible. It doesn't get to the point for adb to be recognized and pull one. It gets to the initial Samsung logo, than to the Samsung Galay S III logo, then it boot loops before the Samsung animation happens.
I am in recovery right now, and I have not went back to the stock kernel yet. Is there anything you can think of that might be useful to pull via adb?
I can't think of anything else right now... but I also suspect that my script didn't work the way it should - I'm sure I remember a situation where the "wait for device" part would never detect my phone even after it was fully booted, but only on one OS - I thought the Linux version was the one that didn't work as expected, but I might have that backwards...
As a last test, you can try entering "adb devices" at the command prompt, pressing enter even though it will fail (this is preparation before you turn the phone on), then while the phone boots, repeatedly press up then enter to bring up the last entered command and re enter it - if you ever see a device id before the boot loop, then the wait for device command doesn't work correctly in the Windows version of adb
Sent from my SPH-L710 using xda app-developers app
"What is this?! When does this happen in the movie?!"
"Now, sir. You're looking at now - everything that's happening now, is happening now."
I haven't been able to test this just yet, but try the following:
adb wait-for-device; adb pull /proc/last_kmesg
(Enter both commands on one line with a semi-colon separating them as shown)
The first command should wait until adb detects your phone, forcing the second command to wait to run until that point - the result should be that the pull command runs at the earliest possible moment, placing a copy of the last_kmesg file in your current directory on your computer...
I tried this, and the phone will never boot to the point to recognize adb.
---------- Post added at 09:47 PM ---------- Previous post was at 09:45 PM ----------
Quote:
Originally Posted by styles420
As a last test, you can try entering "adb devices" at the command prompt, pressing enter even though it will fail (this is preparation before you turn the phone on), then while the phone boots, repeatedly press up then enter to bring up the last entered command and re enter it - if you ever see a device id before the boot loop, then the wait for device command doesn't work correctly in the Windows version of adb
Sent from my SPH-L710 using xda app-developers app
adb devices never shows up a device, so it won't even get to adb at all.
Hey Ktoonsez, thanks for trying man. If you can think of anything else to try or any kind of log to pull please let me know I am more than willing to help. I sure wish we could get this kernel running on TW 4.1.2. I love your kernel, and it gave me unbelievable battery life, but I don't want to go back to 4.1.1, so hopefully one day you can figure it out man.
I even wiped everything back to factory then just installed the system.img only then your kernel with no data.img to see if it was hanging on data or something, and I still got the boot loop. I have exhausted my brain on this, and I can't think of anything else.
I tried this, and the phone will never boot to the point to recognize adb.
---------- Post added at 09:47 PM ---------- Previous post was at 09:45 PM ----------
adb devices never shows up a device, so it won't even get to adb at all.
Hey Ktoonsez, thanks for trying man. If you can think of anything else to try or any kind of log to pull please let me know I am more than willing to help. I sure wish we could get this kernel running on TW 4.1.2. I love your kernel, and it gave me unbelievable battery life, but I don't want to go back to 4.1.1, so hopefully one day you can figure it out man.
I even wiped everything back to factory then just installed the system.img only then your kernel with no data.img to see if it was hanging on data or something, and I still got the boot loop. I have exhausted my brain on this, and I can't think of anything else.
Have you tried the 4.1.1 just for the hell of it? That was stock ramdisk so I believe it is not the ramdisk, so that means code which is very rare. Have to start completely over
If you like my work, donate with this link: http://forum.xda-developers.com/dona....php?u=4325945
_____________________________
Do NOT flash my kernels if you are allergic to AWESOME!!!!!!!!!!!!!!!
_____________________________
I tried this, and the phone will never boot to the point to recognize adb.
---------- Post added at 09:47 PM ---------- Previous post was at 09:45 PM ----------
adb devices never shows up a device, so it won't even get to adb at all.
Hey Ktoonsez, thanks for trying man. If you can think of anything else to try or any kind of log to pull please let me know I am more than willing to help. I sure wish we could get this kernel running on TW 4.1.2. I love your kernel, and it gave me unbelievable battery life, but I don't want to go back to 4.1.1, so hopefully one day you can figure it out man.
I even wiped everything back to factory then just installed the system.img only then your kernel with no data.img to see if it was hanging on data or something, and I still got the boot loop. I have exhausted my brain on this, and I can't think of anything else.
If you like my work, donate with this link: http://forum.xda-developers.com/dona....php?u=4325945
_____________________________
Do NOT flash my kernels if you are allergic to AWESOME!!!!!!!!!!!!!!!
_____________________________
Have you tried the 4.1.1 just for the hell of it? That was stock ramdisk so I believe it is not the ramdisk, so that means code which is very rare. Have to start completely over
LMAO.... Your 2/9 version of the 4.1.1 kernel boots the phone!
So far it is still running smoothly/fast. Should I look for any errors, or should I expect any errors or lack of features using the 4.1.1 kernel?
LMAO.... Your 2/9 version of the 4.1.1 kernel boots the phone!
So far it is still running smoothly/fast. Should I look for any errors, or should I expect any errors or lack of features using the 4.1.1 kernel?
Nothing really, it was just some updated drivers really, I believe freeza listed them.
Try the one above too
If you like my work, donate with this link: http://forum.xda-developers.com/dona....php?u=4325945
_____________________________
Do NOT flash my kernels if you are allergic to AWESOME!!!!!!!!!!!!!!!
_____________________________
Your "C" version (the last one you posted) of the MA6 4.1.2 kernel boots my phone. What did you change on it, I'm curious?
Its 2/9 kernel code with new ramdisk, you have gtalk? I want to merge in some stuff slowly if you feel like flashing a bunch of times? PM if you want to do it
If you like my work, donate with this link: http://forum.xda-developers.com/dona....php?u=4325945
_____________________________
Do NOT flash my kernels if you are allergic to AWESOME!!!!!!!!!!!!!!!
_____________________________
Your "C" version (the last one you posted) of the MA6 4.1.2 kernel boots my phone. What did you change on it, I'm curious?
Quote:
Originally Posted by ktoonsez
Its 2/9 kernel code with new ramdisk, you have gtalk? I want to merge in some stuff slowly if you feel like flashing a bunch of times? PM if you want to do it
You both rock! Nice work guys, do wjat you have to to get it golden ktoonsez, we ALWAYS love the underwear you add in. Lol.
Its 2/9 kernel code with new ramdisk, you have gtalk? I want to merge in some stuff slowly if you feel like flashing a bunch of times? PM if you want to do it
U know you have all of team Kernelizers to test and help you buddy
President of {Team Kernelizers}
Im Gman and I approve this message
This is entry number one in a series of articles about tools for app developers, … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?