Long time ago, my phone had the usb host mode problem when plug in into pc, but can charge at OS. So i didn't bother it because it still can transfer files to PC via USB OTG.
Last month, itself random went into usb host mode when charging and the phone totally cant charge, need to restart then its ok. When i go into fastboot it shows FASTBOOT AC and then FASTBOOT randomly (like gotten shock) and after awhile the problem gone so i didnt bother about it.
Last week, I unplug my phone after i wake up and then itself shows USB HOST MODE, so i tried connect USB OTG and then it didn't works. I thought it was kernel problem so I downloaded ElementalX 18.2 and then i flashed it. Now, after boot, the phone wont charge. It only charge when powered off and RECOVERY mode. Fastboot shows no sign, no FASTBOOT AC or USB, even OTG power. This is strange and weird.
Also, i flashed ARHD 81.0 at older version of TWRP Recovery, and then after i got that problem, i reflash my phone with TWRP 2.8.0.2, at the end it says : "set_metadata_recursive some changes failed" , and the phone can't boot. Luckily i got a nandroid of it so i flash it immediately. It can boot, but the no charging problems still exist.
I later upgrade my TWRP to 2.8.3.0 via TWRP Manager, still get "set_metadata_recursive some changes failed" problem. But, I found out that after i flash the rom, then flash nandroid, when i boot into OS with charging, it can charge in the OS, but not anymore after i went into fastboot or recovery.
And something interesting is, when the phone boot, haven't load the drivers, itself began OTG mode and powered up my powerbank, PLEASE HELP!! Im totally stuck on this!
Does this is a hardware or software problem? Its this the USB board broken or the motherboard? Please respond..
Sorry for my bad English.
I cannot boot the device into Recovery mode. If I attempt to the device stays on the Samsung boot screen. Since I have gotten the device all I have done is rooted the device and it is running android version 2.2
When I put the device into download mode it is not recognised by my computer (tried using Windows 7, 8.1 and 10 build 9926) and Odin (v4.38) does not register that the device has been plugged in. In Device Manager I get Unknown USB Device (Device failed Enumeration). Re-installing drivers and the device does nothing to fix this.
Any assistance with this issue would be welcomed.
~Edit - The device is not booting at all now. It is stick on the Samsung Boot Screen.
~Edit - For some reason putting the device into Download Mode then plugging it into a my laptop and allowing Windows Update to find the drivers worked and allowed ODIN v4.38 to detect the device.
Then by following this guide I was able to flash CWM to my device. After doing this I was able to boot the device normally and I was able to boot it into the custom recovery.
The best way to boot to recovery in case you aren't able to.
The best way to boot to recovery in case you aren't able to is using ADB. Use the command adb reboot recovery and for sure you will either know what the exact problem is, or will be taken to recovery.
Hi guys, I have unlocked my phone but I still can't flash TWRP on it.
I have done manually flashing too but when I access recovery mode it's still in Huawei eRecovery(stock?)
Any help is appreciated.
Model is EVA-L19
Android 7.0
Build L19C636B381
Unplug usb cable?
so do I unplug after "flashboot reboot"?
If you flash the recovery and your usb cable is still plugged, it is strange but you will not get the twrp recovery. Just after flash, when you reboot your phone to recovery, unplug the usb cable as fast as you can.
I was texting, using xiaomi.eu rom stable lastest, stock kernel, no root.
Gallery stopped, then camera, whatsapp closed, instagram gave black screen...
I turned the phone off and then turned it on, bootlop, so I went to TWRP and wiped all partitions and also formatted data. I also did a selinux fix contents or something like that, I flashed another recovery, a custom one via zip and then phone died, mi logo and rebooted, only fastboot available.
When I use fastboot and connect it to my pc it gets detected as kedacom adb automatically, I tried lots of drivers, uninstalling any driver and installing google drivers and lots of things, got ADB and fastboot 15s installed, I also tried different cable, other pc, 2.0 ports, 3.0 ports, other Windows, virtualbox, doing fastboot flash recovery twrp.img with waiting device and then connecting...everything I've seen and know. I bricked my phone and other phones more than one time, and managed with almost no issue to fix it, but now i'm just lost.
I get Press any key to shutdown, on the left top corner of the phone, I do the following:
fastboot devices(gets detected by fastboot)
fastboot flash recovery twrp.img(instantly I get press any key to shutdown)
I can't do anything, it's dead, any tips or something? Thanks guys.
I needed 13h in total to fix it, so I wanna share what to do, the fix is in the post, scroll down a little bit and you'll see it. Hope it worked.
I fixed it finally, if anyone wants info, pm or reply
I need to tell this honestly, you should share what you did and how you did, so you can help anyone anytime if they encounter this problem anyhow. They can use this thread as a guide and don’t need to start a new topic and we save the forum from flood messages and topics. Thanks in advance.
THE FIX
It was very hard and tricky, but possible, you'll need a computer, usb data transfer cable, type c to usb, and a usb mouse, you'll need your device to be unlocked first, if it's not unlocked, I can't help you.
I used Tool All In One by Mauronofrio, installed drivers and with phone in fastboot connected it, if I press check, it will reboot and fail, you have to go to recovery flasher, if no recoveries are available, then download and put it on the same folder where the tool is. Go to recovery flasher(not zip one) select it, I recommend mauronofrio one, the lastest, and then select when going to flash flash and boot, it should be black screen with waiting devices and the phone with the press any key thing, then just disconnect the phone from the cable, restart it to fastboot and connect it, it should boot, you'll have mi logo or fastboot for a minute or 2 and then it will boot to twrp, but you may not have your touch working, just connect the type c to usb adapter and use a mouse, you should be able to use it, go to wipe, wipe all partitions, then format data and connect the phone back to computer, if it does get detected, you'll see the phone in file explorer, so you'll be able to move any files, move any rom to internal storage, use then the usb adapter and with the mouse, flash the rom, reboot and everything will work.
IF IT DOES NOT GET DETECTED, Go to recovery flasher(not zip one) select it, I recommend mauronofrio one, the lastest, and then select when going to flash flash and boot, it should be black screen with waiting devices and the phone with the press any key thing, then just disconnect the phone from the cable, restart it to fastboot and connect it, it should boot, you'll have mi logo or fastboot for a minute or 2 and then it will boot to twrp, but you may not have your touch working, just connect the type c to usb adapter and use a mouse, you should be able to use it, partitions allready wiped, so just put the rom file if it was deleted and flashbe sure that under partitions is MTP enabled, if it is and it still does not work, just go to reboot and select recovery, wait for it to boot to recovery. If it goes to fastboot and does not work, When booted, your twrp touch will be working again, if not, just flash another one.
There are other options, trying usb hub, 2.0 ports, a non amd pc, uninstall drivers and install google ones with internet disabled all time when flashing... But this is the one that worked, if anyone needs help, I can help you with Discord or pm.
Thanks for sharing the fix.
I am stuck in a very weird situation, my device is not getting detected in both adb in recovery mode and fastboot. I have no ROM (No OS) installed at the moment.
I am booting to recovery and fastboot through hardware keys.
I have tried installing drivers from mi unlock tool and any other USB drivers I could find in top searches of "USB drivers".
I am sure the USB cable is not the issue as other xiaomi device (Redmi note 4) is getting detected.
The port also looks fine as I can see 'charging' in recovery mode.
What are my options here? is my device 'gone'? I have orange fox recovery so I have access to `shell` if that helps.
Sparkenstein said:
I am stuck in a very weird situation, my device is not getting detected in both adb in recovery mode and fastboot. I have no ROM (No OS) installed at the moment.
I am booting to recovery and fastboot through hardware keys.
I have tried installing drivers from mi unlock tool and any other USB drivers I could find in top searches of "USB drivers".
I am sure the USB cable is not the issue as other xiaomi device (Redmi note 4) is getting detected.
The port also looks fine as I can see 'charging' in recovery mode.
What are my options here? is my device 'gone'? I have orange fox recovery so I have access to `shell` if that helps.
Click to expand...
Click to collapse
Hey man, I know this might sound dumb, but have tried using a different PC ??, I have been in a situation like this and trying using a different pc actually was successful
> Have you tried different PC
Yes. My first suspicion was USB3.0 Ports. So I tried a different PC as well. Unfortunately couldn't find a PC with USB 2.0 ports but yeah another PC didn't work as well (Note mine worked for past 4 years just fine)