that would be awesome, as it stands there is bugs i have no idea whats going on as i have no logsIf you don't have a log yet I will try this now.
that would be awesome, as it stands there is bugs i have no idea whats going on as i have no logsIf you don't have a log yet I will try this now.
thats what i've been trying but i have not been able to connect while in recovery.flash twrp test 5
tap around in twrp for a min
adb pull /tmp/recovery.log
the last two need to be in recovery
![]()
I have not messed with twrp much is adb access generally enabled by default?well crap :/ since when you reboot /tmp/ gets wiped
it should be :/I have not messed with twrp much is adb access generally enabled by default?
We need to modify the recovery init. I'll try to tonightwell crap :/ since when you reboot /tmp/ gets wiped
reboot the device and dothats what i've been trying but i have not been able to connect while in recovery.
Daemon starts but error: device not found from adbreboot the device and do
adb pull /cache/recovery/last_log
hopefully that will help us![]()
did you enable usb debugging?Daemon starts but error: device not found from adb
see if this is what you needreboot the device and do
adb pull /cache/recovery/last_log
hopefully that will help us![]()
yes t is now please remove this file as it has info you may not wnat publicsee if this is what you need![]()
I was getting that a lot. Had to unplug and connect again.Daemon starts but error: device not found from adb
Yes sir. Do you need another? If so, I'll keep trying.did you enable usb debugging?
Thanks
No matter what I do can't get the dmesg to write to file.i need a dmesg of the device booting up
adb reboot
adb wait-for-device shell su && dmesg >/mnt/sdcard/dmesg.txt
when teh device fully boots open the lockscreen and then you can end teh log by holding control and hitting c in the terminal/cmd