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!
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)
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?
My LG-E970 (AT&T) will not boot. What happened was FreeGee had an error part way though and I did not think anything of it. I had already successfully rooted my phone hours earlier and all seemed to be working well. I turned my phone off for the night and when I went to turn it back on it would not boot. It went into what it called "Demigod" mode, from which I can access Fastboot, but the recovery appears to be broken as well. I have tried accessing Fastboot to re-flash the recovery but neither Fastboot or ADB can even find the device. I've tried every USB driver I can find and nothing seems to help. Device Manager shows when it's connected under Unknown Devices and it names it Android, but ADB and Fastboot don't see it. All I can see on the Fastboot screen is the following information:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 16GB
HW VERSION - rev_10 (168)
BOOTLOADER VERSION - MAKOZ10f
BROADBAND VERSION - N/A
CARRIER INFO - NONE
SERIAL NUMBER - 003fa9505095f3a5
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Any solutions would make me incredibly grateful. I have tried everything I can think of and I hate having to ask for help, but I see no other choice at this point.
fyrestorm90 said:
My LG-E970 (AT&T) will not boot. What happened was FreeGee had an error part way though and I did not think anything of it. I had already successfully rooted my phone hours earlier and all seemed to be working well. I turned my phone off for the night and when I went to turn it back on it would not boot. It went into what it called "Demigod" mode, from which I can access Fastboot, but the recovery appears to be broken as well. I have tried accessing Fastboot to re-flash the recovery but neither Fastboot or ADB can even find the device. I've tried every USB driver I can find and nothing seems to help. Device Manager shows when it's connected under Unknown Devices and it names it Android, but ADB and Fastboot don't see it. All I can see on the Fastboot screen is the following information:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 16GB
HW VERSION - rev_10 (168)
BOOTLOADER VERSION - MAKOZ10f
BROADBAND VERSION - N/A
CARRIER INFO - NONE
SERIAL NUMBER - 003fa9505095f3a5
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Any solutions would make me incredibly grateful. I have tried everything I can think of and I hate having to ask for help, but I see no other choice at this point.
Click to expand...
Click to collapse
I hope you backed up your EFS. Mine was borked by the broken FreeGee that I ran the other night.
I was able to install a custom recovery from Linux by adding a udev rule and restarting the udev service. (Unlike Windows nonsense, this doesn't require a complete new packaging of the driver.)
If you're willing to tackle some Ubuntu (which is easy), I can give you a step-by-step to getting a custom recovery on your phone. It will probably work even from a live CD without even having to install Ubuntu to your harddrive.
Have you read and tried about the LGNPST method of flashing the TeenyBins and installing TWRP recovery ??
I think it should work , as I had the same issue as of today and with the help of those I was at least able to install TWRP recovery. Haven't tried flashing any ROM but I think it should work.
------------------------------------------------------;
http://forum.xda-developers.com/showthread.php?t=2230994
Please read it carefully.You'll find all the information in the thread , let me know if I can be of any help.
Here's my thread for the issue I had today , it seems similiar to your's.
http://forum.xda-developers.com/showthread.php?t=2557320
Phone model : Huawei G610-U20
Hey guys, I'm new to this ADB stuff and root editing files.
What I did was try to run an nvidia shield game but since it wont launch I thought that it's probably my build.prop now allowing me to run it since some other guy made it run because he changed his build.prop. When i applied the changes and restarted the phone, I got stuck on bootloop, usb debugging is disabled, no CWM installed, I can't flash the update.app in my SD card through download mode, although I can get to recovery mode. ADB can't detect my device. Is there anyway to fix this problem maybe through flashing from a third-party app such as livesuite or something? Thanks in advance.
Hello Ive got a bit of a problem actualy a few with my pipo U1 Pro
I installed CWM V6.o.3.1 and rebooted fine, pipo boot image was normal, then i installed from ext SD card Decontaminat V3.1
after install the screen was Split at 2/3 and touch orintation was off with buttons in wrong corners
so i read alot found change in build.prop (ro.sf.hwrotation=270) from 270 to 0 and reinstalled form ext sd card
all it fixed was position of touch screen the image of ui was still split 2/3 and out of rotation.
i reinstalled CWM fron ext sd card reboot ant the cwm recovery is straigt on the vertical and the android shows in center of screen, but ther is a fine line showing where the screen was split in the os.
after reboot the os is still split 2/3 image i have to us the show touch function to navigat the touch field to make thins work
i had TNT pipo u1 pro.img installed before and was rooted worked fine but latly had a few minor problems with it so i desided to chand up a bit.
second problem is i cant get ADB , android studio or rkbatch tools to find my tablet, usb debugging is on, tried the load from adb sideload function in cwm
im running linux mint 17 added udev.rules rebooted every thing many time s swapped usb plugs cords you name it.
as it is the tablet works but the ui is buggered up and touch is off
any help would be verry appricated
mike
May be bricked now ?
I have the pipo stuck in what might be a boot loop?
just says decontaminate with a split screen on bootup shows pipo image then goes to decontaminate screen and nothing.
lsusb shows device { Bus 002 Device 009: ID 2207:0006 }
shows Android device in file manager But Error unable to mount android unable to open mtp device
pushing the buttons '' esc, +vol then power gets nothing.
pushing +vol, power gets nothing
incerting usb and pushing +vol gets nothing
only thing gets anything is push and hold power, CWM is not working cant boot to cwm
tried a bootable sdcard still no boot
was a nice Tablet till decontaminat screwd the screen up
got recovery yeah !!!!
found a way into the cwm recovery through adb.
i added a line into the file here.
/yourusername/.android/adb_usb.ini
its a hidden file added a simple line as root user
0x2207
saved file and rebooted computer.
will post again if i can recover the pipo.
buggered
had total access to the pipo.
i used flash_image to install freaktbs ryley rom for the pipo u1 pro.
now im stuck in a worse position. the kernal.img was not for the pipo.
he was playing with a another tablet and left its kernel.img as kernel.img and had pipo kernel as 1kernel.img
so im stuck with no touch support on the screen and its not defaulted to usb debug mode.
i can see the button acking to allow debug when i connect to usb on linux but no access to touch.
also the rom didnt have any tools for adb installed in recovery /system/bin.
no adb shell support.
only access is adb ls /
to read files and push pull commands.
any ideas on how to edit the default.prob make it stick through reboot and get it to debugg after reboot ?
this sucks MR.RYLEY built a bad rom I was almost into my pipo again.
my guess is the decontaminat rom was using a similar kernel to ryley to get the screen all buggered up.