Related
I'm wondering if anyone else ever came across this weird issue. I am on the Rogers network with a HTC Dream. I've tryed several ROMs and none make a difference. The issue is, I lose 3G connection and my SIM card gets corrupted. I have a LG GW620 and I used it for a long time and this never happened. What happens is I totally lose 3g capability and I can't get it on any other phone unless I get another SIM card activated. I've had this happen to me twice now and it ONLY happens when I used my HTC Dream for couple weeks it seems. Could this be due to that my phone is using roms or is my phone just mangled? I'm just thinking of smashing this phone with a hammer as it is useless to me if my 3G connection is gone.
Any information would be appreciated.
Thanks
IIf you currently have radio 3.22.26.17, please find and download the 3.22.20.17 radio image and flash via fastboot 'fastboot flash radio-3.22.20.17.img'
The image is on bcrooks server.
Please note the imei-sv is 3 in 3.22.26.17 but 2 in 3.22.20.17, this means if you are a rogers/Fido customer with a rogers branded dream you will be flagged by rogers for not having the e911 rom.. and thus they will disable your data if you have not filled the wavier. To reactive a call to the call center is usually required (preferably on a phone other than the cell in question)
Note the radio has nothing to do with the e911 issue, as the bug was in android not the radio.. so if you have signed the wavier or are not a rogers customer feel free to use 3.22.20.17.. of if preferred downgrade to 2.x via fastboot
(its unknown if the lattest 2.x or the older 3.x provides better signal on the Rogers network .. but the newer 3.x has problems in every rom.. including the official one HTC/rogers forced on everyone, sad since the bug was just in the Java code of one file on the phone in /system.. nothing to do with the radio)
Alright just let me get this straight.
So they are flagging me because of my phone, or radio? I am a Rogers Customer, have been since 2004 I believe. How would I go about getting data to not dissapear on my phone again? I had just bought this phone used and rooted it and put on a custom OS. I'm not exactly sure which radio I have at the moment, but if i update to 3.22.20.17 would that fix the issue if I got rogers to re-activate my data?
What radio do you have now
I believe this one is on there.
Radio Image update 2.22.23.02
So if I update to Radio 3.22.26.17 via Fastboot and call the support line to re-activate my data or w.e that will work?
Not quite that simple your current rom wont work with the 3.x radio as is..
I recommend one of two things..
1) goto http://rogers.com/htcwaiver and sign it.. then call rogers saying you signed the waiver and want data back.. if it fails tell them that..
2) if this is a rogers branded dream and I assume it is unroot to the stock e911 patched rogers rom and start from scratch on android 1.5 .. this is not optimal and I highly recommend option 1.. and you still may need to call after to get data back http://forum.xda-developers.com/wik...Branded_EBI1_Dreams#Returning_to_Stock_Rogers
Huge low blow in Rogers case. Plus I have to call them cause they say my number does not exist when I put it in that Waiver. What a joke in my opinion.
Thanks for the information though. Much appreciated.
Thought I would share based on my experiences on trying to get this phone to work on t-mobile. It works on ATT 3g/T-mobile Edge, but still a pretty cool phone to have.
Also another note, this is a mod that will only go through on Windows. You will need ROOT EXPLORER app for this method to work.
1 - Make sure you are on the stock XT862 ROM, if you aren't flash it via this method found here: http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/
2 - Make sure your phone is rooted, if not download the following and follow the steps found here: http://www.psouza4.com/droid3/
3 - Unlock the phone. This can be accomplished by purchasing the unlock code, and later entering the code upon insertion of a sim card. (T-mobile ATT sim cards will work, but you will get an error saying UNLOCK FAILED, this is NORMAL do not freak out)
4 - Download the following files and unzip it to your desktop: http://www.mediafire.com/?y1wjw775v8itsx3
5 - Click Start and open cmd.
6 - Type in the following in cmd:
'cd desktop'
'cd fastboot'
'moto-fastboot flash radio radio.img'
ONCE it flashes, then enter:
'moto-fastboot reboot'
7 - Use root explorer to push the build.prop into the system folder
8 - Reboot, select GSM/UMTS in Network Settings.
AND BAM now it works. If there is any confusion please let me know.
Nice! Is that the XT883 radio you're flashing or a real unlocked (and signed) XT862 radio?
Also - change
Code:
ro.mot.phonemode.vzwglobalphone=1
to
Code:
ro.mot.phonemode.vzwglobalphone=0
in build.prop to get normal reading on signal strength indicator.
You can also change
Code:
ro.telephony.default_network=7
to
Code:
ro.telephony.default_network=3
so phone starts automatically in GSM/UMTS mode after hard reset.
Can anyone confirm that it's running on AT&T with 3G/4G?
Sent from my Droid Razr using xda premium
MeNaCe2s0cieTy said:
Can anyone confirm that it's running on AT&T with 3G/4G?
Sent from my Droid Razr using xda premium
Click to expand...
Click to collapse
it has att 3g bands you can check for yourself over at gsm arena.
leobg said:
Nice! Is that the XT883 radio you're flashing or a real unlocked (and signed) XT862 radio?
Also - change
Code:
ro.mot.phonemode.vzwglobalphone=1
to
Code:
ro.mot.phonemode.vzwglobalphone=0
in build.prop to get normal reading on signal strength indicator.
You can also change
Code:
ro.telephony.default_network=7
to
Code:
ro.telephony.default_network=3
so phone starts automatically in GSM/UMTS mode after hard reset.
Click to expand...
Click to collapse
Thanks man I'll reupload when I get back home with the edited bits . It is the XT883 radio.
Nice Guide!
I've read some people have had trouble unlocking the D3....and apparently it could be due to it being used on the Verizon network who then alter the unlock code via some update.
Anyone know if there is any truth in this? (I'm awaiting the delivery of a used D3 so would be handy to know).
fl4r3 said:
Nice Guide!
I've read some people have had trouble unlocking the D3....and apparently it could be due to it being used on the Verizon network who then alter the unlock code via some update.
Anyone know if there is any truth in this? (I'm awaiting the delivery of a used D3 so would be handy to know).
Click to expand...
Click to collapse
Even after the update, if you restore it to the first link and then follow the steps, you will be fine. It can still be unlocked.
Awesome! I am about to try this on my friend's droid 3. Are there issues with the market (as some have mentioned in a previous thread)?
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
I am stuck on <waiting for device> in the command prompt after telling it to flash the radio. What sort of USB connection should I be selecting?
EDIT: I'm an idiot.... I figured it out!
Is anyone else who is using this method on AT&T experiencing super slow data speeds? I have tried the sim card in an at&t branded phone and it seems to work ok. On the Droid 3, I am getting a ping of 2500~ ms, and speeds in the 15-60kbps range.
I can't seem to add an APN and connect to the 3G network. Does anyone else have this issue? I am using a Bell SIM at the moment
Follow all the steps, no luck here
When I put the unlock code, phone shows for a sec "requesting unlock" and goes back to a subsidy lock message with a discard dialog box.
After that, I followed all other steps, and still enter unlock code appears
Any ideas?
I dont have an att sim card, Im just using foreign sim cards cause Im outside US.
geek_riot said:
Is anyone else who is using this method on AT&T experiencing super slow data speeds? I have tried the sim card in an at&t branded phone and it seems to work ok. On the Droid 3, I am getting a ping of 2500~ ms, and speeds in the 15-60kbps range.
Click to expand...
Click to collapse
You can always call the carrier and make sure they are allowing your phone to connect. I'm not sure if this is the problem, but I read about another AT&T branded 4G phone (the D3 will never get 4G) getting only edge because the carrier thought it was foreign, and they just called in and gave the IMEI number to get access.
The customer service rep may not understand your problem, but just tell them the truth that you want to use your compatible device on your valid account and they should redirect you to someone who can help.
I can verify this works on T-Mobile and AT&T since I've tested it on both. Didn't test 3g on AT&T though cuz I didn't think about it lol. I know it allows the connection to umts in the settings though.
The OP poster helped me get it working on my phone just make sure you follow the directions closely and it's pretty simple. If your unlock codes aren't working because you got them off the internet, you may need to have the phone put on Verizon temporarily to get them to give you a code. Just ask a friend with a valid account to help you out.
Good luck to everyone, this is a great hack that definitely saves some money while letting us use this cool phone. I will have to edit my build.prop as mentioned above to fix the reboot network loss problem, thanks for that as well!
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img & custom build.prop
If verizon changed the codes while phones are connected to his network, changes could only be stored on a new bootloader.
There is no other unwritable part on the phone.
Wonder if the original poster used an ebay code or a verizon one...
Nice job! Pretty amazing what can be done with fastboot and signed radio images!
Custom ROM
What will happen if somebody follows this procedure and unlock the phone for AT&T but afterwards flash another rom? Will the radio still be unlocked for AT&T?
koukobin said:
What will happen if somebody follows this procedure and unlock the phone for AT&T but afterwards flash another rom? Will the radio still be unlocked for AT&T?
Click to expand...
Click to collapse
As long as that ROM you're flashing does not have radio image in it, you should be fine. If you meant sim lock - once unlocked, it will remain unlocked forever.
Sent from my HTC Desire Z using Tapatalk
I was asking about radio unlock, i know sim unlock is permanent. But has anyone tried to install any rom after the radio unlock and if yes which one?
thanks
koukobin said:
I was asking about radio unlock, i know sim unlock is permanent. But has anyone tried to install any rom after the radio unlock and if yes which one?
thanks
Click to expand...
Click to collapse
Just as @leobg said,
leobg said:
As long as that ROM you're flashing does not have radio image in it, you should be fine...
Click to expand...
Click to collapse
Now, I haven't tried flashing another ROM since flashing the xt883 radio.img, because I really don't mind the stock ROM with some build.prop tweaks and the help of Zeam Launcher. I would assume that any ROM you flash would cause the build.prop and radio.img to be replaced with new ones, made specifically for that ROM. You should probably consult with the developer of the ROM you want to use, and ask them if the build.prop changes specific to this process will have issues with their ROM. The xt883 radio.img shouldn't have any conflicts, but I believe it will still require the custom build.prop file which is found in the OP, or at a minimum the specific changes which allow this tweak to work.
BenSWoodruff said:
Just as @leobg said,
Now, I haven't tried flashing another ROM since flashing the xt883 radio.img, because I really don't mind the stock ROM with some build.prop tweaks and the help of Zeam Launcher. I would assume that any ROM you flash would cause the build.prop and radio.img to be replaced with new ones, made specifically for that ROM. You should probably consult with the developer of the ROM you want to use, and ask them if the build.prop changes specific to this process will have issues with their ROM. The xt883 radio.img shouldn't have any conflicts, but I believe it will still require the custom build.prop file which is found in the OP, or at a minimum the specific changes which allow this tweak to work.
Click to expand...
Click to collapse
Aslongasyoukeeptheradioandbuild.propchnges
Yikesmyspcebarisfiling and some"a's"
Enviado desde mi DROID3 usando Tapatalk
Will loading XT883 radio undo the wifi-hotspot hack?
My phone is Verizon Droid 3 XT862.
It can't use cdma 3g or 1x network.
SMS and voice is normal. WIFI is normal too.
If i use GSM card, same problem appears.
I flashed the rom , changed the file named 'ppp-rils.option'.
But nothing happened.
Please help me.
thanks.
powerword said:
My phone is Verizon Droid 3 XT862.
It can't use cdma 3g or 1x network.
SMS and voice is normal. WIFI is normal too.
If i use GSM card, same problem appears.
I flashed the rom , changed the file named 'ppp-rils.option'.
But nothing happened.
Please help me.
thanks.
Click to expand...
Click to collapse
Fully restore your phone using my Fast / Easy unbrick method, just search the general section. (All it does is restore your phone to complete stock.)
You can try other stuff, but this method seems to fix most issues that aren't "easy" to fix.
I will try this method.
But I want to know if there are something can be changed or flashed other than this rom.
I want to fix my phone's network.
It not work on cdma , gsm or wcdma.
I flash xt883 rom, but nothing happened.
Can i flash radio? Change hardware setting.
who can tell me.
powerword said:
I will try this method.
But I want to know if there are something can be changed or flashed other than this rom.
I want to fix my phone's network.
It not work on cdma , gsm or wcdma.
I flash xt883 rom, but nothing happened.
Can i flash radio? Change hardware setting.
who can tell me.
Click to expand...
Click to collapse
You don't need the xt883 ROM in order to use the phone on any foreign gsm. The phone must be unlocked by Verizon, then you need to flash the xt883 radio.img, then edit/replace the build.prop. I would flash back to stock first, since the xt883 is a weird ROM, but you probably don't have to. There are already plenty of threads where the explanations have been given, so look around: search Verizon D3 on T-Mobile, D3 on AT&T/T-Mobile, etc.
You will have to turn off 'automatically select operator' in settings and choose manually the one you're using. T-Mobile users will only get edge and below, while AT&T users will get 3g.
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img & custom build.prop
BenSWoodruff said:
You don't need the xt883 ROM in order to use the phone on any foreign gsm. The phone must be unlocked by Verizon, then you need to flash the xt883 radio.img, then edit/replace the build.prop. I would flash back to stock first, since the xt883 is a weird ROM, but you probably don't have to. There are already plenty of threads where the explanations have been given, so look around: search Verizon D3 on T-Mobile, D3 on AT&T/T-Mobile, etc.
You will have to turn off 'automatically select operator' in settings and choose manually the one you're using. T-Mobile users will only get edge and below, while AT&T users will get 3g.
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img & custom build.prop
Click to expand...
Click to collapse
I flashed xt862 rom .
Calls and text is OK whether GSM or cdma.
Network is wrong whether GSM or cdma.
I changed APN settings, nothing happened.
What can i do next.
powerword said:
I flashed xt862 rom .
Calls and text is OK whether GSM or cdma.
Network is wrong whether GSM or cdma.
I changed APN settings, nothing happened.
What can i do next.
Click to expand...
Click to collapse
I'm not sure what is wrong with your connection, but mine has problems sometimes where the phone will not recognize any available gsm networks. It's sometimes like this after I reboot my phone, but if changing my settings doesn't work, rebooting again will usually work.
Is your phone unlocked by Verizon? Did you flash the xt883 radio.img since changing your ROM? Did you replace your build.prop file with the tweaked one? I will try to find these resources for you if you still need them, but you should be able to find them by searching if you haven't already. After doing these things, you just have to reboot then go to your settings and tell it to prefer gsm. On T-Mobile, you wont get umts. On AT&T you will get gsm and umts.
In settings, you need to select wifi & network settings -> mobile networks -> network mode -> then choose gsm/umts, back to mobile networks -> under gsm/umts settings, click select network, then choose gsm only for T-Mobile or automatic for AT&T, then click operator select, select network and choose your operator. Select automatically will have a check box next to it and you should deselect it. I didn't have to put in my apn settings, because my sim card provides those automatically.
If these settings tweaks don't work for you then I really have no clue what will fix it because it is likely that something else is wrong. I can't be of much more help without seeing the device. I would suggest to keep playing around in settings and just use your head to see why it's not connecting. If you are getting voice and text service on your carrier, data shouldn't be a problem if your settings are done correctly.
Good luck!
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img & custom build.prop
I have been fiddling with RadioComm v11.11.11 (is this the latest version?), and there are some sections that deal with the TX power and other items for the radio. Has anyone successfully tweaked the radios on these devices? I am running a XT862 with a Xt883 radio, on T-Mobile. The reception of this phone is pretty bad, and it takes it a LONG time to find signal again, once you get it into a known good reception area. Any ideas/pointers?
Did you try using CM9 for some reason I get better reception on it.
nemiroG1 said:
I have been fiddling with RadioComm v11.11.11 (is this the latest version?), and there are some sections that deal with the TX power and other items for the radio. Has anyone successfully tweaked the radios on these devices? I am running a XT862 with a Xt883 radio, on T-Mobile. The reception of this phone is pretty bad, and it takes it a LONG time to find signal again, once you get it into a known good reception area. Any ideas/pointers?
Click to expand...
Click to collapse
Does it do this with all roms? It sounds like something may be wrong with your phone. I have had very few issues and I live in a notoriously poor reception area for both AT&T and T-Mobile.
Also, are you running the updated build.prop? I added some signal improvements in the v2 file.
It has done it with .894, .905 and now on .906. I realize these are VZW CDMA ROMs. Not sure if something is hanging around in there. I also have not tried swapping out any of the RIL files. Should I? I've made my own build.prop (attached), renamed build.txt, for the .906 VZW build. It gets GSM and EDGE data on T-Mobile. Would you mind looking it over? If it can be tweaked, I'm all over it!
I have tried flashing CM9, and it just keeps giving me boot loop issues. I will download the latest, and try it tonight.
nemiroG1 said:
It has done it with .894, .905 and now on .906. I realize these are VZW CDMA ROMs. Not sure if something is hanging around in there. I also have not tried swapping out any of the RIL files. Should I? I've made my own build.prop (attached), renamed build.txt, for the .906 VZW build. It gets GSM and EDGE data on T-Mobile. Would you mind looking it over? If it can be tweaked, I'm all over it!
I have tried flashing CM9, and it just keeps giving me boot loop issues. I will download the latest, and try it tonight.
Click to expand...
Click to collapse
It should not matter since the radio is independent. Only some custom roms might have issues with GSM. Stock Verizon would be the best place to test reception issues.
Try this build.prop on your existing rom and see if it makes any difference:
http://forum.xda-developers.com/showthread.php?t=1406812&page=8
Hi, I forget to enter my unlock code and I just flashed the phone with XT 883, so no GSM sim is not working even is not asking for activation code, only CDMA sim is working. How I can get back the verzion ROM to enter the unlock code ? Please help me out
radiocomm
radiocomm-I have 11.12.2- here it is if u need it
https://www.dropbox.com/s/ctgg9obrjdkf1in/RadioComm_v11.12.2_Install.msi
Not the latest version,the latest version is 12.xx
can u post it
Can u post it or pm me,I like to stay on top o the newest of the radiocomms,thanks for the reply
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.