Develop Bugs

Accidentally Wiped Network. Null IMEI. Uknown Baseband.

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

bricked Lumia 550 (RM-1127) seen as Lumia BootMgr by Windows Device Recovery Tool

A Lumia 550 (RM-1127) phone in bootloop is recognized by Windows Device Recovery Tool as "Lumia BootMgr"
{
"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"
}
Besides pressing the Install software button, which will delete all content, is there anything else it can be done?

most likely not, data is lost. but the wdrt should be able to recover
i assume you bootet it manually into blink/flashmode,selected my device doesnt get recognized and chosed the 550? thats the right way to recover it
if even the blink/flash modus doenst work its not bricked then its physically defect cause that flashmodus part is located in a place of storage which isnt and cant be touched by any update

tofuschnitte said:
i assume you bootet it manually into blink/flashmode,selected my device doesnt get recognized and chosed the 550? thats the right way to recover it
Click to expand...
Click to collapse
Yes, otherwise it's not detected. When powered on, the phone displays the Microsoft text, the logo and then the screen goes black.

w.bogdan said:
Yes, otherwise it's not detected. When powered on, the phone displays the Microsoft text, the logo and then the screen goes black.
Click to expand...
Click to collapse
Whats the status now, bro. You get it working?

mabry said:
Whats the status now, bro. You get it working?
Click to expand...
Click to collapse
It's not my phone and I was waiting for some other suggestions. It's still under warranty and the owner might want to take it to an authorized service. It strange because the phone was not messed with, likely wasn't even connected to the Internet when it stopped working.

either the os itself ****ed up or its damaged
but the internal data is lost. no way to get them. just use the wdrt. you wont risk the warranty with reflashing it with the wdrt and if the device itself is not damaged it will work like it did before. if the wdrt isnt able to recover it -> rma it

I've got a little more info: the phone was running 10.0.10586.420 (version taken from Microsoft account - Devices) and crashed while starting the camera. It has been succesfully restored with WDRT to 10.0.10586.107 then OTA upgraded to 10.0.10586.545. For now, it looks good.

why was it stuck in 420 at all? that version is ooooooooooooooooold and should have got 494 and 545 in the last weeks.
and good that it worked (expected nothing else), and its normal that it flashed the .107. MS doesnt build images for every cumulative update (or lets say they never done it only for the 950 devices which were released with the .0 got updated images for the 107. maybe the 550 too? dunno if it was released that early together with the 950 devices)

tofuschnitte said:
why was it stuck in 420 at all? that version is ooooooooooooooooold and should have got 494 and 545 in the last weeks.
and good that it worked (expected nothing else), and its normal that it flashed the .107. MS doesnt build images for every cumulative update (or lets say they never done it only for the 950 devices which were released with the .0 got updated images for the 107. maybe the 550 too? dunno if it was released that early together with the 950 devices)
Click to expand...
Click to collapse
Some people actually use their phones to make phone calls and don't care for 1 hour OTA update every three weeks. Besides, it’s good to be able to call 911/112 if an emergency occurs and not wait for Microsoft to finish installing bloatware. Personally, I still use an eight-year-old Symbian phone which never fails me. My Lumia is just for fun, not like a real phone.

sure, thats why those updates autodownload and prepare and get itself installed in the night when you sleep
just wanted to say with that: something was borked with the os, cause it hasnt itself updated to newer versions (or was never connected to wifi in the last two months...)

tofuschnitte said:
sure, thats why those updates autodownload and prepare and get itself installed in the night when you sleep just wanted to say with that: something was borked with the os, cause it hasnt itself updated to newer versions (or was never connected to wifi in the last two months...)
Click to expand...
Click to collapse
It's possible that it hadn't connected to wifi, it had a data plan. But what if the problem was caused by a failed update? Just starting the camera app doesn't break all hell loose on the OS, doesn't it?

Lumia 550 android
Hi everyone
Can somebody help me for flash Android on a lumia 550
my question is, can i set a rom of android in a .ffu file for flash my lumia win phone 10 to android 6.0
hope somebody can help me

No Signal - won't connect to a network...

Picked up a used AT&T Note 5 recently, everything works except it won't connect to the T-Mobile network. I had previously bought a used(white) AT&T Note 5, factory reset it, put in my t-mobile SIM and bam, I'm up and running.
But with this (black) one I've tried just about everything, adding APN, check IMEI, etc....no dice. Even tried the T-mobile customer service. They tried & checked everything, no go. They even saw the device history and it was running on t-mobile just a couple months ago with the previous owner. I've even ran a ping test and turned the radio off & on in the diagnostics *#*#4636#*#*.
After investigating other threads it seems it could possibly be Marshmallow PE6 that screwed up the radio? But I would think it had been running on that previously.
Any other ideas?

Fredline said:
Picked up a used AT&T Note 5 recently, everything works except it won't connect to the T-Mobile network. I had previously bought a used(white) AT&T Note 5, factory reset it, put in my t-mobile SIM and bam, I'm up and running.
But with this (black) one I've tried just about everything, adding APN, check IMEI, etc....no dice. Even tried the T-mobile customer service. They tried & checked everything, no go. They even saw the device history and it was running on t-mobile just a couple months ago with the previous owner. I've even ran a ping test and turned the radio off & on in the diagnostics *#*#4636#*#*.
After investigating other threads it seems it could possibly be Marshmallow PE6 that screwed up the radio? But I would think it had been running on that previously.
Any other ideas?
Click to expand...
Click to collapse
Just try downloading a different firmware(older) and pull the modem.bin out of the tar file and then re-zip it again into a modem.tar file so it can be flashed with odin but don't try going to far back like if you're on Marshmallow don't try flashing a modem from Lollipop because it won't work.. I use 7zip for the extracting and zipping of files.

Well, the plot thickens.
When I checked the IMEI before purchase on Swappa it said all was good. However, they couldn't identify the type or provider of the phone. I didn't think much of it at the time. So I decided to double check the IMEI on a different 2 other checking sights last night and I got the following info(from both!):
{
"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"
}
Clicked "Network Check" and it said: "IMEI not found on database."
Wtf? Can this be fixed? Is this causing my network issue?

I also checked the IMEI on the back cover, and it states it's clean, not blacklisted and is for an AT&T Note 5.
Anyone restore an IMEI?

Fredline said:
I also checked the IMEI on the back cover, and it states it's clean, not blacklisted and is for an AT&T Note 5.
Anyone restore an IMEI?
Click to expand...
Click to collapse
Messing with the IMEI is illegal! Are you sure you didn't buy a fake phone? Do you have a picture of the front of the phone?

MrMike2182 said:
Messing with the IMEI is illegal! Are you sure you didn't buy a fake phone? Do you have a picture of the front of the phone?
Click to expand...
Click to collapse

Fredline said:
Click to expand...
Click to collapse
Download an app called phone info from the play store over wifi and see if the settings match what they're supposed to for the phone. Is there a sim card in the phone?
http://m.gsmarena.com/samsung_galaxy_note5-7431.php

Yes it recognizes the SIM but still, no network found.
Cosmetically nice phone, guess I'll re-sell for parts.
Thanks anyway, appreciate the responses.

For tmoble you have to unlock it.

Moto g5 plus id bad key

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.

Mi 9 SE bricked after successful MIUI 11 Update

Hello everybody!
I have a problem with my Xiaomi Mi 9 SE. This is what happened:
Few days ago I updated to MIUI 11. Everything seemed to run smoothly.
2 days ago I noticed a huge battery drain during the day. I finished my day with my battery @ 10/1% with my usual daily use.
Yesterday I was using my phone normally while it was charging (watching a video on Youtube). The phone became unresponsive to everything: the touchscreen was not working, the buttons on the right were not working.
I decided to "hard-reboot" my phone. I pressed the on/off button for a few seconds.
The screen turned off.
From this point on, my phone was completely bricked. It does not turn on in any way possible: I tried also pressing the on/off button + volume up or down but nothing. Nothing happens even connecting it again to the power cord.
I tried connecting my phone to the PC via USB and this is what my PC recognized:
{
"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"
}
But my phone still remains bricked/with its screen black.
Has anyone else experienced this problem? Do you have any suggestions on how to fix this or at least recover my data in some way?
I suspect some bug related to battery mgmt in the MIUI 11 and I personally do not suggest you to update to it right now.
Thank you very much in advance!

You're on edl mode. I've been there. Unfortunately, Xiaomi doesn't allow us to recover our phones on edl mode, which is a shame. So, there are two options:
1 - Send it to the seller and try a fix/replacement.
2 - Pay someone with edl authorization to unbrick your phone.
If you want, I'll give you the contact of the person who did that for me. But I had unlocked the bootloader and flashed several ROMS. I bricked the phone trying to restore a full backup. Your case is different and, for what you described, you may be experiencing hardware problems, so I would go for option one.

elpaablo said:
You're on edl mode. I've been there. Unfortunately, Xiaomi doesn't allow us to recover our phones on edl mode, which is a shame. So, there are two options:
1 - Send it to the seller and try a fix/replacement.
2 - Pay someone with edl authorization to unbrick your phone.
If you want, I'll give you the contact of the person who did that for me. But I had unlocked the bootloader and flashed several ROMS. I bricked the phone trying to restore a full backup. Your case is different and, for what you described, you may be experiencing hardware problems, so I would go for option one.
Click to expand...
Click to collapse
Thank you very much for your reply! I really feel disappointed because I never messed up with my phone. I always used official releases. Since I bought it in Italy and now I'm far away from my country, I would go for option 2. Do you know if it is possible at least to recover my photos? Honestly that's the most important thing for me right now and unfortunately I forgot to enable the backup (my bad!).
We can speak in private if you prefer, send me a message with the details of the person that helped you.
Thanks!

Digiaro2 said:
Thank you very much for your reply! I really feel disappointed because I never messed up with my phone. I always used official releases. Since I bought it in Italy and now I'm far away from my country, I would go for option 2. Do you know if it is possible at least to recover my photos? Honestly that's the most important thing for me right now and unfortunately I forgot to enable the backup (my bad!).
We can speak in private if you prefer, send me a message with the details of the person that helped you.
Thanks!
Click to expand...
Click to collapse
Just to update everyone on the status: my phone is still bricked. I contacted the guy suggested by elpaablo but he just suggests to re-flash my phone while I want to recover my data first. I will leave my phone in the closet for 1/2 weeks and then try again to turn it on because I read on other threads that this worked for other people.
I will update this thread later on. I want to highlight again that I did not do anything weird with my Mi 9 SE: no twrp, no custom rom, no weird flashing, nothing. I just updated successfully my phone to the global stable using the official update menu in the settings.

Use your warranty. Your phone should be replaced. As for your photos, didn't you use some kind of backup, like google photos?

elpaablo said:
Use your warranty. Your phone should be replaced. As for your photos, didn't you use some kind of backup, like google photos?
Click to expand...
Click to collapse
Yeah I already contacted my seller and I'm going to ask for repair/replacement. Unfortunately I was not using a backup solution (my bad!).