Related
a quick history of what I've done so far
Sumsung I897 captivate from ATT unlock and being used on Telus network was working great for about 4 days, then all kinds of problem started cropping up.
Phone came unlocked, I rooted using update.zip from xda, installed rom manager and started removing ATT bloatware, entered SMS and APN info which worked fine.
Yesterday I noticed that where I once got good reception I was now getting nothing and would have to drive down the street before I would get something descent. I thought maybe I'd put it back to stock with rom manager and see if that would help which it did not. It actually made it worse, decided to go all out and use the Odin3 one click downloader just to make sure I was back to stock firmware. This didn't work either but now I can enter the SMS and change the preferred network type but it doesn't save. Preferred network type is grayed out and even though I can change it it never save same as SMS.
Now I can't hold connecting in my living room where my wifes Milestone gets full bars. I tried taking the phone to where I had the best signal and change the preferred network, SMS, and set the network operator but it doesn't save any info, can't find on operator half the time on manual or auto and gave me an error and logged it to #*9900#
I've been at this for 2 days straight and can't figure out how to get it right back to stock, it seems to keep hanging onto the same preferred network and not saving anything I enter.
What can I do to get back to stock, and it has to be something that wipes everything clean, clean, clean, because even the GSM disconnects stay logged under *#*#4636#*#*
***I desperately even tried pulling the batt and SIM card for the night in hopes that would do something.
So, if I'm understand what happened correctly, you bought an unlocked Captivate, rooted it, deleted some bloatware, entered your Telus APN info and everything worked awesome for about four days. Now everything has gone down the hole. Is that right?
If that is the case, then we need to figure out what changed. Using Odin3 would have definitely put you back to stock/unrooted your phone, I don't think you could go back any further than that. If I were you, I would act like I first got the phone. As in, I would do everything you did to it, as if was day one. At one point, everything worked fine. Try to recreate that. You can always look into exchanging it or perhaps Samsung customer support can give you a little more insight to what's going on. Here's the number if you want to try them out.
Samsung customer service - 1.800.726.7864
Thanks, I've gone through the process a few times today from start to finish trying to figure it out ... maybe some of the problems aren't real problems and just limitations that I didn't know where their. I've since flash with odin3+re-partion to the bone stock i897UCJF6 as in not the one click method. It loaded fine but still have the same issue, I can't set preferred network type or get it to keep the number entered into SMSC. I think if I can get passed that I'll be be one the up side of winning. I keep noticing that the log of GSM disconnects never clears or the usage statistics under *#*#4636#*# , I'm thinking its in the same area that other bad data is being held onto instead of being cleared when flash firmware or factory reset.
Is anyone able to change preferred network type? maybe I was never able to change it but I think I should be able too.
I may be wrong in assuming this but I don't think ATT is going to be interested helping me connect one of their handset that I'm trying to use on foreign network, but I could be wrong and is an open option.
*#*#197328640#*#*
debug screen
phone control
network control
band selection
wcdma band
wcdma all
menu->end
used this to lock my phone to WCDMA only so that problem is solved
*** never mind posted to soon it still didn't stick after rebooting
be carefull using the service menu as I have no idea what most of this stuff does
I got the SMS service number issue fix by taking out my sim, swapping in another known working sim from the same network, setting the service number, pressing update and then swapping back. Before every time I tried to update the service number it spit out an "update error" can anybody tell where the SMS config data is stored? on the phone or sim.
The only problem I'm having now is with reception which maybe fixable if I can set the preferred network to WCDMA only. But the button for that option is a light blue colour vs other phones that I can change this setting on. Does the blue mean anything like a locked function or something that set by the firmware as unchangeable?
Hi All,
I'll start this off by saying I have an outright purchased, unlocked device, that has had all the latest Samsung updates applied.
I found a rather nasty problem with my i9305 a few weeks ago - I tried to change to WCDMA/GSM (auto) and then GSM only to test a problem i was having with MMS (problem all sorted now, this is not my question) and when I did that, I found that everytime I selected the network mode of LTE/GSM/WCDMA (Auto) the phone automatically snapped it back to GSM/WCDMA (Auto) as soon as I left the settings.
I tried restarting the phone several times and changing APNs but still the same thing occured. The only way I could find to get 4G service back was to factory reset the phone!
As you all know this can be a major hassle. Earlier this week (long after this happeend) I have rooted the phone (using the ExynosAbuse APK that Chainfire posted) but i'm waiting until i have some more time (probably next weekend) to install twirp or CWM recovery so i can backup my rom before attempting to change it again (rom backup + titanium backup = should make a factory reset a bit less painful).
I'm wondering if anyone from here has any advice for me on anything I might be able to do to fix this bug for the future. I wouldn't mind dropping back to WCDMA only sometimes. Until I get decent backups all sorted I'm too scared to try doing it again as I *really* don't want to lose 4G.
Also, if it's ok to ask 2 questions in one post, my locale keeps reverting back everytime i restart the phone - is there a way to permanently change this? That is a minor niggle compared to the major problem i have with an inability to turn 4G off without factory resetting the device though.
Please Help - how can I fix this?
Regards,
Jason
Unfortunalety i don't have much to add, but this doesn't happen to me and i change from LTE to WCDMA all the time
The locale issues seems odd too, maybe something is up with your phone?
jjcoolaus said:
Hi All,
I'll start this off by saying I have an outright purchased, unlocked device, that has had all the latest Samsung updates applied.
I found a rather nasty problem with my i9305 a few weeks ago - I tried to change to WCDMA/GSM (auto) and then GSM only to test a problem i was having with MMS (problem all sorted now, this is not my question) and when I did that, I found that everytime I selected the network mode of LTE/GSM/WCDMA (Auto) the phone automatically snapped it back to GSM/WCDMA (Auto) as soon as I left the settings.
I tried restarting the phone several times and changing APNs but still the same thing occured. The only way I could find to get 4G service back was to factory reset the phone!
As you all know this can be a major hassle. Earlier this week (long after this happeend) I have rooted the phone (using the ExynosAbuse APK that Chainfire posted) but i'm waiting until i have some more time (probably next weekend) to install twirp or CWM recovery so i can backup my rom before attempting to change it again (rom backup + titanium backup = should make a factory reset a bit less painful).
I'm wondering if anyone from here has any advice for me on anything I might be able to do to fix this bug for the future. I wouldn't mind dropping back to WCDMA only sometimes. Until I get decent backups all sorted I'm too scared to try doing it again as I *really* don't want to lose 4G.
Also, if it's ok to ask 2 questions in one post, my locale keeps reverting back everytime i restart the phone - is there a way to permanently change this? That is a minor niggle compared to the major problem i have with an inability to turn 4G off without factory resetting the device though.
Please Help - how can I fix this?
Regards,
Jason
Click to expand...
Click to collapse
have you tried the service menu (access from dialpad).
Just dial the following keys *#197328640#
smaberg said:
have you tried the service menu (access from dialpad).
Just dial the following keys *#197328640#
Click to expand...
Click to collapse
Thanks for that - when i'm in it though, I can't see any obvious method to lock the phone to UMTS only, LTE only, etc?
Each option just allows me to run various tests or find out more about that particular radio part.
PS - I've fixed my non-sticky keyboard & locale settings using Tasker:
Profile is at Device Boot, change keyboard to swiftkey 3, and locale to English (Australia) (it's this last bit that doesn't work yet, but i've raised it in the Secure Settings plugin thread
Hi.
I have never experienced this nor heard about it. But my natural reaction would be to hard reset my phone.
I do it regulary. Once a week somtimes.
It sounds as if your phone has encounterd a unusual state.
Either return it (unrooted) or do a hard reset. Some problems is not worth digging in to.
Sent from my GT-I9305 using XDA Premium HD appI.
i have a same question, what a pity..
I do not believe there is a English (Australia) so that is where that issue is coming from, unless I have completely missed looking at it somehow
For the LTE issue
It is very likely that the issue was solved after the first factory reset so you should have tried it after resetting it
If this persists through a custom ROM then I advise reseting your flash counter (not needed as you used the Exynos exploit though) and bringing it back to stock then sending it straight into Samsung as it may be a problem with the LTE chip itself
Sent from my GT-I9305 using xda premium
Getting GSM (& Straight Talk) working on the Droid Bionic running Jelly Bean 4.1.
If you're here I'm sure you know now that it is possible, contridictory to all those who claim it's not because of these specs or that data sheet or press release.
Apparently it has the exact same radio / chipset as other Moto World phones it's just not for lack of a better term "unlocked".
BTW...If I was to recommend an order to do the "trifecta" in, this would be the last step. I doubt it would effect rooting. But MOST of the problems I ran into updating to JB had to do with the fact I originally did this when I was still on ICS, then it caused a bunch of probs while trying to update. Namely all of the "System 7" errors. See that thread for more.
****FIRST AND FOREMOST*****
Make copies of every file you change in their current untouched state, before editing, and if you can't, keep notes of their current values.
Also do not do this with the SIM in, it's not required for anything other than testing and getting a signal at the end.
This, from my experience, is also the cause of the "android.phone" shut down error loop.
IF you get that, shut the phone down in between hitting the "ok" button of the error loop and remove the SIM and continue. Once you finish and have reception it shouldn't return.
Follow the build.prop edits shown on the XDA thread "Bionic working on T-MO."
*You have to have root access to edit this file. I use ES File Explorer, use in "root" mode and enable R/W for everything. Whatever file explorer you use I'm sure it's similar, just look thru the settings.*
Then I saved changes & rebooted, and did the RadioComm part. Apparently this is the step that turns on / unlocks the GSM radio.
When you open RadioComm and it asks what setting to start on pick, same as chipset setting (will edit & update w exact in a minute don't have it open right now, you have to scroll about midway down the list tho.)
*If the big box in the middle right doesn't fill up with code, or totally turn green after you make the change to the first (16) numbers & save, somethings wrong and the edit didn't save. restart the steps & make sure they're right. Close RadioComm. You're done with it (...for now)
Disconnect Phone & Reboot.
After boot go to Dialer and type *#*#4636#*#* (*#*#info#*#*), should go right to a menu & pick Phone Info. go down to "set preferred network type" & pick WCDMA. back out and should be done.
People have said this won't stay set for them. Following all the instructions, I've not had a problem keeping a network set. I believe this is controlled with one of the build.prop edits. There are suggested fixes out there, if you go thru the settings and edits and you're still having a prob, try those.
In truth, mine defaults to GSM/CDMA auto (PRL), but it doesn't seem to effect my service, and I believe that will auto switch between networks which is fine with me becasue I can't get CDMA with the GSM sim anyways.
If you just want GSM, that should be it. Power down, put your SIM in and reboot. If you have AT&T or T-Mo, the APNs are already loaded and should default after phone reads SIM.
If you get "unknown SIM" dialog just click "ok". It will come up every time you reboot your phone tho so if you want to put an end to it, there's a quick build.prop edit that fixes it. Will Post exactly when I find it again.
but it's something like changing:
vzwphone=1 to
vzwphone=0 (only for ref until I get it up).
****Straight Talk (At&t SIM)
Before putting in SIM and after Preferred Network change.
go to Dialer, ##7764726 (##program) & hit "call" / phone button, enter "000000" for SPC password & "Verify".
Go down to #13 APN Controls,
then APN Config Edit.
Touch menu button on phone (4-squares) & New APN.
These are my settings & Voice, Data & MMS all work.
Name: Straight Talk AT&T
APN: att.mvno (make sure "MVNO" had this as MNVO and couldn't figure out what was wrong)
MMSC: http://mmsc.cingular.com
MMS proxy: 66.209.11.33
MMS port: 80
MCC: 310
MNC: 410
APN type: default,supl,mms,hipri,dun (no space betw commas)
That's it. anything not listed above was left blank or as it defaulted.
power down put in SIM, and in a few minutes you should have service.
If you do, try going on internet, if that works, try sending yourself a picture msg.
All have worked for me.
****BTW - 2 things....make sure you have Wifi turned off, & you have mobile data enabled / on. (the mobile / packet data "On" thing was the issue with my Captivate Glide not getting data & MMS and it drove me nuts, then to find out it was just a switch & bang worked great.)
I hope this helps at least someone.
Cheers.
the one issue I still kinda have....
For whatever reason I get great data speeds.
typically 4.5 - 6+ Mbps down & 1.5 - 2 up.
but my voice levels are typically high -80's to -105 dbms
which equals at best, a not steady 3 bars.
Usually only 2 bars (mid -90's dbms) and quite often the little spec of a triangle.
I've tried the RadioComm Hex edit & adding lines to the build.prop to get boost signal reception that others have said helped them. Neither have done anything for me. (found here)
Currently still have both "running".
also tried this build.prop change
vzwglobalphone=1 to
vzwglobalphone=0
still no change.
The reason this is kinda an issue for me is my daily is currently a Samsung Captivate Glide and I Consistantly am at 4+ bars and high 70's. I don't know why I shouldn't get same reception in same areas, especially because I read that Moto radios are better than Samsung ones.
I do wonder if it's because the other is a "native" GSM, but then I think that the Moto is too, it was just "turned off" before.
Again I'm not a Dev, but I do want this to be my daily, so I'm willing to try pretty much anything since I have a back-up. So if anyone who knows more than me or has found a fix that works for them, please share.
i have followed your directions to the letter but still get bootloop. can u b a lil more detailed on how to save the build.prop to prevent this
@ smutta - Do you mean the android.phone shut down error? THe only time I experienced a boot loop was when I updated to JB, and that's when I was getting the "motorola dual core" boot animation loop. The result of that in my case was the "system 7" errors I mentioned in the JB update thread. Those are a result of, lack of a better way of putting it, the checksum's not matching what the update is looking for. Any hacks / changes you've made will seem to cause it to error out and the boot loop. Please check that thread too.
good luck.
MoodSwinger said:
@ smutta - Do you mean the android.phone shut down error? THe only time I experienced a boot loop was when I updated to JB, and that's when I was getting the "motorola dual core" boot animation loop. The result of that in my case was the "system 7" errors I mentioned in the JB update thread. Those are a result of, lack of a better way of putting it, the checksum's not matching what the update is looking for. Any hacks / changes you've made will seem to cause it to error out and the boot loop. Please check that thread too.
good luck.
Click to expand...
Click to collapse
Thank you i got it working and with a few roms also
@MoodSwinger
I am very new to this whole hack thing.
I've read, read, and read some more about trying to find the right way to do this.
I've successfully (through a combination of steps on here and other threads) got my (previously Verizon) Bionic on the Straight Talk network. I have voice, text, and data. Now, I'm running into a few of things that I can't seem to fix.
1st- My radio signal is real low (1 bar to 3 max) The network does not read 3G, it reads "H" ... What does that mean? I've never seen "H".
2nd- The phone seems to have a hell of a time detecting the SD card. Sometimes it does, but most of the time it doesn't.
3rd- I usually have no problem getting my apps back on from my Google account that backs them up after I would FXZ. I usually have to re- download them, but they are at least there. That doesn't happen anymore. I don't know how to recover them. This might have something to do with not having the proper signal. ???
What do you think I should do from here? Any input?
I have a feeling that a couple of tweaks in the build.prop would do the trick, but I'm not sure which ones to modify.
Also, I called Straight Talk and they gave me a more suitable APN for my area(I guess):::::
Name:
Straight Talk
APN:
tfdata
MMSC:
h t t p://mms-tf.net (without the spaces in the http, of course)
MMS Proxy:
mms3.tracfone.net
MMS port:
80
----------------
The rest he told me to just let it default, and that it would fill in itself if need be.
Otherwise, I tweaked the build.prop just like you illustrated in your post.
Thanks for the help, or even pointing me in the direction of an amazing Motorola radio tech.
I have root and I have flashed thru radiocomm the 1877 values.
I get the android.phone FC every time I switch to anything GSM or WCDMA related in phone testing.
I can't find the current workable build.prop edits, am trying to get it to work on Simple mobile.
Also what does renaming / deleting the stk.apk and atk.odex do?
Current edits
persist.radio.ap.phonetype=2 and changing the value to 1.
^only for JB
ro.telephony.default_network=7 (to set GLOBAL preferred network type)
ro.mot.phonemode.vzw4gphone=0 (to make possible APN edit)
telephony.lteOnCdmaDevice=0 (to fix signal strength and wrong carrier)
ro.telephony.ril.v3=signalstrength (to fix non-updating signal strength indicator)
I probably knew what it did at some point but I've since forgotten.
gsm help!!
hey guys i have my droid running both cm 10 and liquid v 2.9 . ive done all the build.prop edits and then some and when i set the prefered network it keeps finding aTT instead of t-mobile which is what im asumming it should be on for metro...i really need help been at this a while on and off i feel like im real close.
Deadman001 said:
Current edits
persist.radio.ap.phonetype=2 and changing the value to 1.
^only for JB
ro.telephony.default_network=7 (to set GLOBAL preferred network type)
ro.mot.phonemode.vzw4gphone=0 (to make possible APN edit)
telephony.lteOnCdmaDevice=0 (to fix signal strength and wrong carrier)
ro.telephony.ril.v3=signalstrength (to fix non-updating signal strength indicator)
I probably knew what it did at some point but I've since forgotten.
Click to expand...
Click to collapse
with this changes on build.prop you get strong singnal and no more signal drops?
MoodSwinger said:
Getting GSM (& Straight Talk) working on the Droid Bionic running Jelly Bean 4.1.
If you're here I'm sure you know now that it is possible, contridictory to all those who claim it's not because of these specs or that data sheet or press release.
Apparently it has the exact same radio / chipset as other Moto World phones it's just not for lack of a better term "unlocked".
BTW...If I was to recommend an order to do the "trifecta" in, this would be the last step. I doubt it would effect rooting. But MOST of the problems I ran into updating to JB had to do with the fact I originally did this when I was still on ICS, then it caused a bunch of probs while trying to update. Namely all of the "System 7" errors. See that thread for more.
****FIRST AND FOREMOST*****
Make copies of every file you change in their current untouched state, before editing, and if you can't, keep notes of their current values.
Also do not do this with the SIM in, it's not required for anything other than testing and getting a signal at the end.
This, from my experience, is also the cause of the "android.phone" shut down error loop.
IF you get that, shut the phone down in between hitting the "ok" button of the error loop and remove the SIM and continue. Once you finish and have reception it shouldn't return.
Follow the build.prop edits shown on the XDA thread "Bionic working on T-MO."
*You have to have root access to edit this file. I use ES File Explorer, use in "root" mode and enable R/W for everything. Whatever file explorer you use I'm sure it's similar, just look thru the settings.*
Then I saved changes & rebooted, and did the RadioComm part. Apparently this is the step that turns on / unlocks the GSM radio.
When you open RadioComm and it asks what setting to start on pick, same as chipset setting (will edit & update w exact in a minute don't have it open right now, you have to scroll about midway down the list tho.)
*If the big box in the middle right doesn't fill up with code, or totally turn green after you make the change to the first (16) numbers & save, somethings wrong and the edit didn't save. restart the steps & make sure they're right. Close RadioComm. You're done with it (...for now)
Disconnect Phone & Reboot.
After boot go to Dialer and type *#*#4636#*#* (*#*#info#*#*), should go right to a menu & pick Phone Info. go down to "set preferred network type" & pick WCDMA. back out and should be done.
People have said this won't stay set for them. Following all the instructions, I've not had a problem keeping a network set. I believe this is controlled with one of the build.prop edits. There are suggested fixes out there, if you go thru the settings and edits and you're still having a prob, try those.
In truth, mine defaults to GSM/CDMA auto (PRL), but it doesn't seem to effect my service, and I believe that will auto switch between networks which is fine with me becasue I can't get CDMA with the GSM sim anyways.
If you just want GSM, that should be it. Power down, put your SIM in and reboot. If you have AT&T or T-Mo, the APNs are already loaded and should default after phone reads SIM.
If you get "unknown SIM" dialog just click "ok". It will come up every time you reboot your phone tho so if you want to put an end to it, there's a quick build.prop edit that fixes it. Will Post exactly when I find it again.
but it's something like changing:
vzwphone=1 to
vzwphone=0 (only for ref until I get it up).
****Straight Talk (At&t SIM)
Before putting in SIM and after Preferred Network change.
go to Dialer, ##7764726 (##program) & hit "call" / phone button, enter "000000" for SPC password & "Verify".
Go down to #13 APN Controls,
then APN Config Edit.
Touch menu button on phone (4-squares) & New APN.
These are my settings & Voice, Data & MMS all work.
Name: Straight Talk AT&T
APN: att.mvno (make sure "MVNO" had this as MNVO and couldn't figure out what was wrong)
MMSC: http://mmsc.cingular.com
MMS proxy: 66.209.11.33
MMS port: 80
MCC: 310
MNC: 410
APN type: default,supl,mms,hipri,dun (no space betw commas)
That's it. anything not listed above was left blank or as it defaulted.
power down put in SIM, and in a few minutes you should have service.
If you do, try going on internet, if that works, try sending yourself a picture msg.
All have worked for me.
****BTW - 2 things....make sure you have Wifi turned off, & you have mobile data enabled / on. (the mobile / packet data "On" thing was the issue with my Captivate Glide not getting data & MMS and it drove me nuts, then to find out it was just a switch & bang worked great.)
I hope this helps at least someone.
Cheers.
Click to expand...
Click to collapse
i have done many bionics using this radiocomm hack, everything works on stock, but when i try AOKP rom 4.2 (milestone 2) , custom rom, my sms do not work (inmeadtly receive a message not sent error) any ideas why?
No, no ideas. Is it just SMS or MMS too? or all data? can you get on the internet? does it work w WIFI?
I have been wanting to try the AOKP rom, but I installed the MS1 and at that time it didn't work w GSM, so I haven't gotten around to trying it even since the GSM patch had come out. Does the MS2 have the GSM "Built in"? If I can use it w Safestrap I'' give it a shot and see if I can fig it out.
arana1 said:
i have done many bionics using this radiocomm hack, everything works on stock, but when i try AOKP rom 4.2 (milestone 2) , custom rom, my sms do not work (inmeadtly receive a message not sent error) any ideas why?
Click to expand...
Click to collapse
Honestly, every straight talk modded phone i have seen that isnt getting sms has a problem within the apn settings. The ones you quoted in that post are the best i have used but depending on where you live, you may have to use the tracfone version. Or it ay be something totally different and unique.
MoodSwinger said:
No, no ideas. Is it just SMS or MMS too? or all data? can you get on the internet? does it work w WIFI?
I have been wanting to try the AOKP rom, but I installed the MS1 and at that time it didn't work w GSM, so I haven't gotten around to trying it even since the GSM patch had come out. Does the MS2 have the GSM "Built in"? If I can use it w Safestrap I'' give it a shot and see if I can fig it out.
Click to expand...
Click to collapse
I got it fixed, just tweaked some biuld.prop settings , that was the problem, i had made the buildprop tweaks only in the stock one, so no wonder the aokp had problems, and to answer your question , everything works, WIFI, DATA, just by installing it you will not get GSM working you have to do:the the radiocomm edit, the build.prop edit, i even got FM radio working again on JB, no the MS2 doesnt work as GSM until you make the changes, but ponce you do , everything GSM is in there in the aokp menus (apn edits, etc)
I have my bionic going on straight talk w/At&t. Under settings>mobile networks>Network operators I have the choice to search networks and select from a couple of different At&t options, a t-mobile option or I can set it to "choose automatically." Should I keep this on choose automatically or should I select one of the At&t networks it detects, and is there a difference? The two at&t bands appear to operate at the same frequency whereas the T-mobile network looks like a smaller range. I'm trying to optimize signal/data. Thanks in advance.
***UPDATE*** I left my house for the first time today since getting my phone going on GSM w/AT&T StraightTalk and I had 4 bars of reception and full 3g downloads and full messaging capabilities. I'm satisfied with the results and I think any difference in signal strength may come from having been spoiled on Verizon's coverage, even though I never got good reception at my house with verizon either so I guess I can't expect more from someone else.
I can root, flash recovery, flash the TBH GSM.zip hack -- As soon as I reboot from CWM I recieve the error "Encryption Unsuccessful" screen.
I am on 0A.78 - restoring with cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip (It is the only build that won't err on flash.)
After Restore, I use Oracle VM Ware to root with Root_Bionic_JB_20130501-4.ova
I then install BionicBootstrap.apk - I reboot into CWM, then BAM- Encryption error all over again......
Any ideas? I've been all over the Android boards and can't find much help. I have only had SIM detection and service 1 time previously- I tried to make a call and the phone would not connect. I had to do a manual reboot and I was right back where I started.
You can't use Bionic BootStrap recovery on any build after ICS and you also can't use the TBH zip method anymore.
You have to use RadioComm or other NV access tool to make the edits manually along with the build.prop edits needed.
Is there an actual STEP BY STEP guide? I had it working on stock 4.1.2 ... as soon as I flashed a custom recovery I was right back to Encryption unsuccessful. I was up for 24 hrs + last time when I managed to get it going, so needless to say I'm a little fuzzy on the details of how I managed it.
finally
I had an awful time of trying to use my stock ROM with ST AT&T; I damn near lost my mind.
Most threads fail to mention (or as a newbie I couldn't decipher) that a custom ROM is the way to go, and oh so amazing.
SS slot 2, changed a few lines in build.prop including my default network to WCDMA preferred (which I could not do in stock), easily added APN using the ST Data Settings app, and it is going pretty good so far. The only problem I am experiencing is the absence of my car dock, but that is a whole 'nother thread!
Thanks for all y'all's help! Very brilliant!
I have rooted my phone, and am trying the radiocomm hack, but, radiocomm is not recognizing my phone. how can i get radiocomm to recognize my device is connected?
For just one post that a lot a stuff well anyways, one problem I see is that on the XT860 rom it doesn´t read the SIM ID but on the XT862 it does. Since in my stupidity something tells me that that maybe related to the fact that is not reading the sim properly, I guess I will go into that route to find out what´s happening.
Just a quick update for ya.
Just installed minimoto version of the XT860 into my XT862 and it worked, the only problem is that it says invalid sim, but interestingly I can receive and make calls, signal indicator works better also. Anyways, I will try to find out how to get the rom to detect the sim correctly later.
Click to expand...
Click to collapse
Re phrasing the question, is there a way to make an xt862 into an xt860, since they are technically the same phone, just with different radios. What I want is to maybe use the phone.apk from the xt860 (that is only gsm/utms) into the xt862, in that way the phone won´t be looking for CDMA settings.
Is that possible?
Click to expand...
Click to collapse
Hi guys, I already searched on google, on xda, on droidforums and I haven´t found a way to disable the Global mode and CDMA mode, because in my country we don´t use CDMA anymore just GSM (GSM with sim card).(since 1990 something, the whole country moved to GSM).
I want my Droid 3 to just have the option between 2G and 3G (that would be Edge and 3G here), the only option I need would be GSM/UMTS. the other 2 options are CDMA and Global and I want to get rid of them.
Also because for some reason in some areas if I am in 3G and I get a call, the call will drop after making some weird sounds and I will get no signal for some minutes, and I will have to manually go into airplane mode and then out to get a signal again.
So I think, since the phone has this global mode thing, I though what the hell, let´s just disable the global mode and cdma mode and that will fix it. I mean, I believe that the phone instead of falling back to gsm mode (from 3G in lower signal areas) it goes directly to global mode, or even CDMA.
For more info, my phone is a Droid 3 XT862, from Verizon, unlocked and brought overseas, using the latest minimoto rom (I wanted something light so minimoto looked good).
I already applied some build.prop fixes and they worked but the ultimate fix would be to disable global and cdma mode.
Is it possible?
Click to expand...
Click to collapse
XDADoog said:
For just one post that a lot a stuff well anyways, one problem I see is that on the XT860 rom it doesn´t read the SIM ID but on the XT862 it does. Since in my stupidity something tells me that that maybe related to the fact that is not reading the sim properly, I guess I will go into that route to find out what´s happening.
Just a quick update for ya.
Click to expand...
Click to collapse
I was wondering if this is possible too, I know there is a line in the build prop that sets gsm to default, but it seems that my droid 3 will change that setting once in a while.
I, too, would like a permanent fix for this.
I do not use Minimoto, but I do use the XT883 radio. I have zero idea how I did it, but my Stock rom (I use SS) does NOT have the network choice. I assume this is what you were aiming for. It only shows the GSM options (2g/3g/auto toggle, Operator select, and APNs menu) and nothing for CDMA. Effectively making my Stock rom GSM only like the XT860. SIM reads fine, calls/text/data all work, no invalid SIM reading anywhere.
I've attached a couple screenshots to showcase this (if it's what you want) and my modified build.prop (incase this is actually what caused it). I've no idea what I've done to the build.prop, I've gone through and randomly changed things in my adventure of doing GSM tweaks, and I mainly use Maverick so my main modifications (that I remember) are there. Use at your own risk, though I doubt it'll do any harm (remove the .txt from the end and make sure you have proper permissions). Remember to backup your originals.
Interestingly enough im having the opposite problem on my XT862. I flashed Minimoto 1.7 to it and I get the "Invalid SIM, 911 calls only" message. Which is weird since my phone works off of CDMA. Anyone else have a clue to remedy this?
I tried your build.prop on the stock ROM with the xt883 radio, but after setting permissions and rebooting, I still have the CDMA network options present, plus the occasional "switch to global" prompt.
--posted from my phone
Skreelink said:
I do not use Minimoto, but I do use the XT883 radio. I have zero idea how I did it, but my Stock rom (I use SS) does NOT have the network choice. I assume this is what you were aiming for. It only shows the GSM options (2g/3g/auto toggle, Operator select, and APNs menu) and nothing for CDMA. Effectively making my Stock rom GSM only like the XT860. SIM reads fine, calls/text/data all work, no invalid SIM reading anywhere.
I've attached a couple screenshots to showcase this (if it's what you want) and my modified build.prop (incase this is actually what caused it). I've no idea what I've done to the build.prop, I've gone through and randomly changed things in my adventure of doing GSM tweaks, and I mainly use Maverick so my main modifications (that I remember) are there. Use at your own risk, though I doubt it'll do any harm (remove the .txt from the end and make sure you have proper permissions). Remember to backup your originals.
Click to expand...
Click to collapse
I have the 862 with the 883 radio and occasionally my phone will lose the cdma/global options entirely but then after a reboot they willl randomly reappear. The first time this happened I thought it was great lol cuz I don't need them anyways but then the box that normally pops up if you lose gsm signal asking you to switch to global popped up but said "no cdma signal detected, switching to gsm/umts mode" which is exactly the opposite of what it normally says. Kinda weird and I have no idea what would cause it since I'm using the build.prop found in the diy thread with no other changes that I would assume many others are using.
Sent from my XT862 using xda app-developers app
Hello,
I feel like this has probably been covered before, I have tried to search a bit, but the options that I have been finding (here and other places) either don't work or confuse me.
I recently bought my phone from Best Buy. They did not have a verizon note 8 in stock, but did have an unlocked one in stock. I was told that there was no difference and that it would be better ie. no verizon bloatware.
I thought that this would be a great deal and bought the phone, best buy swapped everything over for me (did not transfer apps and such as I wanted to go through and pick what I wanted to keep). Phone has worked great until 2 days ago (I've had it for just over a week now). I bought it when I was on the road down in Wyoming. Everything functioned like it should.
I travel home to North Dakota and try to send some pictures through text message...MMS? It had been a few days since I had tried it but I get an error. It says "Service not activated on network" and then "server response error". After spending an hour in the verizon store trying to solve this on the phone with a level 2 tech at verizon, they concluded that they weren't able to figure it out because I was running different software than they were used to. They are currently investigating it and will get back to me. I feel that chances are that since I did not get a Verizon phone they will probably just tell me not our problem and good luck!
Anyways, I feel that this is probably an issue with the APN settings, however my phone has them greyed out, I cannot do anything with them. I have researched a few different options, including rooting (don't really want to do) and none of them seem to work. I was hoping that you guys could help me out! I apologize if this isn't the correct forum, I just saw that there seems to be a great wealth of information on here and figured I'd ask.
PS. Mobile data,hotspot,phone calls, regular text,etc all work. It strictly seems to be MMS.
Thanks!
There is an add button in the apn settings. If the greyed out are not correct, you can add your own and then use them.
Sent from my Galaxy Note8 using XDA Labs
Thanks for the response!
Unfortunately even that is greyed out as well. Clicking it doesn't do anything. Also their are three little dots next to the add button and that brings up a greyed out "restore to default" clicking that doesn't do anything either.
On the apn screen it says something along the lines of "current user profile does not have access". I'm starting to think this is something verizon built into the phone or sim card, any other issue I've found similar to mine all seems to be related to Verizon.
Any other suggestions?
Thanks!
Apn setting
Check this out.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-enable-hot
Try the steps here
Mod Edit
This is strictly related to apn settings, so you might be able to fix this issue
Thanks! I haven't had time to try these but I hopefully can this evening.
Thanks for the responses!
Hey, did you find a solution for editing the APN?
No I didn't...it's all locked by the Verizon sim card. I had to get Best Buy to swap me over to a Verizon phone.
Very unfortunate that they decide to do this.
Well I have a unlocked note 8 on metro and I can edit the apn. You can try to update phone see if th that works. Pr a factory reset.
download quick shortcut maker, search for lte, select com.test.LTEfunctionality, scroll down to LTE APN Setting, Edit APN @heepo18