I want to enable the camera api so i need to change the build prop which means i have to root.
Can i unroot after changing the build prop and will i still be able to update using the built in system?
Will fastboot oem lock after changing the build.prop wipe the edited build prop?
thanks.
w1ll1m said:
I want to enable the camera api so i need to change the build prop which means i have to root.
Can i unroot after changing the build prop and will i still be able to update using the built in system?
Will fastboot oem lock after changing the build.prop wipe the edited build prop?
Click to expand...
Click to collapse
I haven't tried personally but it should work as you described.
There's anyway no guarantee that changes will survive to further OTA updates...
Cheers
Related
Need Stock build.prop for updating to 4.1.2 I get Status 7 build.prop in CWM and red triangle is stock recovery Need Untouched, 4.1.1 build.prop
Thks!
mgsstar said:
Need Stock build.prop for updating to 4.1.2 I get Status 7 build.prop in CWM and red triangle is stock recovery Need Untouched, 4.1.1 build.prop
Thks!
Click to expand...
Click to collapse
I had the same issue, got it from the second post here: http://forum.xda-developers.com/showthread.php?t=1783152
Yadao said:
I had the same issue, got it from the second post here: http://forum.xda-developers.com/showthread.php?t=1783152
Click to expand...
Click to collapse
Didn't work Gave me an android with a exclamation mark on it
EDIT: BTW it also bricked my device Had to do nandroid backup....
bump
Really Need The Stock Build.Prop!!
Thks...
Its a Canada Nexus 7
If you manually edit the build.prop file it saves the original as build.prop.bak. If you didn't edit it more than once, you may have your original on the phone which can be renamed.
Groid said:
If you manually edit the build.prop file it saves the original as build.prop.bak. If you didn't edit it more than once, you may have your original on the phone which can be renamed.
Click to expand...
Click to collapse
I did edit it more than twice...
mgsstar said:
Need Stock build.prop for updating to 4.1.2 I get Status 7 build.prop in CWM and red triangle is stock recovery Need Untouched, 4.1.1 build.prop
Thks!
Click to expand...
Click to collapse
Did you have any luck? I am also having issues updating to 4.1.2. I have edited my build.prop a couple times and it might be the issue. Like you exprienced, the other build prop soft bricked my tablet as well. Luckily was able to it back.
Just install:---> Google Nexus 7 Toolkit V3.2.0,
Then Put Rom 4.1.2 in the folder: --- put_google_factory_image_here
Then Press number 9 to Flash Google Factory Stock rom and follow instructions.
My Method that made the update to work:
I used this build.prop https://www.dropbox.com/s/qu7kppjjoqlczdd/build.prop (creds to Sebianoti)
I dragged it in to the build.prop location and replaced it. Rebooted it, soft bricked my device.
I booted the TWRP recovery using Google Nexus 7 Toolkit (Option 10) and installed the zip and it worked!
I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE!!
USE AT YOUR OWN RISK
mgsstar said:
Need Stock build.prop for updating to 4.1.2 I get Status 7 build.prop in CWM and red triangle is stock recovery Need Untouched, 4.1.1 build.prop
Thks!
Click to expand...
Click to collapse
Untouched build.prop from JRO03D https://www.dropbox.com/s/j5d396wnc8fqnc1/build.prop
Why did you want an OTA update? The factory image for 4.1.2 has been out for awhile now so you could of just (backed up everything and) flashed that instead of needing to do the hassle of finding a working build.prop.
Does updating cyanogenmod reset your build.prop file? So do I need to redo all changes after every update?
xzaxox said:
Does updating cyanogenmod reset your build.prop file? So do I need to redo all changes after every update?
Click to expand...
Click to collapse
Yes, it will replace the previous build.prop
Remember if you want to enable the test version of multi window in MM
you just need to change the ro.build.type in build prop from user to userdebug, then go to the drawing section in developer options and enable.
So far no major issues except a few graphic glitches but i can now watch a video with mx player and use chrome at the same time, so let the good times role
more detailed guide can be found below with root and non-root methods ( Root tested by me only)
[GUIDE] Enable Multi-Window Mode on Android 6.0 Marshmallow
Haven't rooted my Pixel as of yet, but I think this might just be the reason I do! Thanks for the heads-up!
NJ72 said:
Haven't rooted my Pixel as of yet, but I think this might just be the reason I do! Thanks for the heads-up!
Click to expand...
Click to collapse
you can do it without root just adb push pull the build prop to make changes
Even frigging better! thanks!
EDIT: Tried this and could pull absolutely fine, but can't push without unlocking BL and flashing TWRP I don't think as android recovery doesn't work and it won't let me write whilst it's booted.
Any advice welcome
You will need to unlock and boot loader and do it with TWRP. No need to root.
clubtech said:
You will need to unlock and boot loader and do it with TWRP. No need to root.
Click to expand...
Click to collapse
I have tried following this method with the new Software of Pixel C (6.0.1 (MXB48T)) and no root. I was able to flash the TWRP and do the pull/push method. But after that whenever I try to reboot the device, it goes back to the TRWP screen. It never boots to Android OS no matter how much or what I try and it only works when I flash the whole factory image all over again.
Anyone has a clue on how to make it work?
oneshotaz said:
I have tried following this method with the new Software of Pixel C (6.0.1 (MXB48T)) and no root. I was able to flash the TWRP and do the pull/push method. But after that whenever I try to reboot the device, it goes back to the TRWP screen. It never boots to Android OS no matter how much or what I try and it only works when I flash the whole factory image all over again.
Anyone has a clue on how to make it work?
Click to expand...
Click to collapse
TBH, this may only work with root, given the unique architecture of the pixel c or something else.
But seeing as you have flashed twrp and gone that far, why not just flash the xceed kernel, as I can confirm I have it working on lastest stock build with xceed and su
beardymcgee said:
TBH, this may only work with root, given the unique architecture of the pixel c or something else.
But seeing as you have flashed twrp and gone that far, why not just flash the xceed kernel, as I can confirm I have it working on lastest stock build with xceed and su
Click to expand...
Click to collapse
Ok I will try to do that!
beardymcgee said:
TBH, this may only work with root, given the unique architecture of the pixel c or something else.
But seeing as you have flashed twrp and gone that far, why not just flash the xceed kernel, as I can confirm I have it working on lastest stock build with xceed and su
Click to expand...
Click to collapse
I have flashed the kernel and rooted the device. It is all working great on the new build.
P.S: I also enabled the Multi-Window feature and it is working great
Every device I've ever had has been bootloader-unlocked and rooted within hours of receiving it.
However, with the Nexus 6P, I didn't think the hassle of losing android pay and OTA updates was worth it since the device works so well as stock.
I've seen the posts about porting the Pixel-exclusive features to the 6P via build.prop edits. However, as far as I'm aware, changes to the system partition break both of the above.
Is there a way to modify system files like build.prop without breaking OTA updates and Android Pay?
chrispy_212 said:
Every device I've ever had has been bootloader-unlocked and rooted within hours of receiving it.
However, with the Nexus 6P, I didn't think the hassle of losing android pay and OTA updates was worth it since the device works so well as stock.
I've seen the posts about porting the Pixel-exclusive features to the 6P via build.prop edits. However, as far as I'm aware, changes to the system partition break both of the above.
Is there a way to modify system files like build.prop without breaking OTA updates and Android Pay?
Click to expand...
Click to collapse
It's not just modification to the system partition alone. It has to be specific modifications.
build.prop may be one of those but, I have modified multiple files and that didn't kill safetynet checks.
I'm on the latest version, not rooted, custom recovery and kernel. I used the 2 zips and my AP worked with no issue. I bought something using a vending machine with no issue and have assistant working also.
Ok but, the question is: is there a way to edit build.prop without a custom recovery and flashing a zip?
Maybe through adb?
thegios said:
Ok but, the question is: is there a way to edit build.prop without a custom recovery and flashing a zip?
Maybe through adb?
Click to expand...
Click to collapse
No. If you're stock, no root or custom recovery, then no. dm-verity will overwrite your changes on boot and your build.prop will be stock again.
Enabling Assistant via build.prop tweak won't break Android Pay (shouldn't, at least), but it will cause the OTA to fail, even with systemless root / mods.
Hey crew. I rooted my 6P using Heisenberg's guide to get the pixel goodies and while i was there i switched the emojis. After everything was done i deleted superuser from the device to use apps that won't work on rooted devices (i.e. Snapchat).
Works perfectly, but now that google has released npf26f i'm afraid to hit install on it since i have made "permanent" changes to the system. Is it safe to install or should i choose an other way? What could that way be?
Thanks in advance!
you should do the following
re-root
undo changes
apply update via adb
make changes again
unroot
or if you want to do it without flashing factory images
re-root
undo changes
un-root
apply ota
re-root
apply changes
unroot.
tmfvde said:
Hey crew. I rooted my 6P using Heisenberg's guide to get the pixel goodies and while i was there i switched the emojis. After everything was done i deleted superuser from the device to use apps that won't work on rooted devices (i.e. Snapchat).
Works perfectly, but now that google has released npf26f i'm afraid to hit install on it since i have made "permanent" changes to the system. Is it safe to install or should i choose an other way? What could that way be?
Thanks in advance!
Click to expand...
Click to collapse
The update will fail if you hit install.
You can install factory images via fastboot manually (don't flash data image, it will wipe data).