recently my 6t got boot loop due to edit in build prop
and i dont have a backup so can anybody provide me stock build.prop of oneplus 6t
Just reflash the system partition
Sent from my OnePlus6T using XDA Labs
alexander lama said:
recently my 6t got boot loop due to edit in build prop
and i dont have a backup so can anybody provide me stock build.prop of oneplus 6t
Click to expand...
Click to collapse
I put a copy of mine here > https://drive.google.com/file/d/10fQZ48sSBT21qXsprtDRcJ2vYOGmXuBe/view?usp=drivesdk
Sent from my ONEPLUS A6010 using Tapatalk
If you're messing with your phone, make sure to install TWRP.
In TWRP go to Settings > Fix Recovery Bootloop
This will UNROOT your phone, but should let you boot.
Related
Link to the developer Preview for anyone interested
https://developer.android.com/preview/download.html#top
I'm currently rooted, with TWRP. So ideally how to install and keep everything and I assume you just flash supersu.zip to root again.
TIA.
flashfire.
Thanks, just tried, but it doesn't seem to recognized this zip from the link above
angler-npf26f-factory-0cd1829d.zip
Is there a different zip to flash?
install it as firmware
Use fastboot and to save your data, don't flash userdata.img.
https://www.youtube.com/watch?v=dsKn2E68A0M
Quick q on the subject. Twrp, rooted, dp1, modded build.prop, flashed Pixel bootanimation and navbar buttons. I suppose I can't use flashfire, right?
Puck24 said:
Quick q on the subject. Twrp, rooted, dp1, modded build.prop, flashed Pixel bootanimation and navbar buttons. I suppose I can't use flashfire, right?
Click to expand...
Click to collapse
I have the same setup and also want to know how to flash without losing anything. Also would rather not adb. Will flashfire do this without losing root?
Also, I went to the OP link to get the ota, and it's just a Google page on how to test an update. Where do I get the update file?
Same here.
Sent from my Pixel XL using XDA-Developers mobile app
I actually got the OTA notification sometime in the last 8 hours while I was asleep. Saw some1 posting the link in the General section, I think
I also have (had) all the pixel goodies installed and flashed the OTA with FlashFire. Now everything is gone
I used FF. If you unchecked recovery and check modem, you'll keep recovery and root. Pixel goodies are gone, but easy to reflash
Confirm: you loose Pixel stuff but just reflash, only strange thing is that I had to flash Pixel Launcher thru twrp as with FlashFire it was not working.
Did you flashfire the OTA or the Factory Image of the DP2?
Enviado de meu Pixel XL usando Tapatalk
Factory image from here
https://developer.android.com/preview/download.html#device-preview
Carterman32 said:
I used FF. If you unchecked recovery and check modem, you'll keep recovery and root. Pixel goodies are gone, but easy to reflash
Click to expand...
Click to collapse
You did put the factory image on your nexus and then press the + button and flash firmware? Is that it? And then you can select to keep your datas and root?
And in order to keep TWRP, do I uncheck recovery or it will keep TWRP anyway?
Thanks in advance.
I unzipped and flashed just system.img in TWRP, followed by SuperSu, and then modified the vendor/build.prop to match the system/build.prop to keep from getting the "internal problem" alert. Maybe not the simplest method, but worked fine.
Sent from my Pixel XL using Tapatalk
timosuomi said:
I unzipped and flashed just system.img in TWRP, followed by SuperSu, and then modified the vendor/build.prop to match the system/build.prop to keep from getting the "internal problem" alert. Maybe not the simplest method, but worked fine.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Unless you have a specific desire not to do this, flash the matching vendor.img in TWRP. This is tied to that "internal problem" warning because of the proprietary drivers included in the file.
Also, I do not recommend flashing just the system.img for every update. You may run into a non functional camera when Google releases an OTA that requires the latest boot and vendor to be installed.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Unless you have a specific desire not to do this, flash the matching vendor.img in TWRP. This is tied to that "internal problem" warning because of the proprietary drivers included in the file.
Also, I do not recommend flashing just the system.img for every update. You may run into a non functional camera when Google releases an OTA that requires the latest boot and vendor to be installed.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Good call. I'm just coming from a Nexus 6, and I don't recall dealing with vendor.img with that or previous Nexii.
Sent from my Pixel XL using Tapatalk
timosuomi said:
Good call. I'm just coming from a Nexus 6, and I don't recall dealing with vendor.img with that or previous Nexii.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Ahh, that makes sense now. The vendor partition was originally part of the system. The Nexus 9 was the first Android device to feature a separate vendor partition and both 2015 Nexus devices launched with this separate partition.
Flash boot, system, and vendor each month OR whenever you move to a different month's OTA. With custom roms, just flash the vendor and custom rom. You can check /vendor/build.prop to see which vendor is currently installed.
Sent from my Nexus 5X using Tapatalk
Wanting to upgrade to Oreo but am unencrypted. I would like keep my phone as is. Would I need to wait for a modified boot image or can I go ahead and install the factory images?
Sent from my Nexus 6P using Tapatalk
afbengochea said:
Wanting to upgrade to Oreo but am unencrypted. I would like keep my phone as is. Would I need to wait for a modified boot image or can I go ahead and install the factory images?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Every OS enforces encryption. You need to wait for a modified boot image or custom kernel.
Sent from my Nexus 5X using Tapatalk
The solution can be rather simple.
Do the update, and right away boot to bootloader. Flash ElementalX kernel or any other boot image of your choice and voila.. no harm done and the system won't be encrypted.
afbengochea said:
Wanting to upgrade to Oreo but am unencrypted. I would like keep my phone as is. Would I need to wait for a modified boot image or can I go ahead and install the factory images?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
We haven't needed to wait for a modified boot image for a long time. If you decide to flash the factory image, just make sure that when it's finished (before booting to the OS for the first time) you either flash SuperSU or a custom kernel like EX. Both of these modify the boot.img to no-force encrypt. If rooted, you can also use FlashFire to flash the image. It will preserve root, modify the boot.img to no-force encrypt and keep your custom recovery.
For those who are looking for the factory Images they were just posted ?
https://developers.google.com/android/images
Maybe we will get a new recovery soon.
Sent from my Nexus 5X using XDA-Developers Legacy app
Anyone tried Magisk (14.3+) with the stock boot image installation method yet?
FSMcas said:
Anyone tried Magisk (14.3+) with the stock boot image installation method yet?
Click to expand...
Click to collapse
I created a patched_boot.img using Magisk 14.3 on my Pixel 2 which is around 23MB... the original is about 32MB, so I didn't bother trying to flash it. I'll try generating on another rooted device and see if it yields the same result.
Pixel 2 XL seems to have the same issue btw. --> https://forum.xda-developers.com/showpost.php?p=74269377&postcount=4340
Hello all,
THIS IS AN ANNOUNCEMENT, DISCUSSION AND INFORMATION THREAD FOR OFFICIAL DIRTY UNICORNS 14.x BUILDS FOR PIXEL 2 XL (taimen).
Special thanks to all who were and are involved in the development and also to the maintenance of this ROM.
Flashing instructions:
Go to TWRP
Factory reset
Flash ROM and TWRP zip
Reboot and enjoy!!
If on a previous DU build:
Go to TWRP
Flash ROM and TWRP zip
Reboot and enjoy!!
Note:
If you're going to flash magisk make sure you flash it after you've booted the OS once.
Reminder
Weeklies and official builds are signed with private keys. This means that if you’re on the first official build or last week’s weekly, you can dirty flash this official build. If you’re on anything other than that and want to use this build you MUST perform a full wipe in recovery. If you decide to disregard this and flash this build or a weekly on top of anything, you will not be able to boot. Have fun looking at a black screen
ANY BUGS MAY BE DISCUSSED HERE OR WITH THE DEVELOPMENT TEAM ON THEIR TELEGRAM CHANNELONLY IF YOU HAVE CLEAN FLASHED
Reserved
its an excellent rom! i helped test here n there n can confirm its almost completely bug free
elliwigy said:
its an excellent rom! i helped test here n there n can confirm its almost completely bug free
Click to expand...
Click to collapse
Can you tell how is the camera quality on that?
And they have listed audi during video is janky is that for stock camera or for apps like whatsapp and snapchat too?
Sent from my Google Pixel 2 XL using XDA Labs
Been waiting very impatiently for this lol
Prattham said:
Can you tell how is the camera quality on that?
And they have listed audi during video is janky is that for stock camera or for apps like whatsapp and snapchat too?
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Just might be seldom janky...not all the time...I've tested stock DU cam, WhatsApp, Facebook, Instagram.... all working fine on all 3 different occasions:good:
Cam quality is as good as stock
No hangups...lags...or other issues
I will be using it as my daily driver
amandeepparmar said:
Just might be seldom janky...not all the time...I've tested stock DU cam, WhatsApp, Facebook, Instagram.... all working fine on all 3 different occasions:good:
Cam quality is as good as stock
No hangups...lags...or other issues
I will be using it as my daily driver
Click to expand...
Click to collapse
Can you post screenshot of the du tweaks that are currently in the rom?
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
Can you post screenshot of the du tweaks that are currently in the rom?
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
DU Tweaks...check screenshots attached
amandeepparmar said:
DU Tweaks...check screenshots attached
Click to expand...
Click to collapse
Good
What steps did you followed to install?
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs
amandeepparmar said:
DU Tweaks...check screenshots attached
Click to expand...
Click to collapse
Factory reset in twrp. flash rom and twrp. Setup phone and flash afterwards kernel and magisk if needed
Anyone know if it has support for esim on Fi?
Flashing this will remove TWRP and Magisk. Just wanted to throw that out there.
MacTheRipperr said:
Flashing this will remove TWRP and Magisk. Just wanted to throw that out there.
Click to expand...
Click to collapse
Yes it will according to what I've been reading. I just got my pixel and have been trying to catch up with all the new a and b slots and how recovery is now baked into the boot.img, so from what I understand is that if you flash anything new such as rom or kernel a flash of both twrp and your choice of root is needed also or you will have stock recovery. So much different from my Nexus 6P. Lol. I have a lot to learn that's for sure
Sent from my Pixel 2 XL using XDA-Developers Legacy app
This rom is awesome !! DU always bring the goods
I've been running since yesterday. Spaceman killed it! Amazing work, where can we donate?
MacTheRipperr said:
Flashing this will remove TWRP and Magisk. Just wanted to throw that out there.
Click to expand...
Click to collapse
Yes but you can reflash twrp and magisk with absolutely no errors ,also twrp has no touch issues with the kernal that's already baked in rom!!!! It's a great rom!
Anyone else having trouble getting this to boot?
I've followed the instructions exactly. Reboot to TWRP (3.2.1-0), factory reset via the wipe menu, install the ROM .zip followed by the TWRP installer zip.
Go to reboot, TWRP asks me if I'm sure I want to do this as there's not an OS installed. I don't know what else to do other than say 'yes' and then it boots to the Google logo with the unlocked icon at the bottom of the screen and just hangs indefinitely at that point. Tried redownloading and recopying the ROM .zip to internal storage and all steps again too.
Any ideas? I've wiped this damn phone so many times and flashed the factory images so many times trying to get a custom ROM to work I'm about to give up. And my phone seems to damn janky where sometimes it does that same freeze on boot (or freezes on the TWRP splash screen) but then a quick reboot will fix it. Doesn't make any sense.
ohlin5 said:
Anyone else having trouble getting this to boot?
I've followed the instructions exactly. Reboot to TWRP (3.2.1-0), factory reset via the wipe menu, install the ROM .zip followed by the TWRP installer zip.
Go to reboot, TWRP asks me if I'm sure I want to do this as there's not an OS installed. I don't know what else to do other than say 'yes' and then it boots to the Google logo with the unlocked icon at the bottom of the screen and just hangs indefinitely at that point.
Any ideas? I've wiped this damn phone so many times and flashed the factory images so many times trying to get a custom ROM to work I'm about to give up. And my phone seems to damn janky where sometimes it does that same freeze on boot (or freezes on the TWRP splash screen) but then a quick reboot will fix it. Doesn't make any sense.
Click to expand...
Click to collapse
I went back to latest stock using deuces script. Boot twrp. Flash twrp then the rom...boot the rom. Go back into twrp and flash magisk
I had no problems getting it to boot, I followed the op. Factory reset, flash ROM, flash magisk, flash twrp and boot into system. It booted right up no problems
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Reuben_skelz92 said:
I went back to latest stock using deuces script. Boot twrp. Flash twrp then the rom...boot the rom. Go back into twrp and flash magisk
Click to expand...
Click to collapse
Did you let the phone do it's initial boot after deuce's script ran? Or just stayed in fastboot mode, fastboot booted to TWRP, and flash the ROM and TWRP installer zip?
Also, did you format userdata when given the option in deuce's script? And you flashed TWRP before the ROM? I was under the understanding that the ROM flash would erase the TWRP install.
EDIT: I didn't format userdata, didn't reboot afterwards (just booted straight into TWRP and proceeded), and flashed TWRP before ROM and now it is indeed booting. Just need to figure out now whether or not TWRP is still installed. Many thanks! Deuce's must have fixed something I must have janked I guess.
EDIT2: Yeah appears TWRP should be flashed after the ROM not (just) before like the DU post says. I'm back to stock recovery afterwards.
So, I've gone back to LineageOS for Android 10 on my v20(vs995) and I rooted via magisk.. Why can't I edit any system files or anything related to the system? I can't edit permissions for system files, can't install BusyBox to system, can't edit buildprop, etc.
I've tried resetting the system even and still nothing.. Help please
Thanks.
texas7412 said:
So, I've gone back to LineageOS for Android 10 on my v20(vs995) and I rooted via magisk.. Why can't I edit any system files or anything related to the system? I can't edit permissions for system files, can't install BusyBox to system, can't edit buildprop, etc.
I've tried resetting the system even and still nothing.. Help please
Thanks.
Click to expand...
Click to collapse
You can no longer make changes to system it is all done systemlessly in magisk, refer to the magisk thread for more info
Sent from my LG-H910 using XDA Labs
cnjax said:
You can no longer make changes to system it is all done systemlessly in magisk, refer to the magisk thread for more info
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Why on earth would they do this?..magisk is just getting to be more of a pain... SuperSU was such a simple root method but it doesn't work anymore
Thanks though.
texas7412 said:
Why on earth would they do this?..magisk is just getting to be more of a pain... SuperSU was such a simple root method but it doesn't work anymore
Thanks though.
Click to expand...
Click to collapse
Changes Google made to the Android OS forced magisk to adapt
Sent from my LG-H910 using XDA Labs