I mistakenly the wrong version of TWRP stuck itself in a boot loop and now I can't flash the correct version of TWRP OR the stock recovery img from fastboot.
output after attempting to flash:
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (131072 KB) OKAY [ 3.270s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
fastboot: error: Command failed
the device is unlocked
ive tried flashing the stock boot image, erasing the partition from fastboot and switching slots but i still cannot flash the recovery partition with the same error every time
any help at all would be greatly appreciated
I've tried to follow the steps here
[STOCK][FULL-ROM] OxygenOS_11.3_A.20 EU DN2103 | Unbrick guide
/* * Your warranty is... still valid! * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. * Please do some research yourself before asking or use anything on this...
forum.xda-developers.com
but the tools listed still could not flash the recovery partition
mtk client could not detect my device
Code:
# with PartitionBackupper restore
flashing recovery...
Error with fastboot command
ioaxisx said:
I've tried to follow the steps here
[STOCK][FULL-ROM] OxygenOS_11.3_A.20 EU DN2103 | Unbrick guide
/* * Your warranty is... still valid! * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. * Please do some research yourself before asking or use anything on this...
forum.xda-developers.com
but the tools listed still could not flash the recovery partition
mtk client could not detect my device
Code:
# with PartitionBackupper restore
flashing recovery...
Error with fastboot command
Click to expand...
Click to collapse
You should firstly follow the "Fix corrupted fastboot/preloader partition" section from the guide.
If mtk-client is not detecting your device, then you may check if the drivers are correctly installed. If your device is not properly listed in device manager, then mtk-client nor other similar tool, will detect your device.
Related
Hello,
I have successfully unlocked my AT&T HTC One M9 and I am now trying to flash the recovery and root device. I am currently getting a error when attempting to flash that it cannot open file. I have renamed 'twrp-2.8.6.1_CPTB-B1-hima' to 'recovery.img'.
I currently have the file located where my ADB is located.
I am using command 'fastboot flash recovery recovery.img' with no success.
Any help would be appreciated.
Thank you.
dgub said:
Hello,
I have successfully unlocked my AT&T HTC One M9 and I am now trying to flash the recovery and root device. I am currently getting a error when attempting to flash that it cannot open file. I have renamed 'twrp-2.8.6.1_CPTB-B1-hima' to 'recovery.img'.
I currently have the file located where my ADB is located.
I am using command 'fastboot flash recovery recovery.img' with no success.
Any help would be appreciated.
Thank you.
Click to expand...
Click to collapse
You have to put your phone into download mode, either load boot loader and choose download mode or "adb reboot download" Also the official 2.8.6.1 is working great now, I would recommend it. https://dl.twrp.me/hima/ You don't have to rename the file either
Thank you for you reply.
That unfortunately will not work.
This is what I receive during command:
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT53RYJ08038 device
C:\adb>adb reboot download
C:\adb>fastboot flash recovery recovery.img
error: cannot open 'recovery.img'
C:\adb>fastboot flash recovery recovery.img
error: cannot open 'recovery.img'
C:\adb>adb devices
List of devices attached
C:\adb>adb reboot bootloader
error: device not found
C:\adb>
I believe my phone is no longer available once it goes into bootloader and/or download mode. My commands no longer work in that state. I have tried to reinstall HTC drivers, but that does not work. I don't know if it is an issue but I can uninstall HTC Driver Install from my computer to install the latest which I believe is HTCDriver_4.2.0.001. If I try to install this with the current driver installed, it will not install.
dgub said:
Thank you for you reply.
That unfortunately will not work.
This is what I receive during command:
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT53RYJ08038 device
C:\adb>adb reboot download
C:\adb>fastboot flash recovery recovery.img
error: cannot open 'recovery.img'
C:\adb>fastboot flash recovery recovery.img
error: cannot open 'recovery.img'
C:\adb>adb devices
List of devices attached
C:\adb>adb reboot bootloader
error: device not found
C:\adb>
I believe my phone is no longer available once it goes into bootloader and/or download mode. My commands no longer work in that state. I have tried to reinstall HTC drivers, but that does not work. I don't know if it is an issue but I can uninstall HTC Driver Install from my computer to install the latest which I believe is HTCDriver_4.2.0.001. If I try to install this with the current driver installed, it will not install.
Click to expand...
Click to collapse
adb does not work in boot loader mode. It says cannot open recovery.img. something is wrong with your image, or your not in the right directory, or your fastboot isn't working correctly. Nothing is wrong with your phone. Just install htc sync if you are worried about correct driver
Again thank you for your response. I have the image in the same file where I open on the command prompt. I have it on download screen, but it will not work. I will be trying this on a different computer, and hopefully it will work.
I have successfully flashed and rooted my phone. The issue is with computer I was using and I am unable to get Fastboot working properly even after re-install.
The subject of this thread has been resolved and I greatly appreciate your help.
Sent from my HTC One M9 using XDA Free mobile app
dgub said:
I have successfully flashed and rooted my phone. The issue is with computer I was using and I am unable to get Fastboot working properly even after re-install.
The subject of this thread has been resolved and I greatly appreciate your help.
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Can you specify what the problem with the computer was? cause i have the same problem
I was in twrp recovery because I wanted to wipe my oneplus and start from zero.
I have no idea what I've done, but I can't boot my phone anymore...
All I see is the oneplus logo and I can get in twrp...
It says there is no OS installed, so I started searching for a way to fix this.
I've been trying to go into ADB sideload on the phone and cmd on my windows PC, but no success..
I can't seem to install a factory ROM from here.
I'm not able communicate with your phone through fast boot and ADB
Cownloads\Compressed\fastboot>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Did you format all partitions?
OnePlus One NO oS
victormetal92 said:
Did you format all partitions?
Click to expand...
Click to collapse
Yes all partitions format.
hichs said:
Yes all partitions format.
Click to expand...
Click to collapse
That means that you ereased the OS, so you need to install it, maybe via TWRP, CMW or Fastboot mode.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Flash Rom works
- F2FS support
- Fastboot boot command support
Not working:
- Fastbootd
- Adb sideload
- Backup restore and image flash (system-vendor-product)
- Android 11 fully support
- Touch works
Download:
TWRP 3.4.0-15 Unofficial by mauronofrio
TWRP 3.4.0-14 Unofficial by mauronofrio
TWRP 3.4.0-12 Unofficial by mauronofrio
To Flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_surya
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
- Thanks to @bigbiff and @Captain_Throwback for the hard work on this android 10 TWRP
Thanks to all testers on the Telegram Group
Created 2020-09-23
Tyvm
Ok men
this gets hot
Thanks
Wow! The first one
I am still waiting for my bootloader to be unlocked but then I will give it a try for sure
not working fastboot? what impact does that have? Fastboot not working? Thank you
Thanks for your work
Not working : image flash (system-vendor-product)
Click to expand...
Click to collapse
Doest it mean that when flashing a rom from recovery, theses partitions won't be updated ?
adrenochrome25 said:
Thanks for your work
Doest it mean that when flashing a rom from recovery, theses partitions won't be updated ?
Click to expand...
Click to collapse
means you cant flash .img yet (like for gsi roms). zip roms will work fine
My phone is not here yet.
Can you backup persist.img partition using dd command from twrp terminal?
do you need to unlock recovery to flash twrp? unlocking will cause data erase, right? is it possible to do it without data loss?
Yes! It came earlier than expected, didn't even receive my phone yet, very good news!
crazyjuliano said:
do you need to unlock recovery to flash twrp? unlocking will cause data erase, right? is it possible to do it without data loss?
Click to expand...
Click to collapse
Yes for first two questions . No for the 3rd One.
LUNARIO said:
Yes for first two questions . No for the 3rd One.
Click to expand...
Click to collapse
Thank you, one more question though, once we have twrp ready does it also mean we have possibility to root device as well?
Hi
I have a little problem...
I have done:
fastboot flash recovery twrp-3.4.0-12-surya-mauronofrio.img
and fastboot says:
Sending 'recovery' (131072 KB) FAILED (remote: 'Requested download size is more than max allowed
')
Finished. Total time: 0.004s
How could I fix?
crazyjuliano said:
Thank you, one more question though, once we have twrp ready does it also mean we have possibility to root device as well?
Click to expand...
Click to collapse
Yes it it will be possible to Root
---------- Post added at 11:55 AM ---------- Previous post was at 11:31 AM ----------
Phoenix_Alx said:
Hi
I have a little problem...
I have done:
fastboot flash recovery twrp-3.4.0-12-surya-mauronofrio.img
and fastboot says:
Sending 'recovery' (131072 KB) FAILED (remote: 'Requested download size is more than max allowed
')
Finished. Total time: 0.004s
How could I fix?
Click to expand...
Click to collapse
Fastboot by default wont work with USB 3 ports. Connect to USB 2 or you need to install Windows 7 drivers
LUNARIO said:
Yes it it will be possible to Root
---------- Post added at 11:55 AM ---------- Previous post was at 11:31 AM ----------
Fastboot by default wont work with USB 3 ports. Connect to USB 2 or you need to install Windows 7 drivers
Click to expand...
Click to collapse
upps sorry I didn't say. It is connected in USB2 and linux.
Anyway. After of many reboots in bootloader I have flash recovery but...
now, whe phone enter in twrp doesn't working touch in screen and show a screen with the title: mount and it ask a password.
very strange
Phoenix_Alx said:
upps sorry I didn't say. It is connected in USB2 and linux.
Anyway. After of many reboots in bootloader I have flash recovery but...
now, whe phone enter in twrp doesn't working touch in screen and show a screen with the title: mount and it ask a password.
very strange
Click to expand...
Click to collapse
O, fixed.
I have flashed the rom from xiaomi.eu https://forum.xda-developers.com/xiaomi-poco-x3-nfc/how-to/rom-xiaomi-eu-rom-poco-x3-nfc-t4165247
and boot with its boot.img. Miui has started fine and then I have restarted in recovery mode. it's working fine now
Phoenix_Alx said:
upps sorry I didn't say. It is connected in USB2 and linux.
Anyway. After of many reboots in bootloader I have flash recovery but...
now, whe phone enter in twrp doesn't working touch in screen and show a screen with the title: mount and it ask a password.
very strange
Click to expand...
Click to collapse
Are you in stock or xiaomi.eu?
Very happy to see this thread. Thank you for your work
piranime said:
Are you in stock or xiaomi.eu?
Click to expand...
Click to collapse
before, with the problem in stock. Now in xiaomi.eu
Phoenix_Alx said:
upps sorry I didn't say. It is connected in USB2 and linux.
Anyway. After of many reboots in bootloader I have flash recovery but...
now, whe phone enter in twrp doesn't working touch in screen and show a screen with the title: mount and it ask a password.
very strange
Click to expand...
Click to collapse
I've managed the same, I guess it's because I forgot to remove any fingerprint / password before flashing
So now phone always boots into twrp and is stuck at the Mount / Decrypt Data screen where it's asking for a password
I've downloaded stock ROM xxx://bigota.d.miui.com/V12.0.2.0.QJGEUXM/miui_SURYAEEAGlobal_V12.0.2.0.QJGEUXM_c68aede605_10.0.zip and am wondering how to get working system back
Would this be the correct steps?
1) extract boot.img from the ROM
2) flashing the boot.img through command fastboot flash boot boot.img
Any other step necessary to get my phone to boot back to stock?
Thanks for your help
* Disclaimer *
* Your warranty is now void and your phone is cute. *
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will turn you into a furry.
Femboy Recovery is a fork of TWRP with many more UwU stuff to make your experience better. It's more flexible & easy to use.
• Based on Non-CFW-TWRP 3.5.0-Unified
Notes:
• Non - CFW based For Custom Roms and Miui Android 10.
• Magisk v21.4 Option Added.
• UnRoot Option Added
• Patch Vbmeta avb 2.0 added
• Close avb 2.0 added
• Flash the img from current non-cfw twrp or using fastboot.
• If flashing Miui , in case close avb 2.0 didn't worked then patch vbmeta avb 2.0.
• If it didn't booted on miui then flash Lrtwrp Q and close avb 2.0 and flash this over it.
Method to Flash
Use fastboot method
-put recovery in adb platform tool
-open cmd in same folder
-type
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
Use current custom recovery
-go to install , select install img and select the FBRP recovery file .
-on next screen select recovery as partition .
OUR WEBSITE: https://sites.google.com/view/femboyrecovery
Femboy team: mikusgszyp#2945, Sugaryy_#9400
Flashed with "fastboot flash recovery recovery.img" over TWRP and now phone entered bootloop
madanadam said:
Flashed with "fastboot flash recovery recovery.img" over TWRP and now phone entered bootloop
Click to expand...
Click to collapse
Because you need to have root with dmverity disabled or flash vbmeta before recovery
MikqPL14 said:
Because you need to have root with dmverity disabled or flash vbmeta before recovery
Click to expand...
Click to collapse
My phone's mainboard is burned after flashing and reboot this recovery
You just need to use miflash and re-flash stock, on my note 8 Pro it normalny works
We'll wait for the Android 11 based one. I bootloop-ed my phone trying it lol.
Hi!
I created a simple .bat script that roots poco m4 pro and redmi note 11s
Code:
/*
** Your warranty is now void.
**
** We are not responsible for bricked devices, dead SD cards,
** thermonuclear war, or you getting fired because the alarm app failed. Please
** do some research before rooting!
** YOU are choosing to make these modifications, and if
** you point the finger at us for messing up your device, we will laugh at you.
**
**/
Requirements:
1. Internet
2. Unlocked bootloader
3. Brain
Instructions:
1. Download magisk app from internet
2. Copy boot.img from your miui version to your phone
3. Patch boot.img with magisk app
4. When done, copy rooted image to computer
5. You MUST rename boot.img to rootedboot.img, if you don't rename it, the script simply won't work
6. Reboot phone to bootloader (vol+ & Power button)
7. Start the script
Code:
@echo off
adb devices
adb reboot bootloader
fastboot flash boot rootedboot.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot reboot
rootdone.vbs
You can download already rooted boot.img from RKEMIXM 13.0.7.0 that is attached below (but only if you have global 13.0.7)
Download easyROOT below:
The script:
Code:
adb devices
adb reboot bootloader
fastboot flash boot rootedboot.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot reboot
I can't recommend this.
It won't work, as you haven't included the vbmeta.img in your .zip.
But also, it's important to learn what you're doing when rooting your phone, and this is an extremely fragile solution that will only work if you have exactly the right device and firmware, have already unlocked your bootloader and enabled USB debugging, have installed the magisk app (at least, if you want anything useful from your root), have the right USB drivers installed, have the adb platform tools installed, etc.
This solution (if it worked) would go out of date as soon as Magisk or the system firmware is updated.
aricooperdavis said:
The script:
Code:
adb devices
adb reboot bootloader
fastboot flash boot rootedboot.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot reboot
I can't recommend this.
It won't work, as you haven't included the vbmeta.img in your .zip.
But also, it's important to learn what you're doing when rooting your phone, and this is an extremely fragile solution that will only work if you have exactly the right device and firmware, have already unlocked your bootloader and enabled USB debugging, have installed the magisk app (at least, if you want anything useful from your root), have the right USB drivers installed, have the adb platform tools installed, etc.
This solution (if it worked) would go out of date as soon as Magisk or the system firmware is updated.
Click to expand...
Click to collapse
You are right! I edited it so now that zip have vbmeta, also i added which results can bring rooting