Related
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
I'm trying to revert back to stock firmware but unfortunately for me, my Moto G XT1034 is bricked (it would go in a boot loop). Since it's bricked, i began searching for tutorials on how to unbrick the device and it would also fail whenever i'm installing stock firmware. When installing through adb and fastboot, it always fail when the first 4 commands are typed; mfastboot flash partition gpt.bin, mfastboot flash motoboot motoboot.img, mfastboot flash logo logo.bin, and mfastboot flash boot boot.img. Also when i type "adb devices" into the command promt, it doesn't display my device's serial number under "List of devices attached". Yes i installed Motorola Device Manager and Android SDK. The bootloader is also unlocked. I was coming from the ParanoidAndroid rom. I'm thinking the issue maybe that the fastboot falcon s driver is not installed, but whenever i try to install it by plugging it in into my computer, it would not install. :/ Please help.
uninstall moto drivers restart pc, install, restart pc, connect phone in fastboot and have internet on the pc
maurocds said:
uninstall moto drivers restart pc, install, restart pc, connect phone in fastboot and have internet on the pc
Click to expand...
Click to collapse
Followed instructions. "Fastboot falcon S X No driver found" :crying:
Having same issue with drivers
YungMono said:
Followed instructions. "Fastboot falcon S X No driver found" :crying:
Click to expand...
Click to collapse
I am having the same issue, the only difference being my Moto G labeled as Fastboot peregrine S (I guess it's different for the 4G LTE version?). I have attempted to reinstall drivers numerous times to no avail. Any suggestions?
---------- Post added at 07:51 PM ---------- Previous post was at 07:01 PM ----------
salbee1 said:
I am having the same issue, the only difference being my Moto G labeled as Fastboot peregrine S (I guess it's different for the 4G LTE version?). I have attempted to reinstall drivers numerous times to no avail. Any suggestions?
Click to expand...
Click to collapse
Let me give some more details, I have the Moto G XT1045.
I had no issues unlocking and was attempting to flash CM 11. However when after rebooting it brought me back to fastboot, It is clear the installation went wrong. I figured I could just try again and that's when I started having issues with the Moto G being recognized and driver issues. I uninstalled Motorola Device Manager several times, as well as the drivers in the device manager. I also reinstalled sdk tools. I have done all this in all orders possible, yet no success.
At first the device would show as a motorola adb device however I was not able to access it using sdk platform tools. I could perform the reboot command as well as the "fastboot getvar all," so that combined with my device showing in the device manager meant my pc was recognizing it in some capacity. However any attempt to list the device in "adb devices" or "fastboot devices", it would not show. Also other commands attempting to load TWRPS or CWM recovery would result in device not found or remote failure.
So it seemed clear this was all a driver issue, however the reinstall attempts have done nothing. At this point the phone shows up as "Fastboot peregrine s" not even as a motorola device. Every time I attempt to reconnect the phone the drivers do not install. I am not sure how to link them manually? when I browse to the System32 folder or system32/drivers folder, the drivers are not found.
The sdk tools worked fine until I rebooted after the blotched install and now I cant get my PC to properly recognize my device.
Please any help would be great, I've searched rather thoroughly and can't find any answers specific to my issue until I saw this post that was never resolved.
If I am not being clear about something or using incorrect language let me know. Or if I need to clarify any more details.
salbee1 said:
I am having the same issue, the only difference being my Moto G labeled as Fastboot peregrine S (I guess it's different for the 4G LTE version?). I have attempted to reinstall drivers numerous times to no avail. Any suggestions?
---------- Post added at 07:51 PM ---------- Previous post was at 07:01 PM ----------
Let me give some more details, I have the Moto G XT1045.
I had no issues unlocking and was attempting to flash CM 11. However when after rebooting it brought me back to fastboot, It is clear the installation went wrong. I figured I could just try again and that's when I started having issues with the Moto G being recognized and driver issues. I uninstalled Motorola Device Manager several times, as well as the drivers in the device manager. I also reinstalled sdk tools. I have done all this in all orders possible, yet no success.
At first the device would show as a motorola adb device however I was not able to access it using sdk platform tools. I could perform the reboot command as well as the "fastboot getvar all," so that combined with my device showing in the device manager meant my pc was recognizing it in some capacity. However any attempt to list the device in "adb devices" or "fastboot devices", it would not show. Also other commands attempting to load TWRPS or CWM recovery would result in device not found or remote failure.
So it seemed clear this was all a driver issue, however the reinstall attempts have done nothing. At this point the phone shows up as "Fastboot peregrine s" not even as a motorola device. Every time I attempt to reconnect the phone the drivers do not install. I am not sure how to link them manually? when I browse to the System32 folder or system32/drivers folder, the drivers are not found.
The sdk tools worked fine until I rebooted after the blotched install and now I cant get my PC to properly recognize my device.
Please any help would be great, I've searched rather thoroughly and can't find any answers specific to my issue until I saw this post that was never resolved.
If I am not being clear about something or using incorrect language let me know. Or if I need to clarify any more details.
Click to expand...
Click to collapse
I think i know why i can't revert back to stock firmware. I believe i forgot to enable USB debugging before attempting to revert back to stock firmware, but i can't enable USB debugging because the OS is probably corrupted :/
YungMono said:
I think i know why i can't revert back to stock firmware. I believe i forgot to enable USB debugging before attempting to revert back to stock firmware, but i can't enable USB debugging because the OS is probably corrupted :/
Click to expand...
Click to collapse
Did you find any solution to this...or anyone for that matter?
thanks
YungMono said:
I think i know why i can't revert back to stock firmware. I believe i forgot to enable USB debugging before attempting to revert back to stock firmware, but i can't enable USB debugging because the OS is probably corrupted :/
Click to expand...
Click to collapse
You've just described my situation.... have you had any luck resolving it?
orakitine said:
You've just described my situation.... have you had any luck resolving it?
Click to expand...
Click to collapse
Do any new devices appear in device mamager when you connect the phone? Can you get into fastboot mode on your phone?
audit13 said:
Do any new devices appear in device mamager when you connect the phone? Can you get into fastboot mode on your phone?
Click to expand...
Click to collapse
Can get the phone into fastboot.
Device manager shows it as: Fastboot falcon S ( Motorola ADB interface, Android Device)
"adb devices" does not list it
orakitine said:
Can get the phone into fastboot.
Device manager shows it as: Fastboot falcon S ( Motorola ADB interface, Android Device)
"adb devices" does not list it
Click to expand...
Click to collapse
ADB devices may only work if the phone has booted into the ROM and you have enabled USB debugging.
Boot the phone into fastboot mode, connect phone, and type fastboot devices.
audit13 said:
ADB devices may only work if the phone has booted into the ROM and you have enabled USB debugging.
Boot the phone into fastboot mode, connect phone, and type fastboot devices.
Click to expand...
Click to collapse
ROM is no more phone would not boot normaly
So you can't get into fastboot?
audit13 said:
So you can't get into fastboot?
Click to expand...
Click to collapse
I can get the phone into fastboot mode and TeamWin recovery but my laptop adb/fastboot does not see the device.
Hi
Has anyone managed to get out of this one please?
Doing this for a friend:
Moto G (1039) shows in device manager as "fastboot peregrine s",
does not get listed after "adb devices" under W7 and linux
phone bootloops
<power> + <sound -> keys get me to screen with
AP Fastboot Flash Mode (s)
some device info
+ following options:
Normal powerup (when chosen --> bootloops)
recovery (when chosen --> bootloops)
factory (when chosen, does not work --> bootloops)
barcodes
BP Tools
qcom
+ device is not detected by Odin
I was trying to flash a custom ROM on my moto g xt1033. I used choosing the zip from USB otg after wiping and formatting everyrhing but. It flashed but a black screen came instead of cm logo and I was stuck at welcome to cm screen without touchscreen working. http://forum.xda-developers.com/mot...4-4-4-help-t3019082/post58587594#post58587594
Then I tried side loading or pushing method. But problem is adb commands are not working in fastboot mode. They are working when phone is switched on. (Adb devices show serial number and device in normal mode) Fastboot commands are working fine in fastboot mode but not adb. When I type adb devices in fastboot mode there is nothing after list of device attached. So adb push or adb side load give me waiting for device or device not found result. Is it normal. Earlier I have latest Motorola device manager and latest android SDK. Tried uninstalling and installing them, tried changing USB ports, tried rebooting the phone and restarting windows pc several times but still no luck.!!
Yes, it's normal that ADB commands do not work in Fastboot mode. But you can access custom recovery from the fastboot screen.
@lost101 if adb commands do not work in fastboot mode then how "adb sideload" works when we clean install a ROM? Many threads at XDA say it should work
Guru.Eclairs said:
@lost101 if adb commands do not work in fastboot mode then how "adb sideload" works when we clean install a ROM? Many threads at XDA say it should work
Click to expand...
Click to collapse
You have to be in a custom recovery (TWRP, CWM, Philz Touch) and enable the 'adb sideload' option.
lost101 said:
You have to be in a custom recovery (TWRP, CWM, Philz Touch) and enable the 'adb sideload' option.
Click to expand...
Click to collapse
I have latest philz touch. Also tried twrp..but adb still not working in fastboot mode or recovery mode. The device disappears from My Computer area when in fastboot
Guru.Eclairs said:
I have latest philz touch. Also tried twrp..but adb still not working in fastboot mode or recovery mode. The device disappears from My Computer area when in fastboot
Click to expand...
Click to collapse
It doesn't work on all versions of Windows; I think I've had it working in Windows 7. But I mainly use it in Linux - where no driver is required.
I also have windows 7.. Thanks Anyway
Guru.Eclairs said:
I also have windows 7.. Thanks Anyway
Click to expand...
Click to collapse
It's a driver issue. Your phone is not being recognised. If you boot a Linux LiveCD from DVD / USB, you can access recovery mode ADB that way.
sudo apt-get install android-tools-fastboot
Not sure if this will help but, after completely wiping my phone, I installed TWRP using fastboot commands, booted to TWRP, mount, copy ROM to moto g, and install using TWRP.
If you are in fastboot mode, type fastboot devices and see what happens.
audit13 said:
Not sure if this will help but, after completely wiping my phone, I installed TWRP using fastboot commands, booted to TWRP, mount, copy ROM to moto g, and install using TWRP.
If you are in fastboot mode, type fastboot devices and see what happens.
Click to expand...
Click to collapse
Fastboot Devices command works flawlessly in fastboot mode. I can flash .IMG files. But none of adb commands working. When I type adb devices there is no result after List of Devices attached. So I can't sideload anything
I'm not 100% sure how adb works on the moto g but I don't think adb commands work in fastboot mode. When I connect my moto G to my computer after the ROM has booted and I am at the phone's desktop, I type "adb devices" and I see my device listed. Then I type "adb reboot-bootloader" to get into fastboot mode and adb commands no longer work.
I have Philz Touch on my Moto G and sideloading is an option. I don't think you can side load from fastboot.
audit13 said:
I'm not 100% sure how adb works on the moto g but I don't think adb commands work in fastboot mode. When I connect my moto G to my computer after the ROM has booted and I am at the phone's desktop, I type "adb devices" and I see my device listed. Then I type "adb reboot-bootloader" to get into fastboot mode and adb commands no longer work.
I have Philz Touch on my Moto G and sideloading is an option. I don't think you can side load from fastboot.
Click to expand...
Click to collapse
If adb doesn't work in fastboot mode then whats the propose of word "sideload"
Guru.Eclairs said:
If adb doesn't work in fastboot mode then whats the propose of word "sideload"
Click to expand...
Click to collapse
I have no idea as I have never used adb to install anything except apk files when the phone has been booted to the desktop.
I always use fastboot commands to install recovery and install stock ROMs.
Using adb to side load may refer to the aibility to install files while the phone is running.
http://www.geek.com/mobile/what-is-adb-and-how-do-i-use-it-1461697/
audit13 said:
I have no idea as I have never used adb to install anything except apk files when the phone has been booted to the desktop.
I always use fastboot commands to install recovery and install stock ROMs.
Using adb to side load may refer to the aibility to install files while the phone is running.
http://www.geek.com/mobile/what-is-adb-and-how-do-i-use-it-1461697/
Click to expand...
Click to collapse
OK leave it. Do you have any idea how to increase 2g/3g speed. Any trick/mod/script?? I flashed cm11 quarx build and internet is painfully slow
Edit- no sideload means pushing a flashable zip to the root of internal storage when phone is in recovery mode. We do it for clean installing ROMs.(Format and wipe everything). After format there is no operating system left in phone so we do sideload rom
Guru.Eclairs said:
OK leave it. Do you have any idea how to increase 2g/3g speed. Any trick/mod/script?? I flashed cm11 quarx build and internet is painfully slow
Edit- no sideload means pushing a flashable zip to the root of internal storage when phone is in recovery mode. We do it for clean installing ROMs.(Format and wipe everything). After format there is no operating system left in phone so we do sideload rom
Click to expand...
Click to collapse
Sorry, I don't know how to increase speed except try a different radio/modem on your phone. I rarely use data on my phone because I have an iPad with LTE.
Guru.Eclairs said:
Fastboot Devices command works flawlessly in fastboot mode. I can flash .IMG files. But none of adb commands working. When I type adb devices there is no result after List of Devices attached. So I can't sideload anything
Click to expand...
Click to collapse
Sounds like your fastboot driver is working fine but your adb driver is not...go into your custom recovery and then check Device Manager in Windows to see if you have all your drivers working properly.
If you are having adb driver issues you could try the Universal adb driver setup file attached.
adb commands don't work in fastboot mode. Install a recovery (Preferably TWRP because I forget how CWM's adb sideload works). For TWRP, go to advanced, then adb sideload. Make sure to install the adb drivers tho, or else the sideload won't work. If you're sticking with stock, press the Vol+ button for about 15 secs, then tap the power button. Use the Vol- and + keys too scroll. There should be an option like "Install firmware through adb" or something. Scroll to that, then hit the power button to go to that option. Then, just sideload the firmware.
Check device manager 1st phone is conected properly
adb has no relation to fastboot.adb will not work while in fastboot, it never worked that way either.
There is no sideload while in fastboot, you're confusing it with the adb sideload, that has nothing to do with fastboot.
Reading and comprehension are desirable here.
Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
jchen221 said:
Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
Click to expand...
Click to collapse
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Heisenberg said:
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Click to expand...
Click to collapse
I'm sorry for this mistake.
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
jchen221 said:
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
Click to expand...
Click to collapse
What command are you using while in fastboot mode?
Heisenberg said:
What command are you using while in fastboot mode?
Click to expand...
Click to collapse
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
jchen221 said:
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
Click to expand...
Click to collapse
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Heisenberg said:
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
jchen221 said:
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
Click to expand...
Click to collapse
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install , reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
Heisenberg said:
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
Click to expand...
Click to collapse
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
I have the same problem.
jchen221 said:
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
Click to expand...
Click to collapse
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
pavanakshay said:
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
Click to expand...
Click to collapse
for me too bro same problem please help me
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
i too having the same problem bro the driver link is not working please send me the link thankyou in advance
i am also facing the same problem that phone loops into fast boot mode whenever turned on i do totally every kind of drivers softwares and etc like tenorshare but all in vain i guess at last that phone must be enabled usb debuging in order to be detected as a active adb device,i pratically do this stuff by using another phone with enabled debuging and it was an active device andd can be processed further but when i disabled the usb debugging of same phone it was not working with adb interface i hope you understand,,,,but a miracle happenend i removed the battery for about a week and suddenly i pluged and try to turn it on hola it starts from roms boot logo
HELP!!!!! Stuck on bootloop and fastboot not working
i was flashing twrp on infinix s4 withfast boot. after flashing the device is stuck on bootloop. the recovery is not accessible (i press the key combo nothing happens) and fastboot combination is also not working. i tried connecting it with adb cmd and ran the command "adb reboot bootloader" but no device is detected.
ps: the link for drivers is broken
Hi guys, a friend gave me this phone because it has boot loop. It has no root and no strange flashes have been attempted. I'm trying to flash custom firmware with UpgradeDownload but as soon as it turns on, it restarts right after logo shows up. Any idea on how I can flash through adb/fastboot? Or maybe with SD?
You can flash phone's Stock ROM by means of ADB.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.ZIP>
adb reboot
jwoegerbauer said:
You can flash phone's Stock ROM by means of ADB.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.ZIP>
adb reboot
Click to expand...
Click to collapse
Will this work if debug mode is not enabled? And I don't know if bootloader is unlocked
ADB only works if USB debug got enabled: should be obvious.
BTW: FastBoot only works if OEM unlock got enabled.
jwoegerbauer said:
ADB only works if USB debug got enabled: should be obvious.
Click to expand...
Click to collapse
I don't know if it's enabled, as I said this isn't mine. Any way to check?
Run
Code:
adb devices
If nothing is listed then it isn't enabled.
jwoegerbauer said:
Run
Code:
adb devices
If nothing is listed then it isn't enabled.
Click to expand...
Click to collapse
I get this result:
List of devices attached
JAD82015000614 sideload
but if I try to use the second line of code I get:
error: closed
Phone is configured to operate in Sideload mode. When ADB returns "error:closed" then it's not really specific, can have many reasons.
Try
Code:
adb devices
adb usb
adb reboot
jwoegerbauer said:
Phone is configured to operate in Sideload mode. When ADB returns "error:closed" then it's not really specific, can have many reasons.
Try
Code:
adb devices
adb usb
adb reboot
Click to expand...
Click to collapse
it gives me back the same error when trying "adb usb"
My recommendation: Take phone to authorized service center and let them try to fix it.
jwoegerbauer said:
My recommendation: Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
It's not worth for this phone, thanks for your time, if you have other ideas let me know
TunguskaMed said:
Hi guys, a friend gave me this phone because it has boot loop. It has no root and no strange flashes have been attempted. I'm trying to flash custom firmware with UpgradeDownload but as soon as it turns on, it restarts right after logo shows up. Any idea on how I can flash through adb/fastboot? Or maybe with SD?
Click to expand...
Click to collapse
That's how I solved the issue. I called the Wiko assistance and I asked for the stock firmware because of boot looop. They sent me an exe wich did all by itself and now the phone is fully working. That was easy after all!