First of all, i tried to start my device Samsung galaxy E7 on download mode,
i couldn't start it trying (Home + Volume down + power button)
I tried to install ADB so i can't start the download mode using it,
But failed too,
Because i couldn't find my device on "ADB devices" command.
even thought i installed drivers but i can't find the Android device on device management (ADB Android interface)
I can't startup the device completely (I've little virus, so i can't go to settings to enable USB Debug) So guys if you can help me step by step, please.. I'm new in this community
Related
Hello everyone! This is my first thread here. I hope you can help me and that maybe in the future I can also help somebody here. I tell you my problem and I hope it's not to confusing.
I have a problem with my gionee elife e7 (32GB). The problem occured without a obvious reason. My girlfriend was using the phone which was running android 4.4 Kitkat (stock). So one day it just stopped booting. There is just a black screen and I can't enter recovery mode or factory mode by pressing buttons on the device. At least I tried unsuccessfully. Anyway the device vibrates If I hold the power button and also it is recognized by my PC. This is why I am hoping to be able to restore the smartphone again by flashing a new rom.
The device is recognized as "gionee android composite adb interface". I tried to flash the ROM with the gionee download tool but unfortunately the tool says "open COM ports fails". So I tried to deinstall all COM-ports on my PC without this problem going away. Sometimes - I don't know why - The tool doesn't show this error. But then the tool doesn't find my device when I plug it in.
Also I tried to get access to the Smartphone via ADB or Fastboot without luck. The PC didn't recognize the device.
I tried everything with Windows 8.1, Windows 7 and Windows XP via Virtualbox.
All in all I have no idea left about how to repair the smartphone. I hope some of you can help me with this. Does anybody know how I can access the smartphone again and reinstall the Android System on it?
Thank you very much
try pressing the power plus volume + and volume - simultaneously, release only the power when the phone vibrates and wait bout 10 secs pressing the volume keys. Then release them and plug the phone to the PC and check if the QLoader driver is loaded. If so try flashing in Emergency Mode.
Let me know how it went...
tried
Wrong description!
Thank you for your help! The result was that the device vibrates constantly every 3 sconds after I stop to press the powerbutton und keep pressing the Volume + and - buttons together. As soon as I release them it stops vibrating. In the Device manager it still shows the "gionee android composite adb interface".
I tried to do the same with the device plugged into a USB. What I then recognized was that the Status-LED was blinking red every second . After 10 seconds of pressing the buttons there was a little break in the blinking (like the device would try to restart or something). As I didn't get any changes in the device-manager I disconnected it. After that it stopped to blink and doensn't blink anymore if I do the exact same thing again. it only vibrates now.
I'm sorry that this might be a tough case! Anyway I am thankfull for your advice!
But do you have access to the via ADB?
RSGI said:
But do you have access to the via ADB?
Click to expand...
Click to collapse
If you have ADB access you can try:
Code:
adb shell
su
setprop sys.usb.config diag,adb
I'm not familiar with ADB but I tried to get access to it via Minimal ADB and Fastboot. Even though the smartphone is recognized as ADB Composite Device in the device manager, it don't get any connection (as shown in the screenshot)
The drivers have been tricky with the Amazon Fire to say the least, and this seems to be because windows recognizes the driver as unsigned. To get around this issue, you will need to temporarily enable installation of drivers that are unsigned.
First go to Settings>Update and recovery.
from there click on advanced startup.
Your PC should say "please wait" then pull up a menu.
In this menu click on "troubleshoot" then click "start up settings"
Your PC will now restart
The PC will now boot into Startup Settings. Click 7 on your keyboard to disable driver enforcement then hit enter.
Your PC will restart once more.
Now your fire drivers should install as they are intended. Allowing installation of unsigned drivers can be a security risk, so once you have completed this process and installed the drivers reboot your PC and windows will automatically turn Driver Signature Verification on once again.
its smart to uninstall the fire drivers and reinstall them using the driver signature mode to make sure theyre installed correctly.
its also worth noting that in my case, the device needed a different driver from the downloaded for each mode (normal/on, fastboot, sideload), there is another thread on here for this but Ill add it here just in case someone else stumbles upon this first.
when installing the drivers in device signature mode, youll want to put the device in all 3 states while in signature mode to make sure you dont run into any problems trying to return the device to stock or moving on from fastboot etc. ( i did this, it was scary..)
1. when installing the drivers in signature mode youll come across 3 different drivers to choose from, the first driver "android ABD interface" is for when the device is in normal/on mode.
2. youll need to next boot the device into fastboot mode, i used the rootjunky amazon fire supertool and booted the device to fastboot, then disconnect and reconnected it to my pc and chose the second adb usb driver "android bootloader interface"
2. after installing that driver disconnect the device from the computer and power it down. power the device into the recovery mode by shutting it down then holding volume down and power (when holding the device in portrait orientation the volume down button is the one to the left) and navigate to the option that requires you to connect your device to a PC to load software (sorry i cant remember what option it is) it will say something like its waiting for a connection, connect the device to the PC and install the final driver "android composite ADB interface" now every facet of operation should have a driver, reboot your PC out of driver signature mode and if you were in the same boat as me, you should be able to sideload back to the android os, and flash roms or whatever else.
Hello,
First of all I read all topics regarding this issue and I'm using Windows as my operating system (no linux/unix). I do not consider my phone to be "bricked", just it has the display broken.
My problem is I cannot make the device available when issuing the adb device command, in adb, although I ran all steps (read the hole 72 pages from [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 ), maybe it's related to not having activated before the screen damage the debugging mode.
If I start the phone normally I can hear it when connecting it to computer and also it is shown in device manager, under "Portable device".
I read a thread in which someone gave a hint to similar issue, by flashing the stock image to one "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307), where I can see my device mapped at some COM port, but after successfully flashing I expected to have my device showed in "adb device" command, but I don't.
Also I tried using the drivers from above topic, the ones from Samsung (which allowed me to use ODIN and successfully flash), I'm using the up volume key after booting in order to put Samsung device in "download mode", but still...I'm not able to see it under adb (because I want to use it to retrieve files).
Is there anything else I can try? As long as I can successfully flash, isn't there an image with debugging mode on? For now I think this is the only "variable" which I'm not able to alter, as I do not have the display.
Many thanks,
[Tools, Tips & Tutorials] [kenzo]Entering EDL mode via Test Mode Screen
Who cannot enter EDL mode from standard Android boot and have no abilty to boot an image from FastBoot mode, you could try the following:
Switch the phone off.
Press and hold both Volume keys and Power key.
As Mi logo appears on the screen, release all buttons.
After several seconds, Test Mode Screen should appear (SYSTEM INFO, KEYPAD BACKLIGHT etc.).
Open Device Manager in Windows.
Connect the phone to the Windows computer (no matter which cable end is inserted first).
If ADB drivers are installed, "Android device" branch should appear in Device Manager, containing "Android Composite ADB Interface" and "Xiaomi Composite MDB Interface". Addionally, there should be "Portable devices" branch with "Redmi Note 3" device. If some drivers are not installed, install them.
Execute "adb devices" command to check if ADB connection is established.
If no devices are shown by ADB, wait a minute until "Redmi Note 3" device gets the "!" mark. Repeat "adb devices" command.
If "Redmi Note 3" device is not marked by "!" after a minute and ADB does not list the phone ID, try to disable "Redmi Note 3" in Device Manager.
As the phone ID becomes listed by ADB, execute "adb reboot edl" command.
Click to expand...
Click to collapse
Keep repeating "adb devices" until it reports connected.
Thought this deserves a thread of it's own. If anyone tried to get to EDL via volume buttons, will probably know how difficult it is.
not working
Redmi note 3 , screen on while put to charging, I tried to start mobile , by pressing Volumn + , volume - & Power buttons simultaneously, tried several times but unable to start mi note 3
Hello there members.
i have a Nothing Phone 1 in Edl Mode. Tried to restart it but still connected on Edl. i have searched around for this problem but sill unlucky to find a solution.
Client pretend to have played with roms and flashed the wrong one.
Any help suggestion?
pogradecari said:
Hello there members.
i have a Nothing Phone 1 in Edl Mode. Tried to restart it but still connected on Edl. i have searched around for this problem but sill unlucky to find a solution.
Client pretend to have played with roms and flashed the wrong one.
Any help suggestion?
Click to expand...
Click to collapse
Try holding power+volup+voldown with the phone unplugged from a computer.
If it doesn't work, let me know.
how to boot to edl mode ??
Try this :
Install ADB and Minimal Fastboot drivers through which Windows will recognize your Device.
Enable USB Debugging on your Android Device. You can do this simply by following the given direction:
Settings > About Phone > tap 7 times on the Build Number. This will enable Developer options on it.
Now, again go back to the main Settings > Developer options > USB Debugging and Enable it.
Connect your smartphone with your PC via a USB cable.
Open Command Window by the press and hold Shift Key + right-click of your Mouse.
Choose Open Command Window here.
Type the following command and press the Enter button to check whether the device is connected or not.
" adb devices "
You will see a device serial code on the screen. That means it is successfully connected. Then follow the next step.
Type the command from below and hit enter to Boot into Download Mode (EDL Mode):
" adb reboot edl " or "fastboot oem edl" or "fastboot reboot-edl" or "fastboot reboot edl"
muppetz said:
Try this :
Install ADB and Minimal Fastboot drivers through which Windows will recognize your Device.
Enable USB Debugging on your Android Device. You can do this simply by following the given direction:
Settings > About Phone > tap 7 times on the Build Number. This will enable Developer options on it.
Now, again go back to the main Settings > Developer options > USB Debugging and Enable it.
Connect your smartphone with your PC via a USB cable.
Open Command Window by the press and hold Shift Key + right-click of your Mouse.
Choose Open Command Window here.
Type the following command and press the Enter button to check whether the device is connected or not.
" adb devices "
You will see a device serial code on the screen. That means it is successfully connected. Then follow the next step.
Type the command from below and hit enter to Boot into Download Mode (EDL Mode):
" adb reboot edl "
Click to expand...
Click to collapse
my phone is bricked while flashing stock rom via fastboot
so unable to boot to recovery or bootloader
To begin with, power off your device. If you can’t do so, then you will have to wait until the battery completely drains out.
Now connect one end of the USB cable to your PC, but don’t attach the other end to the device.
Press and hold the Volume Up and Volume Down buttons together for a few seconds.
Now connect the other end of the device to the USB cable.
Your device will now be recognized as Qualcomm HS-USB QDLoader 9008. You may now flash the device-specific firmware to unbrick it.
Even you have a black screen , PC does recognize your phone . Use only a USB 2.0 port . Verify if Qualcomm USB Driver have been installed on Windows .
muppetz said:
To begin with, power off your device. If you can’t do so, then you will have to wait until the battery completely drains out.
Now connect one end of the USB cable to your PC, but don’t attach the other end to the device.
Press and hold the Volume Up and Volume Down buttons together for a few seconds.
Now connect the other end of the device to the USB cable.
Your device will now be recognized as Qualcomm HS-USB QDLoader 9008. You may now flash the device-specific firmware to unbrick it.
Even you have a black screen , PC does recognize your phone . Use only a USB 2.0 port . Verify if drivers have been installed on Windows .
Click to expand...
Click to collapse
tried these steps but phone goes in 900E mode
OK , look then at this :
muppetz said:
OK , look then at this :
Click to expand...
Click to collapse
it does not work as he just changed the drivers from diagnostic mode to qdloader mode
pogradecari said:
Hello there members.
i have a Nothing Phone 1 in Edl Mode. Tried to restart it but still connected on Edl. i have searched around for this problem but sill unlucky to find a solution.
Client pretend to have played with roms and flashed the wrong one.
Any help suggestion?
Click to expand...
Click to collapse
Maybe it's too late already but you can unbrick the phone with this tool
Unbrick / Flash Stock Rom (1.1.7 global) QDLoader 9008 fix | EDL Mode fix
Hi everyone, If your phone (1) does not react on any of yours actions. You may have the same problem. This is an instruction how to fix it without Disassembly. ‼️ Do this at your own risk, I am not responsible for any damage that may occur to...
forum.xda-developers.com
none of these will work
pogradecari said:
none of these will work
Click to expand...
Click to collapse
Why? Have you tried?