TeamWin / Team-Win-Recovery-Project

Core recovery files for the Team Win Recovery Project (T.W.R.P) - this is not up to date, please see https://github.com/TeamWin/android_bootable_recovery/
http://twrp.me
1.96k stars 741 forks source link

twrp-3.3.1-0-cheeseburger fails to boot. #1467

Open F-i-f opened 5 years ago

F-i-f commented 5 years ago

Device codename: cheeseburger TWRP version: 3.3.1-0

WHAT STEPS WILL REPRODUCE THE PROBLEM?

WHAT IS THE EXPECTED RESULT?

WHAT HAPPENS INSTEAD?

ADDITIONAL INFORMATION

The device is running OOS 4.5.15 (Nougat), and is not formatted for Treble since that's an OOS 5.x (Oreo and later) feature. Versions 3.3.0-0 and 3.3.0-1 are equally broken, won't boot and exhibit the same symptoms. Version 3.2.3-0 works flawlessly.

/tmp/recovery.log: TWRP didn't boot, I wasn't able to get a /tmp/recoverly.log from a live TWRP run. After the failed recovery boot, and booting into Android, the /cache/recovery directory was created by the failed recovery boot, but there were no files in the directory. dmesg: Since TWRP didn't boot, I wasn't able to get the dmesg output from TWRP.

Vince1171 commented 5 years ago

same here

blieque commented 5 years ago

Can confirm. All three 3.3.x releases give me a black screen with the notification light. 3.2.2 and 3.2.3 also fail to properly detect /data and show the decryption unlock screen.

I'm running OxygenOS 5.1.4.

Vince1171 commented 5 years ago

twrp-3.3.1 works with the latest oxygenOS version (9.0.x)

skbhati199 commented 5 years ago

How to fix

E:\obu driver\Quectel_Smart_EVB_G2_Kit_Support_Package_V1.2\Tools\adb&fastboot\adb>fastboot.exe boot TWRP.img downloading 'boot.img'... OKAY [ 0.874s] booting... FAILED (remote: unknown reason) finished. total time: 1.559s

blieque commented 5 years ago

@skbhati199 What device are you using? Also, where did you get that version of fastboot? Try downloading ADB and fastboot using this tutorial: https://www.xda-developers.com/what-is-adb/