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
I have flash magisk with twrp (J610F)
But my phone still doesn't have root
Hello and welcome to XDA.
This is a place with lots of information and resources, so the first thing to do should always be to search. But since there's so much information, finding what you want can sometimes be a challenge...
If you do need to ask for help, it matters how you ask. Providing as much details as possible is usually a good idea. And if possible, logs. Take a look here:
https://didgeridoohan.com/magisk/MagiskHelp
A good idea when trying to figure things out is to visit your device's forum:
https://forum.xda-developers.com/galaxy-j6+
There you can usually find guides on things like rooting Thar applies to your specific device (if there are extra things that need to be done).
I did a quick search and found this thread:
https://forum.xda-developers.com/ga...ecovery-twrp-3-2-3-1-galaxy-j6-j610f-t3875150
In there, you'll find this little tidbit of information:
Due to some new securities in Samsung's latest Pie kernels, root will not work with the stock kernel. The patched kernel below is required to gain root on Pie.
Click to expand...
Click to collapse
So, extra stuff seems to be necessary for your device...
Hope you get things working, and don't hesitate to ask for help if you get stuck somewhere. But make sure to be detailed. Good luck.
Cheers
/Didgeridoohan
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.
why is it we have roms availavble but no twrp??
Seriousfreedom said:
why is it we have roms availavble but no twrp??
Click to expand...
Click to collapse
Since neither of us are developers it's impossible to say other than A13 is a horse of another color as are devices since the P4 or 5. Here's a link if you are so inclined. https://twrp.me/site/update/2022/10/10/3.7.0-released.html Pay attention to this paragraph it might help you understand why you may get flamed here and elsewhere. So if you really want it then perhaps you can help out.
"We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!"
Twrp isn't as easy to get to work properly how it used to being it's a pixel I'm sure eventually someone will have it working I miss twrp my last device never really got a proper twrp
rob420p said:
Twrp isn't as easy to get to work properly how it used to being it's a pixel I'm sure eventually someone will have it working I miss twrp my last device never really got a proper twrp
Click to expand...
Click to collapse
Neither did mine
Is it possible to install a rom ithout a custom recovery?
I think pixel experience and lineageos use their own recovery that you got to flash
I've had my S10 for a few years, and it's the first phone I haven't rooted in years. One reason is that I just don't have the time to get up to speed (unless things have changed and rooting is now easier?).
I use the paid version of NetGuard, but am unable to use my vpn at the same time, since NG uses the vpn service. NG doesn't block my DNS.
I'll likely replace this phone in the next year or so, so if rooting has become an easier & less time consuming process, I'd gladly jump on board.
Is there a good no-root firewall that doesn't prevent me from using my vpn?
ANy other advice to secure this unrooted device?
Thanks for any help.
Please be aware that questions regarding specific devices should be asked in that device's section. Your thread will be moved shortly.
Sam Sung said:
I'll likely replace this phone in the next year or so, so if rooting has become an easier & less time consuming process, I'd gladly jump on board.
Click to expand...
Click to collapse
TWRP is available for your device; rooting with Magisk is as simple as flashing it in TWRP. The "official" method is to patch the AP firmware file in Magisk, but this doesn't work for everyone. There are a few guides available such as this one.
Sam Sung said:
Is there a good no-root firewall that doesn't prevent me from using my vpn?
Click to expand...
Click to collapse
No, due to the way networking works on Android. The "VPN" is the loopback that directs your data traffic through the app. My recommendation is to use a VPN with integrated security features such as NordVPN.
V0latyle said:
Please be aware that questions regarding specific devices should be asked in that device's section. Your thread will be moved shortly.
Click to expand...
Click to collapse
Apologies for posting in the wrong forum...I mentioned the device, but felt my question was general to all devices.
TWRP is available for your device; rooting with Magisk is as simple as flashing it in TWRP. The "official" method is to patch the AP firmware file in Magisk, but this doesn't work for everyone. There are a few guides available such as this one.
Click to expand...
Click to collapse
Thanks for the link to the guide. I'll check that out. Truth is that I've missed being rooted.
No, due to the way networking works on Android. The "VPN" is the loopback that directs your data traffic through the app. My recommendation is to use a VPN with integrated security features such as NordVPN.
Click to expand...
Click to collapse
I already use Mullvad vpn and have been happy with it, but am unable to use NG at the same time.
Am I correctly understanding that a vpn and a firewall blocking specified and default outbound traffic can't be used at the same time with no recourse even if rooted?
Thanks for your comments.