Unlocked bootloader, flashed twrp through fastboot, no errors, when I input fastboot boot recovery.img it didn't work, Failed (command unknown) tried booting into recovery manually through keys and stock recovery opened up. Tried flashing Orangefox, same error. What do I do?
dyush007 said:
Unlocked bootloader, flashed twrp through fastboot, no errors, when I input fastboot boot recovery.img it didn't work, Failed (command unknown) tried booting into recovery manually through keys and stock recovery opened up. Tried flashing Orangefox, same error. What do I do?
Click to expand...
Click to collapse
Use custom roms.
Or boot into recovery after flash, before Android boots.
Stock ROM always overwrite recovery with stock.
Sent from my ZenFone Max Pro M1 using Tapatalk
Related
SOLVED:
Hi,
I just bricked my MX4 after trying to update system image from 4.5.6 to 4.5.7 using this guide:
Extract I version update.zip
use sdat2img to create system image
dd system image to system partition on live phone and reboot.
I used the same procedure successfully before, x-updating 4.5.4A ti I then updating to 4.5.6I.
After updating to 4.5.7, the phone goes into an infinite loop of Meizu splash screen, Flyme balloon, reboot.
I can enter fastboot and official recovery, but can't flash any partition from fastboot.
The bootloader is still locked.
Does anyone have any advice for unbricking?
Update:
The bootloop suddenly froze up for long enough for me to use adb to push an update.zip to the "sdcard" root. Have now flashed 4.2.8A from recovery and booted the phone.
As I had to clear all data I will unlock bootloader before trying anything else.
Try do flash 4.2.8.2 with uboot.img modded (to reunlock bootloader) and reboot fastboot and tell me
bobslesbricoleurs said:
Try do flash 4.2.8.2 with uboot.img modded (to reunlock bootloader) and reboot fastboot and tell me
Click to expand...
Click to collapse
Hi,
I managed to push 4.2.8.2 to sdcard then do a normal recovery reflash.
Have now successfully unlocked using the .apk method.
Now I need to find out if I can use that unlocked bootloader to flash recent "I" firmwares, or if I can only flash the unfinished cyanogen (would like to wait 'til that's a bit more polished before using it.
Anyway. Happy to have my phone back!
Maybe that newest 4.5.7I need a new kernel so you'll need to update to 4.5.7A before flashing system.img or you can flash directly 4.5.7I but you'll need to use fastboot flash boot boot.img
If a rom/firmware needs a specific kernel it'll bootloop if you don't flash it
Can I flash 4.5.7 I now that I have unlocked bootloader and custom recovery? If I understand the unlock threads correctly, I think I will relock the bootloader, or even brick if I try to flash the complete update.zip. Can I flash system and boot partitions using fastboot?
Fully BRICKED.
Now I FULLY bricked it (no more recovery).
Had successfully upgraded to 4.5.7 "I" and was installing super su for full root, before disabling update, but had forgotten that I still had official 4.2.8 rom as update.zip on "sdcard" root.
rebooted to TWRP recovery for full su install and recovery found the update.zip and flashed it.
Result: Bootloop, No recovery, locked fastboot, no possibility to flash anything.
Aaargh!
Where do I find a 4.2.8 recovery.img for this phone?
Maybe there's a possibility doing a fastboot boot recovery.img ???
NOPE:
[email protected]:/home/marius/Downloads# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.662s]
booting...
FAILED (remote: unknown command)
Fixed with large hammer! Goodbye Meizu!
Learnincurve said:
Where do I find a 4.2.8 recovery.img for this phone?
Maybe there's a possibility doing a fastboot boot recovery.img ???
NOPE:
[email protected]:/home/marius/Downloads# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.662s]
booting...
FAILED (remote: unknown command)
Click to expand...
Click to collapse
Fixed with large hammer! Goodbye Meizu!
fastboot boot recovery.img isn't a command at all... It's fastboot flash recovery C:/path/to/recovery.img
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!
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
that link just saved me!
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
I managed to get it working by flashing CM after flashing the recovery.
Sent from my Nexus 9 using XDA-Developers mobile app
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
pitrus- said:
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
Click to expand...
Click to collapse
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.
Spannaa said:
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.
Click to expand...
Click to collapse
That's exactly what I meant to convey.
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 :
FAILED <data Transfer failure <unknown error>>
Please help
bhanuodin said:
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
Click to expand...
Click to collapse
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
pitrus- said:
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
Click to expand...
Click to collapse
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
bhanuodin said:
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
Click to expand...
Click to collapse
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.
This TWRP should be compatible
https://dl.twrp.me/oneplus2/twrp-3.0.2-1-oneplus2.img.html
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.
Hi, i am having the same problem.
some background: I was on Oxygen OS 2.x.x, i wanted to upgrade to Exodus 6. I had the older version of TWRP. So I tryed to install the new twrp image within twrp. When i rebooted i couldnt boot into twrp, receiving the same error message as in OP title, when using fastboot.
Using the tool all in one toolkit I was able to flash stock recovery.
But I still cant flash Twrp.
I can still boot into system though.
Any advice? Thanks.
That explains why you're having problems. You're doing it the wrong way.
First you must upgrade the bootloader by either flashing the convert to Marshmallow zip file which also installs the correct TWRP for the new bootloader (easiest way). Or you could flash the latest official OOS3, then fastboot flash the latest TWRP and from there format system and flash the ROM that's using the newer bootloader.
Does that Link work with oneplus x also? Having same problem as Higgings when trying to install twrp and cyanogenmod.
thnx a lot for sharing
:good:
Higgings said:
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
Click to expand...
Click to collapse
Hello,
I've decided to install the Beta version of Oxygenos 3.0. Since my phone came from the OnePlus support, I've unlocked the oem, installed TWRP and flashed the Oxygen zip.
However, a day later I've spotted important touchscreen issues (I can't use the touchscreen sometimes).
To see if it is a software problem, I've decided to go to the recovery to reflash a backup. When I try to go to recovery mode, nothing Happen! (Just the oneplus logo ).
So, i've decided to reinstall TWRP by flashing it with fastboot.
"fastboot flash recovery recovery.img" -> OK
"fastboot boot recovery.img"
downloading 'boot.img' ...
OKAY [0.702s]
booting...
FAILED (remote: dtb not found)
Click to expand...
Click to collapse
I've tried to install the stock recovery but I've the same error.
PLEEEASE HELP. I've waited a week to receive my phone because it had a problem but it's broke again :crying:
Note: I can go in Android normally (but with the touchscreen problem)
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 try this.
This happened to me too except I would not boot into the OS or recovery. I ended up going into fast boot and formatting the System, recovery and data partitions. Here is what I typed.
fastboot format system
fastboot format recovery
fastboot format data
I am not sure if you have to format the data but I did.
After that I flashed TWRP
fastboot flash recovery recovery.img
Then I booted into recovery and was able to restore.
AndroidBeginNinja said:
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 try this.
Click to expand...
Click to collapse
Thank you,
I've done this and I had a working recovery, (bootloop if I try to boot up normaly but it's not a problem I just have to flash a rom)
Trey22200 said:
This happened to me too except I would not boot into the OS or recovery. I ended up going into fast boot and formatting the System, recovery and data partitions. Here is what I typed.
fastboot format system
fastboot format recovery
fastboot format data
I am not sure if you have to format the data but I did.
After that I flashed TWRP
fastboot flash recovery recovery.img
Then I booted into recovery and was able to restore.
Click to expand...
Click to collapse
I've tested your manipulation and it worked well too.
For those having the same problem OR want to install Oxygen OS the CLEAN WAY, read this post before: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
It is very important to read the faq before flashing and doing **** like me.
http://forum.xda-developers.com/one...overy-teamwin-recovery-project-3-0-0-t3310713 flash this first before you flash oos3
Dear everyone,
I am stuck in fastboot. I installed the greek TWRP, and cleaned my data by typing ''yes''.
I connected my phone to my PC to put a ROM zip on it, but it only glitched out (it showed multiple storages in Windows)
I restarted my phone, and it won't boot in recovery. When I try to boot to recovery via adb, it just shows
PS C:\adb> fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.616s]
booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
I am really scared now that my phone is hard bricked. Not sure why though.
Flashing a fastboot ROM wont work either, it just says flash done instantly.
I have done this so many times on my other Xiaomi phones I had without any problems.
And also, is it possible to turn the phone off for now? Because I dont want to have the fastboot screen burned in.
Regards
Jordytjes said:
Dear everyone,
I am stuck in fastboot. I installed the greek TWRP, and cleaned my data by typing ''yes''.
I connected my phone to my PC to put a ROM zip on it, but it only glitched out (it showed multiple storages in Windows)
I restarted my phone, and it won't boot in recovery. When I try to boot to recovery via adb, it just shows
PS C:\adb> fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.616s]
booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
I am really scared now that my phone is hard bricked. Not sure why though.
Flashing a fastboot ROM wont work either, it just says flash done instantly.
I have done this so many times on my other Xiaomi phones I had without any problems.
And also, is it possible to turn the phone off for now? Because I dont want to have the fastboot screen burned in.
Regards
Click to expand...
Click to collapse
Did you try flashing the fixed russian twrp? When I flashed the greek twrp on my phone and rebooted through adb it didn't reboot so I rebooted manually and it rebooted into stock recovery. I rebooted into fastbood and flashed the fixed twrp and it worked. If you can get into fastbood you have a chance of reflashing twrp or flashing stock rom so I don't think its bricked yet
Aserar said:
Did you try flashing the fixed russian twrp? When I flashed the greek twrp on my phone and rebooted through adb it didn't reboot so I rebooted manually and it rebooted into stock recovery. I rebooted into fastbood and flashed the fixed twrp and it worked. If you can get into fastbood you have a chance of reflashing twrp or flashing stock rom so I don't think its bricked yet
Click to expand...
Click to collapse
You are my hero! Thank you so much!
this is soft brick, try to flash another twrp as the above user mentioned.
So i flashed twrp succesfully but i cannot boot into it because os flashes stock recovery and btw i unlocked bootloader. I tried power and volume+. Power and volume down and sudo fastboot boot twrp.img but nothing worked. I tried flashing using fastboot flash recovery twrp.img and using xiaomi tolls v2 but it didn't work and i would like to root it but i can't to do it