I do hate the new Android interface, large Button in the notification screen, screen that is also always full screen, can't control Chromecast volume with cellphone buttons.
So there is some major bug that are really annoying to me.
Is there anyone who rollback to A11?
Can i just Flash the latest version over Android 12? Is a full wipe required?
Full wipe is required when downgrading. If your bootloader is unlocked, you should be able to use the Android Flash Tool to install a previous build.
If your bootloader is locked, you will have to unlock it in order to downgrade.
V0latyle said:
Full wipe is required when downgrading. If your bootloader is unlocked, you should be able to use the Android Flash Tool to install a previous build.
If your bootloader is locked, you are out of luck unfortunately.
Click to expand...
Click to collapse
Yeah my bootloader is unlocked, well.. Doing the rollback worth it, even if i want to have root on a12 that need to be done for now.
Thanks
Man, it's like I wrote this topic lol.
If we downgrade to Android 11, will it be possible to get all the security updates, or are they included in the latest images available on google.
Lol, 11 is no gem. I'd go back to 10. That is as high as I will go. Apple trashware is what Android has become, a bloated yappy poodle of an OS.
Who left that big Apple into the room?☠
dotmehdi said:
Man, it's like I wrote this topic lol.
If we downgrade to Android 11, will it be possible to get all the security updates, or are they included in the latest images available on google.
Click to expand...
Click to collapse
Just like previous updates, Android 11 on the Pixel series has now been deprecated and will no longer be supported with updates.
blackhawk said:
Lol, 11 is no gem. I'd go back to 10. That is as high as I will go. Apple trashware is what Android has become, a bloated yappy poodle of an OS.
Who left that big Apple into the room?☠
Click to expand...
Click to collapse
While you're entitled to your personal opinion regarding Android versions, your comment is neither helpful nor appropriate in this context. Some of us like Android 12, some like 11, you apparently prefer 10. Everyone has their own preference. I personally don't like the C8 Corvette, and if I were to buy a Corvette, I'd go with the C7 (or maybe keep it old school and go with a C3). But, I'm not going to be disrespectful to someone and imply the C8 is trash because it's a wannabe Ferrari.
V0latyle said:
Just like previous updates, Android 11 on the Pixel series has now been deprecated and will no longer be supported with updates.
While you're entitled to your personal opinion regarding Android versions, your comment is neither helpful nor appropriate in this context. Some of us like Android 12, some like 11, you apparently prefer 10. Everyone has their own preference. I personally don't like the C8 Corvette, and if I were to buy a Corvette, I'd go with the C7 (or maybe keep it old school and go with a C3). But, I'm not going to be disrespectful to someone and imply the C8 is trash because it's a wannabe Ferrari.
Click to expand...
Click to collapse
I'm sorry my question wasn't clear
I meant, if I download the latest image on https://developers.google.com/android/images , will it include the latest patches of Android 11 ? I assume I will not get an invite to update to the latest patches, but directly to Android 12 which is why I wonder if I will also have to install all the ota patches myself
V0latyle said:
Just like previous updates, Android 11 on the Pixel series has now been deprecated and will no longer be supported with updates.
While you're entitled to your personal opinion regarding Android versions, your comment is neither helpful nor appropriate in this context. Some of us like Android 12, some like 11, you apparently prefer 10. Everyone has their own preference. I personally don't like the C8 Corvette, and if I were to buy a Corvette, I'd go with the C7 (or maybe keep it old school and go with a C3). But, I'm not going to be disrespectful to someone and imply the C8 is trash because it's a wannabe Ferrari.
Click to expand...
Click to collapse
You don't need updates.
Don't buy the scare hype.
Almost all malware infections are done by the user and most are preventable.
{Mod edit} 11 is just a bad OS by design.
Android wanted to make it "safe" and "secure" for even the ignorami.
There's no saving ignorami... load at you're own peril
{Mod edit: Language slightly adjusted - regards Oswald Boelcke}
dotmehdi said:
I'm sorry my question wasn't clear
I meant, if I download the latest image on https://developers.google.com/android/images , will it include the latest patches of Android 11 ? I assume I will not get an invite to update to the latest patches, but directly to Android 12 which is why I wonder if I will also have to install all the ota patches myself
Click to expand...
Click to collapse
Take a look at the link you posted. Every update, from the initial release to the most recent, is hosted there. The updates are cumulative, so if you install the latest firmware, it incorporates all previous updates.
blackhawk said:
You don't need updates.
Don't buy the scare hype.
Almost all malware infections are done by the user and most are preventable.
11 is just a bad OS by design.
Android wanted to make it "safe" and "secure" for even the ignorami.
There's no saving ignorami... load at you're own peril
Click to expand...
Click to collapse
If you have nothing productive to contribute, feel welcome to find your way to an OT forum.
blackhawk said:
Lol, 11 is no gem. I'd go back to 10. That is as high as I will go. Apple trashware is what Android has become, a bloated yappy poodle of an OS.
Who left that big Apple into the room?☠
Click to expand...
Click to collapse
There isn't any Android 10 factory image for the Pixel 5..
andybones said:
There isn't any Android 10 factory image for the Pixel 5..
Click to expand...
Click to collapse
That's unfortunate, I thought that may be the case... my bad.
Maybe a custom rom built on Q but this may difficult because Titan M security chip found on the newer Pixels. Don't know if it can be bypassed as it's primary function is security.
In Q scoped storage doesn't appear to be implemented at least with older apps. That changes with R.
At the least I wait for 12 to see wide spread release for a few months before upgrading; let someone else work out/suffer the glitches.
How can I downgrade to 11 I'm not feeling the new update
xstokerx said:
How can I downgrade to 11 I'm not feeling the new update
Click to expand...
Click to collapse
Easiest way: Use the Android Flash Tool. Make sure you wipe data.
I feel the same way about Android 12 and successfully did a rollback (with full wipe unfortunately) using https://9to5google.com/2021/10/21/how-to-downgrade-from-android-12-to-android-11-on-google-pixel/ as a guide.
However, my concern now is how do I block 12 from updating automatically? I've disabled automatic updates under Developer Tools, but is that sufficient? I keep getting popups to update to 12 but so far I've managed to dismiss them. Last time I inadvertently dismissed an update popup like that the phone eventually told me too much time has passed and it will update now without giving me an option to prevent it. Do I need to enable OEM debugging and/or unlock the bootloader to really block OTA updates or is there an easier way?
lapingultah said:
I feel the same way about Android 12 and successfully did a rollback (with full wipe unfortunately) using https://9to5google.com/2021/10/21/how-to-downgrade-from-android-12-to-android-11-on-google-pixel/ as a guide.
However, my concern now is how do I block 12 from updating automatically? I've disabled automatic updates under Developer Tools, but is that sufficient? I keep getting popups to update to 12 but so far I've managed to dismiss them. Last time I inadvertently dismissed an update popup like that the phone eventually told me too much time has passed and it will update now without giving me an option to prevent it. Do I need to enable OEM debugging and/or unlock the bootloader to really block OTA updates or is there an easier way?
Click to expand...
Click to collapse
OEM Debugging won't do anything to prevent updates; disabling Automatic Updates should do the trick. Not sure how to prevent the notification though, I'm on the latest 12 release and still getting an update notification. So are some others that aren't even rooted.
lapingultah said:
I feel the same way about Android 12 and successfully did a rollback (with full wipe unfortunately) using https://9to5google.com/2021/10/21/how-to-downgrade-from-android-12-to-android-11-on-google-pixel/ as a guide.
However, my concern now is how do I block 12 from updating automatically? I've disabled automatic updates under Developer Tools, but is that sufficient? I keep getting popups to update to 12 but so far I've managed to dismiss them. Last time I inadvertently dismissed an update popup like that the phone eventually told me too much time has passed and it will update now without giving me an option to prevent it. Do I need to enable OEM debugging and/or unlock the bootloader to really block OTA updates or is there an easier way?
Click to expand...
Click to collapse
You need to use an adb edit or package disabler to kill it or it will likely force update.
If the update downloads clearing the system cache before it completes may purge it. I haven't tested that though.
Go in settings, apps, In the Google Play services apps notification, there is a system update notification that can be disabled there.
I've format and install A11 back, rooted it, and since October 25, i haven't seen any update notification. I've already tried by the past to let the system update itself with the normal update way and it wasn't able to do it caused I'm rooted.. So i think I'm safe.
blackhawk said:
You need to use an adb edit or package disabler to kill it or it will likely force update.
Click to expand...
Click to collapse
ADB edit or package disabler to kill... what exactly? I'm sorry I'm not that familiar with this specific area.
ShadowJP88 said:
Go in settings, apps, In the Google Play services apps notification, there is a system update notification that can be disabled there.
Click to expand...
Click to collapse
This is only for the notification though while other things do happen in the background still, right?
lapingultah said:
ADB edit or package disabler to kill... what exactly? I'm sorry I'm not that familiar with this specific area.
This is only for the notification though while other things do happen in the background still, right?
Click to expand...
Click to collapse
I might be wrong but the fact of being rooted prevent the update to be pushed.
lapingultah said:
ADB edit or package disabler to kill... what exactly? I'm sorry I'm not that familiar with this specific area.
Click to expand...
Click to collapse
Are you rooted? If so there are better alternatives for you.
Package Disabler is what I use as I run stock. There are numerous threads on XDA about ADB apps and editing. Use Google search to dredge them up, put XDA at the search phase end.
Related
I have the 6gb ram TA-1062 build that I bought from China on ebay. On the box there is no Android One specification, just the regular Android logo.
When I boot my phone, I see "Powered by Android" screen followed by "Android One" screen and Nokia letters with white background.
I'm confused if my phone is truly Android One or the global rom that I have is just a modification of the regular Oreo?
The build number starts with 00WW. Currently 8.1 with security patch level dated to May 1. I havent't received the June update yet.
It's not Android One version.
If you wanna convert it to Android One version, try this:
1. unlock bootloader. (ask him---> hikari_calyx for help)
2. change SKUID to 600WW (https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-change-skuid-to-worldwide-t3808520)
3. If still can't get OTA, try https://forum.xda-developers.com/no...-to-convert-nokia-7-china-variant-to-t3769541 , you probably need factory reset and sideload 213B twice.
SUN Huayan said:
It's not Android One version.
If you wanna convert it to Android One version, try this:
1. unlock bootloader. (ask him---> hikari_calyx for help)
2. change SKUID to 600WW (https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-change-skuid-to-worldwide-t3808520)
3. If still can't get OTA, try https://forum.xda-developers.com/no...-to-convert-nokia-7-china-variant-to-t3769541 , you probably need factory reset and sideload 213B twice.
Click to expand...
Click to collapse
Thank you for your instructions. I wish I read this forum before making my purchase.
Additionally I want to ask, if I used my phone as it is, will I get OTA updates? Depending on whether I get the updates (even if it is a bit late), I may stick with this phone for a while. I don't want to brick it for nothing since I'm not very knowledeable working on it.
Baskettoman said:
Additionally I want to ask, if I used my phone as it is, will I get OTA updates? Depending on whether I get the updates (even if it is a bit late), I may stick with this phone for a while. I don't want to brick it for nothing since I'm not very knowledeable working on it.
Click to expand...
Click to collapse
You will get the OTA updates but not as fast as the Android One version though. The updates will be given as per the schedule of the country who's version you have - I am thinking China, since 6 GB is available only there.
Baskettoman said:
Additionally I want to ask, if I used my phone as it is, will I get OTA updates? Depending on whether I get the updates (even if it is a bit late), I may stick with this phone for a while. I don't want to brick it for nothing since I'm not very knowledeable working on it.
Click to expand...
Click to collapse
Of course you can get OTA updates. And it won't be late, just the same time as other countries.
Hi, when i reverted back to android 11 from android 12 beta 1 my play store system update is stuck on January patch. How do i get to the latest security patch? i've checked for update but nothing happens.
Is this after the June update? Mine is currently on May 1st after the June update. If unlocked I would try dirty flashing a full image. If locked, sideload the latest OTA via recovery.
I'm having the same issue since the first android 12 preview,when downgrading to android 11, google play system update stuck at January,i tried many ways but no luck.
Same here with Pixel 4
gm007 said:
I'm having the same issue since the first android 12 preview,when downgrading to android 11, google play system update stuck at January,i tried many ways but no luck.
Click to expand...
Click to collapse
Did you try flashing the full image and allowing a data wipe (fresh install). I'm guessing you tried dirty flashing it already. @2WildFirE
v12xke said:
Did you try flashing the full image and allowing a data wipe (fresh install). I'm guessing you tried dirty flashing it already. @2WildFirE
Click to expand...
Click to collapse
I said everything
I had to ask also in Google pixel community https://support.google.com/pixelpho...gle-play-system-update-stuck-at-january?hl=en
Yes I tried all tips, Google Support doesn't know to help.
It's an downgrade issue when come from 12
2WildFirE said:
Yes I tried all tips, Google Support doesn't know to help.
It's an downgrade issue when come from 12
Click to expand...
Click to collapse
When you reflash your phone using a full image, it wipes and formats your partitions, returning it to out of the box condition. That is the sole purpose of unlocking the bootloader and flashing a full factory image. There is nothing residual after flashing this way, so it cannot be a downgrade issue. I also agree the Google Pixel community is totally useless and laughable.
I suspect it is a server problem, it seems as if the pixels are still marked as beta and are therefore not getting an update.
2WildFirE said:
I suspect it is a server problem, it seems as if the pixels are still marked as beta and are therefore not getting an update.
Click to expand...
Click to collapse
I suspect people don't want to lose their data by properly wiping & restoring their phone to its factory state.
U don't know how often I did a full factory image flash.
But nothing worked!
v12xke said:
When you reflash your phone using a full image, it wipes and formats your partitions, returning it to out of the box condition. That is the sole purpose of unlocking the bootloader and flashing a full factory image. There is nothing residual after flashing this way, so it cannot be a downgrade issue. I also agree the Google Pixel community is totally useless and laughable.
Click to expand...
Click to collapse
I met the same issue with 4a5g. I tried flashing 5 times but issue still come. Google play services system update will automatically display 1 jan 2021 when i log in google account ( the account i was enroll to using android 12beta via OTA, but i've cancelled android 12beta)
I think issue need to be resolve by google or we can use other google account.
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
So that mean, we need to enroll pilot update 12beta again via OTA or flashing, right?
2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
Strange how it is behind. I thought new beta versions came out after the general release so they could roll the new security release into the beta. This would mean A12 beta would also be current. But I also haven't been running the betas for a couple years. Interesting.
2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
Please share your solution with android 11.
Sorry mate, no solution for Android 11 yet.
Only works so with Android 12 Beta
So thinking if Android 12 goes out live for all, our problem is solved.
The solution on Android 11 is to simply install the "Main components" APK from APK mirror
It's basically you're just updating manually.
Main components APKs - APKMirror
Main components APKs - APKMirror Free and safe Android APK downloads
www.apkmirror.com
2WildFirE said:
Sorry mate, no solution for Android 11 yet.
Only works so with Android 12 Beta
So thinking if Android 12 goes out live for all, our problem is solved.
Click to expand...
Click to collapse
There is a solution check my post.
Alexisnotfrommars said:
There is a solution check my post.
Click to expand...
Click to collapse
This isn't a solution. It only change the date not more or less!
Hello there!
I have a Xiaomi Redmi Note 10 Pro, and yesterday I made the grave mistake of hitting that "update" button. What used to be a close to perfect smartphone turned into a pile of trash with about 10 GREAT functions REMOVED. Instead they added 10 new phone-destroying functions which make this phone close to unusable for me at the moment.
That being said, I obviosuly want to downgrade my phone to the version it came with apparently is V12.0.15.0.RKFMIXM (Global). Is it safe to downgrade to this version from the version I'm on now 12.5.1? Even if it's not safe, could you please tell me how likely it is that my phone ends up bricked?
Thanks! I hope this works!
If you have updated it using Official Updater app, then there is a high risk of bricking your phone. It depends on ARB index.
Try flashing Fastboot ROM using Mi Flash tool. If it's not safe to downgrade, Mi Flash will prevent you from flashing it.
Yes, I used the official updater app in settings.
OK so you're there's a chance? Because this 12.5.1 version is complete and utter ****. I REALLY want to downgrade. Please help me out here, this version is SO BAD that I have to buy a new phone if the downgrade doesn't work.
In order to use Mi Flash tool, your bootloader has to be unlocked. If you are not familiar with these process, I suggest you to follow this method instead.
This is how you go back to a previous version of MIUI: revert your Xiaomi a buggy update - Xiaomi News - World Today News
When we update our Xiaomi we run the risk that this new update contains bugs. Although Xiaomi tests each new version before launching it, like any other software there may be undetected errors that spoil our user experience. It is not the first time that an update released by Xiaomi negatively...
www.world-today-news.com
Warning: Someone else stuck in bootloop while tried to use this method. check this
If you are not familiar with recovering phone from brick, decide yourself whether it's worth the risk. Alternatively, you can wait for the next update, which might solve your problem.
Have you tried updating to the latest 12.5.3?
I'm stuck on this crappy 12.5.1 as well but I don't want to unlock anything or wait for the update... So my question is can I use the Mi Tool without unlocking the bootloader?
Spudsicles said:
Have you tried updating to the latest 12.5.3?
I'm stuck on this crappy 12.5.1 as well but I don't want to unlock anything or wait for the update... So my question is can I use the Mi Tool without unlocking the bootloader?
Click to expand...
Click to collapse
I have not, because I have not received the update on my device yet. However I don't expect them to fix these god-awful "updates" in the next update, hence I'd rather just downgrade, which I'll probably try to do tomorrow. 12.0.15.0 was absolutely perfect (the version it came with) and I KNEW I shouldn't have updated ((
OSX.Nobody said:
In order to use Mi Flash tool, your bootloader has to be unlocked. If you are not familiar with these process, I suggest you to follow this method instead.
This is how you go back to a previous version of MIUI: revert your Xiaomi a buggy update - Xiaomi News - World Today News
When we update our Xiaomi we run the risk that this new update contains bugs. Although Xiaomi tests each new version before launching it, like any other software there may be undetected errors that spoil our user experience. It is not the first time that an update released by Xiaomi negatively...
www.world-today-news.com
Warning: Someone else stuck in bootloop while tried to use this method. check this
If you are not familiar with recovering phone from brick, decide yourself whether it's worth the risk. Alternatively, you can wait for the next update, which might solve your problem.
Click to expand...
Click to collapse
I have another Xiaomi I don't care about which ALSO has the horrible 12.5.1. Since I don't care about this device I'll try downgrading it tomorrow, and if it works I'll do it again with my Redmi Note 10 Pro
I'm really curious about those features you said they remove and why miui 12.5 is so bad, I was just about to update!
Hi! I would also like to know what is wrong with 12.5.1 on the redmi note 10 pro. Mine has 12.0.6 (Russian version I think), and I'm trying my best to figure out how to update it to 12.5.1, but I've read many comments saying it is trash.
Can you tell me your biggest complains? What I don't like about my current version is the 10 seconds always on display, and not being able to select an icon pack for the system launcher. Do you have those features on 12.5.1?
My friend, the uptade to 12.5 did not ad or remove any aplications or funtions.
My be you collect them from any place.
Spudsicles said:
So my question is can I use the Mi Tool without unlocking the bootloader?
Click to expand...
Click to collapse
No, installing a Fastboot ROM requires your device to have an unlocked bootloader.
Little Snevil said:
I'm really curious about those features you said they remove and why miui 12.5 is so bad, I was just about to update!
Click to expand...
Click to collapse
DON'T update! Here's a list of the worst ones:
1) They REMOVED the progress bar from the media players on the lock screen, so now you CAN'T scroll through music and audio directly from the lock screen.
2) The screen automatically shuts off after 5 seconds after receiving a notification and there's NO WAY to increase it, making it impossible to read more than 1 notification.
3) When swiping/deleting the last notification the notification screen automatically closes REGARDLESS if you had a media player or something else you wanted to check out, so now they're forcing you to open it up again every time you close the last notification.
4) The notification screen now has a non-removable "No notifications" text, as if I needed someone to TELL me that. Completely unnecessary and ugly as crap.
Note that these are NOT bugs, but features, so if you update you're never getting these features back.
I use a smartphone when I work and this crap only makes things harder for me! Downgrading today!
EDIT: These are ONLY my main issues, the whole update is super buggy and laggy ALL AROUND, so be prepared to add aother 100 bugs and glitches to that list!
Are you sure that you had that options before, at last 2 one impossible....
OSX.Nobody said:
In order to use Mi Flash tool, your bootloader has to be unlocked. If you are not familiar with these process, I suggest you to follow this method instead.
This is how you go back to a previous version of MIUI: revert your Xiaomi a buggy update - Xiaomi News - World Today News
When we update our Xiaomi we run the risk that this new update contains bugs. Although Xiaomi tests each new version before launching it, like any other software there may be undetected errors that spoil our user experience. It is not the first time that an update released by Xiaomi negatively...
www.world-today-news.com
Warning: Someone else stuck in bootloop while tried to use this method. check this
If you are not familiar with recovering phone from brick, decide yourself whether it's worth the risk. Alternatively, you can wait for the next update, which might solve your problem.
Click to expand...
Click to collapse
1 extremely quick question, which one of these is the correct one?
Thank you!
artembazhanov said:
1 extremely quick question, which one of these is the correct one?
Thank you!
Click to expand...
Click to collapse
The recovery rom is for TWRP, fastboot rom is of course fastboot flashing.
artembazhanov said:
1 extremely quick question, which one of these is the correct one?
Thank you!
Click to expand...
Click to collapse
Recovery ROM
OSX.Nobody said:
Recovery ROM
Click to expand...
Click to collapse
I downloaded the fastboot load because it's easier to install. Great news, I downgraded my Redmi Note 7 without issue and it's working flawlessly! Then I tried unlocking my Note 10 Pro, but it's telling me to wait 168 hours. Can I use it during that time? Because I kind of need to.
Thanks!
artembazhanov said:
I downloaded the fastboot load because it's easier to install.
Click to expand...
Click to collapse
I thought you were asking about the method that described in the link I shared, which needs Recovery ROM. If you have unlocked bootloader, you have plenty of possibility.
artembazhanov said:
Can I use it during that time?
Click to expand...
Click to collapse
Yes you can. But don't touch any options in Developer settings related to unlocking procedure. Specially do NOT logout Mi Account.
If you are going to unlock, you should try MIUI EU ROM first, It might solve your problem.
OSX.Nobody said:
I thought you were asking about the method that described in the link I shared, which needs Recovery ROM. If you have unlocked bootloader, you have plenty of possibility.
Yes you can. But don't touch any options in Developer settings related to unlocking procedure. Specially do NOT logout Mi Account.
If you are going to unlock, you should try MIUI EU ROM first, It might solve your problem.
Click to expand...
Click to collapse
Definitely won't be messing with developer mode any more this week, and yeah, I'm not logging out either. Thanks!
I'm waiting a week before trying anything else. According to xda-developers you have to wait if you want to unlock.
artembazhanov said:
I'm waiting a week before trying anything else. According to xda-developers you have to wait if you want to unlock.
Click to expand...
Click to collapse
Sorry I mean after unlocking your bootloader, you should try EU ROM first (before flashing official ROM).
Hi all,
In November 2019 I purchased this Tencent ROG phone ii off eBay. It came with a ww firmware, however it seems like I am unable to update to any version on the Asus website.
I have attached my HW Info. What is the path I need to take to update this thing to android 11?
Any help would be appreciated. Thank you.
Yes, you can't if your device is Tencent, even if you changed the fingerprint to ww and all the other stuff. There is a thread and someone made a small app or something that enables OTA ups for devices like yours (and mine) but I forgot the name and with the miriad of posts here, srsly I can't find it, lol. That thing work by changing the IMEI and other stuff iirc?? but since I'm lazy af it was too troublesome for me so I'm doing the upgrades like this: download the zip file from Asus website, move it to Internal root directory, I mean I just move with File manager from Downloads to Internal and restart the phone. Bam! after restart the phone asks me, do you wanna update? And I'm like O yeah baby, do you have to have to even ask? And thats all. Anyway as of this hours they didnt up the WW version there yet. There was a TW version for testing if I understood corectly but it's gone. Just wait for it
Thanks for your reply. If someone could link me with that app that would be nice.
I have tried every manual update on the Asus website (A9 and A10 ones) and I get "update failed" when trying to run them. This would indicate that i need to flash Raw? The thing is, I thought if I had a ww fingerprint I would be able to at least run the manual updates from Asus?
Also if someone has the version directly after 1908.12.0, I could try update to that via manual update, however I can't find that version anywhere on the internet. I believe 1908.12.1.1 exists somewhere, but it's not on the Asus website
I think u can upgrade by downloading the RAW firmware and install it
I would have to unlock my bootloader, clear all my data and flash via PC to use the raw firmware right? or would i be able to put it in the root directory of my phone and launch it that way?
Yes you have to use your pc and unlock the bootloader and everything it's not that hard and there's a lot of guides here u can use
No worries, thank you. I will flash directly to the android 11 WW Raw once that is released. I'm assuming there will be no problem going straight from 9 to 11 via a raw flash?
U welcome. And I don't think there will be any problems going straight to 11
android 10 on ROG Phone 2 is a mess, im also using Tencent version
android 10 on ROG Phone 2 is a mess, im also using Tencent version
android 10 on ROG Phone 2 is a mess, im also using Tencent version
Yeah that's why i remained on A9, i didn't feel like it was worth the effort to upgrade. However A11 has some cool features with google home that i want.
twicken said:
Yeah that's why i remained on A9, i didn't feel like it was worth the effort to upgrade. However A11 has some cool features with google home that i want.
Click to expand...
Click to collapse
A10 was a mess in the beginning, in the end it was better than A9.
A11, is even better than both. Battery life has been improved by about 15%.
gilsol said:
A10 was a mess in the beginning, in the end it was better than A9.
A11, is even better than both. Battery life has been improved by about 15%.
Click to expand...
Click to collapse
Sounds good. Does anyone know roughly how long it takes for the raw to show up? Can i raw flash to 10, then manually upgrade to 11?
twicken said:
Sounds good. Does anyone know roughly how long it takes for the raw to show up? Can i raw flash to 10, then manually upgrade to 11?
Click to expand...
Click to collapse
There's never a known timeline.
You can't use the images provided by Asus in their downloads? The manual OTA?
Nope i can not use the images provided by asus in their downloads. No. That's why i started this thread. I get the dreaded update failed message and nothing happens.
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Why you so eager that you can't wait a few days?
It's available now.
it has been up for about 5 hours
kevinireland11 said:
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Click to expand...
Click to collapse
Layoffs, poor employee morale, and Google moving away from innovation and a move to deplete resources from projects/divisions that are not returning enough profit.
If you've ever had to deal with Google customer "service" for any technical issues before, you already know why. Sometimes you get lucky and find a unicorn of a tech to help, but it's usually an infuriating mess dealing with them.
But, to be honest, I'd rather have a delayed update than a rushed and buggy update. Quality control is important.
kevinireland11 said:
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Click to expand...
Click to collapse
After all we are all just humans ... they sure have their reasons
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
No problems here.
JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
Rooted, Kirisakura Kernel, Apr. update. All good here.
JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it???
The mobile phone system is running normally.
Click to expand...
Click to collapse
Assuming you're rooted, that message is normal and can be ignored.
JimSmith94 said:
Assuming you're rooted, that message is normal and can be ignored.
Click to expand...
Click to collapse
The red eio corruption message isn't normal, but it can be ignored. You may be thinking of the "Your bootloader is unlocked....." message.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
Click to expand...
Click to collapse
It usually takes an update to get rid of that message. Flashing back to an earlier month and then updating again should get rid of the message. You can also just ignore it until the next update.
Sometimes flashing an old boot image (your phone likely won't boot) and then flashing a newer boot image gets rid of that message as well.
JimSmith94 said:
Assuming you're rooted, that message is normal and can be ignored I am root and magisk on my device..
Click to expand...
Click to collapse
Lughnasadh said:
The red eio corruption message isn't normal, but it can be ignored. You may be thinking of the "Your bootloader is unlocked....." message.
It usually takes an update to get rid of that message. Flashing back to an earlier month and then updating again should get rid of the message. You can also just ignore it until the next update.
Sometimes flashing an old boot image (your phone likely won't boot) and then flashing a newer boot image gets rid of that message as well.
Click to expand...
Click to collapse
I refresh init_boot.img or prompt this message.
Can someone please explain to me....
On official site for factory images there is only one factory image for april update as far as I can see.
(TQ2A.230405.003.E1, Apr 2023)
Does the E1 on the end means that it's for specific carrier?
If it is, does it matter for us that have unlocked phones?
ozyk100 said:
Can someone please explain to me....
On official site for factory images there is only one factory image for april update as far as I can see.
(TQ2A.230405.003.E1, Apr 2023)
Does the E1 on the end means that it's for specific carrier?
If it is, does it matter for us that have unlocked phones?
Click to expand...
Click to collapse
No, the E1 does not mean that -- in the past, the ending of the version number can indicate something like that, but if there is no other monthly version, it's safe to say that is not the case. Linked below is a post on how the version numbers are determined and/or how to read them...
When there is no carrier specific version of firmware updates, it means the factory firmware image is applicable to all. If there is any specific version, it is identical in most ways, it just has special data/setup/applications(not apps or programs) that usually help the device's radio connect to the carrier's network optimally -- and from what I've read somewhere, all subsequent updates have said modifications included in them anyways. But if you're not certain, always flashing the "global" version is a safe bet; at worst, you're just not implementing the optimal "code" for the device's radio to the carriers network is all.
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] 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
simplepinoi177 said:
No, the E1 does not mean that -- in the past, the ending of the version number can indicate something like that, but if there is no other monthly version, it's safe to say that is not the case. Linked below is a post on how the version numbers are determined and/or how to read them...
When there is no carrier specific version of firmware updates, it means the factory firmware image is applicable to all. If there is any specific version, it is identical in most ways, it just has special data/setup/applications(not apps or programs) that usually help the device's radio connect to the carrier's network optimally -- and from what I've read somewhere, all subsequent updates have said modifications included in them anyways. But if you're not certain, always flashing the "global" version is a safe bet; at worst, you're just not implementing the optimal "code" for the device's radio to the carriers network is all.
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] 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 for that explanation, I'll read up on it from the provided link.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
Click to expand...
Click to collapse
I had the same issue, but everything works normally without any issues. I regularly flash custom roms and factory images, so if you still want to fix this issue, restore a factory image using the Android flash tool.
Any info on whether the fingerprint scanner is being fixed or at east bettered with this?