[Q] CommServer has started - Moto G Q&A, Help & Troubleshooting

A few days ago I booted my phone normally and I got an strange app running right as the phone turned on. It's called CommServer, and theres a message saying "CommServer has started".
I investigated a lot about this and it seems that this is a testing app to check the phone functions, and to use it you have to fastboot the phone and select the BPTools option. However, I am booting my phone normally and I get this app running on the background. It's really annoying because the phone starts up on Airplane Mode when this happens, and the USB connection to the computer doesnt work, along with a lot of other functions that are turned off.
When I fastboot my phone and select either "Start up normally" or "BPTools" the CommServer thing disappears completely, and my phone works perfectly. I tried flashing my device from 4.4.4 to 4.4.4 from a different country and the problem persisted. I tried upgrading to 5.1 and the problem still persists.
So I assume something like BPTools became the default launch for the phone, since it appears only when I start the phone without fastboot. Is there a way to permanently change the default boot mode for the phone?
Thanks in advance.

1. OPEN UNI ANDROID TOOL
2. CLICK ON MOTOROLA TAB THEN NEW FRP METHOD
3. THIS WILL REMOVE FRP AND WILL ALSO REMOVE "The CommServer has Started." The process is CQATest. NOW YOUR PHONE WILL BOOT NORMALLY.

Related

[Q] Trouble flashing Stock & Custom ROM's

So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
morr22066 said:
So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
Click to expand...
Click to collapse
I had tried everything I could think of and it appeared that there was a partition problem. The phone continued to shut down and would only stay on while connected to the PC. If it were a PC I would reformat and re-partition the drive but I did not want to risk a permanent brick by messing with it.
So, as a last ditch effort to try and get my phone functioning again I let it download and install system updates. The phone is now working again, it has not shut down at all and there have been no warning messages about cool down mode.
BUT, I am now on "4.4.4, SU-5-24, build 23.3.24 dated 10-27-14. Since my boot loader is unlocked I flashed TWRP but it would not not accept Super SU zip so I am no longer rooted.
I finished reading up on it in the forums and realize I am pretty much screwed as far as root goes. But at this point I don't even care anymore. I just need to get the phone functioning correctly.
*So, I am still having the problem with flashing stock and getting the "red" letter message after system image boots saying "sp space not enough". So long as it is hooked up to the computer it stays on and if it is downloading or installing an update it stays on and I never get a warning about cool down mode and it does not shut off, but once I disconnect from the computer it starts all over again. The phone boots up but at random intervals it still either gets a pop up message saying that it has gone into "cool down mode" or it shuts off. It is not doing it as often as before, but it is still doing it. Does anyone have any suggestions on whats causing it or how to fix it? It sounds like a software / firmware issue but I am not sure how to fix it.
*Update. The phone is still not functioning correctly. At times it will appear to work fine for hours with frequent to heavy use at times then suddenly it will start acting up, the phone will shut down randomly and when it reboots some of my settings have changed. The temperature is usually pretty low but once in a while after a shut down I will check the temp when I'm able to reboot it and it will be high. When it shuts down like that I usually have trouble getting it to boot up again unless I plug in the factory cable, either in the PC or just the wall charge then it seems to boot up fine and I can even reboot it but once it shuts itself down it doesn't want to start again unless I use the factory cable.
It really does sound like a software / firmware / partition problem but after multiple attempts to flash the firmware with RSD I continue to get the same error message at the end of the system flash and the phone continues to have problems. Does anyone have any suggestions?
Got me an xt1080 which I'm trying to restore to stock, and in both House of Motor and RSDlite 6.2.4 at some point during the system partition flash 'so space is not enough' as well. The phone is in perpetual bootloop, unless I use a 'Factory/power' cord and starting up in fastboot (eventually). Tried both 1FF and CFC fxz files, no luck.

Z5 stuck in bootloop (100% stock firmware)

Over the weekend, my Z5's battery died. When I booted it back up, it started running dexopt which I found unusual. Once it completed and switched to "starting apps" the phone rebooted and began running dexopt again. The next time, I ran logcat and saw that com.sonymobile.wifi/.internal.SomcWifiService was ANRing at the end of starting apps which caused the phone to reboot. Any ideas how I can fix this?
This is one of the first phones I've used that is 100% stock firmware and not rooted or unlocked. Any ideas what may have caused this or how I can get out of the boot loop?
I tried running adb shell svc wifi disable as a last resort but it didn't fix it.
EDIT: I've created a gist with the logcat during dexopt and leading up to the crash here: gist.github.com/gpeal/d580d12c8f8f01569128
Try to repair your phone with pc companion,or remove sd card if you have one and try without it.
Update: I was somehow able to get it to boot in to safe mode while trying to do the 3 finger salute to get it into recovery mode. After it booted into safe mode, I had it forget all wifi networks (hoping that it may have caused the wifi anr). I rebooted after that and it booted back up normally. I still have no idea what caused the ANR though.
goorioles747 said:
Update: I was somehow able to get it to boot in to safe mode while trying to do the 3 finger salute to get it into recovery mode. After it booted into safe mode, I had it forget all wifi networks (hoping that it may have caused the wifi anr). I rebooted after that and it booted back up normally. I still have no idea what caused the ANR though.
Click to expand...
Click to collapse
How did you get the phone to boot into safe mode?
Mine is stuck showing "Optimising application 1 of 76" and I have to let the battery run out before I can charge it and try again. Sometimes it gets through all 76 and then says "Starting Android" and then just re-boots and it all starts again.
Plugging it into the PC doesn't seem to give any response either as the thing won't turn on so I can't run the PC repair option in PCC, any advice muchly appreciated
TaZ4444 said:
How did you get the phone to boot into safe mode?
Mine is stuck showing "Optimising application 1 of 76" and I have to let the battery run out before I can charge it and try again. Sometimes it gets through all 76 and then says "Starting Android" and then just re-boots and it all starts again.
Plugging it into the PC doesn't seem to give any response either as the thing won't turn on so I can't run the PC repair option in PCC, any advice muchly appreciated
Click to expand...
Click to collapse
Turn the phone on and directly press volume down and keep it pressed till the phone boot will take you to safe mode.
TaZ4444 said:
How did you get the phone to boot into safe mode?
Mine is stuck showing "Optimising application 1 of 76" and I have to let the battery run out before I can charge it and try again. Sometimes it gets through all 76 and then says "Starting Android" and then just re-boots and it all starts again.
Plugging it into the PC doesn't seem to give any response either as the thing won't turn on so I can't run the PC repair option in PCC, any advice muchly appreciated
Click to expand...
Click to collapse
If you have adb setup, run logcat while the phone is optimizing. Let it continue running until the phone reboots. When it does, the adb connection will close and you'll be able to find the crash/ANR pretty close to the end of the log.
Thanks guys. I actually didn't need to do either of those things, I found a little reset switch next to the Sim card tray, pressed that and then it took twice as long as previous attempts to optimize the apps but then it booted up fine
Z5 SOV32 stucks in bootloop after phone restart
Hi, my phone Z5 SOV32 that 100% stockfirmware stucks in bootloop everytime i restart it ( it was normal before), then i have to repair it by using Xperia Companion many times. I created a logcat.txt file but i don't know how to analyze it, please help me.
This is the logcat link: mediafire.com/download/c5ap0zngixmo5ts/logcat.txt
Thanks.

Boot loop on optimizing apps

I have the US 32gb unlocked version. Tried to do the downgrade to install CM using the method mentioned several times that changes the version from a command put in twrp.
First I unlocked bootloader, then installed twrp, then did the command line thing to lower the fw version, then put the v1.12 firmware on zip then rebooted to install.
Well, the install failed so I decided to stop there and try to put everything back to stock by using the latest ruu exe from HTC. The exe started sending a file to phone, then locked up and threw an error. I restarted the exe and it finally passed. I got everything set up and went to bed while it was updating apps.
This morning, shut off phone to put in SD, and when turning on it was optimizing apps then when done, would reboot and optimize again. The phone was stuck in this loop until I let the battery die. I couldn't do anything with it.
Battery finally died and tried to run the ruu exe again. This time it would not pass at all, no matter how many tries. I wanted to try to run the zip from SD but the latest firmware I can only find as exe.
Finally decided to just do a factory reset from recovery mode. This let the phone boot normally and I could do set up again. I tried doing a soft reboot, and it booted fine. Then I disabled apps I don't use, and did a full power down, now the phone is back to doing the 'optimizing apps' bootloop.
Right now I'm waiting for it to run its battery down again so I can at least get to download mode/recovery. Maybe I will try a full power off and app disabling separately, to see which is causing the loop.
Anyone have an idea what's going on? A link to the latest ruu in zip form? I really need a sure fire way to get this thing full clean stock (remember the exe is failing for me) to eliminate if thats the cause. Is it because I edited the version number?
Edit: just realized I put this in the wrong section
Update: Once battery died, I did factory reset again from recovery. Went through setup, and I then immediately shut the phone completely off and turned back on. It booted up fine. I then went to disable the same apps as before, EXCEPT for the "Google App". Phone still powers up fine, so I left it there and phone is working fine. I didn't want to see if disabling the Google App was causing the phone to boot loop. I had that app disabled the entire time I've had the phone, but don't think I've ever completely shut the phone down, so maybe that's why I never had the problem.
Still don't know why the ruu exe didn't work. Hopefully it was the computer, and I can still take updates.
I have the same problem, can't disable apps without phone going into bootloop on restart. Can you tell me what apps did you disable? Facebook, Instagram, Google docs, HTC apps etc,etc...
hmedved said:
I have the same problem, can't disable apps without phone going into bootloop on restart. Can you tell me what apps did you disable? Facebook, Instagram, Google docs, HTC apps etc,etc...
Click to expand...
Click to collapse
I think what caused my problem was disabling the app called "Google App". No problem disabling all the Facebook and Instagram apps.
What about Google docs, slides and news apps? Can those be disabled?
Same problem with my A9 bought a week ago. Like Rouyal, I recall disabling the Google App and then came the OTA update and the bootloop. Tried alll permutations of buttons and even when I could get to RECOVERY MODE, all the options looped as well, returning to the same screen: no bootloader, no recovery. The only alternative screen was the "Enter your code to decrypt your drive" after leaving RECOVERY MODE. It looped as well. Copied the stock RUU to an external SD card; did nothing (with HTC Sync).
SOLUTION: Enter wrong codes for the "decrypt your drive" screen 30 times; that is the limit before the drive gets a factory reset. After the 30th it was factory reset. On restarting, the systems asks for the SAME email that was used previously.

How to bypass Recovery Mode?

Hello everyone,
So I have a rare issue. I have a OnePlus 6. Today, it started to act really weird. It became so slow that even swiping on home screen with no apps opened takes like a minute to register. I forced power off the device. When powering on again, it seemed like it take around 10 minutes or so to boot. Again, extremely slow. I tried everything from restarting and clearing app cache while in the system itself but no luck.
So, next thing I booted to recovery mode, typed my pin, and cleared system cache and settings. It started to progress until just a tiny bit left before the end of the progress bar, and it got stuck again. Kept like this for a long time. I had to force power off the device again. Now, when I try to power on the device, it launches into Recovery Mode. I tried my pin but it wouldn't decrypt and looks like the device is no longer recognizing it. I tried a couple of "default passwords" but it wouldn't work either. It only gives the option to "Forget Password?" Which should wipe everything off the phone. The only other mode it launches into is Fastboot Mode. I'm using Stock everything and Device State is Locked. I'm not sure where to go from here.
Now my question is, is there any way I can open my device again without losing data? Maybe some way I can pull files using adb in that state then factory reset? Or maybe someway I can bypass Recovery Mode and boot again? I have important data that I can no longer access if the only way to fix this is by wiping everything!
Can anyone help? Much appreciated in advance.
When a phone permanently boots into Recovery mode then either Android OS is corrupted - for whatever reason - or phone's bootloader is misconfigured.
If phone is accessible by either ADB or Fastboot you can try to exit Recovery mode by forcing phone to boot into Android OS ( Normal mode AKA System ) by applying the related ADB and/or Fastboot command.

Question Bricked can't Seem to access anything

Hi everyone.
Last night my phone ran out of power and when I charged it back up it wouldn't boot at all, so this morning I decided to try and fix it but I think I have just screwed it up even more to the point that its completely bricked.
I could still access TWRP and tried to reinstall the firmware and flash TWRP through the checkbox execpt about 1 minute in the screen went off due to the time out, but the screen wouldn't come back on at all so I left it for an hour just in case if it was still running in the background, after this time I hard restarted the phone and entered TWRP again and but it didn't install the firmware properly and my computer wasn't reading the phone properly so as a test I tried to swap bootloader from A to B stupidly and now I can't seem to access anything, only thing I can do is the menu where it says start, power off, recovery mode and restart bootloader. Pressing any of these settings seems to just put me back in to this menu again.
When plugging in the phone in to the PC it make's no noise at all as well.
Have I completely hard bricked my phone? Or is there a way to fix it?
Thanks Ben
All fixed I flashed the RAW firmware

Categories

Resources