Yes, at boot (as in I press and hold the button for about 18 seconds, the screen goes blank, then put's up the note splash image/logo.
Is this the first time I've seen this version of the console log? Yes, mostly. If you look at previous pastebin log in this thread, it would get up to around 13 seconds and reboot itself, blank the screen, start the boot process all over.
With note2-rec.img or recovery.img it "boots" but then get's stuck. Whereas before it did the bootloop.
I completed a recovery flash from the update.npx (zip) file and the misc-recovery.prc from post #47. Looks the same as using the note2-rec.img.
[ 18.758023] mdss_mdp_epdc_thread: mdss_mdp_epdc_thread(): start!!
[ 18.763253] mdss_mdp_epdc_thread: mdss epdc open fb0.
[ 18.768133] ################ fb_blank(): caller = mdss_mdp_epdc_thread+0x110/0x920, blank=0
[ 18.786029] ################ fb_blank(): END!
[ 23.049206] random: nonblocking pool is initialized
no response from adb commands
I see references to Ubuntu in the bootup log. This line was in previous bootlogs
Linux version 3.18.120-perf-gce29d74-dirty (onyx@onyx-ubuntu)
This line was not
OEM_IMAGE_VERSION_STRING=ubuntu
It's at the top. If you look at the recent
https://justpaste.it/db6rl everything from
Quote:
|
Format: Log Type - Time(microsec) - Message - Optional Info
|
to
Quote:
|
Android Bootloader - UART_DM Initialized!!!
|
is new.