Nexus 9 searching for wifi networks - Nexus 9 Q&A, Help & Troubleshooting

I have a Nexus 9 WiFi. I recently tried installing various custom ROMs but for each one the wifi wouldn't work correctly. It would always just stay "searching for wifi networks". For each of the ROM installs I would wipe all device partitions and then attempt the install using TWRP (3.1.0.0). I've attempted:
SlimRom flounder 6.0.1 2.1,
SlimRom flounder 6.0.1.1.18
SlimRom flounder 7.1.1 0.18.
cm13.0-20161218-nightly
cm14.0 20160910
Each had he same behavior, install went okay, went through setup but wi-fi never got past searching. I could specify one of my own networks SSIDs manually but with no luck. Wondering if perhaps wifi just happened to get hosed while doing all this, I flashed a stock image (volantis-ota-mob30d-1da7c803) and using this I was able to setup and connect to wifi so I know it's not the hardware. I was able to stay connected from various other devices at home with no issues. So it would seem to be an issue with using a custom ROM. With each of the custom installs I was able to turn WiFi on and a Mac address was listed, just didn't get beyond the "searching" step.
I've done searches on this and other forums and see issues with not being able to turn wifi on or connecting but getting dropped but I've not found a thread that has a fix for the device just searching.
Update: I wanted to also add that I've tried booting into safe mode with no effect.
Thanks in advance for any help you might be able to provide.

I'd reboot the router then see what happens.
Sent from my Nexus 9 using XDA-Developers Legacy app

jd1639 said:
I'd reboot the router then see what happens.
Click to expand...
Click to collapse
I've rebooted the router to no effect. There are also several other routers in my neighborhood that will shows up on my other devices but not the Nexus 9. I also don't think it's a router issue because flashed a stock rom back and the Wifi worked again which leads me to a software issue.
Thanks for the reply though. Keep 'em coming.

Fixed wifi with vendor.img
Got it fixed. I'd wiped everything in my various ROM flashes and after some more research found that I needed to reflash the vendor.img.
I downloaded the most recent image from google (developers.google.com/android/images).
I then unzipped that zip file, which contained several items in it.
In that group were a few other files, one of them another zip (image-volantis-n4f26x.zip), which I unzipped
This contained a vendor.img file
I copied that file over to the tablet and booted in TWRP
From TWRP I installed the image. It gave me a few target locations and Vendor was one, which I selected. I then cleared cache and dalvik
Once I booted up I was presented with a message about my vendor image not matching (or something to that effect) but my Wifi was now listing networks and able to connect
To get ride of the matching vendor image message, I booted back into TWRP and installed a zip I had downloaded at some point in the past for this (vendor-build-prop-fix-signed.zip)
Once I rebooted the message was no longer present and the wifi worked.
Hope this helps someone down the line.

Related

[Q] [solved - it wasn't kernel/libs!] Wifi 'Unable to scan for networks'

So I've been on Ineffabilis since just about New Year's. 1.0, and on through 1.3 now.
Wifi Tether has always worked.
I use stock Kernels - always.
I recently got on Ineffabilis 1.3, and did not flash the Kernel (since I was already on the 2.01.605.11 kernel). Wifi tether works great. I use it all of the time.
So I go to turn on Wifi the other day (which I know worked on 1.1)... Error. I turn it on again.... Turns on, but 'Unable to scan for networks'.
Awkward.
So Troubleshooting 1:
Go to the Stock 2.01.605.11 Kernel and Wifi Modules thread. Flash the Wifi Modules. Flash the Kernel (again).
Still Error (won't turn on), then the second attempt, it 'turns on' (or appears to) and 'Unable to scan for networks'.
I say OK.
Troubleshooting 2:
Flashing Ineffabilis 1.3 again, and then letting it go into Bootloader, and flash its own Kernel. The kernel comes with the ROM (even though I think it's that same 2.01.605.11 version kernel - but just for the procedure). So Fresh flash of Ineffabilis 1.3. Then Flashing the kernel that comes with Ineff.
Boot up.
Same problem. Wifi gets 'error'. Then when I try to turn it on again, it's 'Unable to scan for networks'.
Am I stupid?
Should I flash wifi drivers and a kernel from 1.02 (original version, before OTA)?
Is my middle name Suzie?
I'm so confused here.
------------------------------------SOLUTION-------------
I did adb shell and deleted /data/misc and /data/local
then exit
then adb reboot
Problem solved!
I don't know what data in one of those two areas did it, but my wifi works now 100% without issue. I had already tried so much, I don't know which of the two had the problem in it, but neither one seemed to affect the data on my phone enough for me to notice, so I am happy.
You need to do a full wipe and install everything including the kernel. ROM does not like flashover.
I had this since the kernel auto-flash in this rom appears broken. You only need to flash the updated kernel with the updated libs for you to get past this.
here's the one you need- http://bit.ly/zCmQGk
flash that zip in recovery. Once it copies the new libs into place it will create a PH image and drop it onto the flash card. Reboot into hboot and allow it to update the kernel itself.
That will set you straight.
dottat said:
I had this since the kernel auto-flash in this rom appears broken. You only need to flash the updated kernel with the updated libs for you to get past this.
here's the one you need- http://bit.ly/zCmQGk
flash that zip in recovery. Once it copies the new libs into place it will create a PH image and drop it onto the flash card. Reboot into hboot and allow it to update the kernel itself.
That will set you straight.
Click to expand...
Click to collapse
I appreciate that!
Still 'Unable to Scan for Networks'. I think I need to wipe something.
Upsetting. Time to finally wipe with 112 apps.
This would be the solution though. Installing the libs and kernel should be the fix. I must have some messed up data somewhere.
Turns on, Scans for networks, and says 'Unable to scan for networks' in a toast notification like every 5 seconds, and after a few times, it goes off then on again (unlimited cycle).
I added a network for a known wifi hotspot. Didn't add in the list!
It's my Data. As soon as I restore (just my data) from nandroid, and boot up, wifi is fried.
A completely fresh wipe and flash of ROM works great. I'm trying to wipe
/data/system (didn't work)
/data/data (didn't work - but the 'Weather lockscreen was blank and all kinds of interesting icons and widgets were missing.... yet WiFi still did its thing)
So it's not in /data/data or /data/system..... hhhmmmmmm. still hunting.
and then let the data folders sync back up after the phone boots up. Trying each folder inside /data until I find which one messed up my wifi. I'm determined!!
I get this in DDMS when I try to turn it on.
http://pastebin.com/DYFF0Ft3
FOUND IT!
I deleted (just to try it)
/data/misc
/data/drm/
/data/radio
/data/local
One of those did it. I don't know if I'm going to narrow it down, or just wipe those and leave the rest of my data.
So it was in /data/local or /data/misc
I deleted them both - wifi works! Awkward.
Thanks for the help either way, gentlemen!
so i noticed that my wifi also stopped working (in addition to my bluetooth). so i tried going back to RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00 .1123r_3161E_9K_QMR_release_233635_signed.exe. i thought going back to stock would restore it, but no dice. i'd like to try deleting the folders you mentioned, is there any risk in doing this?

Atrix reboots constantly

I know there's a few posts on this, but looking for advice specific to my symptoms. The problem started off with Android media process using up a lot of cpu each time the phone was powered on. It gradually got worse and started rebooting when this happened. Started off as once or twice a day. Then got worse and worse. I had been on a bell atrix ROM (2.3.6) for about a year.
Tried flashing a number of roms, and making sure to clear caches and factory reset each time. Tried numerous versions of the CWMRecovery, no good. I notice that it noly seems to restart if it tries to communicate wirelessly (wifi or 3g seemingly). If I just leave it in cwmrecovery, it stays on fine. If I leave it at the first motoblur setup screen, without entering wifi settings, it stays on fine.
So I guessed it may be related to the radio. Installed a UK radio, bell original one and a euro one to no avail
Is there anything else I can do before I give up, or is it hardware?
cruhoortwunk said:
I know there's a few posts on this, but looking for advice specific to my symptoms. The problem started off with Android media process using up a lot of cpu each time the phone was powered on. It gradually got worse and started rebooting when this happened. Started off as once or twice a day. Then got worse and worse. I had been on a bell atrix ROM (2.3.6) for about a year.
Tried flashing a number of roms, and making sure to clear caches and factory reset each time. Tried numerous versions of the CWMRecovery, no good. I notice that it noly seems to restart if it tries to communicate wirelessly (wifi or 3g seemingly). If I just leave it in cwmrecovery, it stays on fine. If I leave it at the first motoblur setup screen, without entering wifi settings, it stays on fine.
So I guessed it may be related to the radio. Installed a UK radio, bell original one and a euro one to no avail
Is there anything else I can do before I give up, or is it hardware?
Click to expand...
Click to collapse
just had a look around and came across this http://forum.xda-developers.com/showthread.php?t=1884381 . Forgetting the Jb reference it might be an idea to follow the steps and see if that helps.
If it were me, I would do a complete system wipe first (CWM>mounts and storage>format system,data,preinstall,osh) and then reinstall a rom (I would recomend CM7.2 to start). I also might be inclined to take the external sd card out as well before restarting phone and see if that helps (going down the corrupt media file route)
Good Luck!
barry_ said:
just had a look around and came across this http://forum.xda-developers.com/showthread.php?t=1884381 . Forgetting the Jb reference it might be an idea to follow the steps and see if that helps.
If it were me, I would do a complete system wipe first (CWM>mounts and storage>format system,data,preinstall,osh) and then reinstall a rom (I would recomend CM7.2 to start). I also might be inclined to take the external sd card out as well before restarting phone and see if that helps (going down the corrupt media file route)
Good Luck!
Click to expand...
Click to collapse
Thanks for this, I never spotted the mounts and storage section for formatting before. Looks to be good to get a clean wipe
Will try now
I managed to get the MROM rom on to it, and it has stayed on for about 30mins now with wifi on.
However, it doesn't boot normally, it says 'Modem did not power up, starting RSD protocol support'. I have to choose Boot Android (no BP) to get it to boot ok. What would make it fail like this?
Is there any way to make the phone always boot android by default?
Another thing to add: I can't add any APN. If I add one and save, it doesn't save.
cruhoortwunk said:
I managed to get the MROM rom on to it, and it has stayed on for about 30mins now with wifi on.
However, it doesn't boot normally, it says 'Modem did not power up, starting RSD protocol support'. I have to choose Boot Android (no BP) to get it to boot ok. What would make it fail like this?
Is there any way to make the phone always boot android by default?
Another thing to add: I can't add any APN. If I add one and save, it doesn't save.
Click to expand...
Click to collapse
I can see that i am missing a boot.img to make it boot properly. Where can I download it?
A boot image always comes with any ROM, and MROM is no exception. If you sucessfully flashed the ROM, you've flashed the boot image too, I'm not sure why you think it's missing. But if you really want to reflash it, you can always extract it from the ROM's zip file.
ravilov said:
A boot image always comes with any ROM, and MROM is no exception. If you sucessfully flashed the ROM, you've flashed the boot image too, I'm not sure why you think it's missing. But if you really want to reflash it, you can always extract it from the ROM's zip file.
Click to expand...
Click to collapse
Alright, looks like I misunderstood the function of the boot.img. Any idea as to why it would not load the OS without me prompting it to boot android with no bp?
What is the best process to follow before flashing a rom?
I was doing factory reset,clearcache and clear dalvik from CWM. And I have started doing CWM>mounts and storage>format system,data,preinstall,osh now too.
Is that sufficient to get a good clean slate to start fresh?
And what's the best way to flash the radio? I have tried moto-fastboot radio radio.img, but that seems to stop the OS from loading. I assume the radio be installed after the ROM?
Tried an older gingerbread Bell rom, and same problem. I can only get it to boot by choosing boot android(no bp).
I also can't add an APN to it. I create it, save it and it doesn't save it to the list.
Found a fix here for the APN problem on ICS, but wondering if there's an equivalent on Gingerbread?
'Settings --> More... -> Uncheck 'Enable alt OEM telephony code' and 'Enable alternate getIMSI code'. Then reboot, and now you can add your own apn. '
No idea really, sorry. Kinda seems to me for some reason it's your bootloader that's having issues, not the ROM.
Still cant get it working, can't add an APN.
Replaced the SIM, same.
Noticed that the IMEI and baseband are listed as unknown, and think it's related. So I tried flashing a few radios.
Bell radio stays on about a min, then reboots phone
UK radio reboots once OS has loaded
French radio reboots once OS has loaded
I am based in Ireland, using a phone that was originally Bell Canada. Which radio should I try flashing?
Have you tried AT&T 36p or 37p radio?
No dice. What is the standard process with the radio zip? I have been extracting to a folder, then using moto-fastboot to clear the cache, then install the radio.
Am I missing a step or 2?
Why were you extracting it? Most radios come in a flashable ZIP, which means you flash it through recovery. No extracting.
I always got an error trying to install the zip in CWM. So installed img from fastboot instead. I'll try the newer zips from CWM.
cruhoortwunk said:
I always got an error trying to install the zip in CWM. So installed img from fastboot instead. I'll try the newer zips from CWM.
Click to expand...
Click to collapse
I get error 'assert failed' ...status 7.installation aborted..'trying to install both ATT radio zips via CWM, and status 0 trying Bell radio zip
Update on this:
I got a new phone a few days ago, and had trouble adding an APN (same problem it wouldn't save). Problem was it was not reading the sim correctly. I had some sellotape on part of the card. Removed this, and I was able to add the APN no problem.
I have cleaned the contacts on the sim card reader, no luck.
I am convinced that this is the faulty part though. When I go to add an APN, it should automatically populate the MCC and MNC from the sim, but it doesn't.
Sorry to bump an old thread but...
I have left this Atrix aside for a few months,and wanted to try it once more before giving up entirely.
It reboots when I use 3g or wifi. If I leave it offline or in cwm mode, it stays on ok.
Any ideas? Is it definitely hardware? (Have tried about 4 different images)
cruhoortwunk said:
Sorry to bump an old thread but...
I have left this Atrix aside for a few months,and wanted to try it once more before giving up entirely.
It reboots when I use 3g or wifi. If I leave it offline or in cwm mode, it stays on ok.
Any ideas? Is it definitely hardware? (Have tried about 4 different images)
Click to expand...
Click to collapse
Does it reboot if you put it in Airplane mode, then connect to WIFI only?
My Atrix randomly reboots if I have the cellular radio on, but if I put it in Airplane and only use WIFI, its very stable. I tried dozens of radios and ROMs, nothing seems to help, so I've chalked it up to some flaky hardware.

[Q] cm11 wifi problem

I am having trouble connecting to my router at home...Idk why this is happening, it was working fine on the stock 4.1.2 rom but ever since I updated to cm11 nightly (tuesday march 10, 2014), I cannot connect to my wifi.....Any help?!?!
why are people overlooking my thread?!?! I really need to fix this
AlainFarqy said:
I am having trouble connecting to my router at home...Idk why this is happening, it was working fine on the stock 4.1.2 rom but ever since I updated to cm11 nightly (tuesday march 10, 2014), I cannot connect to my wifi.....Any help?!?!
Click to expand...
Click to collapse
This is a ROM problem (I have this problem too) so don't worry about your device. I'd recommend switching to ParanoidAndroid (where WiFi works) and connecting to your network, then flashing back to CM11. If you care about data then make a Nandroid backup and after reinstalling CM do advanced restore and just restore data.
Step-by-step:
1. Download PA 4.4.2 (in the Original Android Development forums for this device)
2. Reboot into recovery
3. Full backup
4. Wipe, and install PA as per the instructions on the original post in the PA thread
5. Boot into PA, set up, connect to WiFi
6. Boot into recovery
7. Install CM11 but don't wipe. This is a little risky but mostly you shouldn't have a problem, since you haven't done anything on PA . 99% of the time you can restore to a backup if anything goes wrong.
8. (Optional) In the recovery choose advanced restore and restore data ONLY. this will restore your original apps and shouldn't cause any problems since the apps are originally from the same CM11 environment.
Hope I helped.
I having wifi problem with cm11 and PA too. I've flashed many radio file but it didnt work. i can connect to wifi after flashed radio but it stop download after a while, althought it still connect to wifi
xike456 said:
I having wifi problem with cm11 and PA too. I've flashed many radio file but it didnt work. i can connect to wifi after flashed radio but it stop download after a while, althought it still connect to wifi
Click to expand...
Click to collapse
If this is your problem, and flashing a radio works for a while, then try more radios. There are a few lists of hybrid radios in the general area for the e970. Though, I doubt this is a radio problem as when the stock ROM is flashed WiFi works with pretty much any radio, so I find it somewhat weird that using a new radio fixes the issue for you.
Sent from my LG-E970
I need more details. What do you mean by cannot connect? What happens? Please post a logcat of trying to connect.
Sent from my LG-LS970 using xda app-developers app
Shelnutt2 said:
I need more details. What do you mean by cannot connect? What happens? Please post a logcat of trying to connect.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Same is happening with me(CM11 M4)
when i turn on the wifi it scans n shows all the available networks.
when i select mine to connect, as usual it asks password.
after entering password; all that happens is it shows "saved" in wifi list.
nothing else happens.
i have tried connecting all types of wifi networks.
Also on the same line, i cant start the Wifi hotspot as well
after clicking on Portable hotspot it keeps on showing "Turning hotspot on..." for infinity.
I was also having wifi issues. For me, it was because my phone still had the ICS radios. Once I flashed the JB radios everything started working great. maybe that is your issue?

[Q] No mobile network after flashing roms

Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Verilin said:
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Click to expand...
Click to collapse
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
topherk said:
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
Click to expand...
Click to collapse
No, didnt realize that i needed to do that. I'll do some research on it because i don't have any idea how to update the bootloader. If you have a link to a good tutorial that would be wonderful! Thanks!
Ok so i tried that, found this tutorial, followed it, no luck. Tried full wipe/reset after that to see if it would let me install the hltespr versions, still no dice. Same situation, mobile data works, calls don't. Will have to wait till daylight to try texting so i don't wake anyone up but i suspect that texting won't work either. Has anyone experienced this and fixed it? Lol i really didn't drop $100 on a phone to be saddled with all the Samsung and Sprint baloney that it comes with, don't wanna unroot....
Bump
Anyone have ideas on this? Have continued to try fooling around with the udater-script file to resolve the status 7 problem so I can install the hltespr variant, still no dice. Please someone help!
Bump!
Sorry, I typically don't have access to XDA forums on the weekend, so couldn't answer your question till now.
You flashed only the baseband/modem, not the Bootloader. If you want to update the Bootloader, you need to use ODIN to flash the Complete OTA NH7 Update.
In order to update the Bootloader, you need to make sure that you use the PC ODIN (not the mobile one) and that you completely power off the phone before you enter download mode (don't access download mode by using the extended power menu when shutting down the phone). I don't think you need to do the battery pull that Freeza had in his instructions (I didn't do it when I ODIN-flashed the NH7 OTA update), but it wouldn't hurt to do it.
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Verilin said:
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Click to expand...
Click to collapse
Well, I always recommend a full wipe (data, system, cache, dalvik) when flashing ROMs. I haven't wiped my internal storage or external storage since I got the phone, so that's not really necessary.
I don't think that unrooting your current ROM is necessary. Flashing the ODIN OTA update will automatically remove root access, so that's not an issue. Here's the steps I took when I updated to NH7 and installed my current ROM (see my sig):
Make a Nandroid backup.
I always do this just so I have a "record" of what I left behind. It also allows me to have all of my app data that I can restore via Titanium Backup (you have to buy the Pro version in order to restore specific apps from a Nandroid backup). I always store a copy on my ext. storage and on dropbox.
Do a full wipe
As I mentioned above, I always wipe data, system, and the caches when flashing ROMs. While I have to take some time to get the new ROM exactly as I like it, it minimizes any potential FCs and errors that some people get when dirty flashing.
Install NH7 all-in-one via ODIN
I installed the NH7 via ODIN. Please note that this is the fully stock, unrooted ROM and will also install the stock recovery.
Let the phone boot and connect to Sprint. Update Profile and PRL.
I do this periodically whenever I go back to stock (from AOSP). I rarely have connection issues, but updating the PRL an profile can help with those.
Install a custom recovery using ODIN.
My recovery of choice is TWRP, but others have found just as much success with CWM and Philz. Just make sure that you're installing the correct version of the recovery (4.4.X version, not the 4.2.X version). I always reboot to the main system after installing a recovery, but that's up to you. In the rest of this post, I'll say "TWRP," but I really mean "custom recovery."
[OPTIONAL] Make a Nandroid backup of the stock ROM
I always do this, but I recognize that it's not necessary, especially since we can just ODIN back to this image at any time. I just like having the option of having a stock backup on the device (in case catastrophe strikes while I'm away from a computer).
Use TWRP to flash your AOSP ROM of choice.
If you haven't installed any apps or messed around with the settings, you shouldn't have to wipe before flashing, but (in case you haven't noticed by now), I tend to err on the side of caution, specifically: wiping everything (data, system, and the caches) before I flash anything.
Set up the ROM how you like it and [OPTIONAL] make one last Nandroid Backup
Whenever I set up a new ROM to the exact way I like it (statusbar settings, accounts set up, apps installed and configured, etc), I make a nandroid backup of my device. This allows me to go back to that "fresh" image whenever something happens to the device and I don't have to muddle around fixing those minor tweaks. Again, I tend to err on the side of wiping the phone too often and taking too many backups, but I've rarely had issues with my phone and ROMs because of it (to the point where I can spend most of my XDA time helping others with their phones), so it might be prudent to follow the advice.
Anyways, that's how I upgraded to NH7 and installed a custom ROM. Others may take a less conservative approach and you're welcome to adjust any of the optional steps.
Hope this helps!
-Topher
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Verilin said:
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Click to expand...
Click to collapse
Dumb question but are you a Verizon customer or Sprint?
Sent from my SM-G900P using Tapatalk
Sprint, I've had big red before but when they did away with unlimited data it wasn't worth paying their high rates.
Bump!
Anyone have any ideas on this? I am just confounded as to why this continues even after being reset to stock.
Same Issue!!!
I have the exact same issue and have been trying to resolve it for the last 2 days... Did you find a solution?
I have the same problem on a Samsung Mega. LTE and 3G data work but phone won't dial if LTE is active. It WILL voice dial if only 3G is active. Sprint. CM11.
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
thanks forget the little things reset wifi and sprint cell extender
GAPO said:
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
Click to expand...
Click to collapse

CM-13.0-20151223-NIGHTLY constant checksum Fail, flash from recovery returns error

Hi XDA,
first, I greatly appreciate all the effort you are putting into this. You have made using my age-old i9300 a blessing multiple times. So thank you for that!
Now on to my problem. I have recently wiped&clean-installed the CM-13.0-20151222-NIGHTLY build and appear to have lost root-access. I did enable it in the developer options (I have tried both app and adp and "just" app access) but rootChecker ist still returning a negative result and any app using root doesn't function (titanium back-up for example). Primarily I want to use it to stop some apps from auto-starting that I hardly ever use.
I had read that when updating the ClockWorkRecovery (latest verison.. 6.0.4.7) prompts you if you want to re-enable root access (like it did when I first auto-updated from CM11 to CM13 (which obviously didn't work which is when I wiped everything and flashed the CM-13.0-20151222-NIGHTLY)). Today a new nightly came out and I thought I'd give it a shot but the checksum constantly fails from within the updater and it won't allow me to flash it claiming the download is bad (multiple downloads tried, always same result).
Is anyone else experiencing these issues with the checksum Fail and the lost "full" root access? Did you manage to find a solution to it?
Kind regards,
kidd
Tried two times downloading update and both times got checksum error, then downloaded manually and dirty flashed in TWRP, everything went fine.
Do an error test on your hdd and power cycle your router.
If the hdd is corrupt it will corrupt data. If the routers network address translator is borked it will corrupt data.
I wish I stole my HTC M9.
The issue has appears to have resolved itself. The Update went through fine after I had tried the next day.
Is there any fix for the converting the pseudo-root back to the full root you know of?
Best,
Kidd

Categories

Resources