Related
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
This thread applies to Huawei Mate 9 Pro only (model LON*, as M9Pro below). For Mate 9 (model MAH*) please go to the corresponding forum.
-----
Disclaimer:
I won't be responsible for bricked phone. Proceed with your own risk, make sure you know what you are doing.
This thread can be seen as a guide if your phone has exactly the same model and build version as mine. Otherwise please consider it as a description of my experiences for unlocking, flashing and rooting the phone.
SUPPORTED DEVICES:
LON-L29
LON-AL00
-----
As a start, this phone is great and I feel that it doesn’t need to be unlocked and rooted for a stable and long lasting daily use. However, unlock and root is almost a religion if you use Android phones
As a piece of info, big thanks to @raimondomartire, there is a thread for unlock, flash TWRP and root in the Mate 9 forum https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976, which is however according to my experience not totally applicable for the M9Pro anymore. There are also several other threads on the Mate 9 forum. Many things can be shared between both phones, but not always. Be careful about what you are doing!
-----
General info and attentions:
- My phone is M9Pro LON-AL00 (All net version from Chinese Mainland); LON-L29 (International version) should also work.
- This thread applies for build LON-AL00C00B213. Can be also applicable for similar builds, but I couldn’t test. Please report.
- None of the current builds of TWRP (up to 3.1.0) can decrypt data partition by default, which means you could only format the data partition in TWRP in order to access it in recovery (for backup to and install from internal storage etc.). But after formatting, you have to flash Huawei’s special stock data back to data partition (/data/hw_init), otherwise several functions of Huawei ROM won’t work. Refer to this (https://forum.xda-developers.com/showpost.php?p=71302827&postcount=627) or this (https://forum.xda-developers.com/showpost.php?p=72497328&postcount=204). Thanks to @gm007 and @ante0
- There are several root methods which handles encrypted or decrypted data partition. I didn’t format the data partition, i.e. data is still encrypted. If you want to format the data partition, please refer to this thread: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986. Thanks to @eddmecha
- If you need stock ROM, refer to useful links below. Use Huawei Update Extractor to extract the individual partitions from the ROM: https://forum.xda-developers.com/showthread.php?t=2433454
-----
Unlock bootloader:
There is enough info in the internet about unlocking M9Pro’s bootloader. Just a few points to mention:
- Generally, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976). But unlike he describes in his thread, there is no OEM Unlock options in the developer options anymore. Just use ADB to unlock.
- FRP unlock is not required!
- Huawei enables now a 14-day limitation, where you can officially get the bootloader unlock code 14 days after you first activate your Huawei ID on your phone and have logged in using your Huawei ID 14 CONSECUTIVE days.
- To go around this limitation, you can use dc-unlocker to get the bootloader code immediately. Google yourself
-----
Flash TWRP:
- Still, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976).
- The image from this thread is 3.0.3, which has some bugs built in, especially when flashing SuperSU.
- You could use TWRP 3.1.0-1 from https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617, but this one seems to have problem to be recognized as ADB device in recovery.
- There is a version 3.0.2 for Mate 9, which seems to have problem mounting USB-OTG.
- If your data partition is encrypted, you can only use ADB sideload or USB-OTG to install anything.
- If you want to do data wipe in TWRP, you have to flash Huawei’s special stock data back to data partition. See above general info and attentions.
-----
Root:
Firstly, thanks to @ante0 for explaining different flags in the root methods: https://forum.xda-developers.com/showpost.php?p=72504501&postcount=210. Some more discussions between us are also around this post.
I also tried several other root tools on the market (mobilego, vroot, YoRoot, OneClickRoot, iRoot etc.), NONE of them works.
As mentioned, there are different root methods around for unlocking M9Pro, depending on if you want to format your data partition. For me, I didn’t format, and SuperSU works for me. And the mate_9_pro_root.zip from @raimondomartire thread didn’t work for me.
I followed the steps below:
1. Get TWRP 3.1.0-1 (https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617)
2. Disable fingerprint ID (I think it’s probably optional, but have read somewhere that fingerprint stops working after flashing root).
3. Flash stock boot image for B213D (in download section). I think it’s optional too, but if you have tried other methods before, you can do this step to make sure your boot is stock and clean
4. Flash TWRP 3.1.0-1
5. Flash SuperSU-v2.79-MATE9-init.d_support_no_decrypt-signed.zip (in download section) via USB-OTG (in TWRP the device is not recognized as an ADB device, hence no “ADB sideload”). Thanks to @ante0 for building this zip!
6. Reboot – phone will reboot itself twice and SuperSU.apk will be installed automatically
7. You could flash back to 3.0.3, if you want the ADB sideload function.
-----
Download:
- TWRP 3.0.3-1: https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976
- TWRP 3.1.0-1: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
- SuperSU modified for M9Pro (thanks to @ante0): https://mega.nz/#!bR8D2Bab!bIgMLVmoll9R0GFqoFgkLxULrXlQ2710INt3TNbuI0c
- Boot image from B213D: https://mega.nz/#!LFlGTTZY!AaFq-_quM44YlK_Qdh9PgOjBE3Wtepmyz5OAuo_mabw
-----
Useful links:
- Stock firmware: http://hwmt.ru/oth/HWFF/info/view.php?find_model=lon
- Huawei Update (ROM) Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
Enjoy your Mate!
Just some clarification: (eventhough you wrote it's for AL00C00B213, which I missed xD)
Flashing stock boot is only needed if you're already rooted.
Boot image B213D is only for AL00C00. If you have a different model/build, use the boot image for that specific build:
Download your stock firmware from hwmt.ru and Huawei Update Extractor. Extract update.app from your firmware zip.
Open update.app in Huawei Update Extractor. Rightclick on BOOT and click on Extract selected.
Flash the extracted boot.img using fastboot in download mode (fastboot flash boot boot.img).
OEM Unlocking is required to be enabled. It's just not there in the chinese version (AL00). So check if it's there first and enable if it is.
Hi guys. Not sure if this is the right place to ask but how do I get rid of that annoying "your device is unlocked and can't be trusted....etc " msg?
I have a mate 9 pro and I want to flash twrp and to root it. I did it for some one plus, xiaomi, samsung so I have some experience. reading xda posts about the case of M9pro I understood that is not a simple path and I dont want to hard brick the phone. what precautions should I take?
attached phone config
thank you in advance
ante0 said:
Just some clarification: (eventhough you wrote it's for AL00C00B213, which I missed xD)
Flashing stock boot is only needed if you're already rooted.
Boot image B213D is only for AL00C00. If you have a different model/build, use the boot image for that specific build:
Download your stock firmware from hwmt.ru and Huawei Update Extractor. Extract update.app from your firmware zip.
Open update.app in Huawei Update Extractor. Rightclick on BOOT and click on Extract selected.
Flash the extracted boot.img using fastboot in download mode (fastboot flash boot boot.img).
OEM Unlocking is required to be enabled. It's just not there in the chinese version (AL00). So check if it's there first and enable if it is.
Click to expand...
Click to collapse
hwmt. ru is unavailable
mcn1970 said:
hwmt. ru is unavailable
Click to expand...
Click to collapse
http://hwmt.ru/hwmtsite/firmware-database/
working fine for me.
Edit: I should probably have posted the full link in my previous post. Sorry.
ante0 said:
http://hwmt.ru/hwmtsite/firmware-database/
working fine for me.
Edit: I should probably have posted the full link in my previous post. Sorry.
Click to expand...
Click to collapse
is it all procedures safe? no risk of hard brick?
ante0 said:
Just some clarification: (eventhough you wrote it's for AL00C00B213, which I missed xD)
Flashing stock boot is only needed if you're already rooted.
Boot image B213D is only for AL00C00. If you have a different model/build, use the boot image for that specific build:
Download your stock firmware from hwmt.ru and Huawei Update Extractor. Extract update.app from your firmware zip.
Open update.app in Huawei Update Extractor. Rightclick on BOOT and click on Extract selected.
Flash the extracted boot.img using fastboot in download mode (fastboot flash boot boot.img).
OEM Unlocking is required to be enabled. It's just not there in the chinese version (AL00). So check if it's there first and enable if it is.
Click to expand...
Click to collapse
i unlocked the bootloader and flashed recovery but my OTG stick is not recognized and cannot be mounted. also while in recovery the phone is not seen on PC.
i tried with both recoveries above.
ADB sideload doesnt work...keeps saying starting ADB sideloading features...in TWRP sdcard content is a bunch of files with weird names...
therefore how can I root the phone?
someone please help me!!
mcn1970 said:
i unlocked the bootloader and flashed recovery but my OTG stick is not recognized and cannot be mounted. also while in recovery the phone is not seen on PC.
i tried with both recoveries above.
ADB sideload doesnt work...keeps saying starting ADB sideloading features...in TWRP sdcard content is a bunch of files with weird names...
therefore how can I root the phone?
someone please help me!!
Click to expand...
Click to collapse
edit: solved it
any OTA after?
hi guys. You may or may not find this interesting. I certainly did. I'll post this in the mate 9 pro forum as well but i just thought i could get some ideas from as many of guys as possible seeying that theres a lot more posts here for mate 9 in general.
I have chinese version mate 9 pro that has been rebranded from AL00 to LON Spcseas and rooted. Build number b228. Anyway i recently saw in FF the new b229 so i downloaded all three files which had longer file names than usuall by the way. In twrp, the only file that was visable was the update.zip. So i renamed the hw and public zip files to what they would usually be named. Wiped data, and flashed all three files. Then reflashed supersu.
This is the interesting bit ( i think ). My imei numbers have changed, before flashing, the first imei number ended in 7 - now it ends with 4, the second imei number ended in 9 and now it ends with 7. Also, i now have a MEID number visable which was not there before and a section called android security patch level. Oddly enough im not getting any issues out of play store, im on play store right now and not a single problem regarding authentication. The build number is the same as well. As far as functionality goes, everything seems to be tip top, in fact everything seems to be working better, even unofficial exposed is working well. Only one thing isn't working properly. In phone manager there was a feature in the battery section that darkens the interface for everything to save power and prolong battery. That doesn't seem to be working anymore. In App - Permissions, the permissions is greyed out and it says no permissions requested.. Any thoughts or explenations guys??
Trying to flash another orginal stock rom
I bought a Mate 9 Pro, China Version (LON-AL00C00) want to install Mate 9 Pro, Asia Version (LON-L29C636) software on it. All explanations about Mate 9 Pro is for models which have SD Card. My Mate 9 Pro with dual sims and not containing a SD Card enrty.
I succesfully unlocked the bootloader, installed TWRP but couldn't flash LON-L29C636 stock software. Because TWRP don't see update.zip file. Not only update.zip, any files I downloaded or copied before. When I put a OGT TWRP suddenly exits and phone restarts.:crying:
As you see I can't flash a zip file and ofcourse superuser zip file to root as well. I'm stuck in this triangle. Please give me a hand guys.
I can't root my phone. Because I can't view and locate any file of my phone. When I plug a ogt cable twrp exits and phone restarts. 6GB-128GB Dual Sim version
---------- Post added at 11:48 AM ---------- Previous post was at 11:47 AM ----------
Seems I am the only one who is looking for something about Mate 9 Pro
CrisperNeO said:
This thread applies to Huawei Mate 9 Pro only (model LON*, as M9Pro below). For Mate 9 (model MAH*) please go to the corresponding forum.
-----
Disclaimer:
I won't be responsible for bricked phone. Proceed with your own risk, make sure you know what you are doing.
This thread can be seen as a guide if your phone has exactly the same model and build version as mine. Otherwise please consider it as a description of my experiences for unlocking, flashing and rooting the phone.
SUPPORTED DEVICES:
LON-L29
LON-AL00
-----
As a start, this phone is great and I feel that it doesn’t need to be unlocked and rooted for a stable and long lasting daily use. However, unlock and root is almost a religion if you use Android phones
As a piece of info, big thanks to @raimondomartire, there is a thread for unlock, flash TWRP and root in the Mate 9 forum https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976, which is however according to my experience not totally applicable for the M9Pro anymore. There are also several other threads on the Mate 9 forum. Many things can be shared between both phones, but not always. Be careful about what you are doing!
-----
General info and attentions:
-My phone is M9Pro LON-AL00 (All net version from Chinese Mainland); LON-L29 (International version) should also work.
-This thread applies for build LON-AL00C00B213. Can be also applicable for similar builds, but I couldn’t test. Please report.
-None of the current builds of TWRP (up to 3.1.0) can decrypt data partition by default, which means you could only format the data partition in TWRP in order to access it in recovery (for backup to and install from internal storage etc.). But after formatting, you have to flash Huawei’s special stock data back to data partition (/data/hw_init), otherwise several functions of Huawei ROM won’t work. Refer to this (https://forum.xda-developers.com/showpost.php?p=71302827&postcount=627) or this (https://forum.xda-developers.com/showpost.php?p=72497328&postcount=204). Thanks to @gm007 and @ante0
-There are several root methods which handles encrypted or decrypted data partition. I didn’t format the data partition, i.e. data is still encrypted. If you want to format the data partition, please refer to this thread: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986. Thanks to @eddmecha
-If you need stock ROM, refer to useful links below. Use Huawei Update Extractor to extract the individual partitions from the ROM: https://forum.xda-developers.com/showthread.php?t=2433454
-----
Unlock bootloader:
There is enough info in the internet about unlocking M9Pro’s bootloader. Just a few points to mention:
-Generally, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976). But unlike he describes in his thread, there is no OEM Unlock options in the developer options anymore. Just use ADB to unlock.
-FRP unlock is not required!
-Huawei enables now a 14-day limitation, where you can officially get the bootloader unlock code 14 days after you first activate your Huawei ID on your phone and have logged in using your Huawei ID 14 CONSECUTIVE days.
-To go around this limitation, you can use dc-unlocker to get the bootloader code immediately. Google yourself
-----
Flash TWRP:
-Still, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976).
-The image from this thread is 3.0.3, which has some bugs built in, especially when flashing SuperSU.
-You could use TWRP 3.1.0-1 from https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617, but this one seems to have problem to be recognized as ADB device in recovery.
-There is a version 3.0.2 for Mate 9, which seems to have problem mounting USB-OTG.
-If your data partition is encrypted, you can only use ADB sideload or USB-OTG to install anything.
-If you want to do data wipe in TWRP, you have to flash Huawei’s special stock data back to data partition. See above general info and attentions.
-----
Root:
Firstly, thanks to @ante0 for explaining different flags in the root methods: https://forum.xda-developers.com/showpost.php?p=72504501&postcount=210. Some more discussions between us are also around this post.
I also tried several other root tools on the market (mobilego, vroot, YoRoot, OneClickRoot, iRoot etc.), NONE of them works.
As mentioned, there are different root methods around for unlocking M9Pro, depending on if you want to format your data partition. For me, I didn’t format, and SuperSU works for me. And the mate_9_pro_root.zip from @raimondomartire thread didn’t work for me.
I followed the steps below:
1.Get TWRP 3.1.0-1 (https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617)
2.Disable fingerprint ID (I think it’s probably optional, but have read somewhere that fingerprint stops working after flashing root).
3.Flash stock boot image for B213D (in download section). I think it’s optional too, but if you have tried other methods before, you can do this step to make sure your boot is stock and clean
4.Flash TWRP 3.1.0-1
5.Flash SuperSU-v2.79-MATE9-init.d_support_no_decrypt-signed.zip (in download section) via USB-OTG (in TWRP the device is not recognized as an ADB device, hence no “ADB sideload”). Thanks to @ante0 for building this zip!
6.Reboot – phone will reboot itself twice and SuperSU.apk will be installed automatically
7.You could flash back to 3.0.3, if you want the ADB sideload function.
-----
Download:
-TWRP 3.0.3-1: https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976
-TWRP 3.1.0-1: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
-SuperSU modified for M9Pro (thanks to @ante0): https://mega.nz/#!bR8D2Bab!bIgMLVmoll9R0GFqoFgkLxULrXlQ2710INt3TNbuI0c
-Boot image from B213D: https://mega.nz/#!LFlGTTZY!AaFq-_quM44YlK_Qdh9PgOjBE3Wtepmyz5OAuo_mabw
-----
Useful links:
-Stock firmware: http://hwmt.ru/oth/HWFF/info/view.php?find_model=lon
-Huawei Update (ROM) Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
Enjoy your Mate!
Click to expand...
Click to collapse
I unlocked bootloader but couldn't root. Anyway I wanted to rebrand my phone to Asia version. Now I'm done but not successful because there is no Google,frp locked, and version is test one.
I can't install twrp because frp lock don't allow it. Also twrp can't read 128 GB internal memory, so I needed to install from pc.
Is there anyway to resolve and install stock Oreo version to my Mate 9 Pro or do you suggest me to resolve it via paid services?
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
livevalue said:
I unlocked bootloader but couldn't root. Anyway I wanted to rebrand my phone to Asia version. Now I'm done but not successful because there is no Google,frp locked, and version is test one.
I can't install twrp because frp lock don't allow it. Also twrp can't read 128 GB internal memory, so I needed to install from pc.
Is there anyway to resolve and install stock Oreo version to my Mate 9 Pro or do you suggest me to resolve it via paid services?
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
I've installed Oreo to Mate 9 Pro. If you have 128GB edition don't try to install anything from internal storage. That's it.
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
Hi guys, for re-branding there are threads in general Mate 9 forum. I didnt do it and am not planning to do it either...
CrisperNeO said:
Hi guys, for re-branding there are threads in general Mate 9 forum. I didnt do it and am not planning to do it either...
Click to expand...
Click to collapse
Rebranding is easy with HWOTA system if you will keep your phone EMUI 5.0 Nougat. And there is no risk if you make everything clearly.
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
never used Huawei before have a couple of questions
1. Is there anyway to get back to full stock with relock bootaloder in case the device need to go to service center?
(assume unlock bootloader with dc-unlocker not huawei id one)
2. From question 1 what do i need to do or backup before root?
thnak you so much!
44alphabeT said:
never used Huawei before have a couple of questions
1. Is there anyway to get back to full stock with relock bootaloder in case the device need to go to service center?
(assume unlock bootloader with dc-unlocker not huawei id one)
2. From question 1 what do i need to do or backup before root?
thnak you so much!
Click to expand...
Click to collapse
Yes you can always flash stock ROM as factory out, if you are not in Oreo.
And you can root it. It's your own protection to have a backup. I suggest you have, anyway it's up to you. You can loose all your data after root.
Hi, yersterday I used TWRP trying to install a newer firmware and I wiped system partition and now it does not boot because it doesn't have an OS. I was on EMUI 8 (636) trying to update the firmware.
Is there any way to flash a firmware via TWRP or Fastboot on EMUI 8 (i know partition names change on Oreo).
Thanks!
There was a security update released in the fall of 2016, at first I used the disable services app to disable system update servive in google play services but recently it keeps downloading anyway, could be that I did not re-disable the service fast enough in the google play services updates, not sure but it almost got me, luckily I was rebooting into recovery to backup and notived it so I used the file manager to delete update.zip from cache.
Anyway I have the update.zip file saved from last year and what I need to know is...
Has anyone successfully use flash fire to apply this update on this model if the LG K7 without losing root?
Will the update applied by either method (normal or using flash fire) overwrite the TWRP recovery?
If I lose root attempting this can I just flash it back with TWRP assuming it does not overwrite the recovery or flash my system backup again if needed?
Basicly, I don't know if flash fire can do this flawlessly and I don't know for certain if TWRP will still work on the phone without root on the phone and I don't know if the security update will overwrite the TWRP recovery.
All credible and valid answers appreciated.
Thanks
The answer:
No.
All of the updates to modern day (2017-12-20) do not remove root status; Nor do they affect the recovery partition (TWRP).
So you have successfuly used the OTA update with flash fire?
What really troubles me is all the patches to the GAPPS .odex files, my GAPPS is current so this seems like it would have a negative effect and the patch to boot.img particularly since it was changed during the rooting process apparently since I can't update supersu and supersu support's answer has been to restore the original boot.img.
Patch generally don't work on changed files so that's a concern.
Does anyone have the original boot.img they can share?
I only assume the update addressed the WI-FI KRACK exploit and that the new radio.img is worth having, that's the extent of my interest.
Any help out there? Anyone know of a properly prepared flashable zip?
Anyone successfully used flash fire for this?
flashfire doesnt work for some reason. it goes into a bootloop until you reboot the phone.
I have tried installing through ADB and used the one provided by KingOfMezi. Have also tried the automated installation of CATUVA21. It always brings me to the Huawei eRecovery. I have unlocked bootloader, USB Debugging is on too.
First indicate which version are you in, Noughat or Oreo ??? I say so bcoz there are separate recoveries for
the 2 versions of Android available here @ XDA
Also indicate what happens when you try to flash the TWRP after fastboot command, does it say
FAILED or any error or it installs properly ? Send screenshot of your fastboot command and its result
themagicalmage22 said:
I have tried installing through ADB and used the one provided by KingOfMezi. Have also tried the automated installation of CATUVA21. It always brings me to the Huawei eRecovery. I have unlocked bootloader, USB Debugging is on too.
Click to expand...
Click to collapse
If i were you dont install twrp now. On huawei nova 2i because the device is new. Developers of twrp have some issue to backup all of the system data. So it is useless and remember you cant update OTA. I rooted and install twrp now i regret. Because stock roms and software update are hard to find. And you cant flash it so easy. Im just giving you an idea.
A new Update for the ZenFone 3 Ultra is finally here. OTA Updates are live for eligible devices. This is not the Android 8.0 Update I was hoping as the Version number still shows 7.0 so lets hope I am wrong. Given the size I thought it might be the Android 8.0 Oreo Update but does not appear to be.
I have the WW Version and got the update notification this morning. It is 470.75MB in size and hopefully soon the full Firmware package will also be available for offline install.
Anyway, lets see how the firmware is and hope it fixes previously identified issues such as battery drain and others.
Enjoy!
I got it this morning as well, didn't think it was Oreo but hoping to see better performance........
DJMRLONG said:
I got it this morning as well, didn't think it was Oreo but hoping to see better performance........
Click to expand...
Click to collapse
So, is Ultra getting Oreo or not? What i hear are all rumours, nothing from the horses mouth.
australia here, today got OTA and now i have WW_14.1010.1804.74_20180605
still android 7.0
AWFRONT said:
A new Update for the ZenFone 3 Ultra is finally here.
Anyway, lets see how the firmware is and hope it fixes previously identified issues such as battery drain and others.
Enjoy!
Click to expand...
Click to collapse
not for my case, the update doesnt fix anything.
the battery drain is AMAZING. congrat Asus!
charged overnight, pull it at 100% in the morning, open 2 websites clicks 2-3 links, and battery down to 98%. whatttttt???
(not website with FHD photos, just normal websites with texts)
so anyone know wat the update about ?
I downloaded the update from Asus website and installed it manually cause my Ultra is rooted and didn't receive OTA. After downloading the zip file I placed it in the root of the phone (no folder), I rebooted the phone and after the boot I received a notification "update available". I taped on it and the whole process was automatic, the phone rebooted into twrp and from there it booted back into Android. After the first boot I didn't had installed anymore Magisk (no root) so in went to the PC and flashed once again the twrp image using fastboot mode (twrp was replaced with the stock recovery image during the update). From there (twrp) I flashed once again Magisk and everything was ok, I regained root access. With the exception of the security patch, witch is now from April 2018, everything seems to be the same as before the update.
lucian1983 said:
I downloaded the update from Asus website and installed it manually cause my Ultra is rooted and didn't receive OTA. After downloading the zip file I placed it in the root of the phone (no folder), I rebooted the phone and after the boot I received a notification "update available". I taped on it and the whole process was automatic, the phone rebooted into twrp and from there it booted back into Android. After the first boot I didn't had installed anymore Magisk (no root) so in went to the PC and flashed once again the twrp image using fastboot mode (twrp was replaced with the stock recovery image during the update). From there (twrp) I flashed once again Magisk and everything was ok, I regained root access. With the exception of the security patch, witch is now from April 2018, everything seems to be the same as before the update.
Click to expand...
Click to collapse
Hello. I would like to know how you rooted and installed twrp (without unlocking bootloader?)
Since to get update available, you need locked bootloader from what I understand.... so if you got update available, it appears your bootloader is still locked. But you are rooted and have custom recovery also. Thanks appreciate how you managed to root and install twrp without unlocking the bootloader.
mac231us said:
Hello. I would like to know how you rooted and installed twrp (without unlocking bootloader?)
Since to get update available, you need locked bootloader from what I understand.... so if you got update available, it appears your bootloader is still locked. But you are rooted and have custom recovery also. Thanks appreciate how you managed to root and install twrp without unlocking the bootloader.
Click to expand...
Click to collapse
I got my Ultra second hand and it camed with bootloader unlocked and magisk allready installed, so it was rooted and running latest firmware from Asus website at that time, several months ago, the firmware ww_1010.1804.64. in fastboot mode it said "unlocked" for the bootloader, so probably the seller used the unlock tool from Asus website to unlock the bootloader and after he flashed TWRP with the computer, by putting the phone in fastboot mode. You can find the TWRP zip file on a Indian site and download it with the Mega app. Just search on Google "TWRP zenfone 3 ultra".
Several days ago, I downloaded the new firmware from Asus website, ww_1010.1804.75 and placed the zip file in the root of the internal storage, under all the other folders. When I used the update system feature in the settings it didn't detect any update available, but after I rebooted the phone it appeared a notification message with "update available", I taped on it and the update was installed with TWRP and the phone rebooted. After reboot the TWRP image was replaced with the stock recovery from Asus and I had to go to the computer to flash TWRP image once again with the help of fastboot mode (also it said "unlocked " for the bootloader even after the update). From there (TWRP) I flashed back Magisk 16.0 zip file and everything is back to normal for me, I have the latest firmware from Asus and root.
understand now..thanks. So it did not do an ota update (my confusion) but did an update since you had the rom already in storage (hence the prompt for update available) ok thanks!
mac231us said:
understand now..thanks. So it did not do an ota update (my confusion) but did an update since you had the rom already in storage (hence the prompt for update available) ok thanks!
Click to expand...
Click to collapse
Anytime!!! Yes, that's it, it was no OTA update, only a notification prompt because I put the rom in the root of storage.