Related
I have bought my kenzo from gearbest and now I can't even update using the updater app because when I try to install the global stable rom it says "Can't verify update"!!!
What shuold I do now?
I noticed that if I press volume down and powerbutton it goes into fastboot mode... but I don't know if my device is locked or not... please help me!
What rom is reported in settings - about phone - MIUI version.
See the reddit xiaomi wiki on how to flash official roms with locked bootloader using "Mi PC Suite" or "EDL / Download Mode".
It says: MIUI 7.4 stable 7.4.9.0 (LHOCNDD)
I had the same issue like you but I bought mine from aliexpress. Anyway what worked for me is applying for official bootloader unlocker then I put the phone in to recovery mode ( updater app 3 dots in top corner) .
On your pc you should install mi suit and It will recognize update.
It may delete your gapps it did it for me.
next step is unlocking bootloader through official app ( you may need to wait for approval sms)
Last step is installing the new software http://en.miui.com/a-234.html
I hope that helps
Your right it is a Vendor Rom.
http://en.miui.com/thread-310405-1-1.html
Thanks a lot!! :d
One of my phones came with the same 7.4.9.0 (LHOCNDD), but bootloader was unlocked. Check yours, perhaps you're lucky too
It's a vendor rom, use EDL mode to flash to miui rom. Follow the steps here. No need to unlock bootloader.
http://en.miui.com/thread-235865-1-1.html
mine had the same LHOCNDD (not global), I bought mine from aliexpess, Xiaomi authorized store- phone build date is 2016.7 so I think they come from Xiaomi like this I had to wait 2 weeks for them to get one in stock,
I wish Xiaomi would stop with these strange firmwares, they block OTA updates, have unlocked bootloaders and cause other issues -
why they don't just use the global firmware on en.miui.com is a mystery, it would probably prevent 50% of returns from people bricking their devices.
I have the same 7.4.9.0 LHOCNDD vendor ROM. Bootloader is already unlocked. I want to flash TWRP to use with custom ROM because I don't want MIUI. Which guide should I follow in flashing TWRP?
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
Hello
I have a new M10 Pro (BLA-A09) here in the US, and I haven't activated it yet as I remain undecided about using it. The activity in this thread is limited, and I thought that there were more ROMS available. Perhaps I'm wrong, but I see very little activity for this phone. My current phone is an LG V10 which is unrootable, therefore moving to the M10P would be a good change since I can at least root the M10P and remove the bloatware.
I have a bootloader unlock code that I got on the last day! And I am on build 8.0.0.65 (C567).
I've read most of the current threads in this forum and the ROMS/kernels forum, and I remain confused as to what can be done with this phone.
I ask:
1. Can the phone truly be rooted? If yes, what for? To remove bloatware only? Or are there rooms (xirin, etc)?
2. I think that I read that rooting removes the data partition. Is that true? And how does that hurt?
3. I know that I can rebrand the phone with funkyhuawei. Why would I want to do that here in the US?
4. An OTA that follows a root, requires re-rooting the phone after the OTA, right?
Thank you for the help. I am excited about using this very powerful phone, I superficially read some threads before buying it, and I thought that it would be a very rootable and ROMable phone; I am not sure if that is the case.
nabril15 said:
Hello
I have a new M10 Pro (BLA-A09) here in the US, and I haven't activated it yet as I remain undecided about using it. The activity in this thread is limited, and I thought that there were more ROMS available. Perhaps I'm wrong, but I see very little activity for this phone. My current phone is an LG V10 which is unrootable, therefore moving to the M10P would be a good change since I can at least root the M10P and remove the bloatware.
I have a bootloader unlock code that I got on the last day! And I am on build 8.0.0.65 (C567).
I've read most of the current threads in this forum and the ROMS/kernels forum, and I remain confused as to what can be done with this phone.
I ask:
1. Can the phone truly be rooted? If yes, what for? To remove bloatware only? Or are there rooms (xirin, etc)?
2. I think that I read that rooting removes the data partition. Is that true? And how does that hurt?
3. I know that I can rebrand the phone with funkyhuawei. Why would I want to do that here in the US?
4. An OTA that follows a root, requires re-rooting the phone after the OTA, right?
Thank you for the help. I am excited about using this very powerful phone, I superficially read some threads before buying it, and I thought that it would be a very rootable and ROMable phone; I am not sure if that is the case.
Click to expand...
Click to collapse
1: yes. For anything you need root for, really.
Most bloatware can be removed without root, unless you want to start removing system apps. There are a few treble roms available over at the treble forum https://forum.xda-developers.com/project-treble.
Most, if not all, should be compatible. And you have https://openkirin.net/ which are for Huawei phones.
2. It does not. Well, it depends on where you read it. TWRP couldn't decrypt /data before, so you had to Format it and remove the encryption flag in fstab, but that is not needed anymore. (Official TWRP still can't, see download link below)
3. Do not rebrand. A09 is not compatible with L09/L29/AL and you will brick.
Also, if you had used it you would now be bootloader locked. What FH does is that it flashes an included oeminfo that has dualsim enabled. This also changes your IMEI, IMEI2 and SN in fastboot, making your old unlock code invalid. And right now there is no way to get a new one (I'm not sure if DC still works with A09, it doesn't on C432 as of B145.)
4. Yes. As ramdisk is overwritten you have to flash Magisk again (I suggest Magisk as SuperSU is not updated anymore)
Basically, you want to:
Go here to download TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Or Beta Magisk, can be buggy: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Backup your sdcard contents.
Go to Settings -> System -> About Phone -> Tap Build number until Developer options is enabled
Go to Settings -> System -> Developer options
Enable OEM Unlocking
Reboot to fastboot.
Unlock bootloader using: fastboot oem unlock ##unlock_code##
Use Volume key to move to 'Yes' on phone, then power to accept.
Wait for format to finish, setup phone again.
Transfer magisk zip to sdcard.
Reboot to fastboot again
Flash TWRP using: fastboot flash recovery_ramdisk twrp_bla_alp_0.7.img
Reboot to recovery by holding Power and Volume Up.
Enter your Pin
Now flash Magisk
Finished.
ante0 said:
1: yes. For anything you need root for, really.
Finished.
Click to expand...
Click to collapse
Thanks a lot ante0. I really appreciate it.
1. You pasted
Enable OEM Unlocking
Reboot to fastboot.
How do I reboot into fastboot?
2. So, can I use twrp? I really like it and have been using it for years on other phones and tablets.
3. I will use magisk and not SU, right?
4. I've been using the phone on wifi only and without a sim card, so it's not active on ATT here in the US. In the twrp thread I see that for OTA I need the following:
Flash with TWRP Magisk Uninstaller
Flash in Fastboot Mode recovery_ramdisk.img (=EMUI Recovery) + ramdisk.img + kernel.img
In Systemupdate settings (dot menu) use "Download and install current full package" (=FullOTA-MF, some GB) instead of only OTA (some MB)
Wow. How complicated, but I'm sure it's not that difficult. Although, in that same thread, I also read that some people have installed the OTA without removing magisk.
5. Kirin or treble roms? I can't see screenshots of either, so how do we decide?
Thanks again
nabril15 said:
Thanks a lot ante0. I really appreciate it.
1. You pasted
Enable OEM Unlocking
Reboot to fastboot.
How do I reboot into fastboot?
2. So, can I use twrp? I really like it and have been using it for years on other phones and tablets.
3. I will use magisk and not SU, right?
4. I've been using the phone on wifi only and without a sim card, so it's not active on ATT here in the US. In the twrp thread I see that for OTA I need the following:
Flash with TWRP Magisk Uninstaller
Flash in Fastboot Mode recovery_ramdisk.img (=EMUI Recovery) + ramdisk.img + kernel.img
In Systemupdate settings (dot menu) use "Download and install current full package" (=FullOTA-MF, some GB) instead of only OTA (some MB)
Wow. How complicated, but I'm sure it's not that difficult. Although, in that same thread, I also read that some people have installed the OTA without removing magisk.
5. Kirin or treble roms? I can't see screenshots of either, so how do we decide?
Thanks again
Click to expand...
Click to collapse
1. Either you can use adb: adb reboot bootloader
Or power off phone then hold volume down and plug in usb
Or plug in usb, reboot, hold volume down.
2. Yes, it's fully functional.
3. Magisk is preferable. Mainly because it's being updated, and can pass Safetynet if any of your apps need it to pass.
4. You *should* only need to flash recovery_ramdisk (I guess you can use the one from the last update on http://pro-teammt.ru/firmware-database/?firmware_model=BLA-A09&firmware_page=0)
To get recovery_ramdisk you need to download update.zip from pro-teammt.ru, then extract update.app from it.
Download Huawei Update Extractor https://forum.xda-developers.com/showthread.php?t=2433454
Extract Huawei Update Extractor zip and run the exe. Go to settings in the program and disable header check.
Next open up update.app in it, rightclick on recovery_ramdisk and click on Extract Selected.
Now you can flash that image using fastboot (fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img)
This will restore stock recovery and will let you flash OTA directly from System Update.
The reason you have to restore stock recovery is because phone will reboot to recovery to update, but if you have TWRP flashed it won't update at all
You would have to flash back both TWRP and Magisk after update finishes.
(You can actually flash FULLOTA Update.zip directly in TWRP if you use HuRUpdater, but seeing as the US Mate 10 Pro rarely get any updates it's not really needed.)
5. Kirin is treble, they are built for Huawei devices rather than being just for treble enabled devices.
I've only really used Lineage, but moved back to stock as TWRP does not work with Treble roms. It should work once we get 8.1 firmware though.
ante0 said:
5. Kirin is treble, they are built for Huawei devices rather than being just for treble enabled devices.
I've only really used Lineage, but moved back to stock as TWRP does not work with Treble roms. It should work once we get 8.1 firmware though.
Click to expand...
Click to collapse
thanks again Ante
Would you say that it makes sense for me to, when I put the sim in the phone and use it (if I decide to), to attempt an OTA update first, and then do root and whatever else? My phone's build is from December 2017, so I assume that ATT will have some sort of update for the phone.
You mentioned that the US Mate10 rarely gets updates. So, then how would any of us get any updates , security or otherwise? How will we get 8.1, for example? Are you in the US, btw? What ROM are you using on this phone?
ante0 said:
5. Kirin is treble, they are built for Huawei devices rather than being just for treble enabled devices.
I've only really used Lineage, but moved back to stock as TWRP does not work with Treble roms. It should work once we get 8.1 firmware though.
Click to expand...
Click to collapse
thanks again Ante
Would you say that it makes sense for me to, when I put the sim in the phone and use it (if I decide to), to attempt an OTA update first, and then do root and whatever else? My phone's build is from December 2017, so I assume that ATT will have some sort of update for the phone.
You mentioned that the US Mate10 rarely gets updates. So, then how would any of us get any updates , security or otherwise? How will we get 8.1, for example? Are you in the US, btw? I assume that you have the device; what ROM are you using?
nabril15 said:
thanks again Ante
Would you say that it makes sense for me to, when I put the sim in the phone and use it (if I decide to), to attempt an OTA update first, and then do root and whatever else? My phone's build is from December 2017, so I assume that ATT will have some sort of update for the phone.
You mentioned that the US Mate10 rarely gets updates. So, then how would any of us get any updates , security or otherwise? How will we get 8.1, for example? Are you in the US, btw? I assume that you have the device; what ROM are you using?
Click to expand...
Click to collapse
I do not have a US Mate 10 Pro (A09), but the global (L29) on C432.
You can read a bit in this thread about the US version updates:
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-bla-a09-c567-usa-t3775258
I guess the lack of updates is due to the problems Huawei has with the US government. :/
You do get updates, but there seem to be a few months between them.
I would update and then root. There is an update in that thread which is fairly new, but it has not been indexed by Firmware Finder (pro-teammt.ru). You could flash it using TWRP and HuRUpdater as I don't think you have Nocheck recovery for A09.
hi all there
as we know recently almost all ANNE got update to pie
which is really good but bad also at the same time
as in latest hauwei secuirty patches users are unable to unlock bootloader except downgrading to android 8
so i have very critical questions
how to downgrade/rollback only security version/patch ?
or alternativly which partitions from update.app include security update?
basic goal behind this questions is to find a way to rollback secuirty while staying in android pie,
few idea in my mind is that if we get partitions which is responsible for security patch then that same partitions from older version will downgrade the security while actually staying in pie,
another way is risky as we need to connect device to USB COM 1.0, (open device, connect test point)and from board firmware flash only xloader, this one is real risk, and this is just a theory its not neccecery that it will work,
experts here can help
Hey folks,
So somehow when unlocking my bootloader with the unlock_key/code from OnePlus, I switched the ROM from the T-Mobile variant to the stock OnePlus variant. I may have corrupted/wiped one of the two slots and gotten lucky, that was months ago and I've forgotten.
Mostly I wanted to confirm an unlocked bootloader in the event there is a stable and up-to-date ROM made available on this device. It's my primary phone and I don't want to be alpha testing updates, so I'm happy with the stock OnePlus OS.
However, my device won't apply updates. I'm NOT rooted, though the bootloader is unlocked. What are my options for applying updates?
Do I need to re-enable bootloader via adb, which will likely wipe the OS and require re-configuration of all my apps and settings? If I apply root (and wipe-OS), can the root receive updates easily?
Been about two months now without the latest security patch, things could be worse but I definitely want to update!
ANy thoughts are appreciated, thanks!
lifebringer123 said:
Hey folks,
So somehow when unlocking my bootloader with the unlock_key/code from OnePlus, I switched the ROM from the T-Mobile variant to the stock OnePlus variant. I may have corrupted/wiped one of the two slots and gotten lucky, that was months ago and I've forgotten.
Mostly I wanted to confirm an unlocked bootloader in the event there is a stable and up-to-date ROM made available on this device. It's my primary phone and I don't want to be alpha testing updates, so I'm happy with the stock OnePlus OS.
However, my device won't apply updates. I'm NOT rooted, though the bootloader is unlocked. What are my options for applying updates?
Do I need to re-enable bootloader via adb, which will likely wipe the OS and require re-configuration of all my apps and settings? If I apply root (and wipe-OS), can the root receive updates easily?
Been about two months now without the latest security patch, things could be worse but I definitely want to update!
ANy thoughts are appreciated, thanks!
Click to expand...
Click to collapse
If you do a factory reset with the MSM tool you will get the T-Mobile ROM back and it will also relock the bootloader (and of course wipe all your apps and settings). You will definitely be able to get updates that way. I don't know if there is a way to get updates without wiping all of your data.
towardsdawn said:
If you do a factory reset with the MSM tool you will get the T-Mobile ROM back and it will also relock the bootloader (and of course wipe all your apps and settings). You will definitely be able to get updates that way. I don't know if there is a way to get updates without wiping all of your data.
Click to expand...
Click to collapse
OK, thank you! I will give it a try eventually...
Any recommended ROMS that are lightweight but super stable and also regularly updated? Like LineageOS (which I believe is not updated for this phone)...
nothing beats stock in stability period. yes you can update vs stock OTA on unlocked bootloader
You can also update and receive OTA while rooted with magisk, my current method is here:
1) click "try again." click "resume" which may or may not reboot the device.
2) adb reboot fastboot
3) fastboot boot previous_magiskpatched_boot.img
4) find active slot with adb shell /bin/getprop ro.boot.slot_suffix
5) dd
if=/dev/block/bootdevice/by-name/boot_a_or_b of=/sdcard/Download/boot.img to backup stock boot.img
6) direct install magisk, reboot
7) repeat step 5 to backup patched boot.img
8) adb pull sdcard/Download patched and stock.img
towardsdawn said:
You can also update and receive OTA while rooted with magisk, my current method is here:
1) click "try again." click "resume" which may or may not reboot the device.
2) adb reboot fastboot
3) fastboot boot previous_magiskpatched_boot.img
4) find active slot with adb shell /bin/getprop ro.boot.slot_suffix
5) dd
if=/dev/block/bootdevice/by-name/boot_a_or_b of=/sdcard/Download/boot.img to backup stock boot.img
6) direct install magisk, reboot
7) repeat step 5 to backup patched boot.img
8) adb pull sdcard/Download patched and stock.img
Click to expand...
Click to collapse
thanks!
Ytube21 said:
nothing beats stock in stability period. yes you can update vs stock OTA on unlocked bootloader
Click to expand...
Click to collapse
Are you saying that if I re-lock my bootloader, it will NOT wipe my OS/factory reset, and I'll be able to update the OS via OTA updates?
Remember, bootloader is unlocked but I'm on the stock ROM (not the T-Mobile ROM, though this is the physical T-Mobile variant).
lifebringer123 said:
Are you saying that if I re-lock my bootloader, it will NOT wipe my OS/factory reset, and I'll be able to update the OS via OTA updates?
Remember, bootloader is unlocked but I'm on the stock ROM (not the T-Mobile ROM, though this is the physical T-Mobile variant).
Click to expand...
Click to collapse
Hello there, lifebringer123.
I believe Ytube21 made a grammatical error in his response to you. I believe what he intended to imply was that, with an unlocked bootloader, you can install OTA updates on the stock ROM.
Because the phone will be transitioning from a non-assured software integrity state and unprotected personal data condition to a guaranteed software integrity state and protected data condition, relocking the bootloader will result in a factory reset to ensure no trace of a root related process capable of accessing /data.
Since I assume you don't have unlocked firmware, I'm guessing you don't have the "Local upgrade" option in settings (Settings -> System -> System update -> Gear settings icon in top right corner -> Local upgrade), which means you're missing out on the most direct and authentic way of installing OTA updates.
However, I have another idea in mind, which I'm not sure will work, but could if your circumstances allow it. Is it possible to install the most recent OnePlus Nord N200 OTA update after flashing TWRP?
Here's what I'm thinking:
1. Download the most appropriate TWRP image (Current most recent TWRP for OnePlus Nord N200)
2. Boot OnePlus Nord N200 into bootloader (adb reboot bootloader while the device is on, or, while the device is off, hold the volume down and power key for a while, release the power button when the OnePlus logo comes up (but keep pressing the volume down button), go appropriately through the menu (select suitable language, then choose Advanced -> Reboot to fastboot)
3. Ensure that fastboot detects your OnePlus Nord N200 (fastboot devices)
4. Momentarily boot into recovery (fastboot boot NameOfRecoveryHere.img (This will only boot the recovery, not install it)
5. Flash the desired OTA update .zip file using the recovery and reboot
Note: Your build number will be useful for me to point you in the right direction for finding the appropriate .zip for the OTA update (Step 5)
Apart from the way described above, I'm very confident you won't be able to properly apply updates without wiping your phone. I would suggest just backing up your phone (Save anything you want to preserve) to a secure location and then following the procedures mentioned by towardsdawn of utilizing MSM tools to restore the T-Mobile ROM.
If you have any questions or issues, please let me know.
Aselloph said:
Hello there, lifebringer123.
I believe Ytube21 made a grammatical error in his response to you. I believe what he intended to imply was that, with an unlocked bootloader, you can install OTA updates on the stock ROM.
Click to expand...
Click to collapse
The OS notices the OTA updates, but it cannot apply/install them no matter what I do to try.
Aselloph said:
Because the phone will be transitioning from a non-assured software integrity state and unprotected personal data condition to a guaranteed software integrity state and protected data condition, relocking the bootloader will result in a factory reset to ensure no trace of a root related process capable of accessing /data.
Click to expand...
Click to collapse
Makes sense; thanks.
Aselloph said:
Since I assume you don't have unlocked firmware, I'm guessing you don't have the "Local upgrade" option in settings (Settings -> System -> System update -> Gear settings icon in top right corner -> Local upgrade), which means you're missing out on the most direct and authentic way of installing OTA updates.
Click to expand...
Click to collapse
That is correct; I don't have that option. I also no longer have the "T-Mobile" Splash sceen on startup, my assumption since doing this earlier this year was that I may have wiped the t-mobile branded ROM variant, and the phone reverted to the "slot B" stock variant. But I could be wrong. In any case...
Aselloph said:
However, I have another idea in mind, which I'm not sure will work, but could if your circumstances allow it. Is it possible to install the most recent OnePlus Nord N200 OTA update after flashing TWRP?
Here's what I'm thinking:
1. Download the most appropriate TWRP image (Current most recent TWRP for OnePlus Nord N200)
2. Boot OnePlus Nord N200 into bootloader (adb reboot bootloader while the device is on, or, while the device is off, hold the volume down and power key for a while, release the power button when the OnePlus logo comes up (but keep pressing the volume down button), go appropriately through the menu (select suitable language, then choose Advanced -> Reboot to fastboot)
3. Ensure that fastboot detects your OnePlus Nord N200 (fastboot devices)
4. Momentarily boot into recovery (fastboot boot NameOfRecoveryHere.img (This will only boot the recovery, not install it)
5. Flash the desired OTA update .zip file using the recovery and reboot
Note: Your build number will be useful for me to point you in the right direction for finding the appropriate .zip for the OTA update (Step 5)
Apart from the way described above, I'm very confident you won't be able to properly apply updates without wiping your phone. I would suggest just backing up your phone (Save anything you want to preserve) to a secure location and then following the procedures mentioned by towardsdawn of utilizing MSM tools to restore the T-Mobile ROM.
If you have any questions or issues, please let me know.
Click to expand...
Click to collapse
Model DE2118
Build 11.0.1.9.DE18CB
ONE PLUS Nord N200 5G
(dre8t, but unlocked bootloader via unlock_code.bin)
I would give that a whirl if you could point me to the current OTA update .zip package. However, I bookmarked that TWRP thread months ago, but it still hasn't been updated, and I never did get it working correctly. But I'll try it. If it works and the manual OTA update .zip is only monthly/quarterly, the inconvenience is not severe. Still, I'm not using root or any custom ROM at the moment, so I should really go back to a locked bootloader so I can receive OTA updates, and suck up the loss of a few hours of restoring settings/apps...
Again (for all on thread), if there is a solid Custom ROM which regularly gets security updates, please point me to that thread/ROM! The
Thank you so much for your time!
Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)
Hey there. i'm a new XDA Member myself. i've been mostly stalking these forums for the N200 Ever since people started the root phase and twrp projects for codename HOLI. but i'm here to convert @summersofar's guide in order to make it more...
forum.xda-developers.com
Try re-doing it. First, use MSM tool to return to Tmo, then unlock the bootloader again, then follow that guide.
It should completely fix your broken slots. And yes, my phone is rebranded, and it can apply updates perfectly.
I'm even rooted.
justauserthatusesaphone said:
Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)
Hey there. i'm a new XDA Member myself. i've been mostly stalking these forums for the N200 Ever since people started the root phase and twrp projects for codename HOLI. but i'm here to convert @summersofar's guide in order to make it more...
forum.xda-developers.com
Try re-doing it. First, use MSM tool to return to Tmo, then unlock the bootloader again, then follow that guide.
It should completely fix your broken slots. And yes, my phone is rebranded, and it can apply updates perfectly.
I'm even rooted.
Click to expand...
Click to collapse
Thanks! When OTA updates end for our OS, in 1-2 years, what will you do? Switch phones, or do you think you have a custom ROM/OS that sounds stable enough?
I'll try the MSM tool, debate rooted or not, then report back...
Thanks again all!
lifebringer123 said:
Thanks! When OTA updates end for our OS, in 1-2 years, what will you do? Switch phones, or do you think you have a custom ROM/OS that sounds stable enough?
I'll try the MSM tool, debate rooted or not, then report back...
Thanks again all!
Click to expand...
Click to collapse
you're welcome, sorry for being late lol
after 2-3 years, ill probably keep this phone and install lineageos or pixel experience (that is, if it gets support)
although by that time, the trade in value is probably 2 dollars so I'll use it if i ever get into android development.
Any word on custom ROMs for this like Lineage OS or Pixel Experience?