Hi everyone, these may be of help to you. I'm not a dev so all I was doing here was using a rooted Sirocco to pull OTA files off the phone (data/ota_package). Using logcat/android bug report doesn't catch OTA URL on this device. It's my understanding they will need to be unpacked.
Files are in order of download/installation from A1N-310B-0-00WW-B03-OST604 onwards. That full firmware can be obtained here thanks to Hikari (Under Sirocco) https://hikaricalyx.com/fih-android-firmware/
The boot image for the firmware above can be found in the zip. It's already unpacked (A1N-0-310B-00WW-boot.img).
OTA 1 (Changelog - https://i.imgur.com/EeQeHyR.png)
https://mega.nz/#!SA1U3SzR!WAUtzV5AH2g6jYUYqhrUfMNh_tOe7ziNhNwZ8eZBxew
Boot image - https://mega.nz/#!2J8wBaBR!PbYVY4Ysr4l9idxReLrJe6wWu83KRy5tO29j0H2b3Ew
OTA 2 (Changelog - https://i.imgur.com/AOvs4Ps.png)
https://mega.nz/#!mB0EgCRa!oEKAxCl5iGnR3rHC91te0mgU3JgW3AXAO991kR4nj9g
Boot image - https://mega.nz/#!iU1WlKxT!mz1VrSGS987BbiPj1nvyUQzb4GEBw3686onS6ymctJI
OTA 3 (Changelog - https://i.imgur.com/nEpvMq2.png)
https://mega.nz/#!rNNAhASA!5_CdYQIym6iqc5ycN6wMqG0XvzrsCf70I3VQsy8bjFg
Boot image - https://mega.nz/#!SJt0WSxK!UkG4DbsDmUwIzExcmG1qo2xqhRk4lJlylhWHfMFJxfM
OTA 4 (Changelog - https://i.imgur.com/QH6Dnox.png)
https://mega.nz/#!HF8WlKDS!OpfBdAEUJSe_vzTebdCGg_DN_8Kzj5UZVG29x8aG6Q8
Boot image - https://mega.nz/#!7Usw1aKS!jEoZDlj5mtu5tqVpVG7XFaHLdDleiq3M6GBfy7_IUzc
OTA 5 (Changelog - https://i.imgur.com/bDSCAqX.png)
https://mega.nz/#!XUlWFKiC!_trT2aVmGQVhD-lzeZjWEn2LlmRZ4d6CMrKuAB41kkw
Boot image - https://mega.nz/#!KVl2WKqT!AcDI4YSOSo6vBe4Jb3FrOBsKGzO-KM5a8gowgNQXHog
OTA 6 (Changelog - https://i.imgur.com/ColEcRJ.png)
https://mega.nz/#!DE8QxSDQ!G1xRrjN9do28trYeQT-E9jAYmP7dszuXMKZ8kpmhcMI
Boot image - https://mega.nz/#!XB9EnY4A!UxLAX0hBabbKy09pGQz_BLQW9Hy5Lz0K4y15uVJcY7o
OTA 7 (Changelog - https://i.imgur.com/Tll0QuI.png)
https://mega.nz/#!zUsAzKLZ!TngURPA1pDUFjrmsrWvVglLmkE3GGGE4qX53-Vp38iU
Boot image - https://mega.nz/#!jck0iAjI!nEd890ZxQS1OaXX4ELNtdsIsa3TJZxddC1D7faPOB9U
OTA 8 (Changelog - https://i.imgur.com/HsZLwV4.png)
https://mega.nz/#!3dtEXQwY!CY6J3auoDeMelGSDmQiAJgOBHw3eH-sxrA3x51gXQ-U
Boot image - https://mega.nz/#!SQsUUYSD!iBwTMYd4OEDJJ7Me-zb2SnfPghc2me_ZEYR6SrdOkgU
OTA 9 (Changelog - https://i.imgur.com/eLVqDrM.png)
https://mega.nz/#!CEc1GQ7L!EiZYCubGDf5C97NNQDLZxmjcEaw555FbxHKvMNveZDw
Boot image - https://mega.nz/#!mNFzVCbD!RNTJI1_oPiHSapyykE0szjosBo_QnIoJiGZ0EQtmzqY
OTA 10 - Pie (Changelog - https://us.v-cdn.net/6031042/uploads/editor/je/y2ok3dg0norb.png)
https://mega.nz/#!fYUAgQJY!p6kO-B-IFwz0NhDv4ZlrDCQYKQGakH3fy9GbfG_kmDM
Boot image - https://mega.nz/#!qANy1a7b!ODh8ol97h8qJwZGndUCHqyG3qifnsfT7ILkggDaVoFA
Magisk patched boot - https://mega.nz/#!HYVimArR!m7BHM2iYVZVstTFx0W-zB01cSN-bb4lquKiYUmXoIm4
edit: TWRP removed, buggy
OTA 3 zip was corrupt, it has been replaced.
Also for helping out anyone who gets their Sirocco unlocked, this is a pre-rooted boot image for A1N-310B-0-00WW-B03-OST604
You can use this to do fastboot boot patched_boot.img and then use Magisk to root your device.
https://mega.nz/#!6dMgjCjL!KRkB39ppPp4RA0Wj57yjIjiXaE6B21f-B488yQFc61s
You can, of course, do the above yourself if you have a second phone that is rooted and go into Magisk and patch one of the stock file boot images above.
Now you can do OTAs and keep root
STEPS_TO_UPDATE:
1. Go into Magisk Manager -> Uninstall -> Restore Images
2. Apply Update, DO NOT REBOOT YET
3. When step to finished and it promts you to reboot go into Magisk Manager -> Install -> Install to inactive Slot
Congratulations you can now reboot and will have an updated Android while keeping full root.
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390
If anyone is already on the November security update with this device and wants to root without downgrading, here is a magisk patched boot image
https://mega.nz/#!HBcHzYCB!KpqytpNth0Vfu3K9eX0vbP7heJ3MFPm6MX4ozC5L_qk
December security update added as OTA 9.
No Pie yet
Audioboxer said:
December security update added as OTA 9.
No Pie yet
Click to expand...
Click to collapse
Its a shame.
December patched boot for anyone who's had this phone unlocked and has done OTAs up to December without rooting
https://mega.nz/#!6R8RCIoB!ZPR7s-w4LWDXO1UcI7GBuhf7U0U3fujHLQIc6qlqx2g
As always, fastboot boot this image to root your phone with Magisk direct install. Do not flash my boot images, otherwise, you won't be able to do the OTA trick above with Magisk.
Removed: Oreo homebrew packages by Hikari are buggy, avoid.
So i found this...
https://mega.nz/#F!W50gzawY!nC8Yb9yE6n08gGafFi700A
The A1N-4120 is a Pie build. A guy i met on twitter installed it and said it is a decent build without bugs. I'm a bit hesitant to install it. I'm afraid that if i install it and the offical update comes out i can't update via OTA. Is there a way to revert back to 8.1?
The guy's phone isn't rooted or unlocked.
Still, he says it's the official build from HMD. They are holding it back... If that's true it's kinda sad...
marccoppers said:
So i found this...
https://mega.nz/#F!W50gzawY!nC8Yb9yE6n08gGafFi700A
The A1N-4120 is a Pie build. A guy i met on twitter installed it and said it is a decent build without bugs. I'm a bit hesitant to install it. I'm afraid that if i install it and the offical update comes out i can't update via OTA. Is there a way to revert back to 8.1?
The guy's phone isn't rooted or unlocked.
Still, he says it's the official build from HMD. They are holding it back... If that's true it's kinda sad...
Click to expand...
Click to collapse
It's the internal OTA and he wasn't sensible installing it without BL unlock
https://forum.xda-developers.com/no...ide-how-to-install-android-pie-build-t3885834
These internal builds don't pass safetynet so Google Pay will not work. It is also unknown how to get back onto retail OTAs without an unlocked bootloader. When HMD did the Nokia 8 beta test they had an official rollback method.
I'd strongly advise staying away from this if you haven't unlocked the BL. The build wasn't all that good either, missing adaptive battery, pro camera, Pie themeing and more. From above two new OTAs exist since the December pie build. I'll try them and see if anything has been added.
Audioboxer said:
It's the internal OTA and he wasn't sensible installing it without BL unlock
https://forum.xda-developers.com/no...ide-how-to-install-android-pie-build-t3885834
These internal builds don't pass safetynet so Google Pay will not work. It is also unknown how to get back onto retail OTAs without an unlocked bootloader. When HMD did the Nokia 8 beta test they had an official rollback method.
I'd strongly advise staying away from this if you haven't unlocked the BL. The build wasn't all that good either, missing adaptive battery, pro camera, Pie themeing and more. From above two new OTAs exist since the December pie build. I'll try them and see if anything has been added.
Click to expand...
Click to collapse
Thanx for the reply! Gonna stay away from it then... Usually i try everything, but since the BL is still officially locked there aren't that many people out there that can help when things go wrong. Especially with this being my daily phone, i don't want to mess it up.
marccoppers said:
Thanx for the reply! Gonna stay away from it then... Usually i try everything, but since the BL is still officially locked there aren't that many people out there that can help when things go wrong. Especially with this being my daily phone, i don't want to mess it up.
Click to expand...
Click to collapse
Yeah, it's not worth it, Pie should drop this month.
With the Nokia 8, HMD advised if you stayed on the beta you'd get 1 OTA and that would be it. You basically had to rollback.
In order for us to flash firmware packages, we need an unlocked bootloader if HMD isn't providing an official rollback method. As it seems we won't get an official beta test for the Sirocco it's a bad idea anyone with a locked bootloader flashing these internal releases.
Audioboxer said:
Yeah, it's not worth it, Pie should drop this month.
With the Nokia 8, HMD advised if you stayed on the beta you'd get 1 OTA and that would be it. You basically had to rollback.
In order for us to flash firmware packages, we need an unlocked bootloader if HMD isn't providing an official rollback method. As it seems we won't get an official beta test for the Sirocco it's a bad idea anyone with a locked bootloader flashing these internal releases.
Click to expand...
Click to collapse
That was my guess to. Thanx for the info.
You are wrong. And I am the guy he met on twitter. And btw he is referring to Nokia 8 Sirocco and sorry but could you explain how you termed as insensible. I downloaded the internal OTA and then rebooted the phone in safe mode and the update automatically installed. For your information
1. Adaptive battery is there
2. Wellbeing is there
3. Pro camera is there.
So stop being judgemental. Nokia 8 and Nokia 8 Sirocco and two different handsets. Nokia 8 is what you mentioned above . So next time mind Ur tongue while u talk
rajeev.rao87blr said:
You are wrong. And I am the guy he met on twitter. And btw he is referring to Nokia 8 Sirocco and sorry but could you explain how you termed as insensible. I downloaded the internal OTA and then rebooted the phone in safe mode and the update automatically installed. For your information
1. Adaptive battery is there
2. Wellbeing is there
3. Pro camera is there.
So stop being judgemental. Nokia 8 and Nokia 8 Sirocco and two different handsets. Nokia 8 is what you mentioned above . So next time mind Ur tongue while u talk
Click to expand...
Click to collapse
My advice was just following what Nokia devs like Calyx Hikari state. If you do not have an unlocked bootloader its best not to install internal OTAs because there is no way to revert to retail FW. The Nokia 8 had an official beta test so there was a way to rollback off of the beta Pie firmware to Oreo again, to then install the final Pie OTA.
Otherwise you need an unlocked bootloader to flash an Oreo/Pie retail package with LA OST.
I don't mean to offend anyone, I just don't want anyone installing these leaked OTAs on their bootloader locked device and being stuck.
Currently, there's no way to roll back to Android 8.1 for Nokia 8 Sirocco by yourself, so use these packages at your own risk.
It will be better if you're using prototype device or a retail device with unlocked bootloader.
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...stall-android-pie-build-t3885834/post78591840
Nokia 8 Sirocco doesn't need any bootloader to be unlocked.
Nokia 8 Sirocco doesn't need bootloader to be unlocked. Like I got it and others who installed got it without doing the same. You just have to downloaded the A1N 4200 file and reboot the phone to safe mode and the phone automatically detects the update. So I assume that's pretty much official and valid .
Don't know why people end up spreading rumours without knowing the real picture. Just because one device works in a specfic way doesn't mean every device functions the same way.
Plus Nokia 8 Sirrocco gets all the features a full fledged android one device gets including the below
1. Adaptive Battery
2. Gestures
3. Digital Wellbeing
I myself wanted to write a review and a video but never written one for mobile devices, I have done for vehicles.
And most importantly Nokia 8 and Nokia 8 Sirocco are different mobiles . The only common point is The processor.
Pie OTA Rom
Now that the official PIE OTA has been released can anyone capture it and post a link to the file? It can take weeks to reach people over the air sometimes!
Thanks
Let's say they will be captured, can i install them with a locked bootloader?
marccoppers said:
Let's say they will be captured, can i install them with a locked bootloader?
Click to expand...
Click to collapse
I did on the Nokia 8 and the Nokia 7 plus by downloading to the device, renaming the file and using the phone keypad ( *#*#874#*#*) so I assume it will be the same on the Sirocco?
marccoppers said:
Let's say they will be captured, can i install them with a locked bootloader?
Click to expand...
Click to collapse
Sideloading the OTA via ADB can be done on a locked bootloader. The method by EGGMEN should work as well. :good:
I currently have an Unlocked Z Fold3 purchased directly through the Samsung US site.
Model: SM-F926U1
Baseband version: F926U1UEU1CVC5
I would like to downgrade to Android 11 to see if it resolves the no service issues with T Mobile the update caused. Does anyone know if this is possible?
Yes. Download android 11 package and use Odin
domineus said:
Yes. Download android 11 package and use Odin
Click to expand...
Click to collapse
I thought I needed an unlocked bootloader for this? If its that easy is there a way to prevent getting the update to 12?
No, Odin flashes the Android firmware.
Unlocking the bootloader gives the ability to install TWRP, custom ROMs, and delve into the system folder easily. Odin flashes firmware. However, once you update a bootloader, you cannot roll that back...if I remember correctly.
was the bootloader updated in the Android 12 update? if it was that means flashing Android 12 really wouldn't change anything or may not even be possible?
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.