Hello, I will have Pixel 6 Pro today or tomorrow. As a grandfather unlimited data user on verizon I am wondering if editing the build prop and adding the line "net.tethering.noprovisioning=true" would still work as a hotspot work around? And if so, is there a way to edit build prop file without unlock and root? Do I have to wait until TWRP recovery is released for the Pixel 6 and Pull/Push the file through ADB? Thank you in advance for any help/info!
Nope ... even WITH root, you won't be able to edit the file as the filesystems are not write mountable nowadays.
With root, you can either overwrite the property or use Magisk's resetprop in a script to do that at boot time.
foobar66 said:
Nope ... even WITH root, you won't be able to edit the file as the filesystems are not write mountable nowadays.
With root, you can either overwrite the property or use Magisk's resetprop in a script to do that at boot time.
Click to expand...
Click to collapse
Thanks.. I haven't been up to date on these things.. I did edit the file on my last phone.. but it was unlocked and rooted.. I made the mistake of buying p6p from Verizon which seems like it's going to be a big hassle to get it unlocked? Guess I'm probably stuck paying the $30/month if I want hotspot on gUDP for a couple years
foobar66 said:
the filesystems are not write mountable nowadays.
Click to expand...
Click to collapse
What? When did this happen and how?
mko000 said:
What? When did this happen and how?
Click to expand...
Click to collapse
A long time ago. I want to say scoped storage but maybe even before that.
mko000 said:
What? When did this happen and how?
Click to expand...
Click to collapse
Yeah, somewhere around the time of 4.4 KitKat or so. Or started there with external MicroSD cards and then they proceeded to do internal storage that way later, maybe as soon as 5.0 Lollipop.
roirraW edor ehT said:
Yeah, somewhere around the time of 4.4 KitKat or so. Or started there with external MicroSD cards and then they proceeded to do internal storage that way later, maybe as soon as 5.0 Lollipop.
Click to expand...
Click to collapse
That can't be true, I'm on Android 10 and can mount my system partition r/w just fine.
mko000 said:
That can't be true, I'm on Android 10 and can mount my system partition r/w just fine.
Click to expand...
Click to collapse
What I said in my post is definitely true, and I remember it when I was on KitKat and Lollipop devices. What is Scoped Storage in Android?
"With Android 4.4 KitKat, Google started making changes to and adding restrictions on how an app could access files it did not own, and with Android 5.1, the Storage Access Framework was implemented."
Click to expand...
Click to collapse
Also more up to date information on it here: Scoped Storage
roirraW edor ehT said:
What I said in my post is definitely true, and I remember it when I was on KitKat and Lollipop devices. What is Scoped Storage in Android?
Also more up to date information on it here: Scoped Storage
Click to expand...
Click to collapse
You want to tell me you have root and can't mount your system partition r/w?
Yeah I'm not super familiar with the technicalities, but I was able to do it with Razer Phone 2 on Android 9.. but that was an unlocked device with root.. idk what has changed since then but if any one figures it out for a verizon locked P6P please let me know! lol
mko000 said:
You want to tell me you have root and can't mount your system partition r/w?
Click to expand...
Click to collapse
I'm not talking about root. I was replying to your first question below.
mko000 said:
What? When did this happen and how?
Click to expand...
Click to collapse
roirraW edor ehT said:
Yeah, somewhere around the time of 4.4 KitKat or so. Or started there with external MicroSD cards and then they proceeded to do internal storage that way later, maybe as soon as 5.0 Lollipop.
Click to expand...
Click to collapse
roirraW edor ehT said:
I'm not talking about root. I was replying to your first question below.
Click to expand...
Click to collapse
I replied to that: "Nope ... even WITH root, you won't be able to edit the file as the filesystems are not write mountable nowadays."
mko000 said:
I replied to that: "Nope ... even WITH root, you won't be able to edit the file as the filesystems are not write mountable nowadays."
Click to expand...
Click to collapse
You're confusing me, man. I was just answering your question.
roirraW edor ehT said:
You're confusing me, man. I was just answering your question.
Click to expand...
Click to collapse
Thank you. I should have qouted more I guess.
Answer this one please: Is the following statements made above true?
"Nope ... even WITH root, you won't be able to edit the file as the filesystems are not write mountable nowadays."
mko000 said:
Thank you. I should have qouted more I guess.
Answer this one please: Is the following statements made above true?
"Nope ... even WITH root, you won't be able to edit the file as the filesystems are not write mountable nowadays."
Click to expand...
Click to collapse
No sweat, you're welcome. That, I don't know and I'm not in a position to test right at the moment. Sorry for the confusion.
android 11 on current device and i can mount system R/W with root just fine
squee666 said:
android 11 on current device and i can mount system R/W with root just fine
Click to expand...
Click to collapse
What device? Not on a pixel. The only way in to do it is systemlessly, through a Magisk script at boot.on a older pixel for sure no problem
If I remember correctly, it started with pixel 3.
It seems that the partition is formatted with EXT4 with a shared blocks feature that makes the partition read-only without the ability to change that:
https://twitter.com/i/web/status/1170404631865778177
I'm in this exact situation. But I got my p6p from Google directly. My OnePlus 7 Pro isn't rooted but it didn't verify my hotspot subscription at all. I thought getting the non carrier version would avoid this problem. Now with no build.prop what to do...
Related
Hi
Does anyone know anything a out the current status of Flashfire on the Pixel (XL)?
I've tried to backup data and the screen turned black, afterwards I hard to hard reset the phone to get it working again.
niko26 said:
Hi
Does anyone know anything a out the current status of Flashfire on the Pixel (XL)?
I've tried to backup data and the screen turned black, afterwards I hard to hard reset the phone to get it working again.
Click to expand...
Click to collapse
Good place to start https://plus.google.com/+Chainfire
danw_oz said:
Good place to start https://plus.google.com/+Chainfire
Click to expand...
Click to collapse
I've tried to contact him already, plus asked him in one of his threads/posts. No response.
niko26 said:
I've tried to contact him already, plus asked him in one of his threads/posts. No response.
Click to expand...
Click to collapse
It's probably because he got sick of being asked the same question over and over again.
If I read the XDA forums http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 searching for the word PIXEL. This app appears that people have this working on Pixel XL, but not since the November release
danw_oz said:
It's probably because he got sick of being asked the same question over and over again.
If I read the XDA forums http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 searching for the word PIXEL. This app appears that people have this working on Pixel XL, but not since the November release
Click to expand...
Click to collapse
Thanks for your comment.
I was not asking why he was not replying to my questions - I've got total sympathy for that because the number of messages he might get must be insane.
My question still stands: Obviously Flashfire is not yet aware of the different layout of partitions on the Pixel phones. Does it still work correctly? If not, did Chainfire say anything about Flashfire being fixed to work with the pixels? I couldn't find anything, that's why I'm asking here.
I assume any announcement on it working on the Pixel will be made when it works on the Pixel. Much like superSU. (hope that doesnt sound like an ass thing to say) it's just the way things have been. unless someone else works on something and it looks like they are going to beat another dev to the punch, you don't usually see any info, much like boot-loader unlocks, rooting of a certain phone etc.. i.e when there is a bounty and team blahblah looks like they gonna take the glory, BANG! suddenly there's a solution that said dev was already working on secretly but wasn't planing on releasing any time soon but since there's competition, kinda thing. Know what I mean?
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
larsdennert said:
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
Click to expand...
Click to collapse
Hey just curious what you mean by this. I know that TWRP has some bugs but I thought everything with SuperSU was worked out
I'm thinking they are still working on having them coexist without one wiping the other
larsdennert said:
I'm thinking they are still working on having them coexist without one wiping the other
Click to expand...
Click to collapse
No they work fine, especially SuperSU. TWRP is in alpha but works for installing and most other things but backup and restore does not yet.
larsdennert said:
I'm thinking they are still working on having them coexist without one wiping the other
Click to expand...
Click to collapse
Wow, that was like week number one.
You're waaaaaay behind on updates.
Lol then we should get on chain fires case
larsdennert said:
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
Click to expand...
Click to collapse
What? SuperSU working perfectly with twrp. As others said twrp still in alpha and some features are iffy, but SuperSU is solid.
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
Are you verizon?
Because if you're verizon then add Verizon to your profile so people can appropriately address your questions.
And add your freaking state/country while you're at it. :good:
CZ Eddie said:
Are you verizon?
Because if you're verizon then add Verizon to your profile so people can appropriately address your questions.
And add your freaking state/country while you're at it. :good:
Click to expand...
Click to collapse
My apologies. T-Mobile, US - added to profile. Thanks for the suggestion!
s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
You can sideload the update via ADB supposedly.
I've never used that method though.
I just flash the entire update on top of my old OS using flashboot and my guide here:
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Make sure to remove the -w from the script if you don't want your old data/apps wiped.
Then re-root your phone afterwards.
Nothing to worry about there if it's not a Verizon phone.
s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
I do it like in this guide http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
Very helpful, thanks guys. I did it and it worked - ran flash-all with -w removed. I wonder though if there's any downside to doing this that may not have been identified yet, such as extra space being taken up or diminished performance (even if negligible) possibly due to some duplication of data or something like that.
s1dest3pnate said:
Very helpful, thanks guys. I did it and it worked - ran flash-all with -w removed. I wonder though if there's any downside to doing this that may not have been identified yet, such as extra space being taken up or diminished performance (even if negligible) possibly due to some duplication of data or something like that.
Click to expand...
Click to collapse
No, no downside at all. Flash all without the -w is how most people do it. It could even be argued that it is better.
Sent from my Pixel XL using XDA Labs
hello i have pixel 2 xl root with magisk is ok but why i can to ReadWrite Permissions I'm trying to change a file and i cant why
who i change to Write Permissions Someone has instructions I tried a lot without success??
i run android 10 october security
oraned said:
hello i have pixel 2 xl root with magisk is ok but why i can to ReadWrite Permissions I'm trying to change a file and i cant why
who i change to Write Permissions Someone has instructions I tried a lot without success??
i run android 10 october security
Click to expand...
Click to collapse
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post80368009
I'm afraid your SOL, as we all are until, and if TJW finds a way to deal with the new logical partitions google implemented with A10
More from the man himself!
https://github.com/topjohnwu/magisk...a0/notes.md#new-system-as-root-implementation
Badger50 said:
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post80368009
I'm afraid your SOL, as we all are until, and if TJW finds a way to deal with the new logical partitions google implemented with A10
More from the man himself!
https://github.com/topjohnwu/magisk...a0/notes.md#new-system-as-root-implementation
Click to expand...
Click to collapse
thanks good day
As the title states. Am just wondering what happens exactly when you take a ota on a rooted device. Am not talking about the full ota. Am talking about the smaller otas just curious to know
v.konvict said:
As the title states. Am just wondering what happens exactly when you take a ota on a rooted device. Am not talking about the full ota. Am talking about the smaller otas just curious to know
Click to expand...
Click to collapse
You can't on OOS. You have to take full.
jhlogan said:
You can't on OOS. You have to take full.
Click to expand...
Click to collapse
That much i know. I want to know what will happen
v.konvict said:
That much i know. I want to know what will happen
Click to expand...
Click to collapse
Do it then tell us
ej8989 said:
Do it then tell us
Click to expand...
Click to collapse
Am sure its already been done just wanna understand how root affects the partions when taking an ota
v.konvict said:
Am sure its already been done just wanna understand how root affects the partions when taking an ota
Click to expand...
Click to collapse
You'll end up breaking your phone's functionality, simply causing boot looping, unable to root your device and have to install a full base factory ota to fix the damage done. And you wouldn't even be able to backup anything either since the device will basically be semi-bricked
Shen Ron said:
You'll end up breaking your phone's functionality, simply causing boot looping, unable to root your device and have to install a full base factory ota to fix the damage done. And you wouldn't even be able to backup anything either since the device will basically be semi-bricked
Click to expand...
Click to collapse
Thanks for this. Am not new to flashing updates with root. Was hoping for a more detailed explanation. Like the ota updates a certain partition which when rooted will cause a bootloop because a certain partition wont readable
v.konvict said:
Thanks for this. Am not new to flashing updates with root. Was hoping for a more detailed explanation. Like the ota updates a certain partition which when rooted will cause a bootloop because a certain partition wont readable
Click to expand...
Click to collapse
Every partition except the boot partition will be ok for the most part but you'll still end up boot looping even if you installed magisk over again, so unless you do a fresh install which depending on how badly you messed something up or forgot to disable any modules, you will have to start from scratch to save your phone. But if you already made a backup whether it's before everything went south or in twrp to save your data then you should be okay
after flashing twrp recovery (chinese) i don't see my internal storage.
how to fix it?
altojd said:
after flashing twrp recovery (chinese) i don't see my internal storage.
how to fix it?
Click to expand...
Click to collapse
I would think format data but that will wipe yr phone
Edit: nevermind.
Lossyx said:
Don't come here for support of the chinese TWRP.
Click to expand...
Click to collapse
WTH...? Why may he not ask such question here? If Am I right, It's only not allowed to be shared here. He can ask about whatever he want.
@altojd AFAIK decryption is not working even on chinese recovery. Some guy once told me to format data but it didnt worked for me.
EugenStanis said:
WTH...? Why may he not ask such question here? If Am I right, It's only not allowed to be shared here. He can ask about whatever he want.
@altojd AFAIK decryption is not working even on chinese recovery. Some guy once told me to format data but it didnt worked for me.
Click to expand...
Click to collapse
Yes, and the reason why it's not allowed to be shared here is because it's violating licenses and XDAs TOS.
So why would we be able to talk support regarding it? Doesn't make much sense.
I don't know though, I'm not a moderator. I'll edit my initial post.
Lossyx said:
Yes, and the reason why it's not allowed to be shared here is because it's violating licenses and XDAs TOS.
So why would we be able to talk support regarding it? Doesn't make much sense.
Just to make it clear. All versions of custom roms state that they can be flashed with chinese twrp. Many posts state that chinese twrp works flawlessly on our device. All those without any intervention of moderator. Hope this answer your question/remark which would be better if you didn't write it.
Click to expand...
Click to collapse
altojd said:
Lossyx said:
Yes, and the reason why it's not allowed to be shared here is because it's violating licenses and XDAs TOS.
So why would we be able to talk support regarding it? Doesn't make much sense.
Just to make it clear. All versions of custom roms state that they can be flashed with chinese twrp. Many posts state that chinese twrp works flawlessly on our device. All those without any intervention of moderator. Hope this answer your question/remark which would be better if you didn't write it.
Click to expand...
Click to collapse
You are right, i should have no said anything. I apologise for that.
To answer your initial question, I have read it needs formatting data first in order to decrypt internal storage.
Click to expand...
Click to collapse
Lossyx said:
altojd said:
You are right, i should have no said anything. I apologise for that.
To answer your initial question, I have read it needs formatting data first in order to decrypt internal storage.
Click to expand...
Click to collapse
Thank you
Click to expand...
Click to collapse
I really want to be able to do full backups of my phone, but losing the camera is obviously a no go. I assumed that a work around would be found by now, but can't find any recent discussion.
No.
Nobody could find a way currently, so they're waiting for Android 12.
dirtybudha said:
No.
Nobody could find a way currently, so they're waiting for Android 12.
Click to expand...
Click to collapse
Android 12 is allready here, you can manual install it tru ADB, i am running it for more then a week allready
robsmith11 said:
I really want to be able to do full backups of my phone, but losing the camera is obviously a no go. I assumed that a work around would be found by now, but can't find any recent discussion.
Click to expand...
Click to collapse
you can even if not rooted, just use the ADB command style to fully backup your phone.
Gojira-r32 said:
Android 12 is allready here, you can manual install it tru ADB, i am running it for more then a week allready
Click to expand...
Click to collapse
That's the beta.
Gojira-r32 said:
you can even if not rooted, just use the ADB command style to fully backup your phone
Click to expand...
Click to collapse
Does that work with the US variant? Can you give a step by step? Thanks!
Alxoom33 said:
Does that work with the US variant? Can you give a step by step? Thanks!
Click to expand...
Click to collapse
There is literally a thread about installing the Beta 4 release. Go up one level in this forum to find it.
And yes, but you have to be on a certain software version. PLEASE read through that forum to find out what you need to do.
Gojira-r32 said:
you can even if not rooted, just use the ADB command style to fully backup your phone.
Click to expand...
Click to collapse
That's been deprecated with Android 12. And even before thst, many apps prevented adb from backing up their data. The only way I know of to get a full backup is with root.
Honestly, I've yet to find a way to get the data backed up without rooting. Given that almost all my apps either export a file to use as a backup, or I don't actually need a backup. But if you do, you might want to wait for the official update.
dirtybudha said:
There is literally a thread about installing the Beta 4 release. Go up one level in this forum to find it.
And yes, but you have to be on a certain software version. PLEASE read through that forum to find out what you need to do.
Click to expand...
Click to collapse
Thank you!
Alxoom33 said:
Thank you!
Click to expand...
Click to collapse
No problemo, good luck. I tried and it didn't work so I decided to wait.
future updates from Samsung aren't going to make more
things possible, the trend is that they make less things possible.