Help - No data on Verizon network using stock image - Nexus 6 Q&A, Help & Troubleshooting

Ver 5.0.1
Baseband MDM9625_104335.118.02.55.04R
Kernel 3.10.40
Build LRX22C
All stock
Received phone today, popped in SIM no issues at all.
Performed the following steps.
1-Decrypted phone (unlock bootloader)
2-Root
3-Flash TWRP
4-Flash lean kernel
After these steps no issue with data. Everything working.
5-Started installing apps/configuring phone. Restarted phone several times during this process. Noticed after restarts that LTE wouldn't come up. Toggled airplane mode to fix. Eventually no service after restarts.
Re-flashed stock image, no root, no custom recovery, stock kernel. No service at all. Confirmed that SIM still works in different device.
I am aware that some N6 custom ROMs have data issues with Verizon. I had not seen anything reported with the stock image.
Has anyone experienced this?
Any help is greatly appreciated.
Thanks.

Related

Fix 'No SMS sending' problem when installing official CM ROM

A friend got the Motorola Droid 4 (maserati) and gave it to me to install a custom ROM on it, to get rid of the bloat on stock.
I installed the latest stable CyanogenMod on it (cm-10.2.1), but then the phone would not send any SMS, it did received them though.
I tried this guide but it didn't work (the SIM card did work in other phones). I then proceeded to install a snapshot version of CyanogenMod (cm-11-20140708-SNAPSHOT-M8) and followed this guide, that didn't help either.
When I finally gave up, I went back to stock and the SMS sending problem was fixed, but now a new problem came up with the cellular and the WiFi signals being very low and sometimes nonexistent.
Then I found this thread and did the following:
- Rooted and installed custom recovery using @mattlgroff's DROID 4 Utility XT894 Jellybean guide.
- Went into custom recovery and did factory reset.
- WITHOUT EXITING CUSTOM RECOVERY, I installed the latest CM again.
- Again, WITHOUT EXITING CUSTOM RECOVERY , I installed @Mentor.37's Patch to fully enable GSM on Verizon CDMA Android phones patch.
- Success!
SMS sending works now on other ROM besides stock and the low signals on cellular and WiFi, got fixed too.

[Q] Phone rooted but stuck on bootloop

Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.
cowboyv said:
Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.
Click to expand...
Click to collapse
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.
Revontheus said:
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.
Click to expand...
Click to collapse
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?
cowboyv said:
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?
Click to expand...
Click to collapse
You can always download GAPPS manually, and flash it via Recovery if you think the Google Play Services that comes with your FW is bugged

touch-screen freezes at lock screen

hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( https://www.youtube.com/watch?v=epcXXkMPRWk ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
It's possibly a corrupt backup file. I would use TWRP to flash the stock ROM & see what happens.
i assumed re-rooting would clean everything since it uses the send-command program (essentially dd's the whole disk) but i guess not.
we also tried installing the rooted stock rom using twrp but still no joy.
Re-rooting doesn't do anything to the rom or drivers unless you're doing the easy root using a system img file. Then you're pretty much replacing your rom with one that has superuser already on it. That being said, did you upgrade to the 10n firmware/bootstack? The easy root is for 10h firmware/bootstack so that could be the source of your issues.
schneidz said:
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
Click to expand...
Click to collapse
I relatively had the same problem where I flashed CM and did not like it because it was buggy and so I restored an nandroid and the once working nandroid was plagued with errors of the touchscreen not working, the phone would freeze, system crashes... It ended up being caused by the fact that I did not flash the 10N bootstack update before hand. After I flashed the new firmware and then flashed CM; all of CM's bugs disappeared. I haven't gone back to stock LG software since CM works flawlessly and is now my dailydriver so I cant say for sure if it will fix the stock rom but It probably will since it cleared up all my bugs like the camera not working, videos now playing...
btw to get data working in CM go to settings/mobile networks/Access point Names/ then scroll down and click "T-Mobile US LTE IPv6" and that should fix the internet issues you have since it fixed it for me.
they didnt do anything with the 10n bootstack (i dont know what that is).
maybe cyanogenmod automatically does the 10n thing (how to manually go back to 10h) ?
i assumed re-loading the 5 gb .img file would bring us back to square-1 but i guess not.
also, how to know what bootstack they are running. i told them to check about fone but they told me nothing in there mentions 10n or 10h.
About phone > Software Info > software version will will say h81110n if on 10n.
Same here on Stock...
I have this running stock H81110n software, which I flashed using a KDZ. However, it only freezes up occasionally, and turning the screen on and off once or twice always gets rid of the problem. It's not bad enough for me yet to warrant any factory resets or tweaking so far, but the problem is there...

If i install the nexus 6 factory zip can i easily flash TWRP?

I am being plagued by wifi issues ever since i went to a new version of Purenexus. It seems to have something to do with going to 7.1.1
I've tried the older version of the rom that was working fine before, but i still seem to have wifi issues even in these older versions now.
i tried resurection remix, but still have the same issue.
after a while the wifi wont be connected and it says authentication problem, or sometimes shows it as simply discconected.
i can manually forget the network and re add it and it seems to work fine for a while.
Durring troubleshooting today, i have tried to resey my router, even upgraded the firmware,
anyways, i'd like to flash the factory image to test to see if i still have issues. but i want to make sure that if i install 7.1.1 factory image, or 7.0 that i can still re-flash twrp from adb or am i going to have to find a root exploit?
if i flash a factory image does it "relock" my bootloader? i guess that is the more important question
thanks.
citrusfizz said:
I am being plagued by wifi issues ever since i went to a new version of Purenexus. It seems to have something to do with going to 7.1.1
I've tried the older version of the rom that was working fine before, but i still seem to have wifi issues even in these older versions now.
i tried resurection remix, but still have the same issue.
after a while the wifi wont be connected and it says authentication problem, or sometimes shows it as simply discconected.
i can manually forget the network and re add it and it seems to work fine for a while.
Durring troubleshooting today, i have tried to resey my router, even upgraded the firmware,
anyways, i'd like to flash the factory image to test to see if i still have issues. but i want to make sure that if i install 7.1.1 factory image, or 7.0 that i can still re-flash twrp from adb or am i going to have to find a root exploit?
if i flash a factory image does it "relock" my bootloader? i guess that is the more important question
thanks.
Click to expand...
Click to collapse
There will be no locking of the bootloader unless you issue the command. No exploits needed. Just flash away...

No network connection on my Note 4. Please Help!

So I noticed that I lost my network connection randomly. I didn't download anything recently other than a few icon packs and I don't think I updated any apps or anything like that. I was on Aurora Full Note7 rom for many months with no significant issues until I noticed this yesterday. I've tried 2 other roms since, one being the 6.0.1 Stock Rooted Odex with clean installs on both and the issue still persist, but when I boot into safe mode the issue goes away and I have network connection again. I never had this issue before, so I don't know how to track this down and what needs to be deleted. Recovery is TWRP v2.8.7.0. Please help!
HalfmanHalfamazing said:
So I noticed that I lost my network connection randomly. I didn't download anything recently other than a few icon packs and I don't think I updated any apps or anything like that. I was on Aurora Full Note7 rom for many months with no significant issues until I noticed this yesterday. I've tried 2 other roms since, one being the 6.0.1 Stock Rooted Odex with clean installs on both and the issue still persist, but when I boot into safe mode the issue goes away and I have network connection again. I never had this issue before, so I don't know how to track this down and what needs to be deleted. Recovery is TWRP v2.8.7.0. Please help!
Click to expand...
Click to collapse
Try stock firmware via odin.
Trex888 said:
Try stock firmware via odin.
Click to expand...
Click to collapse
Didn't work. I have a OPO as well and it dosen't have this issue. Idk what else to try.

Categories

Resources