Related
Is there a XT860 Radio Image or sbf / fastboot file that
will work on gsm (U.S. Bands, I.E. T-Mobile)?
instead of the chinese one, you know!
We have fastboot files from Brazil, Argentina and Mexico. All of these will work on an XT860 and GSM bands. Check out this thread for details and downloads:
http://forum.xda-developers.com/showthread.php?t=1370721
As far as I know, these will not give you H+, only 3G speeds. Currently the only way to have H+ on an XT860 is to be on the Bell Firmware, which we do NOT yet have an SBF for.
Hope that helps.
gbarayah said:
We have fastboot files from Brazil, Argentina and Mexico. All of these will work on an XT860 and GSM bands. Check out this thread for details and downloads:
http://forum.xda-developers.com/showthread.php?t=1370721
As far as I know, these will not give you H+, only 3G speeds. Currently the only way to have H+ on an XT860 is to be on the Bell Firmware, which we do NOT yet have an SBF for.
Hope that helps.
Click to expand...
Click to collapse
i could flash em :/
If you have an xt860 afaik any firmware will work on american gsm though T-Mobile will ply get edge speeds. If you have an xt862 I do not know if xt860 radio.img will work on an xt862. They have different radio hardware
Sent from my XT860 using xda premium
Endoroid said:
If you have an xt860 afaik any firmware will work on american gsm though T-Mobile will ply get edge speeds. If you have an xt862 I do not know if xt860 radio.img will work on an xt862. They have different radio hardware
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
afaik they all have the exact same hardware, idk i have a 62, but i want a better radio, the chinese is INDECIPHERABLE :/, i would like 3g going on tmo which i'm pretty sure possible just not on the chinese radio image, also i can flash the 60's image, i just need a proper(er) img (Hopefully bell's) And a build prop to go with it, i'm making a "Ghetto Fastboot"
ericerk said:
afaik they all have the exact same hardware, idk i have a 62, but i want a better radio, the chinese is INDECIPHERABLE :/, i would like 3g going on tmo which i'm pretty sure possible just not on the chinese radio image, also i can flash the 60's image, i just need a proper(er) img (Hopefully bell's) And a build prop to go with it, i'm making a "Ghetto Fastboot"
Click to expand...
Click to collapse
As far as I know the best you can do with T-Mobile is edge speeds due to them using a band neither device ca use. I wish you the best of luck, if you succeed im sure others would be interested in your results
Sent from my XT860 using xda premium
Endoroid said:
As far as I know the best you can do with T-Mobile is edge speeds due to them using a band neither device ca use. I wish you the best of luck, if you succeed im sure others would be interested in your results
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Thanks!! we'll see how it goes
T-Mobile uses 1700 MHz for its 3G. These phones do not have compatibility with that frequency. This is what I was trying to tell you before, when I said T-Mobile's 4G is not compatible: it's the same exact network. 3G=4G, only they call it 4G when your phone is capable of greater speeds due to more advanced radio technology, not a different frequency.
T-Mobile only uses 1900 MHz for Edge, and 2100 won't work because it's 4G only, and won't work if you don't also have access to 1700, which is for both 3G and 4G. I hope this makes sense.
I'm glad you made your own thread to deal with this issue, and I hope I am wrong and that someone more knowledgeable comes along and corrects me and tells us all how to make it work. If you figure it out I will apologize as well. However, I just want it to be clear that no one who has made gsm work on the D3 has been able to (let alone interested in) getting 3G/4G to work on T-Mobile. I have assumed it is because it's an incompatibility problem between the hardware of these phones and the network you're trying to use.
Even if you had an xt860, it wouldn't work on 3G on T-Mobile, so using their radio.img and build.prop won't help on the xt862. Just because you can flash them doesn't mean they will work.
By all means, please post results and let me know if I'm wrong. As I said, I would prefer to be wrong in this case, but I don't think I am.
By the way, the xt883 radio.img shouldn't change the functionality of the phone beyond letting it connect to gsm in the US. I really don't see what your gripe is with it. Not that I'm offended or something; who cares. But I use it every day and haven't seen any results worth frowning over, let alone trying to switch to the xt860's which is not at all compatible with CDMA.
BenSWoodruff said:
T-Mobile uses 1700 MHz for its 3G. These phones do not have compatibility with that frequency. This is what I was trying to tell you before, when I said T-Mobile's 4G is not compatible: it's the same exact network. 3G=4G, only they call it 4G when your phone is capable of greater speeds due to more advanced radio technology, not a different frequency.
T-Mobile only uses 1900 MHz for Edge, and 2100 won't work because it's 4G only, and won't work if you don't also have access to 1700, which is for both 3G and 4G. I hope this makes sense.
I'm glad you made your own thread to deal with this issue, and I hope I am wrong and that someone more knowledgeable comes along and corrects me and tells us all how to make it work. If you figure it out I will apologize as well. However, I just want it to be clear that no one who has made gsm work on the D3 has been able to (let alone interested in) getting 3G/4G to work on T-Mobile. I have assumed it is because it's an incompatibility problem between the hardware of these phones and the network you're trying to use.
Even if you had an xt860, it wouldn't work on 3G on T-Mobile, so using their radio.img and build.prop won't help on the xt862. Just because you can flash them doesn't mean they will work.
By all means, please post results and let me know if I'm wrong. As I said, I would prefer to be wrong in this case, but I don't think I am.
By the way, the xt883 radio.img shouldn't change the functionality of the phone beyond letting it connect to gsm in the US. I really don't see what your gripe is with it. Not that I'm offended or something; who cares. But I use it every day and haven't seen any results worth frowning over, let alone trying to switch to the xt860's which is not at all compatible with CDMA.
Click to expand...
Click to collapse
That's how i've understood it, our devices lack the 1700 band. It will work on t-mobile network, but only at edge speeds. I do believe this has been tried. I also don't think an xt860 radio.img will work as expected on an xt862, but i wish him the best of luck. I would like to use t-mobile when i travel to the states, they have a really good pay per day plan compared to others i looked at(although for a week at a time i can live with edge speeds). and yes, xt860 is GSM only if the flash does work there will be no CDMA functionality
bp.img VS radio.img
What is the difference between bp.img and radio.img ?
Is it the same file ?
SX86 said:
What is the difference between bp.img and radio.img ?
Is it the same file ?
Click to expand...
Click to collapse
Open in a Hex Editor to compare. I don't think they are the same... I took apart all of the files in the latest Bell update with no success, as well I tried dd'ing all of the different partition blocks to my phone just before sending it into the shop to get Bell firmware re-loaded onto it and didn't get any luck... in the end it was basically an encrypted bootloader problem.
If we can get the phone bootloader-unlocked we *might* be able to use some of the dd images that were created (I have each partition from bell 2.3.4) flashed through RSD then do the upgrade to the latest Bell, which overwrites the radio and boot partitions...
Let me know if anybody is interested in them. Please note, they the whole partitions and have extra padding on them. Also, I think I missed /preinstall, but I can't remember.
I created a new thread for this... again it's the original Bell stuff 2.3.4. I can probably do the same thing for the current Firmware as well.
Please see http://forum.xda-developers.com/showthread.php?t=1449027 for the 2.3.4 dd images
I've never seen/heard of that first one you mentioned before.
Sent while mobile using Tapatalk.
BenSWoodruff said:
I've never seen/heard of that first one you mentioned before.
Sent while mobile using Tapatalk.
Click to expand...
Click to collapse
its in a candian rom, no its not the same, don't try to flash you'll mess up ur phone
So... did anyone try the XT860 radio on the XT862?
Hey everyone.. I've been combing through forums for the past 5 hours trying to help out a buddy. He picked up an unlocked Verizon XT862 a while back, but we're having a heck of a time getting it on Manitoba's MTS network (partnered with Rogers in Manitoba, Canada). I put on .890, then rooted, safestraped, and tried Steel Droid. It won't find the MTS gsm network. I even have tried screwing around with a 883 radio and modified build.prop. It would be great if I could just run the Bell XT860 firmware as that would probably do it, but I have heard that's impossible. So has Verizon just locked the ever locking crap out of this things GSM or what? Any way I can get voice/sms/data working up here on this thing? I desperately need some help. Thanks!
System version
5.6.890.XT862.Verizon.en.US
Model number
DROID3
Android version
2.3.4
Baseband version
N_03.18.29P
Kernel version
2.6.35.7-g790a33c
[email protected] #1
Build number
5.5.1_84_D3G-55
ERI version
5
PRL version
58008
i dont think verizon locked anything.... Im using a GSM simcard in Lithuania without any problems, try switching your phone Network Mode to Global or GSM/UMTS
Hm.. Okay thanks. I'm just reloading the SBF to get it back to stock. It will find Rogers, but I can never get it to see MTS for some reason. I will keep trying.
So I reloaded the SBF and same issues. When this phone is on Network Mode: GSM/UMTS , it finds Rogers 3G and 2G. If I pick Rogers 3G, I don't get any service. It just has the red No over the signal bars. If I switch it to Network Mode: Global, it gets almost full signal strength, but in *#*#4636#*#* its using the CDMA network. If I change the preferred network type to GSM only, it never finds anything (assuming its only looking for Verizon?). If I try GSM auto (PRL), then it doesn't find anything either. I just don't get why its not finding our MTS 3G network in Network Mode: GSM/UMTS.
Try these apns
http://www.howardforums.com/showthread.php/1709183-MTS-APN-settings
Sent from my XT860 using xda premium
Yeah I have the apns from MTS already. It still doesn't seem to find MTS though. Only Rogers comes up after network scans. I'm going to try to modify the build.prop.
HiQ said:
Yeah I have the apns from MTS already. It still doesn't seem to find MTS though. Only Rogers comes up after network scans. I'm going to try to modify the build.prop.
Click to expand...
Click to collapse
Does it use the Rogers network, or have its own? What spectrum does it use? Are you sure the d3 supports its spectrum? I didn't see that info in my good search, although I did see they have a legacy cdma network, can you find that?
Sent from my XT860 using xda premium
Endoroid: Thanks for the help. Yeah they used to be purely CDMA (EVDO and 1x), but they decided to partner with Rogers in Manitoba and share the HSPA+ (21Mbps) towers. As taken from their website: Please note that any unlocked device must support 4G North American Frequencies (850Mhz), older GSM devices will not function on our new 4G network. You can find out if your device is 4G compliant by reviewing the phone's settings.
So it looks like they operate on the 850Mhz spectrum, which should be fine for the quad band XT862. I'm not 100% sure if the network search should show up MTS 3G or not. I don't have an official MTS GSM phone to check it with. It does find the following two networls:
CAN Rogers Wireless Inc. 3G (302-720)
CAN Rogers Wireless Inc. 2G (302-720)
I would assume I should see something like: CAN MTS Wireless Inc. 3G (something here), but nothing ever shows up. If I select either of the Roger's networks, nothing ever happens. It just has the red block over the signal bars and it never grabs a signal. Then I randomly get the following popup:
Network Error
No GSM/UMTS networks were found. Would you like to switch to the Global mode?
I've had it pull the 1x legacy MTS CDMA network before. I think that might have been in Global mode.
So confused.
Okay I'm RSD'ing VRZ_XT862_5.5.1_84_D3G-55_1FF_01.xml back onto this thing. That should get me back to stock, right? I don't know why it doesn't just work with the stock setup. I really should, shouldn't it? It's unlocked, just load the apns and go? Weird. Does RSD'ing that file reset the radios and everything? I'm not sure what all has been messed with on this thing. I'd like it back to virgin if possible.
Edit: So I reload that file and it boots up asking about international roaming. I agree and it pulls a network. It's MTS 1x CDMA though. I put it to GSM/UMTS and do a network search and the two Rogers networks show up again. If I pick one of them, I instantly get a notification bar error about no service and selected network unable... I have an MTS SIM in this thing and the mts apn entered. So weird.
My buddy said at one point while he was messing with it, he had it find the MTS gsm network. He can't remember what rom or what he had done, but he still couldn't get data working. Only voice/sms. Should I try a different rom? Any suggestions?
HiQ said:
Okay I'm RSD'ing VRZ_XT862_5.5.1_84_D3G-55_1FF_01.xml back onto this thing. That should get me back to stock, right? I don't know why it doesn't just work with the stock setup. I really should, shouldn't it? It's unlocked, just load the apns and go? Weird. Does RSD'ing that file reset the radios and everything? I'm not sure what all has been messed with on this thing. I'd like it back to virgin if possible.
Edit: So I reload that file and it boots up asking about international roaming. I agree and it pulls a network. It's MTS 1x CDMA though. I put it to GSM/UMTS and do a network search and the two Rogers networks show up again. If I pick one of them, I instantly get a notification bar error about no service and selected network unable... I have an MTS SIM in this thing and the mts apn entered. So weird.
My buddy said at one point while he was messing with it, he had it find the MTS gsm network. He can't remember what rom or what he had done, but he still couldn't get data working. Only voice/sms. Should I try a different rom? Any suggestions?
Click to expand...
Click to collapse
I dont think rom will matter. You could try editing the build.prop. Change default network mode from 7 to 3 and verizon global phone from 1 to 0. These are the changes needed to get d3(cdma)roms to work on my xt860(GSM) .
You could add the apns to /system/etc/apns-conf.xml I don't think that will make any difference as it should read it from the sim, but never hurts to try.
Sent from my XT860 using xda premium
That's exactly what I've been trying in regards to the build.prop. Doesn't seem like it ends up doing anything thouhg. Not sure. I will definitely try adding the apns to that other file though. Thanks again!
Ya im sort of at a loss. I've only ever used my device on the bell network(the carrier I bought it from) so I've never had to deal with this issue. Hopefully someone with more experience in this will pipe up
Sent from my XT860 using xda premium
Endoroid said:
Ya im sort of at a loss. I've only ever used my device on the bell network(the carrier I bought it from) so I've never had to deal with this issue. Hopefully someone with more experience in this will pipe up
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
For some reason I recall reading about XT862 users having to flash something like the XT883 radio to access GSM networks? Or am I mixed up...
LaZiODROID said:
For some reason I recall reading about XT862 users having to flash something like the XT883 radio to access GSM networks? Or am I mixed up...
Click to expand...
Click to collapse
Hmmm... That might actually make sense. It's supposed to be locked against us gsm networks, but I wonder if it extends to Canadian networks as well. Maybe take a look in the unlock for at&t thread
Sent from my GT-P5113 using xda premium
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
http://forum.xda-developers.com/showthread.php?t=1406812
Sent from my GT-P5113 using xda premium
Endoroid said:
Hmmm... That might actually make sense. It's supposed to be locked against us gsm networks, but I wonder if it extends to Canadian networks as well. Maybe take a look in the unlock for at&t thread
Sent from my GT-P5113 using xda premium
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
http://forum.xda-developers.com/showthread.php?t=1406812
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Hey guys.. I had sifted through most of that thread and attempted the radio and build.prop flash, but I was still having troubles. Maybe I'll give it another go. Thanks!
I'm trying to follow this post: http://forum.xda-developers.com/showpost.php?p=24176930&postcount=176 because I've never put .906 on this thing. I can get the chinese ota to install with rsd fine, but I'm having troubles getting the XT883 OTA.zip to flash. It errors out while installing with safe mode on. Should I be running a different recovery? Also, whenever I try to launch recovery from startup, it just triangle ! errors and dies. Something must be missing. Should I have CMW recovery on this thing instead or any ideas?
Data connection DROID 3
HiQ said:
That's exactly what I've been trying in regards to the build.prop. Doesn't seem like it ends up doing anything thouhg. Not sure. I will definitely try adding the apns to that other file though. Thanks again!
Click to expand...
Click to collapse
I'm having the exact same problem.
I have an unlocked DROID 3, which is working perfectly fine for voice and SMS, but no Data.
I've tried flashing the XT883 radio img, which did nothing.
I'm thinking I might just flash the whole XT883 ROM onto it, maybe it'll make a difference?
But, in regards to your case, I do recall that someone mentioned not being able to get a data connection in Canada, en they had to play around with the libmoto_ril.so file.
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=1406812&page=33
It's apparently been test fro Bells and Rogers.
Hope that helps.
Cheerrs.
I just read in another thread about the stock verizon rom screwing with gsm. Trust big red. Maybe try a custom. Eclipse of mavrom are the most stable gb roms
Sent from my XT860 using xda premium
+1 for both of those roms
Sent from my HTC Raider
Endoroid said:
I just read in another thread about the stock verizon rom screwing with gsm. Trust big red. Maybe try a custom. Eclipse of mavrom are the most stable gb roms
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Flashed XT883 ROM. No luck.
Only change is that it's automatically getting the default APN's for the network. But no DATA.
At this point, Could it be a hardware issue? My voice and sms radio is working perfectly, are they linked? WIFI works fine.
Such a nice phone. pity.
Cheers.
I still do not know how to get FastBoot_SU working on my XT907 so these things are just experimental.
Verizon XT907 Razr M US with US T-Mobile using NON-HLOS.bin from AUSSIE ICS
I know Edge and Voice is working with my Sim.
No idea how to get FastBoot_SU working so i did this a bit different.
You will need:
VZW_XT907_4.1.1-9.8.1Q-27-2-4_1FF.xml (http://forum.xda-developers.com/showthread.php?t=2017200)
RSDLite6.1.4_FLASH
MotorolaDeviceManager_2.3.4 DRIVERS
NON-HLOS.bin from AUSSIE Razr M it is 102.400KB compared to the US 49.xxxKB (http://dl.dropbox.com/u/8648738/NON-HLOS.bin)
WinRar or any Zip Program
1. Navigate inside VZW_XT907_4.1.1-9.8.1Q-27-2-4_1FF.xml using winrar or winzip and find the original NON-HLOS.Bin over write this with the Aussie Radio 100kb one. Make sure its packed normal again.
2. Use RSDLite, make sure Phone is in Debug mode, flash the new VZW_XT907_4.1.1-9.8.1Q-27-2-4_1FF.xml with the modified Radio.
3. Let the update do its thing, once done insert SIM and enjoy GSM reception.
4. Find a way to gain root access ahhahahaha bc this should wiped ur root access.
There is a way to use FastBoot_SU somehow but it does not work me ...
This is the same modification done to ICS to get it to work with US carriers, except you are on JB or in this case i used JB to flash the entire device.
Some one feel free to clean up these steps or improve this for easy use of tutorial ? You are welcome to edit LOL
followed the steps. but it seems the radio is problematic, because att signal is vey vey weak. I couldnot place call.the same micro sim had 4 bar at my hd2 win phone.
any fix?
Sent from my XT907 using Tapatalk 2
Just tried flashing following your instructions and got stuck.
RSD Lite v5.6 Multi-Flash reports:
Failed flashing process. 16/19 flash "cdrom" -> Phone returned FAIL.; phone connected
Please help!!! Phone now stuck in Fastboot Flash Mode...
Thank you
I did not use 5.6
Also make sure ur battery is above 50% I did have issues flashing when my phone was at about 30-40 ish %
It will show up as low battery.
Get the Stock Verizon JB reflash it with 6.X and up.
Then use a clean version of JB with a modded PJcon Aussie Radio.
And reflash it from there.
To get out of there just Reboot by holding all buttons Power and Volume until reboot.
Thank you!
It only works with version 6 and above.
All is good now.
BTW I just traveled through the documented refarmed areas in Chicago and Cleveland and still no 3g.
yeah same here.
We still figuring out how to get 3G or 4G
Just to add some "fuel to the fire"...a year or so ago I got bored with my Defy and got an Atrix 4G online from the US (I live in Australia). It was AT&T branded and locked so had to purchase an unlock code. When I got it going on Telstra, the reception was just never that good. People always complained they couldn't hear me and I had similar experiences with hearing them. I even gave it to my bro on the other side of the country and he had the same issues.
I suppose what I'm putting forward is that even if it is 2100mhz band or 850mhz band which the Aussie radio does (I don't know what AT&T/T-Mobile run on), it's possibly more than that? I recall reading a VERY interesting article about how much work carriers do to get phones to work on their selected band - no disrespect to any Devs intended, this is just my thoughts as this may be a ghost we're chasing?
Or is the Electrify M XT905 going to work any better?
Works perfectly fine in Germany though Germany uses Stock Rom for XT907
I am getting Super strong signal everywhere better than my iPhone 4, I am using Aussie radio.
I even get better signal than the AT&T users. So it maybe the area, AT&T been getting worse bc they share some towers with T-mobile now.
By that the same tower rent space T-mobile is allowed to put up their Antenna gear, which sometimes decreases signal strength of AT&T.
Which happened alot in my area, alot of AT&T users loosing more signal... and running a modded phone is probably isn't helping the matter.
But T-Mobile seems to have few more frequencies after the refarm ? Maybe that's why ?
The XT907 Definitively is able to get H+ on GSM with Stock Rom in Europe.
H+ we managed to get it to 2.xMB but her normal area we only get 1.5-1.9MB ish
She also picks up E and 3G here and there.
This is on O2 Germany (DE) in Munich Testing to Frankfurt.
Using Stock Verizon Firmware un-modified stock radio.
I will test Aussie Radio next week in Germany see what happens.
But right now She is enjoying H+ with GSM on a XT907.
Hi guys,
I've read the threads in Q/A and this one about different sim cards in RAZR M, and I must say I'm pretty sad because it doesn't work.
I like this phone very much. It's the best phone I've ever seen. But I won't buy it because I don't have money to pay for expensive plans to Verizon (nor I will be in the US for 2 years which is the minimum contract time), and it doesn't work on T mobile which I would like to use. I guess I will have to stay on my Defy and wait for some new unlocked version of Motorola (never gonna happen imo).
Or should I buy it and try this method so I can use it partially with T mobile? Please advise.
Sent from my MB525 using xda app-developers app
I am using it with this method with T-Mobile.
Though when i am in Germany I have to take the mod out to get onto 3G in Germany.
With US-T-mobile we only managed to get Edge Connectivity so far.
I like it because i dont use much data and edge is enough for geting GPS to work smooth and surfing is slooow.
Else all is well =)
Thanks for the info~~~!!
It'd be really cool if the dropbox link worked. Unless im doing something wrong. Unless i can pull it out of another stock/rom file
Great info. Is the dropbox link down for good? I cant seem to find any mirrors :-/
This method has been made obsolete by the discovery of a much simpler procedure that edits a single bit in the radio NVM that enables full service on US carriers.
I wrote up the updated method in the Q&A section.
http://forum.xda-developers.com/showthread.php?t=2166542
Can someone please reupload AUSSIE RADIO as Radiocomm method is not working for me!
Proda said:
Hi guys,
I've read the threads in Q/A and this one about different sim cards in RAZR M, and I must say I'm pretty sad because it doesn't work.
I like this phone very much. It's the best phone I've ever seen. But I won't buy it because I don't have money to pay for expensive plans to Verizon (nor I will be in the US for 2 years which is the minimum contract time), and it doesn't work on T mobile which I would like to use. I guess I will have to stay on my Defy and wait for some new unlocked version of Motorola (never gonna happen imo).
Or should I buy it and try this method so I can use it partially with T mobile? Please advise.
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
May I suggest buying the RAZR i
Germanese said:
I still do not know how to get FastBoot_SU working on my XT907 so these things are just experimental.
Verizon XT907 Razr M US with US T-Mobile using NON-HLOS.bin from AUSSIE ICS
I know Edge and Voice is working with my Sim.
No idea how to get FastBoot_SU working so i did this a bit different.
You will need:
VZW_XT907_4.1.1-9.8.1Q-27-2-4_1FF.xml (http://forum.xda-developers.com/showthread.php?t=2017200)
RSDLite6.1.4_FLASH
MotorolaDeviceManager_2.3.4 DRIVERS
NON-HLOS.bin from AUSSIE Razr M it is 102.400KB compared to the US 49.xxxKB (http://dl.dropbox.com/u/8648738/NON-HLOS.bin)
WinRar or any Zip Program
1. Navigate inside VZW_XT907_4.1.1-9.8.1Q-27-2-4_1FF.xml using winrar or winzip and find the original NON-HLOS.Bin over write this with the Aussie Radio 100kb one. Make sure its packed normal again.
2. Use RSDLite, make sure Phone is in Debug mode, flash the new VZW_XT907_4.1.1-9.8.1Q-27-2-4_1FF.xml with the modified Radio.
3. Let the update do its thing, once done insert SIM and enjoy GSM reception.
4. Find a way to gain root access ahhahahaha bc this should wiped ur root access.
There is a way to use FastBoot_SU somehow but it does not work me ...
This is the same modification done to ICS to get it to work with US carriers, except you are on JB or in this case i used JB to flash the entire device.
Some one feel free to clean up these steps or improve this for easy use of tutorial ? You are welcome to edit LOL
Click to expand...
Click to collapse
is there a way to flash it in a RAZR-M with JB 4.1.2 ?
toroloco73 said:
is there a way to flash it in a RAZR-M with JB 4.1.2 ?
Click to expand...
Click to collapse
Yes it is.
Though I am not sure if it is possible on the 98.18.78.
Earlier ones will work.
Germanese said:
Yes it is.
Though I am not sure if it is possible on the 98.18.78.
Earlier ones will work.
Click to expand...
Click to collapse
now i'm on xt907_stock_deodex_98.16.3
i can't find NON-HLOS.bin from AUSSIE Razr M file
Anyone know whether or not data works on the new KEXEC builds on a XT862 unlocked for GSM? I'm thinking about switching over to the KEXEC CM10, but want to know if i could still use data. If not, I'll stick with current ROM.
Yes I use T-Mobile. Look for 883 build.props in the thread.
Sent from my XT862 using xda app-developers app
MrObvious said:
Yes I use T-Mobile. Look for 883 build.props in the thread.
Sent from my XT862 using xda app-developers app
Click to expand...
Click to collapse
well i'm sorry to say that in the last year i have been tried all of the available CM9 roms, none of them have a 3G ability to a xt860.....
jawsofire said:
Anyone know whether or not data works on the new KEXEC builds on a XT862 unlocked for GSM? I'm thinking about switching over to the KEXEC CM10, but want to know if i could still use data. If not, I'll stick with current ROM.
Click to expand...
Click to collapse
Yes the xt862 has data on kexec. http://forum.xda-developers.com/showthread.php?t=1989359 here is my info and files about it.
boazal said:
well i'm sorry to say that in the last year i have been tried all of the available CM9 roms, none of them have a 3G ability to a xt860.....
Click to expand...
Click to collapse
The 862 and 860 are different phones. Other people have been able to get 3G on the 860 from what I've seen, or at least Edge.
Skreelink said:
Yes the xt862 has data on kexec. http://forum.xda-developers.com/showthread.php?t=1989359 here is my info and files about it.
Click to expand...
Click to collapse
From what I'm reading, I need to switch radios. I'm running the XT862 Radio unlocked for US GSM. Would that still work or do I have to flash the a different radio?
jawsofire said:
From what I'm reading, I need to switch radios. I'm running the XT862 Radio unlocked for US GSM. Would that still work or do I have to flash the a different radio?
Click to expand...
Click to collapse
What system do you have in your Setings, About, Status? It should tell you the radio version there. If you use T-Mobile/AT&T then it's probably the 883 and you can find the appropriate build.prop for any ROM.
MrObvious said:
What system do you have in your Setings, About, Status? It should tell you the radio version there. If you use T-Mobile/AT&T then it's probably the 883 and you can find the appropriate build.prop for any ROM.
Click to expand...
Click to collapse
I have the XT862 Radio.
jawsofire said:
I have the XT862 Radio.
Click to expand...
Click to collapse
Then if you are trying to use AT&T/T-Mobile you need the 883 radio/build.prop.
MrObvious said:
Then if you are trying to use AT&T/T-Mobile you need the 883 radio/build.prop.
Click to expand...
Click to collapse
It seems like there are a large handful of people having connection issues with the 883 radio. I think I'll just stick with the XT862 radio. I could always give it a try and if it doesn't work, SBF back to stock.
jawsofire said:
It seems like there are a large handful of people having connection issues with the 883 radio. I think I'll just stick with the XT862 radio. I could always give it a try and if it doesn't work, SBF back to stock.
Click to expand...
Click to collapse
The XT883 radio is ONLY required if you're using domestic GSM, such as AT&T or T-Mobile. The XT862 stock radio has an MNC block on 310 (US gsm carriers) but will be unlocked for all foreign carriers, this ensures the D3 is not used in the US on major competitors
Also, if you test the XT883 radio.. why not just reflash the stock radio instead of an entire SBF? I've done this several times. Just make sure you have a backup of the stock build.prop and restore as you flash radios. I have a build.prop.cdma and build.prop.gsm in /system and just take off the corresponding type for the one I want to use. I've uploaded the stock XT862 radio before.
I currently use the XT883 radio and have no issues with connectivity, I've also written a build.prop for use with the XT883 radio on kexec roms and has no issues either. HSPA data everywhere.
883 worked fine for me on that ROM.
Sent from my DROID3 using xda app-developers app
Skreelink said:
The XT883 radio is ONLY required if you're using domestic GSM, such as AT&T or T-Mobile. The XT862 stock radio has an MNC block on 310 (US gsm carriers) but will be unlocked for all foreign carriers, this ensures the D3 is not used in the US on major competitors
Also, if you test the XT883 radio.. why not just reflash the stock radio instead of an entire SBF? I've done this several times. Just make sure you have a backup of the stock build.prop and restore as you flash radios. I have a build.prop.cdma and build.prop.gsm in /system and just take off the corresponding type for the one I want to use. I've uploaded the stock XT862 radio before.
I currently use the XT883 radio and have no issues with connectivity, I've also written a build.prop for use with the XT883 radio on kexec roms and has no issues either. HSPA data everywhere.
Click to expand...
Click to collapse
My phone is unlocked to use the XT862 Radio for US GSM (Don't ask how, not at liberty to say at this moment). That is why I'm asking these questions. I don't want to have to re-flash and loss the unlock like I did with my Droid 4.
jawsofire said:
My phone is unlocked to use the XT862 Radio for US GSM (Don't ask how, not at liberty to say at this moment). That is why I'm asking these questions. I don't want to have to re-flash and loss the unlock like I did with my Droid 4.
Click to expand...
Click to collapse
Besides the 883 radio? Cool. When you can you should share.
Sent from my DROID3 using xda app-developers app
I'll give it a try since I have multiple slots with safestrap. Guess I'll be the first to test. I'll let you guys know how it turns out.
Works fine with the XT862 Radio. Some things I've noticed:
Not very responsive
Picking up HDSPA and 3G instead of just 3G
Only getting 1 bar of signal instead of 4
I flashed the latest build which was CM10.1. I had some problem with the recovery since I previously had clockwork recovery installed. Upon starting the phone, I had 2 force closes(Media and Phone). Once the ROM gets smoothed out and has camera working, I'll make the final switch.
jawsofire said:
Works fine with the XT862 Radio. Some things I've noticed:
Not very responsive
Picking up HDSPA and 3G instead of just 3G
Only getting 1 bar of signal instead of 4
I flashed the latest build which was CM10.1. I had some problem with the recovery since I previously had clockwork recovery installed. Upon starting the phone, I had 2 force closes(Media and Phone). Once the ROM gets smoothed out and has camera working, I'll make the final switch.
Click to expand...
Click to collapse
HSDPA *is* 3G.
HSDPA is in the same line as UMTS, which was technically the first 3g, then HSDPA/HSUPA were developed on that technology, then HSPA, HSPA+, then dual band HSPA+ which tops at 42Mbps. They're all technically the 3g (or 3.5g if you would) standard. Albeit T-Mobile and AT&T boast their HSPA networks as '4G' cause it looks better in marketing.
The Droid 3 supports up to HSPA 14.4Mbps.
Getting 1 bar instead of 4 is normal if you haven't modified the build.prop in a stock rom, there's a line verizon had added in to make the signal look bad (although looking in status shows normal signal levels, it's just cosmetic). On a kexec rom, if your build.prop hasn't been edited correctly to have the signal fix (which is under mobile networks) it'll also be stuck at one bar instead of normal. Although, if you're somehow using the stock XT862 radio, there should be no required edits to the build.prop to get proper GSM signal bars in a Kexec rom...
Skreelink said:
HSDPA *is* 3G.
HSDPA is in the same line as UMTS, which was technically the first 3g, then HSDPA/HSUPA were developed on that technology, then HSPA, HSPA+, then dual band HSPA+ which tops at 42Mbps. They're all technically the 3g (or 3.5g if you would) standard. Albeit T-Mobile and AT&T boast their HSPA networks as '4G' cause it looks better in marketing.
The Droid 3 supports up to HSPA 14.4Mbps.
Getting 1 bar instead of 4 is normal if you haven't modified the build.prop in a stock rom, there's a line verizon had added in to make the signal look bad (although looking in status shows normal signal levels, it's just cosmetic). On a kexec rom, if your build.prop hasn't been edited correctly to have the signal fix (which is under mobile networks) it'll also be stuck at one bar instead of normal. Although, if you're somehow using the stock XT862 radio, there should be no required edits to the build.prop to get proper GSM signal bars in a Kexec rom...
Click to expand...
Click to collapse
The only change I've made to my build.prop is ro.mot.phonemode.vzwglobalphone=0.
jawsofire said:
The only change I've made to my build.prop is ro.mot.phonemode.vzwglobalphone=0.
Click to expand...
Click to collapse
Well, since you seem to be the only person ever to use the stock xt862 radio on us gsm (without proof), and do not feel compelled to share how, we cannot help. I cannot work to fix something without any knowledge of howto, considering the radio lock is in the signed radio.img, radiocomm cannot modify it, as with the d2g, the lock was in the nvitems, which can be edited. Also, the radio.img cannot be modified and flashed, as the signed keys wont match the locked bootloader and will cause brick.
So unless you can provide proof/method of using the stock xt862 radio on us gsm, sorry... My guess is you actually have the xt883 radio and your build.prop just says xt862. Sorry for stating it like this, but I can claim to use the d3 on lte, until proof and method are given, there is a very thin margin of trust.
Skreelink said:
Well, since you seem to be the only person ever to use the stock xt862 radio on us gsm (without proof), and do not feel compelled to share how, we cannot help. I cannot work to fix something without any knowledge of howto, considering the radio lock is in the signed radio.img, radiocomm cannot modify it, as with the d2g, the lock was in the nvitems, which can be edited. Also, the radio.img cannot be modified and flashed, as the signed keys wont match the locked bootloader and will cause brick.
So unless you can provide proof/method of using the stock xt862 radio on us gsm, sorry... My guess is you actually have the xt883 radio and your build.prop just says xt862. Sorry for stating it like this, but I can claim to use the d3 on lte, until proof and method are given, there is a very thin margin of trust.
Click to expand...
Click to collapse
http://imgur.com/a/5NkVv
There is some proof. I know it's hard to prove other things, but I promised not to say anything. I don't want to get anyone in trouble. I can provide more screenshots, but that is about it.
I just flashed this build to my N6 a couple a days ago and right off I noticed that while in my house I wasn't getting a good lte signal anymore. Now before I updated to this build I had good lte in my house almost full bars even in my basement I had at least 2 or 3 bars. Well needless to say I wasn't happy with that so I flashed back to what I was running before which was MRA58N and sometimes R . Well when I flashed back to these builds I noticed again that something wasn't right my signal seemed to have been broke! So I started flashing just radios to see if that would help but to no avail.. I even called T-Mobile and they said nothing was going on in my area and I should have good signal ,but in that same sentence he brought up the cellspot tower that they want everyone in low signal areas to use. Well to make a long story short I live in the city and before I flashed this latest T-Mobile build I had great service even in my house. The messed up thing is I can't fix my N6 now know matter what build I use my signal is no good in my house anymore. It's almost like they have put a patch of some sort to my phone and it modded my phone to not had goog lte service behind walls. My phone now jumps from 3g to h to the ! Mark even when it's in some spot! My battery sucks now because of the constant change. I'm getting a new n6 Monday and I hope it doesn't have this X build on it because I'm going to not flash and see if my signal stays the way it used to which was a good signal. If it has good signal I'm (and this is just my opinion) think there /T-Mobile is just trying to push this cellspot tower on as many as they can and help it along is turning down Rf in our phones so they don't work well indoors.. Just my opinion!
I want the MRA58X radio to see if I have the same problem. I have the MRA58M with the 27R radio and it runs good. I wanna see if the 30R radio gives me more band 12 because I live in a band 12 area but it switches back to band 4 with the quickness. Anybody have the 30R radio in zip forms? It'll be greatly appreciated.
scoonie said:
I want the MRA58X radio to see if I have the same problem. I have the MRA58M with the 27R radio and it runs good. I wanna see if the 30R radio gives me more band 12 because I live in a band 12 area but it switches back to band 4 with the quickness. Anybody have the 30R radio in zip forms? It'll be greatly appreciated.
Click to expand...
Click to collapse
Oh the MRA58X does have band 12. Im not flashing this X build when my new N 6 gets here! I'll stay far away from it! I'll stick with Google's official builds! MRA58N worked great for me on T-Mobile and WiFi calling and I had band 12 as well. When I flashed this X build everything went haywire... IMO!
Im on MRA58X just wanted to know why all these different numbers ? And why is the x bad?
samomamo said:
Im on MRA58X just wanted to know why all these different numbers ? And why is the x bad?
Click to expand...
Click to collapse
MRA58X screwed up my data/ signal it was jumping all over the place for me. It would literally go from band 12 to 2 then 4 the radio never had a chance to settle and was causing major battery drain. The messed up thing is for some reason I couldn't even revert back to other builds cause the radio stayed messed up no matter what build I was on or rom.. I truly think MRA58X messed my n6 up and T-Mobile thinks it may have as well that's why there sending me a new n6 by Monday..?
Oh I forgot this radio jumping all over the place happens anywhere I go even when Im not even moving..?
Flashing different radios don't help either... I'm truly think this build/X does something weird with the way the phone tracks signals and for me its a major problem
beachbum40 said:
MRA58X screwed up my data/ signal it was jumping all over the place for me. It would literally go from band 12 to 2 then 4 the radio never had a chance to settle and was causing mager battery drain. The messed up thing is for some reason I couldn't even revert back to other builds cause the radio stayed messed up no matter what build I was on or rom.. I truly think MRA58X messed my n6 up and T-Mobile thinks it may have as well that's why there sending me a new n6 by Monday..?
Click to expand...
Click to collapse
Interesting, i have moto x pure , nexus 5x amd yesterday got the nexus 6 from the Amazon deal, so before using the nexuses i was with the moto x and had no problems with it watching youtube videos or anything. Then 3 days ago i got the nexus 5x and put my tmobile sim in it and started using that and was noticing that the videos were stopping like i was feeling something is not right , then yesterday got the Nexus 6 and put the sim in this now im having the same issues i was on lollipop and was not offering me the marshmallow update, so i unlocked the bootloader and when the phone started it gave the 6.0 update . so now im on the MRA58X. And im thinking maybe the marshmallow has to do something with that? Because the moto x is on lolipop and its a beast. Sorry for the long write.
you guys do realize that you can use any nexus 6 radio on any version of android? well you can. if this radio is giving you issues, you are more than welcome to try any other radio that you like, until you find the one that works best for you. im on tmobile, am using the 27R radio, wifi calling works fine, and so does everything else.
simms22 said:
you guys do realize that you can use any nexus 6 radio on any version of android? well you can. if this radio is giving you issues, you are more than welcome to try any other radio that you like, until you find the one that works best for you. im on tmobile, am using the 27R radio, wifi calling works fine, and so does everything else.
Click to expand...
Click to collapse
I know but im thinking maybe its the T-Mobile giving problems with the signal not the phone itself? Or maybe the marshmallow is handling the radio differently then the lolipop?
samomamo said:
I know but im thinking maybe its the T-Mobile giving problems with the signal not the phone itself? Or maybe the marshmallow is handling the radio differently then the lolipop?
Click to expand...
Click to collapse
im using marshmallow on tmobile, in nyc, and no problems here. try a different radio, or a few, if the problems still persist then its probably a local tmobile issue. as i said before, im using the 27R radio.
simms22 said:
im using marshmallow on tmobile, in nyc, and no problems here. try a different radio, or a few, if the problems still persist then its probably a local tmobile issue. as i said before, im using the 27R radio.
Click to expand...
Click to collapse
I've tried every radio out there. Before MRA58X this would solve the problem but since I flashed the X build it seems every radio now that I try has same issue. It's like the new X build did some kind of software change and now I'm stuck with every single radio I use jumping all over the place. Before X I didn't have this issue..
I did call T-Mobile and they said there is no problems with the network in my area. They are sending me a new phone and I'm not flashing X period..?
beachbum40 said:
I've tried every radio out there. Before MRA58X this would solve the problem but since I flashed the X build it seems every radio now that I try has same issue. It's like the new X build did some kind of software change and now I'm stuck with every single radio I use jumping all over the place. Before X I didn't have this issue..
Click to expand...
Click to collapse
well, it could be not the radio thats the issue as well. tmo delayed marshmallows release because they found a bug, then waited for a rom update. the rom update might be the issue. no, im not on that last tmo build, but all the builds work on tmo, and all of tmos features too. maybe you should try a different marshmallow build?
simms22 said:
well, it could be not the radio thats the issue as well. tmo delayed marshmallows release because they found a bug, then waited for a rom update. the rom update might be the issue. no, im not on that last tmo build, but all the builds work on tmo, and all of tmos features too. maybe you should try a different marshmallow build?
Click to expand...
Click to collapse
I did go back to NRA58K then N then even R. But after I flashed the X build it screwed up something where now even on those older builds its screwed up my data. before I flash X I was using MRA58k N and r with no issues. But since I flashed X now on any build its screwed up . Hope that makes sense..?
I'd put up a logcat but I run purely stock anymore because of PAY which I have to have?when I get my new n6 I'm not going to flash MRA58X and I'll see how things work. If all is well then it was the X build or maybe just something in my phone broke. I guess I'll find out Monday..
I've been on stock x for about 4 days. I'm seeing none of these issues and I still have great battery life. Phone has been perfect. I took the ota though. I did not flash x
Sent from my Nexus 6 using XDA Free mobile app
I am having the exact same issue on my Nexus 6 after taking the MRA58X update. My phone never used to associate with anything besides LTE or HSPA. After updating my phone would switch between all different network modes, even those that I have never seen in my area before the update. The problem is especially bad when roaming around, but having the phone stationary can also exhibit this behavior. The sequence of events is similar to the following: LTE, HSPA, GPRS, EDGE, UMTS (3G), GPRS, EDGE, LTE for a couple seconds, GPRS, HSPA, GPRS... The network is so unstable on the 2G based networks which made using the Internet very difficult. Reverting the radio to the previous version does not fix the issue as reported by a previous user, and it seems like that the update has made some changes in a way to at affects how the radio associates with neighboring towers permanently. I would advise against taking this update if you are using T-Mobile and your device is out of warranty, as T-Mobile will most likely not cover the "damage" even though it may be OTA related. It does however seem that using the *#*#4636#*#* code and forcing the phone into LTE mode makes the mad network switching go away, although now the phone can't grab onto HSPA in LTE coverage holes and call issues in non VoLTE areas. My standby battery life also seems to be significantly reduced by all of this network searching in the background.
You have been warned...
I took the X Ota and the phone is working flawless for me. Sorry you guys are having issues
Sent from my Nexus 6 using Tapatalk
Clean flash back to lollipop and see if that changes anything.
If it doesn't, it isn't the phone/rom.
BTW I recently got the X update and so far so good but to be fair I'm on wifi alot.
(but LTE does work as before)
...and it there are indeed weird tower issues, a rep won't tell you specifics.
I'm on MRA58N with TMO in the Metro Chicago area, WiFi calling, VoLTE, and HD calling all work fine, but it seems as though my N6 is just stuck on band 4. I've never ever seen this device surf on band 12 (and I run the LTE Discovery app).