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:

[Completed] Xperia Z2 Brick

Hello, I bought a Z2 back in November, but it completely stopped working after 6 weeks. No customs ROMs, no root access, nothing. It started lagging, so I was going to restart and it just wouldn't turn on (I turned it off at 32% battery). I plugged it in, and no charging light o anything. I was away from my house for the weekend, so when I got back home I tried seeing if I could fix the issue. Luckily, I still had my old LG Optimus G Pro (that i'm still using). I bought the phone new (sealed in factory packaging) from eBay (never buy from seller "never-msrp") and their return policy is 28 days. They woudn't take it back, and after calling whoever I could to get my money back ($439.99) the bank finally gave it back (they might not let me keep it, I had to send a letter explaining what happened. Still waiting to hear back). So, 2 months after it stopped working, I'm stuck with a broken Z2. To explain what it does: at first, nothing. No lights, vibrations, nothing. Now, if I plug it in, the red light comes on, but if i unplug, it still does nothing. When plugged in, the phone will have a red light, but if I push the power button, it starts to blink very slowly. Like on for a few seconds, off for a few seconds. Different combinations of power and volume keys yield the same result. Pushing the red reset button when plugged in makes the phone vibrate 3 times, and nothing else. not a thing. Pushing it while unplugged does nothing. The computer does not recognize the phone, and the PC Companion won't install correctly (I get an error saying the program did not install properly). So at this point, I don't care what I do with it, I just want to make it run something. Android, Windows, I don't care what. Is there any way I can get this phone to boot up into any OS or is my poor phone done for good?
PS: I called Sony and asked if I could get a replacement, but when I provided my IMEI, they said my phone was from Hong Kong, was never meant to be sold (whatever that means), and has no warranty. So that's no use.

Hi there,
Please read carefully this thread and register an account on XDA if you have any other questions to post:
[Q] bricked xperia z2
FYI: [INFO] ALL You Need To Know About Owning A Xperia Z2
Good luck

My quest for a new power button with a twist!

So my story begins with me purchasing a used white Nexus 5 for $155 from swappa over a week ago for my wife. *
Phone arrives in perfect condition.
I first unlocked and flash twrp via adb. I proceed with installing Chroma and elementalx. Spend few hours on making the new Nexus 5 the same as my wife's current Galaxy Nexus.
Phone is running great. Zero issues for about 3 days while the phone was just at home running. She throws the phone into her purse and goes to work. Within hour she calls that her phone won't stop rebooting…. *Oh no…. The dreaded power button issue… right?
So I'm assuming the seller did the old “whack against a solid object” temp fix and sold it. I have no proof of that so I'm assuming.
So what do to? Well fixing the power button is still cheaper than buying another Nexus 5 phone. Everyone one quoted me $60. It is what it is… at this point I could have gotten a refurbished phone but what can you do…
So you would think this is the end of my story, right? Wrong.
I go to a cell phone repair place close to my work. They have this tiny power button in stock and replaced it many times before. I come back later that day to pick it up and they have bad news… of course they do.
After the switch replacement, the phone did the same reboot. Goes to Google logo and reboot. If I fiddle with the power button I can get to the OS but reboot right away. The guy proceeds with that it is me rooting it that caused it and I need a new motherboard, price $100.
I started questioning if he really did replace the switch. If it was OS related, the phone would not have worked for couple days and then break randomly. It would not boot to the OS sometimes or at least it would let me boot into TWRP, right?
Long story short, I left with spending the $100 on getting this used $155 phone fixed. Super annoyed at this point.
So after this long story, is there any chance this was really OS related and not a faulty power switch or did I just got lied to and the power switch was never replaced?

For sure, you should've attempted to restore the phone through Google's factory images first. My power button went super wacky twice since I've had it(day 1 model). I just pulled it out, and now the problem is gone all on it's on.
When it kept rebooting, did you try booting into the bootloader at all?
Sent from my Nexus 5 using Tapatalk

Curiousn00b said:
For sure, you should've attempted to restore the phone through Google's factory images first. My power button went super wacky twice since I've had it(day 1 model). I just pulled it out, and now the problem is gone all on it's on.
When it kept rebooting, did you try booting into the bootloader at all?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I sure tried to get into recovery but wouldn't work. Just kept rebooting. I had a nandroid backup done a day before but the phone would not stay powered on for long enough to do anything. It was the equivalent of having no battery left and phone just shut down and attempted to reboot constantly. I took out the motherboard and played around with the button before I went out to repair it but it was the same results. If I "massaged" the button then maybe the phone would get past the Chroma logo and get into the OS, but as soon as I attempted to touch the power button again it would reboot.
I tried reviewing the old motherboard and unless this shop's soldering skills are top notch, I can't tell that the switch was replaced. The soldering point were identical to the volume buttons. When I questioned the store owner, he stated they are that good with their infrared soldering He took out a package of 3 Nexus 5 switches and one was missing... meaning he installed it.
I highly doubt it was OS related. If you brick a phone when flashing, then it would just be constantly in a boot loop, right? I know I can easily go into recovery and flash whatever .img I need to, but this was just nonstop reboot and different times

Zenfone 6 stays black after EDL Mode

Hi!
TL,DR:
Phone froze while using, and it kept freezing. Now phone wont boot at all, only EDL Mode works. However, after EDL phone wont still boot.
Longer story:
I've got quite a problem here. I was playing Pokemon GO with my friend yesterday. Suddenly my phone went quiet. I saw PoGo froze for 5 seconds and then phone rebooted itself. It went back to LineageOS (17.1) which I've installed successfully via TWRP. Then the phone rebooted itself again many times again and again, and each time it crashed earlier than before. When LineageOS did fail for booting for several times, the phone went straight to bootloader. I tried to open recovery but it crashed too. Then It came back to bootloader and I said Power Off.
I waited for half an hour but the phone was failing boot. It wen't even worse: the phone wont go to bootloader any longer, it just stays black.
I've done an EDL Mode recovery couple of times before when I was messing around my first custom ROM installation with Lineage. Now when I set the phone to EDL Mode via cable I made (it was an easy task) I can hear Windows detecting my phone (which it didn't detect before) and uses the QDLoader 9008 EDL Driver.
Then I use the "update_image_EDL.bat" to regenerate the partitions.
Now here's the tricky part: After the .bat file the phone should reboot to bootloader, however this doesn't happen, and the phone just exits ELD mode (I can hear it from Windows it doesn't detect the phone anymore) and then just stays black. It doesn't react to any buttons or cables, and Im also sure it has battery. I even opened the case and removed the battery from its port and putting it back to see if the phone reacts then my actions, but no.
It feels like the only thing I can do here is the ELD mode. I tried it several times later, and that's all.
Also trying to continue with the instructions with QDLoader 9008 fix (the flashall_AFT.cmd) won't lead anywhere, because Windows doesn't detect the phone after that.
Thank you in advance for any tips and tricks.
Edit: Just to add; I've tried removing SDcard and SIM cards also. No effect.
Edit2: Here's the copy of the 'update_install_EDL.bat' results: https: //paste.ofcode.org/bPLQA6T484rKEEb2URa8yv

After more failed tries and thinking, my friend was looking at my log from update_install_EDL.bat he was thinking about the warning it gave. Well, I went looking for the sector limit which was put by rawprogram4.xml and I added the missing sector to the count. Now the error is missing from log but it went nowhere in the progress however. I've done the .bat now many times, but nothing seems to be working. I've removed the battery and put it back before edl and after edl and tried booting with just the powerbutton and with the Vol+ and power btn, but nothing comes up.
If you got a log from the update_install_EDL.bat, I'd appreciate if you could post it somewhere for me to see did you get the same warning as I did.
I also want to point out that ANY comment is welcome... I keep you posted whenever theres some progress.

Okay. I decided to take my Zenfone 6 to Asus authorized repair shop. They said I've got short circuit in the motherboard. God knows how that happened. However I can't get it under the warranty because earlier I repaired my broken screen glass in a unauthorized repair shop. which has voided the warranty. Asus told me that the repair would cost me 527,2 EUR (624,30 USD). I'll not be paying that much for a repair, so it looks like Im out of the business..
I also want to note that I purchased the phone 4.6.2020 and it was in the screen repair for 30 days. So with my quick calculations I paid totally 12 eur for each day I had a chance to use it.
Edit: I want to say here that the repair shop takes 60€ (71 USD) for their excellent service. Okay, I admit that they we're quick on the result, for about 30 hours they responded, but ofc I'd like to have more info but they told the phone must be taken to the ASUS factory then.

Hey bud stumbled upon the post somehow!
What was your error code with the EDL script? (Link that you had shared expired :/) was if shahara error? I'm not so experienced but combining the infos that I've read across the forum maybe try charging the phone for 8+ hrs and try again. Also try diff cable, the one that came with the phone. There are two contact points at the back with which you can force EDL mode as said here. Also the firmware folder should be kept in the main drive (C:// or D) and named without spaces just alpha numerics. Lots of people seems to be getting the same Sahara error damn. Let us know any of these got it fixed! Cheers

Honestly it seems like whoever ASUS sourced to make the main motherboards did a rubbish job with all the failures. My wifes bog standard firmware just died 16 days out of warranty.
ASUS should either offer extended warranty and free motherboard replacements or conduct a voluntary recall to fix them.
I didn't spend a grand to use a phone for 12 months.

abx12 said:
Hey bud stumbled upon the post somehow!
What was your error code with the EDL script? (Link that you had shared expired :/) was if shahara error? I'm not so experienced but combining the infos that I've read across the forum maybe try charging the phone for 8+ hrs and try again. Also try diff cable, the one that came with the phone. There are two contact points at the back with which you can force EDL mode as said here. Also the firmware folder should be kept in the main drive (C:// or D) and named without spaces just alpha numerics. Lots of people seems to be getting the same Sahara error damn. Let us know any of these got it fixed! Cheers
Click to expand...
Click to collapse
Yeah Im sorry for the log. The warning on there was basicly telling that the bios.img is larger by one sector than the sector size given to the update_install_edl.bat. It was fixed by adding the one sector to the rawprogram4.xml file.
I was aware of the sahara fail, it was fixed by unplugging the cable and back in (restarting the edl mode ofc). And I also tried another cable.
What comes to the directory (folder) names I was aware of that too, the script don't do a very good job with folders having spaces or special letters.

homerlovesbeer said:
Honestly it seems like whoever ASUS sourced to make the main motherboards did a rubbish job with all the failures. My wifes bog standard firmware just died 16 days out of warranty.
ASUS should either offer extended warranty and free motherboard replacements or conduct a voluntary recall to fix them.
I didn't spend a grand to use a phone for 12 months.
Click to expand...
Click to collapse
My working theory is that this high failure rate is affecting all of series so they have no way to determine which units should be fixed/replaced. It's very sketchy but they've put themselves into this situation with poor QC in the first place.

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.