Database Info

Random notification tone

If this has been asked and answered somewhere else I do apologize, I couldn't find anything about it.
I bought this thunderbolt a few days ago, everything worked fine and flawless minus the few lock ups on the keyboard when trying to text(if someone knows the answer to that too it'd be appreciated). Anyways, I tried rooting with an easy root method on here. Got through step one and then failed from then on. So I gave up and let it reboot up. It wiped all my data so I went through, re downloaded all the apps I wanted and such. Now, when my phone is sitting locked with the screen off it'll make a random notification sound like I have an SMS message when I don't. I've also received a text, it played the tone fine, I checked the text and it made the sound again.
If anyone knows how to fix this it'd be appreciated, other than just putting it on silent, it's not a big deal just kind of annoying when I think I keep getting texts when I don't

Did you do a factory reset after the root failed? If not, try it. It will delete all your stuff on the phone but not the memory card.
Menu-settings-sd & phone storage-factory data reset
This should clear up both your problems...

I'm not totally sure how this works with HTC, but if I had an issue on my Droid X that couldn't be solved by a factory reset then it needed an SBF. SBF is basically the same as RUU for HTC. So you may have to flash the MR1 RUU to go back to full system stock. Read around on the development forums before you attempt anything.

DaRkL3AD3R said:
I'm not totally sure how this works with HTC, but if I had an issue on my Droid X that couldn't be solved by a factory reset then it needed an SBF. SBF is basically the same as RUU for HTC. So you may have to flash the MR1 RUU to go back to full system stock. Read around on the development forums before you attempt anything.
Click to expand...
Click to collapse
I'm going to give that a look. The factory reset seemed to work, it didn't do it all day until about 5 minutes ago.

Boot Loop To Factory Reset to Nothing now Please Help!

Hi HTC inspire users,
I have a HTC inspire 4g on AT&T that was purchased around last year of March that has never been rooted (too worried about rooting), and a few weeks ago(just found this forum), my phone, to my belief, updated by it self over night. The next morning I found my phone not working at all, and was not able to start up to the home screen. However, the screen was black and lit and kept going through a boot loop. I freaked out, and asked for help on another forum (not phone related forum), and was told to turn off, and factory reset. I did this after removing the SD card so my personal data wasnt wiped. After I did the Factory reset, my phone continued to do the boot loop which has gotten me lost.
Ive been told to do a recovery from the menu by holding down the volume button while turning on the device. Even doing so my phone will not work.
Is there Any way possible to make the phone work again?
Thanks,
Matt

Theoutbackdream said:
Hi HTC inspire users,
I have a HTC inspire 4g on AT&T that was purchased around last year of March that has never been rooted (too worried about rooting), and a few weeks ago(just found this forum), my phone, to my belief, updated by it self over night. The next morning I found my phone not working at all, and was not able to start up to the home screen. However, the screen was black and lit and kept going through a boot loop. I freaked out, and asked for help on another forum (not phone related forum), and was told to turn off, and factory reset. I did this after removing the SD card so my personal data wasnt wiped. After I did the Factory reset, my phone continued to do the boot loop which has gotten me lost.
Ive been told to do a recovery from the menu by holding down the volume button while turning on the device. Even doing so my phone will not work.
Is there Any way possible to make the phone work again?
Thanks,
Matt
Click to expand...
Click to collapse
ok, pulling the sdcard to avoid deleting personal data is useless. When u do a factory reset all information is wiped except the sdcard..anyway, you have to flash this in fastboot usb.
To boot in fastboot you have to do this: pull the battery, then press volume down + power until you get a white screen with 3 androids at the bottom. Then press power to choose fastboot. Plug the phone to the PC and you should see fastboot usb in red in the cell. Run this exe file (is the official AT&T ruu):
http://dl4.htc.com/RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed.exe
If you are not having a hardware issue, then the phone it should reboot normally when done.

Thanks Glevitan!
Ill give this a shot, if something pops-up ill be sure to ask.

Got it working Thanks Alot!!!
However, when i did do the process, i had issue where I couldnt get into the Fastboot menu.. However, I left the phone charging all day and it seemed to cure it. And then the first time I tried to flash the software, it didnt work, second time it had no issues. Could this mean something?
Edit:
After using my inspire 4g for awhile one thing that does not go away is the immense lag from the App Drawer, with no new programs from the market, but the Factory apps.

Theoutbackdream said:
Got it working Thanks Alot!!!
However, when i did do the process, i had issue where I couldnt get into the Fastboot menu.. However, I left the phone charging all day and it seemed to cure it. And then the first time I tried to flash the software, it didnt work, second time it had no issues. Could this mean something?
Edit:
After using my inspire 4g for awhile one thing that does not go away is the immense lag from the App Drawer, with no new programs from the market, but the Factory apps.
Click to expand...
Click to collapse
Att Firmware Is a buggy as all the others. It Is weird that You end up in boot loop being stock.....maybe there's something in the hardware that Is messed. Just try to use it and assess the bebaviour of the device for a while, then if nothing Is failing You can try root it and run a custom ROM.....
Glad to have it back....:laugh:

Strange Issues with my Infuse

I've never had any major problems with my Infuse since I got it.
The battery is getting weaker but I bought a 2600Mah USB Backup Battery and that gives me another 7-8 hours for about 13-14 hours of use.
To make a long story short, I unlocked for use in Mexico City on TelCel and had some issues, so I returned the phone back to stock, unrooted.
Since that point however, while it would occasionally freeze before, its become a daily thing now and really bothersome because I can't even stop audio from playing via bluetooth. The touch screen becomes unresponsive and only a soft reboot or a hard reboot (removing the battery) returns the phone to a useful state.
It seems I have to do is every couple of hours now though, so I am posting here to get some suggestion on how to fix it.
Its been two years already since I got it so I am eligible for a new phone, but this one continues to work well besides this issue.
Thanks

djfourmoney said:
I've never had any major problems with my Infuse since I got it.
The battery is getting weaker but I bought a 2600Mah USB Backup Battery and that gives me another 7-8 hours for about 13-14 hours of use.
To make a long story short, I unlocked for use in Mexico City on TelCel and had some issues, so I returned the phone back to stock, unrooted.
Since that point however, while it would occasionally freeze before, its become a daily thing now and really bothersome because I can't even stop audio from playing via bluetooth. The touch screen becomes unresponsive and only a soft reboot or a hard reboot (removing the battery) returns the phone to a useful state.
It seems I have to do is every couple of hours now though, so I am posting here to get some suggestion on how to fix it.
Its been two years already since I got it so I am eligible for a new phone, but this one continues to work well besides this issue.
Thanks
Click to expand...
Click to collapse
1. your microSD may be going bad
2. if you haven't done so, back up all your stuff and try a factory reset...this may erase all existing info and bring the phone back to day#1

qkster said:
1. your microSD may be going bad
2. if you haven't done so, back up all your stuff and try a factory reset...this may erase all existing info and bring the phone back to day#1
Click to expand...
Click to collapse
I mentioned that in the post, I did it while in Mexico City. It worked fine until this week, late last week. The battery only gives me about 5 hours now with just 32% audio playback and about 10% web access.
I guess I'll order a Anker battery from Amazon.
I rooted the phone again last night but before I did that, the phone became unresponsive three times in an hour. Which microSD card are you talking about? I just bought a 32GB Class 6 card and that works fine, I play all my audio from it, no problems.
If you mean the internal microSD card, that could be possible. I assume I can crack open the phone and replace this easily?
I should mention it never does that while plugged into a power source, so maybe this is all battery related.

Possible Fix...
When I had to hard reboot the phone again this afternoon, a little forced closed window came up for TwLauncher.
After rebooting the phone I looking at Titanium Backup and cleared the cashe from TwLauncher and that seems to have solved the problem.
Somebody on here mentioned that after installing a ROM they had the same problem, was worth a try.
I will report back if the issue returns.

djfourmoney said:
When I had to hard reboot the phone again this afternoon, a little forced closed window came up for TwLauncher.
After rebooting the phone I looking at Titanium Backup and cleared the cashe from TwLauncher and that seems to have solved the problem.
Somebody on here mentioned that after installing a ROM they had the same problem, was worth a try.
I will report back if the issue returns.
Click to expand...
Click to collapse
My personal beliefs are that TB is good for causing a lot of problems.I used to use it,even bought pro,but even not restoring data when restoring apps I seamed to develop odd quirks or problems on about any ROM. Since not using it have much fewer problems.I am sure many people love it and think it's great, just thought I would give my $0.02

if your battery holds a charge...that is, it's letting you run the phone for more than several hours, it's unlikely to be the battery.
lags are usually due to apps misbehaving, media scan, wakelocks and wifi bugs...there are some others.
a factory reset ...complete reset..complete stock..will let you know if you have hardware of software issues.

qkster said:
if your battery holds a charge...that is, it's letting you run the phone for more than several hours, it's unlikely to be the battery.
lags are usually due to apps misbehaving, media scan, wakelocks and wifi bugs...there are some others.
a factory reset ...complete reset..complete stock..will let you know if you have hardware of software issues.
Click to expand...
Click to collapse
Thus far, that issue has not returned. Yes the battery holds a charge, but last only about 5-6 hours now, not 7-8 hours.
It seems it was a minor software issue. I did a factory reset, you keep missing that.
I did it in Mexico City (7 days ago).... Since that point and returning to the US, I have put my apps back on the phone. I had already updated to Gingerbread and it just reset to that.
I won't know more until I am out and about with my phone. I will be watching various auto racing events and don't plan on leaving the house this weekend.
Aussie V8's at COTA
NASCAR All Star Race @ Charlotte
World Challenge @ COTA
ELMS @ Imola
DTM @ Brands Hatch
WTCC @ Sazburg
Nurburgring 24 Sunday-Monday

elbscorp said:
My personal beliefs are that TB is good for causing a lot of problems.I used to use it,even bought pro,but even not restoring data when restoring apps I seamed to develop odd quirks or problems on about any ROM. Since not using it have much fewer problems.I am sure many people love it and think it's great, just thought I would give my $0.02
Click to expand...
Click to collapse
No problem, I've never had a problem with TB. I updated the rom to a rooted version of the AT&T Gingerbread release so I could even use it... lol
The phone was rooted for Froyo, I downloaded the AT&T Gingerbread from Samsung via Kies when it was released and it remained rooted.
But resetting it back to stock, TB didn't work until I put the rooted rom on the phone.

Sent from my SAMSUNG-SGH-I997 using xda app-developers app
After you did the factory reset how did you put your apps back?

elbscorp said:
After you did the factory reset how did you put your apps back?
Click to expand...
Click to collapse
Exactly...you had to use TB or another restore. If you used TB on froyo and restored on GB or vice versa, you may run into issues.
and ...sigh... I did not miss the fact that you stated that you had reset the phone. I just had doubts that you understood what I was trying to say...from inside the phone..under settings/privacy..there is a reset option. make sure everything you wanted is already backed up. reset it..then put it into download mode and use one of the odin or heimdall package and flash it back to complete stock...run it stock and dont back up anything. download only apps from the play store or side load the apps if you had the apk's.
check the battery use to see if you have wake locks or android OS or android system eating up for battery..then you will know

elbscorp said:
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
After you did the factory reset how did you put your apps back?
Click to expand...
Click to collapse
Well like this, I will not go into the details but somebody else put Swipe Lock on the phone and of course I didn't know what he put into the phone. I was trying to resolve data issue on TelCel.
I had to do a hard reset outside of the operating system. Since the ROM was already upgraded to Gingerbread but unrooted, it went back to its unrooted state meaning I couldn't use TB.
So I re-downloaded apps from my memory. All of them are free so it wasn't an issue, just time consuming.
qkster said:
Exactly...you had to use TB or another restore. If you used TB on froyo and restored on GB or vice versa, you may run into issues.
and ...sigh... I did not miss the fact that you stated that you had reset the phone. I just had doubts that you understood what I was trying to say...from inside the phone..under settings/privacy..there is a reset option. make sure everything you wanted is already backed up. reset it..then put it into download mode and use one of the odin or heimdall package and flash it back to complete stock...run it stock and dont back up anything. download only apps from the play store or side load the apps if you had the apk's.
check the battery use to see if you have wake locks or android OS or android system eating up for battery..then you will know
Click to expand...
Click to collapse
See above.
I used download mode to get out of Swipe Lock. I never used Swipe Lock, a-hole wanted to charge me 120 pesos ($7) to wipe it and put it back to stock, I wasn't going to do it, I know enough about Android phones to do it myself.
Oh well, lesson learned, I believe wiping the cashe from TwLauncher has solved the problem.
I did re-install all the apps from the store. I wasn't able to use TB until Thurs night (5/16). I noticed the errors Friday afternoon, wipe the cashe and no issues since.

Nexus 5 became a paperweight overnight (help!)

Hello xda, I have a problem!
My Nexus 5 is only six months old and aside from typical Nexus 5 shenanigans (the camera seizing upon lock, requiring a reset) it has worked fine. (though I have been very discontent with this device) Last night I was using my Nexus 5 as usual and I was tired, but too lazy to plug it into the charge port. By morning my phone died as expected, so I plug the charger in and lo-and-behold, it's stuck in boot up.
So naturally I freak the f*** out; I wait. To no avail.
I wait some more. Nix.
It's still f***ing booting.
So I know something's wrong with my phone and I said "f*** it; I'm just going to factory reset it" because knowing my luck, my phone decided to say "f*** you" and kill itself the night prior. (My affinity with technology is poor.)
So I wipe the damn thing.
I boot it up.
Loop. You've got to be kidding me.
I wipe the cache (don't tell me I should have done this first); nada.
I get flustered, chuck the black pice of s*** down the stairs, get desperate, pick it back up, take it to work with me (while it was still booting), I left for work at 12:00PM, it's now 7:04PM, I'm home and it's STILL BOOTING.
So what's a girl to do?
And I'm going to answer the fusillade of questions I know I'm going to get in response to my peril, so before you all premeditate; here's what I've done to my phone:
I rooted it THREE WEEKS AGO with KingRoot to turn off my proximity sensor. Why? Because I Skype and like to use my device at the same time, and Microsoft thought it would be brilliant to have the screen shut off any time something crosses slightly in front of the Nexus 's two stupid sensors, so horizontal use of the device gets thrown out of the window. (if any muppets at Microsoft are reading this, you're f***ing idiots! If I really wanted to turn my screen off to conserve battery power, I would lock the f***ing screen! I don't need YOU nannying me!)
I wasn't able to shut off the proximity sensor with root permissions so I got cheesed and unrooted, then uninstalled the application.
Things have been working perfectly fine. (And yes, my phone has been rebooted in that three week span.)
Up until last night, my phone was working perfectly normal. I did what I usually did.
Listened to music, checked my work schedule, text, watched YouTube videos, played Gameboy games on an emulator, and that's it.
Someone please help me with this phone so I can at least fix it and sell the wretched thing to some muppet for some money to put towards a REAL phone.
Thanks.
~ Ashley
And it finally died, just as I finished writing this.

Ashleyware said:
Hello xda, I have a problem!
My Nexus 5 is only six months old and aside from typical Nexus 5 shenanigans (the camera seizing upon lock, requiring a reset) it has worked fine. (though I have been very discontent with this device) Last night I was using my Nexus 5 as usual and I was tired, but too lazy to plug it into the charge port. By morning my phone died as expected, so I plug the charger in and lo-and-behold, it's stuck in boot up.
So naturally I freak the f*** out; I wait. To no avail.
I wait some more. Nix.
It's still f***ing booting.
So I know something's wrong with my phone and I said "f*** it; I'm just going to factory reset it" because knowing my luck, my phone decided to say "f*** you" and kill itself the night prior. (My affinity with technology is poor.)
So I wipe the damn thing.
I boot it up.
Loop. You've got to be kidding me.
I wipe the cache (don't tell me I should have done this first); nada.
I get flustered, chuck the black pice of s*** down the stairs, get desperate, pick it back up, take it to work with me (while it was still booting), I left for work at 12:00PM, it's now 7:04PM, I'm home and it's STILL BOOTING.
So what's a girl to do?
And I'm going to answer the fusillade of questions I know I'm going to get in response to my peril, so before you all premeditate; here's what I've done to my phone:
I rooted it THREE WEEKS AGO with KingRoot to turn off my proximity sensor. Why? Because I Skype and like to use my device at the same time, and Microsoft thought it would be brilliant to have the screen shut off any time something crosses slightly in front of the Nexus 's two stupid sensors, so horizontal use of the device gets thrown out of the window. (if any muppets at Microsoft are reading this, you're f***ing idiots! If I really wanted to turn my screen off to conserve battery power, I would lock the f***ing screen! I don't need YOU nannying me!)
I wasn't able to shut off the proximity sensor with root permissions so I got cheesed and unrooted, then uninstalled the application.
Things have been working perfectly fine. (And yes, my phone has been rebooted in that three week span.)
Up until last night, my phone was working perfectly normal. I did what I usually did.
Listened to music, checked my work schedule, text, watched YouTube videos, played Gameboy games on an emulator, and that's it.
Someone please help me with this phone so I can at least fix it and sell the wretched thing to some muppet for some money to put towards a REAL phone.
Thanks.
~ Ashley
And it finally died, just as I finished writing this.
Click to expand...
Click to collapse
Since you've already wiped data, have you tried unlocking the bootloader and flashing the Google factory image

I haven't because I can't. I'm on a Macbook and the Nexus 5 drivers aren't compatible with Macs apparently =/

Wait okay, so I misread what I looked at this morning.
So it says I have to flash a new rom to my phone O.K. but every website says I have to turn on USB debugging--how am I supposed to turn on USB debugging to unlock the bootloader if my phone is bricked to begin with? This doesn't make any f***ing sense!
HELP.
Also, my Mac doesn't recognize my device in fastboot mode; what am I supposed to do?!

Try this? It has Mac instructions too.
http://forum.xda-developers.com/showthread.php?t=2513701
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
I was able to unlock my bootloader on my Mac with no problems...
Sent from my Nexus 5 using Tapatalk

ldubs said:
Try this? It has Mac instructions too.
http://forum.xda-developers.com/showthread.php?t=2513701
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
I was able to unlock my bootloader on my Mac with no problems...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Don't you understand? I can't enable USB debugging because I can't ACCESS my phone! It's stuck in bootloop! I can't unlock the bootloader to begin with! Unless you know how to unlock the bootloader from the fastboot menu, you saying that you unlocked your bootloader doesn't help me. I tried everything in that thread and nothing works, I tried the terminal bull**** and the only thing that happens as I can get into the folder where the factory rom is, but I can't get it to flash, I can't get anything to happen--I don't know what the hell I'm doing.
Is there a way to start over without all of this stupid bootloader crap?

As far as I know ADB is not active in fastboot, it is not recognized. In fact I just flashed TWRP again with ADB off. You do need the fastboot drivers on your Mac installed correctly but that's no big deal. If you have access to your phone in fastboot it is simply fastboot oem unlock to unlock your bootloader.

PROGRESS REPORT
So last night I stayed up trying to fix my issue, and I've had no success. I've managed to flash back to Kitkat 4.4.4 but as soon as the phone boots into set up, immediately I get the error messages "unfortunately Camera has stopped working", "unfortunately Gallery has stopped working", and "unfortunately Google Playstore has stopped working". After setting up, my phone has NO service! It doesn't even recognize if there's a SIM card even inserted, or if I remove it.
I cannot open Playstore, it immediately crashes and my phone believes that it has no storage now, even though I see 12GB of space free. I tried flashing multiple roms and nothing beyond Kitkat will work, otherwise I get caught in a bootloop.
I tried installing Cyanogen mod and although it worked, I had the same issue--no service, no Playstore no storage.
I tried clearing the cache, the Dalvik and factory resetting several times and nothing works. I just flashed 4.4 and I'm updating it to 4.4.3 as we speak.
Also I think it's worth mentioning that every time I got caught in bootloop after flashing a new rom (and I tried all of them, including Lolipop, which always hangs) that when I boot in Recovery mode it says something along the lines of:
Invalid arguement couldn't mount blahblahblahgeniusspeak
Invalid arguement blahblahblahgeniuspeak
and so on. Does this have something to do with my lack of service, camera not working, Playstore not working and storage not working? I'm desperate people.

Have you got an imei number?,settings/about phone
Usually you just flash factory ROM, extract the file and then the second archive and flash each individual file and it should boot, factory reset and wipe cache to fix storage
I do this on my mac
If you can't do this then you may have a hardware issue
How did you try to turn off proximity sensor. There would be another way to keep screen on while skyping (keep screen on wake lock)

Also it sounds like you flashed custom roms without flashing gapps...
Sent from my Nexus 5 using Tapatalk

Definitely sounds like no gapps.

What's gapps? And I have no IMEI number (unknown), it says my (with my SIM inserted) Network is: Unknown
Mobile Network Type: Unknown
Mobile State is disconnected
Out of Service
Phone number is unknown
IMEI SV is unknown
IMEI is unknown
Not roaming either
What's the second archive? Every guide I used said use the flash-all.script and that's all you have to do, what're all these extra steps? How do I flash gapps, I don't even know what that is; I don't see the file anywhere in the factory image folder.
=/

I flashed again (back to stock; 4.4) and did everything manually instead of using the script, I even flashed the cache.img, recovery.img etc . . . and it's still the same issue. No service. No external storage available. No Google Playstore.
=/
I didn't flash a custom rom, I only flashed the official factory image from Google. Why doesn't anything ****ing work.
Is gapps going to return my storage and service?

Gapps is only for custom ROM. Since your imei etc is unknown seems like you have bad efs partition. I am not 100% sure. May be others can help.
Sent from my Nexus 5 using XDA Free mobile app

g930a keeps crashing after about a few weeks of a reload

I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.

dorlow said:
I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
Click to expand...
Click to collapse
It is the fault of the rom you installed. Since it is de-bloated, then the developer of that rom might have accidentally removed an important app or service which is the cause of all of your problems. It can be fixed it by installing the stock rom via odin, rooting the phone and installing a different rom.

You paid to root your phone?

This particular crash was the first time it happened on this pre-debloated rom. The previous ones have all been on the stock rom.

ok, last night my phone required an att update. It attempted to update and rebooted. Stuck in a boot loop. Couldn't get out of it. Would just sit at the AT&T logo indefinitely. This was with the stock ROM rooted. So, I had to reload stock room unrooted again. Does anyone else have this problem with the rooted stock rom? Basically it runs for a few weeks. Then AT&T attempts to update and crashes the OS.

You can't OTA update a rooted phone

So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.

dorlow said:
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
Click to expand...
Click to collapse
Freeze the updater service / process / app, clear the cache to remove the downloaded update

Can u explain further how to freeze the updater service?

Ok, I looked up how to freeze the updater service and did that. I re-unrooted the phone, rooted it, then froze the updater service. My phone never updated. This morning an app was crashing. Rebooted it and same thing. Stuck on the at&t logo and won't boot. I'm having to re-default it again. The phone never updated from AT&T. But something crashed it last night. No clue. Problem is when this happens, the phone never boots back up so I can't look at it to find out why it happened.