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)
Related
Pls help flashing boot.img for CM7 on Xperia Ray ("waiting for device"- error)
Hello,
I am desperately trying to get CM7 onto my Ray.
I got to the last point, but am severely stuck here
When I try to flash the boot img by <flashboot -i 0xfce flash boot boot.img>
it's always stuck at <waiting for device>
I already unlocked the phone using the test point method successfully and am Using the driver provided in the CM7 Wikia from the page about installing the android sdk and fastboot.
Can anyone help?
My OS is Win 7 Enterprise 64-bit
I believe that this should be in the General section, not the Development area.
While it's here though:
Whilst the phone is powered off, hold down Vol[+] as you insert the USB cable to your Ray, it should light up blue around the home button. If it doesn't you've not unlocked the bootloader properly.
If the blue light is there it would seem you've not got the correct drivers installed. Uninstall the ones currently in use and re-install.
The blue light shows up and I am certain the bootloader is unlocked as my log in S1Flash tool was 100% identical to that of the poster.
I tried several drivers to no avail, can you tell with one you used for your Ray or if you don't own a Ray which one I should use?
Thanks.
Also: Should the Phone show up ad Android ADB Interface in device manager?
Posted a reply in the proper thread, where you've also asked this question:
http://forum.xda-developers.com/showthread.php?t=1285977&page=4
Mycorrhiza said:
Hello,
I am desperately trying to get CM7 onto my Ray.
I got to the last point, but am severely stuck here
When I try to flash the boot img by <flashboot -i 0xfce flash boot boot.img>
it's always stuck at <waiting for device>
I already unlocked the phone using the test point method successfully and am Using the driver provided in the CM7 Wikia from the page about installing the android sdk and fastboot.
Can anyone help?
My OS is Win 7 Enterprise 64-bit
Click to expand...
Click to collapse
you must have a pure system there's none other AndroidPhone drivers.And install drivers from "flashtools" or other way.
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
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?
Hi all
Let me expose my problem :
I got an unlocking key from sony ; when I use it with
Code:
fastboot oem unlock 0xDEVICESKEY
, the boot process loops : I can see the sony logo, then the Xperia logo, then a few colorwaves, which in turn stalls for a second or two, and then the device reboots.
I tried to flash the device with kernels adapted to SGP312. Flashing succeeds if I unlocked just before (if I want to re-flash I have to re-unlock), but the device then doesn't boot at all.
I could never access recovery, but I read this thread saying that's normal with stock kernel. Though I couldn't access it having flashed any other kernel.
Thus I'm locked into android.
Can anyone help ? I discussed this with Mamenyaka, he suggested I posted my issue here. I tried to find a similar case in the forums but couldn't figure anything close to this.
I finally found a solution to my problem : I unlocked the device using flashtool-0.9.11's gui procedure, instead of flashtool's fastboot. It succeeded and I can successfully flash anything I want on the device.