Thank You for the suggestion.
Actually, that is already enabled in my kernel, but it does not show in /proc for some reason.:crying:
Last edited:
Yeah. Thanks but I already know that.
I think that when I go into the recovery, the kmsg file will have the logs for szezso's kernel because I am using his cm11 ROM.
If I install my own recovery with the 3.4 kernel then the recovery may not work because the kernel crashes too early.
So I have to try to access the kmsg file from fastboot somehow.
This problem is very hard to solve. No booting. No debugging. No 3.4 kernel.
It just seems hopeless now without any debugging logs. I don't know what is going on in the background so I cannot make it boot. I think the kernel image is not being uncompressed, but I have tried to fix that problem buy correcting all physical addresses of the RAM required for the kernel to boot. What could I be missing?
It just seems hopeless now without any debugging logs. I don't know what is going on in the background so I cannot make it boot. I think the kernel image is not being uncompressed, but I have tried to fix that problem buy correcting all physical addresses of the RAM required for the kernel to boot. What could I be missing?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3Hi there guys.
As might know, I am trying to build 3.4 kernel for HTC Incredible S VIVO using kk_2.7-stable branch from CAF.
Right now, I am having some difficulties getting ADB working.
The problem is that I don't know how to get the serial number of the device, and how to enable adb. But, I have done a lot of work on this so I don't want to give up now. So, I need some help in getting ADB working. So, here is my repository:
https://github.com/rqmok/android_kernel_htc_vivo
Please see through that and let me know how I can get ADB working because without ADB I don't know what to do next.
If you fork and change the code then please test the change before sending me a pull request.
I hope to see this issue resolved.
Thank You.1
I'm assuming you used the command fastboot getvar all in fastboot? I'm pretty sure that yields serial number, that or does your computer not recognize your phone at all?
This belongs in general ._.1
I've done a lot of commits but my computer does not see the device at all. I don't understand why it is not able to see my device, but I think the I need to initialise the following in the kernel:
- androidboot.serialno
- androidboot.mode
- USB ID pin GPIO
The third one I can handle (I think), but I don't now how to grab the serialno and boot mode from the bootloader.1
You are one of the hopes of this community, so, Do your best buddy! We are all proud of you! :fingers-crossed:
New posts
-
-
General [HELP THREAD] Ask ANY Question. Noob Friendly.- Latest: SubwayChamp
-
-
