Database Develop

xt862 Problems with radio

Hello. I have a problem with the droid 3 xt862. The phone is locked by verizon. The problem is that it has a software fault with the radio. In the setting of an android - "baseband version - unknown". IMEI - empty, the hardware menu * # * # 4636 # * # * in the phone info shows - unknown, disconnected, out of service, false. Unlock also does not work - after insert sim card - nothing happens, after entering the code to unlock # 073 887 * - "The process com.android.phone has stopped unexpectedly. Please try again"
I tried to flash swu with rsd, tried to flash other roms,tried to flash via recovery, bootstrap, safestrap , tried to "Flash Verizon DROID three OTA 5.6.890 to phone_psouza4", tried to flash a different radio.img - always in the baseband version - unknown.
P.S. I apologize for my English.

Has it ever worked on Verizon in your possession, or did you buy it this way? If you bought it this way you could probably send it back under warranty. I would definitely try to use this method http://forum.xda-developers.com/showthread.php?t=1339816 to flash back to stock. If it still has problems after flashing that way, then try to send it in anyway and see if they'll replace it.
If you bought it that way from someone else, try flashing using the above mentioned method and see if it works.
If it doesn't work or if it got this way because of you messing with the radio, I have no clue what else to do to fix it. Seems like it's above my level.
P/S: to unlock the phone using a Verizon unlock code, I believe the phone must be connected to an active line of service so that it can communicate with VZW. Entering the code only prompts the phone to communicate with them so they can unlock it from their end. So, it kind of makes sense that it would have no service whatsoever and that inserting a SIM would do nothing if the phone has no service from VZW and hasn't been unlocked.

BenSWoodruff said:
Has it ever worked on Verizon in your possession, or did you buy it this way? If you bought it this way you could probably send it back under warranty. I would definitely try to use this method http://forum.xda-developers.com/showthread.php?t=1339816 to flash back to stock. If it still has problems after flashing that way, then try to send it in anyway and see if they'll replace it.
If you bought it that way from someone else, try flashing using the above mentioned method and see if it works.
If it doesn't work or if it got this way because of you messing with the radio, I have no clue what else to do to fix it. Seems like it's above my level.
P/S: to unlock the phone using a Verizon unlock code, I believe the phone must be connected to an active line of service so that it can communicate with VZW. Entering the code only prompts the phone to communicate with them so they can unlock it from their end. So, it kind of makes sense that it would have no service whatsoever and that inserting a SIM would do nothing if the phone has no service from VZW and hasn't been unlocked.
Click to expand...
Click to collapse
I've already tried this method - successfully flashed (radio.img too), but there is no effect, baseband version - unknown and all the problems.
Thank you for your reply.
p.s. return is not possible, unfortunately.

w4_toleg said:
I've already tried this method - successfully flashed (radio.img too), but there is no effect, baseband version - unknown and all the problems.
Thank you for your reply.
p.s. return is not possible, unfortunately.
Click to expand...
Click to collapse
This phone has a 1 year warranty from Motorola (software included). If it doesn't work and has not been physically damaged, water damaged or has a bad ESN, Motorola will replace it. If you can't go through Verizon (no contract), then contact Motorola directly for a replacement.
Side note: If/when you send it back to Motorola, make sure it is bone stock and unrooted as this would clearly void the warranty.
Sent from my XT862 using XDA App

Sounds like they haven't even unlocked the phone from Verizon yet. Nothing will help this phone work on another carrier (other than Vodafone) if it hasn't been unlocked by Verizon. I mentioned above what to do if you can get a code from Verizon, otherwise good luck finding some code online somewhere.
I may be wrong, but even if you have a Verizon unlock code, I don't think it will work unless the phone is connected to a valid account, temporarily so it can communicate with VZW.

I have the same issue with my Droid3, help please

lost 3G edge2 work fine
eldar4uk said:
I have the same issue with my Droid3, help please
Click to expand...
Click to collapse
I've tried a lot of time: wipe factory/wipe cache/dalvik but nothing 3G. I've also unistalled safestrap. PLEASE without 3G is very frustrant!!!

Note 5 FRP LOCK, phone doesnt open.

Hi guys, i have note 5 (n920c) rooted. I recently installed adaway, and program requests to restart and i press restart button.After that now phone didnt open.It says custom binary blocked by FRP lock.Im searching internet since morning.Therefore, as i see flashing stock rom with odin works.Now ı have 6.0.1 N920CXXU2BPB9(18 february) version but this version changed now it is N920CXXS2BPE4. Should i flash the older version which is exactly same on my phone or newer version? OR what can i do else?

Newer version

That means you accidentally turned off OEM UnLock which you have to keep Turn on Find it In Settings>About Phone> Keep Clicking Build Number Until It Says Developer Mode On Then Go Back To The Setting First Panel And Look For Developer Options And Turn On OEM Unlock And Then You Should Have That Problem No More. Only Fix To Get Your Phone Back on Restore It To Stock Samsung Firmware Heres a video that teaches how to Unroot what you need to do to fix it: https://youtu.be/RRzIvcJDyEA After you do what the video tells you follow the setup screen and put you last google account you had before having that issue. Then Root your phone again if thats what you want but dont turn off Oem Unlock Ever again while been rooted cause samething will happen.
Install Latest version BTW

Need a solution badly.."Invalid ID:Device ID must be a valid IMEI or MAC address."

Need a solution badly.."Invalid IDevice ID must be a valid IMEI or MAC address."
"Invalid ID:
Device ID must be a valid IMEI or MAC address. Without device ID, some Mi Account and Cloud features won't be available."
then it goes for checking device status
Followed by this error:
Couldn't check the Find device status.
What l had done.
A month ago my mi3 started showing "insert sim card" though there was already one in the mobile, i thought that this because of newly "weekly update" but after next update it didn't solved, so i searched for the problem on google and this forum and i found that this problem is hardware one. So i went to the expert, he checked and said that the sim tray is running fine. Then again i waited for an update and it arrived but then again it didn't solved.
Finally i applied "Wipe & Reset" and came the disaster, miui 8 started in fashion but while i was in some elementary steps of selecting language and country I was encountered with this error--
"Invalid ID:
Device ID must be a valid IMEI or MAC address. Without device ID, some Mi Account and Cloud features won't be available."
and I finally stopped at MIUI ACCOUNT Details form.
Followed by this error:
Couldn't check the Find device status.
I reset it several times but the outcome is nil.
I even tried Flashing using Mi pc suite with "miui V7.5.6.0.MXDCNDE" it does nothing and repeated again and again except changing miui 8 (6.7) developer to miui 7.5 stable.
I have no EFS saved
Current status.
phone not opening competely, no debugging option on, no root access.
Is there anyone who can help and guide me.

If you have not tried fastboot, then give it a try. And after it boots try to skip all the MI authentication steps. I think Mi framework is checking something and then giving you error.

Try flashing an old backup. I had the same issue but on pa 6.0(unofficial) or flash a cm rom and see if the problem exists.

There are modules for XPOSED that will allow you to force an IMEI or change various device ID information, you'll be good

Security Error and Network Lock

A few days after updating my phone to Nougat, my phone restarted itself, and after the restart, a security error showed up saying "This phone has been flashed with unauthorized software and is locked", and after unlocking the phone a screen came up saying that my device has been network locked and it can be unlocked using the device unlock app, and the invalid sim card error.
I was never rooted or anything like that, my phone had received OTA updates. I did not master reset, but I rebooted many times, and the error message appeared on every boot, but disappeared after a while allowing me to use my phone. And now, although the error doesn't seem to appear anymore, i still can't use my network, and when I checked the IMEI, it had changed to 350000000000006, and the one on the back is different.
Is there any possible way to fix this without sending this phone back to Samsung/T-Mobile for exchange, because I had bought this phone from USA but brought it to Pakistan, and Samsung Pakistan says that they would charge me for the repairs ( I still haven't visited them, they told this to me through mail).
HELP PLEASE?

Bump?

Have you tried using Samsung Smart Switch?

DevicesNow said:
Have you tried using Samsung Smart Switch?
Click to expand...
Click to collapse
I didn't try Samsung Smart Switch, but I had reflashed it using Odin, and tried a factory reset and it didn't fix it, i got it fixed through Z3X box.

This happened to me also.
ashal said:
A few days after updating my phone to Nougat, my phone restarted itself, and after the restart, a security error showed up saying "This phone has been flashed with unauthorized software and is locked", and after unlocking the phone a screen came up saying that my device has been network locked and it can be unlocked using the device unlock app, and the invalid sim card error.
I was never rooted or anything like that, my phone had received OTA updates. I did not master reset, but I rebooted many times, and the error message appeared on every boot, but disappeared after a while allowing me to use my phone. And now, although the error doesn't seem to appear anymore, i still can't use my network, and when I checked the IMEI, it had changed to 350000000000006, and the one on the back is different.
Is there any possible way to fix this without sending this phone back to Samsung/T-Mobile for exchange, because I had bought this phone from USA but brought it to Pakistan, and Samsung Pakistan says that they would charge me for the repairs ( I still haven't visited them, they told this to me through mail).
HELP PLEASE?
Click to expand...
Click to collapse
The same has happened with me. Can you please tell me how you managed to unlock. From where? how much it costed? Please help me. Thanks.

Hunterzzz said:
The same has happened with me. Can you please tell me how you managed to unlock. From where? how much it costed? Please help me. Thanks.
Click to expand...
Click to collapse
I had taken in to a repair shop who had a Z3X box. That's the only way to get it fixed. He downgraded my phone to Marshmallow and re-flashed the cert. I live in Pakistan and that costed my Rs.1000 (i.e. $10). Make sure you take your phone's box with you as a proof of purchase because changing IMEIs is illegal in many places.
P.S. I can't upgrade to Nougat now, if I will, the phone won't register to the network.

ashal said:
I had taken in to a repair shop who had a Z3X box. That's the only way to get it fixed. He downgraded my phone to Marshmallow and re-flashed the cert. I live in Pakistan and that costed my Rs.1000 (i.e. $10). Make sure you take your phone's box with you as a proof of purchase because changing IMEIs is illegal in many places.
P.S. I can't upgrade to Nougat now, if I will, the phone won't register to the network.
Click to expand...
Click to collapse
Thanks mate. I also live in Pakistan - Lahore. I took my phone to Hafeez center and they charged me 1500. Now the phone is on Marshmallow. I'm receiving notification of update. I've tried 3 times but if failed to install. When I tap on update it downloads the OS which is about 1.3GB. then restarts to install but it fails when reaches 30%.
Can you please tell me why we can't update our phones. I'm using another s6 which is also of T-mobile and it's running fine on nougat.

Hunterzzz said:
Thanks mate. I also live in Pakistan - Lahore. I took my phone to Hafeez center and they charged me 1500. Now the phone is on Marshmallow. I'm receiving notification of update. I've tried 3 times but if failed to install. When I tap on update it downloads the OS which is about 1.3GB. then restarts to install but it fails when reaches 30%.
Can you please tell me why we can't update our phones. I'm using another s6 which is also of T-mobile and it's running fine on nougat.
Click to expand...
Click to collapse
Not sure about that but we can't update because probably our CERT files have been patched in EFS is messed, I got it done back in July 2017, and at that time, the guy who repaired it said that they didn't have Z3X's software update for Nougat, so they had to downgrade my phone to Marshmallow, and the patch they used won't work on Nougat. Don't know about yours though, maybe he used an updated patch or a different tool, you can ask that guy whether if its safe for you to update to Nougat or not, if he allows it, then try flashing Nougat through Odin, if it doesn't work you'll have to get it patched by him again. Don't update if he doesn't allow, otherwise he won't patch it again without extra charges, and if he allows that and something goes wrong you can blame him for that

Going back to Oem bootloader lock?

Hello,
I have the SM-N960F/DS phone who is presently Oem unlocked. Unfortunately, Google safety net fails with CTS profile mismatch because of this, and thus I can't use google pay.
If i turn Off Oem locked, what will be the consequence? I guess the device will get formatted, but is there any thing i should be aware about?
Thanks
Sent from my SM-N960F using Tapatalk

rajil.s said:
Hello,
I have the SM-N960F/DS phone who is presently Oem unlocked. Unfortunately, Google safety net fails with CTS profile mismatch because of this, and thus I can't use google pay.
If i turn Off Oem locked, what will be the consequence? I guess the device will get formatted, but is there any thing i should be aware about?
Thanks
Click to expand...
Click to collapse
In my case with my old Note 8 ( also my old Note 5 )
i was not rooted and i switched OEM unlock, on and off
(2 or 3 times over a period of time).
Nothing really "happened" My device was not "formatted" /factory reset. etc.
Further, i also noticed, that when i unlocked OEM, my Google Play store, had shown
in Play store settings, Play Protect Certification "device not certified"
However when i locked OEM, a day or so later, it showed "device certified"
(See example screenshot)
Good luck

Thanks. I did an OEM unlocked on my non-rooted phone and the device got formatted. Also, it now passes the safety net.
Sent from my SM-N960F using Tapatalk

I have just spent a lot of time with my SM-N960F Anroid 10 'Q' and I have some input because others have found the date shift trick doesn't always work for them and it didn't work for me.
If you get part way through a TWRP reflash and root you will have broken the KNOX security. You can NEVER get it back, which is o.k if you accept what you lose and the benefits of TWRP, Root access, flashing a custom ROM without bloatware and lost warranty. You will save money on phone pay to.
You can download an App to test if KNOX is present or broken. When you power the phone you will either see the OEM Unlocking option missing or it's grayed out with the message saying it's unlocked. If it's grayed out your Note 9 is still useless because ODIN won't accept anything but genuine OE files. FASTBOOT seems unavailable too.
O.K so you flash back the OE firmware and the phone boots o.k but there's no OEM Unlocking option and ODIN still won't accept a non OE flash image like TWRP. You try the clock back tricks and it still doesn't appear. The time initially comes from the firmware file if the phone has been reset to factory defaults after reflash. If you change the phone time and turn it off, it boots back to the firmware date not that date -7 days.
To avoid downloads & updates I always reflash without a phone network SIM (no downloads via network) and with no wifi credentials. This is the problem and could explain why some can't get this to work and others (who still have active wifi or data over network) can.
Having done all the tricks to set the date back leaving it in manual and stopping automatic updates, I re-entered my wifi credentials. Within seconds there was a beep, the date updated (even in manual mode!) and the OEM boot option appeared unlocked in Developer options. Note: You will never get this come up with 'OEM bootloader locked' once KNOX is broken. Went on to ODIN and it now accepts the non-OE TWRP image and anything else.
Conclusion: There has to be a data connection when the phone either gets updated date 7 days later than the date you set from a time server, or gets something back from another (Samsung?) server to restore the missing OEM Bootloader option?? You don't have to wait 7 days either. The problem for many going through reflash is if they never saw OEM unlocked in Developer options they would't know it should be there and will give up sticking the OE firmware back when the missing entry will eventually come back 7 days later. I think after this I'll go back to my Nokia 3310.
I'm still curious as to why I get comms with adb but not FASTBOOT. Which only leaves ODIN as the flash tool for this phone.