Unable to receive calls and SMS after root - Verizon Samsung Galaxy S7 Questions & Answers

After rooting, I cannot receive phone calls or SMS messages. Even after making a call and changing "Searching for Service" to "Verizon Wireless", I still can't.
Does anyone know a fix for this? I really want to keep root, but there's no point of having a phone if you cannot receive phone calls.

I would suggest download the STOCK firmware, install it go thru the setup process. Then flash what ever firmware you are wanting to root a d you should be fine. The important part let it boot up on stock and check everything out before you root.

Same thing happened to me today after the pe1 root. I tried everything to get my text to receive. Only would recieve texts the First two minutes. Ended reverting to stock pe1 and got all my texts from this morning to now

ironbesterer said:
After rooting, I cannot receive phone calls or SMS messages. Even after making a call and changing "Searching for Service" to "Verizon Wireless", I still can't.
Does anyone know a fix for this? I really want to keep root, but there's no point of having a phone if you cannot receive phone calls.
Click to expand...
Click to collapse
I believe I have found the issue. I have returned to stock after the same thing happened to me. Re-rooted and after I set everything back up it happened again. It says "searching for service" in the status bar and lockscreen. Phone status in settings shows out of service.
-- I ended up reflashing the v15 fix for a second time, first was right after I rooted and wiped the cache partition. I am now able to send/recieve texts and phone calls now. Hope this helps

Reflash v15 fix
Do what Kole said – reflash the v15 zip. I had the same problem. I reflashed stock and it worked for about a day before I had the same problem again. Anyways, in order to find the cause, I used my wife’s phone to call mine every time I made a substantial change, for example, after rooting, after flashing one of the fixes, after flashing Xposed… I even did it every time I activated a single module. Long story short, it came back but didn’t seem to be directly caused by anything. After going to safe mode, uninstalling xposed, even calling Verizon to reset my connection with them, nothing worked… until I reflashed the v15 zip. I’ve been going strong for about a month now without any problems.

Same issue but still not working after flash
Zram5678 said:
Do what Kole said – reflash the v15 zip. I had the same problem. I reflashed stock and it worked for about a day before I had the same problem again. Anyways, in order to find the cause, I used my wife’s phone to call mine every time I made a substantial change, for example, after rooting, after flashing one of the fixes, after flashing Xposed… I even did it every time I activated a single module. Long story short, it came back but didn’t seem to be directly caused by anything. After going to safe mode, uninstalling xposed, even calling Verizon to reset my connection with them, nothing worked… until I reflashed the v15 zip. I’ve been going strong for about a month now without any problems.
Click to expand...
Click to collapse
So I'm in a similar boat, but my sms/calling issues have returned after about a day of flashing the v15 zip. So far I've probably reflashed it like 5 times in the last 5 days. It works without fail so far, but this is not a permanent solution. Could it be some setting configuration? Any feedback is appreciated.

elan5 said:
So I'm in a similar boat, but my sms/calling issues have returned after about a day of flashing the v15 zip. So far I've probably reflashed it like 5 times in the last 5 days. It works without fail so far, but this is not a permanent solution. Could it be some setting configuration? Any feedback is appreciated.
Click to expand...
Click to collapse
What build are you on?

Related

[q] stuck in bootloop sprint ls980 please help!!!!

OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Sshaffer1992 said:
OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Click to expand...
Click to collapse
god that is really hard to read...did you make a back up before you do installation? if so do a restore, if you dint, download another rom, kernel, put it in your phone, wipe everything except internal storage via TWRP then flash rom then kernel.
G1_enthusiast said:
god that is really hard to read...did you make a back up before you do installation? if so do a restore, if you dint, download another rom, kernel, put it in your phone, wipe everything except internal storage via TWRP then flash rom then kernel.
Click to expand...
Click to collapse
lol sorry i wanted to be as pacific as possible. I did make a backup before flashing the rom. when i tried to go back to it i had the same problem with it rebooting after a few mins. i tried flashing furnace 0.0.8 kernel after installing a fresh rom but same problem. I am back on factory recovery atm is there anyway to flash twrp back to the phone without it being rooted? i tried to get the computer to communicate with the phone when it turns on but it wont seem to connect unless im in download mode or recovery.
Sshaffer1992 said:
lol sorry i wanted to be as pacific as possible. I did make a backup before flashing the rom. when i tried to go back to it i had the same problem with it rebooting after a few mins. i tried flashing furnace 0.0.8 kernel after installing a fresh rom but same problem. I am back on factory recovery atm is there anyway to flash twrp back to the phone without it being rooted? i tried to get the computer to communicate with the phone when it turns on but it wont seem to connect unless im in download mode or recovery.
Click to expand...
Click to collapse
so the phone turn on? try enable debugging in developer option, sometimes that works for me, not sure why.
Solution?
Sshaffer1992 said:
OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Click to expand...
Click to collapse
I had the same problem except with me, i was just trying to change fonts manually. It went into a bootloop and i stressed dover it for hours until finally i found out that you have to use the lg mobile support tool (you can find it in one of these threads on the lg g2) and revert it back to stock. That fixed it perfectly fine. Its a lengthy process but simple. If that doesn't work you have to do what the lg mobile support tool does semi-manually with another program lg flash tool which is longer but just as simple if you follow the directions given in the thread to the letter.
androidfantic32 said:
I had the same problem except with me, i was just trying to change fonts manually. It went into a bootloop and i stressed dover it for hours until finally i found out that you have to use the lg mobile support tool (you can find it in one of these threads on the lg g2) and revert it back to stock. That fixed it perfectly fine. Its a lengthy process but simple. If that doesn't work you have to do what the lg mobile support tool does semi-manually with another program lg flash tool which is longer but just as simple if you follow the directions given in the thread to the letter.
Click to expand...
Click to collapse
I tried the lg flash tool and it put my phone back to stock but still have the same problem. I also tried lg mobile support tool but it will not recongize my phone. I did happen to get into settings and seen that both my imei and baseband are unknown. Could this be causeing the proble m? is there any way to fix it?
G1_enthusiast said:
so the phone turn on? try enable debugging in developer option, sometimes that works for me, not sure why.
Click to expand...
Click to collapse
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Sshaffer1992 said:
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Click to expand...
Click to collapse
**** thats not good at all. This happen when I was using my S3, if IMEI is gone then you could not use the phone at all, theres no way you can get it back unless you made a back up. you have to sent it in man, sorry this is as good as hard brick.
G1_enthusiast said:
**** thats not good at all. This happen when I was using my S3, if IMEI is gone then you could not use the phone at all, theres no way you can get it back unless you made a back up. you have to sent it in man, sorry this is as good as hard brick.
Click to expand...
Click to collapse
My friend also has a lg g2 that i rooted for him would i be able to use a backup from his phone. Also when i turn the phone conpletely off and hold down all 3 bottons it brings me to a hardware key settings it does shows my imei number there. If i sent it into lg would they know the phone was once rooted or does the back to stock method cover it up? Thanks for your help btw
Sshaffer1992 said:
My friend also has a lg g2 that i rooted for him would i be able to use a backup from his phone. Also when i turn the phone conpletely off and hold down all 3 bottons it brings me to a hardware key settings it does shows my imei number there. If i sent it into lg would they know the phone was once rooted or does the back to stock method cover it up? Thanks for your help btw
Click to expand...
Click to collapse
they have coders there, I'm sure if they really want to know they can figure it out. If you send it in to get it fix out of your own pockets (meaning you pay them) then i'm sure they dont care, but if you want a replacement due to warranty then it may be a different story.
Sshaffer1992 said:
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Click to expand...
Click to collapse
That suck bro I'm facing the same issue right now hope you got it repaired if so feel free to share the process lol
Nba2kgod said:
That suck bro I'm facing the same issue right now hope you got it repaired if so feel free to share the process lol
Click to expand...
Click to collapse
I eneded up restoreing my phone back to stock and took it into my local sprint store it cost ne 75 dollars to replace the phone not under warranty (if u have sprint protection its free) i told them i took and ota update and it started rebooting itself. If you do get a replacement make sure u back up your efs files to a safe place on your phone. Theses files can become corrupted by flashing roms and kernals.
Sshaffer1992 said:
I eneded up restoreing my phone back to stock and took it into my local sprint store it cost ne 75 dollars to replace the phone not under warranty (if u have sprint protection its free) i told them i took and ota update and it started rebooting itself. If you do get a replacement make sure u back up your efs files to a safe place on your phone. Theses files can become corrupted by flashing roms and kernals.
Click to expand...
Click to collapse
Not under warranty? Doesn't it have a 1 year manufacturer warranty? The G2 wasn't released on Sprint until November last year so it should have been covered.
Sent from my LG-LS980 using Tapatalk
Yes its still under manufacturer warranty but when i made a repair order with lg it said it would take 2 to 3 weeks to get my phone back and if they found out it was due to being rooted and flashing roms im sure lg would of charged a arm a leg to repair it. With sprint i got a new phone in 2 days or ordering it.

Huge problem S4 not working anymore..

So this is my sad story..
I bought a second hand Samsung S4 (i337M Telcel) Unlocked, the day i got it, i tested in front of the seller everything was nice and smooth.. So i payed..
I was very excited and i proceed to make the Root proccess, at beginning i was having issues with the drivers and Odin, then i was able to fix it..
Anyways long story short i ended up with the ROOT, CYANOGENMOD CM11, and PHILZ 6.. The first day was working fine my cellphone.. (I must say i rooted in my life at least 4 devices even an S4 i9500 all of then with success and not a single problem.. Using them form months and even gears.. The latest was a Moto E..)
Ok so the i337M was working good since the first morning with the root, but in the afternoon it just turned off one time.. Was weird but i didnt pay much atention..
The second day i was listening music and suddenly it turned off, and since then the cellphone is not able to keep on for more than 10min..
Some times i can load the complete OS and ofter 2 min it turn off sometimes at the Samsung S4 logo turn off something i must say is that the Device every single time i turn it on, on the Samsung S4 screen says "kernel is not seandroid enforcing" in red letters, some people say it happens when the root process is not made correctly some says it normal because its rooted..
I already installed from Odin the Stock ROM from SamMobile, and the problem is exactly the same.. A friend of mine told me it could be the Logic Card AKA Motherboard.. But i want to believe its just a software problem.. Cuz' before i rooted cellphone was working..
- Download mode: Works like a charm not a single problem and basically its the only way i keep trying different options to install on the phone..
- Discovery mode: With CWM sometimes works good, sometimes it just turn off, with Philz runs good not turning off or something and its how i was able to wipe data, cache, dalvik, factory reset to the cellphone..
Im thinking in starting over like pretending i didnt do anything to the cellphone, try again the root, the rom, the PHILZ (dont know how to call it).. and hope for the best..
Any advice or reliable links where i can download the correct files for my S4 i337M.. You are basically the last reliable source i have to fix my S4 if you give up with me, then i must admit my cellphone has passed away ..
Hope you can help me thanks in advance and have an excellent day!!:laugh::good:
The first troubleshooting step (to determine if the issue is hardware or firmware related) is to flash back to stock with Odin. Since you have completed this step and find that the problem is still present, this suggests that it is a hardware problem.
I have seen a custom kernel cause sleep of death, which makes the phone appear to have turned off. But in those cases, flashing the stock kernel fixed the problem.
Perhaps you should see if you can return the phone to the seller for a full refund.
creepyncrawly said:
The first troubleshooting step (to determine if the issue is hardware or firmware related) is to flash back to stock with Odin. Since you have completed this step and find that the problem is still present, this suggests that it is a hardware problem.
I have seen a custom kernel cause sleep of death, which makes the phone appear to have turned off. But in those cases, flashing the stock kernel fixed the problem.
Perhaps you should see if you can return the phone to the seller for a full refund.
Click to expand...
Click to collapse
Thanks for your reply.. I still dont know how but with Philz recovery, i was able to make a full wipe, i mean it deletes everything every single folder previously made was erased, and i can tell you that because i have a folder called ROOM where i places my ROM, Kernel, etc.. So i can flash them in discovery..
So i erased everything and then proceeded to install via Odin the Stock Rom and guess what it works like a charm, not a single problem.. So, so far the cellphone is ok.. I tested for two hrs.. Now i tried to install a custom ROM and its doesnt load from the Samsung S4 screen jaja... But im still having acces to discovery and download mode so thats ok..
Just two advices.. Never ever download files from Youtube ****y links.. Always go to the source.. Youtubers are assholes.. Real help and information comes from real people that knows what they are talking about like this forum and also updated and real ROM's come from the main source not Mega o Linkbucks...
Other advice embrace your self to do it.. Study every single question you have in Android, from KERNEL to ROM and ROOT.. Isn't that difficult..
One more question, Which ROM with Lollipop would you suggest to install i have the i337M?
SUNDR1V3R said:
So i erased everything and then proceeded to install via Odin the Stock Rom and guess what it works like a charm, not a single problem.. So, so far the cellphone is ok.. I tested for two hrs.. Now i tried to install a custom ROM and its doesnt load from the Samsung S4 screen jaja... But im still having acces to discovery and download mode so thats ok..]
Click to expand...
Click to collapse
May I make a suggestion? Now that you have the phone working, can you possibly just use it for a week without doing anything to it? Don't try to root it or do anything other than text, make phone calls, and install a few programs. This will establish a baseline of behavior for your device, so you'll be able to tell when its behavior is out of the ordinary.
I understand your desire to make it your own. I got my S4 brand new from AT&T and said that I would wait at least a month before rooting it or changing roms, in case there was a problem and needed to return it. I had good intentions, but I couldn't stand it anymore and rooted it after only 3 days! It will take a lot of patience, but you really need to use it for more than a few hours to make sure that the hardware is okay.
I agree take baby steps, week stock, week root, week recovery. Figure out if its hardware or one of the steps is causing it.

[Q] Reboots after Lollipop

Verizon Note 3 here, I received the Lollipop ota today and thought no harm in taking it as I was already stuck without root on 4.4.4.
It worked ok for the first couple minutes, then a reboot, then same thing, about 5 minutes and a reboot. Sometimes ~2 minutes, seems using it in any situation made the reboots happen. I did a factory reset thinking that would clear things up. Unfortunately now it is even worse, as it's rebooting anywhere from the first touch to the screen, to about 15 seconds of activity, literally dozens of reboots.
I downloaded the update on my pc and installed via Odin hoping that the ota was just corrupted or some bad luck like that. Nothing changed at all.
It will idle after booting just fine, I just can't do much of anything, every touch of the screen feels like a roll of the dice. Every few reboots or so I can make it to settings maybe but haven't been able to actually change much of anything, not that it would seem to matter here.
I've flashed via Odin twice, cleared the cashe many times, factory reset 3 or 4 times. Am I screwed here? What else to try?
*UPDATE* I flashed back to 4.4.4 with Odin and no more issues. It appears that my device alone is completely incompatible with the new firmware.
I should also note that I tried airplane mode, safe mode, and removing the sd card with no improvements.
After hours of messing with this thing and nearly giving up, not half an hour after I post here for help, I seem to have found a solution, although hopefully not a permanent one. The problem was happening when I would touch the screen, not scrolling ever, but making selections. On a whim I turned off sound and bam, no crashes.
I would still love it if someone had some insight about this problem, or better yet a solution.
I'm not sure yet if it is just the keypress sound that is killing it, or all sounds. I never did have any issues with the stock keyboard clicks now that I think of it, only the menu press sound. In any case it's not every time it made the sound, just half the time or so. Anything anybody could add to this would be appreciated.
*Edit* Not a solution, but it did help.
Well it's not as stable as I'd hoped. More like before the first factory reset now, but still not good at all. The various sounds definitely trigger crashes quickly(menu options, volume pings, mp3 songs from sd card), but regular silenced menu presses do sometimes as well still. Phone also bootloops several times often before it can get booted stable and 100% always crashes immediately if I try to unlock the screen in the first 5-10 seconds after booting up. Not sure if I'll be able to call or text as it's too late to test that atm. I'll update tomorrow, any insight appreciated.
I would say a bad download but I don't remember if ODIN checks MD5 sums (pretty sure it does). I would do a full wipe and reflash the stock image with odin
I am 100% stock not rooted never been rooted 5.0 vzw and I have had a couple of reboots. Never ever had one on this phone before. My old note 3 was rooted but I got this replacement after the root exploits had all been closed.
ehh not all have been closed
What is the root exploit for Verizon Note 3 with 5.0?
recDNA said:
What is the root exploit for Verizon Note 3 with 5.0?
Click to expand...
Click to collapse
None at the current time but CVE-2014-8609 seems like it could be some use
I spoke too soon when I said the phone was usable now. At best 5 minutes of light use as anything seems to crash it now. I did get a fresh image and used it with Odin with exactly the same result which makes me think its my phones hardware or something. Just seems crazy that it was working just fine before the update. The reason I pushed to 4.4.4 and lost root is because my phone suddenly started an issue where it would crash when making or receiving calls. It wasn't caused by any new apps or anything, just out of nowhere. I tried everything then updated as a last resort, carelessly I went to 4.4.4 instead of staying at 4.4.2 and lost chance of root, but it solved the problem I was having. I wonder if the issue is related somehow.
I was able to odin back to 4.4.4 and it's working fine so far, I assumed that you would not be able to revert back like the last ota and just tried it as a nothing to lose last effort. This is very important news to anybody that is having major issues with 5.0. Maybe, just maybe I'll try it again if they make an update patch for reported issues.
But for now, 4.4.4 it is for me.
VZW Note 3 update to Lollipop
I just finished the Lollipop update and my phone is working great for the past 30 minutes. Seems a little slower then usual but have had no issues besides my phone locking up after downloading the update, may have been due to my phone running down to 14%, but after removing the battery for 20 secs and putting it back on, phone came back on, I plugged into charger and started the update. Will post later if I have any issues.
I have been trying unsuccessfully through odin to downgrade but it keeps failing in odin, I downloaded the official firmware from sammobile.
Just curious if u r tried reinstalling newer odin? Try different USB port and cable. At this point maybe even try different pc if u have access to 1

Phone not connecting data

Hey everyone, let me start off that I love XDA and I have been using this site for years! So let me give you a little history. I am still on 4.4.4. Recently I finally updated it to 5.0 and retained root, sweet! I also had a custom lollipop recovery that allowed me to go back to 4.4.x. However, I needed the wireless tether function and I could not find a way to get it unlocked without flashing some mod (which would brick my phone) so I used ODIN to flash back to a rootable tar image that I have always used. It was 4.4.2 on NI2 Kernal. Now normally, no matter how many times I ODIN'ed it, flashed it, restore a backup, everything would be up and running in no time. However, lately my phone has not been able to connect to the network completely for some reason. I can make/receive calls and texts. Anything using data though would not work. I called Verizon to see if they could reset something from the back end and they saw me and connected and running. Needless to say, their help ended almost immediately. I am currently running Ricks ROM v19.2 G900VVRU1ANI2 and was only able to connect to data one time a couple of days ago. I had to restart though and when it booted back up, it lost the data again. It does show that I am connected to 4G LTE, strong signal. I have tried the stock ROM 4.4.2, fresh install of Ricks ROM, restore my backup of Ricks Rom (maybe two weeks old), tried Eclipse ROM, nothing seems to be working. I've never submitted anything on here asking for help so this is a first for me cause normally I can fix any problems I create, however, I cannot figure this out for the life of me. Does anyone have any suggestions that I can try? Thanks in advance!
Nic

N910F stock crash and bootloop after 6.0.1 update

Hello people of the world,
after reading a lot of posts here I still can't fix my phone's issues, so I need to post. Bear with me...
I have an N910F which was entirely stock and functioning without problems. Two days ago I accepted the official update. After that, the phone regularly lost connection to the mobile net, froze, and restarted. It would work for a short while until it froze and restarted again and again. When I tried to use the camera, the live picture was completely distorted. The phone crashed and has then gone into a bootloop.
I pulled the battery, did a recovery start and wiped the cache. No difference. Factory recovery next, no difference.
I have since tried several stock and custom firmwares, always taking care to follow instructions and use the correct bootloaders, modems, etc. TWRP is working.
When I flash a stock firmware, it will go into a bootloop. With any custom ROM, it will crash during startup (logo) and switch off.
Any help would be greatly appreciated!
Protect the eMMC?
So, after more reading I began to suspect that the eMMC had moved on to the valhalla of electronics. Sent my phone to service where my suspicion was confirmed. Luckily, they were able to replace the chip without having to put in a new board.
Is there any way to prevent this kind of failure again, or at least make it less likely?
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
nicholes said:
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
Click to expand...
Click to collapse
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
tullian said:
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
Click to expand...
Click to collapse
installing power wakelock and setting up on partial wake lock is enough.if you get trouble in starting your phone remove its battery and put your phone in refrigerator for five min.and try to start your phone.this problem also related and happens after the latest update

Categories

Resources