Decided to finally change rom as my K40 pro was getting really slow, and I'm afraid I might have actually bricked it this time.
I was using this guide(https://rentry.co/flashing_guide_haydn) but "fastboot boot recovery.img" was just booting back into the system, and "fastboot flash recovery recovery.img" wasn't working either. Eventually I ended up trying "fastboot flash boot_b twrp.img" and it showed the twrp splash screen but just kept bootlooping into that.
I decided to try the same command but with orangefox and now it's stuck in fastboot. The phone shows up as ????????? when I do fastboot devices. When I hold the power button it shows the pixel boot
Related
My OPX is running marshmallow 6.0.1 oxygenos 3.1.3 for the past 1 week or a bit more after the OTA update.
I had unlocked the bootloader 2.5 - 3 weeks ago when it had lolipop but I didn't install twrp. It is still unlocked after the update obviously (i have properly checked the oem unlock by the fastboot command fastboot devices oem and advanced reboot). I downloaded the latest twrp version for the OPX: twrp-3.0.2-0-onyx.img (link: https://dl.twrp.me/onyx/) from the official site. I renamed the file to "twrp" In fastboot mode, I used the command: fastboot flash recovery twrp.img. It flashed successfully, as the 2 "OKAY"s appeared. After flashing was over, I used the recovery boot command: fastboot boot twrp.img which FAILED and gave an error- remote: dtp not found. Then I switched off the device using the power button and the tried the recovery mode combination i.e power button + volume down. Although the phone started, it didn't boot into the recovery and got stuck at the "oneplus powered by android" screen. I tried the combination again after which it switched off and returned to and got stuck at that same screen. Frustrated, I rebooted into the OS using the fastboot reboot command and booted into the recovery using advance reboot. To my dismay, I still had the stock recovery. The only difference in the recovery was that it wanted me to choose a language and then it started, just like when i had first booted into the recovery after buying the phone many months ago. I have tried this whole thing 2 times but with no luck! The twrp recovery flashes but fails to boot by any means, be it that fastboot command, the recovery mode combination after flashing successfully (and enter the boot command which fails) where it gets stuck on "oneplus powered by android screen" and rebooting into OS and booting into recovery using advance boot where the OS has already replaced twrp with the stock recovery.
PLS HELP!!
This is the guide I followed- https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
And also, I used this video for reference- https://www.youtube.com/watch?v=RwYmyXyJeww
I have a LeEco Le Pro 3 phone firstly i tried to root it using the tutorial i found here on how to flash the TWRP Recovery & Root the Le Pro 3 device. I followed the instructions and got to flashing the twrp recovery successfully but it wouldn't boot to the twrp recovery using the power+volume up button neither would it boot up normally the LeEco logo would just flash and it went blank. I eventually got it to boot to the recovery by putting it into the fastboot mode and using the adb fastboot method by typing "fastboot boot recovery recovery.img" i then tried to install the supersu and it install but it still wouldn't boot up normally nor to the twrp recovery still had to use the adb fastboot method. I made the mistake of not doing a back up before I did the wipe. I then figured maybe the OS got corrupted so I downloaded a stock rom and use adb sideload to get it on the storage of the phone. i made another mistake of not wiping the data before i restarted the phone now i can only get it into fastboot mode and i can see it when i do a "fastboot devices" check but it will take no other command as the bootloader is locked. Is there any solution to get the bootloader unlocked again. when i try to unlock it using the adb command "fastboot oem unlock-go" it return the reply "(failed remote oem unlock is not allowed)" fastboot error command failed. Please any help would be greatly appreciated
I wiped my phone to change the rom, but I couldn't find the rom file, so I restart the phone and get stuck at mi logo. I can enter into fastboot, but not in twrp. My computer recognizes fastboot through "fastboot devices", but I can't use "fastboot reboot recovery", I get the output "fastboot: usage: unknown reboot target recovery". What can I do?
Hey,
if fastboot works, you should be able to reboot to EDL and flash stock system image with Xiaomiflash.
Good luck!
HI guys my phone is stuck on fastboot,
its showing the current image(boot/recovery) have been destroyed and can not boot
pressing volume + power put it into fastboot and it shows in adb "fastboot devices" i tried to install custom recovery with "fastboot boot recovery.img" and its not working picture attached and i tried to boot img but same error shows FAILD(remote: unknow command)
use command fastboot flash recovery recovery.img
before installing rom please check vendor inbuilt or not so that after flashing u will be stuck in boot again
TLDR: phone stuck at boot screen. Still can access fastboot mode and twrp recovery mode.
I shouldn't have dived into these stuff without proper knowledge. I wanted to root my phone (redmi note 5a lite) so I unlocked bootloader and ran fastboot flash recovery (attach .img) with bugjaeger app and otg. But after pressing volume up + power, the stock recovery was showing. So I ran fastboot flash recovery (attach .img) again. Still didn't work. So I saw a random tutorial (dumb idea) and renamed the img file to recovery.img. then I ran fastboot flash recovery (attach recovery.img) then ran fastboot boot (attach recovery.img) then twrp opened and I thought everything was good. Then I clicked reboot>system in twrp and my phone is stuck on boot screen. Long clicking the power button gives a little screen off and on and it gets stuck at boot again. I still can access fastboot mode and twrp recovery mode by draining battery and then using bugjaeger app and otg.