can't able to flash twrp recovery.img help please - Moto G4 Plus Questions & Answers

:crying::crying:can't able to flash twrp recovery image after all my bootloader is also unlocked it always shows (target max-sparse-size: 256MB
error: cannot load 'twrp.img': No error).......please help me what should i do...plzz help me developer, members plzz.:crying::crying:

Sounds like you're using an older version of fastboot. Try this one https://www.dropbox.com/s/bc1k1lol9nudy68/fastboot.zip?dl=0

Explain the steps you undertook to flash TWRP via fastboot.
If you haven't used the following,
fastboot flash recovery TWRP.xxxxxxx.img
fastboot boot TWRP.xxxxxx.img
where TWRP.xxxxxx.img is the name of the image file (while typing, pressing TAB after typing t autocompletes it, so that should help). I believe there is where you're going wrong.

Related

Bricked Nexus 4, send help. Flashed wrong version of twrp.

I used the WonderHowTo site incorrectly to flash a nexus 5 version of twrp unto my nexus 4.
My device at this point booted to a blank screen. It could still boot the boot loader at this point.
To "fix" this I found the correct version of twrp for my device and proceeded to flash that unto my device.
This has appeared to work since I can access twrp on my device but it is only thing I can access on the phone. When I attempt to boot to system through twrp I am sent back into twrp.
I have attempted to use the wugfresh root tool kit to unroot and return to stock using both soft bricked and phone is still working normally options with no success.
It can still boot to the boot loader currently.
I have logs from the toolkit if these can shed more light on my issue.
Is there anyway I can return my device to stock? Thanks for any response
Flash factory image
https://developers.google.com/android/nexus/images#occam
attempted
attempted to flash stock and got the following error message
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
codebam said:
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
Click to expand...
Click to collapse
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
MrTalk said:
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
Click to expand...
Click to collapse
Okay adb push a cyanogenmod zip from here and flash it in recovery. It should automatically install a working boot image. You should also flash the latest bootloader in the factory image with "fastboot flash bootloader bootloader.img" if you're using an outdated bootloader.
used the advice
I pushed the zip file using cmd and it appears to have been successful since I was given the summary of data transferred and how long it took once the process was finished.
I can't find the zip file in twrp to attempt to flash it.. Is there any reason the file name would change inside the device once it has been pushed?
Is there a way to flash the zip in question without pushing it unto the device?

Cannot Boot TWRP Recovery After Unlocking Bootloader and Successful Flashing Recovery

Hi, I'm having issues with booting recovery.
I've successfully rooted my phone before, but because of an OTA update, had to revert back to the flashing of recovery (TWRP), booting recovery, then flashing Magisk steps.
So, I have my recovery.img file which I renamed to "twrp.img" (no double twrp.img.img file extensions). It looks like I'm able to flash it successfully, giving something that looks like this when I run "fastboot flash recovery twrp.img" (in the directory where the recovery image is located):
target reported max download size of 536870912 bytes
sending 'recovery' (24496 KB)...
OKAY [ 0.530s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.691s
Click to expand...
Click to collapse
​
However, after I try the "fastboot boot recovery twrp.img" command, it gives me:
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
​
When I try to restart into recovery, it just boots into stock recovery, and not TWRP.
Any help would be super useful, I'm really not able to figure this out. I've done a lot of research, even going through disabling/uninstalling the Kedacom USB drivers and turning airplane mode on and installing adb/fastboot drivers from XDA.
Thanks!
Why are you flashing two recovery images? Maybe I'm missing something but I'm not understanding what it is that you are doing.
Your problems could also be related to whatever version of TWRP you are flashing on whatever OS you are running. Maybe there is a compatibility issue between the two but without more specific information it's pretty much impossible to say.
I'm just flashing one recovery.img file (TWRP), which doesn't display any errors in the flashing in command line. But when I try to boot it in command line, it gives me the above error that the recovery doesn't exist. When I try to boot it by advanced restart -> recovery, it just takes me to the stock recovery.
I'm on Oxygen 4.5.14. Let me know if there's anything else I can provide.
Rename your Recovery file to twrp.img
Seems like you forgot to do that according to your command
k0byf1ch said:
Hi, I'm having issues with booting recovery.
I've successfully rooted my phone before, but because of an OTA update, had to revert back to the flashing of recovery (TWRP), booting recovery, then flashing Magisk steps.
So, I have my recovery.img file which I renamed to "twrp.img" (no double twrp.img.img file extensions). It looks like I'm able to flash it successfully, giving something that looks like this when I run "fastboot flash recovery twrp.img" (in the directory where the recovery image is located):
​
However, after I try the "fastboot boot recovery twrp.img" command, it gives me:
​
When I try to restart into recovery, it just boots into stock recovery, and not TWRP.
Any help would be super useful, I'm really not able to figure this out. I've done a lot of research, even going through disabling/uninstalling the Kedacom USB drivers and turning airplane mode on and installing adb/fastboot drivers from XDA.
Thanks!
Click to expand...
Click to collapse
Edit:Sorry I kind of Missed that its already Done
Please Ignore My Upper Message
Possible another Solution:
Download Another Recovery File and Do the Same again
I've renamed the file since, and it still has been a problem.
Both recovery.img and twrp.img and the original name of the file "twrp-3.1.1-cheeseburger-84-20170820-194433-CEST.img" wouldn't take.
The file name is irrelevant. But it seems like your command to boot into recovery is the problem: fastboot boot only takes one argument (the file to boot into) whereas the fastboot flash command takes two arguments (partition and file to flash).
fastboot flash recovery twrp.img
fastboot boot twrp.img
Okay, I'll give that a shot but I'm still booting into the stock recovery when I advance restart into recovery.

facing trouble while flashing TWRP into recovery

Hi guys
I'm using moto g4 plus . i'm facing problem while flashing twrp into my moto g4 plus using minimal adb.exe .even i hv included twrp.img in minimal adb folder and i have unlocked bootloader. can anyone help me out
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'twrp.img'
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223LBNP4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'twrp.img'
Where did you get the twrp.img from? twrp.me doesn't have the modified version necessary, you have to look through some posts to find a link to a repacked image for our device. I can upload it but you should be able to find it with some twrp searches in this forum
Ophallus said:
Where did you get the twrp.img from? twrp.me doesn't have the modified version necessary, you have to look through some posts to find a link to a repacked image for our device. I can upload it but you should be able to find it with some twrp searches in this forum
Click to expand...
Click to collapse
I got it from twrp official website . As same as procedure i renamed it for twrp . Bt i got stuck . Please let me knw what sure i have to change r which method i have to follow . I need RR custom rom 64bit on my phone platform . While removing Moto boot warning text i flashed it into recovery . So now its not showing any recovery . It will show no command . Please help me out
Mallik Sean said:
I got it from twrp official website . As same as procedure i renamed it for twrp . Bt i got stuck . Please let me knw what sure i have to change r which method i have to follow . I need RR custom rom 64bit on my phone platform . While removing Moto boot warning text i flashed it into recovery . So now its not showing any recovery . It will show no command . Please help me out
Click to expand...
Click to collapse
If you see 'no command' on the recovery, you're booted into the stock recovery. Hold the power key then press volume up to get into the stock recovery. I think you need a custom recovery to flash custom logo.bin images.
As for TWRP, check that Windows has not added on a file extension. You may wish to enable file extensions in Windows explorer. One way around this is to type the first few letters of the file name in adb, then press the Tab key on your keyboard. That should auto complete the file name for you. So 'fastboot flash recovery twr' then press Tab, then should fill in the rest of the TWRP image name as your computer sees it. Ignore the 'image is not signed or corrupt' message and boot straight into recovery after flashing.
Be aware that the official TWRP is 32 bit and won't flash 64 bit ROMs. You'll get an error 255 if you try. You need the 64 bit TWRP as linked in the RR 64 bit instructions https://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-v6-0-0-t3747735
Thanks for rplying brother . I will try it fa sure . If i get any bugs i will let you know . ??
Thanks a lot bro it worked as u said .......thanks for helping me out .
echo92 said:
If you see 'no command' on the recovery, you're booted into the stock recovery. Hold the power key then press volume up to get into the stock recovery. I think you need a custom recovery to flash custom logo.bin images.
As for TWRP, check that Windows has not added on a file extension. You may wish to enable file extensions in Windows explorer. One way around this is to type the first few letters of the file name in adb, then press the Tab key on your keyboard. That should auto complete the file name for you. So 'fastboot flash recovery twr' then press Tab, then should fill in the rest of the TWRP image name as your computer sees it. Ignore the 'image is not signed or corrupt' message and boot straight into recovery after flashing.
Be aware that the official TWRP is 32 bit and won't flash 64 bit ROMs. You'll get an error 255 if you try. You need the 64 bit TWRP as linked in the RR 64 bit instructions https://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-v6-0-0-t3747735
Click to expand...
Click to collapse
thanks a lot bro . as u said I got back twrp recovery . and I have small query how can I remove bootloader warning txt . do I have to flash any zip ?
Mallik Sean said:
thanks a lot bro . as u said I got back twrp recovery . and I have small query how can I remove bootloader warning txt . do I have to flash any zip ?
Click to expand...
Click to collapse
Good to hear your device is working again.
For the bootloader warning, you can flash:
1)These modified logo.bin images via fastboot: https://forum.xda-developers.com/moto-g4-plus/themes/customized-logo-t3451349 Be careful to specify the logo partition when flashing.
2)These modified logo.bin images via fastboot or TWRP e.g. https://forum.xda-developers.com/moto-g4-plus/themes/boot-logos-custom-moto-g4-g4-plus-boot-t3640275 Flashing within TWRP should be via the Install option, as the script inside the zip should flash to the logo partition.
There are more flashables in https://forum.xda-developers.com/moto-g4-plus/themes if you wish to have a look.
If you so wish, you can make your own: https://forum.xda-developers.com/moto-g4-plus/themes/guide-t3588090
Bear in mind that these logo.bin images will not shorten the 5 second delay upon booting, just makes it prettier to look at. Also, if you wish to use OTA updates in the future on stock, you have to re-flash the stock logo.bin from the stock firmware as TWRP does not back up the logo.bin. Of course, you will want to flash the same stock firmware as you currently have, please don't try to flash older firmware, else you may risk hard bricking your device should you choose to take OTA updates on old firmware.
echo92 said:
Good to hear your device is working again.
For the bootloader warning, you can flash:
1)These modified logo.bin images via fastboot: https://forum.xda-developers.com/moto-g4-plus/themes/customized-logo-t3451349 Be careful to specify the logo partition when flashing.
2)These modified logo.bin images via fastboot or TWRP e.g. https://forum.xda-developers.com/moto-g4-plus/themes/boot-logos-custom-moto-g4-g4-plus-boot-t3640275 Flashing within TWRP should be via the Install option, as the script inside the zip should flash to the logo partition.
There are more flashables in https://forum.xda-developers.com/moto-g4-plus/themes if you wish to have a look.
If you so wish, you can make your own: https://forum.xda-developers.com/moto-g4-plus/themes/guide-t3588090
Bear in mind that these logo.bin images will not shorten the 5 second delay upon booting, just makes it prettier to look at. Also, if you wish to use OTA updates in the future on stock, you have to re-flash the stock logo.bin from the stock firmware as TWRP does not back up the logo.bin. Of course, you will want to flash the same stock firmware as you currently have, please don't try to flash older firmware, else you may risk hard bricking your device should you choose to take OTA updates on old firmware.
Click to expand...
Click to collapse
thanks:fingers-crossed: brother i have changed boot warning logo . even i like that app where we can customize our own logo.bin

[ROM][STOCK][FASTBOOT][OP8] Stock Fastboot ROMs for OnePlus 8

Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 8 in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 8 to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 8
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
​
Branded devices is for example a Chinese version with HydrogenOS to which OxigenOS has been installed? If so, how can a branded device be recovered?
Thanks
Hi guys, i'm here again to ask for your support, actually with android 10 Google introduced a lot of changing, from dynamic partitions to the new keymaster 4 encryption/decryption. Teamwin is working hard to update TWRP but they will still take some time. Currently some things already work but there are difficulties in bringing them to the OnePlus 8/8 Pro, for example decryption already works but creates some problems on the OnePlus devices. That's why I decided to create a Paypal moneybox to be able to bring you the latest updates in the shortest time possible. As I have previously done, I assure you of a support of at least 2 years (within the limits of my possibilities). In addition to the TWRP I will improve the fastboot roms and add OnePlus 8/8 Pro to my TOOL ALL IN ONE (and maybe I will also bring the RevengeOS). By getting hold of a OnePlus 8 or 8 Pro I will also be able to improve the TWRP for OnePlus 7T and 7T Pro.
OnePlus 8/8 Pro PayPal MoneyBox: https://www.paypal.com/pools/c/8pfrIOL3Qa
If you are unable to participate in the PayPal moneybox, you can make a normal donation (perhaps specifying that it is for the moneybox), however all private donations that I will receive for this or other projects will be included in the moneybox.
Private PayPal Donations: https://www.paypal.me/MauronofrioTool
Why after flash it, it boot up to Qualcomm crashdump mode and how to fix?
sakun-ice said:
Branded devices is for example a Chinese version with HydrogenOS to which OxigenOS has been installed? If so, how can a branded device be recovered?
Thanks
Click to expand...
Click to collapse
I think unbranded devices mean the device bought from T-Mobile or Verizon. Nothing to do with chinese versiion flash oxygenOS, if I'm not wrong.
Can't seem to get this to work. I'm trying to flash a stock rom for my OnePlus 8 after bricking it during a rooting process.
The device' bootloader is obviously unlocked and i can get the phone into Fastboot mode and connected to my PC.
The only issue is when i execute the flash-all.bat file, it can't seem to flash any of the files and gives an error consisting of the message "FAILED (remote: 'Flashing is not allowed for Critical Partitions').
What to do guys? Can anyone help me out.
Does anyone know where to find mobile oneplus 8 5g tmobile from mine is bricked I had same error as post above
KJStar said:
Can't seem to get this to work. I'm trying to flash a stock rom for my OnePlus 8 after bricking it during a rooting process.
The device' bootloader is obviously unlocked and i can get the phone into Fastboot mode and connected to my PC.
The only issue is when i execute the flash-all.bat file, it can't seem to flash any of the files and gives an error consisting of the message "FAILED (remote: 'Flashing is not allowed for Critical Partitions').
What to do guys? Can anyone help me out.
Click to expand...
Click to collapse
Try to flash fastboot rom with "tool all in one),It worked for me.
I needed modem I forgot to fastboot reboot fastboot guy in post 6 that's all you need to do is reboot fastboot then flash all I was looking for different file
Never mind I fixed it by downloading ota and going to system updates in settings because fastboot won't flash to modem right
I am having issues flashing. flashing not allowed on critical partition. please help I tried to use the large address aware program but nothing has changed.
bluemoel said:
I am having issues flashing. flashing not allowed on critical partition. please help I tried to use the large address aware program but nothing has changed.
Click to expand...
Click to collapse
Make sure your on the latest update: 10.5.8
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 8 in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 8 to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 8
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
​
Click to expand...
Click to collapse
Hi, do you know if patching with local update a Oxygen OS Europe release from a Global release may cause problems to the fingerprint? I have a IN2010 with the Global OxygenOS but I would like to switch to the European versione becasue I live in Italy like you
Why not flash reserve.img?
nnyd said:
Why not flash reserve.img?
Click to expand...
Click to collapse
Because it is placed in userdata and not in a dedicated partition
I have an issue trying to flash on fastboot. It's says I can't flash on critical partitions. Yes I know alot of people are saying that but what I haven't seen is this:
This is my problem:
Fastboot get device-info
(Bootloader) device unlocked:true
(Bootloader) device critical unlock: false
(Bootloader) charger screen enabled: true
I have already tried "fastboot flashing unlock_critical"
It says bootloader already unlocked. I then re lock bootloader which I know is not a good idea( reflash stock with msm tool) and it lock then I try unlock critical command again and it still says device critical unlock: false
i need help please ..
i tried this method not the latest version i tried the 10.5.4 global
so it gave me all failed and error to foramt and others
then it restart my phone to show me crashdump
what should i do ?
should i use latest version ?
i hope you replay fast .. thank you
Alucardo1 said:
i tried this method not the latest version i tried the 10.5.4 global
so it gave me all failed and error to foramt and others
then it restart my phone to show me crashdump
what should i do ?
should i use latest version ?
i hope you replay fast .. thank you
Click to expand...
Click to collapse
Try again with 10.5.7. When it reboot to recovery, let it continue to run till it reboots on its own.
Unbrick from fastboot method
I hope I can help someone since I spent the whole night trying various methods to unbrick my Oneplus 8 and only this one worked for me JUST FOR INTERNATIONAL VERSION
You must have the drivers installed (Adb & Fastboot)
You must have your phone with the bootloader unlocked
1.- Download the file
2.-Unzip it
inside you will find Flash-all.bat
3.-Enter Fastboot mode
4.-Double click on the Flash-all.bat command
5.-It will direct you to the recovery, select the English language and restart in fastboot mode so that the process continues, wait for it to finish flashing everything and ready, the phone restarts on the latest version
https://mega.nz/folder/8tpUSSrR#7wH4NX_ccr2a6Ub8LXpsEA
Donate Link to support my work
https://paypal.me/pakomorales?locale.x=es_XC
cannot relock bootloader on oneplus 8
bro thanks for fastboot room for oneplus 8,i flash your fastboot room 10.5.9 everthing ok,but i relocked to boot loader it the phone be correpted. what should i do ,
please help me.

Cannot flash anything < waiting for device > but found in fastboot devices

Hello, I am trying to flash TWRP to my zenfone, I managed to do it once by some miracle with the exact same setup as I have now.
by typing fastboot devices I get K6AXB7616289*** fastboot
but if I try to flash anything with the phone connected I get no output at all.
If I try to flash with the phone disconnected I get <waiting for any device> and no change when I connect it.
In both of these cases when I disconnect the phone I get:
Sending 'recovery' (31332 KB) FAILED (Write to device failed (No such device))
fastboot: error: Command failed
It is overall wonky and seems to change depending on nothing. Sometimes while writing sudo fastboot reboot bootloader I get to the bootloader as expected, but sometimes I get an error but still manage to get to the bootloader and other times it boots up normally.
I am running ParrotOS from a USB
I also posted in here as my problem is very similar but I hope this post resurrects this particular topic: https://forum.xda-developers.com/t/...but-fastboot-devices-is-working-fine.4295449/
What commands are you using?
Fastboot flash boot boot.img?
The boot.img could be the twrp.img renamed to boot. Img but it should be to recovery I believe.
Fastboot flash recovery twrp.img
Yeah im writing fastboot flash recovery and then the path to my twrp.img. I managed to flash it once after a lot of struggle but now I can't do it again.
After posting I saw that I'm using a USB 3 port and my laptop doesn't have a usb 2 one so I think that might be the issue.
Considering I can get three different outputs from the same command in the span of a couple seconds I think that the problem might be hardware related. I can update once I get my hands on a USB 2 port.
Kaynejulian said:
What commands are you using?
Fastboot flash boot boot.img?
The boot.img could be the twrp.img renamed to boot. Img but it should be to recovery I believe.
Fastboot flash recovery twrp.img
Click to expand...
Click to collapse
I have now tried with a USB 2 port and there is no change.
I have had issue when the phones in fastboot and I'm able to flash via his method. Using platform tools I copy all my IMg's into the folder then open a command prompt window in that folder and fastboot reboot bootloader or fastboot reboot fastboot. Which I learned the hardway is fastbootd mode and then and only then did it actually flash. I also learned the hardway that you boot directly from in fastboot mode or it all just cycles back.
Fastboot reboot.
What version zenfone model and what is system is it running?
If your device is running android 10 or newer then is a different process as you'll need to flash the super.img rather than individual imgs like system vendor product ect
Tue shore image also means it matters where you flash the img
Get a fastboot getvar all printout to me and I'll do what I can to help u get it running again

Categories

Resources