I would be so grateful if someone more knowledgeable than I helps me troubleshoot this issue.
I bought a used Nexus 5x yesterday, everything worked fine and it was all stock, i checked my sim card and it worked on the phone.
I took it home unlocked the phone and installed a custom ROM, somehow In the process I seem to have done something that has made it so the phone cannot connect to my mobile network. It seems to be able to see the mobile network [ imgur.com/IdpFg0O ] but not connect [ imgur.com/5edM5G6 ]. The phones APN setting [ imgur.com/5J1Ixoy ] appear to match the information provided on various websites.
The SIM status page [ imgur.com/WGWnqSM ] might give some indication as to what the problem is. It lists the network as "unknown" and the service state as "out of service" and mobile network state as "disconnected."
What I have already tried:
Restarted the phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Removed and reinserted the SIM card
Tried another SIM card
Manually set APN settings
Manually set Network
Wiped Phone (factory reset)
Reflashed the same custom ROM
Reflashed another custom ROM
Reflashed the Stock ROM
Could I have maybe somehow screwed up the /EFS partition when I was wiping or installing the new ROM?
I dont really know what else to do to troubleshoot or try to fix the problem. I would be sooo sooo grateful if anyone more knowledgeable than I am could help me troubleshoot this issue, there doesn't seem to be much information out there about this problem. I really don't want to have bricked my phone the day after I bought it, so please, if you can offer any assistance helping me understand and diagnose the problem, I would be so grateful!
All Screenshots: imgur.com/a/sq1JbXF
All rooms require a specific version of radio.img make sure you have the right one otherwise you'll have problems like that check out in the xda thread of your rom what version it requires and then download the factory image and flash the radio.img with fastboot
Hi kastik4,
Thanks for the reply, I appreciate you taking the time to lend a little help.
So if I understand you correctly what you are saying is that each specific ROM has its own radio.img and that a mismatch could potentially be causing my problem?
If so, I'm not sure if this is the problem as one of the troubleshootings steps i've taken is trying to go back to the stock factory ROM following Googles instructions and (I believe) flashing the stock radio.img. However, it is entirely possible that I did something incorrectly in this process so I think I will try to redo the process and make sure I got everything right tomorrow.
Any other ideas as to what could be the issue?
@local5x: you wrote, that you reflashed stock ROM. If you did it via flashall.bat (means you lost /data and root) and error persists, probably your hardware is gone.
Messed efs you can detect easily: IMEI shown in settings and on your contract, must be identical.
Generally is the newest radio-image fine. @kastik4's advice is mostly overdressed.
Hey, did you solve your issue or you still need some help?
kastik4 said:
Hey, did you solve your issue or you still need some help?
Click to expand...
Click to collapse
No, I did not solve the problem. I got a cheap phone in the meantime, but haven't been able to figure anything out with the 5x. Maybe it is a hardware issue, IDK, and I dont really know where else to go in terms of troubleshooting, I'm sorta in over my head here. I wish I could narrow down the problem though, even If it is just to find out that it is a hardware problem and I'm screwed at least I would have a little clarity/closure.
hello I have the same problem my phone says no service and only emergency calls, I followed some solutions nothing yet. I would like to find a solution since it does not detect the available networks
Related
OK, I know there are other threads about this, but when I read them I feel like it's for people that messed up other things that they shouldn't have, and I don't believe I'm in that group. Let's start with some basics:
- I have never used a NANDROID backup that wasn't from my own phone
- I ran grep RSA /dev/mtd/mtd0 and I still have my keys
- The only radio I've ever flashed was from Cyanogen based on the instructions from his wiki, and I don't think that messes anything up
I've tried flashing Fresh and Warm ROMs from both Clockwork and Amon, and I've tried both more than once, just in case there was an error. I turn 4G on and it says it's scanning, but nothing connects. I happen to know that I'm about 3 blocks from a Wimax tower, so there's no way I wouldn't be getting a signal. I've read through several other pages that people refer to but none of them seem to apply. It's always for people who don't have keys or who are having problems different from my own.
I apologize in advance if I missed something, and I know I could probably read all night, but I would really appreciate if someone could tell me what I can try to get my 4G radio working again.
Thanks!
UPDATE: OK, I was ready to go back to stock in utter desperation to see if something would fix itself, but I FINALLY got it to work. Here are the steps to follow if anyone else encounters this problem...
1) Make sure 4G is off
2) Open Root Explorer and go into /data/misc/wimax and rename the field there (xxxxxxxxxx.tree.xml where the xxx... is your 4G MAC address) to add .old at the end
3) Go into Settings -> System Updates -> Update profile
4) When that is complete, reset the phone (this may not be necessary, but... why not?)
5) Now turn on 4G and it should recreate the .xml file and be running smoothly
I had heard the tip about deleting the XML file, but nobody told me about updating the profile or anything along with that step. Hope this helps.
UPDATE 2: Now it's not working again. It was just sitting there, working fine one minute, and now it doesn't work again.
FYI, I also have checked to see that my MAC address is correct, and I recreated my tree.xml file. My MAC address is just fine, but still no connectivity. My coworker with an EVO right next to me gets 4G here, so I know I should have a signal.
I just updated my profile (can't believe I didn't think of that before), but that didn't work either. I can't find anything that is in error to fix!!!
WrlsFanatic said:
- The only radio I've ever flashed was from Cyanogen based on the instructions from his wiki, and I don't think that messes anything up
Click to expand...
Click to collapse
What radio did you flash? And not sure if it has anything to do with wimax. Did you try to reflash the stock radio 2.15?
wrapkgb said:
What radio did you flash? And not sure if it has anything to do with wimax. Did you try to reflash the stock radio 2.15?
Click to expand...
Click to collapse
EDIT: Nevermind... it worked for a bit, I even used some data across that network, and now it's borked again.
I flashed the radio that is on this page, but on second view, I think that's just to upgrade people that were on a lower version of the radio. GRRR!!!! Should I try reflashing the stock radio? Would that help?
I keep getting it to turn back on by mixtures of deleting that .xml file and resetting my profile, but it absolutely will not stay. Any ideas?
I am experiencing this issue and have been searching for a week trying to find a solution if you guys found one or if anyone knows of one please please please let me know!!
What am I missing?!?!
Hopefully someone can help me here. My problem is I cannot connect to wimax. So I tried to check to see what wimax version I have so I tried using Android Terminal Emulator as someone else posted. Well I did and it turns out that I am missing something...not sure what though. Here is a screen shot of the Emulator.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone please point me to the right direction. PLEASE!
BTW...if it matters
rom: Myn's Warm 2.2 RLS5
kernel: 2.6.32.15-netarchy-toastmod-4.1.9.1-cfs [email protected] #7
pri: 1.90_003
prl: 60677
Well if you press *#9090#, DO NOT choose option 1 as it will immediately wipe your IMEI and All related network information.
I may have to send my phone out for repair unless anyone knows of a cheap/inexpensive way to fix this problem. I know of a program called Chimera, but it charges €59.90 for the ability.
So currently I have no Network, no IMEI, unknown baseband version and to top it off, my phone reboots after 2 minutes. I've tried Odin'ing back to stock but it didn't work probably because that info I erased is stored elsewhere...
Any ideas?
ZPaul2Fresh8 said:
Well if you press *#9090#, DO NOT choose option 1 as it will immediately wipe your IMEI and All related network information.
I may have to send my phone out for repair unless anyone knows of a cheap/inexpensive way to fix this problem. I know of a program called Chimera, but it charges €59.90 for the ability.
So currently I have no Network, no IMEI, unknown baseband version and to top it off, my phone reboots after 2 minutes. I've tried Odin'ing back to stock but it didn't work probably because that info I erased is stored elsewhere...
Any ideas?
Click to expand...
Click to collapse
nope you'll need to warranty replace i had exactly the same thing happen to me. so to anyone reading this thread pay attention to what @ZPaul2Fresh8 says and be very cautious.
Yup $15 later for overnight shipping and I got a warranty replacement.
What do you do?
ZPaul2Fresh8 You call to service and you said that you would change? They asked you ?
I wiped mine to accidentally and had to send mine to Samsung to be fixed ... they received the phone weds and is know being mailed back to me with a new motherboard ..... they paid for ups 2day air for free both ways ....
This was their finding : Original Problem:
OPERATION SYSTEM ISSUE - PLATFORM / SOFTWARE - OPERATING SYSTEM ISSUE
Problem found:
AUTO POWER OFF W/BATT/TEST CAB - REAR COVER - COSMETICS - KEYPAD / KEYPAD BACKLIGHT INOP
Solution:
REPLACED PBA - REPLACED COSMETIC - REPLACED COMPONENT...
Got phone today
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did the same thing on my note 2 and bought another device then one day i decided to see if i could fix it. I did alot of digging and fixed it. I wanna say i flashed a stock modem and everything imei and all came back. Its fixable just gotta find the right solution but if warranty fix it then i don't blame you .
today if acted very silly, I read this thread and I dont know for what reason did just what he said I should not do and now I have my note 4 in an infinite loop that doesnt allow to use, I already install the current modem device and still the problem persists. The another problem that I have is that Samsung will hardly support me because I didnt have the bill and I'm in a different country in which the note was sold.
thats happens to my phone, restart every 2 minutes i choose the first option on 9090, cim tryingto flash with odin, but i cant find the right files for this model, can someone help me please to find the rom stock SMN910A????
cybertepache said:
thats happens to my phone, restart every 2 minutes i choose the first option on 9090, cim tryingto flash with odin, but i cant find the right files for this model, can someone help me please to find the rom stock SMN910A????
Click to expand...
Click to collapse
unfortunately flashing with odin wont help the only solution is to send it in for warranty replace.
Note 4
Has anyone found a solution fie wiped imei as a result of messing with *#9090*
sincindy said:
Has anyone found a solution fie wiped imei as a result of messing with *#9090*
Click to expand...
Click to collapse
I know that you are not going to want to hear this but I know someone who can repair it via the Internet. You will need a computer with a USB cable to run to the cell phone.. Email me back if you have any questions [email protected]
---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------
Aaron. Edwin79m said:
I know that you are not going to want to hear this but I know someone who can repair it via the Internet. You will need a computer with a USB cable to run to the cell phone.. Email me back if you have any questions [email protected]
Click to expand...
Click to collapse
Wow I just noticed how old this topic was lol sorry
As the title says, I installed the ASUS Official Unlock tool (and didn't really read it, as you should) and it attempted a boot unlock without SU. The funny thing is, it did exactly what it said it would do and rebooted into the Bootloader. The Bootloader said (and still does) it was a success and that the phone will reboot in 5 seconds. Which is fine, except it's doing that every single time I enter the Bootloader. I can't get it to stop doing that so I can actually do the root and re-do the unlock. The phone still functions perfectly fine otherwise.. any advice? (Yes, I can get it into recovery mode) Hopefully that didn't ban me from OTA.
EDIT: It also turned my boot screen white, and I also tried to use the sideloader, but I already have the latest ASUS firmware so that didn't help. However, in my loader I noticed some weird stuff showing about a MOD_SDUPDATE.ZIP not being found.. I don't know what's that about. It was doing that before I tried to use the sideloader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dunno what exactly happened, but you can do " Using Stock.zip from ASUS site:" from here, that should fix basically everything: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
P.S.: your data won't be lost, however your app ache will be cleared, meaning you'll be logged out everywhere. So if you have some game and no account, that game state will be lost.
So I tried that, first with the ROM that's installed on the phone the .97 version. Then with the original version. It appears to actually install the .97 version, but that does absolutely nothing for the phone and if I try an older version it just tells me it can't flash an older version. Should flashing the same version over-top have taken care of the problem? Doesn't look like it did anything. The boot loader is probably unlocked, but I can't keep it in ADB mode long enough to do anything useful and you can't sideload a recovery to my knowledge.
EDIT: I named the file wrong in my tiredness. I did it again and loaded in recovery...
EDIT2: That did not work.
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
ultramag69 said:
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
Click to expand...
Click to collapse
I don't actually know what you mean by that? With the ASUS unlocking tool causing it to reboot in the bootloader improperly or the booting of the file from Recovery?
The phone isn't actually "broken" but now... I can't do anything to it without the use of ADB.. Which blows.
EDIT: Also, can you point me to these threads?
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
m3t4lw01f said:
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
Click to expand...
Click to collapse
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
bewaffled1 said:
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
Click to expand...
Click to collapse
Yep. We're hoping @ASUS_Khang gets a solution from HQ next week to get us back on track!
Probably this is a common issue, and you may want to kill me after opening a new thread for this. I'm so sorry, at the moment I'm very worried because my phone suddenly lost network services and I have no idea how to deal with these things, I'm really bad at flashing and such thing.
Problem is that after a year and half since I bought my Samsung Galaxy Note II GT-N7100, suddenly today this issue appeared.
The device has root access (not performed by me) with Kingo SuperUser/SuperSU. Once I realized it was rooted, I googled and proceeded to perform a factory reset (restarted device with power + volume up + home buttons, which leaded me to android system recovery 3e), which didn't help at all.
If I dial *#06# the IMEI it shows 004999010640000 / 01 but the one I see under the battery slot is (2014) IMEI: 359xxx/05/853xxx/4 (I don't know if this data is relevant, just trying to help).
I found this thread in this forum, which seems to be the same problem I'm facing right now, but I don't have any backup of those files, plus I don't know how to flash this specific phone :crying:
I'll really appreciate any kind of help you can provide me to fix my phone.
Here's a screenshot of the device info (it's in spanish but some names are easily understandable)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance, and please, tell me if I can provide more info.
I recommend removing the imei # (359358...) from your post and refrain from publishing imei #s on a public forum.
Have you tried flashing the latest stock ROM from sammobile.com?
audit13 said:
I recommend removing the imei # (359358...) from your post and refrain from publishing imei #s on a public forum.
Have you tried flashing the latest stock ROM from sammobile.com?
Click to expand...
Click to collapse
Thanks for the advice!
I haven't tried anything but a hard reset. I don't know how to flash a phone, and I'm pretty sure I can screw it up if I try xD
I just heard about sammobile.com, but I don't know how to proceed even on that website.
Anyway, I hope there's something I can try before making that kind of "flashing"
If the imei doesn't get restored after flashing the latest stock ROM from Sammobile.com, you would need to try other methods to fix there imei problem.
Common issue... More than you imagine. Happens to me all the time. But I have one solution in my case Wich is just flash the EFS partition in my previous nandroid backup, but since to be you only were rooted and not custom recovery, I guess you don't have a nandroid backup. Only solution here is flash thru Odin and all will be good.
audit13 said:
If the imei doesn't get restored after flashing the latest stock ROM from Sammobile.com, you would need to try other methods to fix there imei problem.
Click to expand...
Click to collapse
I get your point, but I don't want to flash the ROM if I'm not sure that shall fix the IMEI Plus, I don't know how to do it, and what to download from that website.
imrock666 said:
Common issue... More than you imagine. Happens to me all the time. But I have one solution in my case Wich is just flash the EFS partition in my previous nandroid backup, but since to be you only were rooted and not custom recovery, I guess you don't have a nandroid backup. Only solution here is flash thru Odin and all will be good.
Click to expand...
Click to collapse
Hi imrock666, what do you mean by "flash trough Odin"? What's Odin and how can I do that? Forgive my huge ignorance
After trying to return to the original rom the device does not turn on, it always stays on that screen restarting. I've tried several methods and nothing. Can someone help me?
Your device has been unlocked and can't be trusted.
To learn more, visit: motorola.com/unlockbootloader
"ID: Bad Key"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wagnerwf said:
After trying to return to the original rom the device does not turn on, it always stays on that screen restarting. I've tried several methods and nothing. Can someone help me?
Your device has been unlocked and can't be trusted.
To learn more, visit: motorola.com/unlockbootloader
"ID: Bad Key"
Click to expand...
Click to collapse
Flash Stock Rom And Reloack Bootloader
How to install Stock Rom :- http://ceesty.com/wgKNj2
how to relock bootloader :- http://ceesty.com/wgKMau
How to Remove warning Logo :- https://forum.xda-developers.com/moto-g5s/how-to/remove-unlocked-bootloader-message-moto-t3699273
problem solved, thank you very much.
wagnerwf said:
problem solved, thank you very much.
Click to expand...
Click to collapse
welcome
Hello, y'all. I don't know that I'll get a reply any time soon, as this thread is over a year old, but I am having the same "ID: bad key" problem on my Moto G5S Plus (XT1806) and I have no idea what to do, being that I have not ever even unlocked the bootloader on a phone, as I am having this problem with a phone I bought from eBay that had this issue when I received it.
The full message that displays on my phone is this: "Your device has been unlocked and can't be trusted. - To learn more, visit: motorola.com/unlockbootloader - ID: bad key - Your device will boot in 5 seconds."
For the record, I'm not really concerned with this message being displayed after I restart the phone, as the message goes away after about 5 seconds and the phone starts up properly and is able to be used (*for the most part, with two issues, which I will describe below this paragraph*), it's that the phone will not see any Android updates and is still stuck on these outdated settings: Android version: 7.1.1 - Current version: NPSS26.116-61-8 - Security patch level: April 1, 2018. And I have tried to search for updates with my T-Mobile SIM card in the phone, and also when connected to my home WiFi, but it will not see a new update available.
* The two issues that I referred to earlier have to do with actually making calls on the phone, with outgoing calls taking like 20-30 seconds to actually start dialing and incoming calls not even ringing through to my phone and sending callers straight to voicemail (the phone shows no notification of someone having tried to call me). Text messaging works properly, and I am able to connect to a strong LTE signal with my T-Mobile SIM card in the phone and I can use apps and websites without any issues. However, outgoing calls take much longer to dial out than they should take, and incoming calls will not work at all.
So, I am hoping that flashing a different ROM on to the phone will fix these calling issues and also allow the phone to update to a more recent Android version. However, as I mentioned, I have not ever even unlocked a bootloader, much less, actually flashed a ROM on a phone, so I have no idea what I'm doing when it comes to things this. Also, for the record, I have tried multiple different APN settings on this phone, I have used my T-Mobile SIM card in another phone without any calling issues, and I have done multiple Factory Resets, but nothing has fixed the calling issues or allowed the phone to see any Android updates.
By the way, if flashing a different ROM might be worth trying on this device, being that I would be a first timer doing something like this, how difficult would this be? And about how long should the process likely take?
If anyone has any helpful advice, information or suggestions that they could offer me that might help to fix this issue with my Moto G5S Plus, I would appreciate any and all help that I could get!
If anyone sees this thread and is willing to offer a reply that might help me try to fix this issue with my Moto G5S Plus, I would really appreciate some help with this!
AzAssassin said:
If anyone sees this thread and is willing to offer a reply that might help me try to fix this issue with my Moto G5S Plus, I would really appreciate some help with this!
Click to expand...
Click to collapse
This message means the boot loader is unlocked. Honestly not a huge deal. If you do not plan on using TWRP or Root at all, search the forums on how to relock your boot loader. Otherwise if you wish to use a different recovery or root looks up the logofix which is easy to do. It will have the moto screen, but will say say bad key in small white letters. More thank likely the previous owner had unlocked the boot loader and then flashed it to factory stock before giving it back. That doesn't relock the boot loader so it gives that warning.