I'm on the stock rom BAH2-W19 8.0.0.230 C431 in Germany and the unlock procedure doesn't work. I was wondering if downgrading to a previous version would let the unlocking procedure work and if it is required or not to maintain the same 'version' on the downgraded rom.
In short: on this firmware BAH2-W19 8.0.0.230 C431, can i flash a older one like BAH2-W19 8.0.0.179(C431) or maybe this other one BAH2-W19 8.0.0.217(OCEC432) ?
P4p3r1n0 said:
I'm on the stock rom BAH2-W19 8.0.0.230 C431 in Germany and the unlock procedure doesn't work. I was wondering if downgrading to a previous version would let the unlocking procedure work and if it is required or not to maintain the same 'version' on the downgraded rom.
In short: on this firmware BAH2-W19 8.0.0.230 C431, can i flash a older one like BAH2-W19 8.0.0.179(C431) or maybe this other one BAH2-W19 8.0.0.217(OCEC432) ?
Click to expand...
Click to collapse
Generally (well known for various other Huawei phones), submodel and cust must be followed.
They can be changed, aka rebranded, but only with unlocked Bootloader, since it requires flashing OEMInfo
Also, be careful when downgrading, if you go to an old version of Bootloader (usually it coincides to before GPU Torbo or firmwares with Security patch from the first half of 2018 or earlier), then it causes a serious brick.
To the other side, downgrading to the same Bootloader version does not help to ease getting the BL code.
Btw, Bootloader version can be inspected from a particular Hex address from xloader img, which can be extracted from update.app by Huawei UpdateExtracror (Windows program), that must be unzipped from update.zip, downloaded from a FullOTA firmware from FF
For that reason, people use Testpoints method to erase and then flash the old firmware (board image, if available for the particular device) to be able to downgrade the BL, and thus to be able to buy BL code the old way, simply based on providing IMEI and Serial number
zgfg said:
They can be changed, aka rebranded, but only with unlocked Bootloader
Click to expand...
Click to collapse
This means that the ROM i'd have to download has to be of the same branding (C431). At least here, to flash a C432 for downgrading would not work.
zgfg said:
be careful when downgrading, if you go to an old version of Bootloader
Click to expand...
Click to collapse
My intention was to downgrade the firmware so that it would flash a previous version of the bootloader. You understood the point
zgfg said:
unzipped from update.zip, downloaded from a FullOTA firmware from FF
Click to expand...
Click to collapse
What is FF ?
So, in short, if I really want to downgrade the firmware, I have to download a ROM from FF* of the same brand (C431), then extract the xloader img using the Extractor tool, compare this to my current version of the firmware and re-download any other ROM from FF until I see that the downloaded ROM has got a previous version of the bootloader. Flash this particular ROM. Is that correct?
I have not fully understood the "Testpoints method". Is it a real (documented) Method for flashing?
Thanks for your answer, it helped! Waiting now for this last feedback but until then, thank you!
P4p3r1n0 said:
This means that the ROM i'd have to download has to be of the same branding (C431). At least here, to flash a C432 for downgrading would not work.
My intention was to downgrade the firmware so that it would flash a previous version of the bootloader. You understood the point
What is FF ?
So, in short, if I really want to downgrade the firmware, I have to download a ROM from FF* of the same brand (C431), then extract the xloader img using the Extractor tool, compare this to my current version of the firmware and re-download any other ROM from FF until I see that the downloaded ROM has got a previous version of the bootloader. Flash this particular ROM. Is that correct?
I have not fully understood the "Testpoints method". Is it a real (documented) Method for flashing?
Thanks for your answer, it helped! Waiting now for this last feedback but until then, thank you!
Click to expand...
Click to collapse
FF = Firmware Finder.
Find a thread on XDA, search for XDA Huawei FirmwareFinder.
There is the FF apk on Playstore and FF exe for PC, you can also search firmwares directly from their server:
https://pro-teammt.ru/online-firmware-database-ru/
You don't really need to extract xloader.img (there is also a thread on XDA for Huawei Update Extractor and there was a thread for a special PC program analyzing the required bytes in xloader.img).
Instead, you can read Changelogs by FF, and you will see when there was the upgrade to GPU Turbo, and also which Google Security Patch is coming with which version.
Hence, in short - your intention was to 'cheat' by downgrafing to the old Bootloader, so that you can get the BL code easy and cheap.
Unfortunately, do not go for - you will brick your Huawei device.
(Many people tried similarly, with various Huawei phone models, and bricked them)
For TestPoints search similarly for XDA Huawei TestPoints. Generally, you have to physically open the phone, find the TestPoints pins (picturures can be found on the Net) on the motherboard, two of them have to be shortened
Then you will need a special Huawei loader and USB driver (there is one for Windows and one for Linux), and a board image to flash (there are sites on the Net selling the board images).
That way you can unbrick the phones or downgrade (as you wanted) to the older firmware (with the older Bootloader version)
P4p3r1n0 said:
My intention was to downgrade the firmware so that it would flash a previous version of the bootloader.
Click to expand...
Click to collapse
I realized there is not much to gain if I'd flash a previous bootloader. The original issue was that I thought I couldn't 'unlock' this one, instead I can and did it (check out the unlock thread).
All the others information are still useful, so thank you!
Related
I've gone through the process of entering my IMEI and serial number in the EMUI bootlocker website and its given me a code.
I haven't yet done any further steps including the adb commands required to remove the blootlock.
However I can now see on the MT Huawei Firmware update list that there is a new update (128) and I'm on (120b)
I've tried using the VPN option to force the update to obtain the firmware from its own servers to no avail.
The firmware checker simply states the firmware isn't compatible with device.
..has somehow simply registering caused it to be blocked for future updates?
##Secondly##.. Does continuing the process and using abd unblock commands cause it to no longer work with OTA?
Or is it only when and if you root it - that OTA can not work? (or does it work)
Quite confused and would really appreciate any advice as ideally I would like to keep OTA, but have root at sometimes with the hope that I could disable root anytime a OTA updates comes available and then re-enable after.
Any advice greatly appreciated )
dgoncalves81 said:
I've gone through the process of entering my IMEI and serial number in the EMUI bootlocker website and its given me a code.
I haven't yet done any further steps including the adb commands required to remove the blootlock.
However I can now see on the MT Huawei Firmware update list that there is a new update (128) and I'm on (120b)
I've tried using the VPN option to force the update to obtain the firmware from its own servers to no avail.
The firmware checker simply states the firmware isn't compatible with device.
..has somehow simply registering caused it to be blocked for future updates?
##Secondly##.. Does continuing the process and using abd unblock commands cause it to no longer work with OTA?
Or is it only when and if you root it - that OTA can not work? (or does it work)
Quite confused and would really appreciate any advice as ideally I would like to keep OTA, but have root at sometimes with the hope that I could disable root anytime a OTA updates comes available and then re-enable after.
Any advice greatly appreciated )
Click to expand...
Click to collapse
It is NOT related with unlocked bootloader or rooted firmware.
It's related with emui 8.1 version whitch is NOT supported by FirmwareFinder.
So basically VPN or Proxy wont work with that.
Another thing: the firmwares listed on FF aren't approved at appearance date. This means that we must wait a bit for approval, and after that can FF download the selected firmware (again, emui 8.1 is not supported).
If you are in hurry with flashing the new firmwares, you can via TWRP (methods described on forum).
BUT be aware, that even with that you can brick your phone
(trust me: after 2 days, when i brought my phone, it was hardbricked... i haven't other choice but RMA, and obviously they have changed the phone. SO be very careful.)
tamaskurti said:
It is NOT related with unlocked bootloader or rooted firmware.
It's related with emui 8.1 version whitch is NOT supported by FirmwareFinder.
So basically VPN or Proxy wont work with that.
Another thing: the firmwares listed on FF aren't approved at appearance date. This means that we must wait a bit for approval, and after that can FF download the selected firmware (again, emui 8.1 is not supported).
If you are in hurry with flashing the new firmwares, you can via TWRP (methods described on forum).
BUT be aware, that even with that you can brick your phone
(trust me: after 2 days, when i brought my phone, it was hardbricked... i haven't other choice but RMA, and obviously they have changed the phone. SO be very careful.)
Click to expand...
Click to collapse
Via twrp? What method? Depending on the device type you would have to debrand first
dladz said:
Via twrp? What method? Depending on the device type you would have to debrand first
Click to expand...
Click to collapse
The method I was referring is with HuRUpdater.
HuRupdater Thread
tamaskurti said:
The method I was referring is with HuRUpdater.
HuRupdater Thread
Click to expand...
Click to collapse
Have you used this before? On the P20 Pro?
Only reason i ask is the P20 Pro is not listed on the supported devices and as i said you would need to have the correct firmware for your device, the newer firmwares are made for the European version of the device L29 not L09, so providing you're on L29 and it's the correct firmware then it should work, but i would not like to be the person to crash test this.
I'm on the L09 which doesn't take L29 firmwares unless i debrand and then try it.
I have CLT-L29C432B128. (I have updated with hurupdater since the 128 fw is not yet approved from firmware finder)
I thinking on try flashing cn firmware.
tamaskurti said:
It is NOT related with unlocked bootloader or rooted firmware.
It's related with emui 8.1 version whitch is NOT supported by FirmwareFinder.
So basically VPN or Proxy wont work with that.
Another thing: the firmwares listed on FF aren't approved at appearance date. This means that we must wait a bit for approval, and after that can FF download the selected firmware (again, emui 8.1 is not supported).
If you are in hurry with flashing the new firmwares, you can via TWRP (methods described on forum).
BUT be aware, that even with that you can brick your phone
(trust me: after 2 days, when i brought my phone, it was hardbricked... i haven't other choice but RMA, and obviously they have changed the phone. SO be very careful.)
Click to expand...
Click to collapse
Thanks for the advice!
So the list if updates that firmware finder shows are upcoming updates - rather than being released for offical OTA distrubtion from the date listed?
If firmware finder gets it first I'm wondering if you know generally when the OTA updates start to be pushed out via the OTA update system?
I don't know.
Generally about 2-3 weeks (maybe less).
Can a LLD-AL00 (C00) device be rebranded to a LLD-L31 device? I tried to search for it but didn't find any threads covering this.
Just start mess up with the phone so still have a locked boot but it can be fixed. So far, I just tried to flash the full-OTA update.app (C432B130) and it does not work, system img fails to load (well honestly I didn't expect it to but still had to try..)
Try LLD-L31C432B131 or LLD-L31C432B132 full ota's. Do not flash Al00 to a L31 it doesn't end well.
Sent from my LLD-L31 using Tapatalk
MSandstrom said:
Can a LLD-AL00 (C00) device be rebranded to a LLD-L31 device? I tried to search for it but didn't find any threads covering this.
Just start mess up with the phone so still have a locked boot but it can be fixed. So far, I just tried to flash the full-OTA update.app (C432B130) and it does not work, system img fails to load (well honestly I didn't expect it to but still had to try..)
Click to expand...
Click to collapse
Your phone's varient depends mainly on the motherboard inside so your phone might not work properly if you flash firmware of other varients. If you wanna go back to stock your best option is to flash the correct firmware using HuRupdater tool.
I have searched everywhere but I didn't find a reply to my question.
A couple of days ago I have updated my phone LLD-L31 to the version 8.0.0.132 through Firmware Finder (it worked for me with proxy method) then I decided to revert back to the previous version 8.0.0.131. So I started reading guides to install a firmware on Huawei/Honor devices, I have downloaded the FullOTA package version 8.0.0.131 with Firmware Finder, placed it in the folder dload on my SDcard and started the intstallation in the project menu (accessible digiting *#*#2846579#*#* in the dialer), it started but suddenly it ended with a message "installation failed".
So my question is: how can i revert to the previous version of the software (or to the out of the box firmware installed on my device)?
karmakey said:
I have searched everywhere but I didn't find a reply to my question.
A couple of days ago I have updated my phone LLD-L31 to the version 8.0.0.132 through Firmware Finder (it worked for me with proxy method) then I decided to revert back to the previous version 8.0.0.131. So I started reading guides to install a firmware on Huawei/Honor devices, I have downloaded the FullOTA package version 8.0.0.131 with Firmware Finder, placed it in the folder dload on my SDcard and started the intstallation in the project menu (accessible digiting *#*#2846579#*#* in the dialer), it started but suddenly it ended with a message "installation failed".
So my question is: how can i revert to the previous version of the software (or to the out of the box firmware installed on my device)?
Click to expand...
Click to collapse
You should have an option to downgrade in the about section/ the update menu of your phone if you did it right.
Otherwise you may need to use the HuRupdater Method.
Fredin_ said:
You should have an option to downgrade in the about section/ the update menu of your phone if you did it right.
Otherwise you may need to use the HuRupdater Method.
Click to expand...
Click to collapse
Thanks for your reply!
I don't have this option, but if I remember well I hadn't it also in the previous version of the firmware.
So i can't install a previous version of the firmware simply downloading it an putting into dload folder of the SDcard?
karmakey said:
Thanks for your reply!
I don't have this option, but if I remember well I hadn't it also in the previous version of the firmware.
So i can't install a previous version of the firmware simply downloading it an putting into dload folder of the SDcard?
Click to expand...
Click to collapse
Can you please specify why do you want to roll back?
Because most people just wanna upgrade to a newer version.Newwr versions will have better stability so it's recommended to keep the latest version unless you have some bugs.
I honestly don't know why the dload method doesn't work, seems that it doesn't work for most people.
I think you'll be able to roll back using HuRupdater. But that'll mean you'll have to unlock bootloader and flash twrp first. Then you can go all stock from there.
Here's a guide to the HuRupdater from @zxz0O0
https://www.google.co.in/amp/s/foru...lash-official-firmware-recovery-t3769279/amp/
Fredin_ said:
Can you please specify why do you want to roll back?
Because most people just wanna upgrade to a newer version.Newwr versions will have better stability so it's recommended to keep the latest version unless you have some bugs.
I honestly don't know why the dload method doesn't work, seems that it doesn't work for most people.
I think you'll be able to roll back using HuRupdater. But that'll mean you'll have to unlock bootloader and flash twrp first. Then you can go all stock from there.
Here's a guide to the HuRupdater from @zxz0O0
https://www.google.co.in/amp/s/foru...lash-official-firmware-recovery-t3769279/amp/
Click to expand...
Click to collapse
After installing the version 132 I asked the technical support through HiCare and they told me that installing firmware with Firmware Finder could void warranty so I decided to revert to the previous firmware and wait for regular OTA by Huawei.
karmakey said:
After installing the version 132 I asked the technical support through HiCare and they told me that installing firmware with Firmware Finder could void warranty so I decided to revert to the previous firmware and wait for regular OTA by Huawei.
Click to expand...
Click to collapse
I'm not sure but I think you are on the latest build for your varient now so you won't be getting any updates untill a next build comes in.
I don't think you'll be able to roll back without the firmwares from firmware finder as you don't have an option to roll back.
The best option now would be to just wait for the next official build(might come soon as a small ota which has security patches) and then check if you are facing any issues installing which you won't as you are not rooted and dosent have an unlocked bootloader. So don't worry ?
Fredin_ said:
I'm not sure but I think you are on the latest build for your varient now so you won't be getting any updates untill a next build comes in.
I don't think you'll be able to roll back without the firmwares from firmware finder as you don't have an option to roll back.
The best option now would be to just wait for the next official build(might come soon as a small ota which has security patches) and then check if you are facing any issues installing which you won't as you are not rooted and dosent have an unlocked bootloader. So don't worry
Click to expand...
Click to collapse
Version 8.0.0.133 with July security patch just arrived and installed through official OTA!
karmakey said:
Version 8.0.0.133 with July security patch just arrived and installed through official OTA!
Click to expand...
Click to collapse
Good to hear you are up and running fine ?
Want to downgrade my honor 9 lite
After some update the theme engine crashed. Themes can no longer change the notiifcation bar icons and shortcuts icons.
Downgrading version Problem
I used firmware finder and dns method to downgrade my honor 9 lite and while i register update on firware finder and opens hisuite for update it is saying u r on already the latest version
Plz help me with downgrading my version 9 to 8
Hi
I'm unable to change the firmware on my BLA-L29 C432 B142 May security patch (rebranded from C636 about 6 months ago).
Checking OTA just says 'no updates available' and if I try to update via FunkyHuawei using eRecovery it downloads but after 'verifying' it moves on to 'recovery system running' and then errors with the message 'recovery failed' when it gets to 1%.
I've tried quite a few things to try and get something to move on, but it seems like I'm stuck on an old version of firmware and no way to change it. I need a new plan.
I've tried (with lots of factory resets and wiping cache inbetween):
- OTA updates - always says no update available.
- Via FunkyHuawei:
- Reflash same firmware (eRecovery fails during 'recovery system running')
- Reflash newer or older firmare in same region (eRecovery fails during 'recovery system running')
- Change region, reflash newer or older firmware in same region (eRecovery fails during 'recovery system running')
- Use unbrick tool to flash same or different firmware in both same and different regions (unbrick tool completes but firmware version always stays the same in about phone, the android security patch date changes though, but eRecovery won't let me reflash anything afterwards as eRecovery fails during 'recovery system running')
- The last OTA update I got was C432 .137. When everyone else was getting .145 OTA I got Firmware Finder to move me from .137 to .142.
Has anyone got any ideas on what to do next? I don't want to be stuck on the same firmware version and security patch forever.
Other than the FunkyHuawei rebrand about 6 months ago from C636 to C432, the phone is standard (no attempt to unlock bootloader, root).
I was thinking of:
- Unlock bootloader using DC unlocker (from what I've read this might still work as I'm on B142 which has a May security patch)
- Flash TWRP
- Flash a custom ROM
- Try and restore back to stock
- Possibly rebrand back to factory original C636 as there seem to be a few threads about rebranded phones not getting updates promptly, but I can't see anyone else who is getting eRecovery failing no matter what they do and no way to change firmware. I have already tried rebranding back to C636 via FH, but can't, as eRecovery fails at the same point when trying to flash the C636 firmware.
Funky should always work to update, check that DNS is correct when you enter that test site.
- Unlock bootloader using DC unlocker (from what I've read this might still work as I'm on B142 which has a May security patch)
Click to expand...
Click to collapse
This will work. I have downgraded and tested it
You could do this:
Get unlock code
Unlock bootloader
Flash TWRP (https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904)
Download firmware update.zip, public and hw zip from http://pro-teammt.ru/firmware-database/
Update to the version you want using HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279).
You will stay bootloader unlocked now though, but the rest is stock.
ante0 said:
Funky should always work to update, check that DNS is correct when you enter that test site.
Click to expand...
Click to collapse
The DNS is fine and I can load the test sites, eRecovery gets info and downloads the firmware labelled "FunkyHuawei" and the size is around 3GB. After taking a few minutes to download, the eRecovery moved on to 'verifying package', that completes, it moves on to 'recovery system running' and after it gets to 1% it says 'recovery failed'.
ante0 said:
This will work. I have downgraded and tested it
You could do this:
Get unlock code
Unlock bootloader
Flash TWRP (https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904)
Download firmware update.zip, public and hw zip from http://pro-teammt.ru/firmware-database/
Update to the version you want using HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279).
You will stay bootloader unlocked now though, but the rest is stock.
Click to expand...
Click to collapse
I will try this, anything to get me out of the hole I seem to be stuck in as all methods I've tried so far rely on eRecovery. Thankyou for all of the links.
When using HuRUpdater does it have to be in the same region, or can I rebrand at the same time?
Thasscas44 said:
The DNS is fine and I can load the test sites, eRecovery gets info and downloads the firmware labelled "FunkyHuawei" and the size is around 3GB. After taking a few minutes to download, the eRecovery moved on to 'verifying package', that completes, it moves on to 'recovery system running' and after it gets to 1% it says 'recovery failed'.
I will try this, anything to get me out of the hole I seem to be stuck in as all methods I've tried so far rely on eRecovery. Thankyou for all of the links.
When using HuRUpdater does it have to be in the same region, or can I rebrand at the same time?
Click to expand...
Click to collapse
HuRUpdater can only handle same region updates as far as I know.
You can use HWOTA to rebrand, but mankindtw (original author) has since edited the thread as he thought his tool bricked devices. But it was firmware that caused it.
And I can't remember the exact steps... You have to flash twice though, first to rebrand (example C636) and then to update to the same rebranded (C636) firmware.
https://mega.nz/#!oeATEQQb!qiP3mYlQQgZYlaS3dbY_QCwNJ-urTKyLQ2zKOA9KP8g
You could use FHRebrand tool, but it will change your bootloader unlock code so you'd have to use HCU client (DC-unlocker) twice to get it.
Also, before flashing anything, check xloader with this tool: https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
For now, stay on XLOADER 01 firmware. We don't know if Huawei will change to 02. Going from 02 to 01 will end in a hard brick.
B142 is 01 so you're safe now
Thanks to your advice, I have a plan now. And good to know about the xloader stuff, that could have ruined my day.
I'm going to:
1. Get bootloader code [update: done using dc-unlocker, confirmed working on C432 .142]
2. Flash TWRP
3. Put same region and slightly downgraded version of firmware on to a USB and flash with HuRUpdater (assuming it needs to be put on a USB OTG stick as the M10Pro doesn't have an SD card). I intend to use the downgraded version so I can see the version successfully change in "about phone"
4. Rebrand using FH tool (if there's less chance of bricking than HWOTA) and keeping an older firmware
5. Hopefully it works, and [after getting the bootloader code again from dc-unlocker in case I need it in future] I will be able to update via OTA to latest official firmware
Hopefully starting again completely will overwrite whatever it is that's getting me stuck.
Thanks to @ante0 I got out of the hole I was in.
From what I've tested, there seems to be an inability to update OTA from a rebranded BLA-L29 432 running 137 or 142.
Here's what I did.
1. Unlocked bootloader, flashed twrp, flashed downgraded 137 version of C432 with hrupdater. Success. No offer of an OTA update though so still stuck on old version.
2. Ran FH rebrand tool to change region to the factory original C636. eRecovery failed at the same stage as before. Fail.
3. Kept region as C636, unlocked bootloader and flashed twrp again. Flashed April version of C636 firmware using hrupdater, twice. Success.
4. Immediately on boot up phone offered to update OTA to the latest version of C636 firmware. Success.
It seems that the phone wouldn't offer an update OTA if on rebranded C432 and running 137 or later, but did offer OTA when it was back on C636. I live in Europe, but will keep the 636 region if it means I get OTA, else I can't pass the phone on.
Now to relock the bootloader so banking apps work. Plan to use the fastboot relock command followed by dc unlocker relock tool. Hoping not to brick at the last stage!
This tool will help you upgrade from EMUI 9.0 to EMUI 9.1 .
Requirements:
- Unlocked Bootloader
- A rooted device (if you don't have root use the TWRP EMUI_9.1_Flasher tool.Bootloader unlock is required))
- ADB Debug enabled
- A PC with Windows OS
- EMUI 9.1 FullOTA firmware
- Ability to follow some simple on-screen instructions
Credits:
@ante0 - for the new Pie based no-check recovery --> you should thank him here
all the others that contributed to this tool
Instructions:
- Download and extract the tool
- Connect your device to the PC and make sure ADB Debugging it's enabled
- Launch the Flash.bat
- Follow the on-screen instructions
Download
EMUI9.0_to_9.1_update_tool.zip
EMUI9.0_to_9.1_update_tool_root.zip -- This version will also install Magisk 19.3 Stable - Magisk Manager it's optional and can be skipped
EMUI_9.0_to_9.1_update_tool_root_3_files.zip -- This version will allow you to flash the base firmware,cust and preload.Obviously,you can skip the Magisk part if you want
TWRP EMUI_9.1_Flasher -- This tool won't require a rooted device
EMUI_9_0_TWRP_Flash_Unbrick_Tool.zip -- Use this tool to flash an EMUI 9.0 firmware if your device is soft bricked and is no longer booting to EMUI OS
Firmwares Collection :
BLA-L29 C432 - 9.1.0.300 - > https://forum.xda-developers.com/mate-10/how-to/firmware-version-mate-10-t3722019/post79923909
BLA-L09 C432 - 9.1.0.300 -> https://forum.xda-developers.com/showpost.php?p=79932379&postcount=14 <- base firmware it's the same as BLA-L29
Hello (i have a mate 10 pro on 9.0 with root),
for fullOTA rom, i use FF to find one, BLA-LGRP2-OVS 9.1.0.303, but links for 3 differentes sizes (3.46, 3.4, 3.49GB) of ROM??
my phone will be rooted again? If not ? can you please tell me how to be root again?
is there some issue with 9.1 ROM?
how can i roll back if need?
Thanks for your job.
syd-3 said:
Hello (i have a mate 10 pro on 9.0 with root),
for fullOTA rom, i use FF to find one, BLA-LGRP2-OVS 9.1.0.303, but links for 3 differentes sizes (3.46, 3.4, 3.49GB) of ROM??
my phone will be rooted again? If not ? can you please tell me how to be root again?
is there some issue with 9.1 ROM?
how can i roll back if need?
Thanks for your job.
Click to expand...
Click to collapse
Hi! I don't know which version it's fine for your device and the only way to know it it's to flash it yourself, but i don't recommend you to do that.
Rooting with Magisk is fine on 9.1, just read the latest posts from this thread - > https://forum.xda-developers.com/mate-10/how-to/guide-magisk-root-mate-10-pro-t3886967/page27
As for the roll-back, ut should be possible to do it with this tool and an appropriate roll-back firmware (again, firmware version might depend on your cust/brand).
I recommend you to keep an eye and also read this thread - > https://forum.xda-developers.com/mate-10/how-to/firmware-version-mate-10-t3722019
Tried this but for some reason it fails when checking firmware on my bla-a09 tried all 4 firmwares on FF
tokoam said:
Tried this but for some reason it fails when checking firmware on my bla-a09 tried all 4 firmwares on FF
Click to expand...
Click to collapse
B303 is not for A09, it's for C800 which is some jp cust.
Most new fw links are not up yet, and since Huawei decided to name all their firmware the same regardless of model its hard to know which is which :/
Success! Updated BLA-L29C432. Thank you!
Krasimir said:
Success! Updated BLA-L29C432. Thank you!
Click to expand...
Click to collapse
Great! Soon i will upload a new version that will also flash the patched Magisk ramdisk_recovery and Magisk Manager (this one will be optional, so those who already have it, can skip it).
It worked for me also.
Why is root needed? Unlocked bootloader is not enough?
criszz said:
Why is root needed? Unlocked bootloader is not enough?
Click to expand...
Click to collapse
Nope! Well, it can be done without root too, but it would require twrp in that case.
Firmware for Bla-l09c432 ?
MagicBox96 said:
Firmware for Bla-l09c432 ?
Click to expand...
Click to collapse
Somewhere on Huawei's servers! xD
I found a firmware on Easy Firmware, bla-l09 c432 b300 but I don't know if it can be obtained for free or secure, you have nothing?
MagicBox96 said:
I found a firmware on Easy Firmware, bla-l09 c432 b300 but I don't know if it can be obtained for free or secure, you have nothing?
Click to expand...
Click to collapse
as stated before, since every update is named the same it's hard to tell which is L09, L29, A09 or AL/TL. AL/TL are easier as VERSION.mbn in UPDATE.zip doesn't have Global strings in it.
From what it seems, if you flash L09 on L29 or vice versa you get endless OTA updates for preload and cust. I don't know if just flashing the cust and preload zips fixes it, but you're free to try if you want.
Here's L09 preload and cust:
Preload: http://update.hicloud.com:8180/TDS/...full/update_full_preload_BLA-L09_hw_eu_R1.zip
Cust: http://update.hicloud.com:8180/TDS/...4//f1/full/update_full_cust_BLA-L09_hw_eu.zip
modified tool to include preload and cust:
https://mega.nz/#!oDR2DYCI!SRQlTq1IriGcEt1Wr--ggrBk7uZ4M_R8OwE6DdvmEEc
Extract and put in the EMUI 9.0 to 9.1 update folder.
Rename cust zip to update_cust.zip and preload to update_preload.zip, put in ZIPS-HERE folder, run modified bat.
Thank you very much, I try very soon. Have any of you done that already?
MagicBox96 said:
Thank you very much, I try very soon. Have any of you done that already?
Click to expand...
Click to collapse
I did on L29 with L29 preload and cust, no problems.
Base (280955) seem to be the same for both L09 and L29 C432.
MagicBox96 said:
Thank you very much, I try very soon. Have any of you done that already?
Click to expand...
Click to collapse
Soon i will upload a new tool that will let you flash all the 3 files, so you could wait. Also, a fried of mine is testing on BLA-L09 C432.
Perfect, also because I don't have the Root permissions on the device, and I don't even have twrp. In fact now I have tried and says that it does not find root permissions. Then I did not understand if the phone should be connected from on, in recovery or fastboot?
MagicBox96 said:
Perfect, also because I don't have the Root permissions on the device, and I don't even have twrp. In fact now I have tried and says that it does not find root permissions. Then I did not understand if the phone should be connected from on, in recovery or fastboot?
Click to expand...
Click to collapse
Tool updated. However, if you don't have root, you can't use it, you must root first.
Okay, I thought it was a tool like the ones we made earlier to install EMUI 9. I'll wait until the new tool is released. : D