Database Info

[Q] Bad Motherboard?

Alright Guys so I'm having some issues with my Infuse 4G.. I purchased this phone like a year ago on ebay for $40 with a cracked screen. since it was an emergency i had to buy it. I flashed CM10 and everything worked excellent. one time, I dont remember the reason i had to go back to stock (GINGERBREAD) and once I flashed it (MAYBE I DID SOMETHING WRONG?), the phone kept on freezing, the screen would go black and the lights at the bottom was the only things i could see. Sometimes it would restart by itself, sometimes apps would stop responding at a soft reboot I did wipe/factory reset, wipe cache & delvik cache on recovery before doing anything. So basically the errors would usually say
SORRY!
ANDROID.PROCESS.ACORE STOPPED RESPONDING UNEXPECTEDLY. (this is not the actual message, but something very similar)
SORRY
GOOGLE PLAY.PROCESS.STOPPED RESPONDING UNEXPECTEDLY.
And so on.. so I had to do a soft reboot again to get the phone working again. If i go to FROYO, the phone would NOT let me set up a password, and when i pressed the power button only the option (POWER OFF) when some other options like AIRPLANE MODE, SOUND PROFILE should be visible. So on Friday, I flashed the new CM11 and still the same issue occurs with the GINGERBREAD one.. it freezes, lights light up at the bottom and restarts I did a GTG'S Ultimate Unbrick and no luck, So its been really annoying because this is awesome phone, I wanted to ask for any suggestions? I would deff appreciate any of your help as is driving me nuts..

Boriiboss said:
I would deff appreciate any of your help as is driving me nuts..
Click to expand...
Click to collapse
The problem is the GAPPS you are using!!!
Use this back to stock tool with root:
http://forum.xda-developers.com/showthread.php?t=1705260
Flash CWM synthesis in Gingerbread with SGS Kernel Flasher in Play Store required for flashing:
http://forum.xda-developers.com/showthread.php?p=25724638
Flash cm9 with CM9 GAPPS! :
http://forum.xda-developers.com/showthread.php?t=1601844
Do only basic setups. Ignore other settings. Make sure battery level higher than 50%. Go to recovery and
Use this unofficial cm11 4.4.2 rom and not its GAPPS
http://forum.xda-developers.com/showthread.php?t=2517092
During first flash, it will say error 7. Reboot to recovery and flash ROM again, then the following gapps!
USE THIS GAPPS Mini Modular or Micro Modular Packages:
http://forum.xda-developers.com/showthread.php?t=2397942
This worked well for me

[Q] Can't wake up phone after restore

Hello. I have a rooted OPO, running 05Q. Last night I finally succumbed to the temptation to flash a ROM. I used the app "CM downloader" to obtain the latest nightly of CM12. Using TWRP, I created a backup, then installed the downloaded ROM. It didn't work; the phone got stuck in what is, I think, called a bootloop. That is, it just kept showing "Updating Android" then going back to a CM animation, over and over.
After letting this go on for quite a while, I powered the phone down and rebooted into Recovery. From there I restored the backup I had created. That seemed to go without a hitch; everything looked as it did before I set out on this adventure. But when I let the screen go dark after 30 seconds of not doing anything, I found that double-tap wouldn't wake it, and neither would pressing the power button. It seemed to be still working, since notifications were coming in, but I couldn't get the screen to light up. So I did a reboot, which worked, but only until the screen went dark again, at which point I had the same problem.
So...I used Titanium to backup all apps and settings, and did a "reset to factory", then restored apps and settings. This seemed to work, but once again I found that once the screen went dark, the only way to wake it up was to reboot. And again, even though the screen was dark, the phone was working. I listened to a podcast while driving to work, even though I couldn't wake the screen up.
Any ideas what the cause of this might be? I did check the Settings to make sure the double tap to sleep and wake were turned on. Everything was as I'd left it. And in any case, even the Power button wouldn't do it.

You need to flash cm11 firmware, that is the radio and stuff to get your cm11 05Q to work properly again
Edit
You should flash this
http://boeffla.df-kunde.de/bacon/modems/Full-XNPH05Q-modem-flashable.zip

waterdaan said:
You need to flash cm11 firmware, that is the radio and stuff to get your cm11 05Q to work properly again
Edit
You should flash this
http://boeffla.df-kunde.de/bacon/modems/Full-XNPH05Q-modem-flashable.zip
Click to expand...
Click to collapse
Thank you, that worked!

Unable to recover my OPO

Hi all,
well, to be honnest I already posted my story in the help thread but no answer came so I try with a new thread
We'll see if I'm luckier this way !
a few weeks ago I broke my screen and decided to change it myself.
Everything went fine (even restarted successfully my phone before applying the tape to fix the screen) until I finally tried to restart my phone after the repair is done.
Since then I'm not able to turn on my phone
Holding the power button starts fastboot mode, UP + power doesn't do anything and DOWN + power enters recovery. Weird !
Another weird thing: it only works if I'm not plugged. When I'm plugged nothing ever happens.
I suspected I could have damaged buttons or cables. I have looked carefully but nothing appears to be broken.
Here is what I already did without any result:
- I had access to the original recovery so wiped the cache
- I tried to recover the phone but that did not work so
- I installed twrk using adb (like here)
- and then installed the rom as explained here (I used the last release here, so it should be cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-bacon.zip). It seemed to work but finally no, same situtation
- I tried this but so far not able to get the qualcomm port listed once the phone is on. It may be related to the fact that I have to unplug to boot it but I always got a Android bootloader interface listed.
Any idea someone ?
Thank you very much for your help !

Did you try to "fastboot reboot" while in fastboot mode?

Try flashing a CM14 rom. Mine came with CM12 so I tried flashing back to CM11 and I did flash it successfully through Fastboot but alas it won't boot. The boot logo loads but then I'm introduced to a black screen.. So I flashed back to a (at that time the latest stable) CM12.1 but same result. And I got worried. Then I decided to flash a CM13 rom which was a beta build (at that time newly released Android 6) and it booted into it alright! So I suggest flashing a CM14 and let me know how it does.

The problem seems be much deeper than just a broken screen. It may sometime affect the chipset of the cellphone.
For that we can't do anything.
For now you can try the following things :
1 . Flash the latest Cyanogen Firmware from the same place you have downloaded the snapshot cm13.
2. Flash recovery (TWRP) using adb.
3. Wipe
-System
-Data
-Cache and Dalvik Cache
4. Flash the latest Cyanogen Rom .
5. Boot into recovery.
6. Flash some gapps as per the Android version.( Open Gapps I recommend)
7. Boot back to recovery .
8. Boot into System.
This is the max you can do for now.
You can also check device forums for recovering from a bricked device post.
Go through the post and check if any symptoms matches yours. You'll find the answer right away.
And the last option you can do is going to service center, they will charge you mostly (even if in warranty as you have yourself tampered hardware of the phone.)
Hope it will help. Thanks

MOTO G custom ROM weird bug/problem

Hello, so after I install a custom ROM, after 2-3 weeks of using it, my phone gets stuck, and then reboots. After the reboot, the phone acts weird: no notifications are shown, home/recents buttons not working, some apps not working and not locking and some options just reset.
Thank you in advance.

yakomi said:
Hello, so after I install a custom ROM, after 2-3 weeks of using it, my phone gets stuck, and then reboots. After the reboot, the phone acts weird: no notifications are shown, home/recents buttons not working, some apps not working and not locking and some options just reset.
Thank you in advance.
Click to expand...
Click to collapse
?? Yep i know this thing few symptoms were shown on my osprey so it happened to me bz i just to test many custom rom and many time there residue remain uncleaned even after many twrp formats (it weird but i think this happens) so try clearing your intenal storageand (no need to clean memory just remove it) even remove you sim crad and memory cards
flash a recovery from your current recovery if there is not update just reflash the current recovery and then just make it a reboot to recovery ( msg will pop up no os found but there will be no issue if you're rebooting directly to the recovery)
So after reboot put your memory card in phone where you will store your rom and gapps ( if memory not detected just reboot to recovery one more time) puff install things let your sim cards in enjoy your rom
If this thing failes go install stock firmware its an ultimate solution

i finally flashed the stock os, hopefully no issues now!

yakomi said:
Hello, so after I install a custom ROM, after 2-3 weeks of using it, my phone gets stuck, and then reboots. After the reboot, the phone acts weird: no notifications are shown, home/recents buttons not working, some apps not working and not locking and some options just reset.
Thank you in advance.
Click to expand...
Click to collapse
The same issue happened to me yesterday
So, now I am trying to clean flash the custom rom first

I've been running a Lineage OS PIE version on my Moto G3 2015(Osprey) XT 1541 for several months now and not a single problem.I think it's a Fantastic Custom rom that you might like to try,
http://www.droidthunder.com/android-9-0-pie-on-moto-g3/
Note:
Before installing any Custom rom do a,"Nandroid" backup and then a Factory Reset.
Then once the rom has installed and before setting the phone up do another,"Factory Reset".
I've found this the best way to make sure the install is really good and clean

Resurection Remix reboots on lockscreen then only boots into TWRP

I've been running Resurrection Remix without problem for months.
After booting by phone and trying to unlock it my phone just rebooted on the lock screen without any input from me (I might have been holding the power button or somthing acidently) after the reboot it put's me into TWRP. Trying to reboot it again results in a very long boot animation followed by another reboot into TWRP.
This is the second time this happend and I still have no idea what has caused this (I fixed it last time I tried by re flashing the rom). I haven't installed/changed/updated anything before it happend so I don't even know where I could begin looking for a cause.
Is there a way to fix this without re flashing/restoring a backup and can I do anything to prevent this/find out what's causing this? prevent this/find out what's causing this?

KeinNiemand said:
I've been running Resurrection Remix without problem for months.
After booting by phone and trying to unlock it my phone just rebooted on the lock screen without any input from me (I might have been holding the power button or somthing acidently) after the reboot it put's me into TWRP. Trying to reboot it again results in a very long boot animation followed by another reboot into TWRP.
This is the second time this happend and I still have no idea what has caused this (I fixed it last time I tried by re flashing the rom). I haven't installed/changed/updated anything before it happend so I don't even know where I could begin looking for a cause.
Is there a way to fix this without re flashing/restoring a backup and can I do anything to prevent this/find out what's causing this? prevent this/find out what's causing this?
Click to expand...
Click to collapse
In twrp check if everythings mounted
Try wiping Dalvik/ART Cache & Cache
Maybe reflash /system
Did you using any magisk modules?