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/
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
Here's the full description of my problem.
I wanted to install a custom ROM, so I applied for permission to unlock. I obtained the permission about a month ago, and then the problems began.
First off, I'm not able to bind my account to my device under developer options. It shows error 80612 and some Chinese characters. When I try to unlock, it stops at 99%and says the account is not bound to device. I tried all the solutions listed on mi forums, but to no avail. The only solution left was to install developer ROM and try from there
Here comes the second problem. When I try to install it from updater app, it says I'm only allowed to install stable versions. So I tried to install via recovery. When I boot into recovery, just shows an image of phone and asks me to connect to PC suite. No options are shown, no way to navigate. I can only reboot by pressing power button. So I tried installing PC suite and connecting my phone, but the software refuses to recognise my phone, either says to connect phone via USB(which I did) or tells me to update phone to use suite (phone is on latest stable version)
This is like a roadblock to me. These many problems should not be existing in a ROM, especially when they claim to be developer friendly. It's almost like Xiaomi doesn't want people to unlock their phones. Please someone help me with this. Pics will be provided as requested.
Edit: I tired installing older versions of developer and even tried downgrading the stable version via updater app, but failed, showing error that i can't install anything other than stable and that i can't install older versions respectively
Bro firstly you have to install the developer ROM and yeah it shows the error that you can only install stable ROM
Solution = just download the oldest available developer ROM and then download the newest developer ROM
Flash the oldest zip first with the updater app the developer ROM will get flashed, boot it up but don't set it up completely. After you're in the system again go to the updater app then flash the newest developer ROM
Once all this is done setup all the necessary info on the newest beta build
Go to the MIUI forums , fill up all your info, next go to the MIUI forums on your windows PC and check that if all the info as you filled up in your device is there or not, if it's there then you're on the right track
Next check is the MI cloud services are activated or not, if they are active then go to MI cloud on your PC and just click on find device, if it exactly locates your device then you're all done.
The MIUI forums play a major role in unlocking the bootloader so make sure all your info is there and you browse then for quite a while.
Then just try to unlock your bootloader it'll surely work. ?
Attempting right away
Still the same error
You did all of the things that I wrote right
Got stopped at flashing the oldest developer ROM. It still shows the error that I can't install anything other than stable versions
Blocked at first step itself. Can't flash the older ROM too via updater app. Still shows the error that i can't install anything other than newer stable versions
You tried the oldest available global developer ROM right ?
Yes. I even tried downgrading the stable version. Even that didn't work
Bro try this - Update to the latest global stable ROM then test flashing the oldest global developer ROM . I hope it works for ya
That's what I did in the first step. I'm on the latest global stable. After your suggestion, I tired installing the oldest global developer. Same error
Ok I'll see what I can do to help you now cause your problem is getting pretty strange. ?
I received this notification thousands time
But when i open system update its said im using latest update. But its not this version in about phone!
Go on system update, Press 10 times on the big 10 (I made like this) and flash the official downloadable rom from Xiaomi forum Site. You Can find "select an update package" on the top right menù.
LineageOS 16 without fingerprint.
You can build lineage for equuleus now.
Only fingerprint dosn't work.
Before start i'd like to tell you about my adveture with my phone
I had a Huawei mate 10 ( ALP-L29 c185) installed 8.0.0.139, rooted with magisk and TWRP (By Pretoriano80) as recovery so yesterday i suddenly think that "i shuld try android 9" (i don't know why?) . I searched here and internet so finally i decided to update by "hurupdater" method. I downloaded stock firmware by "Firmware Finder for Huawei" app (9.0.0.177) and hurupdater 0.4 also twrp_bla_alp_0.7.img for twrp recovery. I put them in same folder on sdcard. Renamed recovery.img to keep recovery as twrp. Lastly i restarted recovery and installed hurupdater.zip.
DANG!!! My phone is bricked....... It gave a lot of errors during installation and when i try to reboot it was bootlooping, cant load recovery interface (twrp or stock). I could enter e-recovery but gives "getting package info failed" error. So ended up with bricked phone in my hands. I tried many ways including hisuite but nada....
Then i remembered "Funky Huawei", bought 1 credit and followed instructions. After long hellish hours (firmware downloading takes long) i have my phone back working with stock 8.0.0.140 rom, stock recovery even relocked bootloader also my whole data was intact. My curosity cost me 20 $ and hours. This morning i realised there is system update 9.0.0.159
So my questions o this point
1)What should i do now? Update to android pie (with stcock recovery of course)? Is it worth trying or just install twrp and root my current rom and go on my way for a while longer ? (till a more stable pie relase)
2) For the future, what was wrong in my update process. I'd never want to make same mistake again..
Thanks...
draqkin said:
Before start i'd like to tell you about my adveture with my phone
I had a Huawei mate 10 ( ALP-L29 c185) installed 8.0.0.139, rooted with magisk and TWRP (By Pretoriano80) as recovery so yesterday i suddenly think that "i shuld try android 9" (i don't know why?) . I searched here and internet so finally i decided to update by "hurupdater" method. I downloaded stock firmware by "Firmware Finder for Huawei" app (9.0.0.177) and hurupdater 0.4 also twrp_bla_alp_0.7.img for twrp recovery. I put them in same folder on sdcard. Renamed recovery.img to keep recovery as twrp. Lastly i restarted recovery and installed hurupdater.zip.
DANG!!! My phone is bricked....... It gave a lot of errors during installation and when i try to reboot it was bootlooping, cant load recovery interface (twrp or stock). I could enter e-recovery but gives "getting package info failed" error. So ended up with bricked phone in my hands. I tried many ways including hisuite but nada....
Then i remembered "Funky Huawei", bought 1 credit and followed instructions. After long hellish hours (firmware downloading takes long) i have my phone back working with stock 8.0.0.140 rom, stock recovery even relocked bootloader also my whole data was intact. My curosity cost me 20 $ and hours. This morning i realised there is system update 9.0.0.159
So my questions o this point
1)What should i do now? Update to android pie (with stcock recovery of course)? Is it worth trying or just install twrp and root my current rom and go on my way for a while longer ? (till a more stable pie relase)
2) For the future, what was wrong in my update process. I'd never want to make same mistake again..
Thanks...
Click to expand...
Click to collapse
I have exactly same phone (c185) never tried unlocking bootloader but I updated to emui 9 159 there are some buggy things like when you want to use third party lunchers You can't use gesture navigation and it has so many bugs so not using gesture is better
there are again some problems with third party launchers (im using nova) like sometimes when you go to "resents" its totally blank and you have to force stop "huawei home" to make it right
there are some good changes in camera like new 960 fps slow motion (but there is a huge crop in 240fps 720p and 960fps 720p I can't remember that 240fps had that crop or not) Turning off master ai and some new scene detection but it's slower than last one
there is a new performance mode that i love using it (it feels like a real flagship however it's not because of stupid SOC)
there is a new AI api that android 8 didn't have so most of apps wasn't able to use NPU
in emui 8 there is a little bit better battery
I love changes to my phone so I preferred buggy new firmware to old ones there are so many good little changes in interface (like when you take a picture you can go to gallery then scan it for QR code)
There is a way better Mira cast functionality (and new desktop mode in it)
hi touch, hi vision
These were all expensives I had with emui 9 that I can think of
How did you update @arianamirgholami ?
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
curgervending said:
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
Click to expand...
Click to collapse
Same here, although my brother and I have the same device (ALP-L29C185) and we're on the same career, he got the pie update like a month ago and nothing for me yet. I think it's a matter of time until our imeis turns.
MasterThiefGarrett said:
How did you update @arianamirgholami ?
Click to expand...
Click to collapse
I used Erecovery of firmware finder
curgervending said:
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
Click to expand...
Click to collapse
Yes I saw many people on internet facing same issue, What I assume is that when you purchased the phone it came with 8.0.0.141, that's why its not getting the Pie. Because the phones which were using 8.0.0.140 already got the Pie instead of 8.0.0.141. So one thing you can try is to go back to 8.0.0.140 and then update the phone. I did the same, Installed 8.0.0.140 using HiSuite and then update to Pie.
Fazee99 said:
Yes I saw many people on internet facing same issue, What I assume is that when you purchased the phone it came with 8.0.0.141, that's why its not getting the Pie. Because the phones which were using 8.0.0.140 already got the Pie instead of 8.0.0.141. So one thing you can try is to go back to 8.0.0.140 and then update the phone. I did the same, Installed 8.0.0.140 using HiSuite and then update to Pie.
Click to expand...
Click to collapse
I finally got the OTA update from EMUI 8 to EMUI 9
curgervending said:
I finally got the OTA update from EMUI 8 to EMUI 9
Click to expand...
Click to collapse
Thats great. Means you got more luck. Mine is still on 9.0.0.159 and no update. Please also confirm one thing. What is android security patch in this version?
Finally grab the update today morning...
Another update today. Woww
Considering this guide was written before the Mi 9T Pro was released, it's time to rewrite it and make it more relevant.
THE BASICS
GETTING PREPARED
-----------------------------------
If you want to tinker with your phone then you'll need some ground work.
If you don't yet have a Mi account, go to https://account.xiaomi.com/pass/register and create a new account. It is important, when unlocking the bootloader, to have your correct phone number registered on your account, so either choose to create the account using a phone number or add the phone number in the security settings of your Mi account afterwards. Make sure the number is verified by the OTP that will be sent.
Make sure you have adb and fastboot tools installed on your PC. These are part of the Android development tools. You can either install the official Android SDK Platform Tools which can be found here https://developer.android.com/studio/releases/platform-tools
Or you can install only adb and fastboot from this xda members project, called minimal adb and fastboot. https://forum.xda-developers.com/showthread.php?t=2317790&p=42407269
If you want to know more about these tools then read the minimal adb and fastboot post, you'll find a couple of links that explain both tools in detail.
Install the Mi Unlock Tool. You can find this in the guide I've linked to in the bootloader unlock section below.
Install the Mi Flash Tool. This can be found in the guide I've linked to in the MIUI fastboot flashing section.
Install the drivers for the phone. This is done automatically the first time you connect the phone to PC, so go ahead and connect your phone to your PC and wait until it says the phone is ready for use. At this point the computer should identify the phone correctly as a Redmi K20 Pro.
UNLOCKING THE BOOTLOADER
-------------------------------------------------------
I'll point to 2 guides, both on the new, official Mi Community Forums.
https://c.mi.com/thread-2262302-1-0.html
This first guide is somewhat incomplete, but it does give some good extra information about the bootloader unlocking and has direct links for the Unlock Tool and previous versions. Sometimes using an older version of the tool will resolve unlocking issues.
https://c.mi.com/thread-1857937-1-0.html
This second guide is more complete, but not so well written. Again there is some useful extra info included.
CUSTOM RECOVERIES
---------------------------------------
If you want to flash a custom ROM or root the phone, then you'll need to install a custom recovery. Your only realistic option here is TWRP, however TWRP comes in many flavours. (Before anyone corrects me and says what about Orange Fox? This is, underneath it all, still a heavily modified version of TWRP) For a brief overview of what TWRP is, I'll point you to the official TWRP page which answers that very question https://twrp.me/faq/whatistwrp.html
I should point out that MIUI will check on every boot whether the recovery partition has been modified. If it thinks it has, then the boot process will automatically restore the system recovery. In order to keep TWRP you will need to either flash a custom ROM, or make MIUI stop restoring system recovery on boot up. The most common way to keep TWRP with MIUI is to install Magisk.
If you are planning on using custom ROMs, then I would recommend the official TWRP, or the current 'dev' version from the official maintainer both are found here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
If you plan on sticking with MIUI, then there are a number of TWRP options that have additional functionality specific to Xiaomi devices - e.g. MIUI debloat scripts.
Many of these tend to be from Chinese, Russian and Indian developers, where Xiaomi phones are most popular. A selection of them can be found here.
https://forum.xda-developers.com/k2...irmware-10-3-8-0-9-6-13-t3939647/post79726515
Personally I don't use MIUI so haven't used these much, however OrangeFox seems to have some unique extra functions, like being able to survive OTA updates. So I would guess OrangeFox should be the one to recommend for those that choose to stick with MIUI.
ROOT
----------
Magisk has become the main choice for rooting, so use it. If you have problems with root and you're using something other than Magisk, you're going to struggle to get any help.
Magisk also does so much more than root. Check out the very good official documentation here for all you need to know.
It includes flashing instructions, which is the same whether you stick with MIUI or have a custom ROM. https://forum.xda-developers.com/ap...v7-universal-systemless-t3473445/post68966662
INSTALLING THINGS
From here I will assume you have some basic knowledge. I will not list every single step/command. The instructions won't be high level but at mid level giving enough details for those with basic knowledge. Many links in the previous post should give most of the knowledge needed, so there's no need for me to repeat things too much.
Where fastboot commands are given, I will assume you know how to use them i.e. you will open a terminal/command prompt/power shell window and also navigate to the appropriate directory if required.
I will assume you have checked the phone is connected with the
Code:
fastboot devices
command
INSTALLING TWRP
------------------------------
- Put the phone into fastboot mode (power and vol-) and connect to a PC
- On the PC
Code:
fastboot flash recovery TWRP.img
here you will need to replace TWRP.img with the actual file name of the TWRP image file, including the full path details if necessary.
At this point you have successfully installed TWRP, but if you boot into MIUI it will be lost. From here you need to boot immediately into TWRP in order to perform further steps to persist the TWRP installation.
- Whilst still connected to the PC
Code:
fastboot reboot
- Now as soon as you send the above command press and hold volume up on the phone
- Keep holding volume up until TWRP boots.
Now you are ready to do the next step. Depending on what you are doing this is likely to be flashing a custom ROM, installing Magisk or installing Orange Fox.
Reserved 2 - coming soon ish
Reserved 3 - hopefully not too long to wait
Thanks a lot for your time! New to this, because usually i buy Global phones, first time i buy a 100% Chinese one...
Interested in what ROM's you would recommend!
Indian K20 Pro has NFC Chip?
I thought they removed the NFC hardware from the device
Kalp3sh S1NGH said:
Indian K20 Pro has NFC Chip?
I thought they removed the NFC hardware from the device
Click to expand...
Click to collapse
Initially that was what many people thought. But after people have flashed the Chinese ROM on an Indian phone, they have found that they've got a working NFC chip.
Sealed Chinese ROM works well after switching the language to English.
1) Update to the latest MIUI
2) Make sure Google Services is enabled
3) Install Google Play from APKMIRROR
4) Install Calendar Sync (make sure set it to autostart)
4) Install Contact Sync (make sure set it to autostart)
5) Install Google Pay, Google, Gmail, Drive, Google Keep, Photos etc
5) Install an English keyboard (I don't think you will like Sogou keyboard)
6) Delete all other bloatwares.
You can almost remove almost all bloatwares without ADB or root, except those of Xiaomi's.
Kalp3sh S1NGH said:
Indian K20 Pro has NFC Chip?
I thought they removed the NFC hardware from the device
Click to expand...
Click to collapse
Robbo.5000 said:
Initially that was what many people thought. But after people have flashed the Chinese ROM on an Indian phone, they have found that they've got a working NFC chip.
Click to expand...
Click to collapse
There seems to be conflicting evidence here. Indian users have reported that they got a working NFC after flashing an official China ROM, but there's a new teardown of an Indian phone which appears to show that the NFC chip is missing.
It may be that some Chinese built phones were shipped over to India to cope with the initial demand, but that's a pure guess.
Robbo.5000 said:
There seems to be conflicting evidence here. Indian users have reported that they got a working NFC after flashing an official China ROM, but there's a new teardown of an Indian phone which appears to show that the NFC chip is missing.
It may be that some Chinese built phones were shipped over to India to cope with the initial demand, but that's a pure guess.
Click to expand...
Click to collapse
I just installed MIUI MS because I was facing some deep sleep issues on the stock ROM.
And there is a setting for NFC but if I enable it, it just turns back off. So maybe my particular device doesn't have the NFC chip.
Hello, in your provided link(second link in bootloading ) it is stated that you don't need TWRP to change ROM. So if I buy a Chinese version of K20 pro and I don't want a custom ROM, just MIUI 10 stable ROM ( I've seen a stable version released in Xiaomi.eu if I understand correctly) from a trusted source, do I need to follow your guide or can I just flash rom or even do it via updater app? This would make it much more easy. Thanks in advance
NoobRookie said:
Hello, in your provided link(second link in bootloading ) it is stated that you don't need TWRP to change ROM. So if I buy a Chinese version of K20 pro and I don't want a custom ROM, just MIUI 10 stable ROM ( I've seen a stable version released in Xiaomi.eu if I understand correctly) from a trusted source, do I need to follow your guide or can I just flash rom or even do it via updater app? This would make it much more easy. Thanks in advance
Click to expand...
Click to collapse
Xiaomi.eu is a custom rom you need twrp to flash it.
NoobRookie said:
Hello, in your provided link(second link in bootloading ) it is stated that you don't need TWRP to change ROM. So if I buy a Chinese version of K20 pro and I don't want a custom ROM, just MIUI 10 stable ROM ( I've seen a stable version released in Xiaomi.eu if I understand correctly) from a trusted source, do I need to follow your guide or can I just flash rom or even do it via updater app? This would make it much more easy. Thanks in advance
Click to expand...
Click to collapse
If you are on an official MIUI stable ROM and checking for an update says you have the latest version, but you know there is a newer version, then you can manually update by following that guide, using the section for updating via the updater app.
If you want to install anything that's not official MIUI, then you need to install that with TWRP.
One last dumb question:if I buy the factory sealed version of the phone with Chinese Rom, will I be able to change it to Global official Rom when it comes out? Or will I just get OTA updates and that's it, no possibility of changing official roms?
NoobRookie said:
One last dumb question:if I buy the factory sealed version of the phone with Chinese Rom, will I be able to change it to Global official Rom when it comes out? Or will I just get OTA updates and that's it, no possibility of changing official roms?
Click to expand...
Click to collapse
Yes you can change ROMs. You can flash an official Indian ROM using the Mi Flash Tool. See this post about flashing the Indian ROM https://forum.xda-developers.com/k2...king-flashing-india-rom-t3955129/post80025306
Nobody will know for sure that you can flash an official global ROM until its released, but best guess is that you would be able to.
Well I'm reading this from a galaxy note 4... a sh*t ton has changed, or at least it is very different with non-global phones.
If I understand correctly, the best, most safest way is to buy chinese factory sealed version so you can unlock the bootloader in case you lock it.
Which colour do you guys prefer, I like blue but I watched Frankie Tech video(s) and the red colour looks sick. Oh if you buy blue version will camera light also be blue lol. Gonna check out the other colour in another video.
Btw great guide, will try to stick with this note 4 for one more year as it just works fine!
Can anyone in UK confirm their experience with the signal/bands/carrier.
Windroid-user said:
Well I'm reading this from a galaxy note 4... a sh*t ton has changed, or at least it is very different with non-global phones.
If I understand correctly, the best, most safest way is to buy chinese factory sealed version so you can unlock the bootloader in case you lock it.
Which colour do you guys prefer, I like blue but I watched Frankie Tech video(s) and the red colour looks sick. Oh if you buy blue version will camera light also be blue lol. Gonna check out the other colour in another video.
Btw great guide, will try to stick with this note 4 for one more year as it just works fine!
Can anyone in UK confirm their experience with the signal/bands/carrier.
Click to expand...
Click to collapse
It's more a case of Xiaomi doing things different. They have an awkward bootloader unlock process. It needs to be done through their unlock tool, where you need to log in to a Mi account to use it, and that Mi account must already be bound to the phone you want to unlock, and you must have already registered, on the phone, to unlock the phone, using the same Mi account.
I've got the blue phone and yes the lights around the pop-up are blue.
I've not used it in the UK, but it should be fine on EE, Three and Vodafone.
O2 may be hit and miss depending where you are. Originally O2 only used band 20, which is missing from the phone, but a while back they added extra bands, this was in major cities and large towns. I'm not sure if O2 have rolled out these extra bands across more of the country since then.
Robbo.5000 said:
It's more a case of Xiaomi doing things different. They have an awkward bootloader unlock process. It needs to be done through their unlock tool, where you need to log in to a Mi account to use it, and that Mi account must already be bound to the phone you want to unlock, and you must have already registered, on the phone, to unlock the phone, using the same Mi account.
I've got the blue phone and yes the lights around the pop-up are blue.
I've not used it in the UK, but it should be fine on EE, Three and Vodafone.
O2 may be hit and miss depending where you are. Originally O2 only used band 20, which is missing from the phone, but a while back they added extra bands, this was in major cities and large towns. I'm not sure if O2 have rolled out these extra bands across more of the country since then.
Click to expand...
Click to collapse
Thanks for the reply. I have done a bootloader unlock before with the Sony xperia z3 using the official website, but there was no need to have an account linked to it kind of like apple icloud nightmare. Thanks for the info luckily I don't use O2 only Vodafone and three so far (8gb for £9 with three! Secret/hidden deal, no cashback bull). I would probably also go with blue.
That being said... the only benefit of stock China rom is OTA updates compared to "global" rom? I know there are custom roms but want to try out stock first, least bugs and only fair to give it a chance. Just want to build up my knowledge on this before I decide to say goodbye to my note 4. Also the actual global rom is on its way as far as we know?
Windroid-user said:
Thanks for the reply. I have done a bootloader unlock before with the Sony xperia z3 using the official website, but there was no need to have an account linked to it kind of like apple icloud nightmare. Thanks for the info luckily I don't use O2 only Vodafone and three so far (8gb for £9 with three! Secret/hidden deal, no cashback bull). I would probably also go with blue.
That being said... the only benefit of stock China rom is OTA updates compared to "global" rom? I know there are custom roms but want to try out stock first, least bugs and only fair to give it a chance. Just want to build up my knowledge on this before I decide to say goodbye to my note 4. Also the actual global rom is on its way as far as we know?
Click to expand...
Click to collapse
At the moment there is an official Indian ROM, which is more or less the same as a global ROM, the jury is still out as to whether OTA works OK when flashed on a Chinese phone. It 'should' be OK, but there hasn't been an update to the Indian ROM yet, so nobody has been able to find out for definite.
MIUI isn't without it's bugs. The week I used it there were a couple of issues, and there's a thread just for collating bugs on the Indian ROM.
The global version of the phone, the Mi 9T Pro, should be released in the next couple of months. It's been seen on a Dutch online shopping site in the last week. It was only showing the 2 6GB models, but I've been expecting that, as the Mi 9 never came with 8GB RAM globally. It's €480 for 6/128 GB, so a huge mark up on the Chinese price. Once that's released then official global ROMs will become available