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).
Related
Hi
I have been having this issue with my Xoom for quite some time after I tried to reset it back to stock and followed the instructions I found at a thread which I have lost, but included the instruction to lock the bootloader, which I have since learned is not advisable, and have not been able to fix it after many Google searches for solutions.
Each time I turn my Xoom on it comes up with this message:
{
"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"
}
So far I have tried solutions from these forum threads:
Failed to boot LNX 0x0004 Startinmg RSD mode 2 Xoom WIFI ONLY MZ604
Failed to boot LNX 0x0004 Startinmg RSD mode 2 Xoom WIFI ONLY MZ604
(Xoom WiFi Only MZ604) failed to boot lnx 0x0004 - starting rsd mode 2
Stuck at Motorola Dual-Core? [Wifi-Only]
Every time I get stuck at the same place: <waiting for device> on my command prompt, while my Xoom sits on this screen:
I have set up fastboot and adb on my pc using the tool I found on this thread:
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.2
My Xoom is a wi-fi only EU model (wingray), I do not have the original USB cable that it came with though I do not think that makes a difference. I am at a loss as to how to fix this problem.
Is there anyone with an up to date solution for this issue? Thanks.
what happens when you type "adb devices" ?
the commands for flashing the stock image are as follows (i have a copy, if you need it PM me)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Fixed!
Thanks for replying
After you questioned what happened when I typed 'adb devices' I had the very belated brainwave of maybe checking that it was correctly set up with one of my other devices (duh! ><). Thus it was I discovered that despite the installer I had used assuring me that it was correctly set up, I found that it wasn't actually correctly set up.
With my Nexus 7 as a test device, and the WugFresh Nexus Toolkit at my disposal I was able to set up ADB so that it worked with my N7. Plugging in my Xoom I found that it was still invisible to my computer, so I Googled for Motorola USB drivers and came up with the Motorola Device Manager which installed it's own ADB driver. Once that does done I was pleased to find that my PC was now able to see my Xoom and I have flashed the stock images I got from the Motorola website and my Xoom has now been fixed!
Thanks for your help and inspiration
That's great news! Enjoy your resurected Xoom
hello my oneplus 6 has been blocked on fastboot mode.:crying:
the problem is that I format the phone system with the twrp by mistake. now the phone is empty neither system nor twrp. I tried several methods like msmdownloadtool but the phone does not connect.
i tried to install the twrp with the command prompt when i put the command adb devices the list of phones attached remains empty.
please help me
{
"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"
}
Try too flash stockrom via fastboot, following this thread https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Please read the instruction carefully.
elbachiri said:
hello my oneplus 6 has been blocked on fastboot mode.:crying:
the problem is that I format the phone system with the twrp by mistake. now the phone is empty neither system nor twrp. I tried several methods like msmdownloadtool but the phone does not connect.
i tried to install the twrp with the command prompt when i put the command adb devices the list of phones attached remains empty.
please help me
Click to expand...
Click to collapse
in fast boot mode, only fastboot commands work like "fastboot boot twrp.img" will boot you into twrp
MrSteelX said:
in fast boot mode, only fastboot commands work like "fastboot boot twrp.img" will boot you into twrp
Click to expand...
Click to collapse
When i try the commands fastboot boot twrp.img
The commands gives me failed:error
elbachiri said:
hello my oneplus 6 has been blocked on fastboot mode.:crying:
the problem is that I format the phone system with the twrp by mistake. now the phone is empty neither system nor twrp. I tried several methods like msmdownloadtool but the phone does not connect.
i tried to install the twrp with the command prompt when i put the command adb devices the list of phones attached remains empty.
please help me
Click to expand...
Click to collapse
how Is your phone recognized?
°Washy said:
how Is your phone recognized?
Click to expand...
Click to collapse
Recognized like android phone
despite the drivers are installed
ndp_singe said:
Try too flash stockrom via fastboot, following this thread https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Please read the instruction carefully.
Click to expand...
Click to collapse
https://ibb.co/ctgDjft
extract the images.zip (on the same directory - not a sub directory i.e images\ ).
extract Others_flashall.zip.
Your directory will look like this:
then run flash-all-partitions.bat.
Warning: that will wipe all your data
thanks i put the .bat files in the official rom 9.0.2 Oxyegen.rar
after I install the rom with the program tool all in one.
now all its running well thanks for your help
I just got this tablet a few days ago so I was wondering if it was possible to root it as I already have a primary phone that I use.
Search the WEB for "root any MTK device"
jwoegerbauer said:
Search the WEB for "root any MTK device"
Click to expand...
Click to collapse
Will the method still work even though it's not a MTK device? On CPU-Z it says it's a ARM Cortex device.
ARM Cortex is a processor technology,, what in your case is used by MediaTek when they developed and produced the chipset for your phone.
That seems to make sense. I'll try the method when my laptop charges back up. Thanks for the help
jwoegerbauer said:
Search the WEB for "root any MTK device"
Click to expand...
Click to collapse
The method doesn't seem to work because after doing
adb reboot bootloader
The device just reboots and when I do
fastboot oem unlock, it gets stuck on waiting
What's the method you always are referring to?
jwoegerbauer said:
What's the method you always are referring to?
Click to expand...
Click to collapse
The mtk one you told me about
I was following this to be more specific
The steps to prepare programmatically unlocking a phone's bootloader by means of fastboot what most people do - me included - are
Code:
adb devices <- your phone must be listed here
adb shell "getprop ro.oem_unlock_supported" <- The return value must be 1, if not then don't proceed
adb reboot fastboot <- or: fastboot reboot bootloader
fastboot devices <- your phone must be listed here
to verify the phone is succesfully connected and acting in fastboot ( aka bootloader ) mode.
If phone isn't shown then a fastboot connection doesn't got established.
adb devices - works
adb shell "getprop ro.oem_unlock_supported" - I get a 1
adb reboot fastboot - device just reboots normally
fastboot reboot bootloader - says <waiting for any device>
fastboot devices - just shows a empty line of text
{
"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"
}
You simply confirmed that fastboot isn't working.
Hints:
1. Install its latest version ( -> see my signature )
2. Additionally install the "Android USB Driver" suitable to your phone: with regards to some phones this driver is also needed to make fastboot working - may be your phone is one of these.
jwoegerbauer said:
You simply confirmed that fastboot isn't working.
Hints:
1. Install its latest version ( -> see my signature )
2. Additionally install the "Android USB Driver" suitable to your phone: with regards to some phones this driver is also needed to make fastboot working - may be your phone is one of these.
Click to expand...
Click to collapse
I've finished doing 1 and 2. Do I retry going into fastboot again?
Oskii said:
I've finished doing 1 and 2. Do I retry going into fastboot again?
Click to expand...
Click to collapse
Do what you think is right ...
It seems that the device is still unable to go into fastboot mode.
I will double check to make sure
In @Oskii 's defense, I've had some Alcatel devices that somehow seemed to have fastboot disabled (namely the Alcatel 1 / Orange Rise 54, IIRC), I don't know how though. It's just impossible to boot into any bootloader/fastboot mode (or at least I never found out how).
I *did* manage to (sort of) root them using a method I don't remember (sorry ; it was an obscure app), but it was unreliable : root wouldn't always "get applied/stick" after boot and I had to reboot and cross my fingers to make it work again.
I know it's not of much help, but still…
It's still not working :v
It cannot without booting to fastboot mode.
I purchased a nice Willeyfox Swift in very good condition with Android 7.1.2. , wanted to install LineageOS + MicroG via ADB.
OEM unlock and USB Debugging Mode enabled, drivers installed, the device was perfectly recognized, bootloader unlocked ("DEVICE STATE- unlocked"),
but then problems started:
When I wanted to flash TWRP via platform-tools, „< waiting for any device >“ appeared. This happened using Windows 10 as well as Mac OS (so I guess, drivers aren’t the problem).
TWRP -package is: „twrp-3.5.0_9-0-crackling,img“
{
"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"
}
Has anyone any idea?
Thanks for help!
ADB and Fastboot are 2 completely different softwares: ADB deals with device's Android OS whereas Fastboot deals with device's bootloader.
To successfully run Fastboot commands you have to establish a Fastboot connection as 1st thing of all things:
Code:
adb devices
adb reboot bootloader
fastboot devices
jwoegerbauer said:
ADB and Fastboot are 2 completely different softwares: ADB deals with device's Android OS whereas Fastboot deals with device's bootloader.
To successfully run Fastboot commands you have to establish a Fastboot connection as 1st thing of all things:
Code:
adb devices
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
Thanks a lot - I skipped "adb reboot bootloader"
Now it works.
Just with a problem often posted along with Wileyfox:
After successfully having installed TWRP, the device only reboots into bootloader, not to system.
But I'll follow this problem on other threads (or do you have an answer?)
finally, I managed it: Thanks to wowi63 , I first intalled Cyanogen, before installing lineageOS. Thank you again for reminding me not to forget <adb reboot bootloader> (I did it before with another device, even had it on my list of procedures, but was just to blind to see...)
I'd like to close this thread
jwoegerbauer said:
ADB and Fastboot are 2 completely different softwares: ADB deals with device's Android OS whereas Fastboot deals with device's bootloader.
To successfully run Fastboot commands you have to establish a Fastboot connection as 1st thing of all things:
Code:
adb devices
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
I logged into XDA just to thank you very much!
Cant belive I failed something so elementary.
Finally after 2 days I am able to fix my device.
Thanks.
When I use "fastboot reboot fastboot" command it only reboots and turns on the phone.
I want to try install a GSI rom but I can't get into it.. Is there a way to make it happen?
Am I wrong trying to install it this way? I was reading some forums and I tried a few things without results.
speedmetal444 said:
When I use "fastboot reboot fastboot" command it only reboots and turns on the phone.
I want to try install a GSI rom but I can't get into it.. Is there a way to make it happen?
Am I wrong trying to install it this way? I was reading some forums and I tried a few things without results.
Click to expand...
Click to collapse
Try this:
First reboot to recovery, once you're there select reboot to bootloader, then press and hold VOL UP while it's rebooting, after that voila your now on Fastboot 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"
}
Thx for your reply! And sorry for my poor explanation about the problem, I know how to get into fastboot mode but there is another instance of it, and its fastbootD mode that allows you to make modifications on the dynamic partition called "super", the suposed way to get into it is typing the command "fastboot reboot fastboot" in the normal fastboot mode, but nothing happens, the phone just reboots into normal system.
When I try to erase system in normal fastboot mode it cannot find that partition cause this is in super, it will be great if we can experiment with that but Im stuck right now...
I dont know if this worth it.... Any of you already tried a GSI rom?
speedmetal444 said:
Thx for your reply! And sorry for my poor explanation about the problem, I know how to get into fastboot mode but there is another instance of it, and its fastbootD mode that allows you to make modifications on the dynamic partition called "super", the suposed way to get into it is typing the command "fastboot reboot fastboot" in the normal fastboot mode, but nothing happens, the phone just reboots into normal system.
When I try to erase system in normal fastboot mode it cannot find that partition cause this is in super, it will be great if we can experiment with that but Im stuck right now...
I dont know if this worth it.... Any of you already tried a GSI rom?
Click to expand...
Click to collapse
Yes, but unfortunately their SW REV was just 0, but by device’s one is always 1 (i.e. too high for TWRP and GSI’s atm)
(* Samsung blocks SW REV downgrades at all, the only way to bypass is to run the below for not waiting)
Now it needs waits, or if you don’t wait, you instead need to shut MTK ‘‘secure’’ boot and ‘‘secure’’ Download off at all.
Helix-one said:
View attachment 5299239
Click to expand...
Click to collapse
Are you going to flash TWRP by ADB sideloads on the A12's Recovery mode? If yes, good luck!