Database Info

Galaxy S Blaze on Cm10 Keeps Randomly Shutting Off

So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2

Daze7 said:
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Click to expand...
Click to collapse
Are you running the latest nightly or the 'stable' build? The 'stable' build (note the "") isn't that stable and from the sound of it you are experiencing the screen of death (SoD) that I believe is present in the 'stable' build.
If you flashed the 'stable' build, flash the newest nightly instead. Or better yet, head on over here and also flash this (it's better than CM10 IMO - Just be sure to flash the kernel AFTER the rom). :good:

Daze7 said:
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Click to expand...
Click to collapse
Which version of CM10? No reboots here on Provision.. Used CM10 latest nightly as a base.. If you have random reboots then I should too.. Also a logcat would be helpful.
Sent from my Provisioned Galaxy S Blaze

Im on the stable version, but ill try the nightly like the first post suggest or the link you provided
Edit: logcat on the way sorry about that
Sent from my SAMSUNG-SGH-T769 using Tapatalk 2

anactoraaron said:
Are you running the latest nightly or the 'stable' build? The 'stable' build (note the "") isn't that stable and from the sound of it you are experiencing the screen of death (SoD) that I believe is present in the 'stable' build.
If you flashed the 'stable' build, flash the newest nightly instead. Or better yet, head on over here and also flash this (it's better than CM10 IMO - Just be sure to flash the kernel AFTER the rom). :good:
Click to expand...
Click to collapse
Hey, I downloaded the rom and kernel that u suggested. When i plugged in my phone to my laptop to transfer the files to my sd card i noticed that my internal sd and ex sdcard now reads as 'Generic Hierarchical'. Prior to this i did notice that my ex and internal memory were not showing the correct amount of space after rooting but i was so happy with the root that it slipped my mind somehow.
What in the world is generic hierarchical? And how can I get it safely to Fat32 to flash the ParanoidAndroid without messing up my phone?

Daze7 said:
Hey, I downloaded the rom and kernel that u suggested. When i plugged in my phone to my laptop to transfer the files to my sd card i noticed that my internal sd and ex sdcard now reads as 'Generic Hierarchical'. Prior to this i did notice that my ex and internal memory were not showing the correct amount of space after rooting but i was so happy with the root that it slipped my mind somehow.
What in the world is generic hierarchical? And how can I get it safely to Fat32 to flash the ParanoidAndroid without messing up my phone?
Click to expand...
Click to collapse
Go to settings/storage. Press menu. Then USB computer connection. There you can choose. Select USB mass storage. When connected to the computer it will prompt you if you want to move files from computer to your phone.
Sent from my Provisioned Galaxy S Blaze

In the end I just went back to stock and did a clean new root, this time with ParanoidAndroid. I loved the cm10 stable i had but the phone shutting off was t0o much. Thanks for all the help though i really appreciate it. :angel:

XT925 - Wifi not working after Custom Rom install (but bluetooth works?)

So I'm new to rooting and flashing custom roms on android devices. This also shows that I'm new because I forgot to make a backup of my stock system before moving forward, hence this problem.
So I currently have CM 10.2 flashed on my phone and so far I can't get the wifi to work. My bluetooth works perfectly fine (I've read that if one fails usually the other should too), so I don't know what to do.
At this point I'm sure i'm stuck because I've flashed a few different roms already to see if i can fix it (10.0, 10.1, 10.2, and hacker's aosp 4.4) but the wifi isn't working in either so I stuck to the rom that had the fewest bugs.
What's weird was that it was working when I had 4.4 flashed, but when i found it too buggy and flashed CM 10.2, now it doesn't work.
Anyone else have this problem? I guess I can live with it for a while until maybe I purchase a new phone.
Thanks

di3zelherbert said:
So I'm new to rooting and flashing custom roms on android devices. This also shows that I'm new because I forgot to make a backup of my stock system before moving forward, hence this problem.
So I currently have CM 10.2 flashed on my phone and so far I can't get the wifi to work. My bluetooth works perfectly fine (I've read that if one fails usually the other should too), so I don't know what to do.
At this point I'm sure i'm stuck because I've flashed a few different roms already to see if i can fix it (10.0, 10.1, 10.2, and hacker's aosp 4.4) but the wifi isn't working in either so I stuck to the rom that had the fewest bugs.
What's weird was that it was working when I had 4.4 flashed, but when i found it too buggy and flashed CM 10.2, now it doesn't work.
Anyone else have this problem? I guess I can live with it for a while until maybe I purchase a new phone.
Thanks
Click to expand...
Click to collapse
Did you flash 10.2 directly over 4.4 without wiping system data and both caches?
Sent from my XT926 using Tapatalk

koftheworld said:
Did you flash 10.2 directly over 4.4 without wiping system data and both caches?
Sent from my XT926 using Tapatalk
Click to expand...
Click to collapse
The first time, no. I thought I may have installed 4.4 incorrectly so after installing 10.2 i tried flashing 4.4 again, but I did wipe the caches, system, data and dalvik caches the second time going back after reading in this forum how to flash over a custom rom. But then seeing that the bugs were still there, i wiped again and went back to 10.2 and I've been there for a day now.

Missed Wifi
I'm facing the same trouble , same conditions.

Solved
zirig said:
I'm facing the same trouble , same conditions.
Click to expand...
Click to collapse
This will solve !! http://forum.xda-developers.com/showthread.php?p=47415109&posted=1#post47415109
thanks for xXLuHXx

zirig said:
This will solve !! http://forum.xda-developers.com/showthread.php?p=47415109&posted=1#post47415109
thanks for xXLuHXx
Click to expand...
Click to collapse
That worked! Thank you!

[Q] SMS won't send. Can receive/send MMS calls and Data

The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.
What wont work: Flashing to CM11 does not change the issue.
Disabling Voice+ does not change the issue
Factory Reset does not change the issue
Workarounds: Toggle Airplane mode
Switching Mobile Network to CDMA only (not permanent)
Change your number to a different area code
Going back to a Touchwiz based ROM
The Solution
net-cat said:
Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.
NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)
Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.
Requirements:
A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)
VRBMB1 AIO Flash, available here. (Thread here.)
I'm going to assume you know how to boot into and use recovery.
NOTE: Do NOT let the stock ROM install any updates.
Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
Flash the VRBMB1 AIO.
Wipe data and cache.
Flash the stock ROM.
Boot into the stock ROM.
The reprovisioning seems to happen as a part of ROM's initial boot up.
Send a few text messages to test. (I sent them to Twitter.)
Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.
This would be a good time to back up your IMEI if you haven't already done so.
Reboot into your recovery, wipe data/cache and restore your nandroid backup.
At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.
DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!
CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)
Click to expand...
Click to collapse
buffal0b1ll said:
I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip
Click to expand...
Click to collapse
Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.

This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.
Stock 4.3 is kind of lame:
-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.
-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.
-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.
Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already

It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/showthread.php?t=2654822
It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...
Edit: And another thread http://forum.xda-developers.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.
edit2: and another thread http://forum.xda-developers.com/showthread.php?p=50627899

Just looking for more info
Sent from my SCH-I535 using Tapatalk

Dex954 said:
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
SO this is the current status that I know.
The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).
Current Workarounds:
Switch to TouchWiz based Roms
Switch your radios to be CDMA only
Call verizon and switch your number to a different area code
I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.

I'm 717
Sent from my SCH-I535 using Tapatalk

I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.
And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.

I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?
Sent from my SCH-I535 using Tapatalk

Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658

DreamFX said:
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
Click to expand...
Click to collapse
Godspeed my friend.

Anyone try aosp to see if fixed yet?

Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.

capt730 said:
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
Click to expand...
Click to collapse
I try every other day. 717 for me. Remaining hopeful it's fixed... One day...

What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app

capt730 said:
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.
Sent from my SCH-I535 using XDA Premium 4 mobile app

I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.

capt730 said:
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
Click to expand...
Click to collapse
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.

I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.

Obaterista93 said:
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
Click to expand...
Click to collapse
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,

Whisk_33 said:
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Click to expand...
Click to collapse
Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.

[Q] Losing Network Constantly - Latest CM Nightly Build

Hello!
I was using the SungSonic ROM for almost a year now and I decided to change it today. So I flashed a CyanogenMod Nightly build for the P3100 This morning.
It booted up fine, and there were no issues in the beginning.
But then it started disconnecting calls randomly. Like, Someone calls, The phone rings for a second and boom! It shows a missed call.
I figured rebooting it would fix it but it made my problem only worse.
It now barely shows any Network service at all. If it is there, only for about 20s before it goes back off.
Is there any way to fix it without flashing another ROM? I like CyanogenMod and plus, its for my mother and I prefer keeping it simple.
Also, keep in mind that my Tab does not get recognised on any PC with any Cable I could find.
So, I am stuck with PhilZ Recovery for the P3100.
If the problem can be fixed via Flashing a new Mode/Baseband then please, give me a .zip for only the modem and not the whole ROM.
Thank You for Reading and I will hope you guys help me out.
Regards,
Shinichi Reshima

Always do a nandroid B/U before you flash so if you run into a problem like this you can go back. CM nightlys are not always stable, and sometimes you can't use them unless you have the base stable version of that ROM already installed. Must try and install the base version of the build, it may fix your problem. I run CM11 by Android Andi with no issues and no nightlys.
Pp.

Music issue...

Hey guys, I can't seem to get this figured out, so I have resorted to coming to the forum for help. On every single ROM I have ran lately EXCEPT the old LiquidSmooth 4.4.4(most recent version), I have had issues playing music through AUX. WHenever I would plug in my aux cable, play a song, then turn off my screen, the music would start lagging and there would be lots of static. but if I waked the device it would be fine. Turn the screen back off, same thing. It started happening after flashing this GPE ROM found here http://forum.xda-developers.com/htc-one-m8/development/rom-m8-gpe-01232015-t3010825
Now it does it on Viper, any GPE or AOSP other than LiquidSmooth 4.4.4. I flashed Fluent ROM in the Verizon Dev thread last night and same thing. It will also do it on all versions of Viper(4.4.4 and 5.0.1). Is anyone else experiencing this? BTW I have not tested Bluetooth, so I don't know if it does it there too. I have tested the actual speakers on the phone, and it does not do it there, just on aux. kinda making me think it may be my cable, but I'm just looking to see if anyone else is having these issues.
Thanks in advance guys!

blkhrt13 said:
Hey guys, I can't seem to get this figured out, so I have resorted to coming to the forum for help. On every single ROM I have ran lately EXCEPT the old LiquidSmooth 4.4.4(most recent version), I have had issues playing music through AUX. WHenever I would plug in my aux cable, play a song, then turn off my screen, the music would start lagging and there would be lots of static. but if I waked the device it would be fine. Turn the screen back off, same thing. It started happening after flashing this GPE ROM found here http://forum.xda-developers.com/htc-one-m8/development/rom-m8-gpe-01232015-t3010825
Now it does it on Viper, any GPE or AOSP other than LiquidSmooth 4.4.4. I flashed Fluent ROM in the Verizon Dev thread last night and same thing. It will also do it on all versions of Viper(4.4.4 and 5.0.1). Is anyone else experiencing this? BTW I have not tested Bluetooth, so I don't know if it does it there too. I have tested the actual speakers on the phone, and it does not do it there, just on aux. kinda making me think it may be my cable, but I'm just looking to see if anyone else is having these issues.
Thanks in advance guys!
Click to expand...
Click to collapse
Did you flash any audio mods or new firmware?

loonatik78 said:
Did you flash any audio mods or new firmware?
Click to expand...
Click to collapse
I have not flashed either. However, as we speak, I am updating my firmware to the new 5.0.1 firmware found here...http://forum.xda-developers.com/showthread.php?t=2723159...and I downloaded the version for TWRP users, and I have the latest TWRP 2.8.5.0 installed. So maybe that will make a difference?

blkhrt13 said:
I have not flashed either. However, as we speak, I am updating my firmware to the new 5.0.1 firmware found here...http://forum.xda-developers.com/showthread.php?t=2723159...and I downloaded the version for TWRP users, and I have the latest TWRP 2.8.5.0 installed. So maybe that will make a difference?
Click to expand...
Click to collapse
Possibly, but I doubt it. There's something telling the kernel to sleep which is why it happens when you turn your screen off. I'd try wiping /system before flashing a ROM. There might be something from liquid being left behind. Factory resets don't wipe /system. If you're ROM requires an intact /system such as Adrenaline, flash a stock rooted ROM first, then the custom ROM. That's what I'd try. Someone else might have a better idea.

loonatik78 said:
Possibly, but I doubt it. There's something telling the kernel to sleep which is why it happens when you turn your screen off. I'd try wiping /system before flashing a ROM. There might be something from liquid being left behind. Factory resets don't wipe /system. If you're ROM requires an intact /system such as Adrenaline, flash a stock rooted ROM first, then the custom ROM. That's what I'd try. Someone else might have a better idea.
Click to expand...
Click to collapse
Actually every single time I flash a new rom, I go into advanced wipe and wipe system, data, cache and dalvik cache 3 times. Every Time. But I flagged that new firmware and was rubbing digital high rom from the Verizon thread and did not have the music issue. I'm running fluent rom sense 7 from the Verizon thread now but have not tested the music yet But will update you guys in the morning. Thanks for all your replies