Hi all,
I've successfully compiled the Linux kernel for Android from source, and wish to use it on my phone now, however after flashing it to the boot partition of my device and a reboot, my phone stucks at the init vendor logo, seemingly the the kernel is not properly loaded.
Is there any way that I can debug the boot process in Android?
Thanks,
ryanli
Related
Hi guys,
I am trying to build a custom kernel, and am having some problems debugging. I have successfully (i.e no errors built a zImage using HTC sources and packed it into a boot.img, but when I flash it I get nothing... just sticks at the splash screen.
I have tried getting a logcat but it just says -waiting for device- and never says anything else. Anyone know how I can see what's wrong?
the adb is not enabled when booting. i think its ramdisk problem (my phone is Xperia X8)
Im porting newer kernel version for my device and I after succesful compilation (using config from old version with all new stuff added by make oldconfig) I have a problem.
When I flash kernel to the phone (LG p350) it does not boot (make infinite loop of reboots) before adb deamon is started and I cant get any message what the heck is wrong.
How could I get some debug msg by, for instance, saving them to SD card or phone memory, or mby route them via USB?
Thanks for any help!
I'm currently trying to develop a custom ICS Rom for the Thinkpad Tablet.
One of the problems I'm encountering is, that I'm unable to debug the boot process.
Often, the device hangs on the Vendor logo, suggesting that something went wrong during the boot, but without any way to see what exactly is going on, I can't resolve the problem.
The device doesn't register on my USB-Port until very late in the boot process (i.e. when the Interface is already visible), so I can't see the logcat during boot.
Is there a way to disable the boot animation and see the actual kernel messages?
Or is there a setting for the init.rc, so that I can access the kernel messages either via ADB or directly via a serial console?
I recently installed Android bootloader interface to make possible rooting of my phone. However, can I reverse somehow the process and remove the android logo and bootloader interface?
holocen said:
I recently installed Android bootloader interface to make possible rooting of my phone. However, can I reverse somehow the process and remove the android logo and bootloader interface?
Click to expand...
Click to collapse
Some more information would be useful (your device and guide you used etc).
I am also guessing you mean removing a custom bootloader? You can not remove the bootloader, unless you want a device that will not boot.
The bootloader works in much the same way as your computers BIOS and is not something that can be removed.
see: http://forum.xda-developers.com/showthread.php?t=1466228
"Bootloader:This small program's only job is to load other data and programs which are then executed from RAM.Often, multiple-stage boot loaders are used, during which several programs of increasing complexity load one after the other in a process of chain loading."
My device is ZTE Blade 3. I installed fastboot drivers and after that my ABI show up as green android logo. I made this video:
I used this drivers for fastboot:
Code:
http://www.filefactory.com/file/6et8eo31fq5v/n/fastboot_driver_B3_zip
These are files for rooting of my phone:
Code:
http://www.filefactory.com/file/35dokg7x0vkj/n/B3_root_NGT_zip
I installed modified Google USB driver - driver for fastboot, I guess? I successfully rooted and installed recovery coded for Blade 3. When I try to revert the original stock ROM of my phone, the only thing that is different is green android logo which boot shortly now but there was not before. That logo comes up after implementing fastboot drivers as in video above.
Anyone, please?
Sent from my ZTE BLADE III
Hi, I am trying to do some low level performance testing related to device processor cores through adb which I feel it is affected by Android background services and system stuff.
As I know that the Android boot sequence stages are as follow:
1.Execute Boot ROM code.
2.Execute the boot loader.
3.Load the Linux kernel.
4.Launch Zygote, which initializes the Dalvik VM.
5.System server which loads the Android system.
So my question is how can I interrupt this sequence to force it stop on stage 3 to load Linux kernel. This can help me implement my intermediary performance testings before loading again Android system.
Does Fastboot or Clockworkmod recovery can help here and load my device to a kind of Linux kernel?
Any hint will be appreciated.
Thanks.
mosed said:
Hi, I am trying to do some low level performance testing related to device processor cores through adb which I feel it is affected by Android background services and system stuff.
As I know that the Android boot sequence stages are as follow:
1.Execute Boot ROM code.
2.Execute the boot loader.
3.Load the Linux kernel.
4.Launch Zygote, which initializes the Dalvik VM.
5.System server which loads the Android system.
So my question is how can I interrupt this sequence to force it stop on stage 3 to load Linux kernel. This can help me implement my intermediary performance testings before loading again Android system.
Does Fastboot or Clockworkmod recovery can help here and load my device to a kind of Linux kernel?
Any hint will be appreciated.
Thanks.
Click to expand...
Click to collapse
I'm not 100% on the testing you are trying to do but what about installing Debian to your device, this would not use dalvik and be free from android all together?
Or remove Google services or whatever background stuff you feel may be messing with your tests?
You can use fastboot to force boot a kernel, if zimage and ramdisk are packed into an image then
fastboot boot nameofkernel.img
For more info on fastboot see here
http://forum.xda-developers.com/showthread.php?p=41374534
From my minimal testing and messing with bootloaders I can say it is possible to solder a UART connection to the logicboard and connect it to PC via a serial port (may need a device like an arduino as a bridge) where you can stop the bootloader in different sequences, this being you can trigger debugging modes that the bootloader has. This of course differs in each device but it is possible to enter a debug mode and shell terminal (not adb) before the bootloader finishes its process.
But in reality, depending on what your attempting you probably need a fully booted device so if your not interested in using a hex editor to force your bootloader to do what you want (which would probably take a lot of work) try fastboot to force boot whatever kernel you made or probably just flash Debian to your device
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
I'm not 100% on the testing you are trying to do but what about installing Debian to your device, this would not use dalvik and be free from android all together?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I think the idea of installing Debian/Linux distro to the device is interesting so that I can get red of Dalvik.
But whenever I try to find a suitable Debian/Linux kernel to install on my device, I found that it will be installed on top of the current Android system ( same as Virtual machine). So Android and Dalvik are still there!
So where can I find a Debian/Linux kernel that will replace Android, not to set on top of it.
Thanks
How to modify bootloader to load kernel and ramdisk from SD Card?
demkantor said:
From my minimal testing and messing with bootloaders I can say it is possible to solder a UART connection to the logicboard and connect it to PC via a serial port (may need a device like an arduino as a bridge) where you can stop the bootloader in different sequences, this being you can trigger debugging modes that the bootloader has.
Click to expand...
Click to collapse
Can we modify bootloader to load kernel from some location other than eMMC? I'm talking in this context: https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171