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?
Related
OK, so i am really lost at this point. I have been trying for the past couple of days with no luck.
I used Minimal adb and fastboot, downloaded Lg drivers (LGMobileDriver_WHQL_Ver_4.0.3), sdk google drivers and looked at many comments to figure this out.
i type adb device and my phone shows, I type fastboot device and last couple of my phone shows. I used Mininimal adb and fasboot to unclock the the bootloader and i followed all the commands but when i get to fastboot flash recovery twrpxxxx.img, it tells me cannot load twrpxxxx.img. Also, when i type in adb reboot bootloader in brings me the an LG screen with powered by android at the bottom instead of the correct screen.
So, i tried the other way. Power phone off, hold down the volume down button and plug in usb and bootloader/fastboot opens up ( the screen with the line in the top left, with a blank page). it shows unlocked, few lines in white, and then few lines in red. I type fasboot devices and my phone shows up displaying last couple of the phone sn#. but when i go to type fasboot flash recovery twrpxxxx.img, i get the same message cannot load twrpxxxx.img. and on the phone is shows fastboot getvar partition recovery.
Any idea on what this is and how can i solve this?
Thanks in advance.
Rename it to recovery.img and try again.
I renamed it and I still get the same error. Cannot load recovery.img
papatoon3 said:
I renamed it and I still get the same error. Cannot load recovery.img
Click to expand...
Click to collapse
Make sure the image is in the same folder that you are running adb from; it doesnt scan your whole computer for the file. ��
Elu_sama said:
Make sure the image is in the same folder that you are running adb from; it doesnt scan your whole computer for the file. ��
Click to expand...
Click to collapse
It is in the same folder.
Does it make any difference that my phone is unlocked from T-Mobile via unlocked code? That should not have anything to do with it thought. I am just tying to figure it out.
Figured it out.
papatoon3 said:
I renamed it and I still get the same error. Cannot load recovery.img
Click to expand...
Click to collapse
I suggest you remove and reinstall sdk or install nexus root tools and run a cmd within the updated tools. Make sure you installed the right drivers, delete all others, reinstall, although your error seems more a problem with the tools, permissions perhaps, did you run cmd as admin?
Unable to load tells me it can't find your file.. Perhaps it has a hidden extension? Recovery.img.txt
Whats the complete exact command you're typing?
"fastboot flash recovery recovery.img"
http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
Sounds like this is not enabled
{
"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"
}
Sent from my LG-H901 using Tapatalk
papatoon3 said:
Does it make any difference that my phone is unlocked from T-Mobile via unlocked code? That should not have anything to do with it thought. I am just tying to figure it out.
Click to expand...
Click to collapse
SIM unlocked (tmo has no code, its an app) and bootloader unlocked isnt the same thing.
Never mind got it
papatoon3 said:
Figured it out.
Click to expand...
Click to collapse
What was the solution i need it please and thanks
tanked89 said:
Never mind got it
What was the solution i need it please and thanks
Click to expand...
Click to collapse
When your phone is turned on and plugged in, type command adb devices, Does it show?
Put phone in fastboot mode, type command fastboot devices, does it show?
I figured it out. I had to install motorola and g4 drivers to get fast boot to read when I only had one or the other it was only reading adb when I had both on pc it read and adb & fastboot and worked. Thank you.
Hi sir I am facing a problem I rooted my v10 first I unlocked bootloader and then I rooted it by using fwul I hard reset it but when I turned it on a twrp recovery menu appeared please help that how it fix
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
when you try to open download it shows 3 options resatrt , continue , unlock bootloader i pressed down key long for unlock bootloader screen turns black for few seconds then the device restarts and while using adb adb devices it does not show device but while tryoing fastbootdevices it show the id , while try to unlock the bootloader it fails
fastboot getvar unlocked
Yes or No
tom.android said:
fastboot getvar unlocked
Yes or No
Click to expand...
Click to collapse
Is this a code?
DARK002s said:
Is this a code?
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"
}
DARK002s said:
when you try to open download it shows 3 options resatrt , continue , unlock bootloader i pressed down key long for unlock bootloader screen turns black for few seconds then the device restarts and while using adb adb devices it does not show device but while tryoing fastbootdevices it show the id , while try to unlock the bootloader it fails
Click to expand...
Click to collapse
1. ADB doesn't work in Download nor fastboot. ADB only works while booted into the OS
2. Have you enabled OEM unlock in Developer Options?
tom.android said:
View attachment 5676935
Click to expand...
Click to collapse
Failed
iBowToAndroid said:
1. ADB doesn't work in Download nor fastboot. ADB only works while booted into the OS
2. Have you enabled OEM unlock in Developer Options?
Click to expand...
Click to collapse
I was trying in fastboot mode
DARK002s said:
Failed
Click to expand...
Click to collapse
You didn't installed fastboot driver in your computer?
and didn't have TWRP in you tab?
If not all side , you can't use fastboot command for turn back oem unlock.
I saw error : Remote ...not found
I'd run above command from my tab a7 lite.
DARK002s said:
I was trying in fastboot mode
Click to expand...
Click to collapse
1. You don't unlock the bootloader via fastboot. So there's no use in even being in fastboot mode
2. You didn't answer re OEM Unlock
iBowToAndroid said:
1. You don't unlock the bootloader via fastboot. So there's no use in even being in fastboot mode
2. You didn't answer re OEM Unlock
Click to expand...
Click to collapse
It is not opening in adb it say unauthorised failed
DARK002s said:
It is not opening in adb it say unauthorised failed
Click to expand...
Click to collapse
ADB is not involved in unlocking the bootlaoder, whatsoever. You're not making any sense
iBowToAndroid said:
ADB is not involved in unlocking the bootlaoder, whatsoever. You're not making any sense
Click to expand...
Click to collapse
now unlocked bootloader what do delete through twrp like data , and should i flash vbmeta img before deleting files ? or befroe installing gsi???
DARK002s said:
now unlocked bootloader what do delete through twrp like data , and should i flash vbmeta img before deleting files ? or befroe installing gsi???
Click to expand...
Click to collapse
iBowToAndroid said:
ADB is not involved in unlocking the bootlaoder, whatsoever. You're not making any sense
Click to expand...
Click to collapse
twrp not showing up after flashing
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
Hi,
Has anyone been able to successfully relock their bootloader after erasing and flashing stock firmware?
The fastboot command "fastboot oem lock" returns:
"FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
Maybe you reboot on wrong fastboot mode, or Try use latest adb fastboot
YusukeYuu said:
Maybe you reboot on wrong fastboot mode, or Try use latest adb fastboot
Click to expand...
Click to collapse
Unfortunately I think Sony my have blocked the ability to relock the bootloader
I am using latest 'platform-tools_r33.0.3-windows' and I've also installed specific Sony fastboot driver from Sony Developers.
I am booting into default 'fastbootd' mode.
So this command aint work ?
fastboot oem lock
Yes that is correct, it seems that Sony have sealed up the ability to relock ourselves
{
"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"
}
rasseru16 said:
Yes that is correct, it seems that Sony have sealed up the ability to relock ourselves
Click to expand...
Click to collapse
maybe need to use the same serial number that you used to unlock the bootloader
Sakuma_Eitarou said:
maybe need to use the same serial number that you used to unlock the bootloader
Click to expand...
Click to collapse
How do you mean. I am using the same phone I used to unlock so the serial number should remain the same?
rasseru16 said:
How do you mean. I am using the same phone I used to unlock so the serial number should remain the same?
Click to expand...
Click to collapse
yes
if you save that number
Weird, my xperia 1 iii can relock
rasseru16 said:
Yes that is correct, it seems that Sony have sealed up the ability to relock ourselves
View attachment 5720029
View attachment 5720033
Click to expand...
Click to collapse
Try selecting reboot to bootloader first before using the command
YusukeYuu said:
Weird, my xperia 1 iii can relock
Click to expand...
Click to collapse
Did you also update to Android 12 bootloader?
rasseru16 said:
Did you also update to Android 12 bootloader?
Click to expand...
Click to collapse
Yes
You have to reuse the code you used to unlock the bootloader, for example : fastboot oem lock C46...09
fastbooking said:
You have to reuse the code you used to unlock the bootloader, for example : fastboot oem lock C46...09
Click to expand...
Click to collapse
Will give that a go
fastbooking said:
You have to reuse the code you used to unlock the bootloader, for example : fastboot oem lock C46...09
Click to expand...
Click to collapse
Unfortunately, I still receive the same error, oh well I guess only Sony can repair it and relock the bootloader.
You need to go on bootloader not fastbootd mode
YusukeYuu said:
You need to go on bootloader not fastbootd mode
Click to expand...
Click to collapse
If I select 'Reboot to bootloader' the screen is black and I need to specify which driver to install, seeing as that mode isn't fastboot I am trying to understand how it would relock the bootloader?
Thanks
rasseru16 said:
If I select 'Reboot to bootloader' the screen is black and I need to specify which driver to install, seeing as that mode isn't fastboot I am trying to understand how it would relock the bootloader?
Thanks
Click to expand...
Click to collapse
Yes, the screen will go black, but you can use the fastboot command as long as the notification turns blue.
YusukeYuu said:
Yes, the screen will go black, but you can use the fastboot command as long as the notification turns blue.
Click to expand...
Click to collapse
Ok thanks, I cannot get the notification icon to turn blue am I doing something wrong? :/
You should have read my Guides.
fastboot reboot fastboot is the only command You'll need to switch between fastboot and fastbootd.
But just turn off Your Phone. Hold Volume Up and Connect USB. Blue LED and Done
fastboot oem lock
Done
Do a Software Repair with Xperia Companion after. Just liike told in My Guides. Enjoy