Hello all, I have a Moto G5 Plus and I am currently exploring as many ways as possible to get this thing to boot with a broken power button. The phone has USB debugging enabled because I thought that was all I would need if it ever did completely drain its battery. It did die this weekend and I'm finding it more difficult than anticipated to boot this thing. Options I've tried:
1. Pushing extremely hard on the power button. For awhile this worked, seems to be completely hosed now though.
2. Booting into Fast Boot, which is great, except to actually boot the phone it requires a button press of the power button.
3. Android Debug Bridge, which does not seem to recognize my phone. I was hoping the adb reboot command would work in this case, but so far no luck. Could be a drivers issue.
Is there any tool available that is specific to the Moto G5 plus that can boot this phone? I would think any tool that can flash it should also have the power to boot it, but I'm not sure where to start. Any ideas would be appreciated, thank you!
*** This was solved, I posted an update as the first reply. ***
Just wanted to give an update for anyone who finds this in the future. I believe that USB debugging is required to be on, I installed Android Debug Bridge like normal as well as the basic motorola drivers. Boot your phone into fast boot by holding down the volume button and then plugging in your phone in the PC. From here open a command prompt from within the adb folder "left shift + right click > open command prompt". Issue the command "fastboot reboot" and your phone will reboot and boot up.
greengreenwine said:
Just wanted to give an update for anyone who finds this in the future. I believe that USB debugging is required to be on, I installed Android Debug Bridge like normal as well as the basic motorola drivers. Boot your phone into fast boot by holding down the volume button and then plugging in your phone in the PC. From here open a command prompt from within the adb folder "left shift + right click > open command prompt". Issue the command "fastboot reboot" and your phone will reboot and boot up.
Click to expand...
Click to collapse
If your phone is booted you can use something like this to reboot, boot into TWRP or fastboot without the need of the powerbutton:
https://play.google.com/store/apps/details?id=phongit.quickreboot
It's a standard app on my device.
Sent from my Moto G5 Plus using XDA Labs
It is cool, that you have fixed it.. but you should clbsider on sending it to be fixed, if your device freezes and you don't have ylur computer with you, you'll end with a dead phone for the day...
Related
OK, so I flashed the wrong ROM today (I9000HVJH1) and the phone now boots into recovery everytime the battery is inserted. I have tried all the tricks to get back to download mode with no luck. The device is recognized by the USB in recovery and was able to push the root update file but can not get it to apply sdcard:update.zip (just sits there and doesn't respond to the power button unless i hold it). Interesting thing is when I plug the USB in and insert the battery, it never goes to charging, it boots into recovery.
Tried:
1. Plug USB
2. Hold vol up (and down but the keys are now backwards in recovery)
3. Insert battery
and
1. Power down (removed battery)
2. Hold vol up + down + power
and
1. Hold vol up (and down too for a few hundred times)
2. Hold power until Samsung logo then release
and
all combo's with and without the USB plugged into the phone.
Beside the tricks shown on the forum, can anything think of a way to get this phone into download mode instead of it constantly booting into recovery? ADB see's the device, just no root access or knowledge of how to get it to apply the update.zip that would root the device.
Thanks~!
http://forum.xda-developers.com/showthread.php?t=741027&page=3
Wrong section. This belongs in general...
Sent from my messenger rabbit
UPDATE!!
After going to T-Mobile on Monday to buy a new Vibrant, I started to think about how to get the "bricked" one working again. I was able to admit defeat for long enough to get a new one but was bothered that I couldn't fix my old one.
I started to think about what I could and couldn't do with the "bricked" one. It would constantly boot start to Android Recovery with error about CSC. No matter what combination of buttons pressed, held, release, the darn phone would never get back to a download mode. Since it could never boot into the OS, ADB seemed impossible. The GOOD news (as it turns out) was when it booted into recovery if I disconnected the USB and reconnected, my computer recognized it and Odin saw it on COM10. I began to look at the batch file for the one click root and noticed the line "adb reboot download". I had messed with ADB the day I screwed up the phone but always tried to do commands after typing "adb shell" and without super user access, I felt doomed. Last night I thought what the heck and powered up the old Vibrant and it went straight to recovery. After another 45 minutes of trying to manually put it into download mode I opened a command prompt and typed "adb reboot download" and the freaking phone rebooted into download mode!!!! So after flashing back to stock I now have fixed the phone
So for anyone who can't get their Vibrant to stop rebooting itself into recovery here is a simple breakdown of what I did.
1 - Power up phone (mine went straight to recovery)
2 - Un-plug the USB and plug it back in (computer should recognize the connection)
3 - Open command prompt and change to the directory that has adb.exe
4 - Type "adb kill-server" and then enter
5 - Type "adb reboot download" and then enter
6 - Phone should reboot into download mode and ready to flash
Make sure you have Odin open with the pit and pda file loaded as there seems to be only a short window of time in which the phone will accept the download and get the status bar moving. If you wait too long, repeat the steps above and start the flash quickly.
I hope this helps someone out that might be experiencing the same problem as me.
I forgot my pin on my GT-P7510 and even though there are only three buttons I am able to press I cannot seem to get to a menu with a clear data or reset option. Does anyone know how I may do this?
Edit: I was able to get to the menu on my GF's TAB using `adb reboot recovery`, unfortunately I don't have USB debugging enabled on my device :-/
And just FYI this is what I've discovered:
Holding volume up when powered on brings up a menu with a flashing rectangle over an Android with a shovel and the text "Downloading..." below it, or the USB logo.Using the volume up key will toggle between the two.
Selecting the Android by pressing the voume down key will bring up a "ODIN3 Download Mode (Protocol v2) menu that says the OEM:Lock is unlocked and waiting for a USB cable.
Selecting the USB logo brings up text saying Fastboot USB download protocol.
Holding volume up from the Samsung Galaxy Tab boot screen until boot will bring the device up in safe mode. (Edit: Actually volume up need only be pressed just before the animation is over when it says "Samsung").
Holding volume down after the initial boot logo appears to have no effect.
Holding both after the inital boot logo appears to have no effect.
Update: Solved! I had to manually build the fastboot application on my ubuntu machine in order for the device to appear when running `fastboot devices`. After that it simply required running `fastboot -w`.
Update
I called Samsung support this morning and they informed me that they will not support the device until it launches which is quite lame. I've basically given up trying to find the correct 3-button combo to bring up the restore screen and focused more on the fastboot and Odin3.
I've attempted to get my device recognized when using the `fastboot devices` command so that I can simply perform `fastboot -w` to reset everything however neither on my Linux box nor Windows box will the device appear.
Does anyone have any idea which drivers may work with the fastboot on this device? I've tried the google drivers included in the latest SDK.
I would really appreciate help with this, and would be happy to help out this community as much as I can once I am able to use my device.
Thanks!
bbzbryce said:
I called Samsung support this morning and they informed me that they will not support the device until it launches...
Click to expand...
Click to collapse
Wow, that's kinda weird that they would say that. At the conference they were helping everyone with the devices.
I'm pretty sure that the only way to get into recovery is through adb. It's quite unfortunate.
happilyaccosted said:
Wow, that's kinda weird that they would say that. At the conference they were helping everyone with the devices.
Click to expand...
Click to collapse
I called again later today and the guy attempted to help, however, he said that the documentation is not yet available to him.
smaskell said:
I'm pretty sure that the only way to get into recovery is through adb. It's quite unfortunate.
Click to expand...
Click to collapse
I'm fairly certain I should be able to use either the fastboot or Odin3 interface to reset the device. Anyone have experience with either on this device? Thus far I haven't been able to have the device appear on the fastboot listing.
Odin 3
Anyone have link to odin 3?
Why hasn't fastboot been posted yet?
Having a working fastboot really frustrated me.
Yesterday when I woke up, my Galaxy Tab 10.1 was turned off, and when I powered it on, it would go into an infinite loop with the boot animation. fastboot -w fixed this for me
I'm sad nobody posted their fastboot binary that actually works...so here it is! Compiled this on x86_64 Ubuntu 11.04, but it's a 32-bit binary linked against /lib32 stuff, so if you're on Ubuntu 11.04, make sure you have ia32-libs installed.
I'm having the boot loop problem, but I can ONLY get into "upload mode"
I cannot get into the USB Mode, or the Android OS reset mode that I've read accompanies the Power + Volume down button and Power + Volume up button.
So, from merely "upload mode" what can I do?
I have a Nexus 4. While trying to update to lollipop, my cellphone crashed and its stuck in bootloop animation. I have a lot a photos and contacts that i don't want to loose, the rest i don't really mind (If it's possible to save the rest, i'll save it). The thing is i don't have any backup. USB debugging and dev. are disabled. My question: "Is there a way of manually enable USB debugging via terminal or cmd?" I have a pc and a mac and i have SDK tools.
Glitcherman said:
I have a Nexus 4. While trying to update to lollipop, my cellphone crashed and its stuck in bootloop animation. I have a lot a photos and contacts that i don't want to loose, the rest i don't really mind (If it's possible to save the rest, i'll save it). The thing is i don't have any backup. USB debugging and dev. are disabled. My question: "Is there a way of manually enable USB debugging via terminal or cmd?" I have a pc and a mac and i have SDK tools.
Click to expand...
Click to collapse
i think i could would enabling it in dev options but im not sure jt make sure you have the lg nexus 4 adb drivers installed boot into bootloader and type the command "fastboot devices" to see if its recognized (again im not sure.) http://forum.xda-developers.com/nexus-4/general/drivers-nexus-4-driver-windows-t1992345
you could try and flash factory image and to not lose data try this.... http://forum.xda-developers.com/showpost.php?p=56916654&postcount=3344
Glitcherman said:
I have a Nexus 4. While trying to update to lollipop, my cellphone crashed and its stuck in bootloop animation. I have a lot a photos and contacts that i don't want to loose, the rest i don't really mind (If it's possible to save the rest, i'll save it). The thing is i don't have any backup. USB debugging and dev. are disabled. My question: "Is there a way of manually enable USB debugging via terminal or cmd?" I have a pc and a mac and i have SDK tools.
Click to expand...
Click to collapse
Power phone off, hold Vol Down + Pwr, you will boot to stock recovery (supine android with an exclamation point sign over it), press Vol Up + Power, from the resulting menu, wipe the /cache partition, and then reboot. Your device will be out of bootloop and boot properly. Give it a few minutes.
ariesgodofwar said:
Power phone off, hold Vol Down + Pwr, you will boot to stock recovery (supine android with an exclamation point sign over it), press Vol Up + Power, from the resulting menu, wipe the /cache partition, and then reboot. Your device will be out of bootloop and boot properly. Give it a few minutes.
Click to expand...
Click to collapse
Already did that, nothing much happens. :|
Okay, first off, I know there are threads about this, but none of them were helpful on my problem. So if you're having the same issue and it worked, don't forget to hit the thanks button! This isn't a very well made instruction, but it'll suffice. I haven't seen this method, so I thought I should share it.
Device: LG G2 AT&T D800
- I assume this may work on all the other variants as well
Issue:- Device won't boot to Download Mode even when doing VOL Up + USB, and my android system has crashed/force closed
Solution: (Warning: this is very tedious and annoying so put up with it like I did)
1. If your phone doesn't have USB debugging already enabled, go ahead and do so
- This... I had to press quickly to get to the Software Tab and tried to simultaneously click OK while trying to turn on Developer Option.
2. Install ADB if you haven't already. Run adb as Admin, type in adb reboot fastboot
- You should then boot into fastboot with a bunch of small white text saying some fastboot and shizz
3. Go ahead and hold the power button, at the same time holding the Volume Up button
4. DOWNLOAD MODE should come up
5. You can now restore your G2, You can look up the files somewhere here in the forums to restore.
Good luck, enjoy, say thanks, click thanks.
"We build too many walls, and not enough bridges"
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Conrad-007 said:
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Click to expand...
Click to collapse
Hi, Conrad-007...
This is very strange - your Nexus 7 is clearly 'bootable' (sort of), with a functioning bootloader, ie., it's not hardbricked... or you wouldn't be seeing the Google logo.
In the distant past, back when I used to experiment with custom kernels on my Nexus 7, it sometimes required the POWER BUTTON+VOL DOWN buttons be pressed and held down for a good 30 seconds or more, to generate the necessary 'interrupt', and force the device into the bootloader.
My first instinct, is to suggest you may possibly have a problem with your VOL DOWN button, and maybe it's stuck somehow or not making contact.
It also occurred to me, that you might be able to access the bootloader with...
Code:
adb reboot bootloader
...or possibly...
Code:
adb reboot fastboot
...and even...
Code:
adb reboot recovery
But unfortunately, I'm pretty sure you need to be running fully booted Android or booted into a custom recovery (eg., TWRP) before you can issue ADB commands. I haven't tinkered around in this area of Android for a couple of years now, so my memory of the specifics is a little hazy.
Anyhow, here's a fairly comprehensive listing of Nexus 7 button presses/interrupts, which maybe of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
--------------------------------
Anyway, just some thoughts that might give you some clues/ideas, that may resolve your problem.
Good luck, and I hope you find something that works.
Rgrds,
Ged.
Thanks Ged for the detailed answer.
Unfortunately it seems that my Nexus is not booting complete (not finishing the booting sequence due to corrupted bootloader?) and so I cannot send to it any adb or fastboot command...
I read in the meantime that holding the VOL up button while powering up the Nexus, it will bring it in the APX mode (whatever this mean) and indeed, my computer recognize it as "APX" device.
I hope at least that this is a good sign and a first step to bring my Nexus back to life... but I have no idea what is the APX mode and what can I do in this mode to attempt to save my device...
Do you (or somebody else) have (has) an advice or tutorial for me concerning this?
Regards,
Conrad
Hi Conrad.
I'm in exactly the same situation (I've mistakenly posted a duplicate thread here https://forum.xda-developers.com/nexus-7/general/bricked-tilapia-t4005149). Let's continue here. So:
1. I spent 4 hours trying all possible button press combinations, including VERY long presses. I didn't notice any APX device or Uknown device connected to Windows. I might have missed it, you gave me hope. I will check again.
2. APX mode enables low level access to the chipset via nVidia tool nvflash. You probably came accross these threads here on xda:
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-using-t3342364
https://forum.xda-developers.com/showthread.php?t=2564615
https://forum.xda-developers.com/showthread.php?t=2455927
https://forum.xda-developers.com/showthread.php?t=2340237
I haven't so far, as I was not aware of the visibilty of the tablet in Windows. I will check again.
Well, I must have been blind not to have seen all the posts here on xda and everywhere else. I went through the threads and now I know:
1. I can see the tablet in APX mode in Windows. Possibly I could correctly set up the driver.
2. This would be totally useless, since I hadn't backed up necessary blob.
I have a new paperweight