I just got my Pixel XL today through Verizon. It arrived with the following system:
Android Version 7.1
Security Patch Level: October 5, 2016
Build Number: NDE63P
Kernel Version: 3.18.31g895c4a6
Before taking any updates, I unlocked the bootloader. I have not rooted yet.
My questions are:
Should I take the new 01-2017 update?
Would it fail because the bootloader is unlocked?
If I can successfully update, will I be able to root on the new update?
Should I just say screw it and root on current system and just start flashing ROMs?
Any input or advice is appreciated!
Thank you!
bendrum30 said:
I just got my Pixel XL today through Verizon. It arrived with the following system:
Android Version 7.1
Security Patch Level: October 5, 2016
Build Number: NDE63P
Kernel Version: 3.18.31g895c4a6
Before taking any updates, I unlocked the bootloader. I have not rooted yet.
My questions are:
Should I take the new 01-2017 update?
Would it fail because the bootloader is unlocked?
If I can successfully update, will I be able to root on the new update?
Should I just say screw it and root on current system and just start flashing ROMs?
Any input or advice is appreciated!
Thank you!
Click to expand...
Click to collapse
Yes
No
Yes
Probably not
bendrum30 said:
I just got my Pixel XL today through Verizon. It arrived with the following system:
Android Version 7.1
Security Patch Level: October 5, 2016
Build Number: NDE63P
Kernel Version: 3.18.31g895c4a6
Before taking any updates, I unlocked the bootloader. I have not rooted yet.
My questions are:
Should I take the new 01-2017 update?
Would it fail because the bootloader is unlocked?
If I can successfully update, will I be able to root on the new update?
Should I just say screw it and root on current system and just start flashing ROMs?
Any input or advice is appreciated!
Thank you!
Click to expand...
Click to collapse
With your unlocked bootloader, you can take the new OTA without issues. New OTAs (so far) do not relock the bootloader. The January OTA runs very nice.
If you want to put TWRP recovery, you can do that and root or custom kernel next after installing the Jan. OTA.
If you flash TWRP, a custom kernel, or root it, it will not take another OTA because only an unmodified system
can receive it.
hi i need the OTA zip file for the Moto Z Play because i used to have free unlimited wifi hotspot until i updated the phone,
I already have the Android 7.1.1 update but things keep crashing all the time, is it posible for me to downgrade the os?
the phone is unlocked
model : XT1635-02
Below is the method I know of but it seems people have had issues after upgrading to 7.1.1 so you may not be able to down grade at this moment.
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
I will advise you that it is a bad idea to downgrade. After the April 7.0 patch, downgrading to Marshmallow and OTAing back to Nougat will result in a hard brick, which cannot be repaired without the necessary blank flash files, which are not available.
IncendiaryPyro said:
I will advise you that it is a bad idea to downgrade. After the April 7.0 patch, downgrading to Marshmallow and OTAing back to Nougat will result in a hard brick, which cannot be repaired without the necessary blank flash files, which are not available.
Click to expand...
Click to collapse
I've read about this issue. So basically only for those who had the April 7.0 patch on their Moto Z play will hard brick the device? When they downgrade and update? I've downgraded plenty of times, but decided not to OTA back to nougat.. Now I'm worried if I accidently OTA to Nougat will my phone get hard bricked?
Dchoi229 said:
I've read about this issue. So basically only for those who had the April 7.0 patch on their Moto Z play will hard brick the device? When they downgrade and update? I've downgraded plenty of times, but decided not to OTA back to nougat.. Now I'm worried if I accidently OTA to Nougat will my phone get hard bricked?
Click to expand...
Click to collapse
According to a user here, the brick happens when you install the April security update, downgrade to Marshmallow, then OTA back to Nougat, typically bricking on the first, initial update to Nougat. I've downgraded from the January patch once back to Marshmallow, then OTA'd to Nougat + February, then N + March whenever my carrier released it without any issues. I have not received the April patch yet though, but I think you're good.
Awesome. I think it's time to stop flashing roms now lmao.. I dont wanna brick my phone.
Dchoi229 said:
Awesome. I think it's time to stop flashing roms now lmao.. I dont wanna brick my phone.
Click to expand...
Click to collapse
I just got the April patch today, and it has not bricked my phone, so if you've never installed that update, you should be okay to OTA.
ok, im confused, I want to downgrade from nougat 7.1.1 to android mm 6.0 with adb, my phone is not rooted i just want to downgrade normally to have hotspot again
robertriverabula said:
ok, im confused, I want to downgrade from nougat 7.1.1 to android mm 6.0 with adb, my phone is not rooted i just want to downgrade normally to have hotspot again
Click to expand...
Click to collapse
you can't downgrade unless you unlock the bootloader, and are ok with potentially turning your phone into a brick.
robertriverabula said:
ok, im confused, I want to downgrade from nougat 7.1.1 to android mm 6.0 with adb, my phone is not rooted i just want to downgrade normally to have hotspot again
Click to expand...
Click to collapse
Ah, I finally find out that I am not the only one with hotspot issue on 7.1.1. But 7.1.1 is so good that I am not going to downgrade only for the hotspot issue. I will wait for the Official 7.1.1 release to fix that issue.
IncendiaryPyro said:
I just got the April patch today, and it has not bricked my phone, so if you've never installed that update, you should be okay to OTA.
Click to expand...
Click to collapse
Great. I've heard that the reason for why people are bricking their phone is because of the updated bootloader? The April patch updates the BL to C1.07 and mine right now is 1.05. Do you think I can flash the Xenon HD rom (7.1.1) and if for some reason i want to downgrade again i wont brick my phone?
Dchoi229 said:
Great. I've heard that the reason for why people are bricking their phone is because of the updated bootloader? The April patch updates the BL to C1.07 and mine right now is 1.05. Do you think I can flash the Xenon HD rom (7.1.1) and if for some reason i want to downgrade again i wont brick my phone?
Click to expand...
Click to collapse
Hi just wondering what is the security patch you have? I mean you have c1.05 is it MM?
Kap_Tutan said:
Hi just wondering what is the security patch you have? I mean you have c1.05 is it MM?
Click to expand...
Click to collapse
dont get confused. I never downloaded the april security patch. my bootloader version is c1.05 which i believe is the feb patch. the april patch is c1.07. If you downloaded the April patch and downgraded do not try to install the ota. it will brick your phone.
What's the reason for hard brick ?
When downgrading then receiving OTA Update .
I'm currently on the May security update (NPN25.137-24.4) with TWRP and Magisk. I can't find the stock ROM for this update so I have no way to return to stock May update. Can I flash oem/boot/logo/recovery/system from the April update to "return" to the April update and take the OTAs that way?
I ask because I'm aware of the people downgrading to MM from Nougat and then taking OTAs bricking their device due to different bootloaders.
Afaik, downgrading to mm and then accepting ota will brick your device.
Wait for someone else to confirm.
Sent from my XT1635-02 using Tapatalk
hmmm. bump. the last stock rom before 7.1.1 is still not available anywhere.
To add onto this thread, why isn't there a 7.1.1 stock rom uploaded anywhere?
I bit the bullet and flashed the previous version to return to stock. It worked fine. Updating to 7.1.1.
Now... does anyone have a 7.1.1 stock image anywhere for me to be able to return to stock later? Whenever I try
fastboot boot twrp.img
It just locks up at the TWRP splash screen (using Alberto's twrp port, 3.1.1)
SAGExSDX said:
does anyone have a 7.1.1 stock image anywhere for me to be able to return to stock later?
Click to expand...
Click to collapse
there's still no image of 7.1.1 for the Addison, maybe in a few months
you can downgrade avoiding the gpt.bin and (I believe)the bootloader.bin, after that you can download the OTA file from the forum and install it, check the forum for more info
are you sure that's safe? I felt ok going from 7.0 may update to 7.0 april update cuz I was sure there wasn't a change in bootloader or anything. But going from 7.1 to 7.0 to take the OTA sounds like the exact same scenario as ppl who went from 7.0 to 6.0 and then bricked their device when taking OTAs.
Try this, although it's from Verizon but works for other devices as well without any issues.
"https://www.androidfilehost.com/?fid=673368273298982188"
ROM_HUNTER said:
Try this, although it's from Verizon but works for other devices as well without any issues.
"https://www.androidfilehost.com/?fid=673368273298982188"
Click to expand...
Click to collapse
Isn't that for the Moto Z, not the Moto Z Play?
SAGExSDX said:
Isn't that for the Moto Z, not the Moto Z Play?
Click to expand...
Click to collapse
Yeah, that's for Moto Z (griffin), you'll want ROMs labelled as addison for Moto Z Play.
No sign of a 7.1.1 fastboot stock ROM for Moto Z Play as of yet, from what I can see.
SAGExSDX said:
Isn't that for the Moto Z, not the Moto Z Play?
Click to expand...
Click to collapse
Yeah, my bad, this is the one for Addison.
"https://www.androidfilehost.com/?fid=889764386195928508"
'https://www.androidfilehost.com/?fid=673368273298986785"
Hi there,
Just like the title says.
Xprivacylua won't' work on Android 13 for me. what I was wondering is whether I can downgrade without flashing the bootloader.
I am going to follow the following guide but am afraid to get a bricked phone
How to Bypass Anti Rollback Mechanism in Pixel 6A/6/6 Pro
This guide will show you how to bypass Anti Rollback Mechanism while doing a downgrade from Android 13 to Android 12 on Pixel 6A/6/6 Pro.
www.droidwin.com
Thank you all
------------------------add---
finally managed to downgrade to Android 12, just add --force before update:
fastboot --force update image-oriole-sq3a.220705.001.b2.zip (m phone is pixel6)
then reboot, then choose factory reset.
credits @Bunnehbunn
If you do it, regardless if you succeed or fail, you and your phone shall forever be remembered. And this day
forth shall always be named bush911 Pixel 6 Pro Day. And it shall be written and stories will be told from one generation to the next.
If you do it, the inner Yoda in me tells me to tell you to make sure you flash BOTH slots. Godspeed.
smokejumper76 said:
If you do it, regardless if you succeed or fail, you and your phone shall forever be remembered. And this day
forth shall always be named bush911 Pixel 6 Pro Day. And it shall be written and stories will be told from one generation to the next.
If you do it, the inner Yoda in me tells me to tell you to make sure you flash BOTH slots. Godspeed.
Click to expand...
Click to collapse
You've made my day
I am going to wait and see for several days before proceeding as I just know how to flash-all, I have never flashed step by step or flashed to the specific slots.
I know that Android 12 worked just fine with Android 13's bootloader, but that was before I actually upgraded to 13. After I fully upgraded to 13, I wasn't willing to test downgrading everything but the bootloader since I would have to wipe in order to have app data be consistent with the Android version.
I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine. If you do this, remember to wipe (and have a backup of anything you want to keep from your internal storage), and downgrade on both slots, not just your active slot.
roirraW edor ehT said:
I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine.
Click to expand...
Click to collapse
Oh, I have to find that post. I knew someone was talking about trying that but didn't see that they actually did. Let's see how good of a friend search really is to me
roirraW edor ehT said:
I know that Android 12 worked just fine with Android 13's bootloader, but that was before I actually upgraded to 13. After I fully upgraded to 13, I wasn't willing to test downgrading everything but the bootloader since I would have to wipe in order to have app data be consistent with the Android version.
I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine. If you do this, remember to wipe (and have a backup of anything you want to keep from your internal storage), and downgrade on both slots, not just your active slot.
Click to expand...
Click to collapse
Is downgrading on both slots a must? I have just flashed Android 13 bootloader on both slots. For now chrome (stable, beta and development) keeps crashing. I can't even finish writing this reply on Chrome.
tried clearing the cache, restarting etc., ended up with no luck . It turned out that Chrome often closes itself within no more than 5 minutes of browsing after downloading to Android 12
Post before crashing
.
bush911 said:
Is downgrading on both slots a must?
Click to expand...
Click to collapse
If you want to run Android 12 instead of 13, and you've already flashed 13 to both slots, or at least 13's bootloader to both slots (which you should definitely do if you haven't), then yes, you should downgrade both slots and wipe to start fresh.
You can't expect both Android 12 and Android 13 to operate with the same app data, so having a different version of Android on the other slot isn't going to do you any favors.
bush911 said:
I have just flashed Android 13 bootloader on both slots. For now chrome (stable, beta and development) keeps crashing. I can't even finish writing this reply on Chrome.
tried clearing the cache, restarting etc., ended up with no luck . It turned out that Chrome often closes itself within no more than 5 minutes of browsing after downloading to Android 12
Post before crashing
.
Click to expand...
Click to collapse
Try a factory reset?
Lughnasadh said:
Oh, I have to find that post. I knew someone was talking about trying that but didn't see that they actually did. Let's see how good of a friend search really is to me
Click to expand...
Click to collapse
Here my friend. Also in the OP.
Partial quote:
I tried this as soon as I upgraded to 13 and yes you can downgrade down to Android 12 after upgrading with no noticable issues. The radio and every other image but the bootloader can be downgraded. But I only tried 003, 004 July images for oriole so I don't know about anything lower personally.
Click to expand...
Click to collapse
roirraW edor ehT said:
Here my friend. Also in the OP.
Partial quote:
Click to expand...
Click to collapse
Ok, you are now officially a better friend to me than search is. Sorry search...
Thank you!!!
Lughnasadh said:
Ok, you are now officially a better friend to me than search is. Sorry search...
Thank you!!!
Click to expand...
Click to collapse
You can join the ranks of such like my boss at work (where we use Google officially for everything including company mail). They chat me to ask me for a link to a particular file that's in Google Drive, or to find a particular email for them.
Just kidding about joining the ranks! You're welcome!
roirraW edor ehT said:
Here my friend. Also in the OP.
Partial quote:
Click to expand...
Click to collapse
I guess it would just as easy to remove the bootloader line from the flash-all.bat script and just use flash-all???
It's good to know for sure that we can downgrade though and that it's only the bootloader version that is important and not other parts of the OS.
Lughnasadh said:
I guess it would just as easy to remove the bootloader line from the flash-all.bat script and just use flash-all???
It's good to know for sure that we can downgrade though and that it's only the bootloader version that is important and not other parts of the OS.
Click to expand...
Click to collapse
Absolutely, I agree on both parts.
Hi, I have a question here, as long as I don't update the latest bootloader (>= 1.2 ?), it shouldn't trigger the anti rollback mechanism? My pixel 6 with Android 13 now has a bootloader version of oriole-slider-1.1-8167057, but the bootloader version in this official page has been updated to slider-1.2-8739948.
I pulled the AOSP 13 (branch android-13.0.0_r2), built it locally (userdebug mode), and flashed it without the bootloader because there is no bootloader.img in the build output. And the phone successfully booted.
I've never flashed the Android 13 factory image, so i got away with the risk of ARB?
enderdzz said:
Hi, I have a question here, as long as I don't update the latest bootloader (>= 1.2 ?), it shouldn't trigger the anti rollback mechanism? My pixel 6 with Android 13 now has a bootloader version of oriole-slider-1.1-8167057, but the bootloader version in this official page has been updated to slider-1.2-8739948.
I pulled the AOSP 13 (branch android-13.0.0_r2), built it locally (userdebug mode), and flashed it without the bootloader because there is no bootloader.img in the build output. And the phone successfully booted.
I've never flashed the Android 13 factory image, so i got away with the risk of ARB?
Click to expand...
Click to collapse
I'm surprised with that old of a bootloader you were able to boot Android 13, you're running a bootloader from April. Also I'm surprised you weren't bricked after booting Android 13 because it does increment the anti-rollback counter.
https://cs.android.com/android/platform/superproject/+/android-13.0.0_r2:device/google/gs101/interfaces/boot/1.2/BootControl.cpp;l=226
drivers/soc/google/boot_control/boot_control_sysfs.c - kernel/gs - Git at Google
I'm guessing your bootloader version is old enough to not have the bits implemented so it just doesn't care, but that's weird because the July Android 12 bootloaders do have the bits and will not load if the counter is incremented by Android 13.
I wouldn't recommend continuing to run like this and would update to the August Android 13 bootloader because there's no telling what might be happening wrong under the hood. Example is that the August Android 13 bootloader it is able to boot Android 12 but because of interface differences it is a broken experience.
June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]
Pixel 6 Pro [Raven] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
So yeah if you're correct then it's possible you did get away with it as your firmware is too old to have implemented it. However this is not a supported firmware-software configuration.
Thank you for your reply!
Namelesswonder said:
I'm surprised with that old of a bootloader you were able to boot Android 13, you're running a bootloader from April.
Click to expand...
Click to collapse
Yeah. This bootloader came from the factory image `oriole-sp2a.220405.004`.
Namelesswonder said:
https://cs.android.com/android/platform/superproject/+/android-13.0.0_r2:device/google/gs101/interfaces/boot/1.2/BootControl.cpp;l=226
Click to expand...
Click to collapse
I also noticed this piece of code, but I'm not sure if it was compiled into bootloader.img or boot.img? If it's in bootloader.img, that's a good explanation, because I didn't flash this version (after June) of bootloader so the A13 now isn't restricted by anti-rollback.
BTW I am also curious why the device is not flashed bootloader.img when running `fastboot flashall -w`, even though there is a compiled bootloader.img file in the output directory.
enderdzz said:
Thank you for your reply!
Yeah. This bootloader came from the factory image `oriole-sp2a.220405.004`.
I also noticed this piece of code, but I'm not sure if it was compiled into bootloader.img or boot.img? If it's in bootloader.img, that's a good explanation, because I didn't flash this version (after June) of bootloader so the A13 now isn't restricted by anti-rollback.
BTW I am also curious why the device is not flashed bootloader.img when running `fastboot flashall -w`, even though there is a compiled bootloader.img file in the output directory.
Click to expand...
Click to collapse
That code is not in the bootloader, the bootloader is closed source. The code is part of the bootcontrolhal ([email protected]) on Android and runs on a successful boot of Android. The other code is the sysfs device being called by the HAL, that code is in the kernel.
I don't know if your device actually had the anti-rollback counter incremented, because a system monitor call is made and the source code for TZ/TEE/Titan are also closed source. Your device might've never incremented the counter because the firmware used by them just don't have the ability to, but it's just speculation.
And flashall doesn't flash bootloaders or radios, it only flashes Android system partitions defined by the product information. You can follow the steps here to flash them.
June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]
Pixel 6 Pro [Raven] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Namelesswonder said:
That code is not in the bootloader, the bootloader is closed source. The code is part of the bootcontrolhal ([email protected]) on Android and runs on a successful boot of Android. The other code is the sysfs device being called by the HAL, that code is in the kernel.
I don't know if your device actually had the anti-rollback counter incremented, because a system monitor call is made and the source code for TZ/TEE/Titan are also closed source. Your device might've never incremented the counter because the firmware used by them just don't have the ability to, but it's just speculation.
And flashall doesn't flash bootloaders or radios, it only flashes Android system partitions defined by the product information. You can follow the steps here to flash them.
June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]
Pixel 6 Pro [Raven] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much! I'm much more clear now.
enderdzz said:
Thank you very much! I'm much more clear now.
Click to expand...
Click to collapse
That's good.
Have a question, while you were on Android 13 with the Android 12 bootloader, was everything working right? Nothing crashing or throwing errors? With the Android 13 bootloader on Android 12 having issues with DRM and web browsers crashing it would be interesting to know if the same was also true for you when you were on the opposite scenario.
Namelesswonder said:
That's good.
Have a question, while you were on Android 13 with the Android 12 bootloader, was everything working right? Nothing crashing or throwing errors? With the Android 13 bootloader on Android 12 having issues with DRM and web browsers crashing it would be interesting to know if the same was also true for you when you were on the opposite scenario.
Click to expand...
Click to collapse
Yes, I'm also interested in this topic.
I've only tested webview browser tester 101.0.4951.61 and NNAPI. No problems found so far. I will update here if I encounter any new problems
I'll experience it deeply, won't flash another system or bootloader for a while. Since I flashed the userdebug version, which I think is not as feature-rich as the factory image, but it let me have root access.
I also checked `dmesg` info and didn't find anything abnormal except that it keeps reporting `init: Control message: Could not find 'aidl/android.hardware.biometrics.fingerprint.IFingerprint/default' for ctl .interface_start from pid: 467 (/system/bin/servicemanager)`, I think it's not a big deal. And no useful log about the anti-rollback counter, which maybe needs some reverse engineering.
enderdzz said:
Yes, I'm also interested in this topic.
I've only tested webview browser tester 101.0.4951.61 and NNAPI. No problems found so far. I will update here if I encounter any new problems
I'll experience it deeply, won't flash another system or bootloader for a while. Since I flashed the userdebug version, which I think is not as feature-rich as the factory image, but it let me have root access.
I also checked `dmesg` info and didn't find anything abnormal except that it keeps reporting `init: Control message: Could not find 'aidl/android.hardware.biometrics.fingerprint.IFingerprint/default' for ctl .interface_start from pid: 467 (/system/bin/servicemanager)`, I think it's not a big deal. And no useful log about the anti-rollback counter, which maybe needs some reverse engineering.
Click to expand...
Click to collapse
If WebView applications didn't crash within minutes of launching them then that means the DRM library should either be working or just not segfaulting like it does with Android 12 on 13 bootloader.
The fingerprint scanner HAL not working is completely understandable, part of the bootloader flash also carries the fingerprint scanner's firmware, and we know that one of the big things with Android 13 is that the fingerprint scanner is somewhat more reliable, so it definitely has changed between Android 12 to 13.
Interesting stuff, will be cool to see where it can go, but man is it sketchy to recommend people still on Android 12 to downgrade to April and then try flashing the Android 13 system images, real possibility of making bricks.