Related
Hi Folks,
I'm a smartphone newbie with an Optimus L90. I have some questions about rooting.
I've seen some articles that say that if you root your device you should be careful of automated ROM updates that will unroot your phone. How do most people approach these updates?
How often are these ROM updates necessary? Could I disable this feature & do this manually every month or so?
What about apps? If I manually updated these about every 2 weeks or month, would that be sufficient?
I realize that if I root this device I should only install trusted apps. To me this would mean Google Apps & Amazon, correct?
Regarding antivirus & security, this phone has LookOut running. I've seen some articles that say antivirus software is unnecessary. What are your thoughts on this? I wanted to change the settings for this program. However, I did not find a LookOut app in the apps area. How can these settings be changed?
Thanks,
Mark
What's the reason to root?
Just be careful and do nothing you don't understand. If possible make a backup of your system.
But first read on XDA and be informed
Sent from my LG-D405n using XDA Free mobile app
Root Question
Hello Bravho,
I've seen some info on the internet about these devices being more customizable when rooted. Although, you have an excellent point, I might not have to root. I thought maybe there would be a simple way to root & install a custom ROM on my phone. However, it seems in order to do this correctly I'll need to be more familiar with the OS. This means reading more of the posts on this forum & planning.
Thanks for taking the time to reply,
Mark
bravho said:
What's the reason to root?
Just be careful and do nothing you don't understand. If possible make a backup of your system.
But first read on XDA and be informed
Sent from my LG-D405n using XDA Free mobile app
Click to expand...
Click to collapse
You can use root, but be careful don't do anything you don't understand.
For root: towelroot
Custom roms, read a lot
Sent from my LG-D405n using XDA Free mobile app
mrich72 said:
I've seen some articles that say that if you root your device you should be careful of automated ROM updates that will unroot your phone. How do most people approach these updates?
Click to expand...
Click to collapse
Updates for the L90 are NOT automatic, to my knowledge anyway. You must provide approval for the update to install. However, if you decide to flash a custom ROM such as CyanogenMod ( CM ), you won't have to worry about updates from LG
mrich72 said:
How often are these ROM updates necessary? Could I disable this feature & do this manually every month or so?
Click to expand...
Click to collapse
ROM updates roll out at irregular intervals, if they roll out at all. LG's L90 LG-D415 hasn't had an update as of yet, but several of the other variants have.
mrich72 said:
What about apps? If I manually updated these about every 2 weeks or month, would that be sufficient?
Click to expand...
Click to collapse
Updating your apps is always at your leisure
mrich72 said:
I realize that if I root this device I should only install trusted apps. To me this would mean Google Apps & Amazon, correct?
Click to expand...
Click to collapse
That really depends. With that line of thinking you'll have a very narrow list of applications available. If in doubt, don't install.
mrich72 said:
Regarding antivirus & security, this phone has LookOut running. I've seen some articles that say antivirus software is unnecessary. What are your thoughts on this? I wanted to change the settings for this program. However, I did not find a LookOut app in the apps area. How can these settings be changed?
Click to expand...
Click to collapse
I've found it to be unnecessary. The only thing you can do to manage LookOut is to uninstall it. You must have root privileges to uninstall as it's installed as a system app.
---------- Post added at 10:56 PM ---------- Previous post was at 10:49 PM ----------
mrich72 said:
Hello Bravho,
I've seen some info on the internet about these devices being more customizable when rooted. Although, you have an excellent point, I might not have to root. I thought maybe there would be a simple way to root & install a custom ROM on my phone. However, it seems in order to do this correctly I'll need to be more familiar with the OS. This means reading more of the posts on this forum & planning.
Thanks for taking the time to reply,
Mark
Click to expand...
Click to collapse
Wow! Sorry, don't see many new people come here that actually have enough foresight to research before jumping in to modding their device. They usually jump straight in to modding without doing any research at all and then someone like me gets to explain how to fix what they messed up. :silly:
Rooting is fairly simple and straight forward. Flashing a custom recovery can be tricky for some as can flashing a ROM.
As Faznx92 has abandoned development of his great toolkit that many of us see as an essential to
these devices, I have decided to pick up where he left. I'm continuing the project and, as such, have
recreated it in VB.NET with a proper interface.
Features
supports x.3.1.0-x.3.2.7
root your device; features both jcase and towelroot exploits
disable/enable OTA updates
disable/enable lockscreen ads (special offers)
installers for Safestrap, SuperSU, HDXPosed, and Play Store
To-do
code cleanup
design success forms
implement TWRP installer
Credits
Faznx92 — original idea and much of the logic behind this
jcase — 14/13.3.1.0 root exploit
geohot — towelroot
regaw_leinad — AndroidLib
Hashcode — Safestrap
Cpasjuste — HDXPosed, TWRP (thor)
Chainfire — SuperSU
ggow — TWRP (apollo)
XDA:DevDB Information
HDX Toolkit, Tool/Utility for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
EncryptedCurse
Version Information
Status: Beta
Current Beta Version: 1.2.1
Created 2014-12-29
Last Updated 2015-01-03
Reserved
You can now find the source code in its current state on GitHub:
https://github.com/EncryptedCurse/hdxToolkit
I still need to finish up some things design-wise before I do an actual release.
Feel free to clone the repo and play around with it. Any suggestions on optimization, bug reports and the like are much appreciated.
i haven't been around much in a long time and have been silently lurking the forum. while i don't know how hard it is, a suggestion may be some kind of rollback utility for firmware.
personally, i'm sporting 3.2.4 on my apollo and there is a lot of conflicting information i am finding as to if / how i can roll mine back to .3.1.0 for twrp
theknub said:
i haven't been around much in a long time and have been silently lurking the forum. while i don't know how hard it is, a suggestion may be some kind of rollback utility for firmware.
personally, i'm sporting 3.2.4 on my apollo and there is a lot of conflicting information i am finding as to if / how i can roll mine back to .3.1.0 for twrp
Click to expand...
Click to collapse
not really. There are complete threads discussing your exact situation. And is fairly easy to reproduce. I would advise reading the whole thread involving your modifications. The OP is not always updated with every tidbit of helpful information.
while you're above suggestion. Would be nice to be integrated into another utility. There are fairly easy steps to accomplish what you need to.that have already been thoroughly developed by another developer and he would have to get permission from him also add that.
and keep in mind Apollo is slightly behind in development as far as compared to the Thor.
while i understand that there are whole threads, what i am pointing out, and you said as well is that there is not a definitive process / guide.
anyway, the OP was asking for suggestions which is exactly what i gave.
"not really. There are complete threads discussing your exact situation. And is fairly easy to reproduce. I would advise reading the whole thread involving your modifications. The OP is not always updated with every tidbit of helpful information.
while you're above suggestion. Would be nice to be integrated into another utility. There are fairly easy steps to accomplish what you need to.that have already been thoroughly developed by another developer and he would have to get permission from him also add that.
and keep in mind Apollo is slightly behind in development...blah blah blah"
Ive been all around these forums for years. Never seen a more conflicting and jumbled shamble of tutorial wannabes or confusing information in my life. Most of the bricks dont come from seriously stupid people, they come from a lack of competent, cohesive, coherent information.
conan1600 said:
Ive been all around these forums for years. Never seen a more conflicting and jumbled shamble of tutorial wannabes or confusing information in my life. Most of the bricks dont come from seriously stupid people, they come from a lack of competent, cohesive, coherent information.
Click to expand...
Click to collapse
I cannot completely disagree with you on this. The issue we have is that there are several different routes to currently take with these tablets all depending on what version of firmware you are on, and if you follow one set of directions while on the wrong firmware, its potentially the end for your tablet. Double this confusion with 2 tablets with the "same" yet different sets of firmware. You're right that we are lacking a fully comprehensive guide for people just coming here new. Some bricks have been caused by carelessness, but there is so much confusion with where to begin with some people. Those of us that have had these tablets for awhile may be use to it, but I do feel for the ones new to all of this and the twenty different directions they may have to take based off a single question, "what firmware are you on?".
Am I missing something? I don't see a download link, only contributor links.
SirBindy said:
Am I missing something? I don't see a download link, only contributor links.
Click to expand...
Click to collapse
Re post 3. Basically says OP is working on it and will release it when it's done.
EncryptedCurse said:
As Faznx92 has abandoned development of his great toolkit that many of us see as an essential to
these devices, I have decided to pick up where he left. I'm continuing the project and, as such, have
recreated it in VB.NET with a proper interface.
Click to expand...
Click to collapse
Got the solution from GitHub and started building it. Anything I can do to help? I'm basic to intermediate with OOP languages. I was thinking of attempting to convert the project to C#. If anything, I can help make builds.
It's possible to obtain an installable Windows HDX Toolkit ?
santiga said:
It's possible to obtain an installable Windows HDX Toolkit ?
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=2665683
Davey126 said:
Here: http://forum.xda-developers.com/showthread.php?t=2665683
Click to expand...
Click to collapse
My Kindle HDX 8.9 just arrived and says it is version 4.2....Can I use this toolkit on it?
Thanks
Oh_wow said:
My Kindle HDX 8.9 just arrived and says it is version 4.2....Can I use this toolkit on it?
Click to expand...
Click to collapse
Nope, but there are other methods to obtain root. I will let someone with more experience jump in. While I have read through relevant posts with interest I have not directly worked with Apollo (8.9" HDX) or Sangria (Fire OS 4.x). Don't want to dole out bad/incomplete info ...
Important: Do not connect to WiFi (delete any WiFi networks you may have previously connected to) as you may get upgraded to 4.5.3 which is reported to be much hard to crack. I know it's tempting ... don't do it!
**** ! My Kindle Fire HDX is on 4.5.3 now. :-$
santiga said:
**** ! Muy Kindle Fire HDX is on 4.5.3 now. :-$
Click to expand...
Click to collapse
If you have Thor device (HDX 7") check this
jeryll said:
If you have Thor device (HDX 7") check this
Click to expand...
Click to collapse
I have oficial KF HDX OS.
santiga said:
I have oficial KF HDX OS.
Click to expand...
Click to collapse
Yes, if you need root and you have hdx 7" (codename Thor ), you can downgrade from 13.4.5.3 to 13.3.2.8, then upgrade to 13.4.5.2 which is now rootable.
jeryll said:
Yes, if you need root and you have hdx 7" (codename Thor ), you can downgrade from 13.4.5.3 to 13.3.2.8, then upgrade to 13.4.5.2 which is now rootable.
Click to expand...
Click to collapse
Thx a lot !
I'm wondering what the process for the Pixel devices is, and if anyone has had any success with existing tools/SuperSU.
It's running 7.1 if that's relevant.
sturmeh said:
I'm wondering what the process for the Pixel devices is, and if anyone has had any success with existing tools/SuperSU.
It's running 7.1 if that's relevant.
Click to expand...
Click to collapse
The same way you root other phones, flash custom recovery and supersu.
Sent from my SCH-R220
mattzeller said:
The same way you root other phones, flash custom recovery and supersu.
Sent from my SCH-R220
Click to expand...
Click to collapse
I guess I have to wait for custom recoveries that support this phone then? I can't see a build for TWRP that supports sailfish.
sturmeh said:
I guess I have to wait for custom recoveries that support this phone then? I can't see a build for TWRP that supports sailfish.
Click to expand...
Click to collapse
You'll first need to unlock the bootloader and then wait for chainfire's magic. It is possible to root through fastboot also so there is a good chance that you'll get root before a custom recovery.
Due to seamless updates, things have changed a bit so it'll take some time to be figured out
eatsleep said:
You'll first need to unlock the bootloader and then wait for chainfire's magic. It is possible to root through fastboot also so there is a good chance that you'll get root before a custom recovery.
Due to seamless updates, things have changed a bit so it'll take some time to be figured out
Click to expand...
Click to collapse
Buy it directly from Google and the bootloader won't be locked, only if you buy it through a carrier like Verizon will the bootloader be locked
Sent from my SCH-R220
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Will be interesting if you can do it CF... Looking forward to release - Ill send a donation your way when done
fkofilee said:
Will be interesting if you can do it CF... Looking forward to release - Ill send a donation your way when done
Click to expand...
Click to collapse
The worst possible thing you could write...
ldeveraux said:
The worst possible thing you could write...
Click to expand...
Click to collapse
Hmmm... Does it matter ive donated like 3 or 4 times to him already over the years xd
Either way looking forward to it
fkofilee said:
Hmmm... Does it matter ive donated like 3 or 4 times to him already over the years xd
Either way looking forward to it
Click to expand...
Click to collapse
If your intent was truly altruistic, you wouldn't feel the "burden" of stating it publicly. So no, it doesn't matter.
Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Confirmation number: 57C48888US937054E
Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Appreciate all you do Chainfire, seriously. Can't wait for you to work your magic
Ah its so funny to what people write after all these years of people spending their own time to work out back doors and exploits to enable root / Xposed / Custom bootloaders / Kernels / Recoveries.
People can't just wait and see and if the devs ask for help or testers just be part of it, throwing a few dollars at them is not going to push things forward . . . let them do what they want to do its their project / baby and it will happen when it does.
Support the devs after the fact dont try and attempt to influence them into it with beer money.
Some of y'all are ridiculous! The guy made a harmless statement and didn't mean anything negative by it. And what do all of the analytical geekers do? Just that... Analyze his comment to the bone and find all sorts of self-serving intent within it. Blows my mind...
hutzdani said:
Ah its so funny to what people write after all these years of people spending their own time to work out back doors and exploits to enable root / Xposed / Custom bootloaders / Kernels / Recoveries.
People can't just wait and see and if the devs ask for help or testers just be part of it, throwing a few dollars at them is not going to push things forward . . . let them do what they want to do its their project / baby and it will happen when it does.
Support the devs after the fact dont try and attempt to influence them into it with beer money.
Click to expand...
Click to collapse
Oh shut up. What a stupid thing to say. People are excited about dev work, and if they suggest a donation, what do you care? Why is it any of your business? If the dev has a problem with people providing positive feedback and offering donations, they will make it known.
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Ker~Man said:
Some of y'all are ridiculous! The guy made a harmless statement and didn't mean anything negative by it. And what do all of the analytical geekers do? Just that... Analyze his comment to the bone and find all sorts of self-serving intent within it. Blows my mind...
Click to expand...
Click to collapse
Totally agree. Thanks for speaking up!
Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Hey I've unlocked my bootloader, but with the different partition layout and file based encryption (assuming this device uses that), is there any chance I'll have to erase my data and start over for root?
Because I got the 128GB model and I'm ready to start filling up with apps and keep a big portion of my Google Play music library to save on data and everything but I don't want to do it if there's a real possibility I'll have to erase everything if to achieve root.
I guess it is possible to use a custom recovery (once they come out) to backup, but that'll be a huge backup if I start keeping all my music to the device.
Sent from my Pixel XL using Tapatalk
tveith said:
Oh shut up. What a stupid thing to say. People are excited about dev work, and if they suggest a donation, what do you care? Why is it any of your business? If the dev has a problem with people providing positive feedback and offering donations, they will make it known.
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Totally agree. Thanks for speaking up!
Click to expand...
Click to collapse
What ever but tour the same guys who's going to be asking for OTAs and asking devs to do this that and the other as fast as humanly possible.
If you want it that bad do it your self or sit and wait like a good little child.
No dev is going to rush something because of some people in a forum get a grip, like I said it's their time and it will be ready when it's ready.
You might think I'm going off on one but read the rules page for Christ's sakes.
sionicion said:
Hey I've unlocked my bootloader, but with the different partition layout and file based encryption (assuming this device uses that), is there any chance I'll have to erase my data and start over for root?
Because I got the 128GB model and I'm ready to start filling up with apps and keep a big portion of my Google Play music library to save on data and everything but I don't want to do it if there's a real possibility I'll have to erase everything if to achieve root.
I guess it is possible to use a custom recovery (once they come out) to backup, but that'll be a huge backup if I start keeping all my music to the device.
Click to expand...
Click to collapse
The chance you'll have to erase is always present when rooting. Even when your device is fully prepared something may go wrong. At least you have already unlocked your bootloader, which reduces that chance.
File-based encryption will probably not be a reason to for wiping, though. It works fine in the dev version of SuperSU with Android 7.0 on a 5X.
Hey guys. Found this on the interwebs and was wondering how valid it is. http://www.technobuzz.net/root-google-pixel-xl/
Seeing as it calls for twrp which is not yet available, would flashfire work?
Sent from my Pixel using XDA-Developers mobile app
mrnovanova said:
Hey guys. Found this on the interwebs and was wondering how valid it is. http://www.technobuzz.net/root-google-pixel-xl/
Seeing as it calls for twrp which is not yet available, would flashfire work?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks interesting, but without twrp you sure are taking a big chance if something goes wrong.
Sent from my Pixel using Tapatalk
Hi everyone,
I'm getting really annoyed by Magisk on my phone.
I'm absolutely not able to make it work. No way it can pass safety net control.
If you need some other information, just ask!
Any help would be appreciated,
thanks in advance,
Lorenzo Benevento.
EDIT: I've just upgraded to the last LAOS build and now it doesn't pass also the basic integrity test!
Bump.
With V15.2 basic integrity works, but I can't pass the whole test!
Lorenzo Benevento said:
Bump.
With V15.2 basic integrity works, but I can't pass the whole test!
Click to expand...
Click to collapse
So in other words: MagiskHide is working on your device but Google doesn't recognise it as a certified device.
If you wan't to pass CTS as well, you're going to have to trick Google into thinking you have another device/ROM, probably by using the fingerprint from a stock ROM that is certified. There's some info on that in the troubleshooting guide (which I'm hoping to have some time to update in the next few days).
Okay, thank you for the infos! I will do some research an hopefully go through it.
Hi, unfortunately seems like there is no way of getting it to work, I also tried Universal Fix but it messed out everything.
I was discussing about it on discord and they said that looks like my device (Zuk Z1) is not fully supported (and it is plausible since is not this popular).
So, if I can help with the development (boot images, logcats, Magisk Log, trying, whatever), let me know who should I contact and how.
Thank you so much.
I'm having troubles with Magisk since V13, the first I tried...!
Lorenzo Benevento said:
Hi, unfortunately seems like there is no way of getting it to work, I also tried Universal Fix but it messed out everything.
I was discussing about it on discord and they said that looks like my device (Zuk Z1) is not fully supported (and it is plausible since is not this popular).
So, if I can help with the development (boot images, logcats, Magisk Log, trying, whatever), let me know who should I contact and how.
Thank you so much.
I'm having troubles with Magisk since V13, the first I tried...!
Click to expand...
Click to collapse
Well... Since you can pass basic integrity we know that MagiskHide is working. The Universal SafetyNet Fix module might not be your best option... Simply using a resetprop tool script to change ro.build.fingerprint, like mentioned in the guide I linked (under "Spoofing device fingerprint") might be enough.
Didgeridoohan said:
So in other words: MagiskHide is working on your device but Google doesn't recognise it as a certified device.
If you wan't to pass CTS as well, you're going to have to trick Google into thinking you have another device/ROM, probably by using the fingerprint from a stock ROM that is certified. There's some info on that in the troubleshooting guide (which I'm hoping to have some time to update in the next few days).
Click to expand...
Click to collapse
Didgeridoohan said:
Well... Since you can pass basic integrity we know that MagiskHide is working. The Universal SafetyNet Fix module might not be your best option... Simply using a resetprop tool script to change ro.build.fingerprint, like mentioned in the guide I linked (under "Spoofing device fingerprint") might be enough.
Click to expand...
Click to collapse
Okay, thank you, I have just a question before trying (and mark this thread as solved hopefully). Will this change in props affect LAOS OTAs?
Lorenzo Benevento said:
Okay, thank you, I have just a question before trying (and mark this thread as solved hopefully). Will this change in props affect LAOS OTAs?
Click to expand...
Click to collapse
Changing the fingerprint can cause your phone to be recognised for something it isn't, so it's perfectly possible that it can affect OTAs. It should just be a matter of disabling the script when you need to update.
I have no real world experience with it though... I've just once tested and confirmed that changing the fingerprint can help with passing SafetyNet on a non-certified ROM.
Okay, I'm going to try, the only problem is that I can't find the official fingerprint of my phone! Only outdated version, I think I should match at least Android version, isn't it?
Thank you so much for your quick and useful replies.
Didgeridoohan said:
Changing the fingerprint can cause your phone to be recognised for something it isn't, so it's perfectly possible that it can affect OTAs. It should just be a matter of disabling the script when you need to update.
I have no real world experience with it though... I've just once tested and confirmed that changing the fingerprint can help with passing SafetyNet on a non-certified ROM.
Click to expand...
Click to collapse
Okay, I'm going to try, the only problem is that I can't find the official fingerprint of my phone! Only outdated version, I think I should match at least Android version, isn't it?
Thank you so much for your quick and useful replies.
Lorenzo Benevento said:
Okay, I'm going to try, the only problem is that I can't find the official fingerprint of my phone! Only outdated version, I think I should match at least Android version, isn't it?
Thank you so much for your quick and useful replies.
Click to expand...
Click to collapse
Actually, when testing I used an official Nougat fingerprint for a custom Oreo ROM. If you can't get a hold of a more recent fingerprint, I'd recommend asking in your device's forum if anyone can provide one.
Thank you so much, I'll ask there.
I've just bought this phone, I have a SIM that does support WiFi calling and VoLTE (it's EE in UK), but I don't see the option anywhere. Similarly I don't see a VoLTE option. I've been everywhere in the menus, and it's just not there, or in the phone app.
Is there some magic code I can type in to force it on, like *#*#86583#*#* on a Xiaomi ?
Do either of these work OK for anyone ?
I have version 17.0922.2005.11
I found the answer, and if someone else is looking, Asus needs to add your carrier / country VOLTE/VOWIFI profiles to their firmware.
I guess I have to wait.
lordxenu said:
I found the answer, and if someone else is looking, Asus needs to add your carrier / country VOLTE/VOWIFI profiles to their firmware.
I guess I have to wait.
Click to expand...
Click to collapse
Your carrier/counrty COULD be in there already. Prop edits might be necessary. I posted a thread a few days ago, but deleted it, because the thread got spammed.
bs3pro said:
Your carrier/counrty COULD be in there already. Prop edits might be necessary. I posted a thread a few days ago, but deleted it, because the thread got spammed.
Click to expand...
Click to collapse
can we possibly convince you to share the info again ( read the thread, and yeah, seems people either are clueless or want everything 5G .. aparently they dont get the dofference between network limitations and phone limitations or something :/ ) just got the ROG3 yesterday, but living in a low coverage area, im more or less depending on VoWIFI most of the time, so would be great to have the phone actually working as intended instead of mostly handheld console XD ..
thank you
bs3pro said:
Your carrier/counrty COULD be in there already. Prop edits might be necessary. I posted a thread a few days ago, but deleted it, because the thread got spammed.
Click to expand...
Click to collapse
Please if you have a solution help us
@bs3pro
Can you share this information please? Do you need root? Mind PMing it to me if possible if anything..
bs3pro said:
Your carrier/counrty COULD be in there already. Prop edits might be necessary. I posted a thread a few days ago, but deleted it, because the thread got spammed.
Click to expand...
Click to collapse
Any chance you can share it here mate. It would be of great help to everyone. There are stupids everywhere, please donot hesitate to share the info because of those self entitled pricks.
Thanks mate.
bindassever said:
Any chance you can share it here mate. It would be of great help to everyone. There are stupids everywhere, please donot hesitate to share the info because of those self entitled pricks.
Thanks mate.
Click to expand...
Click to collapse
Hi Guys,
Just finished adding some hours ago all what is needed to enable it for my ROG 3 and my carrier.
[Guide] Enabling VoLTE/VoWiFi v2 | XDA Developers Forums
I have rooted the phone...
1) download the bootloader unlock from asus support webpage and unlock the bootloader (!!!this wipes your phone!!!)...just select the model and they give you the apk.
2) download twrp custom rom and flash it in fastboot (you need drivers and fasbtoot tool)
3) install magisk apk and use the app to download the proper zip that has to be flashed via custom recovery to enable root
4) having root enabled now you can use the guide above and activate diagnostics (I had to use the remote port option as it would not detect it via USB
5) based on the guide I also used the Xiaomi mi9 mbns (sort of config files for volte and vofi) using my carrier file.
Rebooted and all works now
PS: I had to enable magisk hiding mechanisms to make sure banking apps are working also.
While at this I also added some ad blocking capabilities now that I had to have root
PPS: here is a guide for rooting....(https://www.ytechb.com/how-to-install-xposed-framework-on-android-10/)
for custom recovery (https://dl.twrp.me/I003D/twrp-3.5.0_10-0-I003D.img.html)
With the new update to a12, here in USA a lot of users can make or receive any phone call. with the A11 not issues. Any idea how we can fix this issue ? My phone is not rooted.