i bought yureka plus a month ago and i decided to install custom rom on it but i ended up hard bricking it. i managed to fix it however i noticed that imei has been changed to 123456... I looked for some tutorials on youtube to fix it. None of them worked for me. I have windows 8 on pc and lineage 13 on yureka currently. When i connect my phone to pc its detected as android phone. From here i dont know how to install adb.(when i connect phone for "picture transfer" its detected as adb interface) i followed some vids but whenever i type "adb shell" in terminal it says "adb not found" . if i try to connect in diag mode it gets disconnected. so if i use imei repair tool it doesnt show any devices in diag mode. its been a month since this happened. Any help will be appreciated.
Sorry if I made any mistakes.
Related
A friend of mine brought his LG P500 that is stuck in "blue error handler" mode.
The Phone refuse to be detected by my PC. Tried using "KDZ FW" and "LGMDP" still not detected. I also tried using "CMD" to detect if the phone is detected by the pc using " adb devices" still not detected. i have tried different code combination ( emergency mode, hard reset and even some i don't even know what i'm doing .
Please any help on how to go about it??
How many threads have you created??
Hi Guys,
I've had a few problems with my N5 recently...
If I plug my N5 into my PC via the stock USB cable and boot into the Bootloader (PWR+VOLDN) then it will allow me to flash the original N5 firmware, located here: https://developers.google.com/android/nexus/images, this would indicate to me that there is no issue with the actual devices ability to transfer files via USB connection... Right?
No!
For some strange reason my phone will allow me to push a full factory image to it and will also process any Fastboot commands that are sent to it but as soon as you boot into something like TWRP and try to control the phone's ADB functionality it will not find the device at all! The new MTP option in TWRP 2.8 will allow my computer to see my phone's MTP connection for about 1 second and then will immediately disconnect, the same happens when trying to connect to MTP from within Android too.
USB debugging doesn't show that it is connected when my phone is plugged into my PC and Windows makes the 'device connected' sound and then straight after makes the 'device disconnected' sound...
Any ideas? I am certain that this is an issue with my handset's hardware or software rather than any of the computers or cables... I have tried 3 different cables (including the stock cable) and also three different computers (Windows 8.1 @ Work, Mac OS X @ Work and my own personal PC running Windows 8.1 & Ubuntu @ Home)... All OSs and all computers run into exactly the same issue, device connects briefly and then disconnects.
I have troubleshooted issues relating to the driver. This is not the issue... Device Manager cannot even see the hardware after the disconnect.
Thanks for any help in advance,
Lewis
Also:
-Android does not detect that the USB is charging the device unless the device is booted with the cable attached (if it's not attached before the 'Google' screen then it can't see the USB input at all, within android or TWRP, of course...).
Having the exact same problem. Did you find a solution?
EvilBetty said:
Having the exact same problem. Did you find a solution?
Click to expand...
Click to collapse
It's most likely a driver issue.
Elluel said:
It's most likely a driver issue.
Click to expand...
Click to collapse
Not a driver issue.
3 different Nexus 5s, 5 different workstations. Other two Nexi are fine on all 5 PC's.
1 PC used for ADB forensics, 2 used for ADB development work, one known working for ROM'ing / rooting.
Phone has been factory reset, factory ROM'd from Fastboot. Connects fine on Fastboot. Will not connect on ADB / MTP.
On a fresh PC / phone reboot, the PC will detect the phone for just a second and then it will not reconnect until process is completed.
-EB
What's your adb version?
Went on for about 2 weeks, then suddenly went away on its own. I have no idea what the problem was or the solution. Sorry.
i have a nexus 5 which has stock ROM and blu spark kernel . i locked the bootloader while on the same kernel and again unlocked it . . the phone is bootlooping into twrp and the google logo . in twrp it says unable to mount data . i can access twrp . . i am unable to flash anything . it says unable to mount data/ . please the attachment
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
wwwiesel said:
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
Click to expand...
Click to collapse
Hmmm, intermittent ADB occured before attempted sideload falure.
Boot to bootloader and see if you can
fastboot devices
If you can detect the device in fastboot, but still cant ABD, then maybe take a look here http://forum.xda-developers.com/showpost.php?p=59420668&postcount=322
After looking there, if you are absolutely certain that it is not a driver issue, you might be looking at a hardware failure of the charging port.
https://www.youtube.com/watch?v=qqCEXEmcj4Y
If it were me, I'd replace the port and re-attempt ADB sideload.
My phone is stuck in bootloop. I factory resetted my phone, so usb debugging is now off so, when i connect it to pc and go to recovery it shows in device manager android phone>adb composite device but can't do anything. I also tried fastboot but device not found shows in command prompt. Device is rooted. Phone model is hitech amaze s3. Temporary custom recovery is working. Rom is not available anywhere. It's service centre is in far cities. Does anyone know the solution.
I turned USB debugging and OEM on, installed ADB drivers on my computer and plugged my J4 core (J410F). The "adb devices" command shows that my device is recognized by ADB, and I can reach my files problemless. But when I reboot into bootloader (adb reboot-bootloader) My device appears to be "unknown device". It's literally same problem in this thread: https://forum.xda-developers.com/showthread.php?t=2182437
To summarize: Adb recognized my device, can command my device, PC also recognized my device, can explore the files, but fastboot and Odin can't.
I also tried it with J4+, same problem occured. Tried to use another computer and swapped from windows 10 to windows 7, same problem occured. Dealing with this problem for 3 days, I'm about to give up.
My both devices are Turkey versions. Could that be the problem? , is something is broken on Turkish kernels?
I want to be able to use bootloader so I can root my device or be able to recover it when neccessary. Since some other users had same problem, it might be an universal problem, and since both devices are Turkish variations, it might be the problem of Samsung Developers, so primarily to the Samsung developers, after all developers, I'm asking for your help.
anonimazu said:
I turned USB debugging and OEM on, installed ADB drivers on my computer and plugged my J4 core (J410F). The "adb devices" command shows that my device is recognized by ADB, and I can reach my files problemless. But when I reboot into bootloader (adb reboot-bootloader) My device appears to be "unknown device". It's literally same problem in this thread: https://forum.xda-developers.com/showthread.php?t=2182437
To summarize: Adb recognized my device, can command my device, PC also recognized my device, can explore the files, but fastboot and Odin can't.
I also tried it with J4+, same problem occured. Tried to use another computer and swapped from windows 10 to windows 7, same problem occured. Dealing with this problem for 3 days, I'm about to give up.
My both devices are Turkey versions. Could that be the problem? , is something is broken on Turkish kernels?
I want to be able to use bootloader so I can root my device or be able to recover it when neccessary. Since some other users had same problem, it might be an universal problem, and since both devices are Turkish variations, it might be the problem of Samsung Developers, so primarily to the Samsung developers, after all developers, I'm asking for your help.
Click to expand...
Click to collapse
Not sure what you expected?
ADB requires the adb binary to be run at boot via the kernel ramdisk.
Neither FASTBOOT(which isn't supported on Samsung devices) nor ODIN(download mode) run the kernel.
In short ADB does not function in download mode.