Database Users

[Q] SM-N9005 wifi Not Working

Facing Problem at power on Wifi
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

najrazlug said:
Facing Problem at power on Wifi​
Click to expand...
Click to collapse
Factory reset your device (Settings > Accounts > Back Up and Reset > Factory Data Reset > Reset Device > Delete All/Erase Everything.)

Joku1981 said:
Factory reset your device (Settings > Accounts > Back Up and Reset > Factory Data Reset > Reset Device > Delete All/Erase Everything.)
Click to expand...
Click to collapse
Erased and reset everything acording to your comand ....
What Is Next ?

najrazlug said:
Erased and reset everything acording to your comand ....
What Is Next ?
Click to expand...
Click to collapse
Install this APP and add some screenshots.

Screen Shoots
Joku1981 said:
Install this APP and add some screenshots.
Click to expand...
Click to collapse

Take a look: HERE. Your IMEI is blacklisted with the company Telus (Canada).

IMEI Is not original ,am askinn about WIFI
Joku1981 said:
Take a look: HERE. Your IMEI is blacklisted with the company Telus (Canada).
Click to expand...
Click to collapse
IMEI Is not original it was written by Octops support shared certificates
IMEI WAS null at that point wifi was no working ....
iwifi problem du imei blacklisted ?

najrazlug said:
IMEI Is not original it was written by Octops support shared certificates
IMEI WAS null at that point wifi was no working ....
iwifi problem du imei blacklisted ?
Click to expand...
Click to collapse
Wipe all and reflash the same firmware or directly flash android 5.0 Lolipop: HERE.

ok Sir
as u said reflash with same firmware ..... phone in same condition
Now Going to flash With XEO 5.0 ...
In Addition let me infrom you ...phone's CSC Code is unknown ....
in start the phone CSC COD WAS XEO ,But baseband was unknown and wifi was working ....
By Wrting another efs phone PHONE ON RECOVERY SAYS (E: FAILD TO Mount efs .) ..like this ....but at that poing WIFI WAS WORKING....
tHEN I FLASH TO 5.0 AND THENDOWNGRADE AFTER THAT wifi is not working

najrazlug said:
as u said reflash with same firmware ..... phone in same condition
Now Going to flash With XEO 5.0 ...
In Addition let me infrom you ...phone's CSC Code is unknown ....
in start the phone CSC COD WAS XEO ,But baseband was unknown and wifi was working ....
By Wrting another efs phone PHONE ON RECOVERY SAYS (E: FAILD TO Mount efs .) ..like this ....but at that poing WIFI WAS WORKING....
tHEN I FLASH TO 5.0 AND THENDOWNGRADE AFTER THAT wifi is not working
Click to expand...
Click to collapse
Ahhhhhhhhhhhh, only you will have to reflash android 5.0 again coz your bootloader is updated.

Joku1981 said:
Ahhhhhhhhhhhh, only you will have to reflash android 5.0 again coz your bootloader is updated.
Click to expand...
Click to collapse
brother i have the exact same problem i updated to BOB6 today and my wifi is not turning on please help

Warning - You cannot sim network unlock the XT1524 with an unlocked bootloader/CM13

Hi guys, just a word of warning....
I flashed my stock en-GB android 5.0.2 xt1524 phone with en-EU 6.0 rom then flashed with CM13. I was unable to unlock the network sim-card lock that would allow me to use sim cards from any network. In order to relock the bootloader you need an official rom installed, i tried flashing with the en-GB 5.0.2 rom but i got these errors:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The problem seemed to be that i had previously upgraded to the en-EU 6.0 rom which upgrades the bootloader so i had to re-flash the en-EU 6.0 rom.
I then re-locked the bootloader and booted the phone up and put in my network unlock code that i bought for £2.50 off ebay and it successfully unlocked
PLEASE NOTE: I'm not sure whether the bootloader has to be locked, root to be removed or whether you just need an official rom and not a CM13 rom for this to work. In hindsight i should have tried unlocking my phone straight after flashing with en-EU 6.0 without re-locking the bootloader then i would know whether it was having CM13/root that was at fault or having an unlocked bootloader.
P.S I tried entering the network unlock code at least 6 times and it didn't lock me out of the phone or stop me from unlocking it successfully later on so don't stress yourself out over retrying the code fearing that it will lock your sim card forever, that won't happen, not for the first 6 attempts at least.
p.s the reason i didn't unlock the network lock when i first got my phone with stock android 5.0.2 is that many ebay unlock code sellers too ages to respond and those that did were unable to get an unlock code for my phone. I eventually found someone who could get a working unlock code for me.
Here is the errors that i got when trying to re-lock the bootloader when my phone had CM13 on it:

Content of EFS folder I9505 - please check (there is folder content, but IMEI null)

My phone says IMEI unknown, baseband unknown. I don't know if anything is missing from my EFS, but it is present on the phone memory in root folder. Can someone with I9505 please check the files in EFS?
I returned stock firm, but still no imei, so no network.
Here is my EFS folder:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is my menu (Cyanogenmod):

Ive got bluetooth, carrier, cpk, drm, factoryapp and log folders in efs..no lost and found, never installed cm, you probably need to flash the modem/bootloader

Are you with I9505 exactly?
I tried flashing modem several times :/
Can baseband: unknown be a hardware issue?

yea the i9505, what firmware and modem version are you flashing??

First it was stock 5.0.1 XEO touchwiz. Working normal 1 year, then it started loosing network coverage.
After that, i flashed CyanogenMod 13. The coverage problem continued. Then I flashed AOSP 6.0 - same thing. But I had EMEI and baseband OK.
After that I decided to turn back to stock. And some time after that it lost IMEI and baseband. It could be the hardware problem got deeper, I don't know. Since then I tried almost everything. The EFS folder is on the device. I've changed permissions, made efs backup, restored it - no IMEI and baseband. Installed xposed and IMEI changer - set it to my original IMEI. There was IMEI, but again no baseband! I tried getting back to 6.0.1, because the IMEI/baseband was gone when back to 5.0.1. But no IMEI/baseband again.
So I'm stuck.

The IMEI no longer lives in the EFS partition, but in hidden partitions on the device that you cannot normally touch. Thus touching the EFS partition won't help you restore the IMEI, as there is no NV Data in the EFS partition and hasn't been for some time now. So if you're missing your IMEI and didn't make a backup of those partitions using the Wanam Partition Backup tool, you'll have to have the phone serviced. The items that we can flash using Odin do not include those hidden partitions.

Thank you, man! I was so desperately searching for nv_data.
I actually have a back-up, but it was made with clockworkmod, but maybe it doesn't include those partitions
Actually the modem partition maybe is my biggest problem, cause i wrote down an IMEI with xposed, but no baseband, so no need of imei

Nandroid backups don't touch the hidden partitions, so you won't have any of that data. Writing the IMEI I'm not sure is going to help you much, especially where you have already attempted to restore the stock radios on the device.

When i read the info with a tool, PDA, CSC, Phone S/N are present.
The following are empty:
HW version:
Modem board:
RF cal date:
IMEI:
Any ideas?

Modem Board and Hardware Revision having no information is normal. I can't answer about the RF cal date (RF Calibration date). However, not having an IMEI is not normal. Since your NV Data was somehow wiped out in the hidden partitions, your IMEI was also wiped out. It doesn't matter what stock ROM you install, you will not get your IMEI back because there's nothing in the hidden partitions to be read. Therefore your only alternative is to take the phone to a service center and have them restore the IMEI.

Can't restore Baseband, Software version, IMEI and so on

Not really sure when it happened (probably while I was playing around with different custom roms) but my phone managed to lose all private data as well as the ability to "see" what's installed on it.
I can't see my Baseband, Hardware or Software version, IMEI and even MSL is not working.
I can't perform ##RTN# or ##SCRTN# and if I switch to dm+adb+modem DFS doesn't want to connect to it (it doesn't see it on its port).
Also, phone is not recognized by the computer when it's booted but it is in the TWRP recovery.
If I try to ODIN a Lollipop STOCK rom it won't boot, but I can install a Lollipop that's TWRP compatible.
I do have a backup of the efs partition as well as m9kefs1-3 but restoring them didn't change anything.
I've even copied all the partitions from another Sprint S4 (including the system) and replaced them trough the terminal in TWRP but no luck.
I'm out of ideas.
Any help is appreciated.

djuka007 said:
Not really sure when it happened (probably while I was playing around with different custom roms) but my phone managed to lose all private data as well as the ability to "see" what's installed on it.
I can't see my Baseband, Hardware or Software version, IMEI and even MSL is not working.
I can't perform ##RTN# or ##SCRTN# and if I switch to dm+adb+modem DFS doesn't want to connect to it (it doesn't see it on its port).
Also, phone is not recognized by the computer when it's booted but it is in the TWRP recovery.
If I try to ODIN a Lollipop STOCK rom it won't boot, but I can install a Lollipop that's TWRP compatible.
I do have a backup of the efs partition as well as m9kefs1-3 but restoring them didn't change anything.
I've even copied all the partitions from another Sprint S4 (including the system) and replaced them trough the terminal in TWRP but no luck.
I'm out of ideas.
Any help is appreciated.
Click to expand...
Click to collapse
Install stock tar in Odin. Boot to recovery then wipe internal SD and do a factory reset. That should allow it to boot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Been there, done that. I can boot stock KitKat nut I can't boot stock Lollipop even with the factory reset. It just goes into a bootloop. Not sure that would change anything.
I can't explain how is it possible to replace the data on every partition from the working phone and still have a "broken" phone.
Is there any other memory on S4 that is not accessible?

From what I can see it seems that modem and system are not communicating - case in point, even if I put my phone in the airplane mode when I look at the battery consumption I can see that "cell standby" percent constantly increases. In the airplane mode this should be off, right?
Also, is there a way to see if the modem is functioning properly or it might be damaged?

djuka007 said:
From what I can see it seems that modem and system are not communicating - case in point, even if I put my phone in the airplane mode when I look at the battery consumption I can see that "cell standby" percent constantly increases. In the airplane mode this should be off, right?
Also, is there a way to see if the modem is functioning properly or it might be damaged?
Click to expand...
Click to collapse
I mean if you have service it's working, but other than that the only thing you can do is flash the stock tar. Putting it in airplane mode forces it into Cell Standby btw.

bilgerryan said:
I mean if you have service it's working, but other than that the only thing you can do is flash the stock tar. Putting it in airplane mode forces it into Cell Standby btw.
Click to expand...
Click to collapse
That's the whole point, I don't have service. I'm in Europe now, had my phone internationally unlocked, everything worked fine but now the system doesn't see the SIM card at all. It doesn't even report it as "Wrong SIM card" it just doesn't register it.
I've flashed a stock rom *NAE* and upgraded it (without a problem) trough OTA all the way to GPL1 (NAE-NG2-OD2-OH1-OK3-PI2-PL2) - six updates, problem stays the same. All the time I have the system as "Samsung Official", no suggestions what might be wrong.
And why, oh why, system doesn't want to accept my MSL when I try to do the ##RTN# or ##DATA# edit. I doesn't matter what number I put in, I still can't press OK. And ##MSL# "reacts" but does nothing.

djuka007 said:
That's the whole point, I don't have service. I'm in Europe now, had my phone internationally unlocked, everything worked fine but now the system doesn't see the SIM card at all. It doesn't even report it as "Wrong SIM card" it just doesn't register it.
I've flashed a stock rom *NAE* and upgraded it (without a problem) trough OTA all the way to GPL1 (NAE-NG2-OD2-OH1-OK3-PI2-PL2) - six updates, problem stays the same. All the time I have the system as "Samsung Official", no suggestions what might be wrong.
And why, oh why, system doesn't want to accept my MSL when I try to do the ##RTN# or ##DATA# edit. I doesn't matter what number I put in, I still can't press OK. And ##MSL# "reacts" but does nothing.
Click to expand...
Click to collapse
Sounds like it might be a hardware problem then, if the software is completely stock that usually indicates it is hardware. Maybe your SIM reader or the SIM card itself is damaged.

bilgerryan said:
Sounds like it might be a hardware problem then, if the software is completely stock that usually indicates it is hardware. Maybe your SIM reader or the SIM card itself is damaged.
Click to expand...
Click to collapse
Whatever it is, seems like the modem is dead (or there's no way to communicate with him).
I thought that AT commands might do but I can't reach it from the computer either. Tried DM+MODEM+ADB, RNIDS+DM+MODEM but it doesn't give me any reply. It is recognized in the Device Manager, but when I go to Properties\Diagnostics and then "Query Modem" I get - "The modem failed to respond".
I've tried changing UART between PDA and CDMA (AP/CP) but there's no difference.
I've bought a new phone, can't go around without one, this is kind of a side project now to see what I can learn but it will probably be sold for parts (it's not worth fixing it). Shame.
If you guys have any additional ideas, let me know, now I can experiment all I want.
Cheers!

Upgraded B2017G from 6.0.1 to 7.1.1, calling broken, not sure what to do...

So I've had this phone for a few months but thanks to the mess with the US I wasn't able to get the Nougat update from ZTE's servers through the Gold's System Update. I later found a Nougat image on ZTE's support page, put it on an empty SD card and installed it from Settings>System Update. That went fine. I rebooted, did the setup, installed a few apps and everything seemed great until I tried to make a phone call. The display sits on 'Dialing...' for about 20 seconds with no ringing sound and then the call drops, followed by the signal bars going hollow and a message that I have left my Home network. After 10-20 seconds the signal meter returns to normal and I'm on my Home network again. Calling out aside, SMS works fine and 4G works fine.
Rebooting does nothing, re-seating the sim does nothing and factory resets do nothing. When I go to Phone>Settings>Call Settings>Carrier Settings>Additional Settings a pop-up says "Reading settings..." and then after about 20 seconds I get "Network or Sim card error" and the Data Roaming warning (mentioned above) appears in the Notifications bar. Just trying to get that information off of the card breaks my data connection. I called my carrier and they confirm my account is in order and everything is fine on their end. When I put the sim back into my old phone it works properly and I can make calls and browse, etc. Going to the same >Additional Settings on my old phone, it loads up without the "Network or Sim card error" message. This all seems like a very specific error, that trying to pull my connection or account information from the sim is breaking my connection and causing outgoing calls to crash. This never happened on the Gold under 6.0.1.
In case it's important, I have a 7 Mini Gold but the 7 Mini Gold page does not have an update image on it. I used the update image from the 7 Mini page. I figured the lack of an image on the Gold's support page was an oversight rather than the Gold being so different that it needs its own separate updates. I hope I didn't get that wrong.
Unless someone has some insight into fixing this as-is, right now I think I have to either rollback Nougat (except I haven't found an image of 6.0.1 yet) or install Lineage OS. I think I have all the files I need to flash Lineage, using Tulip from here and the directions found here and the image found here. All comments, even just speculation, are welcome.

What carrier are you on? Do you have the right APN settings? I've had similar on T-Mobile when I'm in a Band12\VoLTE market with a non-VOLTE device. I can get LTE data without issues but the device would not call out because it could not see an active voice network.

pizzaboy192 said:
What carrier are you on? Do you have the right APN settings? I've had similar on T-Mobile when I'm in a Band12\VoLTE market with a non-VOLTE device. I can get LTE data without issues but the device would not call out because it could not see an active voice network.
Click to expand...
Click to collapse
Freedom mobile (Canada).
APN settings match what is listed on their site.
Freedom doesn't appear to offer VoLTE. The problem happens whether VoLTE is switched on or off.

I have a similar problem with a UK model. It doesn't give me the roaming pop up but the rest of the symptoms are the same. Calls drop immediately and calling my number from another phone returns busy signal. The network type preference doesn't work as well. It stays on 4g/3g/2g auto no matter what I select. I think mine is like this because I tinkered with the service menu but I am not sure. On another thread someone suggested to erase modemst 1 and modemst2 partitions in fastboot mode but I can't make it connect in fastboot plus someone said that erase command is blocked. I'm looking for a stock firmware image to re-flash it but it's nowhere to be found...
UPDATE: I've managed to erase the modem partitions with twrp and adb shell but it didn't help. network type preference works now but the phone doesn't connect to the network at all.

After taking a long break from fighting with the Mini I dove back in today. I was able to back-up boot and recovery and then flash twrp recovery. After the phone was stuck on the blue ZTE logo when I tried to start it. I flashed the B12 noverity boot image and now it boots normally. SMS is still fine and calls still drop without connecting, briefly kicking the phone to roaming. While I nosed around in the settings again and compared them to my working phone I noticed something that I'd dismissed before. Under Available Networks everything has "null" beside it. "Null" doesn't show at all in that section when using the same SIM in my other phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I call this a clue. Why I try to Google it I get articles about troubleshooting null SIM cards. I also found this stackoverflow thread and this comment:
https://stackoverflow.com/questions...k-is-on-or-available-or-not-on-android-device
in none of the code above i see a check for whether getNetworkInfo() returned null, which happens according to the docs when the requested network type is not supported.
Click to expand...
Click to collapse
This is probably a different kind of null than the one in my screenshot, but it makes me wonder. Are there any apps on either F-droid or Play that people would recommend that might report what is happening when the phone tries to connect to a tower to make a call?
I'm looking for a stock firmware image to re-flash it but it's nowhere to be found...
Click to expand...
Click to collapse
This index has what looks like B2017G-EU images. Can you use them?
http://files.nwwn.com/android/axon7mini/

Yoqui said:
This index has what looks like B2017G-EU images. Can you use them?
http://files.nwwn.com/android/axon7mini/
Click to expand...
Click to collapse
I'll try them, they look legit. Nothing to lose at this point. My mini is not registering in any network (Emergency calls only). Erasing modemst1 and modemst2 deleted my IMEI and MEID. I've managed to rewrite the IMEI but not the MEID. Flashing a custom rom didn't fix it. The phone is not bricked though so there is hope. I can still use ADB and EDL. There is a way to get the phone in deepflash mode even but I have nothing to flash on it so I haven't tried that yet.
PS: I've emailed ZTE and they are not responding. I think they are seizing support completely.