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] PC won't recognise phone, but Moto Tool will

I need to restore to stock firmware to get Lollipop, but adb won't recognise my phone in cmd, thus I can't follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219 . I installed the Motorola Drivers from here: http://forum.xda-developers.com/showthread.php?t=2550635 , and I have the Motorola Device Manager installed. MotoTool picks up my device and is able to boot it into fastboot and install CWM or TWRP, but when I try to flash stock recovery using MotoTool it either gives me a 'no command' screen or doesn't work at all. Anyone having the same problem/know how to fix this? I'm on the Moto G 2013 XT1032 British retail.
EDIT: I fixed it! I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/show...3#post54872143 then used Moto Tool to flash it, as that recognised my phone. I could then download the OTA as normal and installed it like a regular update. Enjoying Lollipop!

If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.

Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?

audit13 said:
If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.
Click to expand...
Click to collapse
SammyP6 said:
Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?
Click to expand...
Click to collapse
Yes to both of these, I was in fastboot and 'adb devices' came back with nothing even though I was in the directory where adb and fastboot were installed and the phone had USB debugging enabled. I fixed it a different way though, I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143 then used Moto Tool to flash it as that recognised my phone. I could then download the OTA as normal and installed it like a regular update.

Adb commands won't work when the phone is in fastboot mode from what I have seen.

audit13 said:
Adb commands won't work when the phone is in fastboot mode from what I have seen.
Click to expand...
Click to collapse
They didn't work at all, no matter what mode I was in. All sorted now though.

Fithboy said:
They didn't work at all, no matter what mode I was in. All sorted now though.
Click to expand...
Click to collapse
It's great you that got the issue sorted out.
Post your solution in case it may help other users down the road. Thanks.

Cannot lock bootloader

So I'm trying to re-lock my bootloader,
I already looked up how to lock the bootloader and you can do that by booting in to fastboot and locking the bootloader from there. My OP6 was rooted but I removed all root related applications, I even reinstalled android.
I tought it would be as simple as unlocking the bootloader, but whatever I try I can't get my device to show up in the command promt when using the "adb devices" command while in fastboot. I tried reinstalling the ADB, fastboot and OP drivers a couple times but it doesn't help. I tried everything possible but I can't lock the bootloader.
Could somebody please help me with this?

ian_99 said:
So I'm trying to re-lock my bootloader,
I already looked up how to lock the bootloader and you can do that by booting in to bootloader and locking the bootloader from there. My OP6 was rooted but I removed all root related applications, I even wiped android.
I tought it would be as simple as unlocking the bootloader, but whatever I try I can't get my device to show up in the command promt when using the "adb devices" command. I tried reinstalling the ADB, fastboot and OP drivers a couple times but it doesn't help. I tried everything possible but I can't lock the bootloader.
Could somebody please help me with this?
Click to expand...
Click to collapse
You have to be in fastboot mode ( power off phone, hold power and volume up til you see fastboot on screen) on your phone to do want to want, if you cant do it that way,you can try this tool, https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 , it will return your phone to stock factory fresh. It will be back on 5.1.5 software. Good luck

in fastboot mode just type without quote"fastboot oem lock"

MrSteelX said:
in fastboot mode just type without quote"fastboot oem lock"
Click to expand...
Click to collapse
I can boot into fastboot mode (I said bootloader instead of fastboot, my bad), but the command promt does NOT show any devices, so I can't use this command. All drivers are correctly installed.

Did you enable USB debug?

whizeguy said:
Did you enable USB debug?
Click to expand...
Click to collapse
Yes I did
And I tried updating to android P but now I can't even access fastboot!
[UPDATE:]
I can finally boot into fastboot again, the only way to do this was to first boot into recovery and restart to fastboot from there.
And my device is still not detected by adb in fastboot

u do fastboot devices not adb devices

I just tried doing this in a Windows 7 virtual machine, but it gives the exact same results, I really don't know what is cousing this

Then take tool all in one

Well.... Use msm download tool then.. Since you can go to fastboot, it will reset everything and lock the BL.

whizeguy said:
Well.... Use msm download tool then.. Since you can go to fastboot, it will reset everything and lock the BL.
Click to expand...
Click to collapse
What a coincidence, I am watching a video on how you can fix a bricked OP6, wich does exaclty what you said.
Thanks!

ian_99 said:
I tought it would be as simple as unlocking the bootloader, but whatever I try I can't get my device to show up in the command promt when using the "adb devices" command while in fastboot.
Click to expand...
Click to collapse
You should do "fastboot devices" in fastboot mode!
I see thay you're doing "adb devices" instead which is wrong.

rhai said:
You should do "fastboot devices" in fastboot mode!
I see thay you're doing "adb devices" instead which is wrong.
Click to expand...
Click to collapse
Oh god that actually worked, how could I have forgotten I had to use the "fastboot" command.
I can't thank you enough :victory:

ian_99 said:
Oh god that actually worked, how could I have forgotten I had to use the "fastboot" command.
I can't thank you enough :victory:
Click to expand...
Click to collapse
No worries. Cheers!

Fastboot not working on samsung j6

So I am trying to use the fastboot package on my samsung j600gt but it doesnt even redognize the device when I type fastboot devices.
adb devices works normaly.
After checking the device management on windows the usb drivers are up to date.
Also the bootlaoder was arrived by adb reboot bootloader . Any thougjt on what can be done to make fastboot work normally?.

Fastboot doesn't work on Samsung devices.

jwoegerbauer said:
Fastboot doesn't work on Samsung devices.
Click to expand...
Click to collapse
Samsung devices don´t have fastboot mode enabled, Samsung calls bootloader to its download mode, that´s different.
What are you trying to do?

SubwayChamp said:
Samsung devices don´t have fastboot mode enabled, Samsung calls bootloader to its download mode, that´s different.
What are you trying to do?
Click to expand...
Click to collapse
Hello. Was trying to flash the TWRP. As trough Odin it doesnt work due to rmm lockrenormal. Even after OEM unlock and the 7 days

Owyeqt said:
Hello. Was trying to flash the TWRP. As trough Odin it doesnt work due to rmm lockrenormal. Even after OEM unlock and the 7 days
Click to expand...
Click to collapse
No. in this state you can´t, first try to bypass that, there are some forums with some tricks.

Question my device is going in to the bootloader and wont boot normaly

i tried rooting my tablet and probly failed miserably but now it wont boot at all i tried factory reset from recovery mode nothing works
S/N: HA1AM1X7

blocky3321 said:
i tried rooting my tablet and probly failed miserably but now it wont boot at all i tried factory reset from recovery mode nothing works
S/N: HA1AM1X7
Click to expand...
Click to collapse
Do you have an error message on your bootloader screen?

V0latyle said:
Do you have an error message on your bootloader screen?
Click to expand...
Click to collapse
This is what i boot in to every time i turn on the device and if i press start i puts me back here

blocky3321 said:
This is what i boot in to every time i turn on the device and if i press start i puts me back here
Click to expand...
Click to collapse
No error message. Hm. What exactly did you do to get to this point?

V0latyle said:
No error message. Hm. What exactly did you do to get to this point?
Click to expand...
Click to collapse
i tried to root my device i patched boot(using magisk) that i got from lenovos rescue thing and flashed it that didnt work so as a sugestion from LSS4181 in this post i did this
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
and after flashing everything its like this

blocky3321 said:
i tried to root my device i patched boot(using magisk) that i got from lenovos rescue thing and flashed it that didnt work so as a sugestion from LSS4181 in this post i did this
and after flashing everything its like this
Click to expand...
Click to collapse
Are you able to reflash the factory firmware?

V0latyle said:
Are you able to reflash the factory firmware?
Click to expand...
Click to collapse
Ok i can using qpst right?

blocky3321 said:
Ok i can using qpst right?
Click to expand...
Click to collapse
To be honest I have zero experience with Lenovo devices; I'm familiar with ADB and Magisk but I'm not familiar with QPST/QFIL.

Can u not use fastboot?

Arealhooman said:
Can u not use fastboot?
Click to expand...
Click to collapse
now no it doesnt show up in fastboot devices

But you can get into fastboot mode? Try draining it and powering it and getting into fastboot

Arealhooman said:
But you can get into fastboot mode? Try draining it and powering it and getting into fastboot
Click to expand...
Click to collapse
Thats the thing i get in to that no matter what i plugit in to charge it goes to the boot loader and it does it instantly no waiting time or the message that the bootloader is unlocked straight in to the bootloader

blocky3321 said:
Thats the thing i get in to that no matter what i plugit in to charge it goes to the boot loader and it does it instantly no waiting time or the message that the bootloader is unlocked straight in to the bootloader
Click to expand...
Click to collapse
This is fastboot. Does your device show up in "fastboot devices"? Make sure you have an up-to-date fastboot binary for the purpose.
For modern Linux distros you should already have the rules necessary. If not, try run fastboot commands using sudo or as root and see if the device would appear.
On the other hand, I noted that in some cases the fastboot interface may have problems responding. In that case, reboot bootloader, then run your fastboot flash commands as soon as the device restarts.

Install RSA from Lenovo.
Following the instruction to rescue your unit as well as getting boot.img for patching
Moreover, install latest Android Platform Tools
Copy boot.img to your unit and patch with Magisk, and copy the patched_boot.img back to host PC.
Then reboot in fastbootd (adb reboot fastboot) and flash patched_boot.img

LSS4181 said:
This is fastboot. Does your device show up in "fastboot devices"? Make sure you have an up-to-date fastboot binary for the purpose.
For modern Linux distros you should already have the rules necessary. If not, try run fastboot commands using sudo or as root and see if the device would appear.
On the other hand, I noted that in some cases the fastboot interface may have problems responding. In that case, reboot bootloader, then run your fastboot flash commands as soon as the device restarts.
Click to expand...
Click to collapse
It does not show up in fastboot and i have quite new adb and fastboot installed

blocky3321 said:
It does not show up in fastboot and i have quite new adb and fastboot installed
Click to expand...
Click to collapse
Well, get newest. Check drivers.

Arealhooman said:
Well, get newest. Check drivers.
Click to expand...
Click to collapse
ok got somewhere got back recovery but still goes back to the screen in the picture. Any way to flash the whole firmware.

blocky3321 said:
but still goes back to
Click to expand...
Click to collapse
Open Windows terminal, connect tablet to PC with adb/fastboot drivers installed.
Enter command:
fastboot set_active other
and again:
fastboot set_active other
then:
fastboot reboot
It might help.

f1tm0t said:
Open Windows terminal, connect tablet to PC with adb/fastboot drivers installed.
Enter command:
fastboot set_active other
and again:
fastboot set_active other
then:
fastboot reboot
It might help.
Click to expand...
Click to collapse
nope still doesnt work

V0latyle