Originally Posted by Maldune

v0.2 doesn't boot for me.

Using Skrilax v6 bootloader I can't boot v0.2 while v0.1 works fine, both flashed from fastboot.
I also tried flashing v0.2 from v0.1 recovery, same results.

It works fine on my A500 with V6 bootloader.

+1

Envoyé depuis mon A500 avec Tapatalk

Hmm... Could it be that I'm using a secboot image? <- nope, just erased it and it still will not boot

Is there a way for me to debug why it won't boot?

Originally Posted by Maldune

Hmm... Could it be that I'm using a secboot image? <- nope, just erased it and it still will not boot

Is there a way for me to debug why it won't boot?

Yes:

With v0.1 installed in recovery:

Boot v0.2 with fastboot (ie: fastboot boot <recovery.img>)

It will presumably fail.. reboot to the working recovery. (If you need to power off boot as quickly as possible)

Run 'adb shell cat /proc/last_kmsg > /tmp/kmsg.log'
Then 'adb pull /tmp/kmsg.log'

Send a copy (optionally masking out your tabs serial numbers)

Also to confirm you have an a500 or other model?

Sent from my Galaxy Nexus using Tapatalk 2

Originally Posted by ezterry

Yes:

With v0.1 installed in recovery:

Boot v0.2 with fastboot (ie: fastboot boot <recovery.img>)

It will presumably fail.. reboot to the working recovery. (If you need to power off boot as quickly as possible)

Run 'adb shell cat /proc/last_kmsg > /tmp/kmsg.log'
Then 'adb pull /tmp/kmsg.log'

Send a copy (optionally masking out your tabs serial numbers)

Also to confirm you have an a500 or other model?

Sent from my Galaxy Nexus using Tapatalk 2

Comfirming that I have an A500

I've done what you asked but I don't see /proc/last_kmsg. I've tried booting v0.2 from fastboot and leaving the tablet online for the following to happen.


/var/log/messages
May 21 14:35:43 fedora kernel: [409004.624034] usb 2-2: new high-speed USB device number 39 using ehci_hcd
May 21 14:35:43 fedora kernel: [409004.738759] usb 2-2: New USB device found, idVendor=0502, idProduct=3201
May 21 14:35:43 fedora kernel: [409004.738765] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 21 14:35:43 fedora kernel: [409004.738768] usb 2-2: Product: Fastboot
May 21 14:35:43 fedora kernel: [409004.738771] usb 2-2: Manufacturer: NVIDIA Corp.
May 21 14:35:43 fedora mtp-probe: checking bus 2, device 39: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2"
May 21 14:35:43 fedora mtp-probe: bus: 2, device: 39 was not an MTP device
May 21 14:35:48 fedora kernel: [409009.768338] usb 2-2: USB disconnect, device number 39

$ fastboot boot A500PubRecovery_v0.2.img

/var/log/messages
May 21 14:35:59 fedora kernel: [409020.527030] usb 2-2: new high-speed USB device number 40 using ehci_hcd
May 21 14:35:59 fedora kernel: [409020.656290] usb 2-2: New USB device found, idVendor=0502, idProduct=3325
May 21 14:35:59 fedora kernel: [409020.656295] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
May 21 14:35:59 fedora kernel: [409020.656299] usb 2-2: Product: A500
May 21 14:35:59 fedora kernel: [409020.656302] usb 2-2: Manufacturer: Acer
May 21 14:35:59 fedora kernel: [409020.656305] usb 2-2: SerialNumber: xxxxxxxxxxxxxxxx

$ adb shell
error: device offline


My udev rules are not to blame, I've set them to 0666 for the time being.

I've also booted this image and then immediately shutdown the tablet once I got the booting... OKAY message. Same result, no /proc/last_kmsg.


$ adb shell
~ # cat /proc/last_kmsg
cat: can't open '/proc/last_kmsg': No such file or directory

Last kmsg is a ram buffer for kernel log messages. Usual a bad kernel will not fully boot and thus trigger a reboot after a few seconds.. at this point if you were ready holding the volume rocker to boot recovery when recovery boots its expected to see the previous kernels log.

I've also seen last_kmsg survive quick power offs but it quickly starts to get garbled as it is ram not persistent storage.

Currently I need a better idea what's happening on the tab.. the USB connections to the computer require something already working.

However that almost looks like the kernel/init portion of adb did start.. (ie USB active but adbd not responding)

Sent from my Galaxy Nexus using Tapatalk 2

Originally Posted by Maldune

$ adb shell
~ # cat /proc/last_kmsg
cat: can't open '/proc/last_kmsg': No such file or directory

All I can say is if you have not powered off your tab (or for less than 5 seconds) its likely the kernel will find its pervious log.

Either from your last sucessful recovery boot or the failed one.

When the kernel fails to find the log in the ram buffer it won't create the last_kmsg entry in the proc filesystem. (This means its being wiped since the last time power has been provided to ram, or you are using a kernel significantly than the stock or my near stock ICS kernels.)

Is there any other symptoms that may hint at the issue? Normal boot with 'fastboot boot' flashes the screen when the kernel is loaded into ram, then 5 or so seconds later enters the recovery screen. If something goes wrong initializing recovery I've seen it become a black screen in my testing but adbd was still active. (my own testing btw was on both the v4 and v6 unlocked boot loaders)

Everyone

Of the other 44 unique downloads besides Maldune, are there any issues booting v0.2?

Originally Posted by micky387

OK.
I want to know if it's possible to add the same app (a part of recovery)
Thanks

So,what do you think about my app ??
Thanks

Originally Posted by Maldune

v0.2 doesn't boot for me.

Using Skrilax v6 bootloader I can't boot v0.2 while v0.1 works fine, both flashed from fastboot.
I also tried flashing v0.2 from v0.1 recovery, same results.

Originally Posted by Skrilax_CZ

It works fine on my A500 with V6 bootloader.

Same here Maldune... v0.2 doesn't boot for me. Same exact setup as you. Tried flashing from fastboot, v0.1 recovery, nflash, and even tried Acer Recovery Installer... Freezes at "Booting recovery kernel image"

Originally Posted by ckarrow2

Same here Maldune... v0.2 doesn't boot for me. Same exact setup as you. Tried flashing from fastboot, v0.1 recovery, nflash, and even tried Acer Recovery Installer... Freezes at "Booting recovery kernel image"

well off you go to try and get a lask_kmsg
(may I recommend flash v0.1 assuming it worked, use the adb command 'adb shell reboot bootloader' then when the fastboot screen arrives use 'fastboot boot <recovery>' to boot v0.2)

assuming it still fails: look carefully, you want to hold power just long enough that the power white LED turns off, then count to 2 and quickly turn it on booting to recovery to get the last_kmsg as indicated in my previous posts.

This way you ought to see either the failed attempt or the previous boot of v0.1 .. the text will tell me which.