I have a T350 tablet that I was attempting to fix E: failed to mount /efs error using adb
I think the instructions I was following might have had an error, or maybe my device is just extra messed up, but when I tried to reboot, the tablet won't turn on.
I've tried the Power + Volume Down buttons to reset it. And when I connect it to my PC, it says the USB device failed to install correctly.
Any advice? I'm worried it will require a trip to a service center and I'd like to solve this myself if I could.
Thank you in advance.
Related
Hi,
I ran into a problem with my Nexus 4, the plan was to unlock the bootloader using my mac and fastboot. (used this as information but didn't follow it step by step, youtube.com/watch?v=fHZJ2f6JLw0)
I turned off the phone and went into the bootloader with volume down + power button. From here i used "fastboot devices" to secure that i was able to communicate with the phone. My device showed up together with an error message saying "ERROR: could not get pipe properties nexus 4".
Before doing any more i wanted to understand what this message meant so I searched the web without any success. I booted up my android, turned on usb debugging and used "adb devices". This time only my devices showed up and no error messages. I used the "adb reboot boatloader" to access the bootloader once again.
I still had the same error message with "flashboot devices" as before.
From here i didn't do anything more, I may have disconnected the usb from the computer while the terminal window was open and the phone in bootloader but without running any command from fastboot.
So I didn't run "fastboot oem unlock" or anything else.
I turned off the phone and tried to access the bootloader one more time with the volume down + power button. It didn't respond to this any more and nothing happened, the device just stayed turn off.
I turned on the phone and tried to use adb to access the bootloader but now when running the "adb devices" it just responds "-bash: adb: command not found".
I have tried to restore the phone thru the android setting meny without any success. The phone is working fine without any problem except i cant access the bootloader or use adb.
So I desperately need help from you guys. :crying:
Have any of you heard of this problem before?
Regards Rasmus
I have to change my statement.
Actually I succeeded rooting and installing CWM recovery using a win7 computer together with Nexus4 toolkit.
The issue i have right now is that i can't start the device into bootloader using volume and power buttons.
To access bootloader i have to go thru the toolkit and this can be an issue in case i flash a bad rom or kernel and can access android usb debugging.
Is it possible to restore the bootloader?
rallanand said:
The issue i have right now is that i can't start the device into bootloader using volume and power buttons.
Click to expand...
Click to collapse
Are you holding the down volume and pressing the power button?
What OS is the computer that you are using? If you have reset the device, make sure that USB debugging is checked again. I know it sounds dumb, but a lot of times it's the simplest things we forget. Once you factory reset your device, it resets everything.
If you are on Windows 7, make sure you are starting the command prompt from the same location your adb is installed. If you are on Ubuntu or another Linux distro, please let me know which one. This seems like it should be an easy fix for you, but a little more info is needed. Thanks!
Okay, so i have a Samsung S4 (i9505) running cm12 (5.1.1). The problem I'm facing is that it won't connect to my laptop (or multiple other computers i've tried, also tried downloading and deleting stuff of windows which didnt work either) via the usb cable, i've also tried mounting multiple USB's (Through an otg adapter), which also didn't work.
I've tried turnign debugging on and off, ADB on and off, developer options on and off. I came to my last resort today, resetting it. I reset it, the samsung boot logo came up it then went into TWRP, though the TWRP logo just kept flashing on and off (i read somewhere this means that its corrupt but im not sure). The only way i could get the phone to boot was by pressing the: home + volume down & power buttons and then pressing down (cancel) on the custom OS warning screen.
The problem now that im facing is, i cant reset my phone, mount anything via the usb or connect it to any computer. If someone could help me, that'd be greatly appreciated.
Hello together,
I have a problem
I bought a used Acer Iconia A200, looked for a modded Rom and found one that works on this unit.
Now i think i have the Pad somehow bricked.
What i did in short:
1) Installed genuine A200 Driver from Acer on PC
2) Installed ADB via fast ADB-Setup-1.4.3 on PC
3) Set the pad to Debugging-Mode and used "AcerA200-SimpleTool-V2" to unlock the Bootloader and install CWM (unfortunatly the CWM 5.5.0.4 was included)
4) Started Recovery Boot Loader and made a Backup to SD
5) Then tried to install the Mod-ROM from SD-Card (onmi-4.4.4-20150210-a200-IconiaHD.zip)
6....) The setup starts and reaches the point "Formatting /system"
but here it ends, i waited somewhat 8 hours in the first attempt, but nothing happened.
Hard reboot; the Tab doesnt boot into an OS, only possible to start the Bootloader.
Back in Bootloader you can see the problem (that seems to be common with CWM 5.5.0.4):
"Error mounting /system" and
"Error mounting /data"
Formatting also not possible.
SD-Card mount is fine.
Now I found some solutions for this problem, by e.g. connecting the pad via ADB-Console and do the partitioning manually or so.
BUT it seems impossible for me to connect the pad via USB again. So I cant use ADB or Fastboot.
Windows only finds an unknown USB-Device and rejects all drivers I downloaded for the A200 (around 10 different versions beside the one from Acer).
Checking deeper I found that the pad sends not Hardware-ID, so Windows doesnt know whats connected there.
So, do you have any Idea what i can do else, either somehow force installing the driver or something within the CWM?
Thanks a lot!
Oliver
Hello guys and gals. So I got an odd one here. S8 Plus on ATT. When I connect the phone to my computer it will connect then disconnect over and over. Sometimes it doesn't connect at all. Sometimes it will say charging and then when I pull the USB plug out it will still say charging. When changing the USB mode in the phone UI it will reset itself back to charge only no matter what I try. When I put it into download mode or recovery it connects every time without issue. I can even flash a rom which I have multiple times.
After doing a full system wipe and firmware update via odin with nand erase checked I get the following errors: failed to mount /efs and I also get a failed to mount /data error. In one instance it finished flashing then rebooted into recovery, said installing update, then failed at 37%.
Things I have tried: several usb cables , different roms, different computers, replaced USB port with a brand new replacement, battery pull, flashing tmobile firmware (which resulted in bootloop).
Oh and also I have been able to get the computer to successfully recognize it as "Samsung Android ADB interface".
I seem to have better luck getting it to connect after a full wipe. But it still disconnects and goes back into its FU state after.
Attached is a picture of the errors I got in recovery.
Thanks all!
Sorry for the long post I suck at summarizing.
Hi, yesterday I tried to unlock my bootloader however it said failed and after that the phone wouldn't turn on at all. I've tried holding power, power and + volume, power and - volume and all buttons at once nothing works. The only sign of life was when it was connected to my PC via USD or plugged in the charger. I've tried a bunch of things including some written on this forum, however errors keep occuring or it won't work at all.
I've installed the MTK drivers and tried to use Flash Tool however it keeps giving me the error "brom cmd send da fail" and the program stops responding after that until I unplug the USB
One post also mentioned a "fix" for the disconnect problem (Device keeps disconnecting and reconnecting) but got another error there saying that the driver has no certificate.
Does anyone know how to fix it?
Thanks in advance
My phone was the same. Enter device manager and as soon as you plug your phone in you should see it appear under the ports section, then right click and update the driver to the media tek preloader. My phone was unrecognised and kept getting a yellow exclamation mark in the usb controller section, and the only way i got round that was holding the volume up button then connecting the phone, then installed the driver. Now though I`m stuck in a constant bootloop of the logo screen
jxcan said:
Hi, yesterday I tried to unlock my bootloader however it said failed and after that the phone wouldn't turn on at all. I've tried holding power, power and + volume, power and - volume and all buttons at once nothing works. The only sign of life was when it was connected to my PC via USD or plugged in the charger. I've tried a bunch of things including some written on this forum, however errors keep occuring or it won't work at all.
I've installed the MTK drivers and tried to use Flash Tool however it keeps giving me the error "brom cmd send da fail" and the program stops responding after that until I unplug the USB
One post also mentioned a "fix" for the disconnect problem (Device keeps disconnecting and reconnecting) but got another error there saying that the driver has no certificate.
Does anyone know how to fix it?
Thanks in advance
Click to expand...
Click to collapse
https://forum.xda-developers.com/le-2/help/brick-restoration-flashtool-s28-x620-t3754590/page2
x626 disconnecting
Hold the power button at least one minute , begin the download on sp flash and just after that connect to computer
It worked for me
jxcan said:
Hi, yesterday I tried to unlock my bootloader however it said failed and after that the phone wouldn't turn on at all. I've tried holding power, power and + volume, power and - volume and all buttons at once nothing works. The only sign of life was when it was connected to my PC via USD or plugged in the charger. I've tried a bunch of things including some written on this forum, however errors keep occuring or it won't work at all.
I've installed the MTK drivers and tried to use Flash Tool however it keeps giving me the error "brom cmd send da fail" and the program stops responding after that until I unplug the USB
One post also mentioned a "fix" for the disconnect problem (Device keeps disconnecting and reconnecting) but got another error there saying that the driver has no certificate.
Does anyone know how to fix it?
Thanks in advance
Click to expand...
Click to collapse