Related
guys, can anyone knows how to revert to android 4.4.2 android 5.0.1 with? updated firmware bass headphones disappeared, this problem occurs not only at me. who are important sound in the headphones do not advise upgraded. ASUS disappointed by this update.
ME572C Lollipop 5.0.1? Where? Please share it with us. You can downgrade with MOFD_SDUPDATE.zip and recovery.
BerndHhn said:
ME572C Lollipop 5.0.1? Where? Please share it with us. You can downgrade with MOFD_SDUPDATE.zip and recovery.
Click to expand...
Click to collapse
I tried to downgrade the firmware. but in the new android 5.0.1 bootloader and recovery, and this does not take recovery firmware based on Android 4.4.2. And here is the update on the official website for ME572C, but only TW version, WW firmware not yet available. http://www.asus.com/ru/supportonly/ASUS MeMO Pad (ME572C)/HelpDesk_Download/
Yeah
I installed this night.
Sound is fine.
Tested on Audio Out and Bluetooth, but unfortunately no root possibility yet.
It broke my auto screen rotation. Although this isn't Asus fault it's a bug in lollipop. Also been reported on nexus and moto.
However I don't like the new look and don't like the new notification system or the way quick settings now require two swipes. Quick should mean quick.
Also noticed more lag in starting apps.
Want to revert back to 4.4.2 too
Frisian said:
It broke my auto screen rotation. Although this isn't Asus fault it's a bug in lollipop. Also been reported on nexus and moto.
However I don't like the new look and don't like the new notification system or the way quick settings now require two swipes. Quick should mean quick.
Also noticed more lag in starting apps.
Want to revert back to 4.4.2 too
Click to expand...
Click to collapse
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Armada17 said:
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Click to expand...
Click to collapse
Thats awful for you. Can't you get into any recovery anymore? Perhaps flash the 5.0.1. again?
I'm not going to try to downgrade but I wish I hadn't installed lollipop. I really like this tablet and everything worked perfectly. Now I have to rotate the screen manually. I cheked the sensors with a diagnostic tool and they are working fine. It's the software. It isn't known what triggers the bug so it could happen at any time or never. Nice work google.
Hopefully we'll have root and custom mods in the near future.
Armada17 said:
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Click to expand...
Click to collapse
If you can boot back into the download screen, you can probably reflash the newest firmware.
pWEN said:
If you can boot back into the download screen, you can probably reflash the newest firmware.
Click to expand...
Click to collapse
does not work, bootloader killed, dependent on Intel Inside logo.
Hi, i try at the moment downgrade from the me581cl. It looks good. You can look at my thread Root with downgrade for the intel developer tool.
The highest importent file is the ifwi.bin.
You can it flash with fastboot flash dnx .....
Has anyone found a way to do this? I foolishly manually upgraded my ME572CL (JP SKU) with the WW 5.0.1 firmware. Seemed OK at first but now noticing a lot of bugs which are making it quite unpleasant to use. Lollipop firmware didn't seem to add anything much to the experience anyway, so I would really like to downgrade back to 4.4.2 but MOFD_SDUPDATE fails.
kanagawaben said:
Has anyone found a way to do this? I foolishly manually upgraded my ME572CL (JP SKU) to the WW 5.0.1 firmware. Seemed OK at first but now noticing a lot of bugs which are making it quite unpleasant to use. Lollipop firmware didn't seem to add anything much to the experience anyway, so I would really like to downgrade back to 4.4.2 but MOFD_SDUPDATE fails.
Click to expand...
Click to collapse
I got ME572C(JP sku) and tried almost same things. Android 5.0.1(WW) seems stable on my environment but root is required for my usage. Downgrading with MOFD_SDUPDATE method also failed and now watching TWRP/CWM forums in order to get revised intel atom platform supports for 5.01....
gmaxjp said:
I got ME572C(JP sku) and tried almost same things. Android 5.0.1(WW) seems stable on my environment but root is required for my usage. Downgrading with MOFD_SDUPDATE method also failed and now watching TWRP/CWM forums in order to get revised intel atom platform supports for 5.01....
Click to expand...
Click to collapse
I did a factory reset and the WW 5.0.1 seems stable again now. Would still like to return to a rooted 4.4.2 if possible though.
Any progress on downgrading or rooting ME572C on lollipop? I do have droidboot.img available took out from 4.4 if that might help.
Myuboku said:
Any progress on downgrading or rooting ME572C on lollipop? I do have droidboot.img available took out from 4.4 if that might help.
Click to expand...
Click to collapse
Thanks for interest that. But it seems that we have no ways to revert 5.0x upgrade to 4.4x with method such as reflash partition or something like that because of fastboot oem stuffs to unlock bootloader are completely changed.
The only thing I succeed was reflashing the same version of OTA image WW_V12.14.1.12 downloaded from ASUS site (stupidly I cleared partitions before I confirmed if oem unlock is still valid or not....so I tried this to unblrick my one..). I tried flash partitions with images extracted from older ROM and fastboot server said "Not able to downgrade to KK" or something like that.
Perhaps fastboot server checks version of current vs to be flashed and reject if the version of the software is OLDER THAN CURRENT. This perhaps shows we can inject some hacks into current image, but I have still no progress regarding this idea because I was newbie to IA architecture hacking....I'm guessing that reversing fastboot.img contents shows the way to next milestone....
gmaxjp said:
Thanks for interest that. But it seems that we have no ways to revert 5.0x upgrade to 4.4x with method such as reflash partition or something like that because of fastboot oem stuffs to unlock bootloader are completely changed.
The only thing I succeed was reflashing the same version of OTA image WW_V12.14.1.12 downloaded from ASUS site (stupidly I cleared partitions before I confirmed if oem unlock is still valid or not....so I tried this to unblrick my one..). I tried flash partitions with images extracted from older ROM and fastboot server said "Not able to downgrade to KK" or something like that.
Perhaps fastboot server checks version of current vs to be flashed and reject if the version of the software is OLDER THAN CURRENT. This perhaps shows we can inject some hacks into current image, but I have still no progress regarding this idea because I was newbie to IA architecture hacking....I'm guessing that reversing fastboot.img contents shows the way to next milestone....
Click to expand...
Click to collapse
On one russian forum there is already a person who was able to downgrade to 4.4. Although, he flashed something from "CL" version, instead of "C" so the tablet was unusable, thats why he brought it to Asus service, they did a normal downgrade for him, but it took almost a month.
Myuboku said:
On one russian forum there is already a person who was able to downgrade to 4.4. Although, he flashed something from "CL" version, instead of "C" so the tablet was unusable, thats why he brought it to Asus service, they did a normal downgrade for him, but it took almost a month.
Click to expand...
Click to collapse
Beside the changed bootloader & recovery i believe it is not possible because of the changed partition assignment on LP5.0.1. KK isnt compatible with that anymore i guess and as far as i can see the partition assignment is not renewed and rewritten within any of the prelollipop firmwares again.
tycoo said:
Beside the changed bootloader & recovery i believe it is not possible because of the changed partition assignment on LP5.0.1. KK isnt compatible with that anymore i guess and as far as i can see the partition assignment is not renewed and rewritten within any of the prelollipop firmwares again.
Click to expand...
Click to collapse
Thus, Asus service has .raw service firmware, and they can downgrade to kitkat
Myuboku said:
Thus, Asus service has .raw service firmware, and they can downgrade to kitkat
Click to expand...
Click to collapse
Ya, that might be true.
tycoo said:
Ya, that might be true.
Click to expand...
Click to collapse
Also as i know, there is a person who has service firmwares. As he explained, when flashing service lollipop firmware, it somehow unlocks bootloader(i can be mistaken at this part), and makes it possible to install any android firmware.
(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.
lgmayka said:
(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.
Click to expand...
Click to collapse
Any reason not to use a Google Factory image? It looks like MMB29V is the most recent.
According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer. As I mentioned, joining the Android Beta program actually seems to be the easiest solution, if the current beta (NPD30G) is stable enough.
Frankly, I am surprised that Google/Motorola/AT&T (or any cell phone designer/manufacturer/carrier) allows a working cell phone to get into this state where the phone refuses to accept security updates.
For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.
That's half the fun of owning a Nexus, not waiting for updates. Dl the factory image, unzip it and the zip file inside and flash the system. IMG only and you'll lose nothing but root. If, of course, you are rooted.
http://forum.xda-developers.com/showthread.php?p=59561445/ You may give it a try..... prerooted lite stock rom.
lgmayka said:
According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer.
Click to expand...
Click to collapse
As already suggested, just install the system image. The simplest way to do that is via fastboot. Nothing gets erased unless you flash the userdata.img. Using Google's script to flash everything would overwrite the userdata partition.
The version you are on (MMB) is released to provide updates without updating the radio. The MOB release is the same as the equivalent MMB plus the package includes the updated radio. This is a requirement of the carriers who want to approve the radio before it's released.
You will be unable to take any *incremental* OTA if there is any differential between what's on your system partition and what the OTA is expecting. You can not hop over incremental OTA updates. They must be sequentially applied. Therefore, the safest way to get to a known state is with a factory image.
If fastbooting a factory image is unacceptably risky, then maybe an eBay phone wasn't a great choice.
Or, as you say, you go straight to N. If the beta program is still available now that N is released.
stevemw said:
For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.
Click to expand...
Click to collapse
I decided to do this. NPD90G is running well enough for me, and before long Google will release Android 7.0 Final.
I'm currently running ALP-L29 9.0.0.109(C185E2R1P8log) and i'm trying to install ALP-L29 9.0.0.159(C185E2R1P12) though system upgrade option, but when i'm trying to upgrade it shows system update error message and the upgrade does not executes.
Do i need to roll back to 8.0 version first? This beta that i have now installed will detect someday the new version and upgrade automatically ? the device is already unlocked.
Please advice.
Dear
How did you manage to install android pie on your mate 10? I am still at 8.0.0.140 and no any update since 2months.
Fazee99 said:
Dear
How did you manage to install android pie on your mate 10? I am still at 8.0.0.140 and no any update since 2months.
Click to expand...
Click to collapse
I'm not sure which method he used to update his phone, but you can use eRecovery method of FunkyHuawei if your phone is not unlocked with bootloader. I used it to update to 9.0.0.108 (mine is C636), going to update to 9.0.0.159 tonighf. Check the attached image, it shows the available Pie firmwares as mentioned.
themathers said:
I'm not sure which method he used to update his phone, but you can use eRecovery method of FunkyHuawei if your phone is not unlocked with bootloader. I used it to update to 9.0.0.108 (mine is C636), going to update to 9.0.0.159 tonighf. Check the attached image, it shows the available Pie firmwares as mentioned.
Click to expand...
Click to collapse
Dear I have tried to update with dload but its giving error after first reatart the device. And i think my phone is locked with bootlader(not sure). Mine is c185 MiddleEast version.
Fazee99 said:
Dear I have tried to update with dload but its giving error after first reatart the device. And i think my phone is locked with bootlader(not sure). Mine is c185 MiddleEast version.
Click to expand...
Click to collapse
Since Huawei stopped the bootloader unlocking service, and I got my phone recently, the method of unlocking the bootloader is troublesome and kind of costly, so I decided not to do anything with it. With FunkyHuawei's eRecovery method, you can update your phone to any firmwares available on their site even with a locked bootloaded. It is quite easy, you should take a look at it. If you decided to go with them, I'd recommend you to back up your data (HiSuite might not be able to restore app data) before updating. I had to factory reset the phone after the update because the phone might have some glitches. Really, I'd recommend this method, it does cost you $18 but it gets the job done. You can PM me if you have any further question.
---------- Post added at 09:36 AM ---------- Previous post was at 09:31 AM ----------
rayxanber said:
I'm currently running ALP-L29 9.0.0.109(C185E2R1P8log) and i'm trying to install ALP-L29 9.0.0.159(C185E2R1P12) though system upgrade option, but when i'm trying to upgrade it shows system update error message and the upgrade does not executes.
Do i need to roll back to 8.0 version first? This beta that i have now installed will detect someday the new version and upgrade automatically ? the device is already unlocked.
Please advice.
Click to expand...
Click to collapse
I had an error while trying to update to 159 via eRecovery method. The computer does not recognize the USB connection. Couldn't fix it myself so I contacted FunkyHuawei and they advised me to do HiSuite method and it worked. I thought I had to downgrade to Oreo first but I just left the 159 on and it could update. May be that could be your solution too.
Thank you all, i have unlocked, rebrand and install Pie my device using funkyhuawei services but since i ran out of credits i want to be sure that if i renew just 1 credit to download the new firmware i can do the upgrade directly from my pie old build to the new one without issues instead of purchase more credits if i have to execute more tasks.
I've manage to download the new build from another site but as i mentioned as im trying to installing using the hidden menu it does not work
rayxanber said:
Thank you all, i have unlocked, rebrand and install Pie my device using funkyhuawei services but since i ran out of credits i want to be sure that if i renew just 1 credit to download the new firmware i can do the upgrade directly from my pie old build to the new one without issues instead of purchase more credits if i have to execute more tasks.
I've manage to download the new build from another site but as i mentioned as im trying to installing using the hidden menu it does not work
Click to expand...
Click to collapse
You might want to try the following procedure:
https://forum.xda-developers.com/hu...uide-how-to-install-emui-9-android-9-t3839316
Re:
[email protected] said:
You might want to try the following procedure:
https://forum.xda-developers.com/hu...uide-how-to-install-emui-9-android-9-t3839316
Click to expand...
Click to collapse
Thanks, but im already in Pie beta and trying to inplace update to Pie final .
rayxanber said:
Thank you all, i have unlocked, rebrand and install Pie my device using funkyhuawei services but since i ran out of credits i want to be sure that if i renew just 1 credit to download the new firmware i can do the upgrade directly from my pie old build to the new one without issues instead of purchase more credits if i have to execute more tasks.
I've manage to download the new build from another site but as i mentioned as im trying to installing using the hidden menu it does not work
Click to expand...
Click to collapse
Hey, I replied to your PM, did you get it?
Re:
themathers said:
Hey, I replied to your PM, did you get it?
Click to expand...
Click to collapse
I've just sent a couple of replies.
Thanks.
When is mate 10 (Alp-l29, c185) receiving emui 9 in the middle east?
Hi I am desperate to receive emui 9.0 after seeing many sites claiming the beta for middle east varients.
I joined the beta program few months ago but misteriously got kicked out or I must say the "my projects" tab was empty a week ago. I would like to know when actually huawei will roll out and OTA update for the mate 10, thankyou
themathers said:
I'm not sure which method he used to update his phone, but you can use eRecovery method of FunkyHuawei if your phone is not unlocked with bootloader. I used it to update to 9.0.0.108 (mine is C636), going to update to 9.0.0.159 tonighf. Check the attached image, it shows the available Pie firmwares as mentioned.
Click to expand...
Click to collapse
Dear,
I have managed to install ALP-L29 9.0.0.159 through funkyhuawei, and its working perfectly fine. but I need to know whether i will receive the future OTA updates or no? Also my ERecovery is no more functional, I can not go back to stock \ROM. Please advise..
Thanks
Fazee99 said:
Dear,
I have managed to install ALP-L29 9.0.0.159 through funkyhuawei, and its working perfectly fine. but I need to know whether i will receive the future OTA updates or no? Also my ERecovery is no more functional, I can not go back to stock \ROM. Please advise..
Thanks
Click to expand...
Click to collapse
Regarding to OTA, FH told me that we might be able to receive (this build is a legit build from Huawei anyway), but we have to wait and see. I notice that Huawei sends out update at different times to different locations for the same model, hate it. Mate 10 pro is on build 161, but Mate 10 is on build 159, so I guess we have to check FH once in a while together with System Updater. Actually, FH released official Pie updates before Huawei officially announced Pie update schedule, kinda strange though, many have a conspiracy theory on the relationship between FH and Huawei
I think the ROMs provided by FH are stock ROM, that is why we can update the phone through Huawei methods and not third-party ones. Let me guess, you did a factory reset after upgarding to Pie? I had this problem with beta version, and it is an issue with Pie builds, according to FH. If you want to downgrade to Oreo or another build, you have to do it via a specific HiSuite version, to me this way is so much faster than eRecovery. I can provide you the software, but I'd suggest you to contact to FH first, they told me that the reason they don't publish this method is because not every one's issue has a same cause. This is a last resort.
Hope this'd be helpful.
themathers said:
Regarding to OTA, FH told me that we might be able to receive (this build is a legit build from Huawei anyway), but we have to wait and see. I notice that Huawei sends out update at different times to different locations for the same model, hate it. Mate 10 pro is on build 161, but Mate 10 is on build 159, so I guess we have to check FH once in a while together with System Updater. Actually, FH released official Pie updates before Huawei officially announced Pie update schedule, kinda strange though, many have a conspiracy theory on the relationship between FH and Huawei
I think the ROMs provided by FH are stock ROM, that is why we can update the phone through Huawei methods and not third-party ones. Let me guess, you did a factory reset after upgarding to Pie? I had this problem with beta version, and it is an issue with Pie builds, according to FH. If you want to downgrade to Oreo or another build, you have to do it via a specific HiSuite version, to me this way is so much faster than eRecovery. I can provide you the software, but I'd suggest you to contact to FH first, they told me that the reason they don't publish this method is because not every one's issue has a same cause. This is a last resort.
Hope this'd be helpful.
Click to expand...
Click to collapse
Dear,
They also told me that they didn't stop OTA updates, it's upto huawei to send OTA updates, I hope so it will be like this,
Yes I did factory reset after installing the Pie on my phone, because it was little slow and glitches. No ERecovery is not working to go back to Stock recovery. Can you please tell me that method to try it. Which version you are talking about for HiSuite. I want to go back to the Stock ROM and to receive updates via Huawei OTA. Its very strange to me, that updates are available in the market for the phone, and Huawei not sending to their phones, and also someone like(FW) able to update the phone, something is fishy. May huawei becomes more professional in doing promises.. and satisfy their customers more.
Fazee99 said:
Dear,
They also told me that they didn't stop OTA updates, it's upto huawei to send OTA updates, I hope so it will be like this,
Yes I did factory reset after installing the Pie on my phone, because it was little slow and glitches. No ERecovery is not working to go back to Stock recovery. Can you please tell me that method to try it. Which version you are talking about for HiSuite. I want to go back to the Stock ROM and to receive updates via Huawei OTA. Its very strange to me, that updates are available in the market for the phone, and Huawei not sending to their phones, and also someone like(FW) able to update the phone, something is fishy. May huawei becomes more professional in doing promises.. and satisfy their customers more.
Click to expand...
Click to collapse
Yes, I also got glitches and many time couldn't turn on the screen, that is why I had to do it. I uploaded the HiSuite version here: https://drive.google.com/file/d/1NYsPYS6aB1BHaf1p5F_mJJJQMOSc0lql/view?usp=drivesdk
Uninstall your current HiSuite, install this version and follow the same steps (DNS) with FH but without eRecovery.
Not so sure about the stock recovery as you mentioned, but may be what you need is to downgrade to Oreo. I checked on FH and they have a new firmware for downgrade purpose, I don't know what is the difference though. Good luck.
Just received a patch for build 159 from Huawei, so I think OTA works normal on FH's roms.
Finally, ALP-L29 9.0.0.159 officially launched here in Saudi Arabia, and I was not satisfied with the FunkyHuawei software. So decided to downgrade my phone to Android Oreo again, and then update officially.
themathers said:
Yes, I also got glitches and many time couldn't turn on the screen, that is why I had to do it. I uploaded the HiSuite version here: https://drive.google.com/file/d/1NYsPYS6aB1BHaf1p5F_mJJJQMOSc0lql/view?usp=drivesdk
Uninstall your current HiSuite, install this version and follow the same steps (DNS) with FH but without eRecovery.
Not so sure about the stock recovery as you mentioned, but may be what you need is to downgrade to Oreo. I checked on FH and they have a new firmware for downgrade purpose, I don't know what is the difference though. Good luck.
Click to expand...
Click to collapse
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?