Related
UPDATED TOPIC! 02.08.2017
ASUS has released the NEWEST Nougat Update for ZF3U:
Newest Release: Version WW-14.1010.1706.50 Release Date: 2017/08/01 Size: 1.71 GBytes
Previous Version: Version WW_14.1010.1705.49 Release Date: 21.06.2017
Here is the official Update for Manual Install. DIRECT from ASUS Servers. Version WW-14.1010.1706.50 Release Date: 2017/08/01 Size: 1.71 GBytes
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/UL-ASUS_A001-WW-14.1010.1706.50-user.zip
Via:
http://https://www.asus.com/Phone/ZenFone-3-Ultra-ZU680KL/HelpDesk_Download/
If the link is expired Get it from the Asus ZenFone 3 Ultra Support and Firmware Website under Drivers and Tools-ANDROID Section. It is for the WW Version:
UPDATE! :OTA Update Working ONLY with phones with LOCKED Bootloaders. The Manual Update will work with both LOCKED and UNLOCKED Bootloaders. I have tested the OTA Update and after I unlocked my ZF3U's bootloader, I can no longer get update notification (on my previous ZF3U-I am on my 2nd one). From what I have read, ASUS servers block any devices with unlocked bootloaders from accessing automatic system updates. My only option is to find a way to RELOCK the bootloader or use the Manual Update file.
Enjoy!
Changelog:
Android 7.0 Nougat comes with handful of features such as App Shortcuts, Multi Window support, restart setting to power menu, Launch the camera by pressing the power button twice, Image Keyboard support, 100 emoji added, GIF Support, Quick Reply via Notification, Notification Redesigned panel, Notifications prioritization, Enhanced Doze Mode, System UI Tuner, Customizable Quick Settings, Don Not Disturb, New Settings Panel Redesigned, Data Saver per App, seamless updates and New Emoji Support.
-----------------------------------------
ASUS ZenFone 3 Ultra=ZU680KL(A001) software Image:V14.1010.1706.50 for WW SKU only*
Improvement Item：
1.Modify strings in several apps
2.Google security patch update
3.Update FR E-label
For more information please refer to：
TW：http://www.asus.com/zentalk/tw/ReleaseNotes
WW：http://www.asus.com/zentalk/ReleaseNotes
Steps of Update:
1.Check software version of your device**
2.Download device software and Update SOP (From “Manual” Item)
3.Only apply to same SKU update, Example: WW->WW, CN->CN, .
4.Software update cannot transfer the software SKU and downgrade the software version.
5.Wrong SKU may cause update failure, please update the same SKU version only.
*How to know the device model?
Path: Settings->About-> Model number
Example: ASUS_Z00ED
**How to know the device software version?
Path: Settings->About-> software information->Build number
AWFRONT said:
The Asus Zenfone 3 Ultra is now receiving the Android 7.0 Nougat update with software version 14.1010.1702.36. The update is rolling out over-the-air.
Check for it from Settings > About > System Updates on your Zenfone 3 Ultra. If you’ve got the update, go ahead and download/install it.
It appears to be currently available for the WW (Worldwide Version)
Currently no manual install file is available but I guess this will be available very soon. I also think this may be the first and last final update from ASUS for the ZF3U before they launch another version but it is nice to have the newest version after all and I very much look foreard to making use of multi-window on the device.
--------------------------------------------------------------------------------------------------
Mine is WW version but couldn't receive the update yet. Why?
Click to expand...
Click to collapse
ctorbaoglu said:
AWFRONT said:
The Asus Zenfone 3 Ultra is now receiving the Android 7.0 Nougat update with software version 14.1010.1702.36. The update is rolling out over-the-air.
Check for it from Settings > About > System Updates on your Zenfone 3 Ultra. If you’ve got the update, go ahead and download/install it.
It appears to be currently available for the WW (Worldwide Version)
Currently no manual install file is available but I guess this will be available very soon. I also think this may be the first and last final update from ASUS for the ZF3U before they launch another version but it is nice to have the newest version after all and I very much look foreard to making use of multi-window on the device.
--------------------------------------------------------------------------------------------------
Mine is WW version but couldn't receive the update yet. Why?
Click to expand...
Click to collapse
It may be because your Bootloader is unlocked. If it is you will not receive the update. My ZF3U's bootloader was locked when I received the update. However, when I unlocked the bootloader, rooted and then decided to wipe everything through TWRP to do a fresh install of everything to reinstall Android 7.0 the trouble started. Now, I cannot do firmware update using the system Update menu (notification of update availability is not there). This is because the bootloader is now unlocked and I don't know if it is possible to relock it. I guess I have to wait for the full manual package of Android 7 to become available or see if anyone can help me to relock the bootloader and then update from Android 6.0 original firmware. I was excited to be finally getting Android 7.0 but only managed to use it for 1 day. Oh well, you live and learn.:crying:
Click to expand...
Click to collapse
UPDATE! As some of us have found out. ASUS has now removed the Nougat firmware (MANUAL Update file) for the ZF3U. As my device's bootloader is unlocked I can no longer receive OTA updates. Perhaps someone could give us an update on the status of the OTA release of Nougat for the ZF3U. I have downloaded the file before removal and successfully installed it. I don't mind uploading it to a file sharing website. However, I am currently using it and I am still having the same issues I had when I used the OTA update, so my advice is for everyone to wait for a confirmed final version of the firmware as the version we have may still be buggy. This may be the reason why they removed it and lets hope they fix and reupload soon. Here are quick my observations of the firmware;
-Fingerprint scanner still not registering when device is setup for the first time or under settings later,
-Screen Rotation is not functional on some of my apps that were able to use it previously with Android 6.0
-My device serial nunber has changed to 111111111111111 (15x1s)( I tried lots of things to put it right but all attempts failed)
-Dual Sim settings access from the notification menu shortcuts is no longer there (it was very useful for me),
-Multi-Window is not operating on all the apps for some reason. On the OTA that i had installed I was able to use it but on the manual firmware file this does not seem to work properly.
-My device is no longer showing under my ASUS account as a registered device (I don't know if this is a firmware issue or not as bootloader does show the correct serial no)
Also, does anyone know how or where in the firmware I can extract the boot.img, recovery.img and all the othr essential .img files to restore stocj recovery after root/twrp installation?
If anyone has any ideas as to why the serial number and fingerprint issues are there, I would like to hear from you. Other issues are tolerable. Thanks.
AWFRONT said:
UPDATE! As some of us have found out. ASUS has now removed the Nougat firmware (MANUAL Update file) for the ZF3U. As my device's bootloader is unlocked I can no longer receive OTA updates. Perhaps someone could give us an update on the status of the OTA release of Nougat for the ZF3U. I have downloaded the file before removal and successfully installed it. I don't mind uploading it to a file sharing website. However, I am currently using it and I am still having the same issues I had when I used the OTA update, so my advice is for everyone to wait for a confirmed final version of the firmware as the version we have may still be buggy. This may be the reason why they removed it and lets hope they fix and reupload soon. Here are quick my observations of the firmware;
-Fingerprint scanner still not registering when device is setup for the first time or under settings later,
-Screen Rotation is not functional on some of my apps that were able to use it previously with Android 6.0
-My device serial nunber has changed to 111111111111111 (15x1s)( I tried lots of things to put it right but all attempts failed)
-Dual Sim settings access from the notification menu shortcuts is no longer there (it was very useful for me),
-Multi-Window is not operating on all the apps for some reason. On the OTA that i had installed I was able to use it but on the manual firmware file this does not seem to work properly.
-My device is no longer showing under my ASUS account as a registered device (I don't know if this is a firmware issue or not as bootloader does show the correct serial no)
Also, does anyone know how or where in the firmware I can extract the boot.img, recovery.img and all the othr essential .img files to restore stocj recovery after root/twrp installation?
If anyone has any ideas as to why the serial number and fingerprint issues are there, I would like to hear from you. Other issues are tolerable. Thanks.
Click to expand...
Click to collapse
After some thought on your issue, do you now which version of the device you have? Maybe you have an China(CN) device and not World Wide(WW)? Just trying to think about your issues and it seems to possibly be that your firmware may not working correctly. This very well maybe because ASUS dropped a faulty firmware on you/us, or maybe because you tried WW firmware on a CN device? Or vice versa? Have you looked into what would happen if a firmware for a different region was installed on a device?
As for the images, I believe you can get the boot.img inside the firmware zip files you download from ASUS. Just unpack it and the boot.img should be in the root of that folder. I can't find the recovery.img from anywhere, other than from Shaka's megadownload page. I was able to get that one working on my Zenfone though and successfully put my Zf3U back to stock.
doctahjeph said:
After some thought on your issue, do you now which version of the device you have? Maybe you have an China(CN) device and not World Wide(WW)? Just trying to think about your issues and it seems to possibly be that your firmware may not working correctly. This very well maybe because ASUS dropped a faulty firmware on you/us, or maybe because you tried WW firmware on a CN device? Or vice versa? Have you looked into what would happen if a firmware for a different region was installed on a device?
As for the images, I believe you can get the boot.img inside the firmware zip files you download from ASUS. Just unpack it and the boot.img should be in the root of that folder. I can't find the recovery.img from anywhere, other than from Shaka's megadownload page. I was able to get that one working on my Zenfone though and successfully put my Zf3U back to stock.
Click to expand...
Click to collapse
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
AWFRONT said:
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
Click to expand...
Click to collapse
hhhmmm, I had a similar issue with a corrupted cache partition that was causing boot loops. I was able to get it fixed. Try this. Download the latest WW firmware from the website, MM no nougat. Then flash the original boot.img and recovery.img from Shaka's megadownload page. Boot into stock recovery and do a factory reset. They should wipe all the partitions and format them again. After that install update from SD card and choose the latest WW firmware zip you just downloaded. Profit??
doctahjeph said:
hhhmmm, I had a similar issue with a corrupted cache partition that was causing boot loops. I was able to get it fixed. Try this. Download the latest WW firmware from the website, MM no nougat. Then flash the original boot.img and recovery.img from Shaka's megadownload page. Boot into stock recovery and do a factory reset. They should wipe all the partitions and format them again. After that install update from SD card and choose the latest WW firmware zip you just downloaded. Profit??
Click to expand...
Click to collapse
I have tried your suggestion numerous times and;
-it appears that when I boot to Android M, I don't have any sound in calls, fingerprint and other issues fully remain.
-when I upgrade to Android N, then Iam able to hear call sounds but fingerprint scanner still does not register and other issues still remain.
I have a feeling that somewhere along the process my device has enabled some sort of encryption and this is preventing the device from enabling all the features. No matter how many times I install/reinstall/wipe using stock or TWRP no change.
Does anyome know how I could disable encryption either using some sort of google service or through root etc... In settings device reports that it is encrypted. Also when I first booted the device after firmware update encrypting device message was shown. Not sure whats going on with my device. Hope to find out/fix soon though.
ASUS Releases new update to fix the previously faulty update that was withdrawn.
Latest Version WW-14.1010.1703.42
Previous Version [Withdrawn due to faults] WW-14.1010.1703.36
I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
AWFRONT said:
ASUS Releases new update to fix the previously faulty update that was withdrawn.
Latest Version WW-14.1010.1703.42
Previous Version [Withdrawn due to faults] WW-14.1010.1703.36
I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
Click to expand...
Click to collapse
???? Thank you!!!
ASUS has released the NEWEST Nougat Update for ZF3U.
Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes
ASUS ZenFone 3 Ultra=ZU680KL(A001) software Image:V14.1010.1706.50 for WW SKU only*
Improvement Item：
1.Modify strings in several apps
2.Google security patch update
3.Update FR E-label
For more information please refer to：
TW：http://www.asus.com/zentalk/tw/ReleaseNotes
WW：http://www.asus.com/zentalk/ReleaseNotes
Steps of Update:
1.Check software version of your device**
2.Download device software and Update SOP (From “Manual” Item)
3.Only apply to same SKU update, Example: WW->WW, CN->CN, .
4.Software update cannot transfer the software SKU and downgrade the software version.
5.Wrong SKU may cause update failure, please update the same SKU version only.
*How to know the device model?
Path: Settings->About-> Model number
Example: ASUS_Z00ED
**How to know the device software version?
Path: Settings->About-> software information->Build number
Once again, I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
Never mind.
AWFRONT said:
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
Click to expand...
Click to collapse
Hey @AWFRONT How did u manage to go back from android 7 to 6 ...i recently updated my phone to nougat and want to go back to mm. Could u help me out I have unlocked bootloader
Hi! I did not downgrade from Android 7.0 to 6.0 on my new/2nd ZF3U. If you read a post I made in another topic you will see that I am now on my 2nd ZF3U because the 1st one had some serious issues and then it powered off so I gave up and sent for repair through my insurance but they said it could not be repaired so I bought another one with the payout I received and this one I am using, I use in its factory state with Bootloader locked and unrooted and given the lack of developer support for this handset, I do not want to modify anything.
My advice would be to stick with Android 7.0 and if there are any features you are missing then write them out and send to Asus and hope thy will fix in future update. With my previous ZF3U, I did do a downgrade on the 1st ZF3U but this resulted in Fingerprint scanner failing and I could not hear the other side when making and receiving calls and the device serial number in About Phone section was incorrect (changed to all 1s).Unless you have insurance and a spare phone, I would not recommend you downgrading. Too much of a risk with this handset. If you want to do it, then go ahead and you can share yoir findings here.
Instructions to follow:
-Disable and erase fngerprint records in settings
-Prepare a microsd card with the MM manual firmware in it and reboot into recovery.
-If you are rooted then wipe cache and factory reset but do not wipe data/system partition,
-Select update from SD Card and select firmware file and wait for the process to complete.
-reboot back.into recovery, you should hopefully see the factory kernel has downgraded to I think version 1.26 from 3.11 and then do another factory wipe and reboot and see the results.
Sorry, cannot be of much help but I wish the developers could pay a little bit more attention to this device like the Samsung Note series.?
AWFRONT said:
Hi! I did not downgrade from Android 7.0 to 6.0 on my new/2nd ZF3U. If you read a post I made in another topic you will see that I am now on my 2nd ZF3U because the 1st one had some serious issues and then it powered off so I gave up and sent for repair through my insurance but they said it could not be repaired so I bought another one with the payout I received and this one I am using, I use in its factory state with Bootloader locked and unrooted and given the lack of developer support for this handset, I do not want to modify anything.
My advice would be to stick with Android 7.0 and if there are any features you are missing then write them out and send to Asus and hope thy will fix in future update. With my previous ZF3U, I did do a downgrade on the 1st ZF3U but this resulted in Fingerprint scanner failing and I could not hear the other side when making and receiving calls and the device serial number in About Phone section was incorrect (changed to all 1s).Unless you have insurance and a spare phone, I would not recommend you downgrading. Too much of a risk with this handset. If you want to do it, then go ahead and you can share yoir findings here.
Instructions to follow:
-Disable and erase fngerprint records in settings
-Prepare a microsd card with the MM manual firmware in it and reboot into recovery.
-If you are rooted then wipe cache and factory reset but do not wipe data/system partition,
-Select update from SD Card and select firmware file and wait for the process to complete.
-reboot back.into recovery, you should hopefully see the factory kernel has downgraded to I think version 1.26 from 3.11 and then do another factory wipe and reboot and see the results.
Sorry, cannot be of much help but I wish the developers could pay a little bit more attention to this device like the Samsung Note series.?
Click to expand...
Click to collapse
all of this from twrp or stock recovery
If you have TWRP installed then apply from it, if not you can use the stock recovery of Android 6.0 as posted in one of the topics of ZF3U forum sections and flash it using custom recovery and then flash the appropriate firmware file of Android MM version 6.0 and on completion wipe cache, factory data and reboot.
Due to lack of developer support for this device, I do not recommend that you rollback the firmware. When my 1st device failed I realised that ASUS devices don't have the software fixability ease of Samsung devices so I am using my 2nd ZF3U in its original factory state. I love the device as it is and don't want to mess with it and root is no longer important to me.
does anyone know if this latest firmware update Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes is still rootable before i update from Android 7.0 (WW_14.1010.1703.42),thanks
gubbilo144 said:
does anyone know if this latest firmware update Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes is still rootable before i update from Android 7.0 (WW_14.1010.1703.42),thanks
Click to expand...
Click to collapse
mine is
Malam
anybody updated to WW-14.1010.1711.62 is it still 7.0 or 7.1.1
The Feb 2018 Security Update is now available for our phones.
If you haven't gotten it already go to Settings->System updates and see if it's available there.
From [ZenFone 3] [180209] ZenFone 3 Zoom ZE553KL_ WW_V71.60.139.27
Update Google security patch
Enable Taiwan CHT VoWiFi functions.
Performance improved and bugs fixed.
Is there a .zip available for people with unlocked bootloaders?
kekley said:
Is there a .zip available for people with unlocked bootloaders?
Click to expand...
Click to collapse
Hi @kekley, mine is still locked so I don't have experience with that scenario here (have done with other phones but decided to leave this one stock).
The update (as zip) is here: Version WW-71.60.139.27 - ZE553KL
(Note the SKU)
This is a message from another user who has TWRP installed and still did a previous update: How to update firmware if you've already flashed TWRP
Hopefully that's enough to get you going.
koimr said:
Hi @kekley, mine is still locked so I don't have experience with that scenario here (have done with other phones but decided to leave this one stock).
The update (as zip) is here: Version WW-71.60.139.27 - ZE553KL
(Note the SKU)
This is a message from another user who has TWRP installed and still did a previous update: How to update firmware if you've already flashed TWRP
Hopefully that's enough to get you going.
Click to expand...
Click to collapse
I was referring more to the fact that the zip file for the update was not on the support page for the device until recently but thank you for going through the trouble to write this up. I'm sure it will be useful to someone. :good:
When I did a factory reset on the last firmware, MiniMovie app came back which had been removed on firmwares before. After the update to this firmware and factory reset again, MiniMovie was gone again but now they added BeautyLive. Just weird.
These update packages should work on global variant Nokia X6.
Usage:
Confirm your current version by dialing *#*#227#*#* before update.
Then download the package and rename to the specific filename I gave, place it to root directory of internal storage and dial *#*#874#*#* to update.
After the update procedure completed, update package will be deleted from your phone automatically.
Global Release:
Note: From DRG-250A build, it blocked current bootloader unlock method, be careful.
Click to expand...
Click to collapse
June 2018 to August 2018 (DRG-250A-0-00WW-B05-229D-0-00WW-B01-update.zip)
August 2018 to September 2018 (DRG-250B-0-00WW-B01-250A-0-00WW-B05-update.zip)
Android Pie November 2018 (DRG-330B-0-00WW-B01-update.zip)
Thanks for your work supporting our device!
Do you have boot image of 250A version?
izkyline said:
Do you have boot image of 250A version?
Click to expand...
Click to collapse
Yes that would be handy. I read that payload_dumper doesn't work on incremental updates. I'm still looking for ways to extract a boot.img
Hi bro I need to unlock the blltloader for my nonia 6.1 ta-1050 . If you could help me plzz
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
My nokia
DRG-250A-boot_patched.img patched with Magisk v17.1:
https://www111.zippyshare.com/v/12gKJE7u/file.html
how to update the path for x6
Hello,
*#*#227#*#* works well.
*#*#874#*#* has no response at all. Is root or bootloader required to do that?
I just realize the X6 I bought from ebay is global firmware version, which does not support OTA. Use OTA to update to latest firmware is a key feature I am looking for. I do not care it is China version or Global version.
Do you have any suggestion that what should be the easiest way? Hopefully no bootloader required. Thanks!
google play pretent CN OTA?
Boss,
After discuss with many other user, we think it is because I am using China version rom, but installed Google play, which pretent OTA update.
Do you think so? Could you give us a solution?
I bought the phone from ebay. I just need OTA.
yshgcs said:
Hello,
*#*#227#*#* works well.
*#*#874#*#* has no response at all. Is root or bootloader required to do that?
I just realize the X6 I bought from ebay is global firmware version, which does not support OTA. Use OTA to update to latest firmware is a key feature I am looking for. I do not care it is China version or Global version.
Do you have any suggestion that what should be the easiest way? Hopefully no bootloader required. Thanks!
Click to expand...
Click to collapse
Will this work on Android one varient i.e , Nokia 6.1 plus?
Do you have boot image of 250B version? I need root my device, boot September, help me
thaidaidong25 said:
Do you have boot image of 250B version? I need root my device, boot September, help me
Click to expand...
Click to collapse
Use the boot image from Nokia 7 Plus. They work. Just don't flash it, only boot it.
thanks for sharing, i just installed the pie version on my nokia 6.1 plus
Hey I just installed the pie version on my Nokia 6.1 plus (TA-1083).
Will the installation void my warranty?
My camera app is crashing like crazy... Is anyone else experiencing this?
xoxoJoelxoxo said:
Hey I just installed the pie version on my Nokia 6.1 plus (TA-1083).
Will the installation void my warranty?
My camera app is crashing like crazy... Is anyone else experiencing this?
Click to expand...
Click to collapse
No, it will not destroy the warranty at all. As for the camera app, go to the app's settings and try wiping its data completely. Then reboot your phone and try again.
DJBhardwaj said:
No, it will not destroy the warranty at all. As for the camera app, go to the app's settings and try wiping its data completely. Then reboot your phone and try again.
Click to expand...
Click to collapse
Well, that didn't do the trick, but I just simply clicked 'disable' after wiping the data and it gave me a message of "uninstalling app and installing factory camera app" which worked beautifully.
Now everything's working fine.
1. *#*#874#*#* is this make my phone rooted ?
because when i type it on my phone, it give message such install, chance data erased, and the last is root
"Would you like to install the following system software?
System upgrade to 330B.B01
You will be unable to use your device or make emergency calls during the upgrade.
It will lead to unexpected result if you cut off power or remove downloaded file while updating software.
There is small possibility of erasing user data caused by upgrade purpose. If need, please backup your data before installing system upgrade.
The normal update can not be guaranteed after the device is rooted. If root contributes to abnormal use on the device in update process, the user should be responsible for it oneself"
2. my type is TA-1116 with build number 00WW_2_50A_SP01, after updating using this method, will it change to another model and build number or not ?
3. is the link that has been shared is the latest update that rolled to some user on 31 October 2018 ?
thank's for sharing the file, and kindly reply to my question
snowdance said:
1. *#*#874#*#* is this make my phone rooted ?
because when i type it on my phone, it give message such install, chance data erased, and the last is root
"Would you like to install the following system software?
System upgrade to 330B.B01
You will be unable to use your device or make emergency calls during the upgrade.
It will lead to unexpected result if you cut off power or remove downloaded file while updating software.
There is small possibility of erasing user data caused by upgrade purpose. If need, please backup your data before installing system upgrade.
The normal update can not be guaranteed after the device is rooted. If root contributes to abnormal use on the device in update process, the user should be responsible for it oneself"
2. my type is TA-1116 with build number 00WW_2_50A_SP01, after updating using this method, will it change to another model and build number or not ?
3. is the link that has been shared is the latest update that rolled to some user on 31 October 2018 ?
thank's for sharing the file, and kindly reply to my question
Click to expand...
Click to collapse
1. Your phone won't be rooted
2. Your phone model won't change but build number, of course, will be changed due to system update.
3. Yes, yes it is.
hoatongoc said:
1. Your phone won't be rooted
2. Your phone model won't change but build number, of course, will be changed due to system update.
3. Yes, yes it is.
Click to expand...
Click to collapse
already installed it last night, and it work's !
thank's for the reply
Will I still receive OTA updates by HMD for my device when I check for it?
xoxoJoelxoxo said:
Will I still receive OTA updates by HMD for my device when I check for it?
Click to expand...
Click to collapse
you will, i already ask it with the support center from my country in indonesia
Hy guys,
i have miui 12.5.5.0 RKIEUXM on mi11 lite 5g but when i search new versions it says there is no update for the phone. So i tried to download the V13.0.4.0.SKIEUXM from official site in order to install it manually. I go in the settings to choose the package to install the update but it can't verify the package and it can't update the phone.
I'm stucked with the 12.5.5.0!!!
What can i do?
or stay on 12.5.5..or flash with fastboot...
Not sure what official site you're referring to but I have used the following without issue. Double check the file sizes/MD5s are the same in case your original download was cut short or something.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
If still not working, it's possible it may require you to have the previous update installed before it will allow the newest. Try installing 12.5.7 first - and if it doesn't allow that then 12.5.6...
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
One issue I've personally encountered is that the update dialogue stops showing the option to install from local package. If you see this then select the updater settings from the Recents and clear data then try again.
sn0uts said:
Not sure what official site you're referring to but I have used the following without issue. Double check the file sizes/MD5s are the same in case your original download was cut short or something.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
If still not working, it's possible it may require you to have the previous update installed before it will allow the newest. Try installing 12.5.7 first - and if it doesn't allow that then 12.5.6...
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
One issue I've personally encountered is that the update dialogue stops showing the option to install from local package. If you see this then select the updater settings from the Recents and clear data then try again.
Click to expand...
Click to collapse
Thanks sn0uts, 2 days ago i did exactly as you explained: choosing that web site and starting to manually updating into 12.5.6, 12.5.7 and then 13.0.4.
Now the phone is up to date, i still don't know why i've encountered this problem but i have a solution also for future.
sn0uts said:
Not sure what official site you're referring to but I have used the following without issue. Double check the file sizes/MD5s are the same in case your original download was cut short or something.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
If still not working, it's possible it may require you to have the previous update installed before it will allow the newest. Try installing 12.5.7 first - and if it doesn't allow that then 12.5.6...
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
One issue I've personally encountered is that the update dialogue stops showing the option to install from local package. If you see this then select the updater settings from the Recents and clear data then try again.
Click to expand...
Click to collapse
Actually, with the app:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
searching through Xiaomi Firmware Updater is easier. The app checks your phone model, your current firmware and points you directly to download your OTA from Xiaomi Firmware Updater.
If you don't want the offered OTA, you can search for the other suitable firmwares for your phone
Even more, it shows you Xiaomi.eu Weekly and Stable ROMs, and TWRP (if applicable)
You can also manually change the phone model and search for another Xiaomi phone
Anyway, it makes searching easier and error-free (newbie, by looking at Xiaomi Firmware Updater, may easily pick a wrong firmware, resulting by bricking his phone)
zgfg said:
Actually, with the app:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
searching through Xiaomi Firmware Updater is easier. The app checks your phone model, your current firmware and points you directly to download your OTA from Xiaomi Firmware Updater.
If you don't want the offered OTA, you can search for the other suitable firmwares for your phone
Even more, it shows you Xiaomi.eu Weekly and Stable ROMs, and TWRP (if applicable)
You can also manually change the phone model and search for another Xiaomi phone
Anyway, it makes searching easier and error-free (newbie, by looking at Xiaomi Firmware Updater, may easily pick a wrong firmware, resulting by bricking his phone)
Click to expand...
Click to collapse
It does look very useful. However if I wasn't reading a recommendation on XDA and only saw it in the Play Store I might not trust an app with this from the look of it. If it's trustworthy then great.
sn0uts said:
It does look very useful. However if I wasn't reading a recommendation on XDA and only saw it in the Play Store I might not trust an app with this from the look of it. If it's trustworthy then great.
Click to expand...
Click to collapse
Actually, they have a useful TG news. Too many things, not everything for everybody but eg, useful info about roadmaps which phones will receive further updates to newer MIUI and Android versions, new phones, new ear buds, etc
If using Xiaomi.eu ROMs, you will usually see a (correct!) changelog for the upcoming weekly an hour or more earlier than posted to Xiaomi.eu forum
nikorzi said:
Hy guys,
i have miui 12.5.5.0 RKIEUXM on mi11 lite 5g but when i search new versions it says there is no update for the phone. So i tried to download the V13.0.4.0.SKIEUXM from official site in order to install it manually. I go in the settings to choose the package to install the update but it can't verify the package and it can't update the phone.
I'm stucked with the 12.5.5.0!!!
What can i do?
Click to expand...
Click to collapse
I had the same problem and FINALLY I CAME UP WITH A SOLUTION. so... I've downloaded the ROM for V12.5.7.0 and installed it through the Updater app on the phone. After that, you can download the V13.0.4.0 and install it as normal.
I made an account just to help you guys because I was really annoyed that I couldn't update and probably you feel the same way.
Good luck and enjoy your mi11 lite
P.S. my battery went ****ty on the V12.5.5.0, idk about you but I had to recharge it often...hopefully it's not a hardware problem...
SuperGeo9 said:
I had the same problem and FINALLY I CAME UP WITH A SOLUTION. so... I've downloaded the ROM for V12.5.7.0 and installed it through the Updater app on the phone. After that, you can download the V13.0.4.0 and install it as normal.
I made an account just to help you guys because I was really annoyed that I couldn't update and probably you feel the same way.
Good luck and enjoy your mi11 lite
P.S. my battery went ****ty on the V12.5.5.0, idk about you but I had to recharge it often...hopefully it's not a hardware problem...
Click to expand...
Click to collapse
What exactly do you mean by "Updater app on the phone"? I am stuck on 12.5.5.0 as well and idk what to do with it. I assume the rom you've downloaded was from MIUI Updates Tracker topic on this board? If so, which one, the Fastboot or the Recovery?
Nevermind, figured it out. Downloaded "MIUI Downloader" app from Google Play, downloaded 1 version higher than ive had. Then, I went to settings -> About phone, clicked version, clicked a few times version logo and additional settings have been enabled. Then Ive clicked the button in top right corner and selected downloaded package. The phone accepted it and installed it. Then I've proceeded with other higher versions.
hehebuhehe said:
What exactly do you mean by "Updater app on the phone"? I am stuck on 12.5.5.0 as well and idk what to do with it. I assume the rom you've downloaded was from MIUI Updates Tracker topic on this board? If so, which one, the Fastboot or the Recovery?
Nevermind, figured it out. Downloaded "MIUI Downloader" app from Google Play, downloaded 1 version higher than ive had. Then, I went to settings -> About phone, clicked version, clicked a few times version logo and additional settings have been enabled. Then Ive clicked the button in top right corner and selected downloaded package. The phone accepted it and installed it. Then I've proceeded with other higher versions.
Click to expand...
Click to collapse
Sorry for the late reply. My solution was slightly different.
I downloaded the recovery rom (so you can install it from the phone) from a website with original miui roms, placed it in the internal storage, created a folder "downloaded_rom" and then I did exactly like you (settings>about phone>clicked the 3 dots>choose update package).
After that I downloaded the latest rom from c.mi.com and that was it.
I noticed that my problem with the battery was caused by the 12.5.5 rom. Now it's good as new.
I'm glad my post helped you and hopefully will help others as well. Take care!
My phone (bought in germany, EEA-rom) was stuck at "V12.5.6.0.RKIEUXM Enhanced" since the only update I received shortly after bying in December 2021. I could resolve the issue as follows:
In the update tracker thread I verified my build version which was EEA (European) in my case. First I tried to download and install v13.0.4 directly which failed (cannot verify stable update bla bla bla). Then I tried to download and install the version that was closest to mine -> V12.5.7.0.RKIEUXM which I successfully could flash. Directly after booting into 12.5.7 I was offered another update to v13.0.4.
Did anyone have similar issues: phone would not update to latest available version? What could be the reason? Regions and Update schedules? But were now in april 2022 and my phone was still not showing any updates.
I am in Australia and have downloaded the latest firmware for the phone, Renoir, but I can't update it because the option to "choose update package" isn't available on my phone...
I downloaded the update as I am getting the problem of not being able to download the package via my phone...keep getting the error that "something went wrong. Wait a minute or two and try again". This is frustrating
I discovered the fix to my problem... If you can't see the option of selecting a package to update under the 3 dots, click on MIUI logo in the updater several times till you see a message that tells you more features have been enabled.
cheers
col
Didn't read the whole discussion but noticed fastboot and xiaomi.eu options...those are the best IMHO.
xiaomi.eu updates renoir (weekly or stable) with fastboot option / scripts.
There are also fastboot recoveries (not the same as xiaomi.eu fastboot ROMs, but in case something goes wrong this can help out of bad situation) and regular update ROMs on MIUI tracker just make sure to pick the correct phone/ROM version: https://xiaomifirmwareupdater.com/miui/
Since a lot of people is asking for firmware files, OTAs, boot.img, I decided to collect all the resources here, so that it would be easier to get what you need.
First of all, you have to identify your ROM version. It is not the scope of this post to teach you how to use adb, so I suppose you already know.
Run adb shell getprop ro.build.oplus_nv_id and check the result with the table at the end of the post to know if you have the export or GDPR ROM.
Full (EDL mode) firmware downloads:This is the firmware you can also find on realmefirmware.com, but the website doesn't have all the versions.
Unfortunately, not all versions are available on the Realme servers, so if a firmware is not listed here, it's not available.
export firmware downloads:Android 12:RMX3301export_11_A.06_2022020500280000.zip
RMX3301export_11_A.08_2022022300070395.zip
RMX3301export_11_A.10_2022031419130229.zip
RMX3301export_11_A.11_2022031821250000.zip
RMX3301export_11_A.13_2022040705040000.zip
RMX3301export_11_A.14_2022041311050164.zip
RMX3301export_11_A.15_2022042701280000.7z
RMX3301export_11_A.16_2022052418230167.7z
RMX3301export_11_A.17_2022062222270183.7z
RMX3301export_11_A.18_2022072511110152.zip
RMX3301export_11_A.19_2022082205500000.zip
RMX3301export_11_A.21_2022092223350165.zip
Android 13:RMX3301export_11_C.08_2022102215440135.zip
RMX3301export_11_C.12_2022121600040215.zip
RMX3301export_11_C.13_2023010918370148.zip
RMX3301export_11_C.16_2023031621430000.zip
Android 13 (ColorOS 13.1):RMX3301export_11_C.18_2023050511080109.zip
RMX3301export_11_C.19_2023052220180130.zip
GDPR firmware downloads:Android 12:RMX3301GDPR_11_A.06_2022021320090088.zip
RMX3301GDPR_11_A.07_2022021800320350.zip
RMX3301GDPR_11_A.09_2022030402540000.zip
RMX3301GDPR_11_A.10_2022031818500135.zip
RMX3301GDPR_11_A.14_2022041414290143.zip
RMX3301GDPR_11_A.17_2022062222280000.7z
RMX3301GDPR_11_A.18_2022072511120000.zip
RMX3301GDPR_11_A.19_2022082205510000.zip
RMX3301GDPR_11_A.21_2022092223360000.zip
Android 13:RMX3301GDPR_11_C.08_2022102215410137.zip
RMX3301GDPR_11_C.12_2022121600050000.zip
RMX3301GDPR_11_C.13_2023010918380000.zip
RMX3301GDPR_11_C.16_2023031621420140.zip
Android 13 (ColorOS 13.1):RMX3301GDPR_11_C.18_2023050510510127.zip
RMX3301GDPR_11_C.19_2023052220190000.zip
Full OTA firmware downloads:You can install this directly from your phone, but it is specific for your nv_id, so if you can't find your ID here, use the full firmware if available or read below to get the URL by yourself.
India (IN) firmware downloads (nv_id = 00011011):Android 12:RMX3301_11.A.14_0140_202204131105: RMX3301_ROLL_BACK_Android12_IN.zip (Can be used to roll back from any future version)
RMX3301_11.A.15_0150_202204270128: 2620c0ef8b8d4057a77b7f114f18f1b9.zip
RMX3301_11.A.16_0160_202205241823: 9d61d0852808452091f4a552997a63ed.zip
RMX3301_11.A.17_0170_202206222227: a4b475a3f4b54619adfbcd36ca4282cd.zip
RMX3301_11.A.18_0180_202207251111: 24968044538344fbb0d34fbd21858e09.zip
RMX3301_11.A.19_0190_202208220550: 57fea9b57d4e4880b7ffb336bcd0d3ed.zip
RMX3301_11.A.21_0210_202209222335: 8b0fb5198b894a218d55d423355bd13e.zip
Android 13 Beta:RMX3301_11.C.01_1010_202205071838: RMX3301_11_C.01_Update_Android13_IN.zip (Android 13 DP1)
RMX3301_11.C.02_1020_202208152015: 3b232a024abc4168a24a0a7e4e24c879.zip (Official Trial Program)
RMX3301_11.C.05_1050_202209011105: 94662e8d4288490394eb240dd040f434.zip (Official Trial Program)
RMX3301_11.C.06_1060_202209192326: 0836f0a8968f4e10bc2dd123615a78b7.zip (Open Beta Program)
Android 13:RMX3301_11.C.08_1080_202210221544: 4ccc3d3cb837437ea787baaac853fc4d.zip
RMX3301_11.C.11_1110_202212121458: cdddcd5ba2c24a88bf8bf12ecb1b848c.zip
RMX3301_11.C.12_1120_202212160004: 2d60293ecc02486db514639c4493e73d.zip
RMX3301_11.C.13_1130_202301091837: bb2e8a1445c742e582a528399eb6d4e3.zip
RMX3301_11.C.16_1160_202303162143: 0389f0251b6243d99a8a23774df59022.zip
RMX3301_11.C.16_1160_202303162143: RMX3301_ROLL_BACK_Android13_IN.zip (Can be used to roll back from any future version)
Android 13 (ColorOS 13.1):RMX3301_11.C.18_1180_202305051108: b741fb43f5a94ffa981f440453ce5e8e.zip
RMX3301_11.C.19_1190_202305222018: 0d8de9b09a2e457a92726bdbcb8390ed.zip
RMX3301_11.C.20_1200_202306191319: 3fd59892f871401f9a4395994ebf6d47.zip
Android 14:RMX3301_11.F.01_3010_202304262041: RMX3301_11_F_OTA_3010_all_M5Kvg6_00011011.zip (Android 14 DP1)
Europe (EUEX) firmware downloads (nv_id = 01000100):Android 12:RMX3301_11.A.14_0140_202204141429: RMX3301_ROLL_BACK_Android12_EU.zip (Can be used to roll back from any future version)
RMX3301_11.A.15_0150_202204270129: 72db4088a1f34478bdc177d850ce3144.zip
RMX3301_11.A.16_0160_202205241824: 2f2b32b599734ca1975f8b95deb3dd0a.zip
RMX3301_11.A.17_0170_202206222228: c1db6ff9301c4de09773f1e1add9bd9d.zip
RMX3301_11.A.18_0180_202207251112: c97759dd1029491cae944ff1fadf8853.zip
RMX3301_11.A.19_0190_202208220551: beac418fbda441a786e58892b10f9538.zip
RMX3301_11.A.21_0210_202209222336: 1c78489d1868491c9e4c5d54369c7d8e.zip
Android 13 Beta:RMX3301_11.C.01_1010_202205071837: RMX3301_11_C.01_Update_Android13_EU.zip (Android 13 DP1)
RMX3301_11.C.02_1020_202206061202: RMX3301_11_C.02_Update_Android13_EU.zip (Android 13 DP2)
Android 13:RMX3301_11.C.08_1080_202210221541: 336d3d23e61d4839a2fdd21c8b9d56d7.zip
RMX3301_11.C.11_1110_202212121459: 7449aed556e444d3b369ef3458f95c1c.zip
RMX3301_11.C.12_1120_202212160005: 685a18388d0047a59c5d16fa16aa2ea5.zip
RMX3301_11.C.13_1130_202301091838: f3c7c3df25ce460399c7c47c608bf8c6.zip
RMX3301_11.C.16_1160_202303162142: 4fceb2d35bb9483ebc73043e00f90dad.zip
Android 13 (ColorOS 13.1):RMX3301_11.C.18_1180_202305051051: 5feda6c46e9649acb610be202d7869ab.zip
RMX3301_11.C.19_1190_202305222019: d3e80c6c535f427fa2e74ab2d31893c7.zip
How to get the latest OTA URL by yourself:You can use realme-ota to get the latest OTA for another nv_id or the ones above if I haven't updated this topic yet after a new update is released. Just keep in mind that, if the rollout is still ongoing, you may still get the previous version. Just wait a few days and try again.
For example, to get the latest TW OTA (nv_id = 00011010), run
Code:
realme-ota -r 0 RMX3301 RMX3301_11.A.00_0000_000000000000 3 00011010
You will find the URL near the top of the response.
How to extract images from EDL firmware package:
Extract the zip or 7z file
Use mct_ofp_extractor or oppo_decrypt to extract the OFP file
If you need to get super.img, open super_map.csv and take note of the files you have to merge for your nv_id
Use simg2img to merge your files like this (search online for the simg2img binary if you're on Windows):
Code:
simg2img super.0.xxxxxxxx.img super.1.xxxxxxxx.img super.2.xxxxxxxx.img super.img
If you need to extract super.img too, use lpunpack (please search online for the download and how to use it)
How to extract images from OTA zip files:
Extract the OTA zip file
Download and extract payload-dumper-go
Drag and drop payload.bin on payload-dumper-go executable
NV IDs table (needs confirmation):
RegionRegion abbreviationnv_id (HEX)nv_id (BIN)ROM typeNotesTaiwanTW1A00011010exportIndiaIN1B00011011exportIndonesiaID3300110011exportRussiaRU3700110111exportMalaysiaMY3800111000exportThailandTH3900111001exportPhilippinesPH3E00111110exportSaudi ArabiaSA8310000011exportLatin AmericaLATAM9A10011010exportBrazilBR9E10011110exportMiddle East and AfricaMEAA610100110exportEurope (EU, EEA, UK and Switzerland)EUEX4401000100GDPRUnited KingdomGB8A10001010GDPR1TurkeyTR5101010001GDPRRest of EuropeEU-NONEEA-Double8D10001101GDPRChinaALLNET9710010111domestic
Notes:
Only found in build C.08 through C.16 inclusive; identical to the EUEX one, but with the potential to differentiate some partitions.
very nice, l'm downloading. but...how did you find them? there are some special sites
Rapper_skull said:
Since a lot of people is asking for firmware files, OTAs, boot.img, I decided to collect all the resources here, so that it would be easier to get what you need.
First of all, you have to identify your ROM version. It is not the scope of this post to teach you how to use adb, so I suppose you already know.
Run adb shell getprop ro.build.oplus_nv_id and take note of the result.
If the result is 01000100, 01010001 or 10001101, you have the GDPR ROM installed, otherwise you have the export one.
Full (EDL mode) firmware downloads:This is the firmware you can also find on realmefirmware.com, but the website doesn't have all the versions.
Unfortunately, not all versions are available on the Realme servers, so if a firmware is not listed here, it's not available.
export firmware downloads:RMX3301export_11_A.06_2022020500280000.zip
RMX3301export_11_A.08_2022022300070395.zip
RMX3301export_11_A.10_2022031419130229.zip
RMX3301export_11_A.11_2022031821250000.zip
RMX3301export_11_A.13_2022040705040000.zip
RMX3301export_11_A.14_2022041311050164.zip
RMX3301export_11_A.15_2022042701280000.7z
RMX3301export_11_A.16_2022052418230167.7z
RMX3301export_11_A.17_2022062222270183.7z
GDPR firmware downloads:
RMX3301GDPR_11_A.06_2022021320090088.zip
RMX3301GDPR_11_A.07_2022021800320350.zip
RMX3301GDPR_11_A.09_2022030402540000.zip
RMX3301GDPR_11_A.10_2022031818500135.zip
RMX3301GDPR_11_A.14_2022041414290143.zip
RMX3301GDPR_11_A.17_2022062222280000.7z
Full OTA firmware downloads:You can install this directly from your phone, but it is specific for your nv_id, so if you can't find your ID here, use the full firmware if available.
India (IN) firmware downloads (nv_id = 00011011):RMX3301_11.A.14_0140_202204131105: RMX3301_ROLL_BACK_Android12_IN.zip (You can use this package to roll back from any future version)
RMX3301_11.A.15_0150_202204270128: 2620c0ef8b8d4057a77b7f114f18f1b9.zip
RMX3301_11.A.17_0170_202206222227: a4b475a3f4b54619adfbcd36ca4282cd.zip
RMX3301_11.A.18_0180_202207251111: 24968044538344fbb0d34fbd21858e09.zip
RMX3301_11.C.01_1010_202205071838: RMX3301_11_C.01_Update_Android13_IN.zip (Android 13 DP1)
Europe (EUEX) firmware downloads (nv_id = 01000100):RMX3301_11.A.14_0140_202204141429: RMX3301_ROLL_BACK_Android12_EU.zip (You can use this package to roll back from any future version)
RMX3301_11.A.15_0150_202204270129: 72db4088a1f34478bdc177d850ce3144.zip
RMX3301_11.A.16_0160_202205241824: 2f2b32b599734ca1975f8b95deb3dd0a.zip
RMX3301_11.A.17_0170_202206222228: c1db6ff9301c4de09773f1e1add9bd9d.zip
RMX3301_11_A.18_0180_202207251112: c97759dd1029491cae944ff1fadf8853.zip
RMX3301_11.C.01_1010_202205071837: RMX3301_11_C.01_Update_Android13_EU.zip (Android 13 DP1)
RMX3301_11.C.02_1020_202206061202: RMX3301_11_C.02_Update_Android13_EU.zip (Android 13 DP2)
Click to expand...
Click to collapse
i finished downloading the complete rom.
I put payload.bin in input in payload_dumper, but in output it only picks me up:
hyp.img
my_manifest.img
xbl_ramdump.img
to fetch the boot?
sorry i'm bothering you so much, but i'm stuck here
marco.chinagliaxx91 said:
i finished downloading the complete rom.
I put payload.bin in input in payload_dumper, but in output it only picks me up:
hyp.img
my_manifest.img
xbl_ramdump.img
to fetch the boot?
sorry i'm bothering you so much, but i'm stuck here
Click to expand...
Click to collapse
I updated the post with the payload dumper I use. Please try it.
Rapper_skull said:
I updated the post with the payload dumper I use. Please try it.
Click to expand...
Click to collapse
when i downloaded the rom, a18 in the phone settings with a file manager i was able to download ota, but i had the same problem that i described above. I didn't know you had to use payload - go. You saved my life man. Now I know how. I promise that with each update I will post the updated files.
Excellent thread. Include Export firmware OTA also if possible
shivrajsingh said:
Excellent thread. Include Export firmware OTA also if possible
Click to expand...
Click to collapse
OTAs are not divided in export and GDPR, but by nv_id. There are OTA links for India in the post, and that's one of the many export nv_ids. Unfortunately, I can not keep track of every nv_id, because there are too many.
Rapper_skull said:
OTAs are not divided in export and GDPR, but by nv_id. There are OTA links for India in the post, and that's one of the many export nv_ids. Unfortunately, I can not keep track of every nv_id, because there are too many.
Click to expand...
Click to collapse
if you want we can do that at each update I take care of the EU.
I create a folder on mega sorted.
Each folder will have the name of the firmware, in it I will put that firmware
boot_stock.img
vbmeta.img
magisk.img
and two bat files
stock_boot.bat
magisk_boot.bat
that I created, just run it to give root permissions or restore the original boot. Whether the phone is on or in fastboot it will be the same. In the bat I have thought of everything. A little thank you here
marco.chinagliaxx91 said:
if you want we can do that at each update I take care of the EU.
I create a folder on mega sorted.
Each folder will have the name of the firmware, in it I will put that firmware
boot_stock.img
vbmeta.img
magisk.img
and two bat files
stock_boot.bat
magisk_boot.bat
that I created, just run it to give root permissions or restore the original boot. Whether the phone is on or in fastboot it will be the same. In the bat I have thought of everything. A little thank you here
Click to expand...
Click to collapse
All users who flashed from China Rom to Global Rom have that particular Export version. They are mostly rooted and get OTA late. So ota link may be beneficial for them.
How to check NV ID?
shivrajsingh said:
All users who flashed from China Rom to Global Rom have that particular Export version. They are mostly rooted and get OTA late. So ota link may be beneficial for them.
How to check NV ID?
Click to expand...
Click to collapse
not so answer you. I have eu firmware
I'm marco.chinagliaxx91. This Is my real account. Now i can use a gt2pro
shivrajsingh said:
All users who flashed from China Rom to Global Rom have that particular Export version. They are mostly rooted and get OTA late. So ota link may be beneficial for them.
How to check NV ID?
Click to expand...
Click to collapse
getprop ro.build.oplus_nv_id
Rapper_skull said:
getprop ro.build.oplus_nv_id
Click to expand...
Click to collapse
Its 00011010
shivrajsingh said:
Its 00011010
Click to expand...
Click to collapse
That is the TW (Taiwan) ROM. I suggest migrating to the IN ROM, since it is also the default region. In any case, I updated the first post with instructions on how to get the latest OTA URL by yourself.
Maybe in the future I will write a script to get all the URLs automatically.
I get 10100110. Does this mean I have the IN version?
when I try realme-ota -r 0 RMX3301 RMX3301_11.A.00_0000_000000000000 3 10100110 it gives me a few lines:
Load payload for RMX3301 (RealmeUI V3)
Wait for the endpoint to reply
Response status mismatch, expected '200' got '500'!
I am trying to get the firmware for my phone because ever since I took the A.18 update my phones Widevine was downgraded to L3. I am hoping A18 just messed something up in update process and flashing the A17 stock rom then rerooting will fix it.
GIutton said:
I am trying to get the firmware for my phone because ever since I took the A.18 update my phones Widevine was downgraded to L3. I am hoping I just messed something up in update process and flashing the stock rom then rerooting will fix it.
Click to expand...
Click to collapse
Widewine degrades to L3 by flashing Global and there is no official fix.
EDIT: Typo, degrades to L3, not L1
Quake94 said:
Widewine degrades to L1 by flashing Global and there is no official fix.
Click to expand...
Click to collapse
But I have never flashed any roms to the phone. Have rooted with magisk and only ever used the stock OTA updates from "about phone"
GIutton said:
But I have never flashed any roms to the phone. Have rooted with magisk and only ever used the stock OTA updates from "about phone"
Click to expand...
Click to collapse
After unlocking bootloader, how did you root your phone? Did you flash a patched boot.img over the stock ROM?
No I booted the phone with a magisk patched boot.img then did a direct install using the magisk app on stock A.17. I had wideine L1 until I took the A.18 official OTA for my phone then it went to L3. It was an incremental update. To go from A.17 to A.18 I used magisk > uninstall magisk > restore images. Then downloaded and installed the OTA, took a copy of the boot.img from the inactive slot and patched it with magisk and copied to PC. Then I restored root with magisk direct install, turned on airplane mode, rebooted the phone from the System Update Dialog "install" then rebooted to bootloader and used fastboot boot magisk-patched-boot.img and then used magisk to do a direct install to make root permanent.
I had to unroot the phone and relock the bootloader in order to get back to Widevine L1. Maybe I am just wrong and it went to L3 right after I unlocked the bootloader. Has anyone been able to keep Widevine L1 with an unlocked bootloader and Magisk rooted?