Database Info

Stuck big time. Help requested (Nexus S)

Hi all,
Well my adventure started last night when I went to return my Nexus S to stock. I did so and it worked well. Then I tried to re-root the device.
After doing so, it now will not boot past the google boot screen (with the unlock icon). It just sits there, even after battery pulls and additional attempts to start up. I can reboot into recovery (fastboot) as shown on the attached images. After hours of reading, it seems I need to flash CWM recovery.img to get the phone to boot. Ok, not a problem. So I installed the android sdk, google and samsung phone drivers and my phone is recognized in device manager.
When I go to flash the recovery.img via fastboot, it just sits there on "waiting on device" and ever goes anywhere. I also have a message on the bottom of the Nexus screen that says "FASTBOOT STATUS - FAILInvalid Command"
I'm at a point where googling is doing no good. Please help.
How can I get my phone to boot? How can I successfully flash the recovery image so I can go forward with root and be done with it?
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.

albundy2010 said:
First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.
Click to expand...
Click to collapse
Ok, how does one go about doing this on Win7x64?
Quides are on the forum? No idea what that means.

The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.

albundy2010 said:
The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.
Click to expand...
Click to collapse
Believe me, I've done that. Hours and hours worth.
Anyone care to help since apparently this information is so easy to locate? Fastboot simply isn't communicating with my phone and it will not boot past the google boot screen.

After many hours of trying, I figured it out. It had to do with the PDA net drivers. Basically, my phone would not boot up, preventing me from finishing the PDA net install. It kept hanging on "Installing PDA net to your phone" because, well, it couldn't install to my phone (since it was in fast boot mode).
I kept clicking on OK on the dialogue box and it would roll back, uninstalling the PDA net drivers. This was why fast boot could not communicate via cmd.
How I worked around this was by NOT clicking ok, hence not uninstalling the drivers.
It was an epiphany. And a pain in the arse.
So, if you have a similar issue, don't click ok on the dialogue. Leave it in limbo and work your command line magic!

Fastboot commands error

Hi everybody, I'm trying to install a custom recovery on my Asus Zenfone Max Pro M1, following the instructions to install the Pixel Experience ROM, but every time I give a command in fastboot mode the screen goes black and on the top left angle appears the message: press any key to shutdown. I've already unlocked the bootloader with the official unlock app, and I tried to do this thing on the stable Pie version and the on the Android Q beta, same thing appened. I'm not an expert but is a strage error, I've not found any help on the internet. Any suggestion? Thanks.

With regards to this thread's title here my 2 cents:
Fastboot commands per se aren't erroneous, at least I've neither encountered it ever, nor heard of this or read this.
The reality is that FastBoot isn't always Fastboot as expected, it depends on how OEM/carrier implemented Fastboot, will say not all Fastboot commands work on all devices.
Always run
Code:
fastboot --help
to get supported commands / their synthax listed.

jwoegerbauer said:
With regards to this thread's title here my 2 cents:
Fastboot commands per se aren't erroneous, at least I've neither encountered it ever, nor heard of this or read this.
The reality is that FastBoot isn't always Fastboot as expected, it depends on how OEM/carrier implemented Fastboot, will say not all Fastboot commands work on all devices.
Always run
Code:
fastboot --help
to get supported commands / their synthax listed.
Click to expand...
Click to collapse
Ok, I tried again and I had the same problem, but this time I gave the command "adb reboot bootloader" to go in fastboot mode and as soon the device booted in fastboot the same message appeared, "press any key to shutdown". i mean, it is a lot frustrating, because I'm working to install the ROM since october but this error is recent, before I had problem with booting and flashing the recovery. I'll attach an image of the error. Thanks for help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Riccardo De Lucia said:
Ok, I tried again and I had the same problem, but this time I gave the command "adb reboot bootloader" to go in fastboot mode and as soon the device booted in fastboot the same message appeared, "press any key to shutdown". i mean, it is a lot frustrating, because I'm working to install the ROM since october but this error is recent, before I had problem with booting and flashing the recovery. I'll attach an image of the error. Thanks for help.
View attachment 5183239
Click to expand...
Click to collapse
What do you expect to be displayed on phone's display when phone is booted into fastboot mode? Fastboot doesn't offer an on-screen menu like recovery. You have to enter the fastboot commands on Windows computer's CMD and/or Powershell.
Code:
fastboot devices
fastboot <FASTBOOT-SUBCOMMAND>

Yes, when fastboot is booted there's no menu like recovery, but the image I attached is what I see every time I give a command, even "fastboot devices", using CMD on the Windows 10 laptop (I have a Ryzen 5 SoC).

Question Made A Mess - ROG 5 CN Fastboot Loop

Was trying to flash my CN ROM to the WW ROM.
Forgot to turn on USB Debugging in Developer Tools.
Couldn't get it work using HunterTik's guide.
Ran flashall_ATF from windows explorer.
Command prompt flashed on screen then vanished.
Tried running flashall_ATF in an elevated command prompt.
It failed but has apparently wiped the ROM. Device is now stuck in boot loop to fastboot.
Whatever option I choose reboots the device back to fastboot.
Windows can see the device but adb devices returns List of Devices Attached is blank.
How do I recover the phone from here?

Found this thread Rog phone 5 stucked on fastboot
Ran this command: fastboot -v flash all WW_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.63_Phone-user.raw
Received these lines of text & now device boots to splash screen, gets stuck there, reboots a few times then sends me back to fastboot.
Still can't access recovery mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Device is now back in a fastboot loop with no access to any options but power off & restart.

Your phone is broken
Buy a new phone and don't try to mess with it next time

Flash back to CN and try again.
or, get a dump of the official firmware, then sent boot / recovery / super over fastboot manually.
[Windows] Asus OTA payload auto extractor
Since nobody is doing it, I thought I'd package it and just put it here to help people This is a packaged version of Vm03's payload dumper make to work with windows without installing python and other stuff I also included a single line script...
forum.xda-developers.com
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.

yurishouse said:
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
Click to expand...
Click to collapse
9008 rescue is the direction I was headed & you're right. Although, on reflection, the partitions were already deleted prior to running the 'fastboot -v flash all xx.raw' command. Not sure how, since that command was the only thing I did which resulted in something happening.

How to fix "Handshaking... [ERROR] UNEXPECTED RESPONSE: 0x78" or "Handshaking... [ERROR] UNEXPECTED RESPONSE: 0x58"

Hello, I installed Pixel Experience Android 13 Custom ROM. But it had IMEI issues, So I decided to roll back. When I opened SP Flash Tool, It said Select the Format All + Dowload Tool. I did the exact, But then it said, Disable verified boot or unselect the "Preloeader, Tkv, Dtbo, Trnsfs" I did what they said, Then, I flashed it completely, It said OK, I tried to boot in my device, But it wont budge. I guess it's bricked? I tried downloading an older firmware like previous version of the firmware for the same model, Then I opened the MTK Auth Bypass tool, I opened it, It used to work, But now, It gives an error:
► Installing driver... [OKAY]
► Waiting for brom... [FOUND]
● DETECT AS MTK USB Port (COM5)
► Configuration port... [OKAY]
► Handshaking... [ERROR] UNEXPECTED RESPONSE: 0x78
How to fix this error, and what could the reason be behind the bricking of the phone over no REASON?
Please guide, as I dont want to spend more on this phone as I alr went to Tech Support and spent my money there.
Thanks
[Update]: Found the Solution after 6 months, All I needed to do is to disconnect the Battery and reconnect it. Full detail on the last point in this thread I created: Infinix Fix

Re-flash Stock ROM.

jwoegerbauer said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
Dear Brother, I cant flash stock rom, unless I get the DA File, and I bypass the DA file, And the Bypass tool gives an error:
Handshaking... [ERROR] UNEXPECTED RESPONSE: 0x78
Is there anyway you could help me?

If phone can get connected by ADB then you connect computer and phone via USB-cable and run
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
adb reboot

jwoegerbauer said:
If phone can get connected by ADB then you connect computer and phone via USB-cable and run
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
adb reboot
Click to expand...
Click to collapse
ummm, i dont have custom recovery.....
if it could work without custom recovery plzz reply.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Carefully read posts.

can you flash via fastboot?
i may be saying something stupid, but I do not hwo ur device works lmao.

Arealhooman said:
can you flash via fastboot?
i may be saying something stupid, but I do not hwo ur device works lmao.
Click to expand...
Click to collapse
Ur Bio is relatable, lol, Btw, Yes, my android is fixed now, But its IMEI is unknown, Idk what to do now.

how did you fix it . i am stuck in the same thing

hello 00101 said:
how did you fix it . i am stuck in the same thing
Click to expand...
Click to collapse
I went to the tech support, I just saw him opening my mobile, maybe he disconnected the battery and reattached it, as disconnecting and reattaching battery resets usb connections.

Question Pixel 7 Pro stuck on "usb serial device" with no screen

Hey all,
after trying to flash images from a private build
[
1) REPO: repo init -u https://android.googlesource.com/platform/manifest -b android-13.0.0_r11
2) LUNCH: aosp_cheetah-userdebug
3) fastboot flashall -w for the out directory
]
the Pixel was stuck on a boot loop, showing the google screen but nothing more.
after battery drained, tried to put it on fastboot mode, unsucessfully
right now, the device is in this state, with black screen showing nothing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does someone know what tools are needed to save the device and guide to do it?
and second question - something in the process I described above is wrong about the flashing that caused it to fail?

Wow...where to begin...?!
I completely don't know to what end you were attempting to get to or how you were trying to get there, but looking at such an unconventional method of flashing and unconventional "private build" (so I assume not the full factory images Google publishes on their dev page), I wouldn't be surprised if you didn't permanently brick your device -- especially considering the outcome is a weird "USB Serial Device" and black screen/no fastboot mode...
But what I suggest is powering on using the button combination (I believe it is PWR & VOL+Down), sometimes it takes 1-2+ minutes holding it down.
I would suggest correcting the driver, but I'm unsure if that will lead anywhere if you cannot get into fastboot mode and/or the screen stays black. But, if you think it will help; download the Google USB Drivers (can be found HERE), unzip it, uninstall (and MOST IMPORTANTLY tick the box that says delete the driver software if it pops up) the "USB Serial Device", Scan for New Hardware, if the new driver does not identify as "Android Bootloader Interface" then -- right click the new driver -- click update driver -- and either Browse to the folder where you unzipped the Google USB Drivers or manually "Let Me Pick from available drivers" and manually select the .inf file to install the driver as. That should correct your driver issue, though I don't know how helpful it will be without the screen or being able to get into fastboot mode...
And, if you don't want to risk breaking your P7P, I would suggest from now on sticking with traditional methods of flashing (platform tools or recovery mode) and Google Full Factory Images or established ROMs....
Or maybe research considerably more in the unconventional method you are trying to attempt...
Good luck to you, seems you will need it...

it's basically flashing from here
Pixel Phones as Development Platforms | Android Open Source Project
source.android.com
which I assumed will be no problems
I have tried the combinations to fastboot, but unsuccessfully, all I see is black screen.
thanks for reply.