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.
Does anyone who get it see a difference?
Could you provide the output of
Code:
fastboot getvar all
So we see, if the bootloader got updated and I can provide TWRP and XPeria AOSP.
Then the custom rom development can start.
Stock Android 8.0 September
(bootloader) version-bootloader:1310-7079_X_Boot_SDM845_LA1.0_O_60
Bootloader got an update and until Sunday I will upload a new Sony AOSP 8.1 build.
If it is bootable, I will release a new TWRP build.
Hmm, keep getting ”Could not install" from the India (IN) variant. Guess I'll try again tomorrow.
Anyone successfully install it and if so, with which region?
eelpout said:
Hmm, keep getting ”Could not install" from the India (IN) variant. Guess I'll try again tomorrow.
Anyone successfully install it and if so, with which region?
Click to expand...
Click to collapse
German H8266 on my H8296.
MartinX3 said:
German H8266 on my H8296.
Click to expand...
Click to collapse
Hello do you think I can possibly flash H8216 firmware to my H8276 just as you flash H8226 to your H8296?
nolihowell said:
Hello do you think I can possibly flash H8216 firmware to my H8276 just as you flash H8226 to your H8296?
Click to expand...
Click to collapse
You should flash H8266, because the H8276 is dualsim, too.
H8216 would work fine, but the second sim is dead.
The external sdcard maybe, too.
MartinX3 said:
German H8266 on my H8296.
Click to expand...
Click to collapse
OTA? Or did you flash it?
Maybe it's time for me to switch. ?
eelpout said:
OTA? Or did you flash it?
Maybe it's time for me to switch. ?
Click to expand...
Click to collapse
Xperifirm and its building new flasher
But it will be like a factory reset.
Buuut it will work like a charm. And you get your updates faster.
But aren't you from Canadia?
Maybe the Canadian software is optimized/calibrated for your mobile network technology. :silly:
Does this update just bring security updates?
dibdin said:
Does this update just bring security updates?
Click to expand...
Click to collapse
And some small fixes and improvements.
MartinX3 said:
Xperifirm and its building new flasher
But it will be like a factory reset.
Buuut it will work like a charm. And you get your updates faster.
But aren't you from Canadia?
Maybe the Canadian software is optimized/calibrated for your mobile network technology. :silly:
Click to expand...
Click to collapse
nah, U.S. but I grew up in Minnesota, which is close to Canada.
IN doesn't have problems with update speed, it's within hours of DE, but this is the second time the OTA has continuously failed. Though other times it's been fine.
OK, I see you're cheating and not getting it OTA.
Flashing another region's firmware though shouldn't require a full reset, as long as one removes the user data sin file from the folder.
dibdin said:
Does this update just bring security updates?
Click to expand...
Click to collapse
A new bootloader.
Which allows custom ROMs and twrp, which allows the DRM fix.
eelpout said:
nah, U.S. but I grew up in Minnesota, which is close to Canada.
IN doesn't have problems with update speed, it's within hours of DE, but this is the second time the OTA has continuously failed. Though other times it's been fine.
OK, I see you're cheating and not getting it OTA.
Flashing another region's firmware though shouldn't require a full reset, as long as one removes the user data sin file from the folder.
Click to expand...
Click to collapse
Since I switched to h8266 in April or May I install only OTA Delta updates.
MartinX3 said:
A new bootloader.
Which allows custom ROMs and twrp, which allows the DRM fix.
Click to expand...
Click to collapse
oh, hmmm. since it's a new bootloader, is it a risk to switch firmware regions?
eelpout said:
oh, hmmm. since it's a new bootloader, is it a risk to switch firmware regions?
Click to expand...
Click to collapse
Of course not.
It is an universal bootloader.
@MartinX3 Just flashed the *51 firmware and my BL version string is:
Code:
1310-7079_X_Boot_SDM845_LA1.0_O_60
I'm trying to boot AOSP Oreo, I just built today, but no success so far.
Have you got better luck booting aosp?
nasko_spasko said:
@MartinX3 Just flashed the *51 firmware and my BL version string is:
I'm trying to boot AOSP Oreo, I just built today, but no success so far.
Have you got better luck booting aosp?
Click to expand...
Click to collapse
Try my build in the twrp thread.
Someone told me, that he successfully booted the old aosp build.
So I made one with the newest sources.
A manual how to flash is there, too.
Maybe you need the OEM file from the last build.
MartinX3 said:
Try my build in the twrp thread.
Someone told me, that he successfully booted the old aosp build.
So I made one with the newest sources.
A manual how to flash is there, too.
Maybe you need the OEM file from the last build.
Click to expand...
Click to collapse
Ops! I apparently forgot to flash dtbo and vbmeta. Boots!!!
nasko_spasko said:
Ops! I apparently forgot to flash dtbo and vbmeta. Boots!!!
Click to expand...
Click to collapse
:laugh::silly:
Any errors, missing features?
How is the camera with the open camera app?
ADB? Usb? Touch? Sound?
The new 9.0 OEM image is compatible?
MartinX3 said:
:laugh::silly:
Any errors, missing features?
How is the camera with the open camera app?
ADB? Usb? Touch? Sound?
The new 9.0 OEM image is compatible?
Click to expand...
Click to collapse
Well the 8.1 is not much of a usable one, i'll try the 9.0 after the build is complete, the touchscreen is not working as expected, it's picked up as a touchpad the UI is navigated with mouse, it seems that the graphics acceleration is not working (gralloc?), brightness is not adjustable. RIL works(sort of), calls work (mic produces robotic sound), Data works. ADB is not working and Developer Options menu crashes the settings app, Sleep not working, device gets quite hot over time(PM?).
Sound works. Camera is not accessible(just gray screen with the navbar at the bottom) It's fast as hell, though... That works SDM845 (rock)
Heya,
I magisked my S21 ultra and when i want to check for updates it says registration failed?
It did not do that before I magisked it.
So I need to restore everything to fix it or ?
you need to be specific on your concern what apps says registration failed? it's better to provided screenshot of your issue
Here is the screenshot
Sorry it took so long
caspaas said:
Here is the screenshot
Sorry it took so long
Click to expand...
Click to collapse
it is not recommend to update your OS directly from Setting while Magisk is installed ...your phone would go into bootloop(unusable state) there are also stories of people that are force to buy new device because of this silly mistake also installing OS update from Setting would uninstall Magisk also worse case scenario would lock your bootloader too which as your provably know it's nightmare
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
You modify your system and expect samsung to push an update on your device? That won't work.
Riyal said:
You modify your system and expect samsung to push an update on your device? That won't work.
Click to expand...
Click to collapse
*laugh in Android 8 because i did not receive Android 9 update*
Riyal said:
You modify your system and expect samsung to push an update on your device? That won't work.
Click to expand...
Click to collapse
yeah sorry , had a Asus ROG 2 before this and it got OTA updates while rooted so.
New to samsung.
caspaas said:
Heya,
I magisked my S21 ultra and when i want to check for updates it says registration failed?
It did not do that before I magisked it.
So I need to restore everything to fix it or ?
Click to expand...
Click to collapse
yea you gotta restore everything in order to fix
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?
My device model is G781B. Sw bit U5. I'm facing battery issue lately on latest April security update. So I wanted to downgrade but as my software version is U5, I couldn't do it. So can anyone guide me which custom rom and recovery I can flash and Is there any way to downgrade to previous version of oneui.
Are you using android 13 (OneUI 5)
Samarimama said:
Are you using android 13 (OneUI 5)
Click to expand...
Click to collapse
One ui 5.1
kawsar4547 said:
My device model is G781B. Sw bit U5. I'm facing battery issue lately on latest April security update. So I wanted to downgrade but as my software version is U5, I couldn't do it. So can anyone guide me which custom rom and recovery I can flash and Is there any way to downgrade to previous version of oneui.
Click to expand...
Click to collapse
Oh God.
I'm sorry to read that you updated from binary, going back will be a bit impossible. through odin no longer.
You will have to wait for someone to work on something for those who are in binary 5.
upgrading to binary 5 in my point of view was totally unnecessary.
Good luck colleague, hope that someone can give you a solution through root or wait for an update in May.
mezacorleehone said:
You will have to wait for someone to work on something for those who are in binary 5.
upgrading to binary 5 in my point of view was totally unnecessary.
Good luck colleague, hope that someone can give you a solution through root or wait for an update in May.
Click to expand...
Click to collapse
I didn't know binary was gonna update
kawsar4547 said:
I didn't know binary was gonna update
Click to expand...
Click to collapse
MMMMMMM..
Every time that OTA sends an update, the software version comes out and therefore the binary.
if you download a system to flash via odin, you force the binary.
I even warned right here about that topic.
but unfortunately, nothing can be done at the moment.
mezacorleehone said:
You will have to wait for someone to work on something for those who are in binary 5.
upgrading to binary 5 in my point of view was totally unnecessary.
Good luck colleague, hope that someone can give you a solution through root or wait for an update in May.
Click to expand...
Click to collapse
the bootloader would need to be signed again after being modified, there's very little chance of this ever being fixed.
3mel said:
the bootloader would need to be signed again after being modified, there's very little chance of this ever being fixed.
Click to expand...
Click to collapse
It only remains to wait for Samsung to send an update that fixes that.
wait for a developer to send solutions via root.
I recommend you to use Kernel Bandido.
I don't know if it is compatible with binary 5.