System update today - Google Pixel XL Questions & Answers

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm rooted and running ex kernel
I'm assuming I DO NOT want to apply this update lest I lose root and kernel ??
Sent from my Pixel XL using XDA-Developers Legacy app

It will fail. You should install the update and then reroot and rekernel. Just grab the full image, edit the flashall bat file and remove the-w to save your data.

jk8260 said:
DO NOT DO THIS IF YOU DO NOT KNOW WHAT YOU ARE DOING,
OR AT LEAST DO NOT BLAME ME WHEN YOU PHONE STARTS ON FIRE
- Started with 8.0 August, SU rooted with SUHide on TMO
(working Substratum, Adaway and Android Pay)
- Downloaded September Factory Image
marlin-opr1.170623.026-factory-1ed9b4b2.zip
- Unzip factory image to \marlin-opr1.170623.026\
- Removed the -W from the FlashAll.bat
- Copy \platform-tools\ folder to \marlin-opr1.170623.026\ (so you have adb & fast boot in same folder as flash-all.bat)
- Connect Pixel to PC USB
- open command prompt in \marlin-opr1.170623.026\
- check you can see the pixel
adb devices
- Boot the device into bootloader
adb reboot bootloader
- Run the Flash-All.bat (phone will reboot several times)
- Once done it will reboot to system
If you want root, re-root again the same as before, works fine...
used - ([Guide] How to systemlessly root your Pixel XL on Android 8.0 (SuperSU) ) in this forum
I still have my substratum themes intact, everything is working smooth.
Click to expand...
Click to collapse
I used this method provided by jk8260. Make sure you download the September image that applies to your phone.

Is marlin-opr1.170623.026 the one that works with Verizon's Pixel XL?
Edit: Maybe nevermind. Verizon's website says OPR3.170623.007.
Source: https://www.verizonwireless.com/support/google-pixel-xl-update/

Related

Xperia Pro MK16i 0.62

Hi I have updated to the most recent firmware, 0.62a and the phone has not been rooted or modded in anyway before.
Is it still the case that I need to downgrade the firmware to root the phone?
Thanks for any help in advance
Try to flash this file (below) in CWM. it should work.
But remember about BACKUP!
I downloaded the file you attached thanks and downloaded ROM Manager on my phone but it says O clicked on CWM Recovery and it says I must install it manually to proceed.
Sorry im a noob to this, so just want to make sure I get it right
here i found easier method - without using reovery and .zip:
Crowds said:
HOW TO ROOT​
Start Flashtool
Connect the device to the computer and wait until it's recognized
Click the icon with the "Padlock [the second in a row]
FT will start pushing files, wait till it finishes. Meanwhile the phone will reboot once.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When it's over Flashtool will notify "Root Access Allowed"
Open the application list on the phone and look for the app "Superuser"
If "Superuser" is there you have Rooted your device successfully.
Congrats!
note: edited by G-FACE at November 25th
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showthread.php?p=19684995
if it wont work here u have how to install recovery to flash .zip:
http://forum.xda-developers.com/showpost.php?p=19684995&postcount=6
Hi thanks for taking the time to post that mate, but no joy -
07/005/2012 15:05:40 - INFO - Running part2 of Root Exploit
07/005/2012 15:05:40 - INFO - Running rootit2
07/005/2012 15:05:40 - ERROR - Cleaning rootit files
Mounting /system R/W
FTError
Click to expand...
Click to collapse
ask Crowds its his method
or try second one

[BOOT] Unsecured boot.img for V10

Hey guys, as you already might have noticed, I am a bit active regarding development for this device. This is all thanks to @JoseVigil as he sent me a device.
While working on the workaround to disable offline charging, I got to know the device a bit, also regarding security measures of the bootloader to not accept custom boot and recovery images.
However, I have a way to modify the images so the bootloader doesn't throw me a security error but accepts the images.
With that being said, it's time for an unsecured boot image.
In case you don't know what "unsecured" means, these are the key features:
ADB on early boot
ADB as root by default
Enabling "adb remount"
Requirements
V10 firmware
Root
A working adb environment
How to flash:
Download the .img file to the root of your internal sd (/sdcard)
Open an adb shell as root
run the following command:
Code:
dd if=/sdcard/unsecured_boot.img of=/dev/block/mmcblk0 bs=1024 seek=18432
reboot the device and be happy
The next step is a properly working CWM recovery, and as it turns out, I happen to have a sneak peek
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And for GPL reasons, I have used the stock zImage.
zimage
hi can you upload the stock boot.img?
thanks and congratulations for you great work
Can't everything
I cant do it. :v
I just wanna cwm so I can backup whole device, and I also cant upgrade to kitkat bcoz of root, I already fully unroot my superuser but It still detects root.
Tested CWM_5.5.0.4_d680.img on LG G686 with D68620d-EUR-XX ROM it is 4.4.2 and it works.
Unsecured boot.img for V10 is not flash only CWM_5.5.0.4_d680.img beacose i am on D68620d-EUR-XX ROM it 20d version.
Thanks for your hard work hope that you will provide Unsecured boot.img for V20d.
I can upload boot.img for V20d if you have time to make unloked bootloader for as with D68620d-EUR-XX ROM.

Pixel assistant

how to enable pixel assistant on op3 without xposed?
You can't
daleski75 said:
You can't
Click to expand...
Click to collapse
You can
Requirements
Android 7.0 or higher
SuperSU or kernel with dm-verity disabled
Latest Google app (6.5.35.21 or newer)
build.prop tweaks
Method 1: Manual editing
Just add or replace these lines on your build.prop:
Code:
ro.product.model=Pixel XL
ro.opa.eligible_device=true
Method 2: Flashable ZIP by @FaserF
Link: http://forum.xda-developers.com/showpost.php?p=69074667&postcount=112
Work for me on tesla N rom and I didn't flash xposed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Amandroid said:
You can
Requirements
Android 7.0 or higher
SuperSU or kernel with dm-verity disabled
Latest Google app (6.5.35.21 or newer)
build.prop tweaks
Method 1: Manual editing
Just add or replace these lines on your build.prop:
Code:
ro.product.model=Pixel XL
ro.opa.eligible_device=true
Method 2: Flashable ZIP by @FaserF
Link: http://forum.xda-developers.com/showpost.php?p=69074667&postcount=112
Click to expand...
Click to collapse
He did not specify if he was rooted, unlocked, running MM or N so if he is stock = NO, not stock then yes I agree you can but buy the wording on his post I would assume he is running stock MM.
Yes sure you are right I just wanted to showed him the way to have Google assistant, even if in 1 second of research he could have found it by himself....
Amandroid said:
Yes sure you are right I just wanted to showed him the way to have Google assistant, even if in 1 second of research he could have found it by himself....
Click to expand...
Click to collapse
I get it but next time tell him to search spoon-feeding is a disease here and it's accompanied by lazy people.. Not you***
See my sig

How to upload the original build.prop file?

Hey,
I made root on my Shield TV 2017 16GB. All worked great.
I decided to edit the bulid.prop file to change the device name, but I don't think I did everything right.
I made a copy of this file on a PC before editing.
The trouble is that the device does not start. The Nvidia logo and the animation of the android logo are shown, which loads indefinitely.
I started the menu with A + B. I chose option 2 (Boot recoovery kaenel) and the second menu came up.
I chose (apply upade from ADB).
ADB detects the device in "sideload" mode.
Can I upload the file itself?
Do I need to restore the entire system?
Sorry for my bad English.
Best regards,
Menu 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Menu 2
use twrp to push the build.prop to system..
if u cant figure it out then flash stock and start over
you can only flash official updates through stock recovery and adb sideload
elliwigy said:
use twrp to push the build.prop to system..
if u cant figure it out then flash stock and start over
you can only flash official updates through stock recovery and adb sideload
Click to expand...
Click to collapse
Thank you. I was able to upload files using ADB Sideload.
The system started and works as it should.

Root Realme 9 4G (RMX3521) Without Custom Recovery

Hello,
As we all know there is no Custom Recovery available yet for our device. I decided to root the device with patched_boot.img.
I am able to root my Realme 9 4G successfully. I am sharing the procedure if someone like me, who cannot use a android mobile without root can follow the steps to root his Realme 9.
Before starting Make sure you are on RMX3521_11_A.31.
As the attached boot.img files are only for RMX3521_11_A.31.
To check your OS version Go to Settings > About device > Version and Match your Build Version. It should be RMX3521_11_A.31
First of all you have to unlock the bootloader.
Follow this Guide to unlock your bootloader.
Once your Bootloader is Unlocked. Follow the steps below
1. Download the magisk_Patched_boot.img from attachment and move it your PC.
2. Reboot your device into bootloader.
3. Open cmd in adb & fastboot directory and type the command
Code:
fastboot flash boot <drag magisk_patched_boot.img here>
And press enter.
4. Now restart your device by entering the command
Code:
fastboot reboot
5. Download the Magisk Manager and install it.
Your Device is Rooted Now. Make sure to disable the auto software update to avoid getting bootloop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Btw there is an unofficial custom recovery for this device. It works and is tested. Here's the github link; https://github.com/cd-Crypton/custom_recovery_tree_realme_messi

Categories

Resources