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

screwed up , any assist appreciated

I can access bootloader and twrp
if i type fastboot devices it recognizes my phone but on my pc it's not showing in explorer except under devices and printers as just android
trying to flash OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT.zip in twrp.
Getting invalid zip file format, error
If i try and run mauronofrio's fastboot rom flash-all-partitions.bat on pc i get not recognized as an internal or external command in cmd window

Redwingsyummy said:
I can access bootloader and twrp
if i type fastboot devices it recognizes my phone but on my pc it's not showing in explorer except under devices and printers as just android
trying to flash OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT.zip in twrp.
Getting invalid zip file format, error
If i try and run mauronofrio's fastboot rom flash-all-partitions.bat on pc i get not recognized as an internal or external command in cmd window
Click to expand...
Click to collapse
hello
you cant flash fastboot rom in twrp . download one that is not fastboot . links in this thread : https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
about not recognized as an internal ... . make sure you installed adb and fastboot drivers .

lalala
i can't get a recovery flashable zip to the phone now anyway.
i did reload adb and oneplus drivers this morning and then again after your reply to make sure.
i did notice the phone shows as a oneplus6 in devices while in twrp but when i switch to bootloader it changes to just android device?
So still stuck.
Between last night and this morning have many hours trying to get it working somehow.

no twrp just bootloader now
rebooted the phone and lost twrp.
tried to flash it and it says failed remote failed to load authenticate boot image :load error
i need to start fresh somehow
*I can't even turn the phone off now, it reboots to bootloader instead!!!!

Try this tool https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892

Question The current image(boot/recovery) have been destroyed and can not boot? - Realme C2

Hi, I have trouble with flashing custom rom to my Realme C2 phone.
Last night i unlocked the bootloader and tried to flash custom rom to my phone, but i really can't get into twrp recovery or fastboot mode. (The screen stuck on fastboot_unlock_verify ok). Then i tried to relock the bootloader and decided to give up and go back to normal. When i entered : fastboot flashing lock : command in terminal (im using mac os), it kept rebooting and says the current boot image(boot/recovery) have been destroyed and can not boot.
Right now i can't boot into recovery mode or fastboot mode, any chance that i can get my phone working again? Is it because that my phone is carrier locked, so they locked my fastboot option? but i got the bootloader unlocked.
Big thanks for every reply and trying to help, I really appreciate it!!

Fastboot and ADB are 2 different drivers: don't mix up. Fastboot deals with device's boot-loader whereas ADB deals with Android OS.

jwoegerbauer said:
Fastboot and ADB are 2 different drivers: don't mix up. Fastboot deals with device's boot-loader whereas ADB deals with Android OS.
Click to expand...
Click to collapse
Sorry, It was in terminal not Adb, but fixed! Anyway that i can get my phone up running again?

To me it seems your installation of TWRP - what amonng other things modifies Android's boot.img and also removes device's Stock Recovery - miserably failed for whatever reason.
You can try to bring back phone's Stock Recovery ( overwrite TWRP ) by means of SP Flash Tool.

jwoegerbauer said:
Fastboot and ADB are 2 different drivers: don't mix up. Fastboot deals with device's boot-loader whereas ADB deals with Android OS.
Click to expand...
Click to collapse
jwoegerbauer said:
To me it seems your installation of TWRP - what amonng other things modifies Android's boot.img and also removes device's Stock Recovery - miserably failed for whatever reason.
You can try to bring back phone's Stock Recovery ( overwrite TWRP ) by means of SP Flash Tool.
Click to expand...
Click to collapse
I tried to follow the guide, but Realme C2 firmware doesn't have scatter file to let me flash the stock firmware

Wondering why you haven't created the Scatter file before starting to hack/mod the phone?

stuck at bootloader , No OS No Recovery :(

hi my oneplus 7 pro 1910 stuck at bootloader and when i press start or recovery it gets back to the bootloader screen i cant even turn off the phone
i accidentally wiped all partitions in twrp and made a format .
anyhelp ? ive tried to do the fastboot rom flash but my pc doesnt detect my phone
i tried almost every solution i found but nothing works

Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?

@soka said:
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
Click to expand...
Click to collapse
Yes it’s unlocked , any help

Search on the fast boot rom thread for the fast boot rom version you were last on, i have used this many times and it worked.
One thing to note, after it flashed everything , I ended up in crash dump error. I went into stock recovery and wiped/formatted my device and it boot up great.

https://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ - just follow this guide

One thing that worked for me is when your phone is plugged into your pc open a command prompt and type fastboot boot twrp-*.img (make sure it is the .img not .zip), and from there download the twrp installer .zip and flash that, reboot to recovery, and install the OTA for your device (OTAs can be found at this thread).
If it fails to boot and gives you an error, try fastboot getvar all to see which slot is currently active then do fastboot --set-active=*inactive slot letter* then fastboot --set-active=*original active slot letter* then try to boot to the twrp .img from fastboot again. If fastboot doesn't detect your device at all, try seeing if adb devices outputs anything, and if it does type adb reboot bootloader

Question [SOLVED] Asus Rog Phone 5 cannot communicate in fastboot mode

I've been using an Asus Rog Phone 5 for some time now and I really like it. Original WW version. Unlocked bootloader and installed magisk without major hurdles. I could carry over root by patching boot image in the inactive slot in case of a new firmware version.
I've just tried to upgrade from Magisk 23.0 to 24.1 and unfortunately it didn't installed itself into the boot image. I assumed I have to repatch the boot image using the new magisk and reflash. I extracted the boot image from the payload and patched it successfully in magisk app.
Now I have a problem accessing the phone in fastboot mode. I have no problem entering fastboot mode: first entering the bootloader and selecting fastboot mode. However I see no activity over the USB port and the phone is not recognized by the computer (either from windows or linux). If I boot into the system I can see the phone in adb mode. It responds and I can issue commands - for example boot the bootloader. But no signs of traffic in fastboot mode.
Am I missing something? How I may flash an image if I cannot access the phone in fastboot mode? Please let me know if you have any ideas how to solve this situation.
Thanks: Dw.

Don't enter Fastboot (Fastbootd) from the bootloader,Just boot into bootloader and try sending Fastboot commands from there. If you're connection & drivers are in good shape, you should be sorted...

use the side port to communicate with the phone in fastboot mode.

yurishouse said:
use the side port to communicate with the phone in fastboot mode.
Click to expand...
Click to collapse
I'm officially an idiot. Thanks for the heads up...

Andrologic said:
Don't enter Fastboot (Fastbootd) from the bootloader,Just boot into bootloader and try sending Fastboot commands from there. If you're connection & drivers are in good shape, you should be sorted...
Click to expand...
Click to collapse
I tried to use the wrong port - and I'm banging my head against the wall...