Hi guys,
I got a G5S+, which got stuck the other day.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me.
I decided to run with that tutorial here:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
Which seemed to be the right one.
Said so, booted into bootloader, installed the driver on my Win10 PC and ran through the steps.
I gut stuck on 'fastboot flash system system.img_sparsechunk.3' (15mins waiting..... after the steps before required about 12 Sec each) and needed to disconnect and connect the phone again.
Started with the same command and it worked.
Anyway when I got to the command 'fastboot flash system system.img_sparsechunk.5' I realized in the Potter Retail, there is no such file (neither there is 6 or 7).
I skipped the commands and continued.
When it came to rebooting the phone disconnected and thats it.
Since then I am not able to turn my phone back on.
Sometimes there seems to be a small notofication led showing up when trying to turn on the phone.
And you can hear the USB connect sound when I connect it to my computer.
Did anyone of you guys experience the same issue or has an idea what to do?
I have no idea what I shall so.
Best regards,
Matt
Which stock ROM did you flash? I'm hoping that following that guide, you flashed a stock ROM for sanders (i.e. the codename for Moto G5S Plus) and not for potter (codename for G5 Plus), which appear to be not compatible with each other.
Your original issue appears to be your device is booting into the stock recovery (which the start of is the 'no recovery' screen).
Do you know what model number or retail software channel, or the software build you had on your device before it failed? If so, we may be able to flash the correct sanders stock ROM to your device and get it going again. Another user appears to have gotten their device working when they incorrectly flashed the potter stock ROM and not sanders. https://forum.xda-developers.com/moto-g5s-plus/help/bricked-moto-g5s-plus-t3747064 Ideally you will want to flash the correct stock ROM for your device.
Oha damn you are right.
I am an idiot and tried to flash Potter to a G5S Plus.
Oh boy. I should not flash a cellphone after a long day at work.
I had the latest safety update installed and the latest release.
I am not sure though which software that used to be.
Unbelievable.....
Anyway, so my screen does not show anything anymore.
I guess the display driver dows not work or something like that.
The cellphone is still working I think, as the USB sound still appears.
Does anyone have an idea what to do if the screen stays black.
I still cannot believe it.....
Thanks though for your help!
EDIT: fastboot still reckognizes the phone. I guess this is good.
But the command 'fastboot oem fb_mode_set' runs into an error.
Edit2:
I skipped the first command and everything ran through (with some error messages though).
I hope it works now.
Device is currently rebooting and showing the blue motorola screen.
Lucky me.....
Okay, at least your device is booting now (ish)... I saw your other post and was wondering if you were able to boot from the bootloader.
1)Boot to fastboot (probably easiest by powering off your device, then hold down power and volume down keys until your device boots).
2)Once in the fastboot menu (with details about your device, like bootloader version), check that 'Start' is selected, and press the Power button to select. If 'Start' is not showing, use the volume keys to scroll through the options until 'Start' appears. Sometimes, this booting via fastboot bypasses an auto-boot to recovery mode.
Failing that, if you're on the 'no command' screen, then hold down the power button and tap the volume up key. Release both and it should let you into the recovery menu. Then, you can try to reboot to system.
Hi there,
I ran through all the steps you said.
But I ended up having the same issue. I always get back to the broken droid.
Is there a way to flash a completely new ROM to the device in its current condition?
I don't mind having a customrom, but I want to get it working again.
Thanks!
Matt
I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!
Related
Hi Everyone,
I have a (Milestone) problem and would love input from anyone who can help.
This is an interesting situation, so feel free to skip the quote section if you'd like to avoid the, albeit quite summarized, background information.
I purchased this device from kijiji. Apparently it's an internal device, with GP hardware and a 90.70 bootloader.
My first mistake was misreading some instructions. On this device you can enter fastboot mode by pressing VolumeDown. I mistook this for bootloader (forgive me, they sound similar), and attempted to flash .sbfs from here. Of course this doesn't work.
What i did find was that i could flash .sbfs fine if i started to run RSD while the device was running (because it restarts itself properly into bootloader). That is, i got Vulnerable recovery to run okay. And then rooted/nandroid backups.
But later i got adventurous and tried to update the annoying outdated bootloader (because of course, i thought you couldn't flash sbfs to it directly). As urged by the community, it's backed up incase anyone needs it.
So i started RSD while the device was running, to flash 90.78. Almost instantaneously the device restarts, but instead of going into bootloader it tries to boot. And fails. Which brings me to:
Click to expand...
Click to collapse
The device gets stuck on the Motorola M splash screen. Every once in a while (~3 minutes?) it goes blank and comes back.
A summary of the state:
Recovery mode will not boot. I've tried X and Camera Button
Bootloader boots. It reads 90.78.
.SBFs can be flashed. It seems like everything is working okay.
Fastboot mode can boot. My PC can detect the device but seems unable to write/read from it
adb logcat forever sits on -waiting for device-
I've tried flashing a number of .sbfs. I've redone the bootloader a few times, tried a number of roms. But now i'm out of ideas.
I'm open to suggestions and really hoping someone can help me figure out a way to restore this. Thanks !
I'll try just one bump, i'm getting desperate.
Nevermind, this got figured out. Consider this closed please .
Hi, I did just got into a similar situation:
- Recovery mode will not boot. "I've tried X and Camera Button" (Same like you)
- Bootloader boots. It reads 90.78. (I tried several BL 90.73, 90.74 and 90.78)
- Several .SBFs can be flashed. It seems like everything is working okay.
Did you get any solution or just discard that phone?
Hey everyone - I've got an interesting one I think.
I had just gotten everything working with CM11 when I got ambitious and went to replace the logo.bin to remove the 'unlocked bootloader' warning that shows up every boot. I realized too late that the logo.bin I used was for a Moto G. Now you'd think that this would just affect the boot logo and I'd be able to try again with the right logo.bin... nope.
On boot all I see is colorful snow. I hear the startup sounds, and I can access the files on my computer when connected via USB. After the screen goes to sleep it shows a flashing white light. Same response with each different startup button combo.
Any ideas? I've tried using adb and fastboot manually, as well as Myth Tools. 'fastboot devices' shows up blank, and adb finds no devices either. I've installed RSDLite but can't find a file to use (lots of broken download links), and I'm not sure that would even solve my problem.
Thanks for any help!
The phone woke me up with it's alarm this morning. That was unexpected. It's also ringing when I call it - CM is running, just the screen is messed up.
How can I get into fastboot in this state? I've never had much success getting the key combos to work on this phone. Adb reboot commands were my most reliable way, but adb isn't detecting a device. If I installed CM11 and have not installed google apps yet, should adb be working?
dta5003 said:
The phone woke me up with it's alarm this morning. That was unexpected. It's also ringing when I call it - CM is running, just the screen is messed up.
How can I get into fastboot in this state? I've never had much success getting the key combos to work on this phone. Adb reboot commands were my most reliable way, but adb isn't detecting a device. If I installed CM11 and have not installed google apps yet, should adb be working?
Click to expand...
Click to collapse
Nope. Not until adb is enabled by going into the developer options or tweaking the build.prop before install.
Just hold down all three buttons when you are booting up and you'll access the boot menu, from there you can select recovery or fastboot or whatever (for me it's easier than using the other key combos as I too have a hard time with them).
skeevydude said:
Just hold down all three buttons when you are booting up and you'll access the boot menu
Click to expand...
Click to collapse
Maybe it's the way you described it, but I was actually able to get into the boot menu this time! I've fixed the logo, and the phone boots normally now.
For anyone else with similar issues, getting the boot menu requires doing a simulated battery pull (vol down + power) followed by booting with all 3 buttons pressed. I think my error was attempting to hold all 3 buttons when the phone was still on and expecting to get the boot menu.
Hooray, my wife has a phone again! And I won't have to worry about touching it ever again because I won't be allowed to. :victory:
Thanks!
Hi, I am having some problem with my Atrix HD. I was doing some rom update and after reboot all I can see is colored snow (not sure whats the technical name for this, as it will help to search better) and goes to nowhere from there. I tried rebooting few times, but nothing except the snow. Its summer now, so How can get rid of this snow and see my normal phone ?
manugoenka said:
Hi, I am having some problem with my Atrix HD. I was doing some rom update and after reboot all I can see is colored snow (not sure whats the technical name for this, as it will help to search better) and goes to nowhere from there. I tried rebooting few times, but nothing except the snow. Its summer now, so How can get rid of this snow and see my normal phone ?
Click to expand...
Click to collapse
What exactly were you doing? Taking the new AT&T OTA or was it something on the custom side?
I know that flashing the wrong sized bootlogo can do this. I actually flashed a bad one I made the other day that turns my screen red and the actual image is all jacked up. The Moto G logo I flashed left it snowing just like you're experiencing. I've also had random bad flashes do this too.
All you can do is fastboot/myth/rsd back to stock and start over. Hopefully you have backups.
Thank you, I managed to fix my phone, it was something related to battery. I simple pressed all three buttons and connected to charger to get to fastboot menu, which also rebooted few times as phone did not had enough battery to run fastboot. Repeated the process few time to get it working. Thanks
Hey guys!
So I've got an issue I'm struggling with on the Moto G (2014). First I'll tell you as much as I can about the phone: I bought it from the Motorola website, so I think it's running whatever the stock firmware is. Also, it's the 8 GB US model and isn't tied to any carrier. (I have it on T-Mobile, but got it directly from Motorola. I was trying to figure out what the firmware is but the closest I've been able to get is by running the Motorola Device Manager app while the phone is in fastboot mode. It says there are no available updates for: 21.11.17.titan_retuaws.retuaws.en.us The bootloader is locked and the phone is not rooted. It's pure stock, though it might have automatically gotten an OTA update to the latest official release, I can't be sure because I bought it for someone else.
Okay, so the problem. I'd bought the phone for my dad and set it up and it worked fine for about two months. Yesterday, he came by my place and asked if I could take a look at it because it was stuck on one screen and since there was no removable battery, he didn't know how to reset it. The screen it was stuck on is the boot screen where the Motorola logo is supposed to come up. It was up, but the bottom half of the logo was stretched to the side and pixelated so my first reaction was "crap, he hit it against something and there's damage to the screen." But there was no visible damage to the screen anywhere (neither from a hard hit or from pressure) and he's got the flip case for it and he said it hadn't been hit or anything.
I tried to power it down by holding down the power button, but as soon as it went off, it tried to start up again. A bootloop that always froze on that messed up Motorola boot screen. I set it on the charger for a bit and let it run through the loop a few times and at one point it got as far as the "world" screen where it shows a cartoon planet. This extended down past where the weird stretch happened on the motorola graphic and it was perfectly clear so I realized there was no damage to the screen, just some sort of boot error.
So then I tried booting into fastboot (hold both volume buttons down along with the power button for a few seconds, release) and I was able to get into fastboot. I tried scrolling down to recovery and then hitting the volume up key to select it but the second I hit the volume up key (the selection key in this mode) it reboots the phone. It doesn't go into the recovery screen, just turns off the phone. I tried this for the "Factory" (reset) option, for the "Normal Powerup" option, and the others. Instead of getting anything different, selecting any of them turns the phone off and nothing happens. The computer is recognizing that there's a device connected to it when I have the phone plugged in via usb in fastboot to my Windows 8 laptop. It also appears that I can enter commands in fastboot. (Though I'm not sure what to put in to fix this so I'm turning to you guys.)
So I can't figure out what's wrong. I've got some experience in flashing roms, both manually and with some of the tools, but haven't had to deal with what I'm assuming is a soft brick before.
Can anyone offer any help?
Thanks very much.
Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4
Roldorf said:
Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4
Click to expand...
Click to collapse
Unfortunately that didn't work. I was able to click the "restore to factory" part and it seemed to do that but I tried it again with the "wipe cache partition" and it just reset. I tried to restart normally and nothing happened. I will start boot and go to the Motorola logo but will always fail there, no matter what I try.
I'm still stuck with the soft-bricked phone. Any help going from Fastboot to somehow getting it to work?
(As I stated in the OP, the recovery options don't work. It seems only the Fastboot area is working.)
try to reflash the rom via fastboot, using the commands on 4.2 on this thread
if you have fastboot working they must work and re-flash the stock rom and everything back to stock...
to have the XML zip of yours rom search in here and download the file regards yours model and OS version that you wanna...
download, very slow download, unzip, to the some folder of mfastboot and give the commands a try... :good:
This is how to solve *ANY* softbrick on the Moto G 2014 (2nd Gen Moto G)
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:
eyhajee said:
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:
Click to expand...
Click to collapse
hello eyhajee.
My Moto G 2014 xt1068, running on Android 5.0.2 has some softbrick issue.
I have unlocked its bootloader, rooted it, unrooted it and while I was trying to lock its bootoader, I forgot to enable USB debugging and now it's stuck on fastboot mode.
So I wanna ask that can flashing a custom ROM turn my phone on??
I think so. If you are able to run some basic commands you should be able to flash it to emergency mode.
First of all, I've looked around for answers, and I seem to find the same solution everywhere, which is OK. It just doesn't work for me.
Here's the drill. My Moto X was sitting in a drawer for a year or two. I took it out a while ago to update it and see how 5.1 worked on it. I put it back in the drawer as an emergency phone. Last weekend I took it out, to find that it's stuck in Fastboot. the up volume key scrolls, and down volume key does nothing (originally down scrolls, up chooses) and the power button reboots.
Long story short, I was able to get my computer to recognize my phone (tried for hours until I realized it was the cable, use the right cable and voila!) I unlocked the bootloader via Motorola, and after hours of trying was able to flash everything I thought was necessary (boot, recovery, motoboot, system, and so on). However, in every thread and video, the "fastboot reboot" command makes the phone reboot into the actual OS, whereas mine just keeps rebooting into fastboot, regardless of what I flash.
I don't notice anything off, so hence why I recur to everyone in here to give me some advice on what I could be doing wrong. I've downloaded stock roms so far. I get a partition error with .zip files so always have to flash the images individually.
Please let me know if I'm missing any details, and/or what other information I should provide.
Thank you!!
SantiagoEB24 said:
First of all, I've looked around for answers, and I seem to find the same solution everywhere, which is OK. It just doesn't work for me.
Here's the drill. My Moto X was sitting in a drawer for a year or two. I took it out a while ago to update it and see how 5.1 worked on it. I put it back in the drawer as an emergency phone. Last weekend I took it out, to find that it's stuck in Fastboot. the up volume key scrolls, and down volume key does nothing (originally down scrolls, up chooses) and the power button reboots.
Long story short, I was able to get my computer to recognize my phone (tried for hours until I realized it was the cable, use the right cable and voila!) I unlocked the bootloader via Motorola, and after hours of trying was able to flash everything I thought was necessary (boot, recovery, motoboot, system, and so on). However, in every thread and video, the "fastboot reboot" command makes the phone reboot into the actual OS, whereas mine just keeps rebooting into fastboot, regardless of what I flash.
I don't notice anything off, so hence why I recur to everyone in here to give me some advice on what I could be doing wrong. I've downloaded stock roms so far. I get a partition error with .zip files so always have to flash the images individually.
Please let me know if I'm missing any details, and/or what other information I should provide.
Thank you!!
Click to expand...
Click to collapse
Flash system.img and boot.img then flash twrp.img and boot into twrp and flash your stock ROM for your device
Hi, I'm having a complete disaster today having tried to go from the latest stable Chinese ROM to a global ROM.
I understand that I need to unlock the bootloader, so after a fair while managed to do this. It didn't work on my PC but it did on my wife's. I really should have given up then. Sigh.
I think this unlocking did work as the developer settings say it's unlocked and when the phone boots up (when it did boot up) there was a little unlocked graphic at the top of the screen.
At this stage I thought all would be good. I have downloaded the MiFlash tool (2021.2.26.0) and the ROM below.
Mi 8dipperstableV12.0.2.0.QEAMIXM10.0GlobalDownload2020-11-23
I'm certain that I have the Mi 8 (and not the lite or other version) so this seems like it should flash?
After having to download a fix (something to do with drivers) I can see my phone in the Flash tool and can select the folder with the rom (before the fix any refresh would just cause my phone to say "any key to shutdown"). So I can click "flash" and keep everything crossed.
But, it doesn't work. Initially it seemed to progress but after about 10 minutes, with the status bat at ~95%, it gives a timeout error. I think - though I'm losing track - but I could still boot my phone up at this stage.
I did this a few times and the same thing happened. Then, I got a worse sounding error "Missmatching image and device". I kept trying and got this or some other instant error that I didn't note down.
After this my phone wouldn't boot up, it just goes into recovery mode. I do note that it I press vol up and power I get the option to connect to some windows app (this doesn't work) but curiously if I try flash from this state I get the same issue as above (it seems to work slowly but then times out).
So I'm at a loss and have a broken phone! Any suggestions would be very helpful to say the least!
I'll add that at the moment the phone is stuck with the fastboot logo on, so I can't even turn the damn thing off. I can try but it just boots up again into this screen :-(
Geeze, on about the 20th try the flash tool just hung so I yanked the phone out and now it seems to have worked. I'm keeping everything crossed right now!
Display fastboot logo, maybe it is not bricked.
"It didn't work on my PC but it did on my wife's. ". I had the same problem when I unlock the bootloader. mi 8 not work well with usb3.0, suggest you use your wife's computer with usb2.0. OR patch you PC registry of windows 10 with attached bat file.
Are you a Chinese ?