Hello,
When I'm trying to install Twrp recovery using adb, I'm getting below error
Sending recovery - failed (Write to the device failed (Invalid argument))
What might be the issue here? Please help.
Added fastboot pic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bharathsjv said:
Hello,
When I'm trying to install Twrp recovery using adb, I'm getting below error
Sending recovery - failed (Write to the device failed (Invalid argument))
What might be the issue here? Please help.
Click to expand...
Click to collapse
Did you try fastboot instead of adb?
https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-x-t3836241/page1
chrome6boy said:
Did you try fastboot instead of adb?
https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-x-t3836241/page1
Click to expand...
Click to collapse
Yes..same error
bharathsjv said:
Yes..same error
Click to expand...
Click to collapse
Your bootloader is unlocked?
chrome6boy said:
Your bootloader is unlocked?
Click to expand...
Click to collapse
Yes.. USB Debugging also enabled.
Drivers are missing in your PC which leads to this error.
Pourush Sharan Bhargav said:
Drivers are missing in your PC which leads to this error.
Click to expand...
Click to collapse
Can you let me know what are those drivers? or what are the drivers required.
bharathsjv said:
Can you let me know what are those drivers? or what are the drivers required.
Click to expand...
Click to collapse
I followed these steps and it worked.
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
I don't think it is a question of drivers as the device shows up fine on typing 'fastboot devices'
I had the same issue... I did the fastbooting in another pc... And it worked
Had to update the ADB driver.. Working now
bharathsjv said:
Had to update the ADB driver.. Working now
Click to expand...
Click to collapse
I had the same problem. My poco used to show , PRESS ANY KEY TO POWER OFF' in the left notch.
Still not resolved. What drivers u updated.
sanjay0501 said:
I had the same problem. My poco used to show , PRESS ANY KEY TO POWER OFF' in the left notch.
Still not resolved. What drivers u updated.
Click to expand...
Click to collapse
Update to latest ADB drivers from Device Manager.
bharathsjv said:
Update to latest ADB drivers from Device Manager.
Click to expand...
Click to collapse
Will try that also.
Incidentally I had flashed twrp and magisk on this same poco on the same laptop and no issues, that's why didn't think it was driver issue.
Btw iirc device manager used to show fastboot Android device instead of ADB
help!
bharathsjv said:
Hello,
When I'm trying to install Twrp recovery using adb, I'm getting below error
Sending recovery - failed (Write to the device failed (Invalid argument))
What might be the issue here? Please help.
Added fastboot pic
Click to expand...
Click to collapse
iam facing the same problem with my redmi note 5 pro can you help?
Change from usb 3.0 to usb 2
I am having the same issue how can i resolve it in my poco f1
Related
My device Mi3 is running on CyanogenMod 13 and latest TWRP recovery. Unable to install weekly updates of CyanogenMod. Recently, got an update cm-13.0-20160516-NIGHTLY when i tried to install that there is an dialog box of "Apply Update" You are about to update bla bla bla... Note: This feature requires a compatible Recovery or updates will need to be installed manually. I didn't get what it means and i thought TWRP is a valid recovery so proceeded from that. After few minutes it rebooted the device top recovery and nothing happened from that. So i rebooted the system again searched over Internet about the issue haven't found any perfect solution (within what i found) but i tried by copying the update file to /sdcard (i mean root directory) and tried to install the update manually by using TWRP recovery but it is showing an error "Updater process ended with ERROR: 7 Error installing zip file '/sdcard/cm-13.0-20160516-NIGHTLY-cancro.zip' Updating partition details......done"
Can you help me out how to install the update and also tell me what I've done wrong so that i will not do that again.
Thanks in advance.
Dude, the answer to your question is in the first post of CM13 FAQ.
Go in here and follow the guide.
https://jrizzoli.github.io/dotfiles/
Hi @diongdyh
sorry for late reply, please help me with a step that is mentioned in the link you've given.
"Run flash_all.bat (on windows) or flash_all.sh (on OS x and Linux - it's suggested to open it from a terminal in these systems)"
Does it mean to run in cmd or what. Please help me out. If you can please elaborate that step.
manideeproyal said:
Hi @diongdyh
sorry for late reply, please help me with a step that is mentioned in the link you've given.
"Run flash_all.bat (on windows) or flash_all.sh (on OS x and Linux - it's suggested to open it from a terminal in these systems)"
Does it mean to run in cmd or what. Please help me out. If you can please elaborate that step.
Click to expand...
Click to collapse
Just connect your device and double click on "flash_all.bat"(I'm assuming you to be on Windows) and it'll do the rest
Well I encountered the same problem a while ago.. I just flashed miui 8 through twrp.. and booted and again flashed latest cm13 and it worked.. No problems so far..
Sent from my MI 3W using XDA-Developers mobile app
@ssasin.monish said:
Just connect your device and double click on "flash_all.bat"(I'm assuming you to be on Windows) and it'll do the rest
Click to expand...
Click to collapse
ok i'll do the same. I doubt whether the device needs to be in fastboot mode or normal system. If you can clear this i'll proceed because previously i tried the same but in fastboot and the device is recognized i checked by 'fastboot devices'.
manideeproyal said:
ok i'll do the same. I doubt whether the device needs to be in fastboot mode or normal system. If you can clear this i'll proceed because previously i tried the same but in fastboot and the device is recognized i checked by 'fastboot devices'.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It is literally written in the second step. Bootloader=Fastboot mode.
diongdyh said:
It is literally written in the second step. Bootloader=Fastboot mode.
Click to expand...
Click to collapse
i've done the same @diongdyh, after selecting run something went in a flash on the desktop screen and nothing happened on my device and its still in fastboot mode. i think booting to miui 8 and then installing cm13 will be a better option as suggested by @sidhg for me as i'm not getting exactly what to do
even I am having the same problem, I nothing happpens on clicking on flash all file.........
manideeproyal said:
i've done the same @diongdyh, after selecting run something went in a flash on the desktop screen and nothing happened on my device and its still in fastboot mode. i think booting to miui 8 and then installing cm13 will be a better option as suggested by @sidhg for me as i'm not getting exactly what to do
Click to expand...
Click to collapse
Yes it'd be best that you flash miui 8 with fastboot/bootloader
http://bigota.d.miui.com/6.6.1/cancro_alpha_images_6.6.1_20160516.0000.22_6.0_cn_2231b4fcb7.tgz
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
multiple internal storages is causing me to boot loop... how can I delete them all??
update: I don't see the multiple internal storages anymore but, I'm still boot looping! please help
YamiRioru said:
update: I don't see the multiple internal storages anymore but, I'm still boot looping! please help
Click to expand...
Click to collapse
Too little information ... Which FireOS are you ? Can you get into recovery ?
You can always go hardcore and just flash TWRP using a special tool :
http://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
bibikalka said:
Too little information ... Which FireOS are you ? Can you get into recovery ?
You can always go hardcore and just flash TWRP using a special tool :
http://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
Click to expand...
Click to collapse
I'm on 4.5.4 and, I can get into recovery
YamiRioru said:
I'm on 4.5.4 and, I can get into recovery
Click to expand...
Click to collapse
I have twrp recovery installed btw... and it keeps boot looping...
YamiRioru said:
I have twrp recovery installed btw... and it keeps boot looping...
Click to expand...
Click to collapse
So just re-install the OS, and you are good to go. Can also do factory reset from TWRP.
Here to get back to 4 :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
Or 5 :
http://forum.xda-developers.com/showpost.php?p=62011228
I did the steps to get back to 4 but when I slided the arrow to the left, it shows the languages then it flashes the os with the main apps then goes back to the languages again... idk what the hell is happening to my kindle fire hd 6....
YamiRioru said:
I did the steps to get back to 4 but when I slided the arrow to the left, it shows the languages then it flashes the os with the main apps then goes back to the languages again... idk what the hell is happening to my kindle fire hd 6....
Click to expand...
Click to collapse
It's an old glitch, see this :
http://forum.xda-developers.com/showpost.php?p=61084629&postcount=26
bibikalka said:
It's an old glitch, see this :
http://forum.xda-developers.com/showpost.php?p=61084629&postcount=26
Click to expand...
Click to collapse
I can't find system folder anywhere when connected to my computer but when I had it on twrp, I found a system folder but no priv-app folder...
YamiRioru said:
I can't find system folder anywhere when connected to my computer but when I had it on twrp, I found a system folder but no priv-app folder...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2073492 I found this post about how I can get the files to show up but, my kindle doesn't show up when I put adb devices in the command line...
YamiRioru said:
http://forum.xda-developers.com/showthread.php?t=2073492 I found this post about how I can get the files to show up but, my kindle doesn't show up when I put adb devices in the command line...
Click to expand...
Click to collapse
it turns out, I just needed to update my drivers lol
I'll let you know if there is any other problems
update: got adb devices working turns out it needed a server restart lol
YamiRioru said:
http://forum.xda-developers.com/showthread.php?t=2073492 I found this post about how I can get the files to show up but, my kindle doesn't show up when I put adb devices in the command line...
Click to expand...
Click to collapse
finally I got it to work again! thanks! I'll come back if any more problems pop up
After updating to android 10, my mobile working fine. But one day my phone automatically restarts and showing EIO state error. Anybody please help me to fix my phone...
Go recovery terminal type
reboot "dm-verity enforcing"
And hit enter
My mobile not able to boot the os, I can't able to go to recovery terminal
Is it red warning "g.co/ABHg.co/ABH"?
Try this method and tell if it works or not
Go to fastboot mode
Connect phone to PC
Open CMD in adb folder
Type : enable dm_verity
Press enter
Techgaming432 said:
Try this method and tell if it works or not
Go to fastboot mode
Connect phone to PC
Open CMD in adb folder
Type : enable dm_verity
Press enter
Click to expand...
Click to collapse
there's no such thing as command enable in cmd or fastboot.
btw its verify, not verity right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ipta said:
Is it red warning "g.co/ABHg.co/ABH"?
Click to expand...
Click to collapse
Yes, can't be able to open recovery mode... Once we go to recovery, phone rebooted
Techgaming432 said:
Try this method and tell if it works or not
Go to fastboot mode
Connect phone to PC
Open CMD in adb folder
Type : enable dm_verity
Press enter
Click to expand...
Click to collapse
When I connect my mobile and entered the code, it shows waiting-for-device. I have installed all drivers but command not running
This is the problem...
LiyasKarthik said:
When I connect my mobile and entered the code, it shows waiting-for-device. I have installed all drivers but command not running
Click to expand...
Click to collapse
Are you sure after you type "enable dm-verity" on CMD in the adb folder, you get respond "waiting-for-device"?
Because there's no "enable" command on fastboot.
ipta said:
there's no such thing as command enable in cmd or fastboot.
btw its verify, not verity right?
View attachment 5175475
Click to expand...
Click to collapse
It's verity not verify
LiyasKarthik said:
When I connect my mobile and entered the code, it shows waiting-for-device. I have installed all drivers but command not running
Click to expand...
Click to collapse
Try this command
fastboot oem enable dm-verity
Techgaming432 said:
It's verity not verify
Click to expand...
Click to collapse
yes, sorry for my mistake but I've tried that also.
see the screenshoot at the attachment.
Techgaming432 said:
Try this command
fastboot oem enable dm-verity
Click to expand...
Click to collapse
FAILED (remote: unknown command)
ipta said:
yes, sorry for my mistake but I've tried that also.
see the screenshoot at the attachment.
FAILED (remote: unknown command)
View attachment 5176169
Click to expand...
Click to collapse
Sadly saying
Locking isn't possible now
I tried the command but my mobile is dead...
Please help me to recover my device
LiyasKarthik said:
I tried the command but my mobile is dead...
Please help me to recover my device
Click to expand...
Click to collapse
Unlock bootloader or flash any ROM
Not able to switch on the mobile... Is there any way to recover my mobile?
I get a tiny message that says
Code:
the serial is not match
fastboot_unlock_verify ok
And the phone doesn't show up in fastboot devices.
Would really appreciate some help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
install drivers
23Aaron said:
I get a tiny message that says
Code:
the serial is not match
fastboot_unlock_verify ok
And the phone doesn't show up in fastboot devices.
Would really appreciate some help!View attachment 5376939
Click to expand...
Click to collapse
Hey mate I also get this, how did you fix it?
mlgmxyysd said:
install drivers
Click to expand...
Click to collapse
I am using a mac and am able to see the phone using 'adb devices'. I do not have Advanced Reboot in dev options, and trying to get to fastboot with 'adb reboot bootloader' gets the same screen as OP. Could not find drivers when I looked, I am unsure what to look for.
Any suggestions?
23Aaron said:
私は言う小さなメッセージを受け取ります
[コード]シリアルが一致しません
fastboot_unlock_verify ok [/ CODE]
また、電話はfastbootデバイスに表示されません。
本当に助けていただければ幸いです!View attachment 5376939
Click to expand...
Click to collapse
私は同じ状態です。再起動できません。助けて。
moisthat said:
Hey mate I also get this, how did you fix it?
Click to expand...
Click to collapse
I still haven’t been able to fix it
23Aaron said:
I still haven’t been able to fix it
Click to expand...
Click to collapse
Do you also have Advanced Reboot missing from Developer Options?
23Aaron said:
I still haven’t been able to fix it
Click to expand...
Click to collapse
Turns out this is the correct screen, and you can just unlock the bootloader from here!
moisthat said:
Turns out this is the correct screen, and you can just unlock the bootloader from here!
Click to expand...
Click to collapse
Kindly tell me how to proceed after mentioned screen. As I cannot do anything further ,
garapaboy said:
Kindly tell me how to proceed after mentioned screen. As I cannot do anything further ,
Click to expand...
Click to collapse
fastboot flashing unlock
Has anyone been able to unlock the bootloader?
Eastw1ng said:
Has anyone been able to unlock the bootloader?
Click to expand...
Click to collapse
Yes, sure
juergenh99 said:
Yes, sure
Click to expand...
Click to collapse
Yeah a pretty useless reply. I got it to work, some extra info here: https://forum.xda-developers.com/t/unlocking-the-bootloader.4327217/
Eastw1ng said:
Yeah a pretty useless reply. I got it to work, some extra info here: https://forum.xda-developers.com/t/unlocking-the-bootloader.4327217/
Click to expand...
Click to collapse
your question and that post is pretty useless - whats your problem? you asked and got an answer - you didn't ask for a step by step guide or whatsoever.
moisthat said:
fastboot flashing unlock
Click to expand...
Click to collapse
step by step guide?
Hello guys can someone help me on my redmi note 10,
So basically my problem is adb can detect my phone when its power on but when my phone switches to fastboot adb cannot detect it anymore. I also try the adb reboot bootloader command, it work and it go to fastboot but after that it didnt detected anymore.
Please help me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure, but it looks like you need install usb/device drivers from MiFlash.
And after, try enable/allow usb debugging
missingN said:
I'm not sure, but it looks like you need install usb/device drivers from MiFlash.
And after, try enable/allow usb debugging
Click to expand...
Click to collapse
i already tried that still the same
@ibanezred16 May be you missing add Environment Variables path?
Adb-fastboot PE guide
ibanezred16 said:
...when my phone switches to fastboot adb cannot detect it anymore. ...
Click to expand...
Click to collapse
This is intended behavior, if your phone is in fastboot mode it can only be detected by fastboot (try command 'fastboot devices'). Devices can only be detected by adb in recovery when sideload is enabled or in OS with debugging on.
Mthw said:
This is intended behavior, if your phone is in fastboot mode it can only be detected by fastboot (try command 'fastboot devices'). Devices can only be detected by adb in recovery when sideload is enabled or in OS with debugging on.
Click to expand...
Click to collapse
sorry im new here, can you tell me a way to flash the twrp? because the regular method don't work with me
ibanezred16 said:
sorry im new here, can you tell me a way to flash the twrp? because the regular method don't work with me
Click to expand...
Click to collapse
What do you mean by regular method? This should work: 'fastboot boot twrp.img' and once it boots up go to Advanced and there is an option called 'flash current recovery'.
Mthw said:
What do you mean by regular method? This should work: 'fastboot boot twrp.img' and once it boots up go to Advanced and there is an option called 'flash current recovery'.
Click to expand...
Click to collapse
that's also one of my problem when it boots to twrp the touch screen is not working can't touch or click anything when im in twrp
Are you using this one? https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4268563/ Either way you should probably ask there.
Mthw said:
Are you using this one? https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4268563/ Either way you should probably ask there.
Click to expand...
Click to collapse
yes, thank you very much for your help
Were you successful? I am guessing you are trying to install a ROM, depending on the rom you could also use a different recovery.
Mthw said:
Were you successful? I am guessing you are trying to install a ROM, depending on the rom you could also use a different recovery.
Click to expand...
Click to collapse
yeah im trying to install Evox
Mthw said:
Were you successful? I am guessing you are trying to install a ROM, depending on the rom you could also use a different recovery.
Click to expand...
Click to collapse
Im succesfully installed twrp I used mouse via otg connector to touch the screen