So, my Maxx suffered a power button failure and I should be receiving my warranty replacement from VZW sometime in the next day or two. Other than the power button not working, the phone is functioning fine. It reboots, runs normally, functions perfectly. I'm running .215 rooted and I want to return the phone back to stock before shipping it back. Problem is I can't access Boot Loader, no matter what I try. It's like it's not there anymore and when I command the phone into it using quick boot, adb, or the built-in menu, the phone just power cycles off. Let me try to explain:
I have Quick Boot installed and I can use it to boot into recovery without a problem. If I try to boot into Boot Loader, the phones powers off and stays off.
I've tried adb shell with the same results. I can connect to my PC and command the phone using shell commands but usin the 'adb reboot bootloader' command results in the same thing: phone power cycles off and stays off.
Even though my power button is AFU, I figured out I can still access the main recovery menu (the vol down to choose, vol up to select one) by holding down the vol up/down and plugging the phone into a charger. Same thing: power cycles off and stays off.
* Funny thing is although my power button doesn't work, I can still soft reset the phone by holding the power button in and vol down - which is what I need to do to exit recovery or other menus I need to input to a prompt using the power button.
Anyone know of this happening? MY guess is since my phone starts and functions normally otherwise, the boot loader is still there in some form. I just don't know how to access it. Any help would be much appreciated.
I can confirm this app will reboot bootloader
https://play.google.com/store/apps/details?id=org.riceknight.gs2reboot
Sent from my DROID RAZR using xda premium
Thanks Dave but not for me. Same result: phone power cycles off and just stays off when selecting reboot bootloader.
Sent from my DROID RAZR using xda premium
jeff_roey said:
So, my Maxx suffered a power button failure and I should be receiving my warranty replacement from VZW sometime in the next day or two. Other than the power button not working, the phone is functioning fine. It reboots, runs normally, functions perfectly. I'm running .215 rooted and I want to return the phone back to stock before shipping it back. Problem is I can't access Boot Loader, no matter what I try. It's like it's not there anymore and when I command the phone into it using quick boot, adb, or the built-in menu, the phone just power cycles off. Let me try to explain:
I have Quick Boot installed and I can use it to boot into recovery without a problem. If I try to boot into Boot Loader, the phones powers off and stays off.
I've tried adb shell with the same results. I can connect to my PC and command the phone using shell commands but usin the 'adb reboot bootloader' command results in the same thing: phone power cycles off and stays off.
Even though my power button is AFU, I figured out I can still access the main recovery menu (the vol down to choose, vol up to select one) by holding down the vol up/down and plugging the phone into a charger. Same thing: power cycles off and stays off.
* Funny thing is although my power button doesn't work, I can still soft reset the phone by holding the power button in and vol down - which is what I need to do to exit recovery or other menus I need to input to a prompt using the power button.
Anyone know of this happening? MY guess is since my phone starts and functions normally otherwise, the boot loader is still there in some form. I just don't know how to access it. Any help would be much appreciated.
Click to expand...
Click to collapse
If there is no bootloader you won't be able to start your phone at all as its THAT what basically boots the whole hardware and software....
How about adb reboot bootloader or adb reboot recovery commands ?
maarawoe said:
If there is no bootloader you won't be able to start your phone at all as its THAT what basically boots the whole hardware and software....
How about adb reboot bootloader or adb reboot recovery commands ?
Click to expand...
Click to collapse
The bootloader being the phone's "bios" is kind of how I understood it so I'm figuring it's still gotta be there. I just can't seem to access it or get to the "device/battery OK, device disconnceted" menu. I tried adb reboot bootloader and got the same results: power cycle to off and stays off. adb reboot recovery works fine.
Knowing this phone is going to be turned back in, is there any other way I could re-install .211 without having access to the bootloader screen?
jeff_roey said:
The bootloader being the phone's "bios" is kind of how I understood it so I'm figuring it's still gotta be there. I just can't seem to access it or get to the "device/battery OK, device disconnceted" menu. I tried adb reboot bootloader and got the same results: power cycle to off and stays off. adb reboot recovery works fine.
Knowing this phone is going to be turned back in, is there any other way I could re-install .211 without having access to the bootloader screen?
Click to expand...
Click to collapse
Try the eternity project flasher or the motorola's rds lite if they will be able to put the phone to the flash mode as they do that automatically...
maarawoe said:
Try the eternity project flasher or the motorola's rds lite if they will be able to put the phone to the flash mode as they do that automatically...
Click to expand...
Click to collapse
I posted a thread over at DroidRAZR.com and got some good feedback and troubleshooting help. It looks like the bottom line is the power button failed in the 'on' postion. One of the folks that replied to the DR thread caused his device to show the same 'AP Fastboot power-off' that I was getting by entering the 'Boot Mode Selection Menu' and holding the power button down while he vol+ to select AP Fastboot. It caused me to look a little closer at what the device was doing and that seems to be exactly what's going on - I powered th phone down using the Quick Boot app and was able to soft reset by holding down the vol- key by itself (didn't need to press power in conjunction). After it SR and i released the vol- key, the device rebooted by itself.
For your info, that thread is here: http://www.droidrzr.com/index.php/topic/3782-cant-access-boot-loader-menu-no-matter-what/
I tried working a thin piece of paper in around the button but no luck there.
Hi, today I've tried to unlock the bootloader in my lg g5 International (H850) and it worked, but now whenever I go to the recovery mode there's a dead robot with a "No command" text waiting for me. What can I do? I've tried many combinations but the no command interface is always there, no matter what I press.
Also to get to recovery mode I have to use adb because Volume down + power on boot doesn't do anything
Hello,
my phone is unlocked (did this a year ago through miflash_unlock tool when fastboot still worked) but after flashing latest stable global firmware and latest TWRP I cannot enter fastboot anymore.
- When I hold volume down and power key for a few seconds the phone powers on but the screen stays black. (The screen is clearly on but it's just showing black.) If I keep holding both keys it just powers off and on again, again to a black screen.
- In TWRP if I choose to reboot to bootloader I get the same black screen.
- If I'm booted into the ROM, USB debugging enabled on phone, connect to my PC with adb and run "adb reboot fastboot" the phone boots directly into the ROM.
- If I run "adb reboot bootloader" instead it boots into the black screen.
What is going on?
Found the solution here:
https://forum.xda-developers.com/showpost.php?p=80849843&postcount=5
Good day everyone. Recently my Mate SE (BND-L34) was left to charge overnight and wouldn't boot up the next day, it's just stuck on the start up screen. Unfortunately, developer options weren't on so no usb debugging although I can only access fastboot when I hold power + vol down. However, when I hold vol + up, nothing happens so I can't access any recovery menu. The phone is completely stock so no root, no custom recovery or firmware, locked bootloader, etc. I did try both methods mentioned here for locked bootloader: "https://forum.xda-developers.com/mate-20-x/how-to/fw-emui-9-1-0-123-evr-al00-t3935995"
Neither of them worked. With HStool, the program (HStool) closes itself after HiSuite has decompressed the download and is about to start installing recovery. The other method mentioned, when "installing recovery" part of the process starts, the phone exits fastboot and goes to the boot screen... both methods actually end in the same result with HiSuite giving me the error message "Recovery Failed" and the phone being on at the boot screen (exiting fastboot before the procedure has finished).
In case it's of any relevance the current firmware on the phone is BND-L34 8.0.0.362. Any suggestions would be greatly appreciated, thanks.
Hi!
M4 Aqua, E2303
Brief history, what I did before:
- On a full stock OS, first, I unlocked bootloader with fastboot oem unlock, which went through nicely.
- After that, I followed this thread to install custom recovery (twrp). Went through nicely (fastboot flash recovery recovery.img and fastboot flash boot boot.img).
- I was able to boot into recovery (twrp), and with the Install function, selecting Conceptify .zip it installed, rebooted.
- On the boot, the Conceptify gear logo was stuck spinning for a very long time. Then I just tried going into TWRP again to install Conceptify again, maybe for the second try it installs without the boot issue.
After this, I was no longer able to enter twrp recovery again. Okay, tried to flash the .img's again (boot and recovery), maybe I can at least get into TWRP recovery again, but no luck, despite both flash commands going through (both sending, writing were OKAY), without errors.
Current symptoms at this point:
- I still can get into fastboot (vol Up + usb plug in; LED red, then blue), and my PC can recognize the phone being in fastboot correctly, with serial number (in fastboot devices). It can still perform the flash/erase commands, but whenever I try fastboot reboot or fastboot reboot-bootloader, it doesn't reboot the phone. At this point, fastboot devices gives back a device in fastboot mode, but with a lot of question marks (?) instead of the serial number. On unplugging it, LED stays blue, like it is frozen or somthing. I kill the phone off with the power cutoff switch (next to microsd).
- holding just Power to turn on phone: Sony logo on the white background and is stuck. After a while I kill off with power cutoff.
- holding Power + vol Up, it vibrates once every 2 seconds or so. Nothing on screen, when I stop holding the buttons, stop vibrating. It however stays in a weird state, cause I can't get into fastboot for example (vol down + usb plug in; like I can do when it was powered off completely). I kill off with power cutoff.
- holding Power + vol Down: Sony logo on the white bkg, and stuck. After a while I kill off with power cutoff.
- tried the all-button hold: Power + vol Down + vol Up for 30 seconds, it was just vibrating every 2-seconds.
- flashmode with Flashtool: I downloaded a stock .ftf, loaded into FlashTool, but upon asking to connect the phone while holding vol Down, it can't detect it. The phone however lights red, then green on the LED light. Tried with both a new Flashtool (0.9.32.0, and a recommended older one as well: 0.9.18.6).
Is there something else I could try to get a working TWRP recovery again, and be able to boot into it?
Thanks for your help!
My M4 (E2312) have pretty much the same symptoms: can not boot anything and just stuck on SONY logo, Flashtool does not recognize phone in flashmode (Vol -), just fastboot. And using fastboot to flash system, boot, recovery shows finished processes but phone does nothing new. And phone does not response well to USB, only after a reset then it updates the status.
I have Pexo ROM v3, custom TWRP, SkyMelon 9 I think,Rooted SuperSU and Magisk( has conflicts so when I boot some pop up says X app has stopped working. When I install some more apps to use it was ok, then the pop ups show up more and more and then it decides to boot loop to the stage we are now.
I have tried install 0.9.33 and 0.9.23.1( somehow only 0.9.23.1 can install 3 drivers), Xperia Companion, Emma, ggsetup 3.2.0.1, Driver SONY so0104 (so0113 ADB interface- status show it cannot start),
So either it is the drivers on computer, the computer USB ports, the phone's software or hardware defects lead to software that caused it.
bdnlspam said:
Hi!
M4 Aqua, E2303
Brief history, what I did before:
- On a full stock OS, first, I unlocked bootloader with fastboot oem unlock, which went through nicely.
- After that, I followed this thread to install custom recovery (twrp). Went through nicely (fastboot flash recovery recovery.img and fastboot flash boot boot.img).
- I was able to boot into recovery (twrp), and with the Install function, selecting Conceptify .zip it installed, rebooted.
- On the boot, the Conceptify gear logo was stuck spinning for a very long time. Then I just tried going into TWRP again to install Conceptify again, maybe for the second try it installs without the boot issue.
After this, I was no longer able to enter twrp recovery again. Okay, tried to flash the .img's again (boot and recovery), maybe I can at least get into TWRP recovery again, but no luck, despite both flash commands going through (both sending, writing were OKAY), without errors.
Current symptoms at this point:
- I still can get into fastboot (vol Up + usb plug in; LED red, then blue), and my PC can recognize the phone being in fastboot correctly, with serial number (in fastboot devices). It can still perform the flash/erase commands, but whenever I try fastboot reboot or fastboot reboot-bootloader, it doesn't reboot the phone. At this point, fastboot devices gives back a device in fastboot mode, but with a lot of question marks (?) instead of the serial number. On unplugging it, LED stays blue, like it is frozen or somthing. I kill the phone off with the power cutoff switch (next to microsd).
- holding just Power to turn on phone: Sony logo on the white background and is stuck. After a while I kill off with power cutoff.
- holding Power + vol Up, it vibrates once every 2 seconds or so. Nothing on screen, when I stop holding the buttons, stop vibrating. It however stays in a weird state, cause I can't get into fastboot for example (vol down + usb plug in; like I can do when it was powered off completely). I kill off with power cutoff.
- holding Power + vol Down: Sony logo on the white bkg, and stuck. After a while I kill off with power cutoff.
- tried the all-button hold: Power + vol Down + vol Up for 30 seconds, it was just vibrating every 2-seconds.
- flashmode with Flashtool: I downloaded a stock .ftf, loaded into FlashTool, but upon asking to connect the phone while holding vol Down, it can't detect it. The phone however lights red, then green on the LED light. Tried with both a new Flashtool (0.9.32.0, and a recommended older one as well: 0.9.18.6).
Is there something else I could try to get a working TWRP recovery again, and be able to boot into it?
Thanks for your help!
Click to expand...
Click to collapse
Yes, I also tried installing conceptify but it doesnt work. At this point its better if you stick with the stock rom, remove as much bloatware as possible and consider it a phone because almost none of the ROMs here work stability wise, or they maybe stable but some features like display brightness or speakers dont work. So I recommend you install stock rom via flashtool and then unlock the bootloader via flashtool again and install twrp again. Also if possible try reinstalling the drivers for the phone in flashtool. Hope this works mate.
Not my name said:
Also if possible try reinstalling the drivers for the phone in flashtool.
Click to expand...
Click to collapse
Thanks for your answer!
Unfortunately, I still can't make Flashtool recognize my M4 as booted in flashmode. Tried installing the drivers with \Flashtool\drivers\Flashtool-drivers.exe , but choosing the "Flashmode drivers" option, it failed during the install (I guess cause there wasnt a connected device that supports it), tried both with phone being connected in flashmode (volDown + plug-inUSB), and phone disconnected as well.
bdnlspam said:
Thanks for your answer!
Unfortunately, I still can't make Flashtool recognize my M4 as booted in flashmode. Tried installing the drivers with \Flashtool\drivers\Flashtool-drivers.exe , but choosing the "Flashmode drivers" option, it failed during the install (I guess cause there wasnt a connected device that supports it), tried both with phone being connected in flashmode (volDown + plug-inUSB), and phone disconnected as well.
Click to expand...
Click to collapse
Can you try it on a Linux PC I guess?