Develop Bugs

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:

Lock Screen Missing Features

Hello everyone. I have recently discovered that my LG G3 (32 GB model, running Android 5.0) has some missing features in the lock screen. The "None" feature which disables the lock screen completely was missing but for some reason it showed up when I deleted the Guest in my phone. I also know from various photos on the internet that the LG G3 has a function where you can unlock your phone by letting it recognise your face. This "Face Recognition" feature is also missing and I haven't managed to find a way to get it back. Can someone help me?

MariosAga said:
Hello everyone. I have recently discovered that my LG G3 (32 GB model, running Android 5.0) has some missing features in the lock screen. The "None" feature which disables the lock screen completely was missing but for some reason it showed up when I deleted the Guest in my phone. I also know from various photos on the internet that the LG G3 has a function where you can unlock your phone by letting it recognise your face. This "Face Recognition" feature is also missing and I haven't managed to find a way to get it back. Can someone help me?
Click to expand...
Click to collapse
Face Recognition is removed from most of phones nowadays,because easily somebody else can unlock your phone with his face..
And as I've seen some companies are developing this feature.
For the "none" i think in 5.0 LG removed it.(I'm not really sure about that)well you can use "swipe" for now.
Also why don't you upgrade to 6.0?It has the "None" for the lock screen and also it has really great performance!

Yeah well I've tried to upgrade it to Marshmallow but I don't know how. I tried LG pc suite but that didn't work. Do you know how to do it?

MariosAga said:
Yeah well I've tried to upgrade it to Marshmallow but I don't know how. I tried LG pc suite but that didn't work. Do you know how to do it?
Click to expand...
Click to collapse
Warning​
With this method your phone may get bricked and everything will get wiped
If you want to proceed then follow these steps​
Go to Settings,then Device information and tell me your device model.

Okay but if I do everything correctly then nothing bad to the device will happen, right?
P.S. Device model: LG-D855

MariosAga said:
Okay but if I do everything correctly then nothing bad to the device will happen, right?
P.S. Device model: LG-D855
Click to expand...
Click to collapse
Yes.
Now tell me what Windows version do you have? Windows 7?

Windows 10

MariosAga said:
Windows 10
Click to expand...
Click to collapse
Not necessary
Before starting you may need to backup your photos,etc.
Go to Settings then "Backup and Reset" then you will see "LG Backup" click on it and make the backup.After all these steps move your backup file to yiur SD Card or to your PC.(Go to File Explorer then to the folder "LG backups")
So let's go on..!
Go here and select the first one.
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/D855/Android+6.0/
Then go over here
http://forum.xda-developers.com/showthread.php?t=2785089
And scroll down to "How to flash ROM kdz method"
Enable usb debugging
https://www.recovery-android.com/enable-usb-debugging-on-android.html#part1
Connect your phone to your PC
Download Lg drivers(Not Verizon one's!)
Download Lguptool, unzip it,open the folder and inside of it where all the lguptool files are located move the kdz file that you downloaded.
Open lguptool with admin prompt!
Select type CMDA and phone mode DIAG
Select the kdz file and click "CSE Flash"
Then click "start"
A menu will appear,select language and click "Ok"
After all these steps you will need to wait till the phone boots.
Then you will be able to root your phone and flash ROMs!
Good luck!
(A "thank you" would be really appreciated!)

Thanks! I really appreciate you helping me! But do I need to root my phone in order to do that?

MariosAga said:
Thanks! I really appreciate you helping me! But do I need to root my phone in order to do that?
Click to expand...
Click to collapse
No there is no need to Root your device.Only follow the guide that i made.

Okay! Now that I got back my computer I can do it. I just have one more question. My phone will be updated by installing custom roms? Will that wipe off my phone's guarantee? Because it lasts for two more years and I don't want to lose it now.

MariosAga said:
Okay! Now that I got back my computer I can do it. I just have one more question. My phone will be updated by installing custom roms? Will that wipe off my phone's guarantee? Because it lasts for two more years and I don't want to lose it now.
Click to expand...
Click to collapse
Yes it will wipe your guarantee so you need to make a choice.

Password Required After Device Restarts

I have a Pixel XL runing Android 8.0 beta. I restarted my phone and it asks for a passord. I don't know the password and was wondering what is the best way to recover it?
Thanks in advance.

rschonfelder said:
I have a Pixel XL runing Android 8.0 beta. I restarted my phone and it asks for a passord. I don't know the password and was wondering what is the best way to recover it?
Thanks in advance.
Click to expand...
Click to collapse
If you're bootloader is unlocked temp boot into twrp. Delete locksettings.db. That will get you in. Then just create a new pin.

If you didn't create a password in the first place and aren't using a stolen phone you should contact Pixel Support and see if there is a default password the phone might have set up but I haven't heard of that happening to anyone who was on stock and not using a custom recovery. If you are using a custom recovery and are rooted then the previous suggestion might work but I'm pretty sure you need to have root access to get to that file.

jhs39 said:
If you didn't create a password in the first place and aren't using a stolen phone you should contact Pixel Support and see if there is a default password the phone might have set up but I haven't heard of that happening to anyone who was on stock and not using a custom recovery. If you are using a custom recovery and are rooted then the previous suggestion might work but I'm pretty sure you need to have root access to get to that file.
Click to expand...
Click to collapse
You don't need root. Just need an unlocked bootloader.

toknitup420 said:
You don't need root. Just need an unlocked bootloader.
Click to expand...
Click to collapse
To delete the password file? I would have thought for security reasons that would be placed in the root directory. No wonder Google flashes a warning on its phones that your phone is not secure when the bootloader is unlocked--it really isn't. According to you if anyone steals your phone and you have the bootloader unlocked they can easily bypass any password, pin or fingerprint requirement you set up by simply deleting a file. If that's actually true there's a giant easily exploitable flaw with Android security.

jhs39 said:
To delete the password file? I would have thought for security reasons that would be placed in the root directory. No wonder Google flashes a warning on its phones that your phone is not secure when the bootloader is unlocked--it really isn't. According to you if anyone steals your phone and you have the bootloader unlocked they can easily bypass any password, pin or fingerprint requirement you set up by simply deleting a file. If that's actually true there's a giant easily exploitable flaw with Android security.
Click to expand...
Click to collapse
Yeah they have to physically take you're phone and know how to boot it to twrp to do it though. And based on these threads I see on here everyday. There's no chance of that happening.

rschonfelder said:
I have a Pixel XL runing Android 8.0 beta. I restarted my phone and it asks for a passord. I don't know the password and was wondering what is the best way to recover it?
Thanks in advance.
Click to expand...
Click to collapse
Did you find the phone somewhere or is it yours legitimately? Are you trying to break into another device to get information off it? If you're honest about your intentions you really should explain accurately.
If it's a startup pin you can't bypass that. I hope for owner's sake the bootloader is locked including you if it's yours.
Sent from my Pixel using XDA-Developers Legacy app

toknitup420 said:
Yeah they have to physically take you're phone and know how to boot it to twrp to do it though. And based on these threads I see on here everyday. There's no chance of that happening.
Click to expand...
Click to collapse
People who have posted on XDA in the past have seemed very likely to be phone thieves trying to get information about bypassing security on a locked phone so I wouldn't underestimate a phone thief. It's not like XDA is hard to find or a secret.

jhs39 said:
People who have posted on XDA in the past have seemed very likely to be phone thieves trying to get information about bypassing security on a locked phone so I wouldn't underestimate a phone thief. It's not like XDA is hard to find or a secret.
Click to expand...
Click to collapse
That's not what I meant at all. Lol. I was being a wise ass regarding all the people that on xda that can't get twrp working. I dunno if you look in the Q&A section all that often but it's riddled with people that can't get things working on this phone. It was merely a facsicous comment. On a more serious note. The ability to remove the pin from an unlocked phone is nothing more than the fault of the person who owns the phone. Not a security flaw from Google. You're bootloader doesn't come unlocked stock, and if you have a pin with a locked bootloader then you needn't worry.

toknitup420 said:
That's not what I meant at all. Lol. I was being a wise ass regarding all the people that on xda that can't get twrp working. I dunno if you look in the Q&A section all that often but it's riddled with people that can't get things working on this phone. It was merely a facsicous comment. On a more serious note. The ability to remove the pin from an unlocked phone is nothing more than the fault of the person who owns the phone. Not a security flaw from Google. You're bootloader doesn't come unlocked stock, and if you have a pin with a locked bootloader then you needn't worry.
Click to expand...
Click to collapse
I misinterpreted your comment then but a lot of people on XDA obviously like to flash their phones and on the Nexus 6P thread you were told by the person who wrote the flashing guides that the absolute first thing you should do with that phone when you got it was to unlock the bootloader. As for getting TWRP to work on the Pixel a lot of experienced flashers including myself have found it challenging to get TWRP to work on this particular phone. Google didn't make Pixels easy to flash on--particularly compared with their earlier Nexus devices. That said I honestly had no idea unlocking the bootloader made the phone that insecure so I sincerely thank you for the heads up.

huh
toknitup420 said:
If you're bootloader is unlocked temp boot into twrp. Delete locksettings.db. That will get you in. Then just create a new pin.
Click to expand...
Click to collapse
Don't you need the pin to even get into TWRP to delete the file?

Raegoul said:
Don't you need the pin to even get into TWRP to delete the file?
Click to expand...
Click to collapse
Ah yes I forgot about this. This trick only works on decrypted devices. Decrypted devices don't require a password or pattern to enter twrp. Pixel is encrypted by default so yes you would need the password in order to access twrp. GLO. I completely forgot about that.

toknitup420 said:
If you're bootloader is unlocked temp boot into twrp. Delete locksettings.db. That will get you in. Then just create a new pin.
Click to expand...
Click to collapse
Won't it ask for the password when op starts twrp. And if op doesn't have it it cannot decrypt the file system to delete the file you mentioned.
Edit:
NVM saw someone mentioned it

No offense to the OP, but I'm going to call it and say we probably shouldn't be saying anymore. I have never heard of someone setting up their device and then not knowing what their password is. Not saying it's not possible, but if you're on XDA, with a Pixel device on Android O, that means; a) you flashed it and should know your way around some key things on Android, b) you stole the phone, or c) you're trying to break into your significant other's device, and last but not least d) you bought it on Swappa or Cracklist or wherever and the seller didn't wipe it.

People forget their passwords ALL the time... ask my lady if you want!

Erikbronx said:
People forget their passwords ALL the time... ask my lady if you want!
Click to expand...
Click to collapse
Buy her a pen and a pad. No excuses in this day and age.
Sent from my Pixel using XDA-Developers Legacy app

Can't you just go to google.com/android/devicemanager and log in with your google account and unlock it there?

Cash Samsung cloud be used on the Verizon N8?

When I run the backup/restore app and press the backup button, nothing happens. I know Verizon hid the app but did they also disable it?
Edit: title should be can not cash.....

I've tried to run in with shortcut naker.. It starts then crashes no matter if I'm on Verizon firmware or the unlocked firmware. I think Verizon disabled it..

anthonykash said:
I've tried to run in with shortcut naker.. It starts then crashes no matter if I'm on Verizon firmware or the unlocked firmware. I think Verizon disabled it..
Click to expand...
Click to collapse
I have the Verizon Note 8 with the unlocked firmware installed on it and Samsung Cloud works fine. It's in the regular settings menu under "Cloud and accounts".
Sent from my SM-N950U1 using Tapatalk

The problem is once I root it puts me back on the u firmware this it's disabled.

anthonykash said:
The problem is once I root it puts me back on the u firmware this it's disabled.
Click to expand...
Click to collapse
It gets deactivated by the csc file settings. If you are rooted you can edit your carrier settings to enable it. Problem is finding the right file and right settings to do so. I've been playing around with both stock and unlocked firmware trying to figure out how to enable smartcall and samsung cloud apps. If i figure it out I'll let you know.

Please do, thank you

So has anyone figured this out yet?

jellyhead said:
So has anyone figured this out yet?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3686535
Read through that, it will guide you.

nu2droid said:
https://forum.xda-developers.com/showthread.php?t=3686535
Read through that, it will guide you.
Click to expand...
Click to collapse
looks like it requires root. I haven't rooted due to the 80% battery issue.

jellyhead said:
looks like it requires root. I haven't rooted due to the 80% battery issue.
Click to expand...
Click to collapse
Yeah, that's the catch.
Fyi, 80% Thing not a huge issue. I still get 12, 14 + hrs .

Where can I get the unlocked firmware for the Verizon note 8

yesimacarguy said:
Where can I get the unlocked firmware for the Verizon note 8
Click to expand...
Click to collapse
Search BlueFox721 and flashing unlocked

Unlock S9 Plusg (SM-G965F) blocked by KNOX/MDM

good afternoon all
so, I found a Samsung S9 locked by knoxx system. I tryied to make the hard reset, change the bootloader and unlock it with odin, but without sucess, everytime that smartphone reinitilaize it is asking to user name and a password that I don't know that it is.... anyone can help me ?
thank tou

Olavo said:
good afternoon all
so, I found a Samsung S9 locked by knoxx system. I tryied to make the hard reset, change the bootloader and unlock it with odin, but without sucess, everytime that smartphone reinitilaize it is asking to user name and a password that I don't know that it is.... anyone can help me ?
thank tou
Click to expand...
Click to collapse
Well if you found it maybe you should turn it into your local police agency or what ever carrier
No one is gonna help you with this on here as your using a lost or stolen phone which we do not support
since you found it maybe some one is missing it and would like it back?
The security you are encountering is put in place just for people like you

TheMadScientist said:
Well if you found it maybe you should turn it into your local police agency or what ever carrier
No one is gonna help you with this on here as your using a lost or stolen phone which we do not support
since you found it maybe some one is missing it and would like it back?
The security you are encountering is put in place just for people like you
Click to expand...
Click to collapse
I totally agree with what you tell me, but I found it into a garbage and the display is not working well, some parts of the screen are not showing nothing.. so I think that no one is missing it now