Related
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!!!
I am deployed to Afghanistan right now. I ordered a brand new XT862, rooted it, and installed safestrap 2.10 and cm-9-20120815-UNOFFICIAL-solana.zip. That worked beautifully.
Unfortunately I am having problems getting the radio to work. I would set an APN but then sometimes it would just not appear in the list. I would set it again and again, then sometimes all of the APNs would appear in my list until the radio failed. After flashing, formatting, and reflashing several times and having the default Verizion access points finally pop up out of nowhere in my APN list, I realized I never "unlocked" the phone. I am using a Roshan SIM.
The weird part is the radio would work for a period of time. First for several hours, then it would start failing more and more frequently.
I found the XT862-5.7.906-SAFE and flashed it, hoping it would ask me for an unlock code upon booting, but no dice. It just went into "Global" mode. I am testing right now to see if the radio stays stable.
So, I am wondering if these instructions:
Guide - Unlock XT862 for T-mobile/ATT
http://forum.xda-developers.com/showthread.php?t=1406812
will get me to the unlock code screen, and once unlocked, will my radio problem disappear when I reflash CM9? My Internet connection is painfully slow here in Afghanistan so I only want to download what I know will work.
I do have a second XT862 that I had unlocked, then rooted and flashed CM9 to and it is working very well on Roshan out here.
Thanks for your help!
While running the XT862-5.7.906-SAFE, the radio cut out and I got a BP paniced message. I couldn't remember all of it before it crashed completely, but it asked to connect the USB for debugging. While the screen was flickering, a window popped up asking if I wanted to switch to GSM.
The radio doesn't seem to be stable even with this firmware.
Any suggestions or help would be greatly appreciated.
The radio cut out again, so I tried switching it from global to CDMA and then to GSM to see if I could get it to reset.
It told me there were no GSM networks available, and then asked to switch to Global.
I hit ok, then it told me that the SIM was invalid...
I'm a noob to this phone stuff, but this just seems crazy.
It seems it's definately the phone, because I swapped the SIMs in my two phones and the problems persist with the new one. My functioning phone continues to work fine on the chip designated for the problem phone.
Did you flash the 883 radio?
MrObvious said:
Did you flash the 883 radio?
Click to expand...
Click to collapse
No, I haven't yet because I didn't know if that was going to solve my problem or not. Downloading is a challenge for me right now, too.
I don't know if not unlocking the phone before flashing CM9 caused the problem or if it's something else entirely that I am missing. I will want to have the phone usable in the states again. Will flashing the 883 radio give me any difficulties there?
I've went back though the steps that I did on my other, working phone and [edit] not unlocking is [/edit] pretty much the only difference.
I'm probably going to try to download the 883 radio stuff tonight when I get home from work and give it a try.
ThunderZuk said:
No, I haven't yet because I didn't know if that was going to solve my problem or not. Downloading is a challenge for me right now, too.
I don't know if not unlocking the phone before flashing CM9 caused the problem or if it's something else entirely that I am missing. I will want to have the phone usable in the states again. Will flashing the 883 radio give me any difficulties there?
I've went back though the steps that I did on my other, working phone and [edit] not unlocking is [/edit] pretty much the only difference.
I'm probably going to try to download the 883 radio stuff tonight when I get home from work and give it a try.
Click to expand...
Click to collapse
Unlocking the phone MUST be done on stock firmware. The XT883 radio is only required for using US GSM networks, such as AT&T and T-Mobile. The stock XT862 radio (after unlock) supports foreign SIM cards (and of course Verizon's Vodafone SIM).
As I recall, CM9/10 normally has issues with the GSM radio, if you need your phone, I suggest flashing a ROM based on a stock GB system, such as Maverick (4.0 version, 4.5 has a battery drain issue with an overclock script) which is based on 906. I tend to keep the phone on GSM/UMTS mode, as "Global" also turns on the CDMA radio, which utilizes more battery. The APN only matters for Data/MMS without the proper APN, you should still get talk/text/signal (no EDGE or 3G icons, which indicate data connection).
Skreelink said:
Unlocking the phone MUST be done on stock firmware. The XT883 radio is only required for using US GSM networks, such as AT&T and T-Mobile. The stock XT862 radio (after unlock) supports foreign SIM cards (and of course Verizon's Vodafone SIM).
As I recall, CM9/10 normally has issues with the GSM radio, if you need your phone, I suggest flashing a ROM based on a stock GB system, such as Maverick (4.0 version, 4.5 has a battery drain issue with an overclock script) which is based on 906. I tend to keep the phone on GSM/UMTS mode, as "Global" also turns on the CDMA radio, which utilizes more battery. The APN only matters for Data/MMS without the proper APN, you should still get talk/text/signal (no EDGE or 3G icons, which indicate data connection).
Click to expand...
Click to collapse
I didn't update the radio on my working phone to 883. It has been doing just fine on Roshan Afghanistan and AIS in Thailand. In the states I use Verizon, so I don't think GSM is a biggie.
So, I have to get back to stock and unlock, then go through the hack process again. I figured I probably did. So before I try to download this file, do you think the 1-click SBF here:
[xt862] .906 1-click-sbf.exe + tools [10-8-2012]
http://forum.xda-developers.com/showthread.php?t=1686911
will do the job? If not, do you know what will? I'm still running XT862-5.7.906-SAFE. I do have Blur_Version.5.6.890.XT862.Verizon.en.US.zip but I don't know how to install it. I'm still learning all of this stuff. Would RSDLite do it?
I wasn't very specific when I talked about the radio, sorry. More or less the voice connection would stop along with the data. It was just weird that sometimes the APNs would show up in the list and sometimes they wouldn't. When they did, it showed multiple from when I tried entering them several times. I don't know why it would write the changes but not read the list.
When about five Verizon APNs showed up and none of my Afghan APNs showed up, I realized I must have needed to unlock the phone. When I hacked it I just assumed it wouldn't have to be unlocked. I figured I WAS unlocking it. LOL!
Thanks everyone for your help.
ThunderZuk said:
I didn't update the radio on my working phone to 883. It has been doing just fine on Roshan Afghanistan and AIS in Thailand. In the states I use Verizon, so I don't think GSM is a biggie.
So, I have to get back to stock and unlock, then go through the hack process again. I figured I probably did. So before I try to download this file, do you think the 1-click SBF here:
[xt862] .906 1-click-sbf.exe + tools [10-8-2012]
http://forum.xda-developers.com/showthread.php?t=1686911
will do the job? If not, do you know what will? I'm still running XT862-5.7.906-SAFE. I do have Blur_Version.5.6.890.XT862.Verizon.en.US.zip but I don't know how to install it. I'm still learning all of this stuff. Would RSDLite do it?
I wasn't very specific when I talked about the radio, sorry. More or less the voice connection would stop along with the data. It was just weird that sometimes the APNs would show up in the list and sometimes they wouldn't. When they did, it showed multiple from when I tried entering them several times. I don't know why it would write the changes but not read the list.
When about five Verizon APNs showed up and none of my Afghan APNs showed up, I realized I must have needed to unlock the phone. When I hacked it I just assumed it wouldn't have to be unlocked. I figured I WAS unlocking it. LOL!
Thanks everyone for your help.
Click to expand...
Click to collapse
If you were on the 906 OTA, the one click EXE would work, no programs required. Connect phone in bootloader > run the exe > The phone will flash. In Global mode, when you check the APNs, only the Verizon ones will show, you MUST be in GSM/UMTS mode for your own APNs to show up. Also, if it's occasionally in and out, I wonder if the connection between the SIM and phone are bad, like a shake or movement will break the contact. (Which when a SIM is not present, only the Verizon APNs will show as well and would prompt for global mode)
Try taking the SIM out, cleaning the contacts, and placing it back in. If the sim seems loose, try slipping a single thin piece of paper behind it to make sure it's getting full contact. Otherwise, it might be a hardware fault.
Skreelink said:
If you were on the 906 OTA, the one click EXE would work, no programs required. Connect phone in bootloader > run the exe > The phone will flash. In Global mode, when you check the APNs, only the Verizon ones will show, you MUST be in GSM/UMTS mode for your own APNs to show up. Also, if it's occasionally in and out, I wonder if the connection between the SIM and phone are bad, like a shake or movement will break the contact. (Which when a SIM is not present, only the Verizon APNs will show as well and would prompt for global mode)
Try taking the SIM out, cleaning the contacts, and placing it back in. If the sim seems loose, try slipping a single thin piece of paper behind it to make sure it's getting full contact. Otherwise, it might be a hardware fault.
Click to expand...
Click to collapse
I'm currently running the SAFE version found here:
XT862 5.7.906 Update FXZ DST
http://forum.xda-developers.com/showthread.php?t=1554916
It doesn't say that it's an OTA. I'm still running safestrap 2.10 with it. That's why I was curious if that might work. I also have that full BLUR download already. I tried installing it using safestrap, but that didn't work. I'm assuming because it's not supposed to. If I can get that installed and it works I'd be happy. I have to remote into my server at home, download there, and then FTP over here at like 6k/sec. Am I correct in assuming I'd install that full BLUR image with RSDLite?
I haven't had any issues with the SIM from the bad phone in my good phone, and everything feels tight when I put the SIM in. I've tried cleaning the contacts a bit. I haven't tried putting something in there to hold it tighter yet, though.
ThunderZuk said:
I'm currently running the SAFE version found here:
XT862 5.7.906 Update FXZ DST
http://forum.xda-developers.com/showthread.php?t=1554916
It doesn't say that it's an OTA. I'm still running safestrap 2.10 with it. That's why I was curious if that might work. I also have that full BLUR download already. I tried installing it using safestrap, but that didn't work. I'm assuming because it's not supposed to. If I can get that installed and it works I'd be happy. I have to remote into my server at home, download there, and then FTP over here at like 6k/sec. Am I correct in assuming I'd install that full BLUR image with RSDLite?
I haven't had any issues with the SIM from the bad phone in my good phone, and everything feels tight when I put the SIM in. I've tried cleaning the contacts a bit. I haven't tried putting something in there to hold it tighter yet, though.
Click to expand...
Click to collapse
The Droid 3 does not require RSDLite, as it has fastboot. Which is able to flash certain parts alone instead of the whole system (or the whole thing together) it's easier than RSDLite and can make modifications without losing everything. That's how the XT883 radio is flashed without modifying the system.
The one click method would fully flash it as if you used an SBF in RSDLite. If you have safestrap enabled on safe; make a full backup with recovery, then disable safe-mode. You'll then reboot into your stock system, unlock there, then enable the safe boot again, restore your backup.
SIM unlocking is for good, no amount of flashing, updating, etc will revert it. If the phone DOES get service with the sim, then it's already unlocked.. if it's occasionally cutting out, that's a different issue.
ThunderZuk said:
I'm currently running the SAFE version found here:
XT862 5.7.906 Update FXZ DST
http://forum.xda-developers.com/showthread.php?t=1554916
It doesn't say that it's an OTA. I'm still running safestrap 2.10 with it. That's why I was curious if that might work. I also have that full BLUR download already. I tried installing it using safestrap, but that didn't work. I'm assuming because it's not supposed to. If I can get that installed and it works I'd be happy. I have to remote into my server at home, download there, and then FTP over here at like 6k/sec. Am I correct in assuming I'd install that full BLUR image with RSDLite?
I haven't had any issues with the SIM from the bad phone in my good phone, and everything feels tight when I put the SIM in. I've tried cleaning the contacts a bit. I haven't tried putting something in there to hold it tighter yet, though.
Click to expand...
Click to collapse
Holy shinto! I didn't know it saved that! I figured it was gone!
So I disabled safestrap, then it kept telling me com.android.phone had stopped. I'd force close and it would say it again. I went back into safestrap, did a factory wipe, rebooted and now it is connected in "Global" mode again on the stock 5.6.890.XT862.Verizon.en.US. It was looking good for a while, until the phone just rebooted itself.
I put my other SIM in the phone, booted back up and it worked for a while until the signal dropped and the phone gave me an invalid SIM error again. So, it's given me an invalid SIM on two different SIMs now in stock and flashed ROMs.
The SIM is in there tight. I couldn't get a piece of paper in there. I cleaned the contacts again, but they don't look dirty at all.
I put the original SIM back in there, it booted up, never got signal, and rebooted itself again. It doesn't have signal now, and I assume it's just about to reboot itself again.
You think I got a bum phone? I didn't test it at all before I started hacking it.
Also, if I do the *#*#4636#*#* while it has no signal it tells me my IMEI number is unknown, if that helps. If press the turn off radio button, it does nothing.
[edit]It also tells me pretty much everything (MEID, IMEI SV, SIM ID, ect...) is unknown if I go into About Phone>Status[/edit]
ThunderZuk said:
Also, if I do the *#*#4636#*#* while it has no signal it tells me my IMEI number is unknown, if that helps. If press the turn off radio button, it does nothing.
[edit]It also tells me pretty much everything (MEID, IMEI SV, SIM ID, ect...) is unknown if I go into About Phone>Status[/edit]
Click to expand...
Click to collapse
That happens if either; Airplane mode is on, or you have an incorrect build.prop, have you modified it in any way? Also have you tried making a backup and turning safe boot off?
Also; If the zips are still on your SDCard, try reflashing your rom to make sure you have the correct build.prop.
Skreelink said:
That happens if either; Airplane mode is on, or you have an incorrect build.prop, have you modified it in any way? Also have you tried making a backup and turning safe boot off?
Also; If the zips are still on your SDCard, try reflashing your rom to make sure you have the correct build.prop.
Click to expand...
Click to collapse
I have safestrap turned off and it appears I am running on stock? It says I am running 5.7.890 and not 5.7.906. There is a Superuser icon in the all apps, but I think that is from where I rooted it.
I rebooted and all the numbers came back... for now.
I don't have airplane mode on. I tried to turn it on after reading your post. It caused the phone to reboot. Once rebooted, it came back up in airplane mode. I turned it off and it is connected again, for now.
I haven't messed with the build.prop that I know of. I only rooted, installed CM9 several times, formatted everything several times in-between those installs, and most recently flashed that XT862-5.7.906-SAFE.zip.
And before I even finished this post it rebooted itself on me again...
ThunderZuk said:
I have safestrap turned off and it appears I am running on stock? It says I am running 5.7.890 and not 5.7.906. There is a Superuser icon in the all apps, but I think that is from where I rooted it.
I rebooted and all the numbers came back... for now.
I don't have airplane mode on. I tried to turn it on after reading your post. It caused the phone to reboot. Once rebooted, it came back up in airplane mode. I turned it off and it is connected again, for now.
I haven't messed with the build.prop that I know of. I only rooted, installed CM9 several times, formatted everything several times in-between those installs, and most recently flashed that XT862-5.7.906-SAFE.zip.
And before I even finished this post it rebooted itself on me again...
Click to expand...
Click to collapse
Alright, did you put the sim in and get the unlock screen to put in the unlock code? 890 is alright to be on, that's what my stock system is. I would suggest staying away from CM9/CM10 as they are unstable when using GSM networks. Either stay stock or flash a ROM based on Blur (I suggest MavRom 4.0).
Skreelink said:
Alright, did you put the sim in and get the unlock screen to put in the unlock code? 890 is alright to be on, that's what my stock system is. I would suggest staying away from CM9/CM10 as they are unstable when using GSM networks. Either stay stock or flash a ROM based on Blur (I suggest MavRom 4.0).
Click to expand...
Click to collapse
It never asked me for an unlock. It just immediately put the phone in world mode.
I literally did this with the phone.
1. open factory sealed box
2. root the phone
3. install safestrap
4. format all partitions
5. install CM9
6. install SIM
7. repeat 4 and 5 serveral times
8. install 5.7.906 hoping to get an unlock screen in order to possibly fix radio issue
9. start this thread.
Now, I did steps 4 and 5 over and over again over about 2 weeks off and on while I tried to figure out what was going wrong. Like I said, I am running CM9 very successfully here since August on a different XT862 that I did unlock before rooting. I installed a KANG build, not a KEXEC.
The amount of times your device seems to be rebooting makes me think there is something wrong with it.
Sent from my XT860 using xda premium
ThunderZuk said:
It never asked me for an unlock. It just immediately put the phone in world mode.
I literally did this with the phone.
1. open factory sealed box
2. root the phone
3. install safestrap
4. format all partitions
5. install CM9
6. install SIM
7. repeat 4 and 5 serveral times
8. install 5.7.906 hoping to get an unlock screen in order to possibly fix radio issue
9. start this thread.
Now, I did steps 4 and 5 over and over again over about 2 weeks off and on while I tried to figure out what was going wrong. Like I said, I am running CM9 very successfully here since August on a different XT862 that I did unlock before rooting. I installed a KANG build, not a KEXEC.
Click to expand...
Click to collapse
Hm... while in unsafe (stock) the unlock screen should have come up. It will not on other roms, as for global mode, that is a default setting, without unlock, will only work with the verizon vodafone sim that came with the phone. Reboots can be either hardware, rom, or app problem. You can try a factory wipe and see if that helps the reboots. Trying to find solutions without you having to download more.
Endoroid said:
The amount of times your device seems to be rebooting makes me think there is something wrong with it.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
I was kind of worried that was the case. I just ordered a refurb unit just in case.
this thread is just for lollipop 5.x m7wls (sprint) based on sense roms
no need to S-OFF
if you are on kitkat or less here or here if you are on the stock ODEX rom
1 - you need just to unlock bootloader from htcdev.com
2 - TWRP or any other here is the TWRP for m7wls(sprint)
3 - flash SuperSU
4 - its time to flash HtcOMADM_SPCS
5 - install sim unlock helper.apk
6 - Insert your SIM card, you may see this massage No Network Found
Code:
Select "YES" to switch to global mode
Select "NO" to stay in the current mode
but do not worry since your phone dose not say invalid sim card . so now go to setting , mobile data . and chose GSM/UMTS only. tell now you wont see any signal , just scroll down to Available GSM netowrks ,then Search networks you will see a list of networks and only one that is available, chose it .
now if you want to stop the annoying vDM crash massage flash the stock-HtcOMADM_SPCS .
Its better to relock your bootloader and flash the RUU rom so every thing works well and you wont see the No Network massage again .
That's it ^_*
it really works but, it didn´t solve my problem i guess my problem is not sim unlock i can not have signal for gsm it stuck in CDMA but in *#*#4636#*#* it shows up like radio turned off i want to turning on but i can not,:crying:
anyway thanks:good::good:
I've tried your guide and elvisypi's guide, but neither work. I'm using a rooted M7, lollipop, stock ROM.
When using the SIM Unlock Helper app, I get "OS Check Fail! You aren't running HTC Sense!", but if I hit the back button I end up at a screen that states "Device verified, root available, sense rom (yes)". Hitting Start does open up the menu, but never before a vDM client crash. After hitting Sim Unlock and it hanging for a few seconds, the log is empty after hitting back to return to the unlock helper. The screen says "Log empty, did you run the program first?"
It seems to me that "vDM" is what is supposed to be doing the work, and it's crashing so it can't...
when OS Check Fail! appears to you press Display SIM Unlock Log then go back and press start and scroll down to sim lock
if that menu did not appear to you try flashing this instead
http://www.mediafire.com/download/9fql3kczdn7mb73/NEW+HtcOMADM_SPCS_2.zip
AnthonyCool said:
it really works but, it didn´t solve my problem i guess my problem is not sim unlock i can not have signal for gsm it stuck in CDMA but in *#*#4636#*#* it shows up like radio turned off i want to turning on but i can not,:crying:
anyway thanks:good::good:
Click to expand...
Click to collapse
check it from the settings / Mobile data / Network mode
i think
flyboy21141 said:
I've tried your guide and elvisypi's guide, but neither work. I'm using a rooted M7, lollipop, stock ROM.
When using the SIM Unlock Helper app, I get "OS Check Fail! You aren't running HTC Sense!", but if I hit the back button I end up at a screen that states "Device verified, root available, sense rom (yes)". Hitting Start does open up the menu, but never before a vDM client crash. After hitting Sim Unlock and it hanging for a few seconds, the log is empty after hitting back to return to the unlock helper. The screen says "Log empty, did you run the program first?"
It seems to me that "vDM" is what is supposed to be doing the work, and it's crashing so it can't...
Click to expand...
Click to collapse
when OS Check Fail! appears to you press Display SIM Unlock Log then go back and press start and scroll down to sim lock
if that menu did not appear to you try flashing this instead
http://www.mediafire.com/download/9fql3kczdn7mb73/NEW+HtcOMADM_SPCS_2.zip
Not unlocking
Hi I am have bootloader unlocked, intalled TWRP, and rooted. Tried with Stock Sprint Lollipop ROM and menu would not pop up. Flashed to Viperone 8.0 and I am able to bring up the menu. Once Sim Lock unhighlights I hit the back button and get the SIM unlocked successful message. The reboot in that screen does not work for me so have to hold power button down and reboot. I have changed settings to GSM and WCMDA preferred. Next pop in an ATT SIM and a Cricket but still get invalid SIM. Any ideas? Also, I am S-On as I have been unable to off with HBoot 1.61
Hi, I bought a Sprint HTC One M7 (running 5.0.2) from someone figuring that I'd be able to unlock for use on Verizon (because every phone can be unlocked...... right? ). I first unlocked the bootloader with HTCDev, ok good. Then I ordered a SIM unlock code off the interwebs thinking that I could just go get a Verizon SIM from them and then enter the code when prompted. Took the phone to Verizon and they couldn't help, said that IMEI was not valid and they couldn't give me a new SIM because the current phone I have (Incredible 2) isn't eligible for a SIM only upgrade, then they said I should just purchase an upgrade with the EDGE plan (yeah right). I then used the SIM card of a friend who has an M7 on Verizon hoping that I'd be prompted for the SIM unlock code then, but I only got "invalid SIM......"
So, I stumbled upon this thread and followed the procedure to flash TWRP, then SuperSU, confirmed that I'm rooted, and then flashed HtcOMADM_SPCS_2.zip, and ran SIM unlock helper. I got the same error as the other guy "OS Check Fail" and vDM client crashed, but then I press back and go through the SIM lock part and reboot. So now I can put my friend's Verizon SIM in and I get no SIM error, but I am still not prompted to input the unlock code for my IMEI. Any Ideas, or is it not even possible to use a Sprint M7 on Verizon?
EDIT: I am now S-off with sunshine (hboot 1.61)
EDIT 2: Ok, now I'm getting to a point where I put my friend's SIM in and it prompts "preparing SIM", "SIM card inserted, tap to complete setup". Once I tap the notification, I get taken to a screen that says select your carrier. It takes a little while to load the carriers but Verizon appears, but after I select verizon, the page disappears and nothing further happens. It then repeats the loop from "preparing SIM".
EDIT 3: From TWRP I wiped all data including the OS. Then I got stuck at the splash screen, reflashed [STOCK ROM] [5.0.2] [SENSE 6] Sprint 6.16.651.2 rooted from phonegeekjr (PhoeniROM ?)
tlwash123 said:
Hi, I bought a Sprint HTC One M7 (running 5.0.2) from someone figuring that I'd be able to unlock for use on Verizon (because every phone can be unlocked...... right? ). I first unlocked the bootloader with HTCDev, ok good. Then I ordered a SIM unlock code off the interwebs thinking that I could just go get a Verizon SIM from them and then enter the code when prompted. Took the phone to Verizon and they couldn't help, said that IMEI was not valid and they couldn't give me a new SIM because the current phone I have (Incredible 2) isn't eligible for a SIM only upgrade, then they said I should just purchase an upgrade with the EDGE plan (yeah right). I then used the SIM card of a friend who has an M7 on Verizon hoping that I'd be prompted for the SIM unlock code then, but I only got "invalid SIM......"
So, I stumbled upon this thread and followed the procedure to flash TWRP, then SuperSU, confirmed that I'm rooted, and then flashed HtcOMADM_SPCS_2.zip, and ran SIM unlock helper. I got the same error as the other guy "OS Check Fail" and vDM client crashed, but then I press back and go through the SIM lock part and reboot. So now I can put my friend's Verizon SIM in and I get no SIM error, but I am still not prompted to input the unlock code for my IMEI. Any Ideas, or is it not even possible to use a Sprint M7 on Verizon?
EDIT: I am now S-off with sunshine (hboot 1.61)
EDIT 2: Ok, now I'm getting to a point where I put my friend's SIM in and it prompts "preparing SIM", "SIM card inserted, tap to complete setup". Once I tap the notification, I get taken to a screen that says select your carrier. It takes a little while to load the carriers but Verizon appears, but after I select verizon, the page disappears and nothing further happens. It then repeats the loop from "preparing SIM".
EDIT 3: From TWRP I wiped all data including the OS. Then I got stuck at the splash screen, reflashed [STOCK ROM] [5.0.2] [SENSE 6] Sprint 6.16.651.2 rooted from phonegeekjr (PhoeniROM ?)
Click to expand...
Click to collapse
I think You need to change the CDMA via DFS so it can be recognized by SIM card
Why
Sprint always use the CDMA as PRL that you can write it via DFS while Verizon use this type of network as a SIM card so that after using sim unlock helper your phone dose not say "invalid SIM" but it didnt show the network signal
As far as I know, the Sprint and Verizon M7s have custom radios operating at their carrier frequencies. Sprint's frequency band is not the same as Verizon's, and even after unlocking, the radio can only scan within its band. Your radio simply can't see Verizon's tower. It seems like your process completely worked, though.
I haven't gotten the chance to try again, but I am planning to eventually.
Also, it is possible to S-OFF through any other method than Sunshine? It'd be nice not to have to pay for that... Is S-OFF absolutely required to SIM unlock/ flash custom roms/ change files at the root level?
This does NOT work...
I think it is pretty obvious that THIS METHOD DOES NOT WORK...
I basically ran the latest RUU - Sprint Stock ROM which put my phone to Lollipop 5.0.2 - Sense 6.0, HBOOT 1.61, S-ON
I unlocked bootloader with HTC DEV, installed the latest TWRP, and rooted the phone, so it is all LATEST and GREATEST as of this post date...
I ran BOTH of the HtcOMADM_SPCS_2 files - both OLD and NEW - and neither one works. NEW is actually worse because the vDM client crashes each time you even try to launch the SIM UNLOCK HELPER app.
With the OLD file you can get to the menu and you can click on SIM LOCK, but nothing gets written to the log before or after reboot, plus when you go to *#*#4636#*#* you can select the connection type, since it is set to CDMA but every time I change it to - GSM only - it will reset to CDMA only when I go back in. So the change refuses to save and I keep getting that prompt saying:
No Network Found
Select "YES" to switch to global mode
Select "NO" to stay in the current mode
So it seems to want to force you back to CDMA mode.
If we are supposed to be running a CUSTOM ROM then please say so, but I am testing with the STOCK ROM and it seems others are NOT having any luck.
So if someone has it working then just let us know WHICH ROM you are using and which files you are using, because it sounds like we are being asked to QA the hack...
Moving on to another solution now...
:crying:
P.S.
Why is someone posting about a VERIZON phone in the Sprint section, kick them out because they add to the confusion...
Wow! OP was edited with a fix 4 hours after I'd figured it out myself. Just made an account to clarify that you need to downgrade the radio if it's too new. I had a lot of trouble trying to unlock it before figuring that out (and I went through an entire series of downgrading and flashing multiple ROMs until I found it out). Here's a guide I made that worked for me.
Have an unlocked bootloader first with HTCDev like said in OP. There's no need to have S-OFF or downgrade anything except radio.
1. Install TWRP.
2. Flash a lollipop ROM (I used Viper 8.0.0) using TWRP. (You can probably skip steps 2 and 3 if you're already on lollipop.)
3. Once booted, go through first time set up.
4. Restart into TWRP and install SuperSU.
5. Reboot and flash the radio (1.00.20.0315_1.29.651.7.zip from elvisypi's thread) and then flash HtcOMADM_SPCS.zip (I used the 4.3 version from chas123) using TWRP.
7. Reboot into System and install the com.viper.simunlockhelperfree.apk (Below; couldn't find where I got it from) then go to display log, press back, press start, then scroll down and press simlock. You could probably also do this using the Terminal method.
8. Wait a few seconds until it unfreezes and reboot.
9. Once rebooted, plug in your sim and go to the phone dial and put in *#*#4636#*#*. Go to Phone Information and set the network to WDCMA preferred. (It might spam you with "No Network Found," so just check do not show again and press No to switching to global mode.)
10. Exit out and open Settings then go to Mobile data and make sure the Network mode is set to GSM/UMTS Only. Scroll down and go to Access point names. (Found steps 10-13 from savage25rcracer while searching through the forums.)
11. In the APNs, choose your carrier and press back.
12. Go to Available GSM networks and press Search Networks.
13. Wait until it finishes and select your carrier.
14. Now you should have service and you are now unlocked on lollipop.
One problem I have is that when data is turned off, it never connects back to data when turned back on and I have to repeat steps 9-13. Any help with that would be appreciated. I did this method with HBoot 1.61 and S-ON and I am using a T-Mobile Sim. Hopefully this works for you guys!
EDIT:
Turns out that switching it to GSM Auto (PRL) made it automatically reconnect for turning data on and off, but data doesn't work after reboot until I repeat step 12.
Check my older post I have a fix for the in an out signal and it reconnects automatically... Thank me later. Spread the word... It's well worth it. I use it.
Sent from my HTC One using XDA Free mobile app
i tried with STOCK & Viper ... not working
with Stock SIMunlockhelper didnt give me MENU after i hit START
with viper it takes about 2 mins freezing when i hit SIMLOCK... then still nohting after reboot Network operator DIMED & alot of times it give me ERROR (vDM Client isn't responding)
NOTE : on lock screen it says (Invalid Card)
It doesn't say invalid sim,i selected ATT from the list of the carriers,i selected GSM/UMTS under mobile settings but my Network Operators Menu is grey and i can't select ATT there.Any ideas.
REVISTED - Did this work?!
Fayr said:
Wow! OP was edited with a fix 4 hours after I'd figured it out myself. Just made an account to clarify that you need to downgrade the radio if it's too new. I had a lot of trouble trying to unlock it before figuring that out (and I went through an entire series of downgrading and flashing multiple ROMs until I found it out). Here's a guide I made that worked for me.
Have an unlocked bootloader first with HTCDev like said in OP. There's no need to have S-OFF or downgrade anything except radio.
1. Install TWRP.
2. Flash a lollipop ROM (I used Viper 8.0.0) using TWRP. (You can probably skip steps 2 and 3 if you're already on lollipop.)
3. Once booted, go through first time set up.
4. Restart into TWRP and install SuperSU.
5. Reboot and flash the radio (1.00.20.0315_1.29.651.7.zip from elvisypi's thread) and then flash HtcOMADM_SPCS.zip (I used the 4.3 version from chas123) using TWRP.
7. Reboot into System and install the com.viper.simunlockhelperfree.apk (Below; couldn't find where I got it from) then go to display log, press back, press start, then scroll down and press simlock. You could probably also do this using the Terminal method.
8. Wait a few seconds until it unfreezes and reboot.
9. Once rebooted, plug in your sim and go to the phone dial and put in *#*#4636#*#*. Go to Phone Information and set the network to WDCMA preferred. (It might spam you with "No Network Found," so just check do not show again and press No to switching to global mode.)
10. Exit out and open Settings then go to Mobile data and make sure the Network mode is set to GSM/UMTS Only. Scroll down and go to Access point names. (Found steps 10-13 from savage25rcracer while searching through the forums.)
11. In the APNs, choose your carrier and press back.
12. Go to Available GSM networks and press Search Networks.
13. Wait until it finishes and select your carrier.
14. Now you should have service and you are now unlocked on lollipop.
Click to expand...
Click to collapse
Well, it seems this is the ONLY SOLUTION that worked for me, because I tried the Bad Boyz custom ROM that some others have suggested but it does NOT seem to work and there are "bugs" like the status\notification bar disappearing when you start to mess with the ROM. I flashed the Viper 8.0.0 ROM with TWRP and everything loaded properly except for one little "bug", which is this constant non-stop blinking NFC icon in the status bar so I might have to find another ROM. I wish I did not upgrade, so if you have ANY HBOOT under 1.61 - DO NOT UPGRADE WITH OFFICIAL ROM - because once you have 1.61 then you cannot S-OFF although you can downgrade the radio with S-ON and it is just a matter of unlocking the bootloader.
2 Notes:
1. Make sure you install SuperSU and do not rely on the Viper version, so let it uninstall any other SuperSU after installing from the Play Store. I believe the SuperSU installation will fail for you if you install through TWRP, but ViperROM should be rooted and instead install SuperSU from the Play Store if TWRP installation fails.
2. When you run "SIM UNLOCK helper" it WILL FAIL the first time, because you need to have SuperSU give it permission so make sure you go to the LOG in the options. Afterwards, make sure you close everything and remove from latest apps list. Then run again, when it fails then open LOG then hit BACK and now it will show you that you PASSED THE TEST. Then START then scroll down to SIM LOCK and wait like a minute or more because it took a LONG TIME for mine to un-freeze but then I hit REBOOT once it came back which is right there in the same list. If you doubt it, then reboot and do again but I was able to get it to work and then when I changed options in 4636 it would look for my SIM and did not give me any errors.
Anyway, I was able to follow all the steps here and the key seems to be downgrading the radio, because nothing seemed to work until I downgraded the radio version and then I tested it with both an AT&T and T-Mobile chip that I have lying around. The T-Mobile chips seem to work with no problems as others have noted, so you are able to make changes, register on the network, and set it up but I had problems with AT&T although I got farther than with any other modification. The AT&T chip will let you select the AT&T network, but you will not be able to scan for networks and you get NO BARS although it seems to be connecting or doing something although I suspect AT&T or something in the software is blocking you from connecting 100%.
So I cannot say 100% this SIM UNLOCK worked, but at least I was able to get to options that I could not get to before and I tried BOTH chips and only the T-Mobile chip seemed to work without any problems, so I suspect what others have reported is true and the Sprint HTC ONE M7 seems to be giving you problems with DOMESTIC US Carriers. I will be able to make a DEFINITIVE test in 2 months, because I am going to Peru and I might as well take this phone with me so I will test the Sprint HTC One M7 with both Claro and Telefonica SIMs down there. I will even try to update to the LATEST Sprint Official ROM to see if the unlock stays and if I am able to get GSM to work with overseas SIMs then the SIM UNLOCK worked, but you might as well not bother using it in the United States, so hopefully this will help others once I post an update after July and this will end up my "overseas" battle phone unless I pawn it off over there.
See you then...
:good:
DonChino said:
I flashed the Viper 8.0.0 ROM with TWRP and everything loaded properly except for one little "bug", which is this constant non-stop blinking NFC icon in the status bar so I might have to find another ROM.
Click to expand...
Click to collapse
Not to derail the thread, but I think there is a fix in HUB - Addons.
http://forum.xda-developers.com/showthread.php?p=59839813&highlight=nfc#post59839813
DonChino said:
Well, it seems this is the ONLY SOLUTION that worked for me
Anyway, I was able to follow all the steps here and the key seems to be downgrading the radio, because nothing seemed to work until I downgraded the radio version and then I tested it with both an AT&T and T-Mobile chip that I have lying around. The T-Mobile chips seem to work with no problems as others have noted, so you are able to make changes, register on the network, and set it up but I had problems with AT&T although I got farther than with any other modification. The AT&T chip will let you select the AT&T network, but you will not be able to scan for networks and you get NO BARS although it seems to be connecting or doing something although I suspect AT&T or something in the software is blocking you from connecting 100%.
So I cannot say 100% this SIM UNLOCK worked, but at least I was able to get to options that I could not get to before and I tried BOTH chips and only the T-Mobile chip seemed to work without any problems, so I suspect what others have reported is true and the Sprint HTC ONE M7 seems to be giving you problems with DOMESTIC US Carriers. I will be able to make a DEFINITIVE test in 2 months, because I am going to Peru and I might as well take this phone with me so I will test the Sprint HTC One M7 with both Claro and Telefonica SIMs down there. I will even try to update to the LATEST Sprint Official ROM to see if the unlock stays and if I am able to get GSM to work with overseas SIMs then the SIM UNLOCK worked, but you might as well not bother using it in the United States, so hopefully this will help others once I post an update after July and this will end up my "overseas" battle phone unless I pawn it off over there.
See you then...
:good:
Click to expand...
Click to collapse
Yep.that's exactly what i've got-i did radio downgrade and was able to run SIM unlock app,but i can't get ANY signal from ATT and my GSM network selection menu is greydout. Any ideas how i can make it work?Suggestion from OP?
i tried both methods ... same results (Not Working)
WLS Hboot 1.61.0000 with stock Lollipop all steps DONE but it says on lock screen INVALID SIM & SIM UNLOCK HELPER didnt show menu after hit start
on viper 8.0 also it says INVALID SIM on lock screen .. when i hit start its show MENU then i hit SIM LOCK it freez about 2 mins then it give me error (VDM isnt responding).. so i tried to flash HtcOMADM_SPCS.zip again then tried to flash Stock-HtcOMADM_SPCS.zip ... the same
what should i do ????
justrelax said:
i tried both methods ... same results (Not Working)
WLS Hboot 1.61.0000 with stock Lollipop all steps DONE but it says on lock screen INVALID SIM & SIM UNLOCK HELPER didnt show menu after hit start
on viper 8.0 also it says INVALID SIM on lock screen .. when i hit start its show MENU then i hit SIM LOCK it freez about 2 mins then it give me error (VDM isnt responding).. so i tried to flash HtcOMADM_SPCS.zip again then tried to flash Stock-HtcOMADM_SPCS.zip ... the same
what should i do ????
Click to expand...
Click to collapse
Downgrade the radio,flash HtcOMADM_SPCS.zip,try unlock app.
Hi. I am a complete noob when it comes to rooting Android.
**************************UPDATE************************************************
THIS ISSUE HAS BEEN SOLVED. PLEASE SCROLL TO POST #89 ON PAGE 9 TO SEE THE SOLUTION.
https://forum.xda-developers.com/showpost.php?p=77950935&postcount=89
***************************************************************************************************
I bought an *unlocked* Samsung Note 9 N960F/DS (Exynos 9810) international phone from a seller on ebay brand new and sealed. Received the phone yesterday (10/19/2018) and popped my working existing sim card from my iphone 6 with T-mobile into the new phone and it *worked*.........except no wifi calling.
Since my house has terrible reception I really do need wifi calling in order to receive calls (I use Skype for outbound). I decided to root and install Detonator (tekhd) even though I've never done this before. Somewhere along the line I messed up and installed the latest LUX ROM because I misred Tekhd's guide on Detonator (my fault).
Here's where I stand now: I found a stock ROM for this model (N960F/DS) and reinstalled it using Odin3 v3.13.1.
After a successful flash when I insert my working T-mobile sim I get "SIM network PIN blocked. Enter SIM network PUK."
Here the Service Provider SW shows XEU/XEU,XEU/MYM
I get the *same* message when I insert a spare T-mobile sim I happened to have that was confirmed as available with T-mobile customer service. If I take the working sim out and put it back into the other phone it works without a problem. I think that rules out the sim cards having issues.
Earlier when I had the phone rooted and Detonator installed (and working), I got a different message when I inserted the SIM:
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Device Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".
Here the Service Provider SW showed TMB/TMB/MYM.
I tried looking for a T-mobile Unlock App apk to download but could not find a recent one. I would get a "Device not supported" error. It seems T-mobile has taken it off the Playstore.
Now, I can't install a stock USA ROM from T-mobile because those ROMS are only for the Snapdragon versions and I have the Exynos chip. I was given two unlock codes over the phone with T-mobile customer service to try and unlock the Pin lock but they both did not work.
Do you think an unlock service will be able to provide me with a valid "Sim Network PUK" code? I'm happy to pay for the service if I can just get the damn phone working. I've spent almost $770 on this phone and in hindsight should just have gotten the T-mobile branded phone for $100 more. I'm really at a loss as to what I can do to rectify this situation.
Also in hindsight I should have done more research before purchasing the phone and also should have backed up my partition in TWRP........You live and you learn.
The irony here is that I had an unlocked phone.....and now it has somehow gotten locked.........by the carrier whose SIM card is working perfectly fine......in a different phone. The device was paid in full btw.
Any help is greatly appreciated. Thank you in advance.
orsonwells456 said:
Hi. I am a complete noob when it comes to rooting Android.
I bought an *unlocked* Samsung Note 9 N960F/DS (Exynos 9810) international phone from a seller on ebay brand new and sealed. Received the phone yesterday (10/19/2018) and popped my working existing sim card from my iphone 6 with T-mobile into the new phone and it *worked*.........except no wifi calling.
Since my house has terrible reception I really do need wifi calling in order to receive calls (I use Skype for outbound). I decided to root and install Detonator (tekhd) even though I've never done this before. Somewhere along the line I messed up and installed the latest LUX ROM because I misred Tekhd's guide on Detonator (my fault).
Here's where I stand now: I found a stock ROM for this model (N960F/DS) and reinstalled it using Odin3 v3.13.1.
After a successful flash when I insert my working T-mobile sim I get "SIM network PIN blocked. Enter SIM network PUK."
Here the Service Provider SW shows XEU/XEU,XEU/MYM
I get the *same* message when I insert a spare T-mobile sim I happened to have that was confirmed as available with T-mobile customer service. If I take the working sim out and put it back into the other phone it works without a problem. I think that rules out the sim cards having issues.
Earlier when I had the phone rooted and Detonator installed (and working), I got a different message when I inserted the SIM:
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Device Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".
Here the Service Provider SW showed TMB/TMB/MYM.
I tried looking for a T-mobile Unlock App apk to download but could not find a recent one. I would get a "Device not supported" error. It seems T-mobile has taken it off the Playstore.
Now, I can't install a stock USA ROM from T-mobile because those ROMS are only for the Snapdragon versions and I have the Exynos chip. I was given two unlock codes over the phone with T-mobile customer service to try and unlock the Pin lock but they both did not work.
Do you think an unlock service will be able to provide me with a valid "Sim Network PUK" code? I'm happy to pay for the service if I can just get the damn phone working. I've spent almost $770 on this phone and in hindsight should just have gotten the T-mobile branded phone for $100 more. I'm really at a loss as to what I can do to rectify this situation.
Also in hindsight I should have done more research before purchasing the phone and also should have backed up my partition in TWRP........You live and you learn.
The irony here is that I had an unlocked phone.....and now it has somehow gotten locked.........by the carrier whose SIM card is working perfectly fine......in a different phone. The device was paid in full btw.
Any help is greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
this is a first. I always though once the region lock was lifted it couldn't be relocked( to me it seems to be a region lock issue, which if it is you need to make a 5 min call on region soil... good luck)
anyways check on your box there is a sticker with model and serial . find what carrier or region its from and grab that firmware and flash it. might want to factory wipe everything (including cache) in the recovery before booting it up indownlaod mode to do Odin flash.
also remove sim before wiping/ flashing, let it boot and do the initial setup then insert sim.
bober10113 said:
this is a first. I always though once the region lock was lifted it couldn't be relocked( to me it seems to be a region lock issue, which if it is you need to make a 5 min call on region soil... good luck)
anyways check on your box there is a sticker with model and serial . find what carrier or region its from and grab that firmware and flash it. might want to factory wipe everything (including cache) in the recovery before booting it up indownlaod mode to do Odin flash.
also remove sim before wiping/ flashing, let it boot and do the initial setup then insert sim.
Click to expand...
Click to collapse
I did wipe and reinstall the stock rom with the sim removed. The strange thing is..........I get the same message if I insert an old, blank, unused t-mobile sim into the device. Plus the working sim works fine in my old phone. So how could it be that the sim is locked?
There is nothing on the box that says anything about a carrier. This was advertised and sold as a factory unlocked phone which by all indications it does seem to be. The only thing on the box that says anything about country is that it was manufactured in vietnam.
orsonwells456 said:
I did wipe and reinstall the stock rom with the sim removed. The strange thing is..........I get the same message if I insert an old, blank, unused t-mobile sim into the device. Plus the working sim works fine in my old phone. So how could it be that the sim is locked?
There is nothing on the box that says anything about a carrier. This was advertised and sold as a factory unlocked phone which by all indications it does seem to be. The only thing on the box that says anything about country is that it was manufactured in vietnam.
Click to expand...
Click to collapse
no sticker with device model or anything? not even in the back of the phone when it was new? a white sticker
bober10113 said:
no sticker with device model or anything? not even in the back of the phone when it was new? a white sticker
Click to expand...
Click to collapse
Yes there are stickers. But it is not associated with a carrier, specific region, or country. I just see IMEI info on the sticker on the back of the phone and S/N.
orsonwells456 said:
Yes there are stickers. But it is not associated with a carrier, specific region, or country. I just see IMEI info on the sticker on the back of the phone and S/N.
Click to expand...
Click to collapse
nothing like
SM-N960FOYAU1MYM or something?
bober10113 said:
nothing like
SM-N960FOYAMYM or something?
Click to expand...
Click to collapse
Ah ok. SM-N960FZBDMYM
bober10113 said:
nothing like
SM-N960FOYAU1MYM or something?
Click to expand...
Click to collapse
btw I think detonator zip backup efs partition. did your issues arise before it after flashing it? if after try to find the backup and refresh it
bober10113 said:
btw I think detonator zip backup efs partition. did your issues arise before it after flashing it? if after try to find the backup and refresh it
Click to expand...
Click to collapse
I was a dumbass and did not backup. I had zero issues other than no wifi-calling before trying to root and flash detonator...... Thank you for your help.
I went to a site with all "official" downloads and I don't see anything for ZBDMYM........
orsonwells456 said:
I was a dumbass and did not backup. I had zero issues other than no wifi-calling before trying to root and flash detonator...... Thank you for your help.
Click to expand...
Click to collapse
https://samsung-firmware.org/model/SM-N960F/region/MYM/
did you flash one of these?
these should be the original firmware U1 and the lates U2 which if you flash wint be able to downgrade bootloader but shouldn't be causing rhe sim lock issue.
flash U1 first and see if it fixes your issue. then try the October U2 just for fun
you can also download it using samfirm tool
enter 960F and MYM in settings it should also be a faster download then the web links
bober10113 said:
https://samsung-firmware.org/model/SM-N960F/region/MYM/
did you flash one of these?
these should be the original firmware U1 and the lates U2 which if you flash wint be able to downgrade bootloader but shouldn't be causing rhe sim lock issue.
flash U1 first and see if it fixes your issue. then try the October U2 just for fun
Click to expand...
Click to collapse
My baseband version currently shows N960FXXU2ARH7 and Service Provider SW Ver. shows XEU/XEU, XEU/MYM. I will try loading U1 first and see what happens.
orsonwells456 said:
My baseband version currently shows N960FXXU2ARH7 and Service Provider SW Ver. shows XEU/XEU, XEU/MYM. I will try loading U1 first and see what happens.
Click to expand...
Click to collapse
ok so it's too late for U1 . ure phone is already on U2 latest bootloader. so flash the October build
but be sure to wipe all with no sim before flashing
and in Odin fill in all slots and for csc use CSC but not HOME csc file.
good luck
bober10113 said:
ok so it's too late for U1 . ure phone is already on U2 latest bootloader. so flash the October build
but be sure to wipe all with no sim before flashing
Click to expand...
Click to collapse
Should I take out sim, use TWRP to wipe, then go into download mode, Odin3=> flash rom? Thanks.
orsonwells456 said:
Should I take out sim, use TWRP to wipe, then go into download mode, Odin3=> flash rom? Thanks.
Click to expand...
Click to collapse
yeah might as well use tarp. and erase all. but before, did you sift through internal s or ext s for an efs backup that detonator might have made automatically?
check for a folder called .backup and or for a file like:
efs_backup.img.gz
efs_backup.img
or anything similar
bober10113 said:
yeah might as well use tarp. and erase all. but before, did you sift through internal s or ext s for an efs backup that detonator might have made automatically?
Click to expand...
Click to collapse
No, but I did download Dr. Ketan's tool to make an efs backup. But that was way later in the process....so it wasn't the original efs directory......It was after I flashed my current "stock" rom. I'm going to try and find another site to download since that one will take 2 days on slow speed......
Btw what does the ZBD mean? MYM I figured is Myanmar......
orsonwells456 said:
No, but I did download Dr. Ketan's tool to make an efs backup. But that was way later in the process....so it wasn't the original efs directory......It was after I flashed my current "stock" rom. I'm going to try and find another site to download since that one will take 2 days on slow speed......
Btw what does the ZBD mean? MYM I figured is Myanmar......
Click to expand...
Click to collapse
probably a date code of some sort. Samsung mashes a bunch if letters to come up with country,date code. just Google it.
but try samfirm 3.6 tool to dl
https://1drv.ms/f/s!AhXVLDDj8g3AgdJZClzJmsN17YL2CQ
I am using Samfirm and found this;
Model: N960F
Region: MYM
File: N960FXXU2ARJ1/N960FOXM2ARJ1/N960FXXU2ARJ1/N960FXXU2ARJ1
Verions: N960F_1_20181001162540_w0h1lv73k8_fac.zip.enc4
If Install this ROM, does this mean my phone will be region locked to MYM again? I'm definitely confused on this......
orsonwells456 said:
I am using Samfirm and found this;
Model: N960F
Region: MYM
File: N960FXXU2ARJ1/N960FOXM2ARJ1/N960FXXU2ARJ1/N960FXXU2ARJ1
Verions: N960F_1_20181001162540_w0h1lv73k8_fac.zip.enc4
Click to expand...
Click to collapse
yeah looks good. its October 1st build
---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------
orsonwells456 said:
If Install this ROM, does this mean my phone will be region locked to MYM again? I'm definitely confused on this......
Click to expand...
Click to collapse
well ure screwed either way. the goal is to restore everything back to stock and see if you can get a line working
btw was there a seal on the box that you had to break in order to open the box when you first got it?
Hey guys,
I searched on google but was not able to find a solution for my issue due to software updates..
For like a week i do have the notification for the software-update to be ready to install (October security patch) and finally yesterday i had time to let the installation do its thing.
All of sudden after the update i can enter my SIM pin and that's it. No network, no cellular NOTHING.
What i did:
- Factory reset
- Data wipe via recovery
- Flashed current DBT firmware manually via ODIN
- Flashed previous DBT firmware
I am out of ideas.. Seems like a hardware problem, right? The lower part inside of the phone - is that the part for network? Should i try to replace it?
I replaced my screen 2 months ago, therefore i am out of warranty i guess, right?
Thanks in advance for any advise or help.
BR
VuBoo said:
Hey guys,
I searched on google but was not able to find a solution for my issue due to software updates..
For like a week i do have the notification for the software-update to be ready to install (October security patch) and finally yesterday i had time to let the installation do its thing.
All of sudden after the update i can enter my SIM pin and that's it. No network, no cellular NOTHING.
What i did:
- Factory reset
- Data wipe via recovery
- Flashed current DBT firmware manually via ODIN
- Flashed previous DBT firmware
I am out of ideas.. Seems like a hardware problem, right? The lower part inside of the phone - is that the part for network? Should i try to replace it?
I replaced my screen 2 months ago, therefore i am out of warranty i guess, right?
Thanks in advance for any advise or help.
BR
Click to expand...
Click to collapse
To decide if you still have warranty or not, you need to visit the sales/service centre. To ascertain your issue, you need to give a little more background on your last activities. Did you change your CSC anytime? When the problem first occurred, were you totally stock? Is your device carrier locked? Lots of questions..
Look if able to see IMEI in device settings - about phone
If IMEI is there and still you are unable to connetc to network, you should ask your operator if your IMEI got banned.
amirage said:
To decide if you still have warranty or not, you need to visit the sales/service centre. To ascertain your issue, you need to give a little more background on your last activities. Did you change your CSC anytime? When the problem first occurred, were you totally stock? Is your device carrier locked? Lots of questions..
Click to expand...
Click to collapse
Hey, thanks for your reponse.
My phone was and is fully stock. Didn't change anything.. Just installed the October security patch OTA and that's it. But in the past two weeks i lost from time to time carrier connection..
dr.ketan said:
Look if able to see IMEI in device settings - about phone
If IMEI is there and still you are unable to connetc to network, you should ask your operator if your IMEI got banned.
Click to expand...
Click to collapse
Hey Doc, thanks for responding!
Well, both of my IMEIs are there. I use dualsim and both of my cards accept the PIN and also shows the IMEI but on both of them no signal. This first happened after replacing the screen. I forgot 1 or 2 screws and then i had no signal. After screwing correctly, i again was able to connect to the network.
And now all of sudden immediately after updating OTA both of my sims stopped working. But well, i have seen some youtube videos saying, that it can be the GSM cable on the side of the phone. I am not sure if i replaced my old cable with the one in the new screen or if i used the old one. I will check later when i am at home.
My only guess is: GSM cable is dead, motherboard died or flex cable is damaged..
// Edit:
I removed the GSM Antenna from my old display and replaced it with my new screen. For a second i had 4G and it died again.. i took out everything at least 5 times and finally i cleaned everything with Isopropyl-alcohol and let it dry and voila my phone has signal again. No clue if some miracle happened but i am happy again.
Thread can be closed or marked as resolved