Database Users

HELP! My Phone is Slowly Self-Destructing!!

Hey guys, I am kind of a noob but have successfully been hacking with my Touch for a while now...or so I thought. I flashed to the 3.37.78 radio a while back and have been keeping up with NSFAN's ROM's for over a year now with no problems....until a few months ago. My phone locked up and I had to soft-reset but to no avail. It got stuck on the startup screen and would not do anything so I did a hard reset and all was good. Then it happened again weeks later. Now it has been happening a lot more recently. I will be texting or on the internet with it and then all of a sudden it will lock up, I do a soft reset and it will hang up either on the startup screen or seem to boot up but then contacts will be missing and there will be no signal. Sometimes the today screen will show but I cannot do anything on it.....all of this requires a hard reset to fix. This happened after I flashed NSFAN's latest ROM so I flashed back to some of his older ROM's that I had no problem with in the past and still the same problem. It has been happening every week or 2 now to the point that I can't even bother setting up the phone the way I want because I know it will happen again. Can any of you guys tell me what the problem is? I really need to get this resolved because I am losing information everytime. Please help!!!

Im a GSM Phone user... and as a general rule, if things start to go wrong.... Flash the OEM rom. That would be the stock ROM. And then flash back to your "custom" rom... Ive had to do that with my phone(s) as well.... It basicly puts things back to 'ground zero'. BUT. Use the phone with the stock rom for a day and see if you still have the same problems... it may be a problem in the phone. In which case you may need to replace and/or send the phone back for replacement to your carrier.
Hope this helps....

Thanks for the reply.....What I ended up doing is reflashing my radio to the 3.42.50 version and then reflashing my ROM to NSFFAN's again. So far so good. I am really hard on my phones and the fact that I drop my phone on a regular basis can't help either....I just need it to last me a few more weeks until I get a new one. Thanks again...

[Q] Phone "stuck" on Motorola Logo

I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...

Have you tried the 2.2.1 leak? This gives you a new kernel and bootloader.

Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
If the phone is not rooted when you take it into the Verizon store then you will be fine. I would ensure that any traces of root have been removed from the SD card (apps that require root, etc). As long as the phone is stock when they see it then it will be fine. I have had to do this several times with roms and root access.

Can't you just SBF it? I'm fairly new to the X but I've had to SBF rescue my D1 and D2 multiple times.
OOOPS didn't read the SBF part...
If it is still hosed after an SBF install I would guess that you have a hardware issue and need to replace the phone.

Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
It's a known issue with 2.3.15. gmanapps, the guy that created the hdmi app in the market said it was the video driver not loading up in time because of some code changes Motorola made; but supposedly it's fixed in 2.2.1. I suggest you don't upgrade to 2.2.1 until there is a full sbf.
I get stuck on the "M" logo 7 times out of 10 after every reboot; I just hold the power button down until the pop-up window comes up (of course I can't see it) and guess where the shutdown press is on the screen to power off the phone, and then power on again after a minute or two. This trick usually works.
Check it out here:
https://supportforums.motorola.com/message/256095#256095

[Q] Boot loop issue - at&t Android 2.3.6

Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR

Well, unfortunately with the screen cracked, you can't return to Motorola. I had a goof with my Atrix when I first got it because I accidentally did a SBF flash to the wrong version and it bricked the phone and fried the motherboard and Motorola replaced it because I said the Gingerbread update messed it up. Ha.
Anyways, since returning to Moto is not an option for you, I would just go ahead and try to install a custom ROM, maybe try Neutrino ROM 2.2 or 2.5?
Do you have ROMRacer Recovery or CWM Recovery installed? Will it let you get into it? If so, put a custom ROM on your SD card, do a wipe data and cache and install it.
I'm no expert, but I have noticed no one else replied and just trying to help.
Hope all works out for you!

Boot loop issue - at&t Android 2.3.6
Thanks andreww88 for your reply. I read in one of the forums that once the phone is updated with 2.3.6 don't try to go back to older versions especially lower than 2.3.4. That would make the phone to be hard bricked. That is why I didn't try any other ROM other than NottachTrix 4G because it is built on 2.3.6. I could be wrong. That is why I need some guidance to try any other custom ROM.

i had the same issue. What i did was get the Atrix Fastool and whipe the phone. Then i extracted the sbf for 141 and then flashed 59 60 and 61 smg files from fastboot. After that everything worked properly. To then unlock my bootloader i used the flashing script and i was set. This is recoverable not easy but you can recover.

Thanks Moneyman1978 for your reply. Can you be more detail what you did to resolve this issue. Can you send me the links or point me to Fastool and 141 .SBF file also SMG files. Thanks again.

gpr789gpr said:
Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Click to expand...
Click to collapse
Well, I had a similar issue. I did the 4.5.141 (OS 2.3.6) OTA update and then it would just bootloop. I'm on stock, rooted, locked BL. I then ran the OTA update again via recovery and that didn't help. I then did a full factory reset, then update via recovery and still didn't fix anything (good thing I had TiBu backup). After calling AT&T they finally admitted that Moto recalled the 4.5.141 build update since there was WIDESPREAD boot-loop issues with many Atrix users. Great.
They're sending me a new phone. Luckily, mine is in good condition.

Any one please have any suggestions for me. Do you think it is a hardware issue or can it be fixed by fixing the software??? Any help is appreciated.

If any of you has any ideas about how to fix this issue I would appreciate if you can share it here.

[Q] i9505 Constant hangs and reboots

Recently I bought a Galaxy S4 i9505, But from the start I started running into problems Random restarts, Hangs, errors even after reinstalling several Stock/Custom roms, Formats, Re-Partitions no luck.
I have came to a conclusion that this might be a hardware issue. Now i would like to figure out which component can be causing the issue.
Will changing the motherboard rescue the device ?

Same problem, but only then device is charging... any advice here?
Sent from my GT-I9100 using xda premium

S4 No sound, reboots when trying to access ringtone
It is now really getting to my nerves, I have updated to Lollipop and now back to Kitkat and the problem is same. There has been nothing done physically to the phone so still i am pretty sure that this is related to the software but the porblem is that the ringtones are not working, when i am trying to call people i cannot hear them and they cannot hear me, camera is super slow and when i am trying to come out of all this the phone reboots and at times gets stuck at the samsung logo.
Please do not suggest to do factory reset, cache cleat etc because i have done all this and still the issue is not resolved. Please please if any expert could bail me out here !!! seriously need your help !!!

Reboot loop when restarting phone

Basically as the title says whenever I want to restart my phone I get stuck in this inexplicable boot loop that doesn't stop and I can only actually get into the phone in some weird magical way that I haven't figured out how is done yet.
I've tried flashing stock(I was on btu 7.0), wiping cache partition/factory resetting but the issue still remains. Anyone encountered anything similar?

If flashing rom and factory reset doesn't fix it then it might be hardware issue and need mainboard replacement.
Sent from my SM-G935F using Tapatalk

This is where most of the people make problem even worst, please don't mess with the software anymore and take it to service,it must be hardware related.