-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues booting TWRP 2.8.2.0 (hammerhead) #1
Comments
I have a Nexus 5 with Android L. I connect the N5 to my PC (Windows 8.1) with a USB cable and in the command line I write:
and I wait till I see the fastboot screen in the N5. The I write:
It starts ok. But with the last TWRP recovery, don't work:
At first N5 starts ok, I see the blue screen, but then restarts in Android L.
I've opened a thread in XDA: http://forum.xda-developers.com/google-nexus-5/help/load-twrp-2-8-fails-t2959998 Thanks !! |
is this problem fixed? is secure to install the latest version? |
Should be -- I don't think I've had this problem. Dowgrading is simple if you do come across another showstopper. |
I also have the problem with the reboot-loop with 3.2.1-1 2.8.1.0 and 2.6.3.4 also don't work, it doesn't reboot but goes in a "teamwin" screen loop. |
A number of users have reported issues booting TWRP 2.8.2.0 (lge_hammerhead). Although TWRP will successfully boot for the first time after flashing, all other instances will fail. Upon attempting to boot to recovery, the device will automatically reboot to system once the user reaches the TWRP "curtains" splash screen.
This issue has been most commonly reported by users running the stock LRX21O ROM, including those that updated via OTA or by (clean) flashing the factory images. Error reports typically involve SELinux set to Enforcing, with either the stock kernel, Chainfire's modified stock kernel (eg. as achieved using CF Auto-Root), Franco kernel, and SuperSU versions 2.20 to 2.27 (beta).
Users have reported flashing TWRP via fastboot, Flashify or with a flashable zip in recovery.
Downgrading to TWRP 2.8.1.0 will typically solve the issue.
The text was updated successfully, but these errors were encountered: