Related
Came with MM from the factory and I want to roll back for root. The build number is MRA58k and software H81020n. Anyone know if it will work and if so would anyone happen to have the proper kdz or tot I need? Thank guys.
Found this on another thread
I was looking for the same info, i haven't tried it but they claim to have done it successfully.
lwg45714 said:
Came with MM from the factory and I want to roll back for root. The build number is MRA58k and software H81020n. Anyone know if it will work and if so would anyone happen to have the proper kdz or tot I need? Thank guys.
Click to expand...
Click to collapse
i did mine you just need LGUP.. i have TMOBILE and i can only downgrade to LP 10N.. lower then that will brick my phone... or go back to MM 20i.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
raptorddd said:
i did mine you just need LGUP.. i have TMOBILE and i can only downgrade to LP 10N.. lower then that will brick my phone... or go back to MM 20i.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Click to expand...
Click to collapse
Hello friend, i found out that my antirollback is 0, so i tried via LGUP to downgrade from MM to LP, but still get error 0x2000, can you help me?
LoneWanderer_97 said:
Hello friend, i found out that my antirollback is 0, so i tried via LGUP to downgrade from MM to LP, but still get error 0x2000, can you help me?
Click to expand...
Click to collapse
not familiar with that error. but seems like maybe you cant you need to find out searching if others have by using same variant.. i did find 2 links
https://forum.xda-developers.com/showpost.php?p=68917209&postcount=2261
https://forum.xda-developers.com/showpost.php?p=65346756&postcount=36
post your question in first link..
Samsung Galaxy S8+
Version Info
Model SM-G955U [SS]
PDA FA70_G955UQU4ARE1
PHONE G955USQU4CRE1
P_S/N UNKNOWN
H/W REV1.0
CAL.ID 2017.04.18
UN (NOT SURE IF TO GIVE THIS NUMBER)
MEMORY 64GB
Ran ODIN v3.12.7 and rom that came with it. now stuck in Factory Binary, trying to flash back to factory, any help? Ive tried several roms and either get fails. or sometimes gets abl.elf
in upload mode
[ UPLOAD MODE ]
User press powerkey 7 sec (it does nothing)
--------------------
DDR Vendor :Samsung
SOC_HW_REVISION : 2.1
last_ns :0xff
Generaring Summary
>>General Info
>>DDR Info
>>DCVS Info
>>RPM
>>Trust2one
>>Hypervisor
>>APSS
>>MOdem
Done!
in Downloading custom rom
CARRIER: vzw
RPMB fuse blown
RPMB PROVISIONED
CURRENT BINARY: Samsung Official
SYSTEM STATUS : oFFICIAL
FRP LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B4(2,1,1,1,1) K3 S4
SECURE DOWNLOAD: ENABLE
DID : 205E53BE31CB
AFTER RUNNING ODIN AND FAILING THERES ANEW RED LINE
SW REV CHECK FAIL : [ABL]FUSED 4 > BINARY 1
I am not an expert, but it sounds like you are trying to flash a bootloader that is an older version than the version 4 on your phone. I don't think you can downgrade the BL version. The fifth character from the end is the BL version. (e.g. G955USQU4CRE1) Also, you may need a newer version of ODIN.
Smithfolk4 said:
I am not an expert, but it sounds like you are trying to flash a bootloader that is an older version than the version 4 on your phone. I don't think you can downgrade the BL version. The fifth character from the end is the BL version. (e.g. G955USQU4CRE1) Also, you may need a newer version of ODIN.
Click to expand...
Click to collapse
so could i just google a "verison 4 BL for s8+" or something along those lines?
Kyles89 said:
so could i just google a "verison 4 BL for s8+" or something along those lines?
Click to expand...
Click to collapse
Yes. There are a lot of software versions available. If you use Updato you can search by model number and service provider (listed as region on Updato. I was able to find one with a version 4 bootloader. Similar to your version, but CRE9 at the end. It is an oreo version. Your phone is a model SM-G-955U when you search there. It might take a long time to download. I have sometimes had luck speeding things up by trying to restart the download. Sometimes it just takes a long time. Be careful when you are flashing if you have any desire to go back to a previous version. I am not sure of the limitations.
Another thing you could try that might be easier for you is to go to the JRKruse ROM thread here - https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206 and use the instructions he has there to install the ROM. There is another rooted ROM that he has that may also work for you. He has instructions on what to do.
Hello, my galaxy s8 is stuck in rpmb provisioned and its boot looping, I can get to download mode, it doesn't say things such as fuse blown etc. How can I get out of the boot loop? Help is appreciated.
Did you find a fix? Im having a very similar problem. I don't see any stock roms with a v4 bootloader. The most recent seems to be a v3.
Fixed it the way Smithfolk said. I was using the combination rom FA70_G955USQU4ARE1 with a V4 bootloader. I used odin v3.13.1 and flashed verizion G955USQU4CRE9 from Sammobile including the bootloader and it fixed my phone.
WARNING
Is you flash this firmware you will not be able to downgrade to any older firmware because this new firmware has new bootloader REV6 "device 6 binary 4" and there is no combination firmware available to downgrade at this moment.i will update once the REV6 combination available for "device 6 binary 4" bootloader.
DISCLAIMER>>>FLASH ON YOUR OWN RISK
WARNING BEFORE START FLASHING.
BACKUP EVERYTHING BECAUSE FLASHING THIS FIRMWARE WILL ERASE ALL YOUR APPS AND DATA FROM YOUR PHONE.
REMOVE ANY SCREEN LOCK SUCH AS FINGERPRINTS/PIN/PASSWORD/PATTERN.
ALSO REMOVE GOOGLE ACCOUNT AND SAMSUNG ACCOUNT TO AVOID FRP LOCK/REACTIVATION LOCK.
ALSO DO A FACTORY RESET TO CLEAN YOUR PHONE BEFORE YOU FLASH NEW FIRMWARE.
IF YOU FORGET TO REMOVE ANY OF THESE AS I MENTIONED YOU CAN LOSE IMEI/BASEBAND AND ALSO YOUR DEVICE CAN BOOTLOOP AND I AM NOT RESPONSIBLE. FOR ANY DAMAGES.
Firmware Download link below
N920AUCS6ERH1 Full official firmware.
Knox counter will remain 0x0
Android 7.0 Nougat
1 August 2018 security patch
BL+AP+CP+CSC 4 files Firmware
https://mega.nz/#!XKZxFSiR!ghbG0EuQAnWJBcdYlYL527noagAejz30kvwbbHLQrJE
Zip Password>>> windows4droid
N920A PIT FILE FOR REPARTITION
https://mega.nz/#!LYdB3IAL!gabDPTTNXrru3xAWilCjI3PVY1uaOIKR3WpkNvVI36U
WARNING
Use this PIT FILE only if you have issues with internal storage such as if your device is 32gb and after flashing nougat it shows 16gb.
Must flash via Odin 3.13 latest otherwise older odin will get error and will not full flash.
Odin 3.13 download from link below
https://forum.xda-developers.com/attachment.php?attachmentid=4431749
WHAT'S NEW IN THIS UPDATE ?
1, Major network improvements in LTE because this firmware comes with new Baseband/Modem that enhances all the LTE BANDS.
2,comes with new NOTE 8 weather widget
3, SECURE FOLDER ALSO WORKS WITH THIS UPDATE.IF YOU WANT SECURE FOLDER TO WORK JUST GO TO PLAYSTORE AND SEARCH FOR SECURE FOLDER AND ENABLE IT THEN UPDATE IT.
4,Google Pay also comes by default just UPDATE it from playstore.
AOD ALWAYS ON DISPLAY
WITH THIS NEW UPDATE THE KERNEL IS FULLY COMPATIBLE FOR ALWAYS ON DISPLAY SO I MADE A TUTORIAL HOW TO GET ALWAYS ON DISPLAY JUST LIKE NOTE 8.
WARNING VERY IMPORTANT
PLEASE DISABLE LOOKOUT ANTIVIRUS OTHERWISE ALWAYS ON DISPLAY WILL NOT WORK PROPERLY AND WILL GET BUNCH OF ERRORS.
AFTER DISABLING LOOKOUT ANTIVIRUS GO TO LINK BELOW AND DOWNLOAD AOD APK FILES THEN WATCH THE VIDEO HOW TO INSTALL AND RUN IT PERFECTLY.
ALWAYS ON DISPLAY APK FILES DOWNLOAD LINK
https://mega.nz/#F!uI9whAZA!KIHK8ELZH26A8xwgmhFsBA
ALWAYS ON DISPLAY VIDEO TUTORIAL.
https://youtu.be/3WMwA-rpNM0
PLEASE NOTE
BASED ON MY USAGE THE ALWAYS ON DISPLAY CONSUMED 3% BATTERY PER HOUR WHILE LAYING ON TABLE WHOLE NIGHT .BUT IF YOU TURN ON THE POCKET MODE FROM AOD ADDITIONAL SETTINGS IT WILL CONSUME LESS BATTERY IF YOUR DEVICE IN POCKET OR BAG.
let me know in comments if you found some more new stuff.
According to AT&T probably this will gonna be the last & final security patch update for our beloved note 5 N920A
Credits>>>>> Samsung & AT&T
Credits>>>>> FOR ALWAYS ON DISPLAY @Sachin Kumar53 https://forum.xda-developers.com/android/apps-games/root-display-samsung-device-running-t3691231
Dont Forget to hit me Thumbs up :good::good:
Enjoy
says password is incorrect
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
correction windows4droid is pass no caps
ownmart said:
says password is incorrect
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
correction windows4droid is pass no caps
Click to expand...
Click to collapse
Sorry about that i will edit in the OP
Thanks
haii broo iam very hepy,my phone is nougat now,
btw, can you give me tutorial root in this firmware
aribz said:
haii broo iam very hepy,my phone is nougat now,
btw, can you give me tutorial root in this firmware
Click to expand...
Click to collapse
Root is impossible on AT&T Nougat because locked Bootloader.
If you want root your phones then don't buy AT&T or Verizon models
My note 5 is aAT&T running android 6 and accepts any network from the time i got it. If i flash this Rom update, what are the chances that my phone will stop accepting other networks. Note:There is no AT&T network in my country(Zambia).
Phyzo said:
My note 5 is aAT&T running android 6 and accepts any network from the time i got it. If i flash this Rom update, what are the chances that my phone will stop accepting other networks. Note:There is no AT&T network in my country(Zambia).
Click to expand...
Click to collapse
You can still use it with your carrier as on Marshmallow.
Once downloaded on pc, how to unzip file to obtain the 4 files to use with odin engine? Thanks
Ian.
Hi there,
I'm gonna buy an unlocked SM-N920 AT&T, upgraded to MM 6.0.2.
May I flash this firmware?
vysus said:
Hi there,
I'm gonna buy an unlocked SM-N920 AT&T, upgraded to MM 6.0.2.
May I flash this firmware?
Click to expand...
Click to collapse
Yes
Janskitech said:
Once downloaded on pc, how to unzip file to obtain the 4 files to use with odin engine? Thanks
Ian.
Click to expand...
Click to collapse
Use winrar or 7zip software on windows pc to extract the 4 files.
When i update my sm-n920a from marsmallow 6.0.1 to nougat 7.0 my imei not shown and i can't use my network. Would this firmware give my imei and network back? Note: Note:There is no AT&T network in my country (indonesia), thanks alot before....
Trex888 said:
Yes
Click to expand...
Click to collapse
Are you sure the phone will be not re-locked to AT&T?
vysus said:
Are you sure the phone will be not re-locked to AT&T?
Click to expand...
Click to collapse
If your phone is unlocked permanently then it will not re-locked again to AT&T.
I tried on my own phone and it's still unlocked.
Tria86 said:
When i update my sm-n920a from marsmallow 6.0.1 to nougat 7.0 my imei not shown and i can't use my network. Would this firmware give my imei and network back? Note: Note:There is no AT&T network in my country (indonesia), thanks alot before....
Click to expand...
Click to collapse
Are you sure your phone was unlocked permanently from AT&T before you flashed nougat ?
Remove simcard and Flash the nougat firmware again then go to recovery and do wipe cache and wipe data factory reset.
Then do not setup the phone immediately let it rest for few minutes.
Insert your sim card and reboot You will get your imei and network back. hopefully...
Note 5 AT&T upgrade
I have samsung note 5 sm-n920a , ant fortunately it works on one network in egypt and i do not know why ?, if i upgraded to the last firmware will it still working for me or will it stop ???
Baseband version N920AUCS4CQB2
Hey, I have a device SAMSUNG-SM-N920A, Android Version 6.0.1, Baseband version N920AUCS4CQB2
Can I use this firmware on this Baseband?
Fayez ayman said:
I have samsung note 5 sm-n920a , ant fortunately it works on one network in egypt and i do not know why , if i upgraded to the last firmware will it still working for me or will it stop ???
Click to expand...
Click to collapse
It will work fine but you have to do factory reset from stock recovery after flashing 7.0 firmware.
nikhilphr said:
Hey, I have a device SAMSUNG-SM-N920A, Android Version 6.0.1, Baseband version N920AUCS4CQB2
Can I use this firmware on this Baseband?
Click to expand...
Click to collapse
Yes
i am new to flashing so i have a question
soo my phone says(in the settings) it is n920F version but when i go to download mode it says n920A. it is a refurbished phone.did they installed wrong version but still worked? and is it okay to flash this rom?
update: i just found out that bootloader, baseband version is n920A but pda,csc is n920f. knox warranty void is 0
system status: custom
product name: sm-n920A
current binary: samsung official
Hi guys i recently bought a refurb phone and i want to unlock it and put some custom rom but i cant identify the real model of this device. i also tried opening the back and see if it has some model print on the motherboard but its not there i think. so ill put the pics of relevant info on my phone to help to identify it so thanks a lot for those who can help i would appreciate it
You must take out the motherboard. It is written on the backside
thanks its there turns out i have an 810 variant. Any tips for me to install marshmallow on my phone and usu it? because on my version of the device i cant update thru system updates its still on LP. should i flash stock 810 rom and update to marshmallow that way?
kukel21 said:
thanks its there turns out i have an 810 variant. Any tips for me to install marshmallow on my phone and usu it? because on my version of the device i cant update thru system updates its still on LP. should i flash stock 810 rom and update to marshmallow that way?
Click to expand...
Click to collapse
First thing is check your kdz version that you have installed - use steadfasterX's SALT program to do this. It will also establish your ARB version (must be less than or equal to 2 - if not, i.e., if greater than 2, UsU is a no-go in your case). It will also let you know your GPT compatibility to show you what custom roms versions you can install.
Once that is ascertained, if you are rooted, re-install your stock LP kdz first (important), then proceed to upgrade to Marshmallow (MM) using LG Bridge first (download from LG site, it will sometimes work when OTA doesn't). If that doesn't work, you'll have to download an MM kdz for your model and carrier and upgrade it with LGUP-NEW. Then, once you have stock MM installed, do at least a partial backup with SALT before proceeding to unlock with steadfasterX's UsU method. Make sure you read and understand the OP completely there.
sdembiske said:
First thing is check your kdz version that you have installed - use steadfasterX's SALT program to do this. It will also establish your ARB version (must be less than or equal to 2) - if not, i.e., if greater than 2, UsU is a no-go in your case). It will also let you know your GPT compatibility to show you what custom roms versions you can install.
Once that is ascertained, if you are rooted, re-install your stock LP kdz first (important), then proceed to upgrade to Marshmallow (MM) using LG Bridge first (download from LG site, it will sometimes work when OTA doesn't). If that doesn't work, you'll have to download an MM kdz for your model and carrier and upgrade it with LGUP-NEW. Then, once you have stock MM installed, do at least a partial backup with SALT before proceeding to unlock with steadfasterX's UsU method. Make sure you read and understand the OP completely there.
Click to expand...
Click to collapse
Is the ARB value stored as a variable? I'm guessing its just a variable that gets checked during a KDZ flash. If so, where is the ARB value stored, and why can't we just overwrite it with 0? Has anyone tried this already?
If it's not possible, can't we alter the ARB values of specific KDZ's? For example if your phone has ARB value 3 and you want you want to flash a KDZ with ARB value 1, can you change the ARB value of the KDZ from 1 to 3, so it won't brick?
dharakv said:
Is the ARB value stored as a variable? I'm guessing its just a variable that gets checked during a KDZ flash. If so, where is the ARB value stored, and why can't we just overwrite it with 0? Has anyone tried this already?
If it's not possible, can't we alter the ARB values of specific KDZ's? For example if your phone has ARB value 3 and you want you want to flash a KDZ with ARB value 1, can you change the ARB value of the KDZ from 1 to 3, so it won't brick?
Click to expand...
Click to collapse
Suggest you read the OP in the UsU thread and pay particular attention to REQUIREMENTS #2.
If you really want to hard-brick your device then go ahead -- i.e., you cannot alter the arb value !!!
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.