Related
I'm trying to get Straight Talk working with this Bionic. Could someone help?
Not sure but...
I used to be a Verizon Wireless agent (Straight Talk piggy backs on their network.) If I remember right straight talk/net10/verizon's own prepaid phones are limited to 3G devices only. Policies may have changed, or I could potentially be wrong but I am going to guess that you won't be able to get it working on their network because they won't be able to issue you a compatible SIM
You have to edit the build.prop and create a local.prop (it probably doesn't exist). I recently put SlimKat 4.4.4 on my friend's Bionic, and got it working well with Straight Talk (Voice, MMS, Data, etc). Just edit build.prop with:
persist.radio.ap.phonetype=1
ro.mot.phonemode.vzw4gphone=0
ro.mot.phonemode.vzwglobalphone=1
ro.telephony.default_network=3
ro.telephony.gsm-routes-us-smsc=0
telephony.lteOnCdmaDevice=0
Create a local.prop file and add:
ro.telephony.ril.v3=signalstrength
Move this into /data/
Next, go into system/etc/ and get your apns-conf.xml file and delete all the entries you don't need, keeping only the one relevant to Straight Talk. In my friend's case:
Code:
<apns version="7">
<apn carrier="StraightTalk ATT" mcc="310" mnc="410" apn="tfdata" port="80" mmsc="http://mms-tf.net" mmsproxy="mms3.tracfone.com" mmsport="80" type="default,supl,mms,hipri" />
</apns>
For the novices, to do this last part, you'll need a file manager like ES that can utilize root permissions after enabling in settings.
After this, any 4.3 or 4.4 ROM should let you edit APN settings, etc. You may need to set your radio to GSM (auto PRL) by going into your dialer and hitting *#*#4636#*#* and going into Phone Information then down to network type or whatever. I don't have a Motorola phone in front of me If that doesn't work, I've noticed GSM/WCDMA (auto PRL) works for some.
Good luck
Edit: I forgot one crucial thing you must do. You have to use RadioComm to enable GSM/UMTS bands. You can find it with Google. The version I used is 11.12.2. You'll either have a green or purple light on the right side, signifying that your phone is connected. It should show up in the status bar too. Steps:
Ensure you have correct Motorola drivers and that device shows up in device manager (You may need to use Google USB driver, as this has worked with some Motorola phones for me)
Ensure that USB is in PC Tools mode
In Radiocomm go to MA->COMMON->MDM 6x00
Go to the FTM Common1 tab, and wait for purple or green light on side
Toward the top of NVAccess you'll see a select box. Scroll to NV item 1877 NV_RF_BC_CONFIG_I
Click on read value
Once read, replace the first 8 bytes with: 8703E80400000200 (back up original as a .txt file or something)
Write the new value to the device and reboot
There's also a flashable zip that does this, but I've not tested it. Use at your own risk:
http://forum.xda-developers.com/attachment.php?attachmentid=1048524&d=1336485537
All of the information I presented is from others, but I can't remember all the threads I got this from. I take no responsibility for any bricked phones or the like.
shadolis said:
You have to edit the build.prop and create a local.prop (it probably doesn't exist). I recently put SlimKat 4.4.4 on my friend's Bionic, and got it working well with Straight Talk (Voice, MMS, Data, etc). Just edit build.prop with:
persist.radio.ap.phonetype=1
ro.mot.phonemode.vzw4gphone=0
ro.mot.phonemode.vzwglobalphone=1
ro.telephony.default_network=3
ro.telephony.gsm-routes-us-smsc=0
telephony.lteOnCdmaDevice=0
Create a local.prop file and add:
ro.telephony.ril.v3=signalstrength
Move this into /data/
Next, go into system/etc/ and get your apns-conf.xml file and delete all the entries you don't need, keeping only the one relevant to Straight Talk. In my friend's case:
Code:
<apns version="7">
<apn carrier="StraightTalk ATT" mcc="310" mnc="410" apn="tfdata" port="80" mmsc="http://mms-tf.net" mmsproxy="mms3.tracfone.com" mmsport="80" type="default,supl,mms,hipri" />
</apns>
For the novices, to do this last part, you'll need a file manager like ES that can utilize root permissions after enabling in settings.
After this, any 4.3 or 4.4 ROM should let you edit APN settings, etc. You may need to set your radio to GSM (auto PRL) by going into your dialer and hitting *#*#4636#*#* and going into Phone Information then down to network type or whatever. I don't have a Motorola phone in front of me If that doesn't work, I've noticed GSM/WCDMA (auto PRL) works for some.
Good luck
Edit: I forgot one crucial thing you must do. You have to use RadioComm to enable GSM/UMTS bands. You can find it with Google. The version I used is 11.12.2. You'll either have a green or purple light on the right side, signifying that your phone is connected. It should show up in the status bar too. Steps:
Ensure you have correct Motorola drivers and that device shows up in device manager (You may need to use Google USB driver, as this has worked with some Motorola phones for me)
Ensure that USB is in PC Tools mode
In Radiocomm go to MA->COMMON->MDM 6x00
Go to the FTM Common1 tab, and wait for purple or green light on side
Toward the top of NVAccess you'll see a select box. Scroll to NV item 1877 NV_RF_BC_CONFIG_I
Click on read value
Once read, replace the first 8 bytes with: 8703E80400000200 (back up original as a .txt file or something)
Write the new value to the device and reboot
There's also a flashable zip that does this, but I've not tested it. Use at your own risk:
http://forum.xda-developers.com/attachment.php?attachmentid=1048524&d=1336485537
All of the information I presented is from others, but I can't remember all the threads I got this from. I take no responsibility for any bricked phones or the like.
Click to expand...
Click to collapse
I'm not sure what the deal is - I'm trying to do the same thing, but with T-Mobile US rather than Straight Talk... Should work fine, but when I make the above changes, I get com.android.phone stopped working over and over. If I follow every step above, but instead of "ro.telephony.default_network=3", I use "ro.telephony.default_network=7", it works fine, I can make calls on T-Mobile, but the signal strength is horrible. I can be where I normally have full 2G/3G signal, and the Bionic barely has one bar if anything. Most of the time it just says "No Service" unless I step outside, whereas my other T-mobile specific phones have no problems with the signal anywhere in my house.
What might I be doing wrong here? I just bought the Bionic as a backup as I've been told it works fine with GSM when you do the above tweaks, but I'm finding it's real-world operability on GSM to be less than stellar.
gully52 said:
I'm not sure what the deal is - I'm trying to do the same thing, but with T-Mobile US rather than Straight Talk... Should work fine, but when I make the above changes, I get com.android.phone stopped working over and over. If I follow every step above, but instead of "ro.telephony.default_network=3", I use "ro.telephony.default_network=7", it works fine, I can make calls on T-Mobile, but the signal strength is horrible. I can be where I normally have full 2G/3G signal, and the Bionic barely has one bar if anything. Most of the time it just says "No Service" unless I step outside, whereas my other T-mobile specific phones have no problems with the signal anywhere in my house.
What might I be doing wrong here? I just bought the Bionic as a backup as I've been told it works fine with GSM when you do the above tweaks, but I'm finding it's real-world operability on GSM to be less than stellar.
Click to expand...
Click to collapse
What rom are you using? I've used this technique on a ridiculous number of bionic roms to make them GSM so hopefully I can help, it's worth noting that I do not create a localprop. I found that most roms have the "ro.telephony.ril.v3" line in the default.prop and I can simply amend them by adding "signalstrength," (note the comma to include the end of the quotes) at the beginning of the entry. You might try wiping the rom and starting over but skip the step changing the radio with the *#*#4636#*#* part
---------- Post added at 11:15 AM ---------- Previous post was at 11:10 AM ----------
shadolis said:
For the novices, to do this last part, you'll need a file manager like ES that can utilize root permissions after enabling in settings.
After this, any 4.3 or 4.4 ROM should let you edit APN settings, etc. You may need to set your radio to GSM (auto PRL) by going into your dialer and hitting *#*#4636#*#* and going into Phone Information then down to network type or whatever. I don't have a Motorola phone in front of me If that doesn't work, I've noticed GSM/WCDMA (auto PRL) works for some.
Click to expand...
Click to collapse
The settings adjusted in the default.prop permit that you do not need to change the radio. since i started using these particular settings, I've never had to change it and additionally found it to be commonly problematic. I also found that MOST roms do not need you to add the straight talk APN. Cyanogen and Paranoid, I know for fact include them. When you boot the phone for the first time you'll need to go into the settings and select the appropriate Straight Talk APN (mine is the MVNO one).
HW-A vs. HW-C
Plasmaleto said:
What rom are you using? I've used this technique on a ridiculous number of bionic roms to make them GSM so hopefully I can help, it's worth noting that I do not create a localprop. I found that most roms have the "ro.telephony.ril.v3" line in the default.prop and I can simply amend them by adding "signalstrength," (note the comma to include the end of the quotes) at the beginning of the entry. You might try wiping the rom and starting over but skip the step changing the radio with the *#*#4636#*#* part.
Click to expand...
Click to collapse
I've tried with stock JB, as well as CM11 M11 in Slot 1. I've wiped and started over more times than I can count.
What do you mean that you add "signalstrength," at the beginning of the ro.telephony.ril.v3 entry? It's my understanding that the entry should be "ro.telephony.ril.v3=signalstrength". I don't understand what you mean by putting signalstrength at the beginning of the entry. Also, what's up with that comma?
Then again, all my difficulties could be in the fact that I have a "HW C" Bionic. Just got a "HW A" model, and will be tinkering with that soon too. It actually came with original Stock 5.5.886 Gingerbread ROM... Right now, I plan on upgrading to the 232 ICS leak (so I can go back to GB if needed), and see if I can get GSM working on it a little better.
How would you recommend I proceed with a bone stock ICS 6.7.232 ROM?
Thanks a BUNCH for your reply on this old (but fun to tinker with) phone!
Brian
gully52 said:
I've tried with stock JB, as well as CM11 M11 in Slot 1. I've wiped and started over more times than I can count.
What do you mean that you add "signalstrength," at the beginning of the ro.telephony.ril.v3 entry? It's my understanding that the entry should be "ro.telephony.ril.v3=signalstrength". I don't understand what you mean by putting signalstrength at the beginning of the entry. Also, what's up with that comma?
Then again, all my difficulties could be in the fact that I have a "HW C" Bionic. Just got a "HW A" model, and will be tinkering with that soon too. It actually came with original Stock 5.5.886 Gingerbread ROM... Right now, I plan on upgrading to the 232 ICS leak (so I can go back to GB if needed), and see if I can get GSM working on it a little better.
How would you recommend I proceed with a bone stock ICS 6.7.232 ROM?
Thanks a BUNCH for your reply on this old (but fun to tinker with) phone!
Brian
Click to expand...
Click to collapse
Ahhhh yes, i believe you found the root of the issue. The method that was used for Ginger Bread was slightly different which almost certainly why the above may not be working for you. I practically forgot about that, I upgraded mine years ago. I've grown so fond of the bionic I'm on my third you can buy them second hand for like $50 to $100. So i Just keep fixing/repairing them haha.
I'm gonna dig through some old book marks and tutorials and find out how I upgraded mine originally and I'll post them up here for you. The timing of this coming up is almost bizarre. I'm actually in the middle of working on a website that lets you point it at a rom, it downloads it, modifies it for GSM, then provides you a link to download it. I'd actually like to make it an Android app because when I download rom updates, I have to make them GSM compatible first.
Plasmaleto said:
Ahhhh yes, i believe you found the root of the issue. The method that was used for Ginger Bread was slightly different which almost certainly why the above may not be working for you.
Click to expand...
Click to collapse
As I mentioned above, I just received the phone that's still running Gingerbread on Rev. A Hardware. Haven't even tried to start messing with that phone yet.
The original phone I was having trouble with, prompting the post to this thread, was running stock Jelly Bean on Rev. C hardware.
You say you're on your 3rd Bionic because you like them so much! They are a rugged and capable phone, for sure. What carrier have you been using it with? I've been attempting plain old T-Mobile, but assume making it work for Straight Talk would make it work for T-Mobile as well, aside from APN settings.
How's your signal strength on your bionic compared to an official GSM phone, both for calls and data?
gully52 said:
As I mentioned above, I just received the phone that's still running Gingerbread on Rev. A Hardware. Haven't even tried to start messing with that phone yet.
The original phone I was having trouble with, prompting the post to this thread, was running stock Jelly Bean on Rev. C hardware.
You say you're on your 3rd Bionic because you like them so much! They are a rugged and capable phone, for sure. What carrier have you been using it with? I've been attempting plain old T-Mobile, but assume making it work for Straight Talk would make it work for T-Mobile as well, aside from APN settings.
How's your signal strength on your bionic compared to an official GSM phone, both for calls and data?
Click to expand...
Click to collapse
The #1 reason I continue using bionics is because of how cheap parts are if I need them (like when I drop them and break the screen ) and accessories. Like I have several docks that I've bought for like $7 a piece (retail was like ridiculous $40 or something but just for a dock $7 is dirt cheap). I even got the lapdock that I picked up on ebay for $50. You can't beat it. That thing is awesome. Add to it that you can get a micro HDMI to HDMI cable, hook this thing up to a TV and use it as an entertainment player sorta like a roku and it just keeps getting better. You can then use another android device and run AllCast to turn it into a chromecast wannabe. I've just found endless fun, with this particular model of android.
I personally utilize Straight Talk. No BS, $45 every month, no surprises. Love it. As far as GSM signal goes, it's like any other GSM phone!
gully52 said:
As I mentioned above, I just received the phone that's still running Gingerbread on Rev. A Hardware. Haven't even tried to start messing with that phone yet.
The original phone I was having trouble with, prompting the post to this thread, was running stock Jelly Bean on Rev. C hardware.
You say you're on your 3rd Bionic because you like them so much! They are a rugged and capable phone, for sure. What carrier have you been using it with? I've been attempting plain old T-Mobile, but assume making it work for Straight Talk would make it work for T-Mobile as well, aside from APN settings.
How's your signal strength on your bionic compared to an official GSM phone, both for calls and data?
Click to expand...
Click to collapse
So here's what I would do
1) Update to Jelly Bean (you can do this with official Motorola OTA updates or more info here http://forum.xda-developers.com/showthread.php?t=2235946)
2) Power on phone and edit the hex values with Radiocomm see: post 29/30 http://forum.xda-developers.com/showthread.php?t=1297714&page=3
- - Be PARTICULARLY picky about this part, I found this to be extraordinarily difficult time and time again. Even though I've done it at least 5 or 6 times, I felt like it never went exactly as it should. After changing the value, you might even disconnect, reconnect, and make sure the hex value has changed.
3) Root the phone (this guide seems a little indepth but it works very well once you get it down compared to other methods http://forum.xda-developers.com/showthread.php?t=2256439)
4) At this point you have a choice of either modifying stock rom or use custom ROMS. I HIGHLY recommend custom ROMS, the stock ROM is highly bloated. I have found that AOSP based ROMS like Cyanogen or Paranoid (personal recommendation), work considerably better in general in addition to being more suited for GSM usage.
Should you choose custom roms then here's what I would do next, I have found this is the easiest way to consistently use GSM:
a) You'll want to install SafeStrap or something similar (I've only got experience with SafeStrap personally and understand the developer has suspended his project from future updates but still works for me) http://forum.xda-developers.com/showthread.php?t=1391875
b) Once you have that, you can download almost any ROM, extract it to a folder, change the build.prop with the proper GSM configuration you listed, find the line for "ro.telephony.ril.v3" inside build.prop and add "signalstrength," (including punctuation) immediately after the equal sign. Don't bother with local.prop.
c) Re-zip it just like it was before, then install the ROM in a SafeStrap slot (probably want to add GApps)
d) Once it's booted, you can connect to wifi to setup the Google Acct and whatnot, then (this part varies slightly depending on the rom but AOSP roms are all pretty similar) go into the Settings: Mobile Networks: Access Point Names: Select the carrier of your choice (there's literally hundreds preloaded)
Lot of detail but a lot of specifics left out, if I can expound on anything please let me know which areas are too vague.
UPDATE: Here's the ROM I'm currently using. I literally install this thing with safe strap along with the pa gapps modular micro and just use it. No editing files, no thing. Just use it.
Paranoid Android Legacy Original - http://get.aospa.co/legacy/targa
Paranoid Android Legacy GSM Ready - http://dailen.bitnamiapp.com/roms/pa_targa-4.6-BETA5-20141022.GSM.zip
PA Gapps Modular Micro - https://www.androidfilehost.com/?w=files&flid=15801
Above and Beyond
Plasmaleto said:
Here's the ROM I'm currently using. I literally install this thing with safe strap along with the pa gapps modular micro and just use it. No editing files, no thing. Just use it.
Click to expand...
Click to collapse
Wow! This is above and beyond! Truly thankful for this guide. I'm fairly familiar with ROMs in general and putting Safestrap on the Bionic... but the fact that you hand-edited the PA ROM and provided a link... I deserve not such service!
Will attempt a flash tonight and let you know. Still plan to keep stock 232 ICS leak, since it will never get used once PA is installed! Will reply tomorrow if I get everything working!
Thanks again!
---------- Post added at 11:05 PM ---------- Previous post was at 10:28 PM ----------
Plasmaleto said:
a) You'll want to install SafeStrap or something similar (I've only got experience with SafeStrap personally and understand the developer has suspended his project from future updates but still works for me)
Click to expand...
Click to collapse
What version of Safestrap are you running? I installed 3.73, and once installed, my stock ICS 232 gets stuck on the boot animation forever. FXZ back to 905 and then update to 232 to get back into ICS...
I dunno, maybe I'm making a big deal out of wanting to keep the path back to gingerbread. I should probably just bite the bullet and go up to stock JB first as you mentioned...
gully52 said:
Wow! This is above and beyond! Truly thankful for this guide. I'm fairly familiar with ROMs in general and putting Safestrap on the Bionic... but the fact that you hand-edited the PA ROM and provided a link... I deserve not such service!
Will attempt a flash tonight and let you know. Still plan to keep stock 232 ICS leak, since it will never get used once PA is installed! Will reply tomorrow if I get everything working!
Thanks again!
---------- Post added at 11:05 PM ---------- Previous post was at 10:28 PM ----------
What version of Safestrap are you running? I installed 3.73, and once installed, my stock ICS 232 gets stuck on the boot animation forever. FXZ back to 905 and then update to 232 to get back into ICS...
I dunno, maybe I'm making a big deal out of wanting to keep the path back to gingerbread. I should probably just bite the bullet and go up to stock JB first as you mentioned...
Click to expand...
Click to collapse
For some reason I distinctly remember their being a link between the stock rom, and those installed in rom slots. I'm currently using 3.7.2. I also THINK I recall that a while back when I wanted to use SafeStrap 3.5 I only could do so if I upgrade to JB. I can't find any documentation to back these up so take it with a grain of salt. Personally, I'm one who upgrades and never looks back so maybe I'm just biased haha
(P.S. your eyes do not deceive you, my username changed from Plasmaleto to Dailen, special request made to XDA webmasters!)
I've made a tool to convert Bionic ROMS to GSM ready if anyone would like to give it a shot I'm likely to move or relocate this at some point btw
http://dailen.bitnamiapp.com/roms/convert.php
Relocated:
http://dailen.net/roms/convert.php
Dailen said:
For some reason I distinctly remember their being a link between the stock rom, and those installed in rom slots. I'm currently using 3.7.2. I also THINK I recall that a while back when I wanted to use SafeStrap 3.5 I only could do so if I upgrade to JB. I can't find any documentation to back these up so take it with a grain of salt. Personally, I'm one who upgrades and never looks back so maybe I'm just biased haha
(P.S. your eyes do not deceive you, my username changed from Plasmaleto to Dailen, special request made to XDA webmasters!)
Click to expand...
Click to collapse
Dailen (the artist formerly known as Plasmaleto),
I took the plunge and updated to stock JB, rooted, installed Safestrap 3.73, then installed your pre-GSM-configured version of Paranoid ROM. Rebooted, connected to wifi, got everything setup. Powered down, inserted my T-Mobile SIM card, and voila! Full HSPA signal! 5.01mb/sec download, 1.22mb/sec upload. Outgoing calls work! Incoming calls work! Data works! Super cool! Thanks again!
Congrats! Glad that worked for ya!
Dailen said:
I've made a tool to convert Bionic ROMS to GSM ready if anyone would like to give it a shot I'm likely to move or relocate this at some point btw
http://dailen.bitnamiapp.com/roms/convert.php
Click to expand...
Click to collapse
Just trying your tool on the CM11 M11 release. Will let you know how it works. Do you know, if I came across some older ROMs... JB 4.2/4.3, would your tool work for them as well?
Also, since you're a Bionic nut, I don't suppose you have a version of CarbonROM sitting around from before they dropped support for the Bionic? I contacted them and was surprised to learn that they have absolutely ZERO archive of old version downloads.
gully52 said:
Just trying your tool on the CM11 M11 release. Will let you know how it works. Do you know, if I came across some older ROMs... JB 4.2/4.3, would your tool work for them as well?
Also, since you're a Bionic nut, I don't suppose you have a version of CarbonROM sitting around from before they dropped support for the Bionic? I contacted them and was surprised to learn that they have absolutely ZERO archive of old version downloads.
Click to expand...
Click to collapse
Well in theory the answer is yes. The way my script works, it changes only what it finds. If you can send me a link to one of the roms you'd like to try I'd be happy to take a look at the build.prop and tell you for sure if anything is missing.
Also, I don't recall having the carbonrom sitting around anywhere but I see their github still has the source posted, I suppose I could always try compiling for you. I got a couple ubuntu systems running I could put to some good use. Might take a few days.
Give it a shot!
Going to give this a shot right now on a friends Bionic. Unfortunately have to wait a few days for the Straight Talk Sim card to arrive. I'll report back.
Think I screwed up!
Dailen said:
Congrats! Glad that worked for ya!
Click to expand...
Click to collapse
I believe I have screwed up. I tried the radiocomm program last night and everything was green for me but I didn't write to the phone. I installed the pa_targa-4.6-BETA5-20141022.GSM.zip file, and the Gapps for that ROM. When I tried to go into Radiocomm again, it comes up red when I try to read (1877). Do I still need to do that or will the phone be good to go once I pop in an AT&T sim card? Thanks, Howie
meandg5 said:
I believe I have screwed up. I tried the radiocomm program last night and everything was green for me but I didn't write to the phone. I installed the pa_targa-4.6-BETA5-20141022.GSM.zip file, and the Gapps for that ROM. When I tried to go into Radiocomm again, it comes up red when I try to read (1877). Do I still need to do that or will the phone be good to go once I pop in an AT&T sim card? Thanks, Howie
Click to expand...
Click to collapse
Radiocomm is EXTREMELY particular and I swear it only works 3 out of 5 times. I seem to recall that when I did it, it wasn't "writing" the settings properly and I had to change the USB connection type. If my current setup is any indicator, it was set to "PST USB Driver". I also recall that one time I uninstalled the bionic drivers and reinstalled them and it started working.
It's probably worth mentioning that I would connect to your phone in Radiocomm while in the stock rom if possible. There's no telling if there's some quirky specific USB driver in the rom that Radiocomm depends on. When in doubt, try a different machine. Be sure to get the Bionic USB drivers working 100% (meaning no device errors in device manager) prior to doing the radiocomm stuff.
So I bought a Nexus 6 on Amazon when they were on sale. I used wugfresh NRT and unlocked it, rooted it (no custom recovery) and then updated the files for tethering. Its activated on Verizon if that matters-
I got an update today, I was running LMY48I and I choose the file to update to LMY48M. I used the NRT and sideloaded it, and after I was done it still shows I have LMY48I, and a few hours later the OTA shows up at in my notifications again.
What am I doing wrong?
caecusscius said:
So I bought a Nexus 6 on Amazon when they were on sale. I used wugfresh NRT and unlocked it, rooted it (no custom recovery) and then updated the files for tethering. Its activated on Verizon if that matters-
I got an update today, I was running LMY48I and I choose the file to update to LMY48M. I used the NRT and sideloaded it, and after I was done it still shows I have LMY48I, and a few hours later the OTA shows up at in my notifications again.
What am I doing wrong?
Click to expand...
Click to collapse
what are you doing wrong? oh, thats an easy one..! you havent done any research into the phone that you are using. i bet you probably used a toolkit to root it as well. anyways, for the 20 billionth time ill repeat it. you can not take an ota if you are not completely, 100% stock. and root is not stock. on top if that, many completely stock nexus 6 cant take updates as well, if any system files have changed.
simms22 said:
what are you doing wrong? oh, thats an easy one..! you havent done any research into the phone that you are using. i bet you probably used a toolkit to root it as well. anyways, for the 20 billionth time ill repeat it. you can not take an ota if you are not completely, 100% stock. and root is not stock. on top if that, many completely stock nexus 6 cant take updates as well, if any system files have changed.
Click to expand...
Click to collapse
Your help is awful, condescending and rude. Maybe its the effect of the internet, but that is how it sounds. I did root using a toolkit- and I used the same toolkit to sideload the OTA. I assumed that I could do that since that is what the 40 threads I read about told me to do. I have a job and a wife and kids, I don't have the time to be a full time developer for my phone just to enjoy it. ALL I needed root for, was to enable tethering- otherwise I'm happy with stock android.
I will take one thing from what you did write and assume that because I edited the build.prop to enable tethering I will not be able to sideload OTA's either? IF I can't, thats fine with me- Can you tell me how to disable the OTAs?
Anyone else know how to read a question and offer an answer without insults?
I did find out how to hide the OTA notification- it was so easy I feel dumb- but not having used a 5.x android before this one I couldn't have known it.
caecusscius said:
Your help is awful, condescending and rude. Maybe its the effect of the internet, but that is how it sounds. I did root using a toolkit- and I used the same toolkit to sideload the OTA. I assumed that I could do that since that is what the 40 threads I read about told me to do. I have a job and a wife and kids, I don't have the time to be a full time developer for my phone just to enjoy it. ALL I needed root for, was to enable tethering- otherwise I'm happy with stock android.
I will take one thing from what you did write and assume that because I edited the build.prop to enable tethering I will not be able to sideload OTA's either? IF I can't, thats fine with me- Can you tell me how to disable the OTAs?
Anyone else know how to read a question and offer an answer without insults?
Click to expand...
Click to collapse
But his answer is 100% correct. If you change any system file cannot OTA. Don't kill the messenger. No OTA with root, Kernel, change build.prop. Or custom recovery. If change any file no OTA.
caecusscius said:
Your help is awful, condescending and rude. Maybe its the effect of the internet, but that is how it sounds. I did root using a toolkit- and I used the same toolkit to sideload the OTA. I assumed that I could do that since that is what the 40 threads I read about told me to do. I have a job and a wife and kids, I don't have the time to be a full time developer for my phone just to enjoy it. ALL I needed root for, was to enable tethering- otherwise I'm happy with stock android.
I will take one thing from what you did write and assume that because I edited the build.prop to enable tethering I will not be able to sideload OTA's either? IF I can't, thats fine with me- Can you tell me how to disable the OTAs?
Anyone else know how to read a question and offer an answer without insults?
Click to expand...
Click to collapse
i apologize, i was a little ruder than i meant to be. but not much, just a little. and i bet that you didnt learn much about the rooting process using the toolkit? anyways, before ever even rooting the phone, you have to do some research about it. or you wouldnt be asking such a basic question. heck, search can a rooted nexus 6 take an ota on google. one search, its all it really needs to take. anyways, it doesnt matter that you have a job, a wife, kids, this applies to everyone, do some research. im not a youngster myself, lol.
Obviously you read only the first sentences of everything I write... its Ok I notice you are from Brooklyn- I can forgive you for not using southern manners that I am accustomed to. I am not trying to take an OTA- I was trying to sideload it using ADB. I know I can't take it normally.
I'm currently downloading the system.img from https://developers.google.com/android/nexus/images
I'm going to try and flash just the system.img and cache.img so I can update to the newest version without going back to stock.
I also found out how to hide the OTA update
caecusscius said:
Your help is awful, condescending and rude. Maybe its the effect of the internet, but that is how it sounds. I did root using a toolkit- and I used the same toolkit to sideload the OTA. I assumed that I could do that since that is what the 40 threads I read about told me to do. I have a job and a wife and kids, I don't have the time to be a full time developer for my phone just to enjoy it. ALL I needed root for, was to enable tethering- otherwise I'm happy with stock android.
I will take one thing from what you did write and assume that because I edited the build.prop to enable tethering I will not be able to sideload OTA's either? IF I can't, thats fine with me- Can you tell me how to disable the OTAs?
Anyone else know how to read a question and offer an answer without insults?
I did find out how to hide the OTA notification- it was so easy I feel dumb- but not having used a 5.x android before this one I couldn't have known it.
Click to expand...
Click to collapse
As someone with a job, a wife and kid and I can assure you, nothing is more frustrating than to do the research after something happened, phone not working while waiting for calls or whatever other inconvenience.
What simms22 tried to convey is "know thy phone".
If you look for how to "root your nexus" you'll see how simple the pRocess is and you might feel better using the tools needed, rather than trusting some obscure tool that could always come with even more payloads.
Simms22 is someone who helped hundreds after they got themselves stuck after using root kits, his frustration I think lies more in the continued pushing of root tool kits for phones that don't need it.
The tone you took personal was directed at the root kits, at them being allowed, as they create just as much problems as they promise to fix.
Know thy Nexus, it's really a great thing.
Sorry if the reply is maybe a little long, must be all this not posting in a while
Daniel
caecusscius said:
Obviously you read only the first sentences of everything I write... its Ok I notice you are from Brooklyn- I can forgive you for not using southern manners that I am accustomed to. I am not trying to take an OTA- I was trying to sideload it using ADB. I know I can't take it normally.
I'm currently downloading the system.img from https://developers.google.com/android/nexus/images
I'm going to try and flash just the system.img and cache.img so I can update to the newest version without going back to stock.
I also found out how to hide the OTA update
Click to expand...
Click to collapse
now see, you made me smile, thank you
btw.. i was born in Ukraine(but Russian). left ehen i was two, came to the states when three, in 1975. lived in and outside cincinnati most my life. moved to Brooklyn 10 years ago
---------- Post added at 11:55 PM ---------- Previous post was at 11:53 PM ----------
morfic said:
As someone with a job, a wife and kid and I can assure you, nothing is more frustrating than to do the research after something happened, phone not working while waiting for calls or whatever other inconvenience.
What simms22 tried to convey is "know thy phone".
If you look for how to "root your nexus" you'll see how simple the pRocess is and you might feel better using the tools needed, rather than trusting some obscure tool that could always come with even more payloads.
Simms22 is someone who helped hundreds after they got themselves stuck after using root kits, his frustration I think lies more in the continued pushing of root tool kits for phones that don't need it.
The tone you took personal was directed at the root kits, at them being allowed, as they create just as much problems as they promise to fix.
Know thy Nexus, it's really a great thing.
Sorry if the reply is maybe a little long, must be all this not posting in a while
Daniel
Click to expand...
Click to collapse
oh, my, god.. its morfic!
Well, Hopefully I didn't mess things up using the toolkit instead of doing it the other ways: I know its not much harder to do it other ways, I'm just pressed for time. A few things about my situation:
I live in the country of Texas where I don't have ANY internet service providers. I have however, an old unlimited data plan from Verizon and a pretty good signal strength that I've boosted with a custom built amplifier (we also have metal roof that blocks a lot of signal otherwise)
I NEED internet so I don't become a savage. My phone tethering the internet is my PRIMARY way of having internet. Its very important that I can tether my unlimited plan...
After flashing the system.img and the radio img it booted back up no problems and I had lost root- I re-rooted it and changed the build.prop to allow tethering.
However- I dun F&*ked up somewhere, because now I can't seem to get LTE and my service is terribad. I'm assuming it was flashing the radios? Maybe because its verizon crap I need to do something else...
This has been a 5 hour ordeal (I watched tv during it all...) but now my phone doesn't quite do what i need it to do.
caecusscius said:
Well, Hopefully I didn't mess things up using the toolkit instead of doing it the other ways: I know its not much harder to do it other ways, I'm just pressed for time. A few things about my situation:
I live in the country of Texas where I don't have ANY internet service providers. I have however, an old unlimited data plan from Verizon and a pretty good signal strength that I've boosted with a custom built amplifier (we also have metal roof that blocks a lot of signal otherwise)
I NEED internet so I don't become a savage. My phone tethering the internet is my PRIMARY way of having internet. Its very important that I can tether my unlimited plan...
After flashing the system.img and the radio img it booted back up no problems and I had lost root- I re-rooted it and changed the build.prop to allow tethering.
However- I dun F&*ked up somewhere, because now I can't seem to get LTE and my service is terribad. I'm assuming it was flashing the radios? Maybe because its verizon crap I need to do something else...
This has been a 5 hour ordeal (I watched tv during it all...) but now my phone doesn't quite do what i need it to do.
Click to expand...
Click to collapse
there are many other nexus 6 radios, you can try sny of them. they will all work. you can try to find which one is best for you.
simms22 said:
there are many other nexus 6 radios, you can try sny of them. they will all work. you can try to find which one is best for you.
Click to expand...
Click to collapse
Link?
caecusscius said:
Link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-modem-collection-t2969380
Last night before bed, the phone appeared to be working fine: it was tethering and data was working. This morning I find that I can't call out or receive calls. I tried lots of things to fix this: none worked. Any ideas?
It appears to be stuck hanging up...
caecusscius said:
Last night before bed, the phone appeared to be working fine: it was tethering and data was working. This morning I find that I can't call out or receive calls. I tried lots of things to fix this: none worked. Any ideas?
It appears to be stuck hanging up...
Click to expand...
Click to collapse
have you tried a reboot?
Yes, and I tried a few other things. Right now, I've factory reset the device and I will re-root it and change build.prop I was trying to NOT have to do that. Right now its back to stock and not rooted... but it makes calls and is updated to the 48M build.
I was trying to enable VOLTE and HD calling which appears to be what messed it up probably (although flashing radios might have done it... )
I used the *#*#4636#*#* to check it and it was all sorts of messed up and not connecting to any towers. I'm in my classroom lab and it was making all the speakers go crazy... something was badly messed up
Mine did it last night. I had to wipe dalvik and cache in TWRP to get it back. Has happened occasionally since 5.0. The one I call can hear me. I don't hear them or the phone ringing. Completely dead on my end. VOLTE was disabled in settings.
caecusscius said:
Obviously you read only the first sentences of everything I write... its Ok I notice you are from Brooklyn- I can forgive you for not using southern manners that I am accustomed to. I am not trying to take an OTA- I was trying to sideload it using ADB. I know I can't take it normally.
I'm currently downloading the system.img from https://developers.google.com/android/nexus/images
I'm going to try and flash just the system.img and cache.img so I can update to the newest version without going back to stock.
I also found out how to hide the OTA update
Click to expand...
Click to collapse
You keep referencing that you found how to disable the ota notification - do tell. This would help.
Sent from my Nexus 6 using Tapatalk
voyageurs60 said:
You keep referencing that you found how to disable the ota notification - do tell. This would help.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
When the notification appears, long press it in your drop down status bar. Then click "app info", then untick the box for " show notifications ".
I looked around and did not see this. Now that the phone is opened up, if there an easy way to just enable the wireless tether?
I've had WiFi tethering since I bought the phone right after it came out, I'm not sure why others don't have the option. I found it in Settings -> More -> Tethering & Mobile Hotspot. I've had this on KK 4.4.4 as well as LP 5.1. Is it because it's only available with non grandfathered unlimited data devices (I think they got rid of that recently too)?
Unlimited can tether the same way, but we have to pay $20 a month. Xposed module xtether seems to work. It let me turn tether on without the message that I need to upgrade. Did not connect and test it yet.
smooth781 said:
I looked around and did not see this. Now that the phone is opened up, if there an easy way to just enable the wireless tether?
Click to expand...
Click to collapse
Just flash CF's 1.1A ROM..it has wireless tether enabled where you can turn on in the stock app. No need for a separate xposed app.
crowax said:
Unlimited can tether the same way, but we have to pay $20 a month. Xposed module xtether seems to work. It let me turn tether on without the message that I need to upgrade. Did not connect and test it yet.
Click to expand...
Click to collapse
Heh, ok. I've got their UNLIMITED TALK & TEXT 2GB plan 75$ and it incudes hotspot/tethering.
Anyone care to share what to edit to get WiFi tethering? Flashing a different ROM is not really what I wanna do right now, would like to just do it on my newly unlocked stock rom Turbo
Anyone care to share what to edit to get WiFi tethering? Flashing a different ROM is not really what I wanna do right now, would like to just do it on my newly unlocked stock rom Turbo
I'm interested in the WiFi tether as well.
Install xposed, look for xtether, I've used it all day and 0 issues.
Alternatively, I think you can add the following line to /system/build.prop:
net.tethering.noprovisioning=true
Batttie said:
Install xposed, look for xtether, I've used it all day and 0 issues.
Click to expand...
Click to collapse
+1 for xTether. It works great for me. I used it all day to play on my tablet while the wife was Black Friday shopping.
acinad said:
+1 for xTether. It works great for me. I used it all day to play on my tablet while the wife was Black Friday shopping.
Click to expand...
Click to collapse
I did this and am having no luck
So I need a little help please. I have my phone unlocked, rooted, twrp installed, made a backup, and now SU updated from reading on here. I have a UDP and want my wifi tether to work without installing custom roms. I'm happy at this point with what stock does. I'm not the greatest with this, but I am not afraid to read. So to my problem. I'm stuck with the xpose thing. I just don't see or get what needs to be done to install it. I read I need to flash something first? But i'm not sure why. I looked a little at just adding the line in the build file but was not sure if that would still work or if that was old news. Please someone point in the right direction.
Thanks.
smooth781 said:
So I need a little help please. I have my phone unlocked, rooted, twrp installed, made a backup, and now SU updated from reading on here. I have a UDP and want my wifi tether to work without installing custom roms. I'm happy at this point with what stock does. I'm not the greatest with this, but I am not afraid to read. So to my problem. I'm stuck with the xpose thing. I just don't see or get what needs to be done to install it. I read I need to flash something first? But i'm not sure why. I looked a little at just adding the line in the build file but was not sure if that would still work or if that was old news. Please someone point in the right direction.
Thanks.
Click to expand...
Click to collapse
Use a file manager with root capabilities such as solid explorer, amaze file manager or whatever to edit the build.prop file. It's in /system/. Add 'net.tethering.noprovisioning=true' without quotes and reboot. Tethering within the settings app should now work.
Thanks for the reply. I added it at the end of the file. Rebooted and turned the tether on. no messages. I think I'm good to go. Again Thanks for the help.
Thanks for the tip on the build prop edit. I've been trying to figure out how to do this for a bit now. Just to confirm, this method will work on the latest version of 5.1 so long as I'm rooted and unlocked, correct?
It has worked great for me. I do not load in ROM'S or make a lot of other changes to my phone. Paying the 25.00 is just math for me. I was giving 30.00 a month to Verizon to pay for tethering. Now I don't. So in 1 month I come out ahead. You need your boot loader unlocked, and will need to pay for that 1 time.
Will this tether-unlock be "visible" to VZ and cause me issues under my unlimited plan? (I presume by smooth's reply that he hasn't had this problem, but I want to be sure)
Just read that Three is discontinuing it's WiFi calling app as most phones have this as standard now. I have no reception in my flat so this has been a lifesaver. I have figured out how to activate the volte and WiFi calling toggles but only the volte seems to work (I get an icon when on 4g). Has anyone been able to get this to work on any UK network?
Eggstones said:
Just read that Three is discontinuing it's WiFi calling app as most phones have this as standard now. I have no reception in my flat so this has been a lifesaver. I have figured out how to activate the volte and WiFi calling toggles but only the volte seems to work (I get an icon when on 4g). Has anyone been able to get this to work on any UK network?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3t/help/los-16-0-uk-native-wifi-calling-t3925743
Any LOS/Based ROM should work.
Thanks. I had a look on the other thread and couldn't see WiFi calling as an option despite being able to toggle it on. Can't remember what code I used.
Eggstones said:
Thanks. I had a look on the other thread and couldn't see WiFi calling as an option despite being able to toggle it on. Can't remember what code I used.
Click to expand...
Click to collapse
If it doesn't show as 'Provisioned' under the *#*#4636#*#* menu, it's not available. You're using OOS, right? I'm not sure there's any method to force the issue. Maybe a Magisk module?
Or start using Custom ROMs?
Dirk said:
If it doesn't show as 'Provisioned' under the *#*#4636#*#* menu, it's not available. You're using OOS, right? I'm not sure there's any method to force the issue. Maybe a Magisk module?
Or start using Custom ROMs?
Click to expand...
Click to collapse
I'm using OOS Oreo. I'm trying to remember what I did to get the toggles under sim preferences. Before then I didn't even have the toggles
Is this operator dependent or phone software. No idea how to add a module but should be able to figure that out.
Eggstones said:
I'm using OOS Oreo. I'm trying to remember what I did to get the toggles under sim preferences. Before then I didn't even have the toggles
Is this operator dependent or phone software. No idea how to add a module but should be able to figure that out.
Click to expand...
Click to collapse
Adding the Toggles to Settings is the easy bit. It doesn't mean a thing as far as getting the functions working though. The ROM, and specifically the telephony parts of it, need to have all the necessary code added. We know that 3 can add the bits needed on phones where they have control over the software updates. Otherwise it's down to the Manufacturer/ROM.
You never know, OOS Pie might have this working natively. You could ask in the Community Beta thread to see if anyone there has any idea. Or wait a while longer until OOS Pie is in Stable channel. (I assume you don't want to try the Community Beta?)
Dirk said:
Adding the Toggles to Settings is the easy bit. It doesn't mean a thing as far as getting the functions working though. The ROM, and specifically the telephony parts of it, need to have all the necessary code added. We know that 3 can add the bits needed on phones where they have control over the software updates. Otherwise it's down to the Manufacturer/ROM.
You never know, OOS Pie might have this working natively. You could ask in the Community Beta thread to see if anyone there has any idea. Or wait a while longer until OOS Pie is in Stable channel. (I assume you don't want to try the Community Beta?)
Click to expand...
Click to collapse
I might download it when I get back from my holiday. Don't want to mess with my phone when traveling.
I'm very much a novice when it comes to ROMs etc.
Downloaded the community build but no joy. No sign of wifi calling working.
Eggstones said:
Downloaded the community build but no joy. No sign of wifi calling working.
Click to expand...
Click to collapse
I'm not surprised. I doubt it's high on their list of priorities. Especially as a lot of this stuff is carrier specific. They probably expect the carriers themselves to add the necessary modifications before the units get into the hands of customers, which is what happens most of the time. Except, Oneplus phones are usually bought off contract as nobody here offers them with contracts.
Eggstones said:
Thanks. I had a look on the other thread and couldn't see WiFi calling as an option despite being able to toggle it on. Can't remember what code I used.
Click to expand...
Click to collapse
The provision toggle shows up now when I am back in the UK. Might try to install lineage to see if it helps.
Did you end up getting this to work on lineage? I'm having the same problem and the three in touch app has just stopped working for me.
This is on a op3 (not t)
welshyoot said:
Did you end up getting this to work on lineage? I'm having the same problem and the three in touch app has just stopped working for me.
This is on a op3 (not t)
Click to expand...
Click to collapse
Haven't gotten around rooting and installing it. I have volte in most of the flat so the phone kinds works at home.
Fair enough, thanks for the reply. If I end up getting it working I'll report back
Tried to figure out how to instal lineage on my phone but I got stranded after installing ADB on my laptop. My problem is that most of the guides assumes that you know what you are doing in minute detail and therefore leave out quite a lot of steps. It also seems like you will lose all your data which means you need to back it up and to back it up you need to root the device which whips the data... Installing twrp seems also to wipe your data which is a bummer as you need that to do the backup of your phone.
As you can see I'm damned if I do and damned if I don't
Tried today to install lineage and I cannot say I'm impressed with the various guides I found. The lineage os wiki page omitted various steps such as which entry you needed to edit in the environment variables. There are several to choose from. Nor did it not mention that you need to enable unlocking the bootloader. Had to Google that to figure out how to get around that error
Installing twrp didn't work as it didn't recognise the file. Tried three different workarounds that didn't work. (File extension, dropping the twrp image onto the command window after typing the fastboot flash recovery line and moving the image to the desktop and the ADB folder.
Why do the people who write these guides assume you have extensive knowledge of installing ROMs instead of including all necessary steps. Needless to say, I failed to install lineage.
Rant over.
welshyoot said:
Fair enough, thanks for the reply. If I end up getting it working I'll report back
Click to expand...
Click to collapse
Any success? I have finally got lineage 16 on my phone but not been able to get WiFi calling working
No, ended up getting a new phone unfortunately.
My much-loved, rooted, V40 405QA with latest and last stock Android has worked great on Verizon since the 4G changeover forced me to move from ATT where it could NEVER make voice calls.
I should say that it has worked great until the last few months and I think this change is due to Verizon's final sunset of CDMA - which is supposed to have been completed 12/2022.
In the last few months I find that the voice/sms network is often on EMERGENCY only (not true of the data network which seems to recover just fine) - even if it was fine only a few minutes ago (in a different location, usually). And this can ONLY be remedied by rebooting the phone. You can see this in the phone's radio details (hard to get at as the normal settings UI has no link to it - but still possible in a couple ways).
It appears that this happens any/every time that the phone has network contact but looses it. This can be caused by passing through a dead zone or by turning flight mode on and then off. It happens every single time! And again, the only "fix" I can find is to reboot. This is clearly unacceptable.
It is NOT Verizon or my SIM. I have tested moving it from by V40 into the wife's Samsung S8+ and it does NOT do this at all. So it has to be something about my phone. Additionally, I put a T-Mobile SIM in the V40 and it does the same thing - only worse because T-Mobile coverage is so crappy where I live and it is almost one BIG dead zone.
I have tried all the network preference options to see if changing them has any influence. It does NOT. So I am really stuck here.
So:
1. Are others seeing this problem?
2. Are there any known work-arounds?
I really appreciate the time and any help.
I have found, by accident, that the issues reported above DO NOT occur if the phone is in Safe Mode.
This makes me think that some mod I have done via magisk, LsPosed, etc is the source of my problem.
Sadly, I cannot get at anything while the phone is in safe mode. I would try to use adb but this damn phone has long had issues with USB connectivity - described elsewhere. I have tried to make my terminal emulator or rooted file manager into system apps hoping that if they were I could use them within safe mode. But that doesn't work either.
I use Magisk all the time without, I must admit, understanding much of what it does or how it works. It just seems to... But now I really think I need to be able to get at files that Magisk seems to "protect" in the system as I suspect what I need might be in there. I have no idea where Magisk puts/keeps all this. I will post in the Magisk thread but thought I'd mention it here as well.
Thanks for any suggestions.