Related
Like most Droid 3 owners I'm sure, I'm tired of paying ~$105 a month for cellphone service through Verizon that I could be paying ~$70 a month for through T-Mobile.
I've read the other thread here associated with unlocking the GSM portion of the Droid 3, but a lot of it seems to be shrouded in maybes and varied successes with a limited pool of test devices to draw on.
From what I gather thus far, the following is true:
- You can unlock the GSM capability of the Droid 3
- You can operate it on T-Mobile
- If you do, you will only get "Edge" connection speeds - No T-Mobile HSPA+ or 3G speeds. "Edge" only, at 512 kb or something like that.
Can anyone confirm this? Is there a way to get a Droid 3 to operate on T-Mobile's network at full speed?
Is there a more reliable and easier to use method to convert a stock VZW Droid 3 to something operable on T-Mobile?
Thanks in advance to anyone who can accurately answer these questions.
The only thing I've seen that works is using the xt883 Chinese ROM and it only gets edge. Edge is fine for me, but I want a better ROM with access to Android market.
Im still learning how this device works; I just installed Safestrap and tried to flash the GSM CM7 ROM today, to no avail. I flashed a custom ROM on my Droid 2 last year, but it's been a while on the G2x which isn't as locked down.
I flashed the CM7 GSM ROM on the safe mode partition, thinking that was how to do it, but I got an error trying to back anything up because /system wouldn't back up. Then when I flashed the ROM it wouldn't boot. Im wondering if I was supposed to flash the ordinary CDMA CM7 first, then use the GSM one, since it's named 3gedit.zip. I haven't tried that yet though, and the fact that /system isn't backing up worries me. I didn't create a partition on internal with Safestrap, but I flashed the GSM CM7 ROM from coreless in safe mode and it wouldn't boot. Got back to non-safe mode and my stock ROM was fine, but I still want to see a good back up :-/
Any ideas from more experienced users would be great. I'm pretty much a blind guinea pig right now lol. I just really want to see CM7 on this D3, and have it work on T-Mobile so I can retire my G2x for a little while.
Thanks in advance
Sent from my DROID3 using Tapatalk
Tutorial
note: This is not tied to any specific rom, it is not using the chinese rom it is simply taking the radio off the chinese rom which is all we need. It hasn't changed anything to me in user space that I have noticed.
I would recommend unlocking, rooting, flashing the radio, and editing the build.prop.
1. Unlock or online sim card unlock code seller but less reliable.
a) Meet the following requirements:
* Must be a Verizon Wireless customer.
* The phone being unlocked must be active on a Verizon Wireless line of service.
* The line of service must be active at least 60 days.
* The line of service must be in good standing for the past 60 days.
* Only one SIM Unlock per line every 10 months.
b) If you don't meet one or more of the above requirements, call anyway. You may still get lucky.
Call 1-800-711-8300 (Verizon Global Support) and ask the representative for a SIM unlock. Occasionally a representative may not know exactly what you are referring to; make sure you are not transferred to a different department. You are in the right place. Explain that they should have a walkthrough on how to do this, and that it allows for the use of local, non-Verizon SIM cards while traveling abroad.
c) Insert a foreign SIM into the SIM card slot on the side of your phone and then enter unlock code.
4. root ----> http://www.psouza4.com/droid3/
5. safestrap and backup in case something goes wrong -----> http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
6. chinese radio ----> http://dropbox.com/u/25454276/radio.zip
7. flash radio ----> http://dl.dropbox.com/u/16206920/moto-fastboot-win32.zip
8. use something like root browser lite(free) to backup to sd card then edit your system/build.prop
gfunkmonk said:
All you have to do is flash the radio.img from SOLANA_SLNCT-57.1.60_Fastboot in fastboot mode
Code:
moto-fastboot flash radio radio.img
then add the following lines to the build.prop
Code:
persist.ril.rssi.enable.param6 = 1
persist.ril.baudrate=230400
I can confirm this works with an AT&T sim in an unlocked phone, tested with stock and liberty 2.0.
Click to expand...
Click to collapse
I have called out, received a call and a text, I have checked my account information with the tmobile app on edge. I have been led to believe that its hardware that tmobile can only do edge since they use some non standard bands.
Credits:
flashing radio - http://forum.xda-developers.com/showthread.php?t=1360157
unlocking - http://community.vzw.com/t5/iPhone-4S/Verizon-iPhone-4S-SIM-UNLOCK-Tutorial/td-p/696707
safestrap - http://forum.xda-developers.com/showthread.php?t=1315982
Even if you go through all of that you I'll still have only EDGE because our radios don't use the 700 MHz. Just sell it and get a phone for T-Mobile.
Sent from my XT862 using XDA App
BenSWoodruff said:
The only thing I've seen that works is using the xt883 Chinese ROM and it only gets edge. Edge is fine for me, but I want a better ROM with access to Android market.
Im still learning how this device works; I just installed Safestrap and tried to flash the GSM CM7 ROM today, to no avail. I flashed a custom ROM on my Droid 2 last year, but it's been a while on the G2x which isn't as locked down.
I flashed the CM7 GSM ROM on the safe mode partition, thinking that was how to do it, but I got an error trying to back anything up because /system wouldn't back up. Then when I flashed the ROM it wouldn't boot. Im wondering if I was supposed to flash the ordinary CDMA CM7 first, then use the GSM one, since it's named 3gedit.zip. I haven't tried that yet though, and the fact that /system isn't backing up worries me. I didn't create a partition on internal with Safestrap, but I flashed the GSM CM7 ROM from coreless in safe mode and it wouldn't boot. Got back to non-safe mode and my stock ROM was fine, but I still want to see a good back up :-/
Any ideas from more experienced users would be great. I'm pretty much a blind guinea pig right now lol. I just really want to see CM7 on this D3, and have it work on T-Mobile so I can retire my G2x for a little while.
Thanks in advance
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
go here http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
Thanks for replying. That's where I wound up going on my own because I was trying to use his CM7 last night. Can't seem to get it to flash though. Backing up with Safestrap isn't working either...getting an error because /system won't backup for some reason.
I think I'm gonna flash everything back to stock, uninstall Safestrap, and try the above from the beginning. I'd like to see if I can at least get edge and below on T-Mobile using a US ROM.
Thanks again!
G2x with CM7
D3 stock for now, trying to get T-Mobile compatibility
anathema_forever said:
I would recommend unlocking, rooting, flashing the radio, and editing the build.prop.
1. Unlock or online sim card unlock code seller but less reliable.
a) Meet the following requirements:
* Must be a Verizon Wireless customer.
* The phone being unlocked must be active on a Verizon Wireless line of service.
* The line of service must be active at least 60 days.
* The line of service must be in good standing for the past 60 days.
* Only one SIM Unlock per line every 10 months.
b) If you don't meet one or more of the above requirements, call anyway. You may still get lucky.
Call 1-800-711-8300 (Verizon Global Support) and ask the representative for a SIM unlock. Occasionally a representative may not know exactly what you are referring to; make sure you are not transferred to a different department. You are in the right place. Explain that they should have a walkthrough on how to do this, and that it allows for the use of local, non-Verizon SIM cards while traveling abroad.
c) Insert a foreign SIM into the SIM card slot on the side of your phone and then enter unlock code.
4. root ----> http://www.psouza4.com/droid3/
5. safestrap and backup in case something goes wrong -----> http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
6. chinese radio ----> http://dropbox.com/u/25454276/radio.zip
7. flash radio ----> http://dl.dropbox.com/u/16206920/moto-fastboot-win32.zip
8. use something like root browser lite(free) to backup to sd card then edit your system/build.prop
I have called out, received a call and a text, I have checked my account information with the tmobile app on edge. I have been led to believe that its hardware that tmobile can only do edge since they use some non standard bands.
Credits:
flashing radio - http://forum.xda-developers.com/showthread.php?t=1360157
unlocking - http://community.vzw.com/t5/iPhone-4S/Verizon-iPhone-4S-SIM-UNLOCK-Tutorial/td-p/696707
safestrap - http://forum.xda-developers.com/showthread.php?t=1315982
Click to expand...
Click to collapse
So, I have a couple of lines on VZW, but they are all used by family members on my account, and I don't have a VZW SIM. The guy who sold me the phone said he already unlocked it, and I believe him, but is the SIM an issue and is there any way to know if the phone is still unlocked? Can an unlock be undone after wiping internal sd?
I'm asking because I think I can just not worry about that step, but I want to double check. I put it back to stock 2.3.4, now showing 5.6.890 xt862 instead of whatever the xt883 was. I did this to get rid of the previous owner's Google account. Edge, calling and text were working on T-Mo when I bought the D3 a few days ago. When I put my SIM in now, however, and change it to GSM/UMTS mode, there are no operators available when I tap on the list and of course it doesn't work yet. I understand this is due to putting it back on stock lol, but I'm gonna go ahead and try flashing the radio and seeing what happens.
It's already rooted using zergrush. Has safestrap and I can boot into it by rebooting/pressing menu, but my /system folder won't back up. That's the only sign that something is wrong other than the fact that no ROMs will flash in safe mode. I've already left comments on Hash's site, so I'm waiting over there too. Figured I'd pop in here again real quick
Thanks.
UPDATE (from the other forum):
My Droid 3 is working on T-Mobile for voice and text. This is exactly what I wanted. Got some great in-depth help on this one, especially from @tspx23. Thanks a ton! This will be my daily driver now until we switch to VZW, at which point this will turn into a back up, unless I fail to find something else worth a contract at that point lol.
I might write a guide later on if anyone wants it. The process is easier than it seems, as long as you have it in plain english lol.
Thanks to anyone who contributed to this!
Is it possible to mix this with a current rom instead of flashing a random Chinese one, like infuse with cm7 or liberty?
Tmo has horrible coverage and awful customer service. Cs is all nice to you but lies about everything constantly. They did nothing but screw me. That's the whole reason I'm on verizon now. At least now I have coverage and won't be lied to whether or not I have it, or be told to get wifi and then u can make calls since u don't have service.
Sent from my DROID3 using xda premium
I don't know of anyway besides a sim card to check if its unlocked and I am not sure a verizon one would ask for the sim unlock code even if it was locked but sim cards can be really cheap. If your phone was unlocked that will never be undone, if it was working on tmobile before you reverted to stock then it is unlocked, it would not have worked using tmobile otherwise.
are you using the latest version of safestrap, he released a bugfix version pretty recently? Could you be more descriptive of what you did while in safestrap?
It is not rom specific as far as I know, I am just using the stock one.
@Darksurf, I agree. I never had them but before I moved they didn't cover my old town. Verizon may be expensive but at least they tell you they will rape you at front and explain all charges.
Sent from my XT862 using XDA App
you can also try with at&t in full3g. As they have the same bands the d3 has
Enviado desde mi DROID3 usando Tapatalk
I will see tomorrow if this works with ICS
Radio and build prop edit
I'm staying on T-Mo till they go under. They are cheap and I have unlimited Edge, which is all I can get on this phone anyway lol. Only ten bucks a month for data, since I have an older package from before they tried to hike their rates.
My D3 is having some issues after I reboot, and sometimes just randomly, it will lose all signal and tell me that my preferred operator cannot be found or error connecting. I have been just rebooting and sometimes wiggling my SIM around to see if it fixes, and it does.
Only other thing that is a little weird is my phone thinks it's an xt883, even though I'm on the stock VZW ROM. I'm wondering if this is causing some issues that I'm not qualified to really diagnose lol. Usually after I reboot, I have some of my google apps' names in Chinese, but I'm not sure if that is from radio.img, new build.prop, or from changing my bloatware to .bak.
Also, be advised that if you remove bloat, conversations.apk breaks incoming text if it isn't seen by the system. I added .bak to the end of it and could send texts to my wife, but couldn't get any messages. I changed it back and texting works fine. I use Chomp SMS, but that didn't seem to matter.
Have fun
P/S: also, when choosing operators in settings, you have the option for T-Mobile 2G, AT&T 2G or 3G. Just to confirm ;-) probably because AT&T's 3G bands are the international standard, right?
when you flashed the stock rom back onto it did you delete the /system partition and do a factory reset on your device before you did it?
ericerk said:
Is it possible to mix this with a current rom instead of flashing a random Chinese one, like infuse with cm7 or liberty?
Click to expand...
Click to collapse
I'd love to see someone put these mods into a ROM, but I'm not sure if any of it is compatible with existing ROMs. I also accomplished this on stock. When I get around to flashing CM7 again (or trying to at least lol), I'll post about how it goes.
I'm thinking that when I wiped my phone, the unlock remained but the radio.img that was on the Chinese ROM was undone or lost. Flashing it was easy though, using cmd mentioned earlier in this thread. I just needed help figuring out how to set it up, since I'm a noob at command line lol.
After that, I downloaded adb and tried to use other commands I've found (which claimed to work, but didn't for me somehow) to change out the build.prop. This failure was likely my fault lol but I found it easier to just use Root Browser lite to back up my original build.prop then replace it with the modified one.
I figure that if my SIM doesn't work after flashing some other ROM, I'll just try the two main steps again and see if it works then. If anyone really wants to do this, it isn't too hard or not worth it in my mind. I also figure this phone will be relevant enough for a while longer, considering I am cool with Edge speeds, I certainly won't mind being stuck with VZW's 3G whenever we change over. I am in no hurry to get LTE battery suck or bulkiness either. I'll wait for a little more refining to be done on that end before I upgrade from this phone
I am interested in making the phone compatible on T-Mobile / ATT by flashing XT883 radio. I have one question: Will the "unlocking" turn the phone completely GSM phone so it can no longer work on CDMA network?
Thanks.
Probably until you flash the Verizon ROM back I would assume.
Sent from my XT862 using XDA App
No. XT883 is also CDMA compatible, so the ability to use CDMA should stay. You might need to do *228 though.
You unlock the phone via carrier unlock code, e.g. they give you a code via email or over the phone allowing your gsm functions to work with foreign sim cards (other than the one they come with). After getting the unlock code and flashing the xt883 radio.img (and changing/replacing your build.prop) you can still choose to use cdma. Flashing this radio (which I'm currently using on T-Mobile) doesn't make your phone incompatible with cdma and is reversible. You would simply have to flash the original radio.img and change back your build.prop, or just flash a regular cdma ROM. I plan to do this some time next year if/when T-Mobile goes under and my wife and I switch to Verizon. In the mean time, I only get edge on T-Mobile (using it on AT&T will get 3g), but I have cheap and unlimited data (legacy data plan $10) and a great phone with keyboard. I'm using the stock ROM, rooted, but will eventually try CM7 with the gsm tweak. I will likely have to reflash the xt883 radio.img and change my build.prop (I think).
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img
BenSWoodruff said:
You unlock the phone via carrier unlock code, e.g. they give you a code via email or over the phone allowing your gsm functions to work with foreign sim cards (other than the one they come with). After getting the unlock code and flashing the xt883 radio.img (and changing/replacing your build.prop) you can still choose to use cdma. Flashing this radio (which I'm currently using on T-Mobile) doesn't make your phone incompatible with cdma and is reversible. You would simply have to flash the original radio.img and change back your build.prop, or just flash a regular cdma ROM. I plan to do this some time next year if/when T-Mobile goes under and my wife and I switch to Verizon. In the mean time, I only get edge on T-Mobile (using it on AT&T will get 3g), but I have cheap and unlimited data (legacy data plan $10) and a great phone with keyboard. I'm using the stock ROM, rooted, but will eventually try CM7 with the gsm tweak. I will likely have to reflash the xt883 radio.img and change my build.prop (I think).
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img
Click to expand...
Click to collapse
i wasn't able to flash the chineese rom, idk why it just wouldn't let me :/
Please help. Just bought a new S5 & have a question about enabling native tethering
I just purchased from the daily steals special unlocked galaxy S5. Being that I am from Canada, and because the description of the phone was in error I did not realize I was purchasingThe AT&T version which is locked down. While I don't strongly feel the need to root the phone and customize it, I would like to still have full functionality which includes native tethering which on my plan, with my provider in Canada I am entitled to. My understanding is that this version of the phone has the tethering locked down to AT&T. Being that I have not taken ownership of the phone yet I do not know which firmware is installed on it to see whether or not the option of rooting the device on kitkat (and changing the tethering can be done) and then bringing firmware up to lollipop is an option. This is something important to me as I use this feature often.
I would like to ask the following questions:
1. Firstly I would like to know when phones are purchased new do they always have KitKat firmware on them for this model or were any of you who purchased the phone did it come with lollipop out-of-the-box? This is supposed to be a new unlocked model for sale. It is not a refurbished model.
2. Question is there a way to know based on the serial number on the outside of the box what the firmware is? The reason I am asking is because when I pointed out the error of the advertised description of the phone they told me I am entitled to return the phone without restocking fee if I have not opened it yet. That it is already on an unrootable firmware.
3. If by chance this phone is on lollipop, is it still possible to enable native tethering if I am unable to root the phone? I have seen mention on an earlier thread where people used ADB and were able to pull the tethering provision file modify it and push it back to the system which would then allow native tethering to work. I am just not sure if this was specific to pre-lollipop firmware. I have also seen somebody advertise on YouTube it he for a fee is providing the service to enable native tethering on the galaxy S5. However he is the only person I have seen mention this anywhere so I am not sure whether or not this is something that can be done without root. Does anybody have any experience having done this?
I am unfortunately in the awkward situation of having this phone currently be in the US and be brought back to me in the next few days. So I essentially have the weekend to make a decision as to what I should do. If anybody can provide me any insight I would greatly appreciated.
Anyone?
Sent from my SM-N910W8 using Tapatalk
Mine came with KitKat but if you connect to the wifi upon setup I believe they automatically update to Lollipop
I have a rooted G900-A connected to MetroPCS, and I downloaded an app from google play which unlocks the tethering function
OK so this is kind of weird. I just took ownership of my factory unlocked AT&T Samsung galaxy S5. I was dismayed to find when i opened the box and booted it up that it actually had the latest version of lollipop 5.1.1. What is very interesting however is I am in Canada it once I realized that I will not be able to root this device, I decided for fun to turn on the Wi-Fi hotspot and see if it would work and to my surprise and excitement the Wi-Fi hotspot worked with my Sim card for my Canadian carrier. So I don't know if this was a special version that was put out because this came factory sealed in the box it was a factory unlocked model the tethering was unlocked as well. It does have the AT&T bloatware on it but otherwise I am quite pleasantly surprised and happy as my primary reason for choosing to root the device was to enable hotspot. Does anybody suggest that I try to root this phone given that the hotspot is working.? Maybe this is a special version does not have the same locked boot loader as before? How should I proceed if I want to try?
This is the phone: https://shop.simplemobile.com/shop/en/simplemobile/phones/sm-moto-e5
1. Is there a way to root it?
2. Where can I find the stock firmware for it?
I can not get anything on the internet about this model
I have done quite a bit of searching online and prodding at this phone in various ways and have found no way to root it unlock it or even get third party manual camera controls.
It appears to be a Tracphone remarketed E5 with a lower resolution camera and a few other locked features (mostly software things). I can only picture that a lot of our problems rooting this phone and getting support (specifically in English) have to do with the fact that "technically" the US isn't even supposed to have an E5, but the E5 play and plus. Which is why we have a Nora Baseband, 8MP camera, Android 8.1, etc. All the features (That may produce or interact with radio emissions) are mismatched to match other "authorized devices".
There is a thread here that lists all the Nora devices as Plus models but "1920" from the same master list is a play model. This model is also listed only with non-contract carriers (appears to be mostly CDMA) woth remarlably little information on it and has a small customer base since most just get the plus.
Even Motorola won't touch it with unlock codes and such like they (supposedly) will the plus model. So I don't think this specific model will get much attention anytine soon, or possibly ever. But again, this is all "from my understanding". So I could definitely be completely wrong. There are guys here who know substantially more than I do on the matter.
This of course isn't to say I havn't enjoyed the only Snapdragon 400 series phone not to be completely piled with non-removable handcuffing UI clutter.
Same question about NETWORK UNLOCK.
So, first to correct myself. This model is now being used for other non-contract carriers, too.
Second, referring to the carrier unlock. That depends on exactly who your carrier is. Some are known for unlocking the day you pay for it in full, others are known to never unlock them even when you meet the requirements by delaying giving codes, rejecting authorization, or removing the ability to submit the code in the phone's firmware. However, most carriers fall in the middle and usually require some number of months of operation of the device on their network and it be paid in full etc. etc.
So, check with your carrier and if they won't unlock it you'll have to meet the requirements or wait for someone to come up with new methods to modify the partitions on the device and/or find a way to unlock the bootloader. Some people (once boot unlocked) have had success with flashing different carrier firmware to gain GSM sim unlock and use with other networks. I did it with an old Samsung ON5 once but our devices don't have near the unlock, root, and rom support lol.
Good Luck though! I hope you figure it out if I don't.
Hi, I'm having trouble trying to convert a LG V40 from ATT to Verizon. Got the LG V40 on a trade, it's an ATT model and only Verizon works at our house. I figured it would be easy enough to flash over to Verizon software, but apparently I can't comprehend it. I read a bunch of articles on how to flash the phone over, downloaded the LG drivers, LG UP, and the KDZ file.
Every time I try to load up LG UP, it gives me the LGUP can't load the model error. I tried to download the Uppercut program and it will let LG UP come up and once I select the KDZ file, it gets to 4% and closes the LG UP program.
From what I've read (I've only got 2 hours a day before or after work other than sleep), I guess I don't have the model file that LG UP is looking for to run. Can anyone point me in the right direction? If there's anything I didn't explain or that needs cleared up I'd be happy to explain better.
Thanks
The LG UP version that works with the 40 hasn't been released yet. I thought all that was needed was to swap out the SIM card? You could download the verizon apps off the store, and snooze the ATT ones.
Sent from my LM-V405 using Tapatalk
AFAIK ATT is GSM, Verizon is not. So you cant use Verizon on ATT device even if you flash firmware.
We don't have a way to flash anything in any way yet, so, leave your phone alone before you brick it.
Craddock87 said:
Hi, I'm having trouble trying to convert a LG V40 from ATT to Verizon. Got the LG V40 on a trade, it's an ATT model and only Verizon works at our house. I figured it would be easy enough to flash over to Verizon software, but apparently I can't comprehend it. I read a bunch of articles on how to flash the phone over, downloaded the LG drivers, LG UP, and the KDZ file.
Every time I try to load up LG UP, it gives me the LGUP can't load the model error. I tried to download the Uppercut program and it will let LG UP come up and once I select the KDZ file, it gets to 4% and closes the LG UP program.
From what I've read (I've only got 2 hours a day before or after work other than sleep), I guess I don't have the model file that LG UP is looking for to run. Can anyone point me in the right direction? If there's anything I didn't explain or that needs cleared up I'd be happy to explain better.
Thanks
Click to expand...
Click to collapse
well where are you located?
i have a Verizon v40 i can trade,
i have service with t mobile crap my Verizon v40 works with my t mobile sim card i just keep getting a lot drop calls. I cannot make calls on 4GLTE.
Hey,
I just unlocked my ATT LG V40 using a Verizon sim card here in NYC and works just fine. Once the unlock pin was set in, the phone restarted and showed on the Verizon network with 4G LTE icon.
Ebay has an unlock code guy selling it for $7 buck if you rather not deal with the headaches of switching or whatnot.
I was also able to disable 80% of the ATT bloat that comes with the phone and ready to go.
kasey348 said:
well where are you located?
i have a Verizon v40 i can trade,
i have service with t mobile crap my Verizon v40 works with my t mobile sim card i just keep getting a lot drop calls. I cannot make calls on 4GLTE.
Click to expand...
Click to collapse
Southern WV. Would be willing to drive some distance to just get the correct one.
I assumed that LG made one V40 and each carrier had a different rom, which would listen to their bands only, to save power.
AT&T has ended all their good plans and has focused on the $30 per month and up, which is 3x to 4x more than I was paying for family and employee phone plans with usable but limited data.
So, I want to flash my 4 lg v40 att phones to T-mobile, since the att firmware does not listen to band 71, which is the best band to have in most situations.
I learned how to use lgup and roms. I assumed that you should be able to just flash any att v40 with a v40 tmo rom. However, I get a cross error. More research led me to qfil files and tools that make building your own Linux look like an afternoon job.
degarb said:
I assumed that LG made one V40 and each carrier had a different rom, which would listen to their bands only, to save power.
AT&T has ended all their good plans and has focused on the $30 per month and up, which is 3x to 4x more than I was paying for family and employee phone plans with usable but limited data.
So, I want to flash my 4 lg v40 att phones to T-mobile, since the att firmware does not listen to band 71, which is the best band to have in most situations.
I learned how to use lgup and roms. I assumed that you should be able to just flash any att v40 with a v40 tmo rom. However, I get a cross error. More research led me to qfil files and tools that make building your own Linux look like an afternoon job.
Click to expand...
Click to collapse
I understand why u think flashing t-mo would help, but unfortunately t-mo is the only one u can't flash, unless the original phone was t-mo.
That's because t-mo signs / encrypts the partitions and if u try to use them, u could brick any other phone (other than t-mo).
But to help with your problem, it's best to use the US Open rom (which I believe only came out up to a9, not a10).
Using that rom, you'll have volte, vowifi, and band 71. And, no specific carrier bloat. Some LG bloat, but not much.
cheers
What I am reading on other threads is that if I had a tmo firmware, I wouldn't be able to flash. Also, that no one made an open att firmware, much less with band 71.
I followed the instructions for cross flashing on https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/page-1
It failed, as others with att failed. Then one guy got the older lg command line to work. I followed those instructions (although the instruction page had 3 typos on it, after an hour and a half I found a youtube video without the typos). The command line failed, without any dialog. I assume more cross flashing prohibition.
I see att firmware, but it isn't open, and band 71 is missing. The only reason to flash is for band 71, otherwise my phone is carrier unlocked, but with band 71 disabled.
I am 97 percent sure I did everything right, including trying about 7 kdz's. I enabled oem unlocking, usb debugging. It is download mode, although the ui lgup is perfectly capable of putting the phone into download mode. I installed all the dlls, and other files.
However, lg up is compaining it can't load new file. I read it is no big deal, but I assume it has to do with the crossflashing config file, and perhaps this is the problem.
I see I can't dump with lgup, which I assume is something only paid up developers can do.
My phone wouldn't root, using any methods. So I am wondering if att has something locked down stopping root or this firmware flash. Maybe in the hidden settings (*#546368#*405#), but I can't make head or tails of anything in those cyptic service menus, even though I explored every menu in detail.
Threads on qfil look like they are written by very advanced cell programmers, and nothing makes any sense. I vaguely get the sense that in addition to the 3 or 4 android partitions (data, system, cache, user) there are scores of hidden phone partitions, which I could dump, if I had a patched version of lgup which probably only a few people have. qfil editing or saving looks linux based, and could take years to learn. And qfil editing probably would brick the phone since any experienced expert in any field has many botched jobs behind them. Of course this doesn't make sense, beyond partion resizing and cloning, to me.
The huge problem is that there are 6 variants of the phone and 4 carriers (formerly), so very few people like me have this variant, switched to tmobile, and realize that they are being screwed because the most important band (for traveling people and fringe area people) for tmobile is missing. My phone has mostly been using band 12, which I asssume is the second farthest reaching band. I thought I bought 4 lg v 40 phones with band 71, but I was mistaken.
I guess the only thing yet to try, is to uninstall all the lg up related stuff and reinstall. I have been searching so many threads, tying everything, maybe there is a sw conflict. Maybe an registry setting and malformed location pointer there to the config file? Who knows. Maybe, I am reading correctly, that if you have an att v40, you are stuck without band 71.
degarb said:
What I am reading on other threads is that if I had a tmo firmware, I wouldn't be able to flash. Also, that no one made an open att firmware, much less with band 71.
I followed the instructions for cross flashing on https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/page-1
It failed, as others with att failed. Then one guy got the older lg command line to work. I followed those instructions (although the instruction page had 3 typos on it, after an hour and a half I found a youtube video without the typos). The command line failed, without any dialog. I assume more cross flashing prohibition.
I see att firmware, but it isn't open, and band 71 is missing. The only reason to flash is for band 71, otherwise my phone is carrier unlocked, but with band 71 disabled.
I am 97 percent sure I did everything right, including trying about 7 kdz's. I enabled oem unlocking, usb debugging. It is download mode, although the ui lgup is perfectly capable of putting the phone into download mode. I installed all the dlls, and other files.
However, lg up is compaining it can't load new file. I read it is no big deal, but I assume it has to do with the crossflashing config file, and perhaps this is the problem.
I see I can't dump with lgup, which I assume is something only paid up developers can do.
My phone wouldn't root, using any methods. So I am wondering if att has something locked down stopping root or this firmware flash. Maybe in the hidden settings (*#546368#*405#), but I can't make head or tails of anything in those cyptic service menus, even though I explored every menu in detail.
Threads on qfil look like they are written by very advanced cell programmers, and nothing makes any sense. I vaguely get the sense that in addition to the 3 or 4 android partitions (data, system, cache, user) there are scores of hidden phone partitions, which I could dump, if I had a patched version of lgup which probably only a few people have. qfil editing or saving looks linux based, and could take years to learn. And qfil editing probably would brick the phone since any experienced expert in any field has many botched jobs behind them. Of course this doesn't make sense, beyond partion resizing and cloning, to me.
The huge problem is that there are 6 variants of the phone and 4 carriers (formerly), so very few people like me have this variant, switched to tmobile, and realize that they are being screwed because the most important band (for traveling people and fringe area people) for tmobile is missing. My phone has mostly been using band 12, which I asssume is the second farthest reaching band. I thought I bought 4 lg v 40 phones with band 71, but I was mistaken.
I guess the only thing yet to try, is to uninstall all the lg up related stuff and reinstall. I have been searching so many threads, tying everything, maybe there is a sw conflict. Maybe an registry setting and malformed location pointer there to the config file? Who knows. Maybe, I am reading correctly, that if you have an att v40, you are stuck without band 71.
Click to expand...
Click to collapse
As mentioned in my previous comment, to you, I can only assume you read, the easiest way for u to get band 71 would be to flash the US Open android 9 kdz.
AsItLies said:
As mentioned in my previous comment, to you, I can only assume you read, the easiest way for u to get band 71 would be to flash the US Open android 9 kdz.
Click to expand...
Click to collapse
This doesn't work, I am getting crossd error. Of course the error that it couldn't load new file doesn't make me confident in the accuracy of the guide, despite reading that we can ignore this error from lgup.
I am 100 percent I did everthing correctly, from enabling oem unlocking to debug mode. All drivers, com ports working. I tried about 9 kdz's or more. I obviously ignored any firmware without band 71.
I am reading that there is not any att open firmware anyway, because no one in the company leaks the code.
This phone apparently doesn't have a bootloader, and so the bootloader can't be unlocked. But that should only affect the rooting ability.
I can't see how att would have locked flashing from the bootloader, it seems to me that they would have had to do it deeper in the phone. so far, about the only hidden dialer code that work is *#546368#*405# (other than 2 others), this yield a very technical service menu that seems purposely obfuscated, so only a tech with an inhouse manual knows what these menus can do. I can only make out of few menu items' purpose. But nothing useful that I understand.
degarb said:
This doesn't work, I am getting crossd error. Of course the error that it couldn't load new file doesn't make me confident in the accuracy of the guide, despite reading that we can ignore this error from lgup.
I am 100 percent I did everthing correctly, from enabling oem unlocking to debug mode. All drivers, com ports working. I tried about 9 kdz's or more. I obviously ignored any firmware without band 71.
I am reading that there is not any att open firmware anyway, because no one in the company leaks the code.
This phone apparently doesn't have a bootloader, and so the bootloader can't be unlocked. But that should only affect the rooting ability.
I can't see how att would have locked flashing from the bootloader, it seems to me that they would have had to do it deeper in the phone. so far, about the only hidden dialer code that work is *#546368#*405# (other than 2 others), this yield a very technical service menu that seems purposely obfuscated, so only a tech with an inhouse manual knows what these menus can do. I can only make out of few menu items' purpose. But nothing useful that I understand.
Click to expand...
Click to collapse
If you read the comments in the Specific guide for doing this, you'll find where the 'crossd error' is resolved.
If u have trouble with that guide, ask questions in that guide. That's where the answers are and where people who have done it will answer. I can assure you it does work. I've done it.
Hey all! Forgive my ignorance, it's been a long time since I've done anything with firmware on Android phones (since I flashed a custom ROM to my Motorola Droid X about 10 years ago, lol). I've been poring over these forums for a few hours now and trying to piece some information together, but I could really use a hand from some more experienced folks.
Here's my situation: I'm in the U.S. I own an AT&T SM-N950U, and a Verizon SM-N950U. The Verizon phone is no longer being used (since April of 2018). I accidentally dropped the AT&T phone and heavily damaged the screen/digitizer and chassis, and would like to go back to using the Verizon phone, but on AT&T's network. I swapped the AT&T SIM to the VZW phone, and I was surprised to see that after a reboot, the AT&T splash screen came up, and after a factory reset, acted just like a new AT&T phone. It will send and receive data, SMS, and phone calls. However, the phone is still running Oreo, and when I tried to update it through OTA or through Samsung Smart Switch, it said that the phone was up to date. A little digging in the settings shows me that the phone is still considered a VZW-branded phone (ATT/ATT/VZW), and I believe this is the reason why I'm not able to receive the OTA updates. I also noticed that I no longer get 5G service, and I'm worried that there may be other functions missing too. I've seen BlueFox721's guide on carrier switching, and decided to do a bit more research before making an attempt, but I figured I would ask some questions.
First off, my main goal is to get this VZW Note 8 to work with all intended functionality of an up-to-date AT&T Note 8, including future OTA updates, bloatware, the whole deal. Is this actually possible?
If it is possible, can it be done without tripping Knox and hindering Samsung functionality?
I've read that root isn't possible with any bootloader past v3... I'm running v4 (N950USQU4CRF3). Is root necessary to switch carriers, or is it as simple as flashing an AT&T firmware with a newer bootloader version than what I currently use?
Again, I know a lot of this information is out there, but there's just so much to comb through I thought it might be better to just ask in regards to my particular situation, in case I'm not understanding something correctly. Any help would be greatly appreciated!