Database Users

[Q] Loosing HSPA on root - no sim card

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

Modem file needed

Can any one provide the stock Single Sim modem file.I need to enable single sim in Dual sim

I have European xt1562
https://www.dropbox.com/s/zv8k5zqj2yo3qhw/modem.bin?dl=0

sjaakd said:
I have European xt1562
https://www.dropbox.com/s/zv8k5zqj2yo3qhw/modem.bin?dl=0
Click to expand...
Click to collapse
Is ur model single sim

anadarco7 said:
Is ur model single sim
Click to expand...
Click to collapse
Yes it is

sjaakd said:
Yes it is
Click to expand...
Click to collapse
Thanks

Make sure to backup and then erase the two modem data partitions as well. You can find the fastboot commands in the XML of the firmware packages.
Without behaviour might be not what you are looking for...

I worked for me thanks

Modem file for dual sim
Can anyone please share modem file for dual sim model as I've accidentally selected radio band as USA and hence won't get the network in sim slot 1. Also, if possible, please share link to a step by step tutorial as I'm a novice. Also plz tell me if flashing is possible without using a pc and will the warranty of the phone get void. A prompt response will be highly appreciated.
Thanks

I think Flashify can flash without an external device BUT having the OS (Android) running with all the options for locks and alarms would scare me.
I do _think_ that flashing original Motorola signed binaries will not void anything, to be more precise: With a locked bootloader such procedure should be impossible.
Before you flash a baseband (modem; for which we'd need your current version - see "my phone"), I would recommend just erasing modem setttings. I suspect this is where the modem config is permanently stored so erasing it should set this to default.
fastboot erase modemst1
fastboot erase modemst2
I would assume that after you boot, your device crashes once - so it does for me after flashing the modem. Happens when I make the first call. So just try calling your mailbox or something.
Again, I can't and I won't gurantee anything. You warranty is void!

Here's the version of baseband my phone has got.
tinypic.com/r/2ntb49c/9

I strongly suggest you try the fix above before going after this. This reflashes your modem which might be unnecessary.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
The modem files are in the download, the ones you are looking for are in:
X_Play_France_Retail_XT1562_LPD23.118-10_CFC.xml.zip
See:
http://forum.xda-developers.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364
http://www.filefactory.com/file/e92ibmowiq5/X_Play_France_Retail_XT1562_LPD23.118-10_CFC.xml.zip

Thanks a lot, erasing the modems did it for me.
Many thanks mate.

Great. You can hit the "Thanks" button if you appreciate it.

I could fix my phone by erasing modems, after doing that I performed a factory reset, but now I've another problem. Installing apk files takes longer time than it would take earlier, does it have to do anything with the problem I was facing earlier?

That does not make sense - it just takes longer on the Moto X; I've experienced the same...

But it was pretty fast before doing the reset, I tried further resets, both hardware as well as software, but to no avail. The installation process is very slow, it took Facebook app atleast 5 minutes to install from apk file. Even installs from market take time and it's annoying.

See my other thread just posted. Assume this is because installs need to be converted from Dalvik to ART.
I know it was a lot faster under e.g. 4.4.2. But you sure it was also for any device with 5+?

I used this device for 2 days before messing up with radio band, i didn't face this problem during those 2 days and i used a Moto g3 for three months, didn't face this problem with that either. And it's dead slow, like currently my fb app is updating in background, it already has taken 12 minutes and is asking for another 3 minutes for a 45mb update.

I guess getting this phone replaced is the safest bet for me, as i have witnessed one more problem. When i keep the phone aside and pick it up after some time i see some strange coloured vertical lines on display at the right with rest of the screen being black. It gets right only when i lock and unlock the screen with power key. Any idea what it could be?

Hardware issue?! I would try and see what happens when you reflash it to full factory but that's of course only what I would do.

Massive LTE issues on Verizon

So I've got a US Moto X Pure, XT1575, currently running TruPure XMM 2.9, just installed a few days ago, and while driving around with my brother I've noticed that my 4G switches to 3G and loses conncections all the time, while his Verizon LG V10 maintains a rock-solid LTE connection. I've also found that in many, many areas, if i run a speed test, most of the time it tells me less than 1mbps down, and usually 0-0.02 up, his get's normal speeds. I've even found areas where I get 40+ mbps down, 0 up.
Is it the modem firmware? Did I break it? I have opened it up a few times but I was always very gentle and triple checked all connections before re-installing the casing.
Is it because of the CDMA/GSM thing? My old Note 3 before this phone didn't have any of these problems, my brother's V10 doesn't either.
I'm losing my mind trying to fix it and nothing's worked.

TallgeeseIV said:
So I've got a US Moto X Pure, XT1575, currently running TruPure XMM 2.9, just installed a few days ago, and while driving around with my brother I've noticed that my 4G switches to 3G and loses conncections all the time, while his Verizon LG V10 maintains a rock-solid LTE connection. I've also found that in many, many areas, if i run a speed test, most of the time it tells me less than 1mbps down, and usually 0-0.02 up, his get's normal speeds. I've even found areas where I get 40+ mbps down, 0 up.
Is it the modem firmware? Did I break it? I have opened it up a few times but I was always very gentle and triple checked all connections before re-installing the casing.
Is it because of the CDMA/GSM thing? My old Note 3 before this phone didn't have any of these problems, my brother's V10 doesn't either.
I'm losing my mind trying to fix it and nothing's worked.
Click to expand...
Click to collapse
Have you tried going into fastboot and erasing modemst1 and modemst2?

hbar98 said:
Have you tried going into fastboot and erasing modemst1 and modemst2?
Click to expand...
Click to collapse
Not yet. First time I'm getting this advice. What does erasing them do?

TallgeeseIV said:
Not yet. First time I'm getting this advice. What does erasing them do?
Click to expand...
Click to collapse
Well, as far as I can tell it erases the info in the modem partitions. I'm not really sure. But when people have gps or lte issues, erasing them seems to help. I've been on a flashing binge lately, and I erase them pretty much in between every flash with no issue.

hbar98 said:
Well, as far as I can tell it erases the info in the modem partitions. I'm not really sure. But when people have gps or lte issues, erasing them seems to help. I've been on a flashing binge lately, and I erase them pretty much in between every flash with no issue.
Click to expand...
Click to collapse
Ok, does it need to be done before flashing a new modem? Or do you erase them after so it rebuilds them automatically or something?

I flash the modem, then erase modemst1, modemst2.

Ok, so let's see if I did this right:
I went and extracted 'NON-HLOS.bin' and 'fsg.mbn' from the latest stock firmware in this post: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then I booted into fastboot mode and used these commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
I found these as a fix for a Moto X Style having similar connectivity issues in this post: http://forum.xda-developers.com/moto-x-style/help/baseband-imei-t3283141
Then i rebooted and i've got signal but nothing seems any better. The only difference, which i'm hoping has been the issue all along, is that now under Settings>More>Cellular Networks>Preferred Network Type I'm able to select CDMA and have it maintain signal. Before, whenever I clicked that I would lose all data signal and it wouldn't come back. Gsm sort of worked but cdma would never work, it does now.
I can't really test it right now since I have crap signal at my house either way, but does this sound like I've solved something or is this just the placebo effect?

Well, that made it waaaay worse. A lot of new gps issues now....

Flashed Verizon RUU, cellular radios, GPS, and camera now broken

Hey all,
So, a little backstory: I got this HTC 10 from Sprint not too long ago, and little did I know that I would be stuck with Sprint unless I reflash the phone firmware. (after research, asking HTC and Sprint, I received misinformation from reps stating that the phone would work on Verizon with just a carrier unlock issued over the air). Moral of the story: don't rely on customer service :silly:.
Fast forward to now, and I have rooted (temporarily to run Sunshine), S-OFF'd (using Sunshine), changed the CID (for Verizon), and flashed the newest Verizon RUU that developer Dottat kindly posted here.
That worked, full LTE, but then whenever the camera or GPS were accessed by any application, the phone would freeze with a black screen (though it seemed something was still running in the background, as notification sounds would still play, and I could exit by pressing the home button and waiting about a minute). After this, I tried flashing the Viper ROM just for kicks, but then the cellular radios only functioned with 3G coverage (no LTE in a coverage area), and GPS was still broken (the camera issue was fixed with this flash for some reason).
Unfortunately (or maybe not), I am pretty sure /system has been wiped multiple times. I also ran
Code:
htc_fastboot erase modemst1
htc_fastboot erase modemst2
after each install of a new ROM, then performed a factory reset from recovery (just a factory reset, nothing more).
Now I went ahead and used an official ROM from HTC's website in an attempt just to get full functionality working on any carrier. I flashed the USA unlocked variant (and changed the CID to BS_US001. MID is still 2PS650000), but now I am experiencing more missing functionality. The camera and GPS are still missing, and now the SIM card is not detected (when entering the access point names dialog, a message pops up stating that there is no SIM, or SIM error when I am using an activated AT&T SIM). When I enter the test menu (*#*#4636#*#*) and select any option for network mode other than what is default (LTE/CDMA), the new option won't 'stick' (it returns to default after a few seconds).
This sounds to me like there is stale firmware on the device from a previous flash, or that the firmware for these core peripherals is corrupt. Is there a way I can get these devices working again? Or am I now stuck with a bricked device ? I do still have a backup I took of what was installed stock by Sprint (all except for /data...but I don't need that partition, right?)
EDIT: Mods, I am terribly sorry! I meant to post this in HTC 10 Q&A. I don't see a way to delete a thread, so hopefully we can move it.

MrFarquad said:
Hey all,
So, a little backstory: I got this HTC 10 from Sprint not too long ago, and little did I know that I would be stuck with Sprint unless I reflash the phone firmware. (after research, asking HTC and Sprint, I received misinformation from reps stating that the phone would work on Verizon with just a carrier unlock issued over the air). Moral of the story: don't rely on customer service :silly:.
Fast forward to now, and I have rooted (temporarily to run Sunshine), S-OFF'd (using Sunshine), changed the CID (for Verizon), and flashed the newest Verizon RUU that developer Dottat kindly posted here.
That worked, full LTE, but then whenever the camera or GPS were accessed by any application, the phone would freeze with a black screen (though it seemed something was still running in the background, as notification sounds would still play, and I could exit by pressing the home button and waiting about a minute). After this, I tried flashing the Viper ROM just for kicks, but then the cellular radios only functioned with 3G coverage (no LTE in a coverage area), and GPS was still broken (the camera issue was fixed with this flash for some reason).
Unfortunately (or maybe not), I am pretty sure /system has been wiped multiple times. I also ran
Code:
htc_fastboot erase modemst1
htc_fastboot erase modemst2
after each install of a new ROM, then performed a factory reset from recovery (just a factory reset, nothing more).
Now I went ahead and used an official ROM from HTC's website in an attempt just to get full functionality working on any carrier. I flashed the USA unlocked variant (and changed the CID to BS_US001. MID is still 2PS650000), but now I am experiencing more missing functionality. The camera and GPS are still missing, and now the SIM card is not detected (when entering the access point names dialog, a message pops up stating that there is no SIM, or SIM error when I am using an activated AT&T SIM). When I enter the test menu (*#*#4636#*#*) and select any option for network mode other than what is default (LTE/CDMA), the new option won't 'stick' (it returns to default after a few seconds).
This sounds to me like there is stale firmware on the device from a previous flash, or that the firmware for these core peripherals is corrupt. Is there a way I can get these devices working again? Or am I now stuck with a bricked device ? I do still have a backup I took of what was installed stock by Sprint (all except for /data...but I don't need that partition, right?)
EDIT: Mods, I am terribly sorry! I meant to post this in HTC 10 Q&A. I don't see a way to delete a thread, so hopefully we can move it.
Click to expand...
Click to collapse
A MOD should move it soon.
I am not the best here, but hopefully can be of some help.
I would just superCID, save a step for flashing RUU's.
So, when you flash the Verizon RUU, does camera work?
(if you RUU and only have 3g, wipe the modems to get 4g back)

If your trying to use the phone on Verizon I would do the following:
1) Change your CID to Super, 11111111
2) Flash the US Unlocked RUU, http://www.htc.com/us/support/rom-downloads.html#unlocked
3) After it fully boots, reboot into the bootloader & flash the Verizon radio, http://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743
4) Make sure the Preferred Network is set to Global, Settings>Mobile data>Preferred Network
5) Get to the secret menu *#*#4636#*#*, and set the preferred network type to "CDMA/EvDO/GSM/WCDMA/LTE Auto"
I use a Verizon model with the US Unlocked firmware. As far as custom ROMs, some work with Verizon's network and some don't. I'm sure theres a workaround but I've stuck with the US Unlocked firmware, and just use Xposed for any tweaks/mods.
If your trying to use it on AT&T and the radio from the US unlocked RUU should work.

andybones said:
A MOD should move it soon.
I am not the best here, but hopefully can be of some help.
I would just superCID, save a step for flashing RUU's.
So, when you flash the Verizon RUU, does camera work?
(if you RUU and only have 3g, wipe the modems to get 4g back)
Click to expand...
Click to collapse
Used to be a guy around here we could trust to help.
Sent from my HTC6545LVW using Tapatalk

X522 no service after update to 5.8.021s?

Bought this phone last week off ebay thought I would update the firmware so I found the 5.8.021s file and did the update ZIP. It updated fine and everything worked except the phone. It shows the sim card as t-mobile with my phone number and cellular data calls and messages as t-mobile but when I try search for network I get "error searching for network". I tried different sims that I know are good and nothing works. I would return it to the original firmware but I wasn't smart enough to back it up. I would flash a new modem if I knew how maybe that is the problem. I have an x829 as my daily driver this was going to be a birthday gift.
Baseband MPSS TA 2.1 c700008-8976 GEN PACK-1.85233.30.76286.2
EUI version 5.8.021S
Thanks in advance.
Rick

Exactly the same issue here, was using the 21s firmware as my daily driver and suddenly the sim stopped working, in settings / about phone / status, I can still see the network and phone number being read but no network service at all.
I have tried flashing as dead phone, and updating roms back to 21s but nothing has worked so far, also different modems but nothing still.
The more I read the more common I see this problem is on Le Eco phones !!
Help anyone !!

Fixed it. Installed the small EUI by aurel. He had a note about my predicament on the first page. Great ROM for me and a big thank you to him. So here is what I did. Probably would have worked on the 21s too.
1. Download the adb, fastboot drivers
2. Install it on your PC.
3. Restart the phone in fastboot mode (power + vol down)
4. Type this commands in the terminal:
Quote:
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
5. Done.
Thanks again

dainbramage said:
Fixed it. Installed the small EUI by aurel. He had a note about my predicament on the first page. Great ROM for me and a big thank you to him. So here is what I did. Probably would have worked on the 21s too.
1. Download the adb, fastboot drivers
2. Install it on your PC.
3. Restart the phone in fastboot mode (power + vol down)
4. Type this commands in the terminal:
Quote:
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
5. Done.
Thanks again
Click to expand...
Click to collapse
This is where mine had bigger problems, I had IMEI for both sims and MEID but after losing signal and trying this advice lost all information and baseband !! ( stupidly I forgot to backup this info )
At the moment I am screwed, I have managed to get back baseband and IMEI numbers but still no MEID ( zeroed out ), I am guessing because it is a global phone it needs some kind of MEID / ESN even if I am not using CDMA at all !!
...Or I 'm missing something stupid ?!
Tried *#*#4636#*#* and in to try to turn on radio but nothing , even tried with various sim cards but still no signal even with IMEI and baseband good !! Just can't switch on radio !
Any ideas would be great !!

Crap, so sorry for you. You might put a question in the questions and answers section. I should have put a note in saying that I have no idea what I'm doing. This happened to work for me after only four days of screwing around with this stupid phone trying to figure out how to put a new ROM in. My patience had almost run out and next I was going to do a crush test video matching the phone against my 4 door Dodge Ram pickup. Best of luck to all.
Rick

dainbramage said:
Crap, so sorry for you. You might put a question in the questions and answers section. I should have put a note in saying that I have no idea what I'm doing. This happened to work for me after only four days of screwing around with this stupid phone trying to figure out how to put a new ROM in. My patience had almost run out and next I was going to do a crush test video matching the phone against my 4 door Dodge Ram pickup. Best of luck to all.
Rick
Click to expand...
Click to collapse
Not your fault man, I need someone to upload a backed up EFS/ QCN file from the X522 model specifically and I can change the IMEI back to my original one and try to figure out how to get the radio switched on to receive signal !! The problem I see here is the MEID numer being zeros and LeEco don't put this number on the box with the rest of the IMEI's etc. I always thought this wasn't needed if I'm not using CDMA but I don't know if it is a must on global phones !!

I installed the small EUI ROM by aurel and that is where the bright idea of deleting those two files came from. The new ROM turned my X522 into a X526. I think the base ROM is 5.9.26S. The only reason I originally messed around was I wanted the nav lights at the bottom to stay lit. They do now.
I don't think these phones have a MEID number since they aren't CDMA but like I said I know nothing.
Rick