Related
Hi,
I have a major issue with my WiFi and reboots.
Background: I am using an ATT phone within the UK on T-Mobile network.
Randomely, the other day, the WiFi turned off and when I turned it back on, it says Error....
I have tried everything I can think of; wiping and reinstalling rom, erasing everything in fastboot, updating the radio (further question on that) and also kernels! Finally I tried FruitCake to get back to stock, still no luck!!
Radio: Are radio's carrier specific, i.e. could I flash a radio meant for Europe to replace the ATT one? (I am on .36)
What can I do now, please. Thanks
benny6812 said:
Hi,
I have a major issue with my WiFi and reboots.
Background: I am using an ATT phone within the UK on T-Mobile network.
Randomely, the other day, the WiFi turned off and when I turned it back on, it says Error....
I have tried everything I can think of; wiping and reinstalling rom, erasing everything in fastboot, updating the radio (further question on that) and also kernels! Finally I tried FruitCake to get back to stock, still no luck!!
Radio: Are radio's carrier specific, i.e. could I flash a radio meant for Europe to replace the ATT one? (I am on .36)
What can I do now, please. Thanks
Click to expand...
Click to collapse
If it helps, i accidentally formatted the PDS partition a while back and the reason for reboot is AP KERNEL PANIC
Any help would be greatly appreciated.
I am having similar problems. Just last night my phone started rebooting frequently after having turl's v8 build of cm9 for probably a week and it was working great. However, now I have tried wiping everything, putting on different cm7 or cm9 builds and what I have come to the conclusion is anytime I turn the WiFi on, it reboots.
It is not even connecting to anything, just turning it on makes it reboot. I was on the .36 radio with this issue, I tried using the .37P radio and it did not fix it.
Does anyone have any other ideas to try and fix?
Benny,
Do you get the option to turn it on? I'm on cm9 and it'll show up like the attached after it reboots.
No. I dont have that screen. It just says wifi error and Bluetooth crashes as well....
Sent from my MB860 using XDA App
From the other threads I have read, I think we are boned. It seems like the Broadcom WiFi/Bluetooth chipset is borked and the only fix other people have gotten is through an actual repair. I hope you are under warranty - I'm going to revert to stock and hope they accept it.
bassmarkie said:
From the other threads I have read, I think we are boned. It seems like the Broadcom WiFi/Bluetooth chipset is borked and the only fix other people have gotten is through an actual repair. I hope you are under warranty - I'm going to revert to stock and hope they accept it.
Click to expand...
Click to collapse
But, how come whenever I flash a new rom, the WiFi will work temporarily, i.e. it would connect, obtain IP etc for a few minutes then just not work until I reflash?
Surely that is not hardware?
Bump
Sent from my MB860 using XDA App
Did you use Titanium Backup, and restore apps like Maps, Music, and YouTube? People are saying this can cause issues.
Also did you restore call logs after flashing? I experienced my wifi and mobile networking dying after doing that on only some of the new roms out there lately. It's a bug with one of the base roms, that a lot of custom roms are based off of. It was fixed with a new base rom version, but some of the custom roms have yet to officially update. Updates are under way though. Try out Morrison's 0.7 and see if you get the same result. It's been updated.
Although, you could be having a completely different issue. If you mean you can just leave it running after flashing and the wifi dies, I don't know what to say.
Drakonas said:
Did you use Titanium Backup, and restore apps like Maps, Music, and YouTube? People are saying this can cause issues.
Also did you restore call logs after flashing? I experienced my wifi and mobile networking dying after doing that on only some of the new roms out there lately. It's a bug with one of the base roms, that a lot of custom roms are based off of. It was fixed with a new base rom version, but some of the custom roms have yet to officially update. Updates are under way though. Try out Morrison's 0.7 and see if you get the same result. It's been updated.
Although, you could be having a completely different issue. If you mean you can just leave it running after flashing and the wifi dies, I don't know what to say.
Click to expand...
Click to collapse
Tried all of the above and still nothing unfortunately. Just want to update on symptoms of the phone if that helps:
Everything eventually gets more and more buggy, even recovery is really laggy and slow
Data will stop after a few days use, and only fix that i know of is to reflash
WiFi does not work, it connects for about 30 seconds after a reflash, but then nothing.
Logcat says - Failed to Load WiFi Driver (after reporting WiFi HUNG)
The phone can crash when I plug in the MicroUSB to charge, when it restarts it says AP KERNEL PANIC.
I have tried everything except for flashing via RSD lite, do you think that could work?
Thanks
BUMP,
Any help at all with this unique situation would be very helpful.
Thanks
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
having the same problem. Did you figure out?
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
illikkalshahid said:
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
Click to expand...
Click to collapse
Hi there,
I have exactly the same problem, have you fixed? How?
Thanks
Q] Galaxy S4 Custom ROM's Issues (no sound, black screen on call)
Omg I was getting to be a little nervous. Still gotta flash but fingers crossed. This is for an att galaxy s4
Hi. I've got a challenge for the experts
I have a galaxy s4 (i9505) and currently on cyanogenmod 11-20140414-nightly so its running on 4.4.2
The minute i got my phone, i put foxhound rom and was on4.2.2 that time and everything was fine. It was about june last year. A couple of weeks ago, i decided to have a go at other roms or update to 4.4.2 so i tried foxhound rom that ran on4.4.2. This is when the problems started. The first problem was the signal was greatly affected that i could not get any signal indoors. So i tried several other roms like omega rom, cyanogenmod, wanamlite, wicked, virgin rom and several others but none of them perfectly worked. I always cleared cache and restore factory settings but still there were problems. On some roms the camera wont work as if there is another app using it. On others, i cant get any signal even though im in an area where i used to get strong signals. Another big problem is that i cant make a call! The screen goes black and can't do anything until the call gets disconnected. I can't use voice services like skype, ym, everything that uses the mic as if there is an app or service using it. When i put the jack to use the headset, i dont get the notification that im on headset unlike before.
So i decided to use stock rom on 4.3. Now i have even bigger problems. In addition to the previous problems stated, the wifi won't turn on but i can get a signal outside. Even though i have already removed the microsd card and wiped cache and restore to factory settings, the phone still says that the device was modified so i can't really return it even though it is still under warranty.
So now i decided to root it again and temporarily use cyanogenmod since the wifi works, texts and the internet works.
Btw, youtube doesnt work also. It doesnt play.
Sorry for the vrry long post but i just want to give much info as possible..
Thanks so much
Noypi14 said:
Hi. I've got a challenge for the experts
I have a galaxy s4 (i9505) and currently on cyanogenmod 11-20140414-nightly so its running on 4.4.2
The minute i got my phone, i put foxhound rom and was on4.2.2 that time and everything was fine. It was about june last year. A couple of weeks ago, i decided to have a go at other roms or update to 4.4.2 so i tried foxhound rom that ran on4.4.2. This is when the problems started. The first problem was the signal was greatly affected that i could not get any signal indoors. So i tried several other roms like omega rom, cyanogenmod, wanamlite, wicked, virgin rom and several others but none of them perfectly worked. I always cleared cache and restore factory settings but still there were problems. On some roms the camera wont work as if there is another app using it. On others, i cant get any signal even though im in an area where i used to get strong signals. Another big problem is that i cant make a call! The screen goes black and can't do anything until the call gets disconnected. I can't use voice services like skype, ym, everything that uses the mic as if there is an app or service using it. When i put the jack to use the headset, i dont get the notification that im on headset unlike before.
So i decided to use stock rom on 4.3. Now i have even bigger problems. In addition to the previous problems stated, the wifi won't turn on but i can get a signal outside. Even though i have already removed the microsd card and wiped cache and restore to factory settings, the phone still says that the device was modified so i can't really return it even though it is still under warranty.
So now i decided to root it again and temporarily use cyanogenmod since the wifi works, texts and the internet works.
Btw, youtube doesnt work also. It doesnt play.
Sorry for the vrry long post but i just want to give much info as possible..
Thanks so much
Click to expand...
Click to collapse
So, which type of rom do you want to be on, assuming most of the things work properly? I don't want to try to address all those issues because there are different ones for the different setups and would take forever. Most likely signal issues are from not using a matched modem with the firmware / rom you are running. Do you know the original carrier / region the phone is from so we can make sure you get the right stuff installed?
Please provide details on the the currently installed baseband version. Also, what is the last official version of Samsung's software that you installed via Odin or OTA (not via custom rom)?
es0tericcha0s said:
So, which type of rom do you want to be on, assuming most of the things work properly? I don't want to try to address all those issues because there are different ones for the different setups and would take forever. Most likely signal issues are from not using a matched modem with the firmware / rom you are running. Do you know the original carrier / region the phone is from so we can make sure you get the right stuff installed?
Please provide details on the the currently installed baseband version. Also, what is the last official version of Samsung's software that you installed via Odin or OTA (not via custom rom)?
Click to expand...
Click to collapse
Thanks for your reply.
The current cyanogenmod is fine although i prefer the virgin rom. but i can go back to virgin once the problems have been rectified.
I agree that the signal issue has something to do with the modem so i tried different modems using odin but the XXUBMEA wouldnt change despite trying several modems and several times.
The phone is on three network (uk) with its current baseband 19505XXUBMEA.
The official rom i tried was on 4.3 and kies said it was the latest
Thanks again
Alright, I'm with ya so far. I'll look into the rom situation when I get back in front of the PC, but the trick with updating the modem is you gotta flash it twice in a row before you reboot unless you flash official firmware.
es0tericcha0s said:
Alright, I'm with ya so far. I'll look into the rom situation when I get back in front of the PC, but the trick with updating the modem is you gotta flash it twice in a row before you reboot unless you flash official firmware.
Click to expand...
Click to collapse
Thanks again for replying.
What i havent actually tried (which i'm reading at the moment) is the formatting of data under the advanced options on twrp. I dunno if it will make a difference say i try a new rom. I don't mind trying and starting from scratch. Like format data then install a new rom. Do u think this will make a difference? (will this be similar to formatting a dard drive on a pc before installing windows?)
What i suspect is there is nothing wrong with the roms i've tried but something in the installation got messed up and remains there even after wiping the data.
I think i have tried doing it twice only to find out that it didnt change the modem despite odin saying pass.
Should i format data then install a fresh rom?
Hard
but challeng refused
Ok, so there is something odd here. If you had flashed the official 4.3 via Odin, your modem would have changed to a newer one. The one you have is still a 4.2.2 one. Or were you referring to the last stock rom that you loaded with a custom recovery? Also, which recovery are you using?
Try this modem via Odin:
http://d-h.st/Kwv
Install Guide:
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Reference thread: http://forum.xda-developers.com/showthread.php?t=2192025
Let's see if that doesn't help anything and go from there.
If you have issues with wifi, there is a wifi fix to be had in the reference thread. Remember to flash that through the Phone slot if needed.
thanks again.
i can't exactly remember what modem i had when i flashed it with the official 4.3 using odin. but my guess would be the XXUBMEA. most of the custom roms i've tried had this modem anyway. some had no problems with 3g signal.
i am using twrp.
i don't want to play around with the modem yet as the 3g and wifi signals are working fine on cyanogenmod. its the call and video that's not working that i want to sort out.
do u think if i reflash by formatting data would clear out the problems i specified earlier? i don't mind trying this if u think it will make a difference.. tthanks.
es0tericcha0s said:
Ok, so there is something odd here. If you had flashed the official 4.3 via Odin, your modem would have changed to a newer one. The one you have is still a 4.2.2 one. Or were you referring to the last stock rom that you loaded with a custom recovery? Also, which recovery are you using?
Try this modem via Odin:
http://d-h.st/Kwv
Install Guide:
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Reference thread: http://forum.xda-developers.com/showthread.php?t=2192025
Let's see if that doesn't help anything and go from there.
If you have issues with wifi, there is a wifi fix to be had in the reference thread. Remember to flash that through the Phone slot if needed.
Click to expand...
Click to collapse
Noypi14 said:
thanks again.
i can't exactly remember what modem i had when i flashed it with the official 4.3 using odin. but my guess would be the XXUBMEA. most of the custom roms i've tried had this modem anyway. some had no problems with 3g signal.
i am using twrp.
i don't want to play around with the modem yet as the 3g and wifi signals are working fine on cyanogenmod. its the call and video that's not working that i want to sort out.
do u think if i reflash by formatting data would clear out the problems i specified earlier? i don't mind trying this if u think it will make a difference.. tthanks.
Click to expand...
Click to collapse
The custom roms you've been using don't install a modem with them, so that would be why you've been on the same one for a bit. Often times the stock rom is a little more picky about which modem it likes best, though this varies by phone and update. What call issues are you having? There were so many issues listed for various things on the first post that I had trouble sorting which problem for which rom (not criticizing, just making sure we're on the same page). And as far as videos go, is it just YouTube that isn't working right or any type of video playback? If it is just YouTube - is it force closing, not loading searches or videos, or some other problem?
es0tericcha0s said:
The custom roms you've been using don't install a modem with them, so that would be why you've been on the same one for a bit. Often times the stock rom is a little more picky about which modem it likes best, though this varies by phone and update. What call issues are you having? There were so many issues listed for various things on the first post that I had trouble sorting which problem for which rom (not criticizing, just making sure we're on the same page). And as far as videos go, is it just YouTube that isn't working right or any type of video playback? If it is just YouTube - is it force closing, not loading searches or videos, or some other problem?
Click to expand...
Click to collapse
thanks again for your interest.
the issue about the modem is somehow clear. thanks for clearing that up.
i think it is better to tackle the problems i have in my current setup rather than the previous problems. so, as previously mentioned, i am on cyanogenmod 11 (on 4.4.2). here are some of the problems i am aware of or rather, those that i have experienced:
1. calls - whenever i dial a number, the screen goes black as if the phone is next to my ear (could there be something wrong with the proximity sensor? i haven't done anything to rectify this yet though. when this happens, i can't do anything as the seems to hang although i could see the call timer working. during that call however, i can't hear a sound nor the person i just rang. same thing happens when someone calls me. my phone vibrates (because there is another problem with the sound which i will discuss next) and when i answer it, i hear no sound and the screen goes black and i couldn't do anything with the phone. i have to wait till the caller disconnects before the phone becomes useable again.
i tried calling using viber and the same thing happens.
2. sound - phone is muted even though all the volume controls are midway or almost 100%. i tried changing the ringing tone but i don't hear any sound at all. normally, when i switch to a different ringtone, it should give me a preview of what the chosen sound is like.
3. videos - it doesn't work. when i go to youtube, it opens up the site, opens the selected youtube clip, tries to play it but pauses then tries to play again then pauses until i get a message saying "there was a problem while playing. touch to retry."
so far these are the problems i have faced.
sorry for the long post again.
Hmm. Seems weird that you are having so many issues that most others aren't having, at least not since some of the earlier builds. During the install of CM, did you wipe /system? If not, I definitely would just start fresh. Install the most up to date modem. Wipe everything (system, data, cache, dalvik). Use the most up to date CWM (I like TWRP most of the time, but since CM says you should try CWM before reporting issues, it's one of those things...) Some Samsung proximity sensors aren't that accurate and really don't work well with CM. Other users reported that issue i the main CM thread for your phone, but was definitely not prevalent. I had a Samsung phone that I couldn't use a tempered glass screen protector with as they had an app to install to test to see how sensitive it was and mine didn't pass the test, though it worked for everything else.
As far as the video bug. It affected some earlier builds and other roms based off of CM but I hadn't seen anyone commenting about it for a bit so can't imagine it still being a common issue as that's a deal breaker for most. It might just be easier at this stage to either go back to stable CM 10.2 or try another rom altogether, such as Slim.
es0tericcha0s said:
Hmm. Seems weird that you are having so many issues that most others aren't having, at least not since some of the earlier builds. During the install of CM, did you wipe /system? If not, I definitely would just start fresh. Install the most up to date modem. Wipe everything (system, data, cache, dalvik). Use the most up to date CWM (I like TWRP most of the time, but since CM says you should try CWM before reporting issues, it's one of those things...) Some Samsung proximity sensors aren't that accurate and really don't work well with CM. Other users reported that issue i the main CM thread for your phone, but was definitely not prevalent. I had a Samsung phone that I couldn't use a tempered glass screen protector with as they had an app to install to test to see how sensitive it was and mine didn't pass the test, though it worked for everything else.
As far as the video bug. It affected some earlier builds and other roms based off of CM but I hadn't seen anyone commenting about it for a bit so can't imagine it still being a common issue as that's a deal breaker for most. It might just be easier at this stage to either go back to stable CM 10.2 or try another rom altogether, such as Slim.
Click to expand...
Click to collapse
i know. i don't really want to blame these issues i've mentioned to the rom i am using or have tried. perhaps there was something i did not do or overdid that messed it all up. the cynagenmod 10 (the stable version for my s4 model) had similar issues as the cm11. so i suspect the problem i've created still lingers within my phone that messes up a lot of things.
during installation, i did wipe the system, data, cache and dalvik which i found in the advanced menu.
the thing is, everything else worked fine when i was on 4.2.2 (like the proximity sensors, videos, sounds, etc) so as i said earlier, i don't want to blame it on the roms.
i might have another go on the slim rom tonight but use CWM instead of TWRP.
thanks again for your interest and help
Noypi14 said:
i know. i don't really want to blame these issues i've mentioned to the rom i am using or have tried. perhaps there was something i did not do or overdid that messed it all up. the cynagenmod 10 (the stable version for my s4 model) had similar issues as the cm11. so i suspect the problem i've created still lingers within my phone that messes up a lot of things.
during installation, i did wipe the system, data, cache and dalvik which i found in the advanced menu.
the thing is, everything else worked fine when i was on 4.2.2 (like the proximity sensors, videos, sounds, etc) so as i said earlier, i don't want to blame it on the roms.
i might have another go on the slim rom tonight but use CWM instead of TWRP.
thanks again for your interest and help
Click to expand...
Click to collapse
Do you have a screen protector or anything like that? Sometimes if it isn't laying on the screen right or dirt gets around it, it can cause issues. There's also a way to pop out the actual proximity sensor and clean between the part and the little piece of clear glass on the back of the front piece of glass that can help too if it ends up being hardware related.
es0tericcha0s said:
Do you have a screen protector or anything like that? Sometimes if it isn't laying on the screen right or dirt gets around it, it can cause issues. There's also a way to pop out the actual proximity sensor and clean between the part and the little piece of clear glass on the back of the front piece of glass that can help too if it ends up being hardware related.
Click to expand...
Click to collapse
I put the screen protector when i got the phone and i don't see any visible dirt so i wouldn't want to blame it either. Although i did read about the screen protectors causing problems. But the thing is, even youtube or any videos do not play. Even any sound.
I've tried the slimkat rom by following the developers' instructions and still no youtube, no sound, can't make a call as i can't hear the person i'm calling nor can that person hear me.
Any other suggestions on what to do? I don't mind going back to stock as long as i get all the features back. I went to official 4.3 before but had more severe issues. Or perhaps i did it wrong?
Thanks..
Videos are another issue, but I still think the call problems and such are modem related. What I would do would be to wipe everything, then use Odin to install official Kit Kat, then test this stuff out and see if it works. If so, then you can do a nandroid and redo recovery and try the roms again, then if they still have that issue then your phone just doesn't cooperate with CM roms or something weird like that. If it doesn't work even after official 4.4.2, then there's probably something else going on, possibly hardware related.
es0tericcha0s said:
Videos are another issue, but I still think the call problems and such are modem related. What I would do would be to wipe everything, then use Odin to install official Kit Kat, then test this stuff out and see if it works. If so, then you can do a nandroid and redo recovery and try the roms again, then if they still have that issue then your phone just doesn't cooperate with CM roms or something weird like that. If it doesn't work even after official 4.4.2, then there's probably something else going on, possibly hardware related.
Click to expand...
Click to collapse
Thanks.
Got hold of the official 4.4.2 and flashed it via odin. Failed. But tried again and now working fine. Sound is back, video is back as well as calls. Just the annoying google search failing all the time.
The baseband it has is I9505XXUFNC9. i didn't install any modem in odin though. Just flashed in the pda section the tar file
Now i don't know whether to root this again and try custom roms or leave it as it is. I saw knox by the way but haven't installed it. Or is it pre installed? I have little knowledge about knox
Any ideas? Other apps I installed to try (eg Signal) fail too. Stock ROM.
This is my fist post, have visited many times. Here we go.
As a LG V20 owner, I recommended the V30+ to two people at work. In a matter of 24 hours, both units stopped sending and receiving emails. I have taken the sims out and tested these in other phones, not a sim issue. I then moved my sim (Telstra Aus) into the V30 and only in the Messaging app, it came up with the message No SIM. This I thought might be a sim slot issue, moved it into the other slot closest to the outside. This worked for about an hour. Then the same issue occurred again. It has to be software, an update or a network change that has caused this. I did a network setting reset, have cleared cache for messaging app. SAFE MODE etc. Very strange.
yanni_pap said:
Any ideas? Other apps I installed to try (eg Signal) fail too. Stock ROM.
Click to expand...
Click to collapse
Yes I used Messenger app for SMS and this failed. It sounds network setting related but still testing.
I had the same problem on my V30, suddenly SMS has stopped working. (I'm using Textra app)
I checked the sim card on the other phone and it was ok.
I found on the internet that other V30 are also affected.
The solution was to install the Message app from Google and run it.
Now SMS is working on Textra and also on the stock app.
Whoa, didn't see this before I posted in another thread. Same problem here, but I already had Messages installed! Wonder if it's just this phone for some reason?? My partner is also on VZ (S7) and can send SMS
edit: apparently it's something Google broke. Temp fix is to disable Carrier Services!
I just recently started having text messages not sending. I am on Verizon LG V30 using the vs996 30c debloated rom. Everything has worked fine until last week when I installed the latest Resurrection Remix rom. Since these roms’ tethering and WiFi do not work, I tried installing the us998 modem zip. I don’t know if that is the problem or not, but, I could not get it to work. I have since reinstalled my 99630c debloated rom and have now lost the ability to send text messages, although I can receive texts just fine. I have done clean installs and dirty installs of the rom. I, just yesterday, did a restore of a previous 99630c backup, changed messaging apps, etc. I even reinstalled Verizon’s messaging app.The messaging problem still persists.
i just got off the phone with a very nice Verizon tech, who spent about 40 minutes trying to help me. No success. She said everything appears to be working fine on their end. She ran out of things to try. She thinks my rooting the phone might possibly have something to do with it, which I agree with.
Does anyone have a working link to John Fawkes vs99630c zip? The one one his zip thread does not download for me. I thought I would try starting again with that zip. Maybe I need to try a different modem download?
Any suggestions much appreciated. Thx
gimpy1 said:
I just recently started having text messages not sending. I am on Verizon LG V30 using the vs996 30c debloated rom. Everything has worked fine until last week when I installed the latest Resurrection Remix rom. Since these roms’ tethering and WiFi do not work, I tried installing the us998 modem zip. I don’t know if that is the problem or not, but, I could not get it to work. I have since reinstalled my 99630c debloated rom and have now lost the ability to send text messages, although I can receive texts just fine. I have done clean installs and dirty installs of the rom. I, just yesterday, did a restore of a previous 99630c backup, changed messaging apps, etc. I even reinstalled Verizon’s messaging app.The messaging problem still persists.
i just got off the phone with a very nice Verizon tech, who spent about 40 minutes trying to help me. No success. She said everything appears to be working fine on their end. She ran out of things to try. She thinks my rooting the phone might possibly have something to do with it, which I agree with.
Does anyone have a working link to John Fawkes vs99630c zip? The one one his zip thread does not download for me. I thought I would try starting again with that zip. Maybe I need to try a different modem download?
Any suggestions much appreciated. Thx
Click to expand...
Click to collapse
See my solution directly above your question. It's not "rooting" that caused it, it's "Google" that caused it. Uninstalling or freezing Carrier Services will fix it. Did for me.
Check the litany of * reviews from today alone:
https://play.google.com/store/apps/details?id=com.google.android.ims&showAllReviews=true
Also, both the standard and debloat ROMs for VS99630c from their respective threads and androidilehost are downloading fine for me.
Thx, but did not work for me. I went into TiBu and found carrier services sitting in the non installed portion of the apps. So, I installed it (first with app, then with data) and tried both messaging apps with it installed. That did not work, so I went back into TiBu again and froze it. It still does not work.
I have tried downloading the standard zip from Fawkes zip thread 8 or 10 times or so. It gets to about 8 or 9% , then gives the message unsuccessful.
I will keep trying. Thx for your suggestions.
As an edit. My phone has also started giving me problems with my fingerprint recognition and my phone dialed has suddenly changed looks forcing me to constantly press and swipe an unlock button to keep the dial pad open if I hesitate too long in punching in numbers or trying to change to speakerphone from there.
I don’t know if it is something I have done/installed (wrong modem perhaps?).
And having the new XDA transition at the same time certainly didn’t help .
gimpy1 said:
Thx, but did not work for me. I went into TiBu and found carrier services sitting in the non installed portion of the apps. So, I installed it (first with app, then with data) and tried both messaging apps with it installed. That did not work, so I went back into TiBu again and froze it. It still does not work.
I have tried downloading the standard zip from Fawkes zip thread 8 or 10 times or so. It gets to about 8 or 9% , then gives the message unsuccessful.
I will keep trying. Thx for your suggestions.
Click to expand...
Click to collapse
I don't know what to tell you about the downloads, confirmed they work.
You don't need to freeze CS, you can literally just uninstall it from the Play store. It's just an enhancement for the Google MEssages app they broke. if you don't use Messages, you surely don't need it. I don't know what you meant about CS showing up in the "non installed portion of the apps". It's either installed and frozen or thawed, or it's not. Maybe you had a backup there for reasons? Regardless, you certainly need to reboot after changing CS, not sure if you did that.
You have alot of other issues coming from RR, then flashing a modem, then trying to dirty flash VS996. Since you have TB already, you should definitely backup your apps, then Maybe clean flash VS99630c once you've followed the WTF thread. You should probably wipe your system after the other ROMs and just start over.
That certainly was a quick answer. In TiBu, under “backup/restore”, I have all the apps that are currently on my phone—a very long list. This list can be frozen, etc., and is bolded and colored fonts. Scrolling down that list, it ends and a list starts that is not bolded and has lines thru it. I guess these are apps, etc. that I have, at one time, had on the phone and can be re installed via TiBu.
I was trying to “start over” by downloading the vs99630c rom and try it. Where were you thinking I need to start over at? I wish to work only on “zips” via twrp, as I don't have much luck/knowledge with kdz and computers.
Thx, again.
Again, I'm the furthest thing from the expert here, but he's on travel! Check the WTF thread, because I'm not sure what happens when you wipe with the flashes you've made. But you'd probably start from 6.7. MORE TWRP ACTIONS here:
https://forum.xda-developers.com/t/...ar-instructions.3790500/page-10#post-76584629
I would reboot to TWRP and do a complete system backup in case this goes tits up you can restore that from TWRP. Then I would boot to OS and back up everything in TB, then delete all uninstalled backups through the batch actions. Then reboot to TWRP again, wipe, install the VS99630c ROM, install MAgisk, reboot. Make sure your install works then restore your apps through TB.
Ok, thx. I wish to install the vs99630c rom zip now (not the debloated) and am unable to download it from JohnFawkes LG V30 vs 996-30c thread from here on xda. I have tried via my phone about a dozen times now and it stops now generally after the 10 to 20% zip has downloaded. I even tried it a couple of times downloading onto a laptop. Can you possibly point me to a different link that I can try? I need to be on Verizon’s vs 996 and not on the 998 rom, I think? Sorry for the big bother.
Well, I did finally find a download mirror on here from chazzmatts thread using his mirror. It is downloaded now. I will try this installation before going thru the wtf steps you referred me to. If this doesn’t work, then i will try it.
thx, again for your help.
As an update, I did a clean wipe and installed this zip. So far, it seems to have settled things down for. I was able to text (2) and make a phone call. Both worked. I did agree to everything they asked (I normally refuse things such as location, etc.). I’m happy for now. Later, I may try to reinstall the debloated zip.
Ideveraux, thx for all your help on here. I really appreciate it.
Make sure you backup TWRP and TB. Just saying!
And to the OP, I’m sorry I hijacked your thread. I hope you got yours solved, too.
I had this problem after owning the phone for several days.
I'm not sure why, but when i installed Google's "Messages" app, the problem was fixed.
I didn't have to run the messages app, just install it. The stock app suddenly started working again.
I then uninstalled google messages (without ever running it), and the next day I had the same problem.
Once again; I installed google messages, and the problem solved itself without ever running google messages.
This time; I haven't uninstalled google messages.
I'm guessing that something about SMS settings got messed up (i checked them when the problem first happened and couldn't find a problem), and installing a new message app restored the settings to normal.
TLDR: if SMS stops working, Install Google Messages. Problem solved.
Lozv said:
I had this problem after owning the phone for several days.
I'm not sure why, but when i installed Google's "Messages" app, the problem was fixed.
I didn't have to run the messages app, just install it. The stock app suddenly started working again.
I then uninstalled google messages (without ever running it), and the next day I had the same problem.
Once again; I installed google messages, and the problem solved itself without ever running google messages.
This time; I haven't uninstalled google messages.
I'm guessing that something about SMS settings got messed up (i checked them when the problem first happened and couldn't find a problem), and installing a new message app restored the settings to normal.
TLDR: if SMS stops working, Install Google Messages. Problem solved.
Click to expand...
Click to collapse
I tried that initially and that's not the accepted fix at all. Read above.
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
iJaviXR said:
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
Click to expand...
Click to collapse
Check my POCO F1 Ultimate Collection & Guides. Try to Clean Install Pixel Experience for example, according my guide (u need to format data also). Let me know how it goes.
Tried Android 10 and 11 Pixel Experience, tried with stock and NG Kernels. Still stays forever in the first load of the SO.
Just got the properties file from XiaomiADBFastbootTools. Maybe someone can see something wrong on it.