his phone has been flashed with unauthorized software and is locked
call your mobile operator for additional support
pleas note that repair/return for this issue may have addtional cost
what i need to do
tanks?
daniellamp said:
his phone has been flashed with unauthorized software and is locked
call your mobile operator for additional support
pleas note that repair/return for this issue may have addtional cost
what i need to do
tanks?
Click to expand...
Click to collapse
which procedure you followed?
daniellamp said:
his phone has been flashed with unauthorized software and is locked
Click to expand...
Click to collapse
The message means just what it says. The phone has detected that you installed or changed some system files that it doesn't like. And is exhorting you to go to a service center and let them return your phone to 100% stock.
We would know a lot more and could have given you a lot better advice had you provided basic and critical information such as which S5 model you have and exactly which files you tried to write to your phone. Since you didn't provide those crucial details, we have no idea what is really going on. Presumably you wrote the wrong firmware to the phone or botched a rooting process.
Without any details, all I could suggest is that you use the Odin software to write a 100% stock firmware file the phone, followed by a factory data reset. This will remove any user files or changes and should resolve the error message. Then you can redo whatever you were trying to do.. root, update, etc.
.
Flash a different kernel made for your device, that is also a kernel error. good luck.
Actually, you need to provide a little more info, like what base are you running and so on. Complete questions will yield complete results.
Could this also be an indication that somebody has injected wiretap/spyware software on your phone? Interestingly, I recently went through a separation and within a week following the separation, my phone began to lag (became very slow), would shut down spontaneously, had less memory space available (without any evident source for the cause of a memory reduction (and with a 64 gb SD card)), and on two occasions, producing this message with an exclamation point contained within a yellow triangle immediately after a spontaneous (not user initiated) reboot, and those reboots occurred with more than enough power to operate (one time at or around 50% and the other at 11%).
Also, soon after I noticed the issues with the phone, I received a T-Mobile "Emergency Security Update" notification. It was not mandatory. I proceeded with the update. Then, within a week thereafter, I received another, that not only stated that it was an Emergency Security Update, but was mandatory, and further provided notice that to ensure that my device had not been compromised, the security update was necessitated.
A question of interest on that note, is whether or not the breach (wiretap & spyware software - (vendors available on-line)), occurred only at the device level, or whether or not it modified the SIM. It would seem, if in any event, the above did occur, that a hard reset, probably three times over, and a new SIM would be in order, if for no other reason than diligence in trying to ensure the integrity of the device and SIM (privacy/protection).
My Phone: G Note 4 (32 GB Internal / 64 GB Ext.)
Any thoughts?
fffft said:
The message means just what it says. The phone has detected that you installed or changed some system files that it doesn't like. And is exhorting you to go to a service center and let them return your phone to 100% stock.
We would know a lot more and could have given you a lot better advice had you provided basic and critical information such as which S5 model you have and exactly which files you tried to write to your phone. Since you didn't provide those crucial details, we have no idea what is really going on. Presumably you wrote the wrong firmware to the phone or botched a rooting process.
Without any details, all I could suggest is that you use the Odin software to write a 100% stock firmware file the phone, followed by a factory data reset. This will remove any user files or changes and should resolve the error message. Then you can redo whatever you were trying to do.. root, update, etc.
.
Click to expand...
Click to collapse
i have the same error my phone is galaxy S6 Edge SM-g925T after actualization send for T-MOBILE i have that error.
Related
Hey all,
So I've ran into a snag on my XT910 over the past few days.
Randomly, the device just dropped signal one evening and it never recovered it. Having troubleshooted with my network (O2 UK) and trying other SIM cards in the device, I have narrowed it down to the "Unknown baseband" or "No IMEI" symptoms found on these forums.. The device downright refuses to read (or even acknowledge the existance of) any SIM cards at all. It doesn't prompt for one to be inserted; it just says "No Service" where my network name should be, with an antenna and red "x" where the signal bars should be. Trying a working micro SIM from my girlfriends phone yields the same result. It doesn't even know it is in there.. In "About phone" it says Unknown baseband and dialing *#06# from my device gives a blank IMEI. Adding/viewing contacts on the SIM returns an error. I went so far as to get a brand new SIM from my network - still no dice.
The device is less than a month old and still under Moto warranty. However, the company I bought it from have neglected to provide a VAT receipt and I'm having trouble getting it off them. Moto have agreed to repair/replace the phone, but on the condition I have this receipt and send a copy of it to them. I really need this phone working, as it's the lifeline to my work, so I am willing to try reflashing/rooting the device ROM or radio as need be.
After some reading I have followed QPST guides to re-input the IMEI on my device, however it still exists and is correct. I have hard reset the phone, booted into recovery and wiped cache/data but no change.. I am considering the method of re-flashing the official OTA update for ICS, as I've read many users have this issue after upgrading, here: http://forum.xda-developers.com/showthread.php?t=1849744 - that is the correct ROM for my phone, but as I am already on that ROM I do not know whether flashing it on top will break things - ultimately brick it?
The device was (and still is) on 672.180.41.XT910.Retail.en.EU. I have not flashed any custom ROMs or rooted it. I have made no software or firmware changes to the device.
Please can someone help?! I do not mind getting my hands dirty and even voiding the Moto warranty if it fixes it (I would also be prepared to root it) but I am at a loss here - all pointers go to hardware fault and if that is indeed what it is, I would prefer somebody back up my assumption so I can send it to Moto knowing there was nothing I can do, rather than being a simple ROM flash away from having my device back..
Your phone may be damaged either physically (e.g. broken contacts SIM card slot) or software-wise (e.g. damaged PDS partition).
I'd go for a reflash, though - at least when properly executed it won't worsen your phone's condition. First, get full 672.180.41.XT910.Retail.en.EU flash file. Then, flash it using RSD Lite.
Vatazhka said:
Your phone may be damaged either physically (e.g. broken contacts SIM card slot) or software-wise (e.g. damaged PDS partition).
I'd go for a reflash, though - at least when properly executed it won't worsen your phone's condition. First, get full 672.180.41.XT910.Retail.en.EU flash file. Then, flash it using RSD Lite.
Click to expand...
Click to collapse
Thank you so much for this.
If it doesn't work by reflashing, can I still send it to Motorola under warranty for a hardware fix?
FrankPlummer said:
Thank you so much for this.
If it doesn't work by reflashing, can I still send it to Motorola under warranty for a hardware fix?
Click to expand...
Click to collapse
Hey,
I've just reflashed with RSD and I still get "Unknown baseband version" and no IMEI on the device. I guess it must be a hardware fault somewhere along the line.. Thank you regardless - and if you have any further suggestions then please do let me know.
try changing baseband. who knows...
china baseband is perfect for EU
heblu said:
try changing baseband. who knows...
china baseband is perfect for EU
Click to expand...
Click to collapse
How would I go about doing that?
I'd really like to know too...
Sent from my GT-N7100 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1863106
install baseband via custom recovery. they are flasheable zip
Firstly, thank you to all who replied to or considered my plea.
Secondly, after extensive research and some testing on my part I have found this is a seemingly irresolvable hardware (or very heavily damaged software) problem. Through various threads online I have read about people getting this mostly after they upgrade their Razr to ICS. It doesn't seem to be limited to one specific baseband/regional version of the device, as customers on Verizon in the States have had the same issue I have in the UK with a SIM-free phone.
I have sent the device off to Motorola for repair/replacement. I will report back when I get the device back.
FrankPlummer said:
Firstly, thank you to all who replied to or considered my plea.
Secondly, after extensive research and some testing on my part I have found this is a seemingly irresolvable hardware (or very heavily damaged software) problem. Through various threads online I have read about people getting this mostly after they upgrade their Razr to ICS. It doesn't seem to be limited to one specific baseband/regional version of the device, as customers on Verizon in the States have had the same issue I have in the UK with a SIM-free phone.
I have sent the device off to Motorola for repair/replacement. I will report back when I get the device back.
Click to expand...
Click to collapse
si I guess it never returned from tha one trip to the repair service?
...im hvinga similar problem with the xt890 (moto RAZR i)
updated to 4.4.2 kitkat, and it lost its anthena. like forever.
since then, spent nights surfing sesrching for a clue. nothing.
even unlocked the bootloader. it ended with the never endings WARNING BOOTLOADER UNLOCKED thing. sometimes i can bypase it buy antherna is still gone.
there are no replacementes for this device i think.
i want to use it so bad
Jorge_Amaya said:
si I guess it never returned from tha one trip to the repair service?
...im hvinga similar problem with the xt890 (moto RAZR i)
updated to 4.4.2 kitkat, and it lost its anthena. like forever.
since then, spent nights surfing sesrching for a clue. nothing.
even unlocked the bootloader. it ended with the never endings WARNING BOOTLOADER UNLOCKED thing. sometimes i can bypase it buy antherna is still gone.
there are no replacementes for this device i think.
i want to use it so bad
Click to expand...
Click to collapse
I have the same problem with xt890
Hello again, I really think I messed up this time as I was trying to unlock my phone (alt carriers). I followed directions off a vague website and didn't realize it wasn't for my specific device. Any who, this is what I did.
Hidden menus were already enabled..
Dialer "*#0011#"
Menu > Back
Menu > Key Input "1"
Debug Screen > Phone Control > Network Lock
Selected PERSO SHA256 OFF
Went back to the main menu
Common > NV Rebuild > Restore Backup
Ever since doing this regardless if I revert and turn SHA back on I have data, I can text but cannot place a phone call and I get bumped off network once and a while. Any idea how I can revert these changes?
I have already factory reset / reinstalled the Rom from scratch. No change and my next step would be odin but I was hoping to avoid having to go through all that.
Any ideas?
Thank you all in advance,
Colton 22
more info
I have also confirmed that doing an Odin I still have the same issue. .. Should I contact vzw and say my headphone jack is bad? Downloading Stock ot a update now which I dont want to do... Lock the phone down ...
[SOLVED] I have been able to revert changes to ServiceMode
I had to Odin back to stock (before root).. I used the No-wipe method offered from my phone.
secondly I actually updated stock OTA software (process failed so it didnt work ^_^ )
- (dont think this step is needed however i did it and it didnt change me to any new version. Still on MDK thankfully)
Factory reset from within system settings and allow it to delete all local sdcard data doing so,
Problem solved. Just working on getting back to my full custom status now !
ALSO FOR INFORMATION
After calling Verizon and asking if they could walk me through the process of unlocking my phone's sim card for othercarriers i was informed that the Verizion GS4 is already unlocked and shouldnt need any alt methods to do it. Just change Mobile Networks to GSM and shut down. Insert new SIM and power on.
Colton22
colton22 said:
I had to Odin back to stock (before root).. I used the No-wipe method offered from my phone.
secondly I actually updated stock OTA software (process failed so it didnt work ^_^ )
- (dont think this step is needed however i did it and it didnt change me to any new version. Still on MDK thankfully)
Factory reset from within system settings and allow it to delete all local sdcard data doing so,
Problem solved. Just working on getting back to my full custom status now !
ALSO FOR INFORMATION
After calling Verizon and asking if they could walk me through the process of unlocking my phone's sim card for othercarriers i was informed that the Verizion GS4 is already unlocked and shouldnt need any alt methods to do it. Just change Mobile Networks to GSM and shut down. Insert new SIM and power on.
Colton22
Click to expand...
Click to collapse
Yup. It's not locked from the factory since they can't. I don't know what you did to your phone with the config rebuild from some random backup, but it's apparently not good. And all this to unlock something that wasn't locked in the first place. Sad.
The backup wasn't a random one, it's generated while in service mode called the 'golden backup'. There is speculation it was meant to be the script to unlock the phone but this proves that wrong. All seems well so far but I have read of others with this same issue after following the first result on Google about unlocking the GS4 (not vzw specific).
I don't understand how this could be classified as sad though. Sad would involve ignorance, not acts from being naive.
Best regards,
Colton22
colton22 said:
The backup wasn't a random one, it's generated while in service mode called the 'golden backup'. There is speculation it was meant to be the script to unlock the phone but this proves that wrong. All seems well so far but I have read of others with this same issue after following the first result on Google about unlocking the GS4 (not vzw specific).
I don't understand how this could be classified as sad though. Sad would involve ignorance, not acts from being naive.
Best regards,
Colton22
Click to expand...
Click to collapse
"Sad" as in getting and acting on bad advice. It's sad that there's so much info out there that doesn't tell people when it applies and when it doesn't, leading folks down the wrong path. YouTube is full of that kind of noise.
Indeed it is and the more popular the phone is, the more half truths are available. I do hope this post helps others who had the same issue.
When I started this I was with
Hyperdrive RLS13 OCd UVd Xposed on KToons Kernel.
Take care all and know your sources ha! Lesson learned.
Colton22
Hello everyone, I'm a desperate noobie here trying to fix this issue for three days now.
So as stated above I have a Samsung Core Duo (SM-G335H) and three days ago I connected trough SmartSwitch and it offered to update my phone. I agreed and during the middle/second half of it my laptop and phone just crashed. I revived both and SmartSwitch told me about the update failure and I made an Emergency Recovery. After that recovery, at first, everything seemed to be working normally, but on the next day I noticed: "Not registered on network " error. It recognizes the SIM card, but when you try to find a network it says "Can't connect. Try later." and so on. I can't call, other peeps can't call me.
I have been researching this matter for days now and am very upset about this. Some say stuff like Odin/flashing/third party tools/settings, I don't know what to do, as I don't have much experience with those things.
Btw, my IMEI is not null, it is being displayed (so I guess the EPF folder is not damaged). The APN settings (I'm on T-mobile) are still there, I don't know what to fix about them.
I am running 4.4.2 KitKat and my Security Patch Level is dated 2016 if that is of any relevance...
I also did a hard reset: nothing. SIM card works in my other phone, so it's not damaged. I just now saw that the end symbols in my Baseband version and my Build number don't match. Could that be it? I've seen people recommending updating manually/flashing with a modem file. How do I go about this?
Also: my phone is rooted. Only that I very clumsily attempted it months ago and before this matter here I would have problems with binary updates and what not, "phone is not rooted completely", I already fixed that issue though, it has SuperSu on it.
Anyway, I may have messed up somewhere along the way leading to this problem.
Please don't recommend me reseting/rebooting the phone again or just re-inserting the SIM card, that doesn't fix it.
I welcome any other suggestions, I hope somebody can help me.
Device model: TA-1178
I cannot upgrade my device to the current firmware no matter what I do.
- No OTA comes in the updater app
- No amount of VPN, clearing various app caches and data helps.
- captured OTAs are available elsewhere but cannot be installed, the phone appears to have sideloaded OTAs restricted
Does anyone has an idea how to proceed here ? will it work if I factory reset without SIM card?
crrodriguez said:
Device model: TA-1178
I cannot upgrade my device to the current firmware no matter what I do.
- No OTA comes in the updater app
- No amount of VPN, clearing various app caches and data helps.
- captured OTAs are available elsewhere but cannot be installed, the phone appears to have sideloaded OTAs restricted
Does anyone has an idea how to proceed here ? will it work if I factory reset without SIM card?
Click to expand...
Click to collapse
Few questions?
1) What provider?
2) Is device rooted?
3) Are you connected to Wi-Fi when attempting update?
4) Is your device fully charged when trying to update?
Answers to these questions will allow me and others to try and help. We may not be able to assist but the answers will give us a place to start.
Thanks for your answer.. it was user error really, forced update worked after cleaning up google framework data and cache, I missed that one in my previous attempts. now at Dec 5 patch level.
Sorry for the noise.
I am at the same problem have tried all the above, via wifi and 4g, model 7.2 TA.1196 Aus.
Fully charged, stock, Belong Australia yet our networks have no input to when a manufacturer releases updates to devices that are unlocked that is solely the manufacturers responsibility by law. Only contracted devices have network inputs for branding otherwise our frequency is published on a government site for companies to use. Nothing ever released since buying the device in September.
Hi all,
Alright so this is going to be a long post. So I recently flashed my phone to the U1 firmware, I currently have an unrooted Verizon Unlocked Samsung S9+. I wanted to switch phone carriers over to Visible (subsidiary of Verizon), here are the order of events that occurred:
1. Visible's website says that my device in not compatible using their IMEI checker, there is a solution that was found on reddit about flashing the device on the U1 firmware.
2. I flashed the device on the U1 firmware using Odin and the Visible SIM card worked as expected. No issues with the flash
3. Data/Texts etc.. are all working as expected. Except for Voicemail.
When I try to check my Voicemail, it is acting as if it's still on the Verizon Voicemail system. It says "Welcome to the message management system, please enter your mailbox number". No one can leave me a VM either because of this. I tried several different combinations of numbers, including my full 10 digit cell number and last 4, to which it says "XXX is not a valid mailbox number", which would be because my number is no longer active on Verizon, so it's unable to access it. Which makes sense. The Visible Customer Care team tried the following:
1. Provisioning my VM multiple times
2. Take out SIM card, turn phone off for 1 min, insert SIM card again, and toggle airplane mode for 30 seconds
3. Reset network settings
After numerous days of troubleshooting with them, eventually they said it was because my device isn't compatible, ok, I can't argue with that. I have not seen anyone else experiencing this issue that had flashed their phone to U1 firmware.
After trying all of this with them, I eventually factory reset my device, hoping that might do something. That still did not work.
My questions is, is there something I missed with flashing the U1 firmware? Why is it still using Verizon's VM system even though I flashed it to U1? Is there any way to fix this? Any help is greatly appreciated, and please don't hesitate if you need any other information.
bornxawkward said:
Hi all,
Alright so this is going to be a long post. So I recently flashed my phone to the U1 firmware, I currently have an unrooted Verizon Unlocked Samsung S9+. I wanted to switch phone carriers over to Visible (subsidiary of Verizon), here are the order of events that occurred:
1. Visible's website says that my device in not compatible using their IMEI checker, there is a solution that was found on reddit about flashing the device on the U1 firmware.
2. I flashed the device on the U1 firmware using Odin and the Visible SIM card worked as expected. No issues with the flash
3. Data/Texts etc.. are all working as expected. Except for Voicemail.
When I try to check my Voicemail, it is acting as if it's still on the Verizon Voicemail system. It says "Welcome to the message management system, please enter your mailbox number". No one can leave me a VM either because of this. I tried several different combinations of numbers, including my full 10 digit cell number and last 4, to which it says "XXX is not a valid mailbox number", which would be because my number is no longer active on Verizon, so it's unable to access it. Which makes sense. The Visible Customer Care team tried the following:
1. Provisioning my VM multiple times
2. Take out SIM card, turn phone off for 1 min, insert SIM card again, and toggle airplane mode for 30 seconds
3. Reset network settings
After numerous days of troubleshooting with them, eventually they said it was because my device isn't compatible, ok, I can't argue with that. I have not seen anyone else experiencing this issue that had flashed their phone to U1 firmware.
After trying all of this with them, I eventually factory reset my device, hoping that might do something. That still did not work.
My questions is, is there something I missed with flashing the U1 firmware? Why is it still using Verizon's VM system even though I flashed it to U1? Is there any way to fix this? Any help is greatly appreciated, and please don't hesitate if you need any other information.
Click to expand...
Click to collapse
Please check your voice mail settings in your phone app. See my screenshots.
There you should select the correct service provider and the Visible mailbox number.