Database Users

Phone dead after try to Reboot to Recovery from Power Menu - please help :(

Hello,
I got a Moto G4 with the LineageOS version 7.1.2 from the end of May.
I wanted to reboot to recovery, from the power menu options. Never thought that something like this may happen.
The only sign of life is the blinking LED while being connected to AC or USB port of PC (it goes fast on and off).
The key combinations don't do anything (even if I hold for 30 seconds). So no possibility to force restart? Access fastboot? Boot menu? Anything? :crying:
Never had a weird issue like that and don't find anything on google about it.
Any ideas? It is the only phone I got, would be soooo bad if it is somehow dead now.

Try holding the power button down for 2-3 minutes, this may invoke a hard restart which may break your device out of whatever state it's in. Then you may be able to reboot as normal.
What TWRP recovery do you have?

Thank you so much, after 2 minutes the phone restarted. I always thought the time needed was 20 seconds.
You saveed me <3
What might be interesting, my phone still consumed battery while it was off, went from 100 to 14%

I also had the same issue yesterday but I did a hell lot of things to flash bootloader again
I first searched xda Moto forums ,there I found 1 thread where in I had to blank flash some file using Qualcomm drivers installed in pc....
Then I was able to boot to bootloader...this was a different bootloader I had seen...but I cud see bootloader version B.***
In bootloader the recovery did not boot
'Your phone did not boot' was d msg
Then I tried flashing fastboot roms of Moto g4 plus
1st I tried mpj 6.0
2nd npj 14.11 7.0
In both above cases partition flash gpt.bin failed...preflash validation failed....!
So I tried fastboot flash recovery twrp.img
Then also it failed ......unable to initialize partition table...!
I loses hopes and worried that I need to go to service center
Then I saw that the same rom which was there was to be flashed
Then I fastboot flash latest rom npsj14.4...
This time I was able to flash partition gpt.bin
Then I successfully flashed bootloader.img ,
Then when flashed boot.img again I faced ' preflash validation failures...'!
Now I saw mobile bootloader was like official Moto bootloader
Finally I successfully flashed twrp.img
This time no error occurred because gpt.bin and bootloader of npsj14.4 worked
From twrp I restored the backup...and life of my phone came back
If I had seen this method earlier only it would have saved 2-3gb data for dwnlding all version fastboot roms and time,the worry I felt...so disgusting......so I feel that reading others problems in forum is very useful for us in future....
ty @ECHO u saved one Junior members problem otherwise had to suffer like me??

Help: G4 Plus won't start after accidentally hitting "Open" on icon pack install.

Help: G4 Plus won't start after accidentally hitting "Open" on icon pack install.
I got this phone literally yesterday, it's unrooted, worked perfectly fine until my hand slipped when installing an icon pack from the play store and I hit "Open" - the phone immediately crashed, and now will not boot. I've tried using standard power on, powering on through the recovery bootloader, and entering recovery mode through said bootloader, in every instance it displays the Motorola startup screen, plays through its sequence of animations, then as soon as the Lenovo brand icon shows on screen emits one long pulse of vibrate and then turns off again.
I can't pull the battery because I don't have the required micro-hex screwdriver. Can anyone help?

Yodhrin said:
I got this phone literally yesterday, it's unrooted, worked perfectly fine until my hand slipped when installing an icon pack from the play store and I hit "Open" - the phone immediately crashed, and now will not boot. I've tried using standard power on, powering on through the recovery bootloader, and entering recovery mode through said bootloader, in every instance it displays the Motorola startup screen, plays through its sequence of animations, then as soon as the Lenovo brand icon shows on screen emits one long pulse of vibrate and then turns off again.
I can't pull the battery because I don't have the required micro-hex screwdriver. Can anyone help?
Click to expand...
Click to collapse
can you reboot to bootloader and start recovery? Then clear cache and see if it helps to boot your device? Or if not make a factory reset if it won't help. Maybe the icon pack screwed up something.
Report back. After that, if nothing worked, you can try this:
Is your device recognized by fastboot? If yes, try "fastboot devices" and see if it shows serial number.
Then try to flash the latest stock in the following guide rom if you have one of this devices https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

strongst said:
can you reboot to bootloader and start recovery? Then clear cache and see if it helps to boot your device? Or if not make a factory reset if it won't help. Maybe the icon pack screwed up something.
Report back. After that, if nothing worked, you can try this:
Is your device recognized by fastboot? If yes, try "fastboot devices" and see if it shows serial number.
Then try to flash the latest stock in the following guide rom if you have one of this devices https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
Hi, thanks for responding. After four or five attempts to boot into recovery it succeeded; wiping the cache did nothing so I did a factory reset, which worked and now the phone will boot to the setup stage. Unfortunately now I'm getting "The device was reset. To continue, sign in with a Google Account that was previously synced on this device.", which after googling seems to be a security feature - the problem is it doesn't accept the google account credentials, every time I enter them it just cycles back to the "This device was reset..." screen again.
I know I'm not getting the details wrong since I made the account specifically for the phone and have the details written down. Any suggestions on how to proceed?
EDIT: Actually nevermind, I managed to follow along with a tutorial on how to bypass it using MotoService & ADB. Thanks again for replying.

HELP! OnePlus 6T Black Screen - Won't Boot

I successfully rooted the device and until recently I wanted to unroot the device, so I uninstalled Magisk.
However, after doing so my device rebooted into a black screen and the only response I got was a vibration when I tap the right side/edge of the screen or press the power button.
I tried pressing the Power button + Volume +/-, and was able to enter recovery and fast boot mode. However, I tried wiping cache, resetting, and formatting, my phone would still reboot into the same state.
When this problem occurred I had 30% battery and I also tried MSMDownloadTool for 6T, but my computer simply does not recognize the device. My device is only two weeks old.
Any help would be appreciated.

wahahah said:
I successfully rooted the device and until recently I wanted to unroot the device, so I uninstalled Magisk.
However, after doing so my device rebooted into a black screen and the only response I got was a vibration when I tap the right side/edge of the screen or press the power button.
I tried pressing the Power button + Volume +/-, and was able to enter recovery and fast boot mode. However, I tried wiping cache, resetting, and formatting, my phone would still reboot into the same state.
When this problem occurred I had 30% battery and I also tried MSMDownloadTool for 6T, but my computer simply does not recognize the device. My device is only two weeks old.
Any help would be appreciated.
Click to expand...
Click to collapse
Reflash the stock boot image.

Hi
TheKnux said:
Reflash the stock boot image.
Click to expand...
Click to collapse
Can you tell me how do you do that? Because I tried connecting my device I couldn't get my computer to recognize it. All I see in Device Manager was: LeMobile Android Device or something.
Thanks!

update
TheKnux said:
Reflash the stock boot image.
Click to expand...
Click to collapse
The problem kinda changed, as I tried to flash a stock fastboot rom onto the 6 following this tutorial: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Now everytime it boot up its stuck at the Boot loader is unlocked warning screen.

wahahah said:
The problem kinda changed, as I tried to flash a stock fastboot rom onto the 6 following this tutorial: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Now everytime it boot up its stuck at the Boot loader is unlocked warning screen.
Click to expand...
Click to collapse
PM me or hit me up on Telegram: TheKnux

wahahah said:
The problem kinda changed, as I tried to flash a stock fastboot rom onto the 6 following this tutorial: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Now everytime it boot up its stuck at the Boot loader is unlocked warning screen.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
This will flash to phone back to completely stock and lock the BL.

Phone stuck on Bootloader [soft brick]

Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.

GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....

slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:

GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.

tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?

H910 bricked after pulling battery during system lockup?

So this is a weird one for me. I've been running an H910 on an LOS 16 build from I think August and Gamma kernel 3.0 (never found the time to update stuff), and a couple nights ago I had the phone completely freeze on me while switching browser tabs, wouldn't even shutdown after holding the power button for ~30 seconds, so I pulled the battery to restart it. However, when I powered it on, after the initial LG logo I just got a screen of unchanging static IDENTICAL to what this poor soul had in the third photo of his linked album. My anxiety then ramped to 10 when I tried booting to recovery and after the "are you sure you want to delete your data" prompts I was greeted by the exact same screen. Booting to download mode would show the same screen after the few seconds of the "download mode" photo, and looking back I'm pretty sure it was just booting to download mode after encountering an error when I tried booting to system or recovery.
The bootloader was A-OK though, so the first thing I tried was flashing the latest TWRP, which seemed to work. I was able to boot into the system, but it was pretty buggy (the open apps button didn't work), so I tried booting to recovery, but it still gave me the static. I booted to system and it worked again, so I went back to fastboot and flashed the recovery again, which put me back where I started, static on everything but bootloader.
At this point I came to terms that things were getting wiped and began looking up what I could do in terms of KDZ flashing. I first settled on converting to US996, so downloaded US99610f_00_1205 and after dumping my system tried flashing it with the patched LGUP using the partition DL option. When I did, it cleared up the static issue in download mode showing the "Firmware Update" header and everything beneath it, but then download mode was still what recovery and system would boot to. I could boot to fastboot, but my bootloader was now locked. I tried that a couple times, but always got the same option, and the "Upgrade" option in LGUP would always return an invalid KDZ error due to H910 -> US996. My device still showed up as version H91010v as well. I then tried flashing over the H91510e_00_VTR_CA_OP_1205 KDZ as described in this thread for getting H910 root, but this gave me the same results.
So that's where I am right now, a phone with nothing but Download mode and where using Partition DL to flash stuff doesn't seem to actually flash it. The program I've been using is the LGUP files in this thread that's always linked. Any help on what next steps to take would be greatly appreciated, thank you.