Develop Bugs

How to fix 3G/2g after debrandig/flashing

(NOTE: You need to backup the files before you install a diferent rom)
This will help you keep the 2G/3G settings (WCDMA) for you country after debranding or flashing another ROM.
Im from Portugal and I bought an orange UK flipout from ebay. Once I got it the first thing I did was debrand it and installed the non-motoblur version found in the debranding guide. I noticed that I did not have 2G network, since when I changed it to 2G I would loose all network.
After reasearching in a lot of forums I found a solution:
- Before changing the original rom (if you live in the country where you bought the phone) backup these files from /etc/motorola/bp_nvm_default:
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init
- After you install a new rom (if you notice that your network is working wierd) just replace the files in the new rom for the ones you backed up previously (Dont forget to check the files permissions after) and reboot.
In case you get stuck in a boot loop you might have forgot to copy one of the files or forgot to change the files permissions. Solution is to flash again (for me at least, maybe you can change it using adb);
[What I did was:
- I installed the rom with the frequencies I wished;
- backed up the files above;
- Installed the non-motoblur rom;
- Replaced the files with the back up ;
- Checked the files permission;
- Reboot.
Voila, I have 2G and 3G working perfectly]
(You have to have ROOT and I used root explorer)
This will allow everyone to install the non-motoblur version in their phones withought loosing their coutrys network frequecies.
Since the new update from motorola aparently corrects reception, maybe someone can share these files after they aplyed the update? In case you do, please specify where your from and if you know the frequencies your countries network works on, e.g. Portugal, 850, 900, 2100.
Sharing the original ones might help someone too, so please go ahead. I'll share the ones from the Italian rom (according to the debrand guide have the most frequencie support, once I get home)
Hope this helps !
(NOTE: You need to backup the files before you install a diferent rom)
[Just in case your wondering, I got this from this guide:
http://www.simply-android.com/discu...-3g-after-flashing-the-wrong-firmware/#Item_5 ]

Hmm.. Interesting.
But I was wondering..
/etc seems to be a symlink to /system/etc , wouldn't it be better to edit the files in /system/etc to make it more clear? (the results are pretty much the same, though)

You probably right but I dont have that kind of knowledge...
If you think its better I can change the location in the post?

Bartleby said:
You probably right but I dont have that kind of knowledge...
If you think its better I can change the location in the post?
Click to expand...
Click to collapse
Nah.. It seems to me that /etc is just a symbolic link to /system/etc
while the rootfs (/) is just a ram image.
Editing whatever from /etc is just the same as editing stuff from /system/etc

i have problem with rom for italy and uk with motoblur. when i installed is i dont have range 2G, only on deblur rom it work properly. do that method works with my situation? on chinese rom i dont have this problem

Yes, that was my issue too

ATT files
can someone please post these files for the att flipout, my phone is stuck in a boot loop and I fear the only way to fix it would be to flash one of the roms, in which case I would really like to have 2g

How you check "file permissions"?
I'm using this on Linda File Manager.
UPDATE: Thanks anyways ROOT EXPLORER Solved the permission stuff.
I'm trying this on a Telus Charm that was flashed with a T-Mobile ROM. Everything works OK apart from the phone (calling) functions.
I do have another Telus Charm working properly to get the files.
But every time I put the file on the folder the phone restarts and I have to do a factory reset; I modified permissions so the look just as the phnes in the original folder (on my Charm rw-r--r--) but still my phone still don't get signal. The only file I can't find on my working Telus Charm is generic_pds_init so I can't replace it on the other phone.
Best Regards.
Best Regards.

MGA2009 said:
How you check "file permissions"?
I'm using this on Linda File Manager.
UPDATE: Thanks anyways ROOT EXPLORER Solved the permission stuff.
I'm trying this on a Telus Charm that was flashed with a T-Mobile ROM. Everything works OK apart from the phone (calling) functions.
I do have another Telus Charm working properly to get the files.
But every time I put the file on the folder the phone restarts and I have to do a factory reset; I modified permissions so the look just as the phnes in the original folder (on my Charm rw-r--r--) but still my phone still don't get signal. The only file I can't find on my working Telus Charm is generic_pds_init so I can't replace it on the other phone.
Best Regards.
Best Regards.
Click to expand...
Click to collapse
When I first tryed this I thought that some files were not needed so i would get stuck in a bootloop. If that file does not exist try to find one that might be the same (similar name?) That file must be important and related to the others. Worst case scenario maybe try copying the entyre folder?

A quick warning - using Motorola Charm (not flipout) it seems that once you flash the T-Mobile ROM no other ROM will work (it updates the bootloader with a locked one). So avoid T-Mobile unless you it's you only solution.
It might be the same point-of-no-return issue on Flipout.

dvfk said:
A quick warning - using Motorola Charm (not flipout) it seems that once you flash the T-Mobile ROM no other ROM will work (it updates the bootloader with a locked one). So avoid T-Mobile unless you it's you only solution.
It might be the same point-of-no-return issue on Flipout.
Click to expand...
Click to collapse
This Telus Charm was semi bricked because I flashed the "de blured" SBF and I could only get to bootloader.
After I flashed T-Mobile SBF I've a semi working phone, as everything works apart from the phone functions.
This is only for 3G? I'm not getting neither 2G nor 3G.
Am I missing any file/folder?
Best Regards.

Hi Guys!
Sadly I saw this post too late.
I flashed my wifes Flipout with the deblurred ROM from the Orange debranding guide.
Now we also have got the missing 2G problem.
I´d really appreciate it if is were somebody out there who could upload the correct baseband files for Germany.
Thanks in advance,
Moe
Update:
Found the baseband config files here: http://dext3r.komodin.org/ (bottom of page)
I´ll also append them to this post for your convenience.

German Baseband files:

Bartleby said:
(Dont forget to check the files permissions after)
Click to expand...
Click to collapse
Which permissions should be given?
In doubt is it okay to set permissions to everyone?
chmod xyz filename. What is xyz?

moritz.narnhammer said:
Hi Guys!
Update:
Found the baseband config files here: http://dext3r.komodin.org/ (bottom of page)
I´ll also append them to this post for your convenience.
Click to expand...
Click to collapse
Hi, I'm from Germany and can confirm that these files not working for german Motorola Flipout devices on O2 network with deblured US version. Use the uk files mentioned in ITA/FR/etc. Thread instead!

I have the same problem. I have a samsung gt 5830i phone. Where do I download the file? So I can have a 2g signal.

[GUIDE][09-12-2011] XOOM 3G Euro Root Instructions + Files[3.2-UPDATE]

I have rooted the boot image from my XOOM, this is a UK 3G XOOM, DO NOT USE if you are NOT 3G, or use at your own risk, attached.
Before you proceed you will need to unlock your bootloader, note this will erase all of your data, you have been warned!
UPDATE for 3.2
Use the following to get root on your 3.2 updated euro xoom. Please note, the modules here from the earlier boot image are most probably not functional anymore. I will try get an updated set. For now, here are the instructions, the new boot image is attached to this post.
Get the boot_3.2_insecure.zip from this post which also contains an su binary i just compiled.
Code:
adb reboot bootloader
fastboot oem unlock
Follow the on screen instructions!
Extract the files into you current directory, then reboot into fastboot mode and do:
Code:
fastboot flash boot boot.img
fastboot reboot
This will get you a rooted bootloader but you still aren't rooted yet, get a prompt or terminal open in the folder where the root_files are from the attached zip you will need the su file.
Make sure you have a computer with adb set up then from the computer perform the following commands with the xoom connected:
Code:
adb remount
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
NEXT: Go to the Market and install "Superuser" by ChainsDD and you will probably want to install busybox too.
Congratulations on rooting your euro 3G XOOM all by yourself, and remember "one click" is for noobs who like to brick their devices (like me) don't do it.
OLD Modules(tun/cifs/etc) 3.0.1:
Code:
I have attached an archive containing cifs.ko, tun.ko, nls_utf8.ko, option.ko
and usb_wwan.ko with correct version magic. I did not compile them,
and I can not provide others (unless I can find them).
How to use:
Copy the modules to "/system/lib/modules", reboot.
If you don't know how to do that, you probably shouldn't be using them.
Disclaimer: I take no responsibility if either this boot image, the tutorial, or the files attached murders you violently, in fact, don't even use them.

alias_neo said:
Guys, I have been through this process, STOP using the US root instructions and images, they don't work on the european 3G XOOMs.
I have boot and recovery images that I need someone with a little experience to contact me about testing before I can release them to anyone else as working.
If a mod could sticky this please to stop people bricking their euro XOOMs until I can get the images tested and get a dump of the recovery partition!
Click to expand...
Click to collapse
As an aside, it's pretty damn obvious from the Wi-Fi/CDMA malarkey that flashing the wrong boot image for the wrong model is bad, especially without stock images.
Did you actually rip the stock boot image? (How'd you manage it?) Can you just post it somewhere? It should be a simple matter to make a root boot image from it.
If there's been an OTA update for the UMTS Xoom already, and you have a recovery-from-boot.p binary patch and the boot image, you can make the recovery image by using applypatch.
I don't have a device yet, sadly, so I can't test yet.

ydaraishy said:
As an aside, it's pretty damn obvious from the Wi-Fi/CDMA malarkey that flashing the wrong boot image for the wrong model is bad, especially without stock images.
Did you actually rip the stock boot image? (How'd you manage it?) Can you just post it somewhere? It should be a simple matter to make a root boot image from it.
I don't have a device yet, sadly.
Click to expand...
Click to collapse
Well, dumping the stock boot was easy enough once recovery partition was sacrificed, you just boot off of that, as for the boot.img I have a rooted boot image that I created, I'll post it here so hopefully some of you can unbrick (as long as you didn't overwrite system too).
I won't post system until it's been tested because that wasn't a simple flash to restore.

alias_neo said:
Well, dumping the stock boot was easy enough once recovery partition was sacrificed, you just boot off of that, as for the boot.img I have a rooted boot image that I created, I'll post it here so hopefully some of you can unbrick (as long as you didn't overwrite system too).
I won't post system until it's been tested because that wasn't a simple flash to restore.
Click to expand...
Click to collapse
Yeah, but what did you flash to recovery? The kernels from source, last time I looked, seemed like they didn't have mods for the UMTS model yet.

ydaraishy said:
Yeah, but what did you flash to recovery? The kernels from source, last time I looked, seemed like they didn't have mods for the UMTS model yet.
Click to expand...
Click to collapse
I flashed a stock 3G boot image that I rooted myself.

alias_neo said:
I flashed a stock 3G boot image that I rooted myself.
Click to expand...
Click to collapse
Ah, got you. Thanks for the info.

The attached boot img MIGHT work for root (unpacked, set ro.secure to 0, repacked).
(ed. If this works, then the guinea pig who flashes it can easily rip a stock recovery from this, if it hasn't been clobbered already.)

ydaraishy said:
The attached boot img MIGHT work for root (unpacked, set ro.secure to 0, repacked).
(ed. If this works, then the guinea pig who flashes it can easily rip a stock recovery from this, if it hasn't been clobbered already.)
Click to expand...
Click to collapse
I already included a working rooted boot image in the first post...
Sent from my HTC Desire using Tapatalk

alias_neo said:
I already included a working rooted boot image in the first post...
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Oops, you're right; I thought you said you had the stock boot image, which is why I got confused.

Xoom Brazilian 3g and wifi
ydaraishy said:
The attached boot img MIGHT work for root (unpacked, set ro.secure to 0, repacked).
(ed. If this works, then the guinea pig who flashes it can easily rip a stock recovery from this, if it hasn't been clobbered already.)
Click to expand...
Click to collapse
In brazilian 3g gsm and wifi works fine tks

rickjardim said:
In brazilian 3g gsm and wifi works fine tks
Click to expand...
Click to collapse
May can you give me a your framework-res.apk file?
Thanks so much

Well, it seems to work - tried on my UK 3G model. The problem is that my 3G no longer works - I try to activate it and it just sits there on "searching for service" and "activation can take a few minutes" with nothing happening.
Wifi etc. works BTW. I may have accidentally overwritten something as I managed to semi-brick it before realising that the US images wouldn't work.
Anyone have any ideas?

mlokane said:
Well, it seems to work - tried on my UK 3G model. The problem is that my 3G no longer works - I try to activate it and it just sits there on "searching for service" and "activation can take a few minutes" with nothing happening.
Wifi etc. works BTW. I may have accidentally overwritten something as I managed to semi-brick it before realising that the US images wouldn't work.
Anyone have any ideas?
Click to expand...
Click to collapse
You have done what I did. There is no such thing as activation on a UK xoom 3g. You have overwritten the system partition with the US one and you will need the stock UK System image. I have one but I had trouble getting it to work and I wont be posting it until it has been tested. You are welcome to be the ginea pig, and this is the only way you'll get your xoom back to UK and get 3g wworking again, believe mem iv been there.
Macbots drool as I XOOM through the Galaxy to my hearts Desire on the back of a Droid.

alias_neo said:
You have done what I did. There is no such thing as activation on a UK xoom 3g. You have overwritten the system partition with the US one and you will need the stock UK System image. I have one but I had trouble getting it to work and I wont be posting it until it has been tested. You are welcome to be the ginea pig, and this is the only way you'll get your xoom back to UK and get 3g wworking again, believe mem iv been there.
Macbots drool as I XOOM through the Galaxy to my hearts Desire on the back of a Droid.
Click to expand...
Click to collapse
Ah - that makes sense. Well the US system image I have works fine except for the 3G access, so if I try and flash this uk system image onto my xoom and it doesn't work can I still flash the old US one back again easily? As it's a new xoom and I haven't installed anything on it I'm fine with being a guinea pig as long as it won't completely brick!

mlokane said:
Ah - that makes sense. Well the US system image I have works fine except for the 3G access, so if I try and flash this uk system image onto my xoom and it doesn't work can I still flash the old US one back again easily? As it's a new xoom and I haven't installed anything on it I'm fine with being a guinea pig as long as it won't completely brick!
Click to expand...
Click to collapse
Yep, I was in the same position, the US version works fine but no 3G cause it's built for a CDMA device. The stock system image I flashed would not boot so I had to relock and then unlock again the device to fix the permissions for it to boot again.
If your confident you can relock and unlock again the device after flashing this image PM me and i'll get the system image to you to test, I won't be around to help though if it goes wrong cause I'm at work so make sure you're confident first.

alias_neo said:
Yep, I was in the same position, the US version works fine but no 3G cause it's built for a CDMA device. The stock system image I flashed would not boot so I had to relock and then unlock again the device to fix the permissions for it to boot again.
If your confident you can relock and unlock again the device after flashing this image PM me and i'll get the system image to you to test, I won't be around to help though if it goes wrong cause I'm at work so make sure you're confident first.
Click to expand...
Click to collapse
PMed now - we can update this thread if it works...

i'm trying to do the opposite, I'm looking for euro gsm images, to flash into my verizon 3g/wifi version. The goal is to verify if, once flashed, the us xoom can work with european 3g networks ( for sure it has a world radio chip, same used in the verizone ip4).
If anyone has got a dump pm please.
Thanks in advance.
M.

aefelix said:
i'm trying to do the opposite, I'm looking for euro gsm images, to flash into my verizon 3g/wifi version. The goal is to verify if, once flashed, the us xoom can work with european 3g networks ( for sure it has a world radio chip, same used in the verizone ip4).
If anyone has got a dump pm please.
Thanks in advance.
M.
Click to expand...
Click to collapse
I doubt it will work, I tried Verizon on my UK 3G and there was no radio detected. They may have the complete hardware available but the baseband probably takes care of access the correct hardware.

alias_neo said:
I doubt it will work, I tried Verizon on my UK 3G and there was no radio detected. They may have the complete hardware available but the baseband probably takes care of access the correct hardware.
Click to expand...
Click to collapse
That make sense, but a complete euro 3g system dump could do the job...I'm investigating on harware differencies on the euro/usa versions, if they are the same , ther's no apparent reason that could not allow me to push a euro version rom on the verizon one (with a good dose of luck and tech skills )

aefelix said:
That make sense, but a complete euro 3g system dump could do the job...I'm investigating on harware differencies on the euro/usa versions, if they are the same , ther's no apparent reason that could not allow me to push a euro version rom on the verizon one (with a good dose of luck and tech skills )
Click to expand...
Click to collapse
I flashed a complete Verizon dump on mine and everything worked except the radio, so I imagine it would be the same the other way around. By all means though give it a go, bear in mind they are different models and so most likely have hardware differences (no LTE upgrade in europe).

[APP] Orange Quick Tap NFC payments apk

I've pulled and attached the apk file for the Orange Quick Tap application. Unfortunately, I've only been able to get it to install on Galaxy S3s. If anyone is skilled enough to get it to install on a Galaxy Nexus (I think there are device checks in the apk?), please have a go.

Almost 30 of you have downloaded this, yet not a single comment? Come on!

Hi,
I installed it on my htc one x but it needs a quicktap sim, I'm going to order one and let you guys know what it says

Can't seem to get it installed on my S3. Moved it to system/app changed permissions but wouldn't install. Rebooted and same story.

That helps. I think that suggests that this apk doesn't actually have a device check. The reason why it's not installing on my Galaxy Nexus is probably due to a missing dependency, which I believe to be the Open Mobile API.
The Open Mobile API is used by many manufacturers to enable the use of special SIM cards as an NFC secure element for payments and other things. Google have not included this API in stock Android, as they want to limit Nexus devices to just the embedded secure element. Compare that to the Galaxy S3, which is confirmed to be able to use the MicroSD, SIM and its embedded secure element.
To test this, could people with any stock software NFC-enabled Samsung (non-Nexus), HTC or Sony device try to install the apk? I'd expect it to install on any ISIS-certified phone for example. And then to confirm that the API is the issue, could someone who has installed an AOSP stock ROM (which shouldn't support the open mobile API) onto their GS3, One X or Xperia S try to install the Quick Tap apk? If I'm right, it won't install on those ROMs.

RichySamui said:
Can't seem to get it installed on my S3. Moved it to system/app changed permissions but wouldn't install. Rebooted and same story.
Click to expand...
Click to collapse
What ROM are you running on your S3?

Right rang up orange and they are not giving put nfc sim cards unless you are a new or upgrading costumer
Sent from my HTC One X using xda premium

Installs fine on stock unbranded SIII.
When ran, says checking for services
Then says "Sorry, you need a quick tap sim card in order to use the quick tap wallet" with customer service numbers to call 150 PAYM/450 PAYG

Alright, thanks. Now we need someone with a STOCK (no TouchWiz) AOSP CUSTOM ROM, e.g. CM9/CM10 on a SIII, One X or Xperia S to see what happens.

Rooted HTC One X with ARHD. Installs with no issue but falls over at the Sim card required stage. I'm going to give Orange a call and see what they say.

dr9722 said:
Rooted HTC One X with ARHD. Installs with no issue but falls over at the Sim card required stage. I'm going to give Orange a call and see what they say.
Click to expand...
Click to collapse
Unfortunately ARHD is based on the stock HTC ROM. Does anyone have one of the phones I've listed above, but running CM9 or CM10?

I tried to install it on my rooted GNex with stock 4.1.1 JB.
Put it into the download folder then went to install it it and it just says "app not installed"
Can someone tell me why it wont install, what the problem is?
I am on Orange UK.

sferg.410 said:
I tried to install it on my rooted GNex with stock 4.1.1 JB.
Put it into the download folder then went to install it it and it just says "app not installed"
Can someone tell me why it wont install, what the problem is?
I am on Orange UK.
Click to expand...
Click to collapse
I've already explained why it won't install. Stock Android doesn't have some components that this application requires for communication with the SIM. Furthermore, it's very possible that this application will never work with the Galaxy Nexus, as Google might have physically removed the connection between the SIM and the NFC controller - forcing Nexus users to be limited to only Google Wallet. Many people don't realise that Google are actually quite anti-competitive.

Guess I better get a Galaxy S3 LTE then.

I have a nfc sim card from starhub. Dk if it will work
Sent from Gnex with AndroidME CM10 ROM

sferg.410 said:
I tried to install it on my rooted GNex with stock 4.1.1 JB.
Put it into the download folder then went to install it it and it just says "app not installed"
Can someone tell me why it wont install, what the problem is?
I am on Orange UK.
Click to expand...
Click to collapse
It won't install because it's a system app. Push it to /system/app instead.

Rusty! said:
It won't install because it's a system app. Push it to /system/app instead.
Click to expand...
Click to collapse
ok did that and tried to install it. got "parse error" as a result.
thanks anyway.

Rusty! said:
It won't install because it's a system app. Push it to /system/app instead.
Click to expand...
Click to collapse
That's not the issue. I've already mentioned twice that stock Android does not contain the dependencies that this application requires; that's why it won't install.

I understand that this orange app installs a barclays app - can you post the apk for this?

AMoosa said:
I understand that this orange app installs a barclays app - can you post the apk for this?
Click to expand...
Click to collapse
I don't have an S3, so I can't install this in the first place. Your signature lists you as owning an S3, so why don't you install it?

[Q] G2 LS980 (sprint) Roms

Ive been looking around the roms on the sprint section to find another stock rom that is already GSM unlocked so it can be used on t-mobile, like the Cyanogen11 one but cant find a definitive answer while reading through the roms and change logs of the roms. i know this might be a stupid anwsers and sorry if it is, but im not used to dealing with sprint phones and the TC method never worked for me when i have tried to do it and i have done it. any suggestios. thank you in advance.

I think for now it's a test it and keep a list of what works or if you try some post your results here I'm sure we are not the only two wondering this. cm11 works good great data speed for me on att but would also like a stock option.
Sent from my SAMSUNG-SM-N900A using Tapatalk

MrKickstand said:
Ive been looking around the roms on the sprint section to find another stock rom that is already GSM unlocked so it can be used on t-mobile, like the Cyanogen11 one but cant find a definitive answer while reading through the roms and change logs of the roms. i know this might be a stupid anwsers and sorry if it is, but im not used to dealing with sprint phones and the TC method never worked for me when i have tried to do it and i have done it. any suggestios. thank you in advance.
Click to expand...
Click to collapse
The TC method never worked for US carriers. Have you tried the build.prop edit method? Should not be dependent on the rom. For a stock rom I find OpTimuS DE excellent. I used it previously with the build.prop unlock and now with the permanent unlock (but I'm in Canada).

scottdanpor said:
The TC method never worked for US carriers. Have you tried the build.prop edit method? Should not be dependent on the rom. For a stock rom I find OpTimuS DE excellent. I used it previously with the build.prop unlock and now with the permanent unlock (but I'm in Canada).
Click to expand...
Click to collapse
What's the build. Prop method?

MrKickstand said:
What's the build. Prop method?
Click to expand...
Click to collapse
Use rom toolbox (or similar) to edit your build.prop... ***case sensitive!!!!***
ro.build.target_operator = SPR
reboot
ro.build.target_operator = OPEN
reboot, then
ro.build.target_operator = spr
reboot
The last one (spr) is done because you will get system UI crashes if you leave it as OPEN.

scottdanpor said:
Use rom toolbox (or similar) to edit your build.prop... ***case sensitive!!!!***
ro.build.target_operator = SPR
reboot
ro.build.target_operator = OPEN
reboot, then
ro.build.target_operator = spr
reboot
The last one (spr) is done because you will get system UI crashes if you leave it as OPEN.
Click to expand...
Click to collapse
Blah, that didn't work, even with the sprint Sim. When I use the LG tool to go back to stock on picks up some service with the sprint Sim.

MrKickstand said:
Blah, that didn't work, even with the sprint Sim. When I use the LG tool to go back to stock on picks up some service with the sprint Sim.
Click to expand...
Click to collapse
I don't follow. Why would you have a Sprint sim in the phone?? If you do this with a Sprint sim in the phone you will lose data. If you flash a rom or back to stock, you have to edit the build.prop again to activate gsm.

scottdanpor said:
I don't follow. Why would you have a Sprint sim in the phone?? If you do this with a Sprint sim in the phone you will lose data. If you flash a rom or back to stock, you have to edit the build.prop again to activate gsm.
Click to expand...
Click to collapse
Haha sorry I didn't mean to make that confusing. But it didn't work with the T-Mobile Sim either. The only time I have been able to get any type of service bars instead of a red x over it is when I put the sprint Sim in and go back to bare stock

Actually now when I put my T-Mobile Sim back in, it shows all the service bars Grey but can't choose and operator or send a text.

MrKickstand said:
Actually now when I put my T-Mobile Sim back in, it shows all the service bars Grey but can't choose and operator or send a text.
Click to expand...
Click to collapse
You can use the app Tweakker to enter your APN settings.

the phone wants to resort back to cdma for phone service, grab an app called telinfo from the play store and use it to set your phone to GSM (auto PRL), then set your APN to get data working, best of luck!

Help with my Default.XML

After flashing TWRP and Venom3.0 I started testing the various ROMs. Of course I was on a very small 8GB Micro after my SanDisk 64GB went corrupt (3years and a few washing machine and drier cycles) and made a newb move. Didn't think to save a backup pre/post unlock to the internal and just copy it onto my PC.
It wasn't until the next day that I realized I wasn't receiving calls. The phone would ring on the callers end but my phone would stay unaffected unless a vm was sent. I searched in the m9 and then overall xda for a solution to no avail. Once I used Gsearch with more vague terms I was only able to find one thread from a few years back when voice over LTE must have been kinda new.
Someone had the exact same problem, described my situation exactly and the fix proposed worked for the guy.
It was to modify the default.XML in system/customize/ACC
I switched all the "voLTExxx" values to "true" as they were all "false" and now callers are directed straight to vm. Im still completely unaffected in my phone abilities so I know I was close. All this is after I switched the the ATT dev edition ROM found here on XDA in one of the M9 stickeys.
Im thinking maybe someone with the same setup could upload their XML file that is working so I can check if it was that? Maybe that won't work but you know what will? Thanks guys.

Im seeing someone else posted just a few minutes ago and turning off LTE works. That is not a solution in my opinion and was the failsafe on the original post I read.

SeanMurphy said:
After flashing TWRP and Venom3.0 I started testing the various ROMs. Of course I was on a very small 8GB Micro after my SanDisk 64GB went corrupt (3years and a few washing machine and drier cycles) and made a newb move. Didn't think to save a backup pre/post unlock to the internal and just copy it onto my PC.
It wasn't until the next day that I realized I wasn't receiving calls. The phone would ring on the callers end but my phone would stay unaffected unless a vm was sent. I searched in the m9 and then overall xda for a solution to no avail. Once I used Gsearch with more vague terms I was only able to find one thread from a few years back when voice over LTE must have been kinda new.
Someone had the exact same problem, described my situation exactly and the fix proposed worked for the guy.
It was to modify the default.XML in system/customize/ACC
I switched all the "voLTExxx" values to "true" as they were all "false" and now callers are directed straight to vm. Im still completely unaffected in my phone abilities so I know I was close. All this is after I switched the the ATT dev edition ROM found here on XDA in one of the M9 stickeys.
Im thinking maybe someone with the same setup could upload their XML file that is working so I can check if it was that? Maybe that won't work but you know what will? Thanks guys.
Click to expand...
Click to collapse
The dev edition (617) ruu won't fix the issue. As far as voLte is concerned, it's basically the same as running a custom rom in that you can still be affected by the issue and you can't disable Ehanced (or HD) Voice in the rom (this is tied to your sim and not the rom, I think).
Currently, this is the best solution, I think...flash an att RUU (502 - either 1.32 or 2.6, it doesn't really matter) . Then go into Mobile network settings, and disable Enhanced Voice. Once this is disabled in stock ATT rom, you can flash a custom rom and that setting should stick.
Alternatively, you might try getting on with ATT support to see if they can disable that setting on their end.

Okay. Maybe post this to the thread from 8hrs ago because some of them are having the same issue. Ill get back when I try that, I am on 1.32 currently.

Quick questions before I proceed.
jollywhitefoot said:
The dev edition (617) ruu won't fix the issue. As far as voLte is concerned, it's basically the same as running a custom rom in that you can still be affected by the issue and you can't disable Ehanced (or HD) Voice in the rom (this is tied to your sim and not the rom, I think).
Click to expand...
Click to collapse
1.Why do you think it this doesn't work after I unlocked? What I mean is, with that value set to true, and everything works fine; what is in the flash that doesn't allow HD Voice?
jollywhitefoot said:
Currently, this is the best solution, I think...flash an att RUU (502 - either 1.32 or 2.6, it doesn't really matter) . Then go into Mobile network settings, and disable Enhanced Voice. Once this is disabled in stock ATT rom, you can flash a custom rom and that setting should stick.
Click to expand...
Click to collapse
2. I'm currently on 1.32 and I don't see that option anywhere despite being on this ROM. Which is now clear that it isn't the same thing as this RUU? I'm downloading the 2.6 RUU from HTC's website and will flash it as per their instructions (Thanks for the link by the way:highfive
3.Should I re-edit my XML file before the flash or is this RUU going to take care of that?
Also, I had to idea the info about your post wasn't copied in the text when I reposted this to that other thread. I'll delete if you prefer.

SeanMurphy said:
1.Why do you think it this doesn't work after I unlocked? What I mean is, with that value set to true, and everything works fine; what is in the flash that doesn't allow HD Voice?
2. I'm currently on 1.32 and I don't see that option anywhere despite being on this ROM. Which is now clear that it isn't the same thing as this RUU? I'm downloading the 2.6 RUU from HTC's website and will flash it as per their instructions (Thanks for the link by the way:highfive
3.Should I re-edit my XML file before the flash or is this RUU going to take care of that?
Also, I had to idea the info about your post wasn't copied in the text when I reposted this to that other thread. I'll delete if you prefer.
Click to expand...
Click to collapse
it didn't have anything to do with unlocking. You have voLte enabled for your att account and you're in an area that supports voLte, but you're running a rom that doesn't.
This is just my current theory. We'll see if it works for you.
I don't know what it will take for a custom rom to support voLte.
I didn't include a link because I thought it would be easy enough to find, but I guess most people here complain if they're not spoon fed.
Um...credit the source of the info or just link to my post. Don't just copy and paste as your own.
Anyway...carry on and please report back if it works for you.
Edit: oh, and forget the default.xml file. It's probably fine as is. I assume you got that from my post from a couple of months ago. I don't think that was the problem.

jollywhitefoot said:
it didn't have anything to do with unlocking. You have voLte enabled for your att account and you're in an area that supports voLte, but you're running a rom that doesn't.
This is just my current theory. We'll see if it works for you.
I don't know what it will take for a custom rom to support voLte.
Click to expand...
Click to collapse
Got it, is voLte an ATT exclusive feature in the U.S.?
jollywhitefoot said:
I didn't include a link because I thought it would be easy enough to find, but I guess most people here complain if they're not spoon fed.
Click to expand...
Click to collapse
You posted the link on the M9 resource thread where I was able to find it on my own, it was a genuine high five, and yes, I thanked that bit as well.
jollywhitefoot said:
Um...credit the source of the info or just link to my post. Don't just copy and paste as your own.
Click to expand...
Click to collapse
This is what I was attempting to explain; I'm not use to the XDA app UI and I didn't know it didn't include the info about the OP when I pasted in the text. Sorry for the confusion Jolly, I must've come off like the biggest assclown to ask for your time in a while. Your help IS appreciated and I have thanked some of your posts so far.
jollywhitefoot said:
Anyway...carry on and please report back if it works for you.
Click to expand...
Click to collapse
I'm stuck at the RUU actually, I have AV off and the install shield wizard loads up, flashed a few windows then shuts down. Sync is still installed, I've restarted my PC, ran as admin.
Do you know if HTC released that as a flashable .zip? I hate doing anything to my phone through my PC because it creates another variable to go wrong.
jollywhitefoot said:
Edit: oh, and forget the default.xml file. It's probably fine as is. I assume you got that from my post from a couple of months ago. I don't think that was the problem.
Click to expand...
Click to collapse
It was you

SeanMurphy said:
Got it, is voLte an ATT exclusive feature in the U.S.?
Click to expand...
Click to collapse
Yes, but only in some areas. Mostly larger cities right now
SeanMurphy said:
You posted the link on the M9 resource thread where I was able to find it on my own, it was a genuine high five, and yes, I thanked that bit as well.
Click to expand...
Click to collapse
Gotcha. I was like...what link?
SeanMurphy said:
This is what I was attempting to explain; I'm not use to the XDA app UI and I didn't know it didn't include the info about the OP when I pasted in the text. Sorry for the confusion Jolly, I must've come off like the biggest assclown to ask for your time in a while. Your help IS appreciated and I have thanked some of your posts so far.
Click to expand...
Click to collapse
No problem....just funny
SeanMurphy said:
I'm stuck at the RUU actually, I have AV off and the install shield wizard loads up, flashed a few windows then shuts down. Sync is still installed, I've restarted my PC, ran as admin.
Do you know if HTC released that as a flashable .zip? I hate doing anything to my phone through my PC because it creates another variable to go wrong.
Click to expand...
Click to collapse
It was you [/QUOTE]
I don't think there's a zip yet. I've had that happen a few times with ruu. Once it was antivirus. Another time or two it was a bad download.

jollywhitefoot said:
I don't think there's a zip yet. I've had that happen a few times with ruu. Once it was antivirus. Another time or two it was a bad download.
Click to expand...
Click to collapse
Wowwwwww was that an adventure.
Re-downloaded the ATT RUU and updating (bad download first time)
Disabled "HD Voice" under the mobile settings (easiest part of the whole show)
re-flashed TWRP (Ran into a million windows problems, had to perform clean windows install)
Flashed the same custom ROM I had before
Calls came through, everything working great.
Thanks again Jolly!!!!! I would be stuck with twitter eating 11% of my battery usage despite me not having a twitter account
:good::highfive::good::highfive::good::highfive: