Database Info

Moto G - all the processes are stopped on phone

Dear XDA mates,
I am facing this different kind of issue currently. None of the process on my phone are working. Here is what has happened and what is happening:
What happened:
1. I dropped my phone in water. It soaked in water literally.
2. I dried it off but saw that phone was starting and shutting down automatically. I kept it the way it is so that it can dry off further.
3. Couple of hours after I started the device and it was all working but I wanted to make sure it is working fine so switched it off and kept it to dry off till next morning.
4. Next morning phone was not switching on.
5. I put in on charge and after a while try to switch it on. The phone started but was giving me zero battery alert and switching off. I thought it is a usual battery going dead issue and left the phone the way it is.
6. After one day I kept it on charge again but nothing happened so I finally decided to take the device to service center.
7. Stupid service center technician told me, phone is dead completely and motherboard has to be changed. I decided to not do anything with the phone and brought it back home.
8. I kept it on charge and guess what, phone was full charged next morning and it started again.
What is happening:
1. The phone started but now as soon as I unlock the phone, I start seeing errors. (Unfortunately, Google Play Newsstand has stopped, Unfortunately, com.google.process.gapps has stopped, Unfortunately, Weather has stopped etc etc, the error never ends).
2. Now it thought of doing a factory reset, went to Fastboot mode, selected the Factory option, phone goes to Moto logo and I see the same old lockscreen. Phone is not resetting.
3. I thought of flashing the phone with stock firmware, went on fastboot mode again, tried to go on Recovery option. Phone returns to fastboot mode with error (in yellow font) "Boot up failed".
Now I am stuck, I see some serious problem has happened for sure.
I need some super expert help and need to understand what might have happened to my phone.

Sad for you, mine opinion is it might related to hardware issues. Hope some pros may come up and help you here.

Flash stock firmware from fastboot

ashu388866 said:
Dear XDA mates,
I am facing this different kind of issue currently. None of the process on my phone are working. Here is what has happened and what is happening:
What happened:
1. I dropped my phone in water. It soaked in water literally.
2. I dried it off but saw that phone was starting and shutting down automatically. I kept it the way it is so that it can dry off further.
3. Couple of hours after I started the device and it was all working but I wanted to make sure it is working fine so switched it off and kept it to dry off till next morning.
4. Next morning phone was not switching on.
5. I put in on charge and after a while try to switch it on. The phone started but was giving me zero battery alert and switching off. I thought it is a usual battery going dead issue and left the phone the way it is.
6. After one day I kept it on charge again but nothing happened so I finally decided to take the device to service center.
7. Stupid service center technician told me, phone is dead completely and motherboard has to be changed. I decided to not do anything with the phone and brought it back home.
8. I kept it on charge and guess what, phone was full charged next morning and it started again.
What is happening:
1. The phone started but now as soon as I unlock the phone, I start seeing errors. (Unfortunately, Google Play Newsstand has stopped, Unfortunately, com.google.process.gapps has stopped, Unfortunately, Weather has stopped etc etc, the error never ends).
2. Now it thought of doing a factory reset, went to Fastboot mode, selected the Factory option, phone goes to Moto logo and I see the same old lockscreen. Phone is not resetting.
3. I thought of flashing the phone with stock firmware, went on fastboot mode again, tried to go on Recovery option. Phone returns to fastboot mode with error (in yellow font) "Boot up failed".
Now I am stuck, I see some serious problem has happened for sure.
I need some super expert help and need to understand what might have happened to my phone.
Click to expand...
Click to collapse
Follow this guide and everything will be good

Tried flashing but nothing happens
I have tried flashing it too. When it fastboot mode, I see that all the processes are running as intended and once the flash is complete and my phone starts with Moto G, guess what - I see the same old wallpaper and lock screen. It means phone is not flashed .
amolgosavi said:
Flash stock firmware from fastboot
Click to expand...
Click to collapse

I suppose that either means you flashed incorrectly, the phone is still wet inside or the phone is damaged.
Try drying it on a warm, dry place for another day or two.
Good luck!

Will trying flashing after 2 weeks of phone phones processes has stopped
I will flash it today again.
Which is the best process to flash the Moto G phone. I have followed couple of methods and they haven't worked for me.
It could also because of the battery issue. I read it on another forum that Factory cable might help.
Can you or anyone else point me to Factoty cable. Searched all over ebay and all I could see is Factory cable for Moto Razr.
Let me know guys.
Thanks.
robm123 said:
I suppose that either means you flashed incorrectly, the phone is still wet inside or the phone is damaged.
Try drying it on a warm, dry place for another day or two.
Good luck!
Click to expand...
Click to collapse

Tried flashing and nothing happens again.
This is crazy!
I do not rely service centers anymore and I can flash myself.
Techies - please help.
ashu388866 said:
I will flash it today again.
Which is the best process to flash the Moto G phone. I have followed couple of methods and they haven't worked for me.
It could also because of the battery issue. I read it on another forum that Factory cable might help.
Can you or anyone else point me to Factoty cable. Searched all over ebay and all I could see is Factory cable for Moto Razr.
Let me know guys.
Thanks.
Click to expand...
Click to collapse

I'm similar situation. Only my daughter's Moto G (android 4.4.4) was not physically damaged.
After sreen unlocking the phone shows errors "Unfortanately [everything] has stopped working".
I flashed stock recovery many times but it does't help.
And one more thing: if the phone is connected to the PC it is possible to run fastboot commands, but the phone filesystem is not accesible.
Is this a hardware problem?
P.s. Sorry for my english

ashu388866 said:
Dear XDA mates,
I am facing this different kind of issue currently. None of the process on my phone are working. Here is what has happened and what is happening:
What happened:
1. I dropped my phone in water. It soaked in water literally.
2. I dried it off but saw that phone was starting and shutting down automatically. I kept it the way it is so that it can dry off further.
3. Couple of hours after I started the device and it was all working but I wanted to make sure it is working fine so switched it off and kept it to dry off till next morning.
4. Next morning phone was not switching on.
5. I put in on charge and after a while try to switch it on. The phone started but was giving me zero battery alert and switching off. I thought it is a usual battery going dead issue and left the phone the way it is.
6. After one day I kept it on charge again but nothing happened so I finally decided to take the device to service center.
7. Stupid service center technician told me, phone is dead completely and motherboard has to be changed. I decided to not do anything with the phone and brought it back home.
8. I kept it on charge and guess what, phone was full charged next morning and it started again.
What is happening:
1. The phone started but now as soon as I unlock the phone, I start seeing errors. (Unfortunately, Google Play Newsstand has stopped, Unfortunately, com.google.process.gapps has stopped, Unfortunately, Weather has stopped etc etc, the error never ends).
2. Now it thought of doing a factory reset, went to Fastboot mode, selected the Factory option, phone goes to Moto logo and I see the same old lockscreen. Phone is not resetting.
3. I thought of flashing the phone with stock firmware, went on fastboot mode again, tried to go on Recovery option. Phone returns to fastboot mode with error (in yellow font) "Boot up failed".
Now I am stuck, I see some serious problem has happened for sure.
I need some super expert help and need to understand what might have happened to my phone.
Click to expand...
Click to collapse
Flash the stock rom via fastboot dat could fix the problem:good:

Boot Loop Issue, Odd Behavior, & Recovery Attempts

Talk about frustrating. During the exact same week last year my older phone ended up with the dreaded boot loop, and now my new Pixel 2 has done the same (Despite no attempts to unlock, root, or otherwise change the software, and with no physical abuse).
I sideloaded an OTA update via ADB in a recovery attempt, but the device is still stuck on the white "G" screen with the progress bar below it constantly moving as if it's trying to make progress albeit without such.
How many others have experienced this with the Pixel 2, especially since early April? My phone first acted a bit odd earlier this month when it refused to turn on, and it then suddenly came back on as someone called me. When I looked at the battery charge profile, the lines were tightly squiggled up and down, which is something I've never come across before. However, my phone acted fine after that, until now.
My phone's memory was recently low, and I admit that, but could that by itself have caused a boot loop?
Additionally, does anybody else have other ideas for what I can attempt recovery-wise before I'm forced to finally try a factory reset?
Thanks, for any and all replies and help.

Which variant of the pixel 2 do you have? The verizon or google?

I have the Google variant.

I had not only that, but it locked into the bootloader - barcodes, [power off or restart the bootloader were the only things it would do.
Make absolutely certain that you're not on a USB 3.0 port with a USB 3.0 cable. (I ended up using a Type A to microUSB cable with a micruUSB-to-Type C adapter, because even the USB 2.0 ports in that computer cause problems with the P2) and run Duece's Script. It brought me from Google willing to replace the phone (they actually shipped the replacement) to a working phone before the replacement arrived. I'm not an expert on the Pixel (or on Android), but I think it's the reboot after each file load that finally does it.
(Now if only Google would make the phone work on 3.0 ports with 3.0 cables. We're not all going to buy new computers (or even new motherboards) because they forgot one little thing.)

XZP goes dead everyday

My XZP goes dead everyday once. No reaction and black screen, even if the power cable is connected. I had to press both volume up and down plus power to wake it up. I wiped everything and flashed the newest official firmware without root. It still died last night. I could go into fastboot but it doesn't recognise the device so I can't flash twrp. Adb is fine. Is it a hardware issue? Do I need a new phone now? The phone is almost 3 years.... please help.

Usually when flashtool (I'm guessing that's what you meant) doesn't recognize a device it's because of incorrect drivers.
The powering off thing is weird because it's not just powering off, because if it were you'd just hit the power button to turn back on. Is the phone reset when you power back up or is everything as it was? If you're on stock firmware that should eliminate it being software. My guess it's time for a new phone. Extremely doubtful Sony will make this a Treble phone which means no android 10 and they're already working on 11, plus the whole 5G thing. My advice, new phone, not Sony.

Thank you for your reply...I don't think it's the driver because I flashed TWRP before with the same laptop. And nothing has been changed. It just didn't recognise the phone in fastboot, when I typed 'fastboot devices' it just says 'waiting for device'. After the phone was dead, it didn't lose anything...I guess you are absolutely correct - it's time for a new phone, not Sony. Maybe a Pixel would be a good choice, my original Pixel is still working fine without any problems, only the battery is not lasting as long as the XZP...

xueyaotianxia said:
Thank you for your reply...I don't think it's the driver because I flashed TWRP before with the same laptop. And nothing has been changed. It just didn't recognise the phone in fastboot, when I typed 'fastboot devices' it just says 'waiting for device'. After the phone was dead, it didn't lose anything...I guess you are absolutely correct - it's time for a new phone, not Sony. Maybe a Pixel would be a good choice, my original Pixel is still working fine without any problems, only the battery is not lasting as long as the XZP...
Click to expand...
Click to collapse
Just for the heck of it go into device manager with phone plugged in, dev mode enabled, blah blah blah and see what it says. I've had to reinstall drivers in the past. Also try disabling usb debugging then re enable and see if the phone asks you to allow debugging from this device (your comp.). None of this is going to fix the powering off but just to see if you can get your computer to recognize the phone again.

Tried to reinstall the driver again...still cannot find device in fastboot mode...maybe I'll just monitor the phone for a few days to see if it behaves normally. It did freeze again yesterday when I was playing a video...

I deleted the old driver and installed again...it is ok now. I'll flash Carbon rom now and see if the phone will go dead in the next few days...

xueyaotianxia said:
I deleted the old driver and installed again...it is ok now. I'll flash Carbon rom now and see if the phone will go dead in the next few days...
Click to expand...
Click to collapse
I tried Carbon on my XZP and had issues with the phone not seeing a sim card. I use eXsistenZ on mine. I know it's not a rom but has nice customization options and works smoothly. I'm getting to where I really don't want to mess with all the glitches of custom roms just to be able to remove crapware and see some arbitrary improvement that means little to me, and then lose the stability of stock. You can always hide the crapware, and yes it's still there, hiding, but I can live with that.

I also had same sim issue with Carbon...back to stock now. Rooted and delete the bloat. It died once last night unfortunately...I think I'll get a new phone after this Covid 19 thing, don't really want to go out now under national lockdown...time to upgrade.

xueyaotianxia said:
I also had same sim issue with Carbon...back to stock now. Rooted and delete the bloat. It died once last night unfortunately...I think I'll get a new phone after this Covid 19 thing, don't really want to go out now under national lockdown...time to upgrade.
Click to expand...
Click to collapse
I hear ya. We need more people to take this seriously.

Just an update. The phone went dead again on stock. So I flashed carbon yesterday, until now there are no issues....I shall stay on carbon now. It feels way better than stock rom.

Hmmm. That's so weird. You would think that if it were a firmware issue, that glitch would be in all XZPs running it. How did you solve Carbon rom not seeing your sim card?

bobsright said:
Hmmm. That's so weird. You would think that if it were a firmware issue, that glitch would be in all XZPs running it. How did you solve Carbon rom not seeing your sim card?
Click to expand...
Click to collapse
Until now the phone is ok. So I'd say it is a firware issue. I found out I had to wait like 2 minutes after each reboot before Carbon recognises my sim card. But, it is still better than the phone dying everyday...it runs much smoother than stock. More features too..I am happy now haha...

Excellent!!

Poco X3 NFC - Can't access bootloader, fastboot or system (bootloop)

Hi. My close friend has this issue. I'm posting this because she can't figure it out by herself. A month ago, her phone downloaded an update and she installed it. Since then, the phone has restarted by itself without any reason, just random restarts and the frequency of restarts was more frequent with each day. Fast forward to this day and the phone is constantly turning up and shows the POCO logo and restarts by itself. This loop is not ending until the battery is completely dead. When trying to access fastboot or recovery mode, she can get there but only for few seconds (until the device restarts again) which is not enough time to make any changes / factory reset. She did not accessed developer tools in system, so the bootloader is still locked. Holding down power button does nothing. ONE SINGLE UPDATE screwed up whole phone. Can't do ****. There's no SD card or SIM card in the slot. Is there any "hack" to stop the phone from restarting itself? Note when the battery is completely empty and she plugs the charger, the whole nightmare starts again. I'm lost. Did you guys have any ideas what to do? Or is the repair centre only solution? (She cracked glass of the display, i'm not sure if that voids warranty. [it's not glass COVER, it's the glass which is part of the display])

Is this device unlocked? If not, then RMA.
If it is, my best guess is to get the device into recovery (or fastboot?) and immediately connect to PC.
If it holds, leave it there as it will charge, although at much slower rate.
When charged, use TWRP to try to reboot to system.
If it doesn't work, then factory reset.

Sadly, i can not get to recovery because in about 2 seconds the device will reboot. There's literally no time to make any changes - factory reset. Also the device is not unlocked. I hope RMA accept the phone even though it has cracked screen . Thanks for response anyway

Then RMA it is. If you're in EU they'll have to take it, even with the cracked screen.
But does the reboot happen even when connected to PC? Two seconds is enough to plug it in if you're fast...

Yeah, we tried every possible idea we can think of. Pressing the toggle button from different angles with different intensity to make sure it isn't stuck inside, covering up the proximity sensor (yeah makes no sense but even that we tried, lol). Tried with connected to PC as with classical charging brick. No change. Back in those days where smartphones doesn't have unibody construction and you were able to take down the back cover and remove battery it was way simple. Nowadays it's not possible to stop the phone from booting itself until battery is completely empty. My friend says the problem started about month ago, when the phone annouced that there is an update available so she downloaded it and installed it. Before that, there was no problem with the phone whatsoever. Maybe it's caused by some kind of virus but IDK which apps she was using. She didn't have rooted phone not unlocked bootloader in developer tools. Also i googled that it may be caused by "Airtel Thanks" app which she didn't have installed aswell. I will keep this thread updated as what happend to the phone cause i'm also interested what went wrong and to help future users who will struggle with this problem a solution. Thank you.

CaptainFedora, did you solve the problem? I have the same issue...

Yeah, actually. Sorry for not posting the answer although it was definitely her fault. It was the power button being pressed down (which made continuous bootloop). But the button was somehow pressed deep into the phone's body. So complete dissasembly was needed.
Btw. my friend lives in other country so we discussed this problem over internet. If i could have the phone physically with me i would definitely know what was the problem.

Hi.
Yesterday I had the same problem, the device kept restarting every 10 seconds, it didn't even come to any screen besides the first one with the POCO logo in yellow.
Things I tried that did NOT work:
restart
hard restart
fastboot (it did enter the fastboot mode, but only showing the picture of the 2 robots and after 10 seconds restarting again to the POCO logo image)
plug it to power
plug it to computer
After 3 hours of continuous restarting and trying anything I could find in the internet and I could imagine of (except extracting the battery because it seemed complicated and difficult to revert), I tried randomly something that miraculously worked...don't ask me why.
pressing the power button shortly and quickly around 30 times (it might have worked after 10 or 20, but I just kept doing it a little longer
Afterwards it just started as if nothing had happened...doesn't make any sense, but I just wanted to tell you in case you are in a similar situation and desperate to not lose all the images and videos as I was yesterday.

Bricked my OnePlus 8 beyond anything ive done before

So, i've been flashing custom ROMS on my android phones for many many years. Never really screwed up... Except now. Let me explain;
I was going to flash LineageOS on my OnePlus 8 phone. Nothing I haven't done before. I follow the guide as the maintainer described (for your reference, https://wiki.lineageos.org/devices/instantnoodlep/install).
Towards the end of the process when I got to Installing LineageOS from recovery I'm asked to format data. Here something went horribly wrong. As the process of formatting finished. All that's left to do is reboot. And so I reboot. This was the last time I ever got any sign of life from my phone. Because after shutting down, it never started back up. No sign of life at all. No fastboot, no adb, not even a splash screen. I've tried to boot it with any combination of keys. But no matter which one (reset, boot to recovery, even boot to EDL). nothing. Not even a buzz or a battery indicator when I plug it into the charger either. Bricked beyond anything I've ever seen.
In the 3 days since it happened I've:
- Charged my phone for 20+ hours
- attempted rescue using fastboot/ adb
- followed the steps from about every comment in this thread: https://forum.xda-developers.com/t/cannot-unbrick-cannot-enter-edl-mode.4148589/ (on USB3 and USB2, with the oneplus official cable and 3rd party cables)
- followed the steps this friendly youtuber explained:
- pressed any button and any combination of buttons on my phone for at least multiple minutes
- screamed at the phone really loud
Obviously none of these steps did the trick. My computer (I tried 3 computers actually, and both in Windows and Linux) just does not recognize the phone anymore. Nothing in device manager. Not even when i'm attempting to EDL.
Quite honestly I'm just stumped. It's not even recognized by device manager. If I didn't know any better I'd suspect the hardware itself failed at the exact same time as the software. I hope any of you can help me out.

One option you can try is getting an EDL cable.

Xryphon said:
One option you can try is getting an EDL cable.
Click to expand...
Click to collapse
Hi Xryphon,
That's interesting actually. I didn't know there were specialized cables for this. I was just using regular USB C. I'll look into getting one.