So yesterday I rooted my Sprint Note 4 and everything went well. I then went and got TWRP as well and when done, I got CM12.2 with the appropriate G Apps and flashed both correctly as well. When CM12.2 booted up, it was a little glitchy at first but then it smoothed out and was an amazing experience until this morning. I loved this, but I didnt know it would do this too me. So I woke up this morning and the service wasnt working. It said sprint, but nothing was happening, couldnt recieve texts or anything. Then it just showed an X next to my bars with zero bars lit up, of course. I had zero service. So I then went into twrp, factory wiped and restored a backup I had done before I flashed all this. STILL, on boot up and setup, a big red x next to my zero service bars! Can someone please help me asap? Would removing the root and completely factory reseting the phone from a computer remove it? (Going to do it anyway). HELP?
Related
Hey Guys, I have been beating my head against a brick wall trying to fix my phone.
Yesterday I was on a call with someone and suddenly I lost service (not uncommon for where I was since I have weak service there), but this time the phone was frozen. The dialer screen was on but was frozen. My phone would not react to anything. So naturally I pulled the battery and rebooted the phone. The phone started up as normally it would but then after 5 minutes of the phone running it froze again. During those five minutes I never received any cell signal.
The most recent "work" I had done on my phone was change the kernel to the AK Kernel on the guide here. This was done 3 days before anything started happening. I tried a new kernel because ever since upgrading to Paranoid 3.0 my phone was acting slow and occasionally I would get a screen of death typically about once a day. The 3 days that I had the new kernel, everything was working great (phone was faster, responsive and no SOD).
I tried restoring a nandroid before upgrading the kernel and it made no difference. Ever since the first time my phone down freezes after 3-5 mins after booting up. Nothing that I have tried has fixed the issue.
I have done a clean install, tried locking and re-rooting, tried a different kernel. All to no avail. Please help I am thinking there is something seriously wrong and may need to take it back to verizon. I am trying to restore my device to stock but am unable to do so. I have been using this guide: Restore to Stock. Any suggestions to make it "clean" enough to get verizon to replace it?
I'm going through withdrawals, please help!
Could not fix it, so I contacted tech support and explained everything that I did to try to fix and they just sent me a warranty replacement. I hope that it was a device error and not something that was caused by other ROMs or Kernels.
Recently, my rooted phone ( I was on clockworkmod recovery and stock rom) became rather volatile and would randomly reboot and get stuck in a bootloop. This lasted about a day and then the phone stabilized on its own and eventually returned to normal. Once it returned, the cell service was spotty and 4G was gone, i only had the occasional E in the top right corner.
This progressively worsened into me having no cell service, however I did not have the circle with the line through it. I had full signal bars all while this was happening.
I decided to unroot my phone and return to stock everything , hoping this would solve the issue. Still nothing.
I did a factory wipe and still nothing. Very rarely ill be able to sneak a text message or two before everything stops working again.
Anyone encounter anything like this before? .
Got a Note 3 last November, everything ran great, a few weeks ago the phone would show full signal with 4g LTE icon and everything but it cant make/receive call/text. No data whatsoever.
Airplane mode does not toggle it just grey out after activation. When trying to make a call it wouldn't go through and the call just get stuck, hitting the end button doesn't do anything. Everything is back to normal after a reboot, but the same thing would happen again every 2-3 days and would require another reboot.
CSR tried to resetting things on their end but that didn't fix it, got a new SIM, a replacement phone from Tmobile it does the same thing but less frequent.
Anyone else experience this? I'm about to get another replacement . Running latest T-mobile firmware/baseband no root/mods.
bobafuzz said:
Got a Note 3 last November, everything ran great, a few weeks ago the phone would show full signal with 4g LTE icon and everything but it cant make/receive call/text. No data whatsoever.
Airplane mode does not toggle it just grey out after activation. When trying to make a call it wouldn't go through and the call just get stuck, hitting the end button doesn't do anything. Everything is back to normal after a reboot, but the same thing would happen again every 2-3 days and would require another reboot.
CSR tried to resetting things on their end but that didn't fix it, got a new SIM, a replacement phone from Tmobile it does the same thing but less frequent.
Anyone else experience this? I'm about to get another replacement . Running latest T-mobile firmware/baseband no root/mods.
Click to expand...
Click to collapse
Are you running pure stock?
Pure stock, just got a replacement and the same thing happened again.
bobafuzz said:
Pure stock, just got a replacement and the same thing happened again.
Click to expand...
Click to collapse
I also got a Note 3 just 2 weeks ago. Same thing happened to my phone and I thought it was ROM that I had flashed. It has gone away but I am still wondering what was causing such symptoms.
I would see LTE but when I try to make calls there is no sound, not even rining and it would never go though. Someone would call me and my phone would not ring. Same with data, when all others get instant messages in a group chat, my note 3 would be the only one not receiving any messages.
It would stay this way until reboot. When the phone restarts then everything is back to normal. This was very very annoying because you would never know when your connection is lost.
Did you have to reboot to get it back?
bobafuzz said:
Did you have to reboot to get it back?
Click to expand...
Click to collapse
Yeah I had to reboot every time it did have those symptoms.
As the title says I am currently only getting LTE signal on initial boot and it shows its registered to tmobile on the top left but after about a minute I get no signal at all just an X on where the signal bar would be. I checked the signal on boot and it is -119dm 21asu then drops to -113dm and 0asu.
Let me start with all I did since last night. I have been planing on upgrading from kitkat to lolipop and finally started taking steps to do that last night. I first used Kies 3 to backup my data then decided maybe its best to do a full nandroid as well. I installed TWRP and did a full backup, played with my phone a bit then wound up falling asleep without finishing. This morning I knocked the phone off my dresser with the charger still attached and nothing appeared wrong with it. It wasn't until I was driving to work trying to load up spotify that I noticed I was getting no signal. I rebooted when I got to work but did not watch the whole boot up process and only saw that I was still getting no signal. On my lunch break I decided that maybe I screwed something up when I flashed TWRP with odin 3.10 and followed this guide to get started with the upgrade (http://forum.xda-developers.com/not...icial-lollipop-n900tuvufob5-t-mobile-t3046295). Note that I already had mobile odin installed on my phone. When I finished up and everything looks good but I still dont have signal. I noticed that the baseband was still showing up as the kitkat baseband so I flashed the lolipop modem with odin and after boot saw that it did indeed upgrade the baseband but still no signal.
I should also mention a week ago I replaced the usb3.0 port on my phone because the old one was a bit loose when plugged in. I had not had any issues with it until I noticed no signal this morning and am at a loss as to what my problem could be. I did remove the back and check the antenna connections once I got home but it does not fix the issue. Wifi still works and wifi calling appears to work as well. Issue seems to be with just the cellular part. Hoping some one here can pick up on what I possibly messed up.
Was a software issue
I got it working. Looks like there was a software conflict with an app or apps possibly because I did a factory reset and re flashed in Odin using this guide (http://forum.xda-developers.com/showthread.php?t=2672393) and my cellular signal is back to normal. I had to start fresh but at least I have a usable phone now. Hope this helps anyone in a similar situation.
Hey guys, I've been having a really weird issue for a couple of days now. For your better understanding I'll list the things that I did with my d855 (Including some stupid ones)
1. I was on a cm 13 nightly rom, I was getting pretty bored so I decided to try out the fulmics 4.2 . So, I did. I flashed it without any hiccups. Everything seemed to be going fairly well. (I did make a TWRP backup and i also checked md5 of the zip file. It matched out)
2. I installed all of my apps that i use, Set up my wallpapers, nova, etc. I used it for a whole day and i noticed that the sot improved quite a bit from cm 13.
3. I'm in my bed, obviously not sleeping, you know how we do. And an incredibly stupid idea came to my mind. I thought "Hey! It's 4'o clock in the morning and i have school tomorrow, BUT WHO GIVES TWO ****S?! why not try out the lg g4 camera app ?!? Now, I had tried it before a long time ago, The camera didn't work, But the phone definitely did. So I wasn't paying too much attention on what the thread said about which version of android it was for. And just like a complete moron i downloaded the thing and proceeded to place the apk and 'libs' folder on my phone. I did give them proper permissions.
4. After that I went ahead and rebooted my phone. It booted just fine. I tapped on the camera app and it gave me an error. So i rebooted again, same as last time it booted up just fine but the camera didnt seem to work. Then suddenly it just shut down and then the lg logo flashed. It booted to the homescreen just fine. Then it turned off again and rebooted again. This loop started to go on and on forever.
5. So I decided to boot into twrp and wipe my art/dalvik cache and normal cache. Then i pressed on reboot. This time the phone didnt turn off, it optimized all of my apps. It took a while but i was on my homescreen and it didnt turn off. So I went ahead and opened up root explorer, located to where i pasted the camera, deleted the libs folder and the apk and also renamed my original camera app from .bak to .apk . Then I rebooted again, and it started the weird looping thing once again.
6. I realized that it boots up just fine if it's plugged in. But it seemed to turn off after 5 mins or so even when plugged in. I thought I messed up my rom or something so i decided to check by entering into recovery. But the result was the same. It just turns off. So since it was turning off even when i was in recovery i thought it was a faulty battery.
7. So i busted out my ZTE pocket wifi router and proceeded to take its battery and hold it up against my d855's battery pins with my finger. (Probably not safe) And the phone seemed to work just fine. I could use it for days without any issues. So at that point im like 110 percent sure its a faulty battery. Fair enough.
8. But, just to be certain i thought lets try doing a factory reset and flash the fullmics again. Result = Wank.
Then I wiped the cache again. Result = Wank. Then i decided to restore to the backup i made earlier that day. Result = An oreo to be given to the one with the correct guess.
9. At this point i wasn't 110 percent sure that it was a faulty battery. I KNEW it was a faulty battery. I was feeling it in my left testicle. So I decide to finally sleep cuz you know, gotta get some sleep, got a big day ahead of me tomorrow. Cuz I dont have my phone. So, I prepare myself and go to sleep.
10. The next day I decide to give it one last shot. I was thinking about wiping it clean and restoring to the backup again.
11. This is where the interesting thing happens. Bear in mind, I am NOT plugged in. Im on my G3's battery. I hold down the volume down and power button. The lg logo shows up. I let go of the buttons. I press them again. The white factory reset screen shows up. Now, I left my phone on that screen for legit 20 mins ladies and gentlemen and it didnt turn off once. But as soon as i click yes for twrp to launch the phone turns off before the twrp logo can show up. I tried the same thing with the ZTE battery as well, and it worked just fine. Only this time it actually booted to twrp. And it booted into the system as well.
Now, wtf is this? Wouldn't the phone turn off in the factory reset screen if it was faulty? And if the battery isn't faulty, then why does it work with a different battery but not with the lg one?
Now, My question to you guys, WHAT SORCERY IS THIS?
Help me out people. Expert help needed. TIA
*sigh*
It's a faulty battery mate. The phone stayed in the factory reset screen because the battery usage was basically insignificant. When you tried to go to recovery mode, the phone used more battery and boom, dead phone Happened to me too, new battery solved it.