Related
Hey guys,
after replying to several other threads i decided to make this a thread on it's own.
i tried to root my nexus 7 3G - "nakasig" with the two toolkits. also i tried it manually pushing the root stuff via adb.
when on stock + unlocked bootloader i have normal 3g connection but after the root it just says "no sim card". still i can search for networks but it doesnt let me connect to them. its as if the sim slot would lose its drivers or something. any ideas on that?
I'd be really happy if any of you would help me, im out of options i suppose...
cheers,
mo
Same problem here. Any news on that?
Here is a quick solution to your problem: STOP USING TOOLKITS!
The process is ridiculously simply. By using these automated tools, you're just asking for problems. And when one occurs, you have no idea how to troubleshoot it.
I wouldn't be surprised if the toolkit you used doesn't support the 3G model and probably broke the 3G capabilities.
1) Unlock bootloader if it hasn't already been done.
2) Flash custom recovery of your choice (make sure it's capable of supporting 4.2 multi-user)
3) Put an "su" flashable zip on sdcard.
4) Go into custom recovery and flash it.
5) Reboot
Voila. Done.
In fact, I didn't use any Toolkit (I want to control everything on my own, and am not afraid of using the console/adb).
Here are the steps, I did:
1. Unlock bootloader (fastboot oem unlock)
2. Boot custom recovery (fastboot boot [recovery.img])
3. Mount /system in recovery
4. adb shell -> put su in /system/bin -> put Superuser.apk in /system/app (and chmodded su to 06755, Superuser to 0644)
5. restarted, no 3G available
The problematic step could be the second, I used the "recovery-clockwork-touch-6.0.1.0-grouper.img", which is not specially for the N7-3G (called nakasig). Is there a better recovery Image?
I didn't want to flash the recovery, so I just booted into it. Could this be the problem?
Best regards
kroegerama said:
In fact, I didn't use any Toolkit (I want to control everything on my own, and am not afraid of using the console/adb).
Here are the steps, I did:
1. Unlock bootloader (fastboot oem unlock)
2. Boot custom recovery (fastboot boot [recovery.img])
3. Mount /system in recovery
4. adb shell -> put su in /system/bin -> put Superuser.apk in /system/app (and chmodded su to 06755, Superuser to 0644)
5. restarted, no 3G available
The problematic step could be the second, I used the "recovery-clockwork-touch-6.0.1.0-grouper.img", which is not specially for the N7-3G (called nakasig). Is there a better recovery Image?
I didn't want to flash the recovery, so I just booted into it. Could this be the problem?
Best regards
Click to expand...
Click to collapse
I had issues on my 16GB unit with that version of CWM on 4.1.2. I ended up using the 'beta' version 6.0.1.5 - it''s on XDA somewhere. When I got my N7 3G, I used the latest version of TWRP, and it works great.
But, based on what you are saying, none of that should even matter. In your case, you're not actually flashing a SU zip, you're manually installing it yourself (I did the same thing). So as long as you are able to mount /system and modify it's contents, which you obviously did, that's fine. The only thing I did differently was install su into /system/xbin, but /system/bin should be fine too.
Does 'su' and the SuperUser app work? If so, then that means your modification was successful.
Assuming that's all you did, I can't think of any reason why that would have broken 3G support. Is everything else 100% stock? If you flashed a custom kernel, it probably won't support 3G. The only one that I know of that DOES work is faux123's beta version.
Can you describe your issue a little more? Does the tablet display signal strength but just not get data? I'm assuming you disabled wifi to test, right?
Does 'su' and the SuperUser app work? If so, then that means your modification was successful.
Click to expand...
Click to collapse
Yes, they did. For example, I could install AdAway, which was able to change the hosts-file.
Assuming that's all you did, I can't think of any reason why that would have broken 3G support. Is everything else 100% stock? If you flashed a custom kernel, it probably won't support 3G. The only one that I know of that DOES work is faux123's beta version.
Click to expand...
Click to collapse
I didn't change anything. Just did the steps I described earlier...
Can you describe your issue a little more? Does the tablet display signal strength but just not get data? I'm assuming you disabled wifi to test, right?
Click to expand...
Click to collapse
Sure, I disabled WIFI. The signal strength display has all 4 bars (full reception), but no "H" or "3G" is displayed and also the bars are grey and not blue.
The weird thing is, that if I check "Use only 2G-Networks", I get blue bars with "G" and can access the internet...
kroegerama said:
Yes, they did. For example, I could install AdAway, which was able to change the hosts-file.
I didn't change anything. Just did the steps I described earlier...
Sure, I disabled WIFI. The signal strength display has all 4 bars (full reception), but no "H" or "3G" is displayed and also the bars are grey and not blue.
The weird thing is, that if I check "Use only 2G-Networks", I get blue bars with "G" and can access the internet...
Click to expand...
Click to collapse
Hrmmm....
I had the exact same issue (gray bars, no Internet), but it was because I flashed a non-3G compatible kernel. Once I replaced that, it started working properly again. I assume it worked fine prior to rooting, correct?
I still can't think of any reason why adding the su binary and SuperUser application would cause any issues with 3G connectivity. The two things have nothing to do with each other. Especially since you did it manually (which eliminates the possibility of some overzealous flashable zip. Hell, you didn't even flash a custom recovery but booted off it of it from your PC.
Have you tried rebooting since, to see if that cleared things up?
Just for the sake of eliminating them as a variable, why don't you try removing su and superuser.apk and see if that fixes it. I doubt it will, but it's worth a short.
The only other thing I can think of is for you to try reflashing the full 4.2 image (sans userdata) and see if that fixes the problem. Something else might have gotten broken and that should fix it.
Well, actually I don't know, if HSPA worked before rooting, because it was the first thing I did with my new N7
I rebooted a thousand times, toggled Airplane-Mode another thousand times and nothing helped. Now, I have reverted everything completely to stock:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.13.img
fastboot reboot-bootloader
fastboot flash radio radio-tilapia-1231_0.10.0_1021.img
fastboot reboot-bootloader
fastboot -w update image-nakasig-jop40c.zip
After that i locked the bootloader (oem lock). And guess what? I still can't get HSPA connection
I checked the SIM card in my Smartphone (N4 btw) and it worked fine, so it can't be the problem.
Do you think, I have to send my N7 back, because it has a hardware-error?
kroegerama said:
Well, actually I don't know, if HSPA worked before rooting, because it was the first thing I did with my new N7
I rebooted a thousand times, toggled Airplane-Mode another thousand times and nothing helped. Now, I have reverted everything completely to stock:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.13.img
fastboot reboot-bootloader
fastboot flash radio radio-tilapia-1231_0.10.0_1021.img
fastboot reboot-bootloader
fastboot -w update image-nakasig-jop40c.zip
After that i locked the bootloader (oem lock). And guess what? I still can't get HSPA connection
I checked the SIM card in my Smartphone (N4 btw) and it worked fine, so it can't be the problem.
Do you think, I have to send my N7 back, because it has a hardware-error?
Click to expand...
Click to collapse
Since you did that full flash (include the -w which wipes userdata), your N7 is completely back to stock.
There is definitely a possibility of a hardware issue, but before we assume that, there's one other possibility that comes to mind since you said you didn't know if it worked before.
What type of SIM card are you using? Is it the AT&T one that it came with? If so, did you activate it? If you did activate it, did you activate it through the tablet? When you turned off wifi, did it popup with a notification about logging into the AT&T network? If you activated it on the tablet, did you complete the whole process and receive the SMS and email?
And finally, the one thing that comes to mind as the possible problem if you are using that AT&T SIM card and it was activated:
What APN are you using? Mine came with two. The default is the one you use to register the SIM and activate it. The second APN is the normal usage one. After my activation, I was still on the registration APN and had to manually switch to the other one. If that is the case for you, and you are still on the registration APN, that could explain the issue. Try changing it to the other one and see if that fixes it.
No, I'm not at AT&T. Actually, I don't live in the US at all, I'm in Germany.
But I double-checked my APN-Settings and they seem to be set correctly. Also the SIM card is activated, as I'm able to use it in my Smartphone...
I've got one question, though: In the drop-down quick-settings pane, do you have a panel with your carrier name on it?
My Nexus 4 has one, but the Nexus 7 doesn't...
kroegerama said:
No, I'm not at AT&T. Actually, I don't live in the US at all, I'm in Germany.
But I double-checked my APN-Settings and they seem to be set correctly. Also the SIM card is activated, as I'm able to use it in my Smartphone...
I've got one question, though: In the drop-down quick-settings pane, do you have a panel with your carrier name on it?
My Nexus 4 has one, but the Nexus 7 doesn't...
Click to expand...
Click to collapse
Ah, well that eliminates my possible explanation.
No, I do not see that carrier name in either drop down. However, the carrier name should be on the bottom of the lock screen.
Are you 100% sure that the carrier in question will support the N7? I ask, because apparently people are having issues with T-Mobile SIM cards in the US. They work perfectly fine in a phone and/or other device, but when they put them in the N7 - nothing. Sounds like a similar issue. It seems like T-Mobile is blocking the N7 IMEIs from using standard voice or data packages.
I think the only real way to tell whether it's a hardware issue or not is if you have a friend with an N7 3G that you could try the SIM card in. That, or try buying some cheap prepaid one that you can use for a day or so.
But with what your saying, I'm thinking it very well might be a hardware issue for you.
Just to clarify:
- Which carrier is your SIM card from?
- Do you get 3G with that SIM in a smartphone? If so, which smartphone?
- My SIM is from "O2 - DE" (O2 Germany)
- Yes, I get 3G in a smartphone. It's a Nexus 4.
Are you 100% sure that the carrier in question will support the N7? I ask, because apparently people are having issues with T-Mobile SIM cards in the US. They work perfectly fine in a phone and/or other device, but when they put them in the N7 - nothing. Sounds like a similar issue. It seems like T-Mobile is blocking the N7 IMEIs from using standard voice or data packages.
Click to expand...
Click to collapse
Well, I'm not really sure, if my carrier blocks Tablets. I asked google, but no one else reported Tablet-blocking in the o2-network. But to be sure, I will test a friend's SIM card from vodafone tomorrow in my N7.
Sadly, I can't test my SIM in another N7-3G, because I don't know anyone who owns one.
So just to be sure, you are using the same APN settings on the N7 that you have in your Nexus 4?
Another thought - I have heard that with some European MVNOs, and even primary carriers that share networks with other providers, sometimes Android considers you to be roaming. Have you tried enabling data roaming just to see?
And when 2G-only is disabled, have you tried going into the mobile networks list to scan and ensure you are connected to the right network?
cmstlist said:
So just to be sure, you are using the same APN settings on the N7 that you have in your Nexus 4?
Click to expand...
Click to collapse
Yes, I used the correct settings in both devices...
cmstlist said:
Another thought - I have heard that with some European MVNOs, and even primary carriers that share networks with other providers, sometimes Android considers you to be roaming. Have you tried enabling data roaming just to see?
Click to expand...
Click to collapse
I enabled data roaming, but that also didn't help.
cmstlist said:
And when 2G-only is disabled, have you tried going into the mobile networks list to scan and ensure you are connected to the right network?
Click to expand...
Click to collapse
When I tap on the scan-button, it loads a few seconds and then says "Fehler bei der Netzwerksuche" (translated: "error while searching for networks")
kroegerama said:
When I tap on the scan-button, it loads a few seconds and then says "Fehler bei der Netzwerksuche" (translated: "error while searching for networks")
Click to expand...
Click to collapse
Yeah Android tends to do that a lot. Usually if that happens I toggle airplane mode off and on, and then try the list again. Sometimes it takes ten minutes of trying to finally get a successful scan for networks that lists all the carriers it can see.
Sent from my Galaxy Nexus using Tapatalk 2
Ok, I was now able to get to the carrier list and manually selected the correct one. But that didn't help either.
When the other SIM card, which I will test tomorrow, also doesn't get 3G access, I will send the device back to google and hope, they replace it for me...
Ok, seems like my N7 has a defect. I will call google to ask for a replacement N7...
kroegerama said:
Ok, seems like my N7 has a defect. I will call google to ask for a replacement N7...
Click to expand...
Click to collapse
Glad to hear you finally got confirmation. Based on your troubleshooting, that was looking more and more likely. I'm sure Google will replace it for you properly.
I just called google and they will send me a new N7. And when the new one arrives, I have to put my defect one in the box and send it back. That's very customer-friendly. So I can use the N7 (without 3G) until I get the new one
I've followed jk's guides to root and flash the PB1 deodexed stock rom v9 to my Verizon s5. Amazing thank you!
Thing is I have a uk number and can't send sms texts on account of smsc being locked to Verizon's.
Sending to 07.. formatted numbers works, but apps default to +447.. format..
Tried everything including changing settings in Advanced Signal Status.
Can use NextSMS app as it doesn't default to +447.. format. But this is inconvenient for new numbers I'm replying to.
Is there a 'deeper' method for changing smsc settings?
In Advanced Signal Status I go to the smsc box and enter +447782000800 which is the smsc for my carrier, I click update.then when I click refresh it reformats number to
"447782000800",145
I think this could be part of problem?
Figured out
There was no way I could get it to work.
In the end I followed the guides to..
Root
Unlock bootloader
Flash twrp via odin
Update bootloader
Flash twrp via ordinary again to fix sd card issue.
Install CyanogenMod 13 + opengapps 6.0 mini
Im sure the following would also work..
Root
Unlock bootloader
Flash twrp via odin
Install CyanogenMod 12 + opengapps.
I'm loving CM13 with opengapps. Pleasant interface, fast, stable, and only takes 1.2GB of internal storage!
Not going back to stock ROMs now!
Hello, everyone! I was hoping maybe you could give me your opinion on the following issue:
About a year ago I purchased a Moto X Play XT1562 in Europe with dual sim support (Asian ROM). I knew beforehand that I'd probably have limited LTE coverage in my country (Argentina), since the bands used by carriers here are B4 and B28, and XT1562 only supports B28 (which is used mostly for coverage in suburbs and rural areas). Band 4 is the main band used in Argentina for LTE coverage in cities and XT1563 is the model that supports it.
For quite some time I've had the theory that most phones should support more bands than they show, and that the differences between various models of the same phone are there to introduce region restrictions, which in turns means that some LTE bands are disabled and that it should be possible to somehow enable them by tweaking the software. For what I've read, there seems to be some support for my theory: there's a thread in this very same forum which claims that it should be possible to unlock all LTE bands in devices with Qualcomm processors by rooting the phone, installing a custom ROM and kernel and changing a few values.
LINK: https://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
Now, I'd really want that to be the last thing I try. I've rooted my phone before and I even unrooted it by flashing stock ROM, so I know my way around, but flashing a custom ROM and kernel are things I'd rather not do right now.
So, that brings me to my second theory: since XT1562 and XT1563 are basically the same device, their hardware specifications are the same and only differ in the LTE bands they support... and since LTE bands seem to be software-restricted...
1) Could it be possible to unlock Band 4 by flashing XT1563 stock ROM to my XT1562 Moto X Play?
2) Has anyone tried to do that (even by mistake) without bricking the device?
3) If there's no option but to flash a custom ROM and kernel, does anyone know for sure if LTE bands in Moto X Play are software restricted? Or is there a hardware limitation?
Probably my secornd theory won't work because I don't think the solution would so simple, and there would be threads about it... but I guess I don't lose anything by asking
Thank you!! =)
Just realized this thread shouldn't go in General. Could someone please move it to Q&A? Thanks!
The frequency bands that your phone supports is region specific (as you guessed) and has legal implications. And just like your device IMEI, these values are found in the non-volatile memory of your phone. The values are basically on partitions that are much secure and not so easily editable (like by fastboot or recovery). But nevertheless, the values are "software" only, and so it must be possible to edit the values anyway (just like it is possible to edit the IMEI), one way of doing so is using Qualcomm software as in the link you had posted.
But this varies from device to device, vendor to vendor, so your second theory could actually work on our phones (really don't think so though).
While it might be possible to run ROMs for XT1563 on XT1562, the baseband/ modem for XT1563 would not work on XT1562; it would probably make your device show "unknown" for IMEI, and so you would get no SIM network. Flashing back the modem for XT1562 would probably fix it.
You could always try and find out...
You would need the NON-HLOS.bin and fsg.mbn files from the XT1563 stock image to try, and the same files from the XT1562 stock to revert back.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
There's chance that you would be stuck with an "unknown" IMEI and then you would have to manually edit volatile memory values after all. This all is just theory, someone who has tried or someone who has more knowledge will be able to help you better.
DragonClawsAreSharp said:
The frequency bands that your phone supports is region specific (as you guessed) and has legal implications. And just like your device IMEI, these values are found in the non-volatile memory of your phone. The values are basically on partitions that are much secure and not so easily editable (like by fastboot or recovery). But nevertheless, the values are "software" only, and so it must be possible to edit the values anyway (just like it is possible to edit the IMEI), one way of doing so is using Qualcomm software as in the link you had posted.
But this varies from device to device, vendor to vendor, so your second theory could actually work on our phones (really don't think so though).
While it might be possible to run ROMs for XT1563 on XT1562, the baseband/ modem for XT1563 would not work on XT1562; it would probably make your device show "unknown" for IMEI, and so you would get no SIM network. Flashing back the modem for XT1562 would probably fix it.
You could always try and find out...
You would need the NON-HLOS.bin and fsg.mbn files from the XT1563 stock image to try, and the same files from the XT1562 stock to revert back.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
There's chance that you would be stuck with an "unknown" IMEI and then you would have to manually edit volatile memory values after all. This all is just theory, someone who has tried or someone who has more knowledge will be able to help you better.
Click to expand...
Click to collapse
Thank you for your kind reply =)
So, if I understood correctly, there's no need to flash the full XT1563 stock image. I'd just have to flash those two files from XT1563 stock rom, and then if it doesn't work then I'd just flash the XT1562 files again, which I already have. Seems worth to try and with low risk of bricking my phone.
Now, if that doesn't work, then my only option would be to use the other method. I don't want to try that one yet because I don't have everything figured out: I'm stuck in step 6, "Open the USB settings screen on your phone." I haven't yet found the correct code to input in the phone's dial screen to edit USB settings. I think in Android 6 the USB options have all been moved to developer mode, but I'm not 100% sure yet.
floydian86 said:
Thank you for your kind reply =)
So, if I understood correctly, there's no need to flash the full XT1563 stock image. I'd just have to flash those two files from XT1563 stock rom, and then if it doesn't work then I'd just flash the XT1562 files again, which I already have. Seems worth to try and with low risk of bricking my phone.
Now, if that doesn't work, then my only option would be to use the other method. I don't want to try that one yet because I don't have everything figured out: I'm stuck in step 6, "Open the USB settings screen on your phone." I haven't yet found the correct code to input in the phone's dial screen to edit USB settings. I think in Android 6 the USB options have all been moved to developer mode, but I'm not 100% sure yet.
Click to expand...
Click to collapse
At step 6, you are basically trying to connect the phone to your PC in a vulnerable mode (Modem + Diag mode) so you could access the NV. On Moto phones this is not really possible by dialing a service code I think.
Did you try to boot your phone in BP tools (or QCOM?) mode from fastboot? Then connect to PC and it should be connected in diag mode (check in Device Manager to confirm). You might need some specific drivers, see last thread, or may be Google.
There is a lot of discussion about this on the internet (for other devices, mostly). Mostly because people with locked devices that work only on specific carriers use a similar edit of values in NV of the phone to get out unlocked.
I think you should Google and try out some of the things people have been suggesting.
Read here, post number 21, for example (the entire thread is pretty informative): https://forum.xda-developers.com/moto-x/moto-x-qa/unlock-lte-bands-moto-x-t2933475/
And here (for Moto X Play),
http://forum.xda-developers.com/moto-x-play/help/trouble-writing-nv-settings-moto-x-play-t3368261
Edit: Most of these NV and QPST threads do seem to repeatedly point out that writing on the NV is extremely risky.
DragonClawsAreSharp said:
At step 6, you are basically trying to connect the phone to your PC in a vulnerable mode (Modem + Diag mode) so you could access the NV. On Moto phones this is not really possible by dialing a service code I think.
Did you try to boot your phone in BP tools (or QCOM?) mode from fastboot? Then connect to PC and it should be connected in diag mode (check in Device Manager to confirm). You might need some specific drivers, see last thread, or may be Google.
There is a lot of discussion about this on the internet (for other devices, mostly). Mostly because people with locked devices that work only on specific carriers use a similar edit of values in NV of the phone to get out unlocked.
I think you should Google and try out some of the things people have been suggesting.
Read here, post number 21, for example (the entire thread is pretty informative): https://forum.xda-developers.com/moto-x/moto-x-qa/unlock-lte-bands-moto-x-t2933475/
And here (for Moto X Play),
http://forum.xda-developers.com/moto-x-play/help/trouble-writing-nv-settings-moto-x-play-t3368261
Edit: Most of these NV and QPST threads do seem to repeatedly point out that writing on the NV is extremely risky.
Click to expand...
Click to collapse
Thanks again!
So, I flashed the XT1563 modem files. It took me a while because when I unrooted my phone, I also locked the bootloader (I honestly don't know why I did it), so I had to unlock it again and of course make a back-up.
While at first it seemed that I'd be stuck with "unknown" IMEI just as you said, after a minute or so both sim cards started working. I still don't know if it worked, though, because I haven't yet seen the 4G sign on my phone, but I did notice a change: after flashing the files I started getting the H+ sign (H was the best I'd get before, both here and in Europe, even after flashing an XT1562 stock image). So, it wasn't a complete waste of time
It could be that LTE reception is just bad where I live, but I doubt it because other phones have 4G connection here. I'll see what happens tomorrow in another place, but but most likely I'll have to try with a custom image and kernel, so I'll take a look at the links you have provided.
EDIT: in Europe the best I'd get was 4G, of course. What I wanted to point out was that H was the best 3G connection I'd get anywhere.
floydian86 said:
Thanks again!
So, I flashed the XT1563 modem files. It took me a while because when I unrooted my phone, I also locked the bootloader (I honestly don't know why I did it), so I had to unlock it again and of course make a back-up.
While at first it seemed that I'd be stuck with "unknown" IMEI just as you said, after a minute or so both sim cards started working. I still don't know if it worked, though, because I haven't yet seen the 4G sign on my phone, but I did notice a change: after flashing the files I started getting the H+ sign (H was the best I'd get before, both here and in Europe, even after flashing an XT1562 stock image). So, it wasn't a complete waste of time
It could be that LTE reception is just bad where I live, but I doubt it because other phones have 4G connection here. I'll see what happens tomorrow in another place, but but most likely I'll have to try with a custom image and kernel, so I'll take a look at the links you have provided.
EDIT: in Europe the best I'd get was 4G, of course. What I wanted to point out was that H was the best 3G connection I'd get anywhere.
Click to expand...
Click to collapse
Dial *#*#4636#*#* (4636 stands for INFO) on dialer and you can select LTE only from network modes to force 4G detection. In this mode, it will pick 4G network (4G only, even if its weak), whenever it's available.
To really check supported bands by your phone, I think you would need to use the QPST app, it was possible earlier by *#*#SERVICE#*#*, the service menu. Maybe somewhere in *#*#2486#*#*?
Edit: I can think of two scenarios now. The sad one... while you flashed the XT1563 modem (that supports LTE Band 4, 8, etc. (values on the lower row, check attached), your NV still says it supports 19 and 8 and so on (not 4). This could mean you are now able to use only 8 (and the other common bands supported by the two variants) and neither of 19 or 4.
Or, Moto X Play decides which bands it supports depending only on the modem files, and you actually managed to get working LTE band 4 on your XT1562. .
DragonClawsAreSharp said:
Dial *#*#4636#*#* (4636 stands for INFO) on dialer and you can select LTE only from network modes to force 4G detection. In this mode, it will pick 4G network (4G only, even if its weak), whenever it's available.
To really check supported bands by your phone, I think you would need to use the QPST app, it was possible earlier by *#*#SERVICE#*#*, the service menu. Maybe somewhere in *#*#2486#*#*?
Edit: I can think of two scenarios now. The sad one... while you flashed the XT1563 modem (that supports LTE Band 4, 8, etc. (values on the lower row, check attached), your NV still says it supports 19 and 8 and so on (not 4). This could mean you are now able to use only 8 (and the other common bands supported by the two variants) and neither of 19 or 4.
Or, Moto X Play decides which bands it supports depending only on the modem files, and you actually managed to get working LTE band 4 on your XT1562. .
Click to expand...
Click to collapse
I did try to select LTE only, but it didn't work.
I also tried using service menu, but I didn't find any of the tests to be useful to check which LTE bands are supported.
About the scenarios you propose, I also thought maybe all I achieved was to restrict LTE bands to the ones supported by both models :S. At work my phone picks band 28, but both models support it, so there's no way to check it by discarding...
There's a third possibility, though, which is that both models' modems are exactly the same and bands are only limited by NV.
After work I'll see which custom roms and kernels are there for X Play and start studying the process to edit NV. Still it might not be possible to do so because the post claims that rom and kernels must be compiled from source code, so the ones made from stock won't work... That means I depend on there someone making a rom and kernels that meet those requirements.
In the second link, the person says he can't save the changes he makes to the NV, which is what is supposed to happen if you're using stock rom and kernel, according the link I've shared.
So, I ended up editing the NV in order to remove Band 4 restriction. It took me a while because I had to figure out how to bypass all the obstacles I found on the way but, once everything was set up, the process was quite simple.
I had to boot my phone in BP Tools mode and configure the QC Diag port driver correctly. Also, I had to use a newer version of QPST because the one I donwloaded first didn't work.
The tutorial claims that your phone must be rooted and that you need a custom rom and kernel in order to avoid the "anti-tamper" mechanisms in newer Qualcomm devices. My first approach was not to do such things (i.e.: unrooted phone with stock rom and kernel).
I edited the NV values as suggested in order to enable Band 4. The good news are that the custom values that I added didn't revert back to the original ones after I rebooted and also that I didn't brick my phone and it's working properly
Right after I rebooted my phone, it picked 4G signal, but after just a few seconds it switched to H. I forced my device to LTE only, and it connected to 4G, but then again it completely lost signal. My phone does pick LTE Band 28 sometimes, but not at my place, so I thought that I must have been picking up Band 4 (I tried to leave it set to LTE only, but it picked no signal at all).
Also, when I'm at work, it sometimes picks Band 28, but signal must be very weak because it never lasts more than a few minutes, after which goes back to H.
So far I'm not sure if the mod worked because I can't find a way to see which bands my phone currently supports or which LTE band it's connected to. I tried an app called LTE Discovery, but it labels it as "unknown band" (I suspect that my phone needs to be rooted in order for that feature to work).
Right now, I'm thinking of three possible things that could have happened:
1) The mod worked and LTE signal is just very poor by my place.
2) It worked and it connected to Band 4 for a few seconds, but then the anti-tamper mechanism detected that situation and software-blocked it (without reverting NV changes I made). In this case, I'll have to flash a custom kernel and see what happens.
3) There's a hardware limitation after all, in which case there's nothing I can do (I don't think this is the case)
Right now I'm at work and my phone has been picking up 4G for over an hour already. Since it usually only lasts a few minutes (connected to Band 28), then I guess there are reasons to be optimistic that it worked after all and it is currently using Band 4.
If I succeed, I'll open a new thread with a tutorial for Moto X Play.
I'll keep updating my progress on the issue in order to leave a record of everything I tried. Also, it could be helpful to other people who are trying to do the same thing or maybe someone who has done this before will see this and point me in the right direction . Again, if I succeed I'll write a more detailed guide.
I can confirm that what I did so far didn't work, I've modified the necessary NV values and even flashed Squid kernel, but still no success: I'm definitely not picking Band 4 anywhere, only Band 28.
While flashing the custom kernel, I also wanted to use the opportunity to root my phone, but for some reason I soft-bricked it in the process, so I had to flash XT1562 stock rom again (with XT1563 modem). This reverted the NV values to the default ones, so I had to customize them again.
The user fffft says that custom rom and kernel are needed in order to avoid the anti-tamper code, but also that it is most likely in the kernel. I could try another kernel, maybe Phoenix, but if that doesn't work either, then we can confirm that the anti-tamper code is actually in stock rom.
This leaves three final possibilities to succeed in unlocking LTE Band 4:
_Flashing another custom kernel
_Flashing a custom rom
_Flashing the whole XT1563 stock rom, as I proposed at first, and see what happens. If this works, this should both set the NV values to enable XT1563 default LTE bands (which includes Band 4) and also set a different anti-tamper code, which should not bother. Worst case scenario I'll soft-brick my phone again and I'll have to flash XT1562 rom.
Daily update:
First thing I tried yesterday was what I wanted to do from the beginning, which is to flash the whole XT1563 rom on XT1562. Kids, don't try that at home! At first it looks like it's working and that the device is going to boot normally, but then it gets stuck in the apps configuration screen or after the boot animation.
The only thing left now was to try with a custom rom, so I flashed Cyanogenmod 13 and Squid kernel. This, however, brought other issues: for some reason, when booting the phone in BP tools mode or Qcom, the device's QC Diag Port isn't detected by PC. It seems to be something implied to happen with custom roms: https://forum.xda-developers.com/moto-g-2014/help/diagnostic-mode-moto-g-flashing-cm-12-1-t3254756
Has this happened to any of you? Is there a way around it?
I also found this: http://www.howardforums.com/showthread.php/1692461-HTC-Evo-and-Cyanogenmod-Diagnostic-mode
There they mention that changes should be made on stock image and just then install the custom rom. That would mean to flash stock image, then change the required NV values, and finally install the custom rom.
That makes some sense, but unless I can find a way to enable Diag mode on Cyanogenmod, this will be the last thing I try and if it doesn't work then I'll give up
floydian86 said:
Daily update:
First thing I tried yesterday was what I wanted to do from the beginning, which is to flash the whole XT1563 rom on XT1562. Kids, don't try that at home! At first it looks like it's working and that the device is going to boot normally, but then it gets stuck in the apps configuration screen or after the boot animation.
The only thing left now was to try with a custom rom, so I flashed Cyanogenmod 13 and Squid kernel. This, however, brought other issues: for some reason, when booting the phone in BP tools mode or Qcom, the device's QC Diag Port isn't detected by PC. It seems to be something implied to happen with custom roms: https://forum.xda-developers.com/moto-g-2014/help/diagnostic-mode-moto-g-flashing-cm-12-1-t3254756
Has this happened to any of you? Is there a way around it?
I also found this: http://www.howardforums.com/showthread.php/1692461-HTC-Evo-and-Cyanogenmod-Diagnostic-mode
There they mention that changes should be made on stock image and just then install the custom rom. That would mean to flash stock image, then change the required NV values, and finally install the custom rom.
That makes some sense, but unless I can find a way to enable Diag mode on Cyanogenmod, this will be the last thing I try and if it doesn't work then I'll give up
Click to expand...
Click to collapse
On step 14 of the first post you shared, it says you could check the active bands on your phone. Do you see something useful there?
AFAIK, once you successfully edit the NV Memory, the changes are there to stay, even if you reflash stock ROM.
I can confirm one thing. BP tools + stock ROM gives you diag mode, but that doesn't work on AOSP based ROMs. And it seems not even on CM based ROMs. However it should be easier to do it on custom ROMs, try enabling and looking into Developer Options. Or may be some service code in phone app?
https://forum.xda-developers.com/showthread.php?t=1626638
On my phone running an AOSP based ROM, I have files that indicate a possible diag mode at /system/sys/class/Android_USB. Need to dig in more.
If you are not able to get your phone connect in diag mode successfully, the route I would now suggest is this:
1. Flash stock ROM (for XT1562)
2. Flash custom kernel
3. Root the stock ROM (use Magisk)
4. Edit NV Values, make sure it is successfully done (step 14 on the first post you shared?).
5. Check if its working.
6. Format /system, /data, and cache partitions, and flash ROM. So your baseband files (and ofc NV memory) is not affected.
7. Try again.
DragonClawsAreSharp said:
On step 14 of the first post you shared, it says you could check the active bands on your phone. Do you see something useful there?
AFAIK, once you successfully edit the NV Memory, the changes are there to stay, even if you reflash stock ROM.
I can confirm one thing. BP tools + stock ROM gives you diag mode, but that doesn't work on AOSP based ROMs. And it seems not even on CM based ROMs. However it should be easier to do it on custom ROMs, try enabling and looking into Developer Options. Or may be some service code in phone app?
https://forum.xda-developers.com/showthread.php?t=1626638
On my phone running an AOSP based ROM, I have files that indicate a possible diag mode at /system/sys/class/Android_USB. Need to dig in more.
If you are not able to get your phone connect in diag mode successfully, the route I would now suggest is this:
1. Flash stock ROM (for XT1562)
2. Flash custom kernel
3. Root the stock ROM (use Magisk)
4. Edit NV Values, make sure it is successfully done (step 14 on the first post you shared?).
5. Check if its working.
6. Format /system, /data, and cache partitions, and flash ROM. So your baseband files (and ofc NV memory) is not affected.
7. Try again.
Click to expand...
Click to collapse
Thanks!
When I edited the NV, the changes were saved (I closed QPST and QXDM, then rebooted my phone and checked the values). However, when I flashed stock rom, the values reverted to the original ones. I also thought that shouldn't happen, but nevertheless it did :S
About getting Diag mode on custom roms, I took a quick look at developer options but I didn't see anything useful. I read a few posts that claim it can be done using a terminal emulator, so there has to be a way around it.
The steps you mention are the ones I had in mind, except for rooting. Do you think it's really necessary? (phone will be rooted after flashing custom rom, anyway).
I'll try it tonight and see what happens =)
EDIT 1: If I understood correctly, step 14 of the thread I've shared is only for 3G bands, so I don't need to change anything there. LTE bands NV's can only be seen and modified using QXDM and that's where I checked if the changes were saved. However, I have seen that there are a few holes in the tutorial, some of which I had to figure out myself. Maybe there's one extra step I'm missing on QPST? Step 24 seems to indicate otherwise.
EDIT 2: I've found this thread. It's about a Lenovo phone, but chances are they are the same: http://www.teamsuperluminal.org/forums/topic/open-diag-port-in-cm-12-1-for-qpst/
This is what it says: "To open the diag port, connect the phone to a PC and use ADB:
adb shell
su
setprop sys.usb.config diag,adb"
Changing the NV and then flashing custom ROM didn't work (I deleted system, data and cache before but still didn't work).
I tried enabling diag mode using ADB with the code I found but it didn't work. No diag port gets enabled.
I'm ready to give up. It seems it can't be done, at least not on X Play
Unless maybe someone know how to use diag mode on Moto X play running Cyanogenmod?
A few days I woke up with no service on the Nexus 6p. This was a few days after updating to the latest oreo build. Sim card seems detected because when I take it out another message shows up "No SIM card - No service", and when I put it back it only shows "No service". Tried putting the card in a Nexus 5X and it works fine.
Tried the following with nothing working so far:
- Switching 2G/3G/LTE and rebooting in between.
- *#*#4636#*#* and turning off the radio, switching between the different options of GSM/LTE/etc...
- Restoring a working nandroid backup
- Reflashing different ROMs
- Factory reset
- Factory reset then flashing ROMs
- Wiping cache and dalvik
- efs fix in twrp
Hardware version ANGLER-VN2
IMEI shows up under IMEI information tab but not under SIM Status tab, there it shows not available.
I live in Ontario Canada, carrier is Freedom mobile.
So now I'm stuck, tried calling google and hwawei and they won't do an RMA because my warranty is expired.
Anyone has any ideas to try?
Thanks in advance.
Not that this is going to help, but this has GOT to be an Oreo issue, myself as well as at least 4 others that I have seen has been getting the No service, or No Sim, mine did the No Sim, then started bootlooping.
---------- Post added at 07:36 AM ---------- Previous post was at 07:06 AM ----------
https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
No this has nothing to do with O.
Which version phone do you have? H1511 or H1512?
What country are you in now?
What is your carrier? If MVNO state that.
Are your IMEI and phone numbers showing up in settings?
Everyone, please put the most basic information in your profile like where you live, which carrier you are currently on, and maybe even which variant of your phone.
I updated the first post with more info. How do I tell if I have H1511 or H1512? I bought it from the google store in Canada.
More information is good. Please update your XDA profile so the next person trying to help can check there first. You can find the device variant by booting to bootloader (not recovery) and using the vol toggle to navigate to "Barcodes". IMEI should show up there too. Date of manufacture, Serial #, etc. I think you should have started a normal thead, not Q/A, BUT your IMEI and a lot of other information should be showing up under SIM info. That's a problem. Second, you say you did the EFS fix in TWRP. Can you explain how you did this? Did you use one of YOUR OWN TWRP backups which contained the modemst1,modemst2 and restored ONLY those two partitions to your device? Did you receive any confirmation or error? Have you tried using a SIM from a Rogers or Telus in your phone to see if the SIM info shows up?
Thanks for the help, I'll update my profile with this info as well.
in the bootloader the IMEI shows up along with the rest of the info. It's a H1511 device.
The EFS fix is by following this: https://www.theandroidsoul.com/fix-empty-imei-corrupted-efs-no-sim-unknown-baseband-wifibluetooth-issues-restoring-twrp-backup/
is modemst1 and 2 contained in the twrp backup? and if so how do I restore it? in restore options there's system, data, vendor and boot only. I guess it's an option in the backup that I haven't selected?
I tried another SIM also from freedom and it didn't work. I don't have a Rogers or other SIM to try currently.
Right, so if you didn't ever select the EFS partitions when using TWRP Backup, you never backed them up so under Restore they don't show up (so you can't use that method). You can however use TWRP terminal or fastboot to wipe those and reboot. I would be sure to try at least one SIM from either Rogers or Telus. If that doesn't work, then wipe the EFS partitions and let them rebuild (hopefully).
Definitely Oreo issue. Google messed with something and it broke data for many people. I have been troubleshooting this for the last week (Verizon, US, fully stock 6P) and finally found a thread where a Google rep acknowledged the problem and said it was high priority for a fix.
I wish you luck with that one @LucJoe. This has been happening for the past 2 years from MM, N, and now O...and XDA is full of threads (just look). So you just go ahead and wait for Google to fix it for you, LOL. - Not a new issue related to O.
Never happened to me before updating. The data issues manifest differently across different carriers but for some reason Oreo likes to play it safe and disconnect data. I have not been able to get LTE for more than a couple seconds, but will get slow unstable 3G occasionally. Google confirmed the issue here: https://productforums.google.com/forum/#!msg/phone-by-google/kw3ZcXd1BVs/7HYuANdoAgAJ
A recent success using terminal from TWRP (or the OS if you are rooted). You can also use fastboot to do the same thing using the commands in the article posted in this Q/A (method 2). Good luck! See thread here.
This seems like it's a different issue described in that thread. I'm not running out of data, there's no service and no connection of at all to any network.
I did find that and try it before posting here. It did nothing to fix the problem. It did say that something was copied over '4 MB copied, at 14.3 MB/s' something like that but nothing changed.
I also have the same issue. Have tried everything including going back to stock 7.1.2 & locking the bootloader. Nothing seems to work. Interestingly, when i pull up the hidden phone diagnostic menu, it shows all cell measurement info which means that the antenna is receiving signals but the phone somehow is not registered on the network?
I can wipe those partitions with fastboot but is it safe? I have never used TWRP and my problems started after updating to Oreo. Is there a chance the official OTA could corrupt those partitions?
@LucJoe- That fix is not for you. That is for users who have no IMEI or phone number under About Phone>>SIM info. Your issue (as I understand it) is a weak and intermittent signal that keeps disconnecting LTE and sounds like a carrier or SIM issue. Why not go get a new SIM provisioned for your phone. That or pop somebody else's SIM in your phone and see if you get a different outcome.
Yes that was my first thought as well. I got a new SIM, then another one. So 3 SIMs now with the same result. I've been on the phone with so many techs from Verizon/Total Wireless and none of them have any answers. If I put the same SIMs into a Moto E4 I picked up for testing, it works fine. But the 6P immediately disconnects from LTE then bounces between 3G/1X.
My next test is to try a SIM from a different network I guess... maybe Verizon is blocking my 6P. Or maybe my LTE radio is damaged somehow.
So I did this using TWRP but wasn't sure if it actually went through or not. I did it now through adb from pc and also fastboot and it says permission denied. Any idea how to bypass that?
I installed the latest lineageOS 19 version, rooted my phone then ran into this problem where the phone says i have service, but when i place a call it wont fully make the call. Then my mobile data will X out and i get pop up error saying mobile service is unavailable. I then tried lineageOS 18.1 and arrowOS and same problem persists.
formating between installs obviously.
I have looked at every option on this phone and tried combinations and everything in the network/system/ everything and still not working.
The process was actually very simple since i have some programming experience. Other sources mention possible baseband issues? On the fastboot screen it shows a baseband version. all the information there appears normal. I only flashed the boot image one time to root and didn't mess with any other manual flashing processes. Just used twrp. I didn't quite understand twrp at first and therefore didn't get a backup using it... iused adb to make a backup which apparently didn't work so Im lost and hope someone could help me out here. please and thank you!
If i may add I can use mobile data just fine, i can browse the internet and such (with wifi off and data on only) so i really dont understand. Is this a normal issue to have when using custom roms? did I trip some security that blocked me now? any input???
I wonder, though, this moto g7 is an A/B partition thing. so if i understand correctly, flashing twrp would not work and thus why i did not do that. it makes sense. But should i try flashing it, booting into it then installing lineage? even if i did i feel like that would give me same issue considering the method i followed got me into lineageos, plus root checker said i was rooted.
What I can tell you is what I had to do in order to get LTE (voice calls) running on my G7 - I was forced to switch over to LTE because AT&T turned off 3G here in the US and 4G without LTE is not good enough for voice calls:
Get the latest stock firmware and install it using e.g. Lenovo's "Rescue And Smart Assistant". That will get Motorola's Android 10 on the phone.
After installation, go through setup and actually make a call (calling your mailbox is fine). Then check your ims status (*#*#4636#*#*, goto phone info, pull ims status) to see that ims is actually working.
Shutdown the phone and start installing LOS (use the partition copy script too to make sure that the partitions not touched by LOS installation are updated "on the other flash bank").
Go through LOS setup, select a valid APN for your setup, set "LTE only" or "LTE / WCDMA" for the network and make a call. You should be good to go.
Again this is what I had to do to get LTE working with AT&T USA. YMMW.
Markus.
I know this is way late, and you probably already figured it out. I didn't share the no text problem. The Problem isn't just the "LTE" setting itself. There is one more option(some Roms show it, some don't) I believe its in the phone app settings? VOLTE must be checked. I have noticed Some Roms do have this option and some don't. when volte is checked, it'll keep your data/internet on during a call, some Roms that option won't show up or isn't available. I haven't used G7 in a while, but I do remember the problem and how to fix (on my phone anyway).