Hi druids of android,
I have an unlocked Asus TF300 with CM-11 and TWRP 2.8.1.0
Recently I’ve updated CM via OTA to the latest available snapshot and after that I’ve done factory reset from android UI (I lost my password so I decided to create a new g. account)
Now my tablet after reset shows Asus logo, 4 penguins and it stucks on blue striped treamwin splash screen.
Splash screen flickers every 6s. I see the device by lsusb, adb devices for 5 seconds, after the device disappears for a while and it backs again. I can do some adb commands like adb shell ls, cat, rm but I can’t do any fastboot command to flash recovery or system.
Any fastboot call ends with ‘waiting for device’. I call it through sudo and I’ve configured udev according to wiki.cyanogenmod.org/w/UDEV
I’ve tried restart tablet with power+volUp, power+volDown, with the same results descibed above. PaperClip+VolUp turns the tablet off.
I’ve found /cache/recovery/recovery.log file. (can’t attach whole file because I’m a fresh member)
Partitions were mounted and the loop begins after:
I have an unlocked Asus TF300 with CM-11 and TWRP 2.8.1.0
Recently I’ve updated CM via OTA to the latest available snapshot and after that I’ve done factory reset from android UI (I lost my password so I decided to create a new g. account)
Now my tablet after reset shows Asus logo, 4 penguins and it stucks on blue striped treamwin splash screen.
Splash screen flickers every 6s. I see the device by lsusb, adb devices for 5 seconds, after the device disappears for a while and it backs again. I can do some adb commands like adb shell ls, cat, rm but I can’t do any fastboot command to flash recovery or system.
Any fastboot call ends with ‘waiting for device’. I call it through sudo and I’ve configured udev according to wiki.cyanogenmod.org/w/UDEV
I’ve tried restart tablet with power+volUp, power+volDown, with the same results descibed above. PaperClip+VolUp turns the tablet off.
I’ve found /cache/recovery/recovery.log file. (can’t attach whole file because I’m a fresh member)
Partitions were mounted and the loop begins after:
Code:
SELinux contexts loaded from /file_contexts
Full SELinux support is present.
I:Boot command: boot-recoveryI’m fighting with it a few evenings 
and I decided to ask You for help.