Database Info

[Q] Stuck on Google logo. Unable to push image file to phone... Please help.

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

[Q] ADB not showing device while in bootloader

Hello guys. I have HTC Sensation, Bootloader unlocked, S-ON, HBOOT-1.27.0000
Yesterday I tried to flash TWRP using fastboot. I have downloaded ADB drivers and also HTC drivers. Connected device and everything was working good. ADB showed my device serial number (or what it is, I don't remember) when I type "adb devices" in command. Then I typed "cd Downloads" to point to download directory (this is where I have twrp.img) and at least "adb reboot bootloader" . Device rebooted into bootloader, but, suddenly, popup appeared on my laptop, it was saying "USB device not recognized". I have closed it and go into command, I typed "adb devices" again, but it didn't show anything at this time. Then I run command "fastboot flash recovery twrp.img" and it returned "Waiting for device...".
After no luck., I have tried to install twrp.img though Flashify. It successfully flashed. I go into recovery, make a backup, perform clean wipe and tried to flash CM12. But it didn't flash. Then I go to restore tab but I can't see my backup. So, TWRP is not flashing anything, I have even tried stock ROM, also it's not backing up things. So now, I'm in bootloop, no OS is installed on my sensation and every time I boot up device, it automatically going into recovery.
I have laptop running Windows 10. I want to make ADB working in bootloader mode or make TWRP working to flash something.
Thanks in advance.

DroidTwe4kz said:
Hello guys. I have HTC Sensation, Bootloader unlocked, S-ON, HBOOT-1.27.0000
Yesterday I tried to flash TWRP using fastboot. I have downloaded ADB drivers and also HTC drivers. Connected device and everything was working good. ADB showed my device serial number (or what it is, I don't remember) when I type "adb devices" in command. Then I typed "cd Downloads" to point to download directory (this is where I have twrp.img) and at least "adb reboot bootloader" . Device rebooted into bootloader, but, suddenly, popup appeared on my laptop, it was saying "USB device not recognized". I have closed it and go into command, I typed "adb devices" again, but it didn't show anything at this time. Then I run command "fastboot flash recovery twrp.img" and it returned "Waiting for device...".
After no luck., I have tried to install twrp.img though Flashify. It successfully flashed. I go into recovery, make a backup, perform clean wipe and tried to flash CM12. But it didn't flash. Then I go to restore tab but I can't see my backup. So, TWRP is not flashing anything, I have even tried stock ROM, also it's not backing up things. So now, I'm in bootloop, no OS is installed on my sensation and every time I boot up device, it automatically going into recovery.
I have laptop running Windows 10. I want to make ADB working in bootloader mode or make TWRP working to flash something.
Thanks in advance.
Click to expand...
Click to collapse
adb doesn't work in bootloader, only fastboot
when you enter in bootlaoder choose fastboot
in the hboot screen you will see fastboot usb
then you can use any fastboot command
i suggest to change the recovery to 4ext
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
then before flashing the new rom from 4ext enable smartflash from it(because you are on S-ON)

rzr86 said:
adb doesn't work in bootloader, only fastboot
when you enter in bootlaoder choose fastboot
in the hboot screen you will see fastboot usb
then you can use any fastboot command
i suggest to change the recovery to 4ext
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
then before flashing the new rom from 4ext enable smartflash from it(because you are on S-ON)
Click to expand...
Click to collapse
It doesn't even works in fastboot too :/ So I can't use any fastboot command

DroidTwe4kz said:
It doesn't even works in fastboot too :/ So I can't use any fastboot command
Click to expand...
Click to collapse
Probably win 10 is the issue

rzr86 said:
Probably win 10 is the issue
Click to expand...
Click to collapse
Drivers and SDK is compatible with Windwos 10. I don't think it's the problem, but thanks anyways.

DroidTwe4kz said:
Drivers and SDK is compatible with Windwos 10. I don't think it's the problem, but thanks anyways.
Click to expand...
Click to collapse
use usb 2.0 ports not 3.0
if nothing works then a ruu.exe to return back to stock
http://forum.xda-developers.com/showthread.php?t=1672425
by the way did you enable usb debugging mode from settings?

rzr86 said:
use usb 2.0 ports not 3.0
if nothing works then a ruu.exe to return back to stock
http://forum.xda-developers.com/showthread.php?t=1672425
by the way did you enable usb debugging mode from settings?
Click to expand...
Click to collapse
OK thanks, I'll try them.
Well, I'm not that much noob USB Debugging is enabled.

No recovery mode, no fastboot, no option to reinstall twrp

Hey folks,
i have a problem with my shieldtablet. The fastboot doesn't work properly. I cannot load anything via "fastboot flash blablabla.img". Minimal ADB and Fastboot just shows "waiting for device" and if i check the devices via "fastboot devices" is just shows nothing but the normal command prompt.
Then i did a mistake and flashed the twrp 3 version with an older one, so i am unable to enter the recovery-mode. If i chose Recovery Mode via bootloader (or if i restart the tablet into recovery mode) it has a short bootloop and then after some trials it starts normal into Blisspop.
How could i flash this without the fastboot? Is there any trick i could use?
The tablet is unlocked. I had several custom-roms installed. Currently Blisspop 6.4 without playstore.

That looks like your PC is not seeing your tablet. Boot into fastboot mode, connect it to your PC and look in Windows device manager for the device.

Thanks a lot! ADB worked fine on Win10. Last time I flashed the recovery was on my old Win7-System. It seems, that the Upgrade deleted just the fastboot drivers.
One last question: is it normal, that if i chose the fastboot protocoll entry on the bootloader, that it restarts the bootloader?

Yes, that's normal. The menu entry is redundant because when you see it you are in fastboot mode already.

[solved] Stuck at boot (even recovery), only fastboot works

I've tried to flash MIUI9 over LineageOS 14 with full formating.
After flashing I'm stuck at boot logo MI. Even if I try to boot into recovery.
Fastboot works, but I'm unable to change anything
Code:
$ fastboot boot recovery.img
> FAILED (remote: unlock device to use this command)
$ fastboot oem unlock
> FAILED (remote: Token verification failed, reboot the device)
The thing is, I remember unlocking bootloader when flashing original ROM with LOS. How is it locked again?
How to get out of this situation? I don't care about any data on the phone.
Thank you.

xda-lukasik said:
How to get out of this situation? I don't care about any data on the phone.
Thank you.
Click to expand...
Click to collapse
In this situation only EDL-mode flashing is possible, but no worries, you can unlock it and get MIUI again at the same time...
https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779

When i type
Code:
$ fastboot oem edl
the phone is no longer listed in
Code:
$ fastboot devices
Also, I don't have a windows pc but i found this tool: XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan (unable to post link)
but it also doesnt list my device after fastboot oem edl (because it uses fastboot devices)

xda-lukasik said:
When i type
Code:
$ fastboot oem edl
the phone is no longer listed in
Code:
$ fastboot devices
Also, I don't have a windows pc but i found this tool: XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan (unable to post link)
but it also doesnt list my device after fastboot oem edl (because it uses fastboot devices)
Click to expand...
Click to collapse
You aren't reading the guide correctly, but for a Linux user I will clarify a few things.
- look, in the guide "Command: fastboot oem edl (this brings your device in a kind of emergency recovery state) -> the device does only show a black screen" - it means fastboot and "fastboot devices" do not exist anymore and your device enters QUALCOMM HS-USB QDLOADER 9008 mode
- run lsusb on Linux in fastboot and then in EDL/9008 mode - the IDs will be different and there is no Linux driver for 9008
- the Linux tool you mentioned is just a script to automate some trivial tasks which can be done manually in fastboot mode. I checked the source code and note "sudo apt-get install android-tools-fastboot", it pulls the fastboot app from a repo and works on it. The tool is completely useless for this job.
- your only option is MiFlash which runs on Windows
- you can get Windows 10 evaluation ISO from Microsoft and get rid of it later
- you can get Windows running in a much easier way but we are forbidden to talk about it on this forum
:good:
Good luck!

Tried and failed.
After oem edl there is no device listed in miflash and "flash" does nothing.

I got same problem last month. I tried using miflash with stock firmware and change the stock recovery with twrp img. Hope this can solve your problem.

cybercruizer said:
I got same problem last month. I tried using miflash with stock firmware and change the stock recovery with twrp img. Hope this can solve your problem.
Click to expand...
Click to collapse
I'm unable to flash anything

Ugh, when you enter edl mode it becomes different device in virtual box and you need to add it again.
But I tried it several times with real windows machine and it didnt show up either (??)
It still didnt worked, I got errors such as:
Failed to hello message
Ping failed
Solution was to use older MiFlash tool (2015).
Thanks all for your help.

Can't unlock oem bootloader on Oneplus 6 (Fixed)

Hey guys, as stated in the title i am unable to unlock my bootloader. The adb devices works up to the point where i boot into fastboot or recovery then it stops working. If i use the command it just says "waiting for any device" I want to install TWRP and change to LineageOS but the bootloader is bottlenecking me hard... any tips would be much appreciated!

Run
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
If this doesn't fix your issue then on Windows PC install the "Android USB Driver" suitable for the phone provided by OEM / Carrier.

jwoegerbauer said:
Run
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
If this doesn't fix your issue then on Windows PC install the "Android USB Driver" suitable for the phone provided by OEM / Carrier.
Click to expand...
Click to collapse
Thank you for your response, found the problem. It was the Qualcom drivers not being signed so after i put test mode on on PC it worked. Thanks for the advice!