Dtb not found twrp что делать
Unable to flash TWRP (remote: dtb not found)
Breadcrumb
Higgings
Member
When I try to flash TWRP (via «fastboot flash recovery twrp.img» then «fastboot boot twrp.img») I receive the following error:
Downloading ‘boot.img’
OKAY [1.477s]
booting.
FAILED (remote: dtb not found)
finished. total time: 1.534s
I’ve tried manually booting it into recovery with power button and volume down but it just freezes on the oneplus logo where I have to turn off and on again.
Any help is greatly appreciated!
Higgings
Member
domuzy
Member
tangiers
Senior Member
I tried this recovery (I had the same problem as the OP) but although I can boot into twrp, I get stuck on the oneplus logo if I try a normal boot?
Sent from my Nexus 9 using XDA-Developers mobile app
tangiers
Senior Member
I managed to get it working by flashing CM after flashing the recovery.
Sent from my Nexus 9 using XDA-Developers mobile app
pitrus-
Senior Member
Next time, correct command is the following:
Fastboot flash recovery twrp.img
Spannaa
Recognized Contributor / Themer
Next time, correct command is the following:
Fastboot flash recovery twrp.img
Actually, fastboot boot twrp.img boots the TWRP image without flashing it.
fastboot flash recovery twrp.img flashes the TWRP image to the recovery partition.
Both are valid commands and have their uses.
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn’t be used.
pitrus-
Senior Member
bhanuodin
New member
Similar problem while flashing recovery
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
pitrus-
Senior Member
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
bhanuodin
New member
pitrus-
Senior Member
The bootloader (also called fastboot) comes with the original ROM. In your case you’re already on the newer bootloader since you flashed OOS3 which means you will have to flash recoverys and ROMs compatible with this newer bootloader.
Also you can’t run ROMs not compatible with this newer bootloader (which means pretty much any ROM that’s not using the official Cyanogenmod source tree for building). That is except for OOS3 or newest HOS of course since these are made for the newer bootloader.
However I would say the error message you get might be caused by bad cable, faulty driver setup, faulty fastboot tool version or in worst case damaged partition layout on phone. The last one can be fixed by the Qualcomm OOS2 factory restore solution.