No network - SIM PIN Operation failed - Nexus 5X Q&A, Help & Troubleshooting

Dear all,
I'm having some serious issues about connecting to my service provider via my Nexus 5x (model LGH791). I'm based in Germany, trying to use o2. Due to the fact I'm using a german user interface some of the following translated description may vary from the original english descriptions.
Bootloader Info:
PRODUCT_NAME - bullhead
VARIANT - bullhead LGH791 16GB
HW Version - rev_1.0
BOOTLOADER VERSION - BHZ10r
BASEBAND VERSION - M8994F-2.6.32.1.13
CARRIER INFO - N/A
SERIAL NUMBER - 00b5xxxsecretxxxx
SIGNING - production
SECURE BOOT - enabled
DEVICE STATE - unlocked
Recovery: TWRP 3.0.2-1
Kernel: Stock Kernel.
Root: No, not rooted.
EDIT:
IMEI: looks like a valid IMEI
When I try to unlock my SIM via PIN I read the message: "SIM PIN Operation failed".
When I'm searching manually for a provider under Settings > Mobile Network I get the message "Error while searching for network".
I already flashed the sugested image from this XDA post here to change the base band.
I flashed the PureNexus ROM located on the XDA-Developers Forum, to change the base band too.
I removed the partition modemst1, suggested by this post, too.
I re-flashed the latest Stock ROM MTC20F from Google Developers.
I were able to choose the "European" and "Automatic" option under *#*#4636#*#* but I had to choose an option multiple times to successfully set it. Even choosing the USA Band says "Setting [USA Band] Unsuccessful". After alternating between "EURO Band" and "Automatic" a few times (varying) it says "Setting [EURO Band] Successful". Seems like some settings can't be set right away. Confusing.
When I'm prompted to unlock my SIM via PIN, I'm able to unlock it the first time. A few seconds pass and I'm prompted a second time resulting in a waiting/looping screen that says "Unlocking SIM..." that seems to be canceled after a timeout. The SIM card won't get unlocked after the second prompt.
Right now I'm not able to get any connection to a mobile service. The rest of the device works as expected.
I tested my SIM card in my Nexus 5. It's working fine. It's a self-cutted SIM card, formerly in the format of a microSIM.
I tested another SIM Card, used within an older HTC One Mini, that is working fine, too. It's a nanoSIM.
Anyone got any idea what's going on?
Best,
huppys

Related

Cannot RElock phone in order to unlock properly

I use a samsung captivate that was locked to Rogers. And now I am running it on Fido
I have been having issues connecting to 3G for over 6 months now. I completely gave up on the idea and lived off 2G, until someone suggested that I had unlocked my improperly. I believe this to be the root of my problems. I need to figure out how to lock my phone, and then if I can unlock it it properly, all my problems will be solved. PLEASE HELP. I will now try and explain all the different methods that I have used
The method I used initially was by extracting nv_data.bin file and using a hex editor to edit it to unlock. This did work, and my phone was working perfectly. But on a ROM update my 3G connectivity issues started.
I have to explicitly state 'only 2G' on my network connections, otherwise I lose my voice connection as well (because somehow the voice connections runs over the data connection - and one wont work with the other)
I decided to unlock properly - by buying a code off ebay. The code is based on the IMEI number of the phone.
I tried locking the phone by entering *7465625*638*# and entered
302720 (mnc/mcc for rogers)
and my purchased nck code
the phone even states that the lock code was successful. But on inserting my fido SIM, my phone acts like it did before - i.e. voice connection does work unless I explicitly select '2G only'
Initially I also tried locking by reediting nv_data.bin file using a hex editor. The instructions state editing the address '0x181468' on the file. There are 5 different bytes representing different locks (network lock, subset lock, sp lock, cp lock, data lock) and they are represented in binary. On just changing 'network lock' to 01 to phone acts the same. But on changing all the values on all the bytes the phone locks and asks for an unlock code on restart - but the purchased nck code does not work
This is over 6 months of trial and error, so I apologize if I am all over the place. Please provide any suggestions and I will clarify as soon as I can

[WIP] Unlocking Note 2 modem for GSM/AWS

This is NOT in relation to changing IMEI/ESN as that is ILLEGAL! This thread is about enabling our baseband/modems to operate on different frequencies/couriers.
Trying the VZW unlock thread first HERE
I'm flashing a VZW ROM right now to check APN menu, etc. Sprint even with hack doesn't show APN.
There are several threads on how to unlock Verizon/Tmobile/ATT modems to work on each other with varying levels of success. I feel that we have a iPhone 4s/5 like device that has the same chipset just different locks around the software to prevent unlocking. I was moved by the community's involvement in adding a SIM card slot to the Note 2 and want this mod to work on US couriers.
Basically put, I want to make any US variant S3/Note 2 an international version. The hardware is the same, it's the NVRAM/Firmware prohibiting us.
This is the SIM card mod for the SPR N2:
http://forum.xda-developers.com/showthread.php?t=1959005
Enabling AWS (T-Mobile) on ATT Note 2:
http://forum.xda-developers.com/showthread.php?p=35933247
Verizon S3 on T-Mobile:
http://forum.xda-developers.com/showthread.php?t=2013647
Verizon S3 on world GSM:
http://forum.xda-developers.com/showthread.php?t=1809314
The primary method of unlocking modem bands is flashing a QCN file that modifies NVRAM params. In the ATT T-Mobile thread the hack works by flashing over a ESN/IMEI stripped T-Mobile qcn backup file.
I tried following this process but was blocked by a "Roaming Lists could not be read" error at 16% when trying to backup my NVRAM using QPST. I attempted flashing the file anyway and received a "Could not Communicate in Diagnostic Mode" error. My modem then would not see any networks. I then flashed a ATT modem which bootlooped my device.
I feel the Roaming List could not be read is the main issue into how Sprint locked down this device for US GSM. In SIM tech, the courier provides a preferred list of up to 80 couriers the phone is to connect to first when roaming due to courier roaming agreements instead of the strongest signal first. As the Spr model uses a chip for a SIM it's possible that the "SIM" could not be read to provide roaming lists and GSM could be blacklisted in this chip as it is more sophisticated then a SIM smartcard. Now that I flashed a ATT modem I'm going to try to download the NVItems again using QPST.
I restored my TWRP backup and sideloaded a SPR modem, back at stock all working.
The alternative is to use the "IMEI/ESN" backup tool:
http://forum.xda-developers.com/showthread.php?t=1867442
I will continue experimenting and will report progress.
When writing back my NVRAM dump I get this list of readonly/locked items:
(NV Items http://forum.xda-developers.com/showthread.php?t=1954029)
Writing NV-items from a file:
Unsuccessfully written NV-items:
00000 (0x0000) - Password (16 digits) is required
0^"Electronic Serial Number"^"Security*"
00001 (0x0001) - Read only item
1^"Electronic Serial Number Checksum"^"Security*"
01943 (0x0797) - Password (16 digits) is required
797^"DCS TX Burst Ramp Down Index 11"^"GSM*"
05597 (0x15DD) - Read only item
05598 (0x15DE) - Read only item
These two are unknown but people get them when doing AWS unlocks:
http://forum.xda-developers.com/showpost.php?p=36078971&postcount=81
Found a AWS/ATT modified TXT file, I flashed it and reset
http://forum.xda-developers.com/showpost.php?p=36008901&postcount=49
Mobile networks show a previously unselectable item WCDMA only as selected which is not in the menu, the network status is unknown. I have a feeling the nv-item is trying to reference a menu item that is not in my ROM.
Next I'm going to ODIN the stock ATT rom over and see what happens.
FAIL! modem.bin won't flash.
Flashed Stock AIO modem+firmware+rom, etc odin to phone and flashed LJC modem manually. No data and was reporting WCDMA only from the last NV items hack. It seems NV-ITEMS are persistent across a complete and total stock restore+modem flash (twice) wipes and bricks. I restored my backup TXT for nv items and stock network has returned.
I'm flashing CM next for Sprint as it has "- Removed preset Network mode/selection (allows for more network modes)"
http://forum.xda-developers.com/showthread.php?t=2047667
Hopefully with the NV Items hack and a ROM without network modes locked w/ a SIM card board I should be gold.
Here is NV Items when flashing on stock ODIN:
Writing NV-items from a file:
Unsuccessfully written NV-items:
00000 (0x0000) - Password (16 digits) is required
00001 (0x0001) - Read only item
00005 (0x0005) - Command failed
00018 (0x0012) - Command failed
00031 (0x001F) - Command failed
00032 (0x0020) - Read only item
00033 (0x0021) - Read only item
00034 (0x0022) - Command failed
00035 (0x0023) - Command failed
00036 (0x0024) - Command failed
00037 (0x0025) - Read only item
00048 (0x0030) - Command failed
00049 (0x0031) - Command failed
00050 (0x0032) - Command failed
00176 (0x00B0) - Read only item
00177 (0x00B1) - Read only item
00178 (0x00B2) - Command failed
00209 (0x00D1) - Read only item
00210 (0x00D2) - Command failed
00211 (0x00D3) - Command failed
00212 (0x00D4) - Command failed
00213 (0x00D5) - Command failed
00215 (0x00D7) - Command failed
00258 (0x0102) - Command failed
00259 (0x0103) - Command failed
00260 (0x0104) - Command failed
00261 (0x0105) - Command failed
00262 (0x0106) - Read only item
00263 (0x0107) - Read only item
00264 (0x0108) - Read only item
00265 (0x0109) - Read only item
00266 (0x010A) - Read only item
00296 (0x0128) - Command failed
01943 (0x0797) - Password (16 digits) is required
05597 (0x15DD) - Read only item
05598 (0x15DE) - Read only item
Done.
1/10/13 6:17pm
http://forum.xda-developers.com/showthread.php?t=2016575
Trying new international ATT rom. CM10 didn't have what I needed for network selections.
I have successfully detected a GSM network type although it's going to need some work.. I got to go home and eat.
1/11/13 11:14am
Using the RF NV editor from QPST I can edit all NV-Items with no roaming lists error.
BY FOLLOWING THESE INSTRUCTIONS YOU ARE INTENTIONALLY BRICKING YOUR DEVICE. I HAVE TESTED RECOVERY BACK TO STOCK WITH A ODIN FLASH AND RESTORATION OF MY NV-ITEMS BACKUP. I TAKE NO RESPONSIBILITY FOR YOUR DEVICE AND THESE INSTRUCTIONS ARE PROVIDED AS-IS.
That being said I have ODIN flashshed ATT firmwares over, international firmwares over, changed numerous NVItems settings and have been successful in restoring my device to fully operational stock with working radio/service. At one point I had to go into download mode and odin TWRP and ADB sideload a modem due to a boot loop but I was still able to recover.
*DO NOT PROCEED UNLESS YOU ARE AWARE OF HOW TO UNBRICK YOUR DEVICE AND RESTORE IMEI/NV-ITEMS*
To enable USB file transfer at anytime dial *#7284# Qualcomm USB Settings and select MTP+ADB
Here is a howto/recap of what I have accomplished:
**YOU MUST BE ROOTED**
You need the SIM card board for this to work otherwise you are simply experimenting. Get one HERE
1. Get the Note 2 toolkit and drivers per your device HERE This is the easiest method of getting all required tools/software for a brick restore and other flashes.
2. Get the Samsung NV Items tool HERE
3. Get your MSL using the *root required* Get my MSL app HERE Write it down and keep it in a safe place!
4. Dial *#7284# go to Qualcomm USB Settings and select RNDIS+DM+MODEM
5. Plug or Replug your device and wait for drivers to install
6. Open Device Manager and expand Ports (COM & LPT) (windows xp/7/8), make a note of which COM SAMSUNG Mobile USB Serial Port (COM*) (If you do not see the port listed then you didn't install drivers, wait for driver install or you didn't enable Qualcomm diag properly)
7. Open NV-items_reader_writer.exe and select your COM* from Port: dropdown. Put your MSL # in where it says 000000. Make sure BOTH checkboxes are checked and click connect. Click Read. Should say in console "Log message: > SPC is correct. Phone unlocked".
If you get "Log message: > Phone does not accept SPC. SPC is not correct" then try 000000 as MSL
8. Click Read and wait 5-10 mins for your nvitems to be read. SAVE THE TEXT FILE somewhere where you won't loose it and MAKE A BACKUP. Email it to yourself and upload it to dropbox. If you loose this file then you could permabrick your device!
9. Download the AWS ATT NvItems unlock file HERE Click DOWNLOAD and save the txt file to your desktop or somewhere where you will remember.
10. Open or go to NV-items_reader_writer.exe. Do the connect, MSL, read and select com port if you closed the app. Click WRITE and select the text file you downloaded in step 9 "nv aftr qxdm removed imei.txt". After writing click on Mode and Reboot or simply reboot your phone.
At this point you are on a Sprint Rom/Kernel/Modem with a GSM compatible radio. Your Sprint software has no idea what is going on and most likely won't connect to GSM even with a SIM card inserted. If you go into Settings->Mobile networks you wont see options to set APN. This is because the Sprint ROM/Radio isn't setup to connect to GSM. Try THIS to "unlock" US GSM couriers on Sprint ROM
11. Flash this ATT ROM: (others may work, although you need a ROM with NO included Kernel/Modem)
HERE
This is the [ROM][4.1.2][XXDLL1] Asylum TJ v1ROM with no modem/kernel/etc. Wipe Dalvik, factory reset, cache. I also wiped system before installing but you may not need to.
12. Boot and verify the rom boots.
At this point you can experiment with the Mobile Networks settings and should see APN options. Change your Network mode and see if you can get any listings for "Network operators" when selecting manual. If you can see ATT/T-MOBILE then report your findings!
13. Next is to flash over a ATT modem/radio in TWRP. Download the modem HERE
THIS MODEM WILL CAUSE YOUR DEVICE TO BOOT LOOP. Although I found on my device it only rebooted every 5 mins or so.
14. After booting you should be able to see ATT/TMOBILE in your network operators settings. Make sure to play with Network mode. I don't have a SIM card and so my lockscreen said "Emergency Calls Only" and I couldn't get into the Mobile Networks menu as it told me to "Please insert SIM card"
At this step I'm fairly certian the GSM bands are unlocked as most people only see Emergency Calls Only when their device is not registered. Normally this is caused by invalid or unauthorized SIM/IMEI/APN settings on a normal GSM phone.
RECOVERY
1. Download Sprint firmware HERE
2. Extract the ZIP to your desktop so you have the "COMBINATION_L900VPLJ1_L900VPALJ1_CL265523_HWID04_HW-Rev0406_user_low_ship.tar.md5" file on your desktop
3. Go into download mode HOW TO
4. Open Odin from C:\Samsung Galaxy Note2 ToolKit\Odin3_v3.07.exe
5. Connect your device
6. Click PDA and select "COMBINATION_L900VPLJ1_L900VPALJ1_CL265523_HWID04_HW-Rev0406_user_low_ship.tar.md5"
It will check MD5 and it'll take a minute
7. Click Start and wait for your device to flash & reboot.
8. Dial *#7284# and go to Qualcomm USB Settings and select RNDIS+DM+MODEM.
9. Open NV-items_reader_writer.exe
10. Find your COM port from earlier in your device manager, same as last time
11. Connect, Read. IF YOU GET SPC ERROR TYPE YOUR MSL or TRY 000000
12. Click Write and select your NV-ITEMS BACKUP .txt FILE
13. After writing click on Mode and Reboot or simply reboot your phone.
14. Dial *#7284# Qualcomm USB Settings and select MTP+ADB
You should now have a fully operational Stock device.
To enable USB file transfer at anytime dial *#7284# Qualcomm USB Settings and select MTP+ADB
If you have issues past this point then you didn't follow instructions completely or you experienced something different then what I experienced. The most important step of unbricking is restoring your NV-ITEMS. Odin flashing of stock firmware/etc is normal procedures as per any unbrick. You are welcome to try modifying the ATT modem to not bootloop (most likely LTE issues as Sprint radio doesn't operate on ATT LTE frequencies) by following THIS post. You can also try the Sprint ROM/Modem by following the Verizon APN/Network hack HERE
Some roms won't let you do *#7284# for ADB/MTP. The way around this (if you need to transfer files and MTP isnt anabled) is to sideload files from TWRP or find the verizon method for dialer codes for Qualcomm USB settings menu. There was a dialer only instruction post but I can't find it now. If all else fails then simply ODIN to stock.
Impressive work you are attempting. It would def be cool to have the same radio functionality that Iphone 5 peeps have. I am on AT&T, but it would be cool to be able to load the CDMA and related stuff to a GSM phone as well. Good luck, I will be foloowing your thread, mostly out of curiosity.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I can successfully see a ATT/T-Mobile GSM network type with the NV-Items hack. I need to do the sim card mod now. I'll order parts this weekend and until then there isn't too much I can do.
rockerrock said:
I can successfully see a ATT/T-Mobile GSM network type with the NV-Items hack. I need to do the sim card mod now. I'll order parts this weekend and until then there isn't too much I can do.
Click to expand...
Click to collapse
Great news! Excellent work by the way, would love to see this end up working!
I can now run a ATT flashed modem. When selecting Mobile Networks it tells me to insert a sim card. I'm getting reboots every 3-5 minutes but I think it's kernel related. The ROM is half the battle, ATT modem boot looped on SPR ROM. I should be able to connect to GSM once I do the SIM hack for proof of concept.
Recap:
NV-Items of the ATT to T-Mobile flashed (AWS/GSM unlock, use both ATT and Tmobile on ATT GN2)
Flashed ATT ROM
Failed flashing ATT Persues kernel (stuck at samsung logo)
Flashed Sprint Persues kernel
Flashed ATT modem
I desperately need the NV-ITEMS from an international phone in txt format.
http://forum.xda-developers.com/showthread.php?p=36559274
this may have nothing to do with what your doing but ill ask anyway I ported a verizon note 2 rom over to sprint galaxy note 2 and everything works but LTE is it possible to get it to work? Its the JellyBeans Rom in the sprint forum
From my understanding the customization of the chipset is in relation to LTE frequencies which are hawdware related. It's the same for the Nexus 4, it supports LTE unofficially on band 4 due to LG keeping in their Optimus LTE chip. Nexus 4 on LTE only works in certain areas in the country due to ATT only providing LTE band 4 in very limited areas.
I doubt I can "unlock" to the point where a Sprint/Verizon phone can see each other's LTE frequencies as LTE is a different chip in question (most frequently) as LTE courier customization is specific to the courier/device.
I may be wrong as it depends on the chip in question and how it's implemented. I need to find a photo of both Sprint/Verizon mainboards and compare. My work focuses on GSM/AWS bands for HSDPA+ and 3G as it is more likely to work as the chipset known supports these bands. Please feel free to post pics of the boards or chipset info and I'll look into it.
Due to my NV-Items trick I now can use QPST to dump a full nvitems+more. I cannot restore items though
When in GSM mode I'm getting an Emergency Calls Only/Enter SIM which means it should work with a SIM chip.
ATT modem + ATT/AWS nvitems unlock on ATT ROM; SPR Kernel.
Buying a cracked screen working ATT Note 2 sometime today for $325 for additional testing
rockerrock said:
Due to my NV-Items trick I now can use QPST to dump a full nvitems+more. I cannot restore items though
When in GSM mode I'm getting an Emergency Calls Only/Enter SIM which means it should work with a SIM chip.
ATT modem + ATT/AWS nvitems unlock on ATT ROM; SPR Kernel.
Buying a cracked screen working ATT Note 2 sometime today for $325 for additional testing
Click to expand...
Click to collapse
Seems like your making progress
Sent from my SPH-L900 using xda premium
I'm following your thread with a lot of enthusiasm.
Sent from SHV-E250/N7105 w/ SJKernel using XDA apps developers app premium.
Post #2 contains instructions.
I have just found a Verizon hack thread to get US GSM data/voice working without all this hacking. I'll try it out and report back
http://forum.xda-developers.com/showthread.php?t=2044449
Flashed Deodex Vzw ROM:
http://forum.xda-developers.com/showthread.php?t=2044351
Flashed APN editor:
http://forum.xda-developers.com/showthread.php?t=2044449
I can see verizon networks, no LTE. Trying GSM now.
Yeah, I really doubt you will get VZW LTE working as for one you will not Auth with their system. Second I am sure the transceiver in our version of the phone is not capable of that frequency on the LTE path.
-- "Sensorly or it didn't happen!"
digiblur said:
Yeah, I really doubt you will get VZW LTE working as for one you will not Auth with their system. Second I am sure the transceiver in our version of the phone is not capable of that frequency on the LTE path.
-- "Sensorly or it didn't happen!"
Click to expand...
Click to collapse
Agreed, my goal is to get HSDPA GSM data working on Sprint Note 2. Verizon allready has a method of unlocking http://forum.xda-developers.com/showthread.php?t=2044449. I do agree that it's impossible for LTE to work on any method as LTE chip is a whole different ballgame than what I'm attempting. It may be possible but someone would have to start by getting a VZW and SPR mainboard and comparing chips. Even if you somehow get the radio working you would might need to hack the ESN which is ILLEGAL, although VZW does use SIM cards..
However I can see VZW frequencies on my Note 2 right now. Alternating between EVDOa and eHRPD.
rockerrock said:
Agreed, my goal is to get HSDPA GSM data working on Sprint Note 2. Verizon allready has a method of unlocking http://forum.xda-developers.com/showthread.php?t=2044449. I do agree that it's impossible for LTE to work on any method as LTE chip is a whole different ballgame than what I'm attempting. It may be possible but someone would have to start by getting a VZW and SPR mainboard and comparing chips. Even if you somehow get the radio working you would might need to hack the ESN which is ILLEGAL, although VZW does use SIM cards..
However I can see VZW frequencies on my Note 2 right now. Alternating between EVDOa and eHRPD.
Click to expand...
Click to collapse
Side note... Altering an ESN isn't just caps illegal, it is caps/bold/underscored/red font illegal. A federal felony from what I've read.
Sent from my SPH-L900 using Tapatalk HD
Skripka said:
Side note... Altering an ESN isn't just caps illegal, it is caps/bold/underscored/red font illegal. A federal felony from what I've read.
Sent from my SPH-L900 using Tapatalk HD
Click to expand...
Click to collapse
Yup, modifying ESN has absolutely nothing to do with my research. My goal is to utilize a provider's SIM on GSM to connect to ATT/TMobile with stock IMEI/ESN. Verizon uses a SIM in their Note2/S3 in which if they accept your ESN/IMEI with their SIM is their discretion. ESN/IMEI, etc is stored in NV Items which is in the modem baseband, not the ASIC. Swapping SIM cards are perfectly legal so removal/replacement of the embedded SIM is legal. ESN/IMEI is like a car's VIN which is illegal to touch, SIM is more like a license plate on a car. I'm a firm believer in its your device do what you want but once you enable your modem to interact with the public infrastructure you are bound to it's rules, period.
On another note I have a ATT Note 2 now but I sold the Sprint Note 2 to get the Nexus 4. I can continue my research into GSM on my Sprint S3 and provide dumps for the ATT Note 2.
I'm fairly certain that I have accomplished a US GSM unlock on my Sprint Note 2 as it exhibits the same symptoms as a Unlocked phone without a SIM, Emergency Calls Only. However I do not see ATT/T-Mobile in my network operators menu which I'm sure the VZW APN hack will fix or it's because I don't have a SIM.
It's going to take someone with a Sprint S3/Note 2 with SIM mod and some tinkering around to get this to work. I'll get a SIM board for my S3 but it's going to take some time as I'm busy with work and my girlfriend. If anything was learned, it was that the S3/Note 2 is pretty much damn near unbrickable. I've flashed every firmware known to man, trashed my NV ITEMS, wiped my ESN/MSL and recovered to absolutely working activationable stock. Don't be afraid to experiment, just BACKUP and BACKUP your BACKUPS.
I am stuck at this step:
13. Next is to flash over a ATT modem/radio in TWRP. Download the modem HERE
THIS MODEM WILL CAUSE YOUR DEVICE TO BOOT LOOP. Although I found on my device it only rebooted every 5 mins or so.
It does cases boot loop, only it's not every 5 minutes, but instantenious, right after "Android is upgrading" Am i missing something?
Update: with ATT ROM, it does give me 2-3 minutes before reboot, however it won't see the Sprint SIM with ATT modem file. I've also tried few other modems from Verizon and some other GN2 carriers, same story. currently i have no SIM mode installed, but I think it should still see SPRINT chip/SIM because it is emmulating a LTE/GSM SIM. SIM manager says SIM state unknown.
Is this the same for you? how are you able to see the T-mobile and AT&T , if you can't get n to the mobile networks menu?
rockerrock said:
Agreed, my goal is to get HSDPA GSM data working on Sprint Note 2. Verizon allready has a method of unlocking http://forum.xda-developers.com/showthread.php?t=2044449. I do agree that it's impossible for LTE to work on any method as LTE chip is a whole different ballgame than what I'm attempting. It may be possible but someone would have to start by getting a VZW and SPR mainboard and comparing chips. Even if you somehow get the radio working you would might need to hack the ESN which is ILLEGAL, although VZW does use SIM cards..
However I can see VZW frequencies on my Note 2 right now. Alternating between EVDOa and eHRPD.
Click to expand...
Click to collapse
Seeing PCS and CLR VZW is easy. I don't think you will auth on ehrpd though.
Did you ever get past the failure to read roaming list issue. Was curious if you found a way to read the PRL from the Note2.
-- "Sensorly or it didn't happen!"
Let me know if you would like me to test your theory.
sent from my phone using rocket fuel

p607t lte/wcdma not working

I have received a p607t tablet, it was flashed by smb. to p905 firmare (with no imei). i re-flashed it with stock P607TUVUBOI2 firmware (4 files, so-called "service" firmare), imei is back (to what is printed at the back-side) but mobile networking *still* doesn't work: no connection. I'm using not t-mo sim-card, but looks like the tablet was already unlocked
From service menu *#0011#:
SERVICE : LIMITED
NETWORK : UNBLOCK
IMEI Certi: PASS, 1
From Advanced Signal Status:
Carrier:
Network Type: Unknown
Signal info: n/a
Neighboring CID: no neighboring cells --- wtf? >> other devices work ok with this sim in lte and 3g modes<<
GSM service: emergency calls only
GPRS service: disabled
Any ideas?
OK, so, what is done with p607t to the moment:
1) reflashed CP (modem/RF??) to latest stock (P607TUVUBOI2)
2) reflashed AP/PDA (core system??) and CSC (consumer stuff??) to P605XXU1EOI5 (from p605, have one right here - it never had network-lock from factory)
3) using qpst and qxdm changed nv parameters (extended lte bands, enabled gsm rf-bands - there were none in stock at all, only wcdma)
now the tablet sees my local gsm network with this sim-card, signal is 4/5 bars, but still no internet connection - WTF??
p.s. when trying manually to register in my local network - it fails with "try again later"
p.p.s.: what is i find weird, in service menu *#0011#:
NETWORK : UNBLOCK
- this line exists only on p607 - is this the key?
Then, i insert this sim into p605 (completely stock P605XXU1EOI5) - it works like a charm
need some help - where to dig next? point direction plz
UPDATE. i've been tweaking 607t nv items with qxdm, making it alike that ones 605 has. practically everything is alike now, but still it doesn't even try to establish data connection with cell...((
btw, 605 does not have "esf embedded file system", while 607t has one (can be seen through qpst-esf explorer)
also, some nv-items present in one model, some present in another
m4D2016 said:
UPDATE. i've been tweaking 607t nv items with qxdm, making it alike that ones 605 has. practically everything is alike now, but still it doesn't even try to establish data connection with cell...((
btw, 605 does not have "esf embedded file system", while 607t has one (can be seen through qpst-esf explorer)
also, some nv-items present in one model, some present in another
Click to expand...
Click to collapse
I had to flash back to the original kitkat firmware and take OTA to upgrade to lollipop. There is a known issue with the 607t losing data after roms are flashed. Some had luck with flashing the same rom twice but it never worked for me. Used Sam mobile to pull original and went from there. Good luck
I performed "device init and reflash" with Keis. The device is back to stock completely, except:
- nv items data
- esf embedded file system data
so... my guess - i need to restore these in order to have mobile networking working.
could someone post a qcn-file with factory esf-data?
ok, let's take another way: how can i get some gsm-module debug-output or log to understand, what's going on it?
i'm trying to write some custom modem.bin to /dev/block/mmcblk0p2, but after reboot data in there is reverted to stock modem.bin - how come?? is that bootloader doing? where is the stock-one stored?

Device doesn't connect to mobile network

I was on PixelExperience (latest) and yesterday flashed through Magisk 17.0 and 17.1. Today morning device couldn't connect to mobile network at all (2G/3G/4G/LTE). Wiped it completely, flashed latest dev firmware and Nitrogen OS + unofficial Gapps for Android Pie. Everything works quite smooth, but still my device can't connect to mobile carrier - any ideas what I can try? It's crucial for me to fix it today since I need to be able to send/receive SMS tomorrow.
Tried switching sim slots?
Just to see if the sim card works with the other slot.
Does an IMEI number show for both slots under settings - about? (Don't tell us your IMEI)
Are you sure your network provider hasn't cut you off by mistake or some other weird account based issue?
Try another sim if you can get one.
A pay as you go sim without credit should still show a connection even if you can't use it
Yeah, I did try.
1. Tried other card (got polish Orange card which connects to EE, UK EE card - both work in my brother's SGS6).
2. IMEI is okay, don't know if IMEI SV should be 00 though.
3. Cards work okay in SGS6.
99% it's software issue - I've used Magisk modules to widen Wi-fi bands and other modules - I did format all partitions and flashed latest stable Global MIUI through fastboot though and it should override all the settings. I've used the *#*# code and I can't pass the test.

My phone doesn't detect SIM*card with lineage OS

Hi,
I recently bought a second hand smartphone Galaxy S4 GT-9505 which according to IMEI info was first delivered on 2013 r. and uses a Qualcom Snapdragon 600 APQ 8064T chipset and is powered by a 4.2 Jelly Bean android version. I use a French Orange SIM card that works normally on other phones.
I installed the recommended version of LineageOS for this device.
The installation went smoothly and the system boots normally. Nevertheless, after booting I can see a barred SIM card icon on top of the screen.
In the Mobile network settings only one entry is available, i. e. :
- Data roaming is greyed and not accessible
- Preferred Network type is greyed and not accessible
- Connected line identification is accessible
- Access Point Names is greyed and not accessible
- Network Operators is greyed and not accessible
Finding a tuto dealing with this kind of issue, I phoned *#*#4636#*#* . Then I could go to Phone info menu and there I could see this :
IMEI : my imei
Phone number : unknown
Current Network :
Signal strenght :
Voice Service:
Data Service: Disconnected
Voice Network Type: Unknown
Data Network Type: Unknown
Voice Call Status:
Roaming:
Set Preferred Network Type: here is a dropdown list. According to the tuto I tried every value but all of them failed to revive anything.
Is this a known issue and what can I do ?
Same can't find any info. I am using a oneplus T6

Categories

Resources