Hello,
I was on B360 Oreo.
I unlocked bootloader, flashed TWRP, used MAGISK (16) to modify boot(ramdisk) partition, flashed it and got ROOT.
Then I flashed HYPER KERNEL.
Now i realised that custom kernel gives me nothing special in term of battery life (after 7 days) so i flashed back all stock partitions (BOOT, RECOVERY, KERNEL).
Now I am on stock, but with bootloader unlocked.
So i can get updates, but no ANDROID PAY.
The TASK is: How to lock bootloader. I mean LOCK not RELOCK.
ON nougat when i used the HWOTA to debrand my device the device was automatically locked after the change.
Now on HWOTA8 i flashed all three parts of the B360 full ota to get the bootloader locked, but still unlocked.
I think to erase and flash OEMINFO again, but i am afraid to brick the device by that.
Does anybody know how to make forced update that the bootloader will lock?
@Blackball maybe?
Actually the only way i discover to do this is, go Back to nougat, and the update vía firmware Finder vía proxy while you had your bootloader locked after rebranding again, Cheers brother
will try to update via firmware finder from b360 to b365 full firmware. Will see.
How this went for You?
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).
So I did a hard reset after relocking my bootloader in order to install my new update (EVA-L09C150B375). I successfully relocked it, then resetted it. However, after I turned it on to install the update and restore it from HiSuite, I was welcomed with the EMUI starting screen (language selection, T&C, wifi, google account) and I'm stuck there. The thing is, all my keyboards are lost and whenever I want to type in something, only the google voice button shows which I can't possibly use to enter passwords or pin. If I skip everything and 'set up as new phone', it brings me to the 'add fingerprint' scene which if I skip, I'm brought all the way back to the beginning of the WHOLE proccess (back to the EMUI logo), and I can't add a fingerprint because you have to give either a PIN or a password in order to be able to use it. I have Wi-fi connection but nothing else. I can't bring up any menus. When I do a hard reset, it bring me to this page again after rebooting. Is there a workaround? I'm completely lost.
horesz1994 said:
So I did a hard reset after relocking my bootloader in order to install my new update (EVA-L09C150B375). I successfully relocked it, then resetted it. However, after I turned it on to install the update and restore it from HiSuite, I was welcomed with the EMUI starting screen (language selection, T&C, wifi, google account) and I'm stuck there. The thing is, all my keyboards are lost and whenever I want to type in something, only the google voice button shows which I can't possibly use to enter passwords or pin. If I skip everything and 'set up as new phone', it brings me to the 'add fingerprint' scene which if I skip, I'm brought all the way back to the beginning of the WHOLE proccess (back to the EMUI logo), and I can't add a fingerprint because you have to give either a PIN or a password in order to be able to use it. I have Wi-fi connection but nothing else. I can't bring up any menus. When I do a hard reset, it bring me to this page again after rebooting. Is there a workaround? I'm completely lost.
Click to expand...
Click to collapse
First of all, unlocked bootloader does not prevent OTA - for OTA you must have stock recovery and stock boot partition (no root) but you can have bootloader unlocked.
Only thing - successful OTA may lock your bootloader back (depending if such a flag is present in stock update.zip or not) but again, you can safely start OTA with the unlocked bootloader.
Don't know why so many people go to relock bootloader before accepting OTA, which triggers hard reset and potentially troubles.
Did you at least leave OEM unlocked (OEM/FRP unlock also does not prevent OTA), that you can unlock bootloder again, install TWRP and revive your system by eg HWOTA method?
About missing keyboard - when you had your previous rooted system, have you disabled/removed Huawei default keyboards: SwiftKey and Swipe for Huawei - after hard reset it looks only for them, without them you have no keyboard...
Also, before hard resetting, have you removed fingerprint protection you have had?
Generally, if you removed fingerprint before hard reset, you should be able to skip setting the fingerprint.
I had a similar situation (no keyboard upun hard reset), and I was able to skip fingerprint, set-up a new system and then to install GBoard from apk on SD card and to continue.
zgfg said:
First of all, unlocked bootloader does not prevent OTA - for OTA you must have stock recovery and stock boot partition (no root) but you can have bootloader unlocked.
Only thing - successful OTA may lock your bootloader back (depending if such a flag is present in stock update.zip or not) but again, you can safely start OTA with the unlocked bootloader.
Don't know why so many people go to relock bootloader before accepting OTA, which triggers hard reset and potentially troubles.
Did you at least leave OEM unlocked (OEM/FRP unlock also does not prevent OTA), that you can unlock bootloder again, install TWRP and revive your system by eg HWOTA method?
About missing keyboard - when you had your previous rooted system, have you disabled/removed Huawei default keyboards: SwiftKey and Swipe for Huawei - after hard reset it looks only for them, without them you have no keyboard...
Also, before hard resetting, have you removed fingerprint protection you have had?
Generally, if you removed fingerprint before hard reset, you should be able to skip setting the fingerprint.
I had a similar situation (no keyboard upun hard reset), and I was able to skip fingerprint, set-up a new system and then to install GBoard from apk on SD card and to continue.
Click to expand...
Click to collapse
I couldn't install the new update when I was unlocked, because it went into a boot loop. That's why I decided to start over with a clean page. I haven't disabled any keyboards and I haven't removed my fingerprint.
horesz1994 said:
I couldn't install the new update when I was unlocked, because it went into a boot loop. That's why I decided to start over with a clean page. I haven't disabled any keyboards and I haven't removed my fingerprint.
Click to expand...
Click to collapse
You couldn't install OTA not because of unlocked bootloader per se, but because of TWRP or root.
You better had to remove fingerprint before forcing to relock bootloader.
Did you leave OEM (FRP) unlocked (it doesn't affect OTA anyhow) - then boot to Fastboot, unlock bootloader, install TWRP and use HWOTA to flash complete firmware
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Otherwise, if you could get over fingerprint, boot to the system and install GBoard (download the apk on the PC or another phone and put it to the SD card)
Last option, rollback to MM and then upgrade by OTAs to the latest Nougat.
zgfg said:
You couldn't install OTA not because of unlocked bootloader per se, but because of TWRP or root.
You better had to remove fingerprint before forcing to relock bootloader.
Did you leave OEM (FRP) unlocked (it doesn't affect OTA anyhow) - then boot to Fastboot, unlock bootloader, install TWRP and use HWOTA to flash complete firmware
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Otherwise, if you could get over fingerprint, boot to the system and install GBoard (download the apk on the PC or another phone and put it to the SD card)
Last option, rollback to MM and then upgrade by OTAs to the latest Nougat.
Click to expand...
Click to collapse
The problem is, I have no way of accessing the file system.
Take out SD card, put on DLOAD for rollback to MM.
zgfg said:
Take out SD card, put on DLOAD for rollback to MM.
Click to expand...
Click to collapse
I will try this, thank you! where can I find the correct rom for my phone model?
horesz1994 said:
I will try this, thank you! where can I find the correct rom for my phone model?
Click to expand...
Click to collapse
Firmware Finder
zgfg said:
Firmware Finder
Click to expand...
Click to collapse
Okay, so I've tried b136 and b167 (the two most common in these solutions in this forum), and both of them went to 5% and then came an error message:
“Incompatibility with current version. Please download the correct update package”
I'm truly lost now. Any ideas? Should I try every single package for the L09?
horesz1994 said:
Okay, so I've tried b136 and b167 (the two most common in these solutions in this forum), and both of them went to 5% and then came an error message:
“Incompatibility with current version. Please download the correct update package”
I'm truly lost now. Any ideas? Should I try every single package for the L09?
Click to expand...
Click to collapse
Here is a proven rollback guide
https://forum.xda-developers.com/showpost.php?p=73448165&postcount=371
Skip steps 7-8.
In step 9 you should get OTA updates till b504 for L09 (b399 for L19).
Steps 11-13 are about rooting by SuperSU, not part of rollback.
PS: This guide is for L09/L19 c432 - if your phone was diff cust, you should rebrand or use b182 for your cust (not b182 for c432 as in the guide - you should look for the appropriate FullOTA-MF-PV build in Firmware Finder - MUST be FullOTA-MF-PV MM for your cust)
zgfg said:
Here is a proven rollback guide
https://forum.xda-developers.com/showpost.php?p=73448165&postcount=371
Skip steps 7-8.
In step 9 you should get OTA updates till b504 for L09 (b399 for L19).
Steps 11-13 are about rooting by SuperSU, not part of rollback.
PS: This guide is for L09/L19 c432 - if your phone was diff cust, you should rebrand or use b182 for your cust (not b182 for c432 as in the guide - you should look for the appropriate FullOTA-MF-PV build in Firmware Finder - MUST be FullOTA-MF-PV MM for your cust)
Click to expand...
Click to collapse
Will do, but I have one more question; how do I find out my model number(cust)? the box only shows the IMEI and that it's EVA-L09 and nothing else. I can't access phone details in the phone itself because of the original problem.
I see for my L09c432 in this file:
/cust/hw/eu/prop/local.prop
at the end:
ro.comp.cust_version=Cust-432000 5.0.0.1(0001)
You can probably (never did myself) copy it by ADB commands to PC and read.
Maybe you need to unlock bootloader to get access.
In that case you can also install TWRP and copy the file to SD card, and then open it on the PC
PS: I usually save screenshots to the cloud with Build info (About), IMEI, etc...
zgfg said:
I see for my L09c432 in this file:
/cust/hw/eu/prop/local.prop
at the end:
ro.comp.cust_version=Cust-432000 5.0.0.1(0001)
You can probably (never did myself) copy it by ADB commands to PC and read.
Maybe you need to unlock bootloader to get access.
In that case you can also install TWRP and copy the file to SD card, and then open it on the PC
PS: I usually save screenshots to the cloud with Build info (About), IMEI, etc...
Click to expand...
Click to collapse
The guide you posted earlier worked! currently at b182, but haven't received any OTA yet (strange...). I'm now waiting for google play to update and install all the necessary apps though. Thank you, Thank you and THANK YOU!
So, is it normal that I'm now stuck on EVA-L09C900B182 ? Firmware finder is not working (not downloading, always getting error), and the stock huawei updater can't find any updates, so I'm now at emui 4.1.1. Will I receive those updates and should I wait, or should I flash from sd card the dload method?
Oh, and HiSuite also tells me that I use the newest update.
horesz1994 said:
So, is it normal that I'm now stuck on EVA-L09C900B182 ? Firmware finder is not working (not downloading, always getting error), and the stock huawei updater can't find any updates, so I'm now at emui 4.1.1. Will I receive those updates and should I wait, or should I flash from sd card the dload method?
Oh, and HiSuite also tells me that I use the newest update.
Click to expand...
Click to collapse
For OTA you must have SIM and must not be in Airplane mode.
It may take few hours or up to a day - it depends on your mobile operator.
Beginning of this year, last time I did rollback, I got b203 (if recalling correctly), then b383 or b387, then up to b398 (at that time).
Give it a try. Otherwise use DLOAD (use FF only for download), you must use FullOTA-MF-PV builds, only those work for DLOAD
zgfg said:
For OTA you must have SIM and must not be in Airplane mode.
It may take few hours or up to a day - it depends on your mobile operator.
Beginning of this year, last time I did rollback, I got b203 (if recalling correctly), then b383 or b387, then up to b398 (at that time).
Give it a try. Otherwise use DLOAD (use FF only for download), you must use FullOTA-MF-PV builds, only those work for DLOAD
Click to expand...
Click to collapse
okay, I'll wait til tomorrow. But the shady part is that even HiSuite can't find an update, what does my operator have to do with this?
I don't know how it depends on Huawei, ypur IMEI, SIM card... but once I was similarly waiting and both HiSuite and System Update told me I had the latest, and then same day later I got OTA push
Oops, sorry, I have overlooked that you say you are now on c900, not c432.
There are no OTA updates for c900
I assuned you have followed the rollback guide as above, didn't you - the guide included c432 b182 (not c900 b182), in which case you should have been getting c432 OTA updates
zgfg said:
Oops, sorry, I have overlooked that you say you are now on c900, not c432.
There are no OTA updates for c900
I assuned you have followed the rollback guide as above, didn't you - the guide included c432 b182 (not c900 b182), in which case you should have been getting c432 OTA updates
Click to expand...
Click to collapse
Yes, I followed that guide, and I don't understand why I'm on c900. Can you help getting me out of this situation? Private message convo is fine by me too.
horesz1994 said:
Yes, I followed that guide, and I don't understand why I'm on c900. Can you help getting me out of this situation? Private message convo is fine by me too.
Click to expand...
Click to collapse
Follow the guide
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
I have a Huawei P9 that doesn't seem to receive updates.
EMUI 4.1.1
Build: EVA-L09C900B182
Andriod: 6.0
I have tried using firmware finder but I always get checksum failed before it passes 1%.
I had a look through the Forums and it seems that people recommend rebranding though that was in 2017.
I was wondering if there is any easy way to update?
I am a noob so i want to try avoid rooting and rebranding if possible.
Has anyone managed to update this?
2 years later and I'm still trying...
focussss said:
Has anyone managed to update this?
2 years later and I'm still trying...
Click to expand...
Click to collapse
For c900 there is no newer firmware.
Flashing anything else than c900 means rebranding - but rebranding requires unlocking Bootloader (not 'rooting')
So wandering, what are you really trying to do for two years?!
- Unlock Bootloader (4 Euros):
https://www.dc-unlocker.com/
- Rebrand properly to be able to update to Nougat eg EVA-L09c432b504:
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
I followed that guide but now my phone is stuck on "Type the password to decrypt storage" when I enter my Google password it says it's correct but data on my phone is corrupted. Any ideas?
focussss said:
I followed that guide but now my phone is stuck on "Type the password to decrypt storage" when I enter my Google password it says it's correct but data on my phone is corrupted. Any ideas?
Click to expand...
Click to collapse
Are you talking about TWRP asking for pass or Android?
If Android, on which firmware are you, what was the last step you performed?
Also, make sure you used TWRP for MM, not for Nougat - since you were on c900 MM when you started with rebranding to c432 (?)
Btw, you unlocked the Bootloader?
Thanks for the quick response and all your assistance. I managed to finally boot into EVA-L09C432B182 and will write what I did in the rebranding post for others who run into this issue. I still have no updates on L09C432B182 though.
focussss said:
Thanks for the quick response and all your assistance. I managed to finally boot into EVA-L09C432B182 and will write what I did in the rebranding post for others who run into this issue. I still have no updates on L09C432B182 though.
Click to expand...
Click to collapse
For OTA you must have a valid SIM card and WiFi - check manually to the System Update to trigger checking for an update
You can also try with HiSuite (PC) - latest versions of HiSuite have an option at the bottom to update the firmware
See:
https://huaweiflash.com/how-to-flash-huawei-stock-firmware-all-methods/
You can also update by DLOAD (read the guide above), you must download FullOTA-MF-PV (must be PV), like b360, from Firmware Finder
There is also HWOTA method, see:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Hi Guys,
I making this thread/guide because there is no where else an guide how to relock the bootloader.
In this example I'm having an unlocked bootloader sitting on firmware .238, what I want is to relock my bootloader is by doing an DOWNGRADE and not by an UPGRADE, yes it can be done also by an upgrade but that's not my point/guide.
Also by doing this you can reset the OTA / testing of your device.. For example if you sitting on the beta release of the firmware on the Mate 20 pro, with this method you can fully go back on the mainroad of the normal update progress through OTA.
By this method once you on a lower firmware you should get notified that there is an update for your current device through OTA.
Example; sitting on .238 (received from OTA) downgrading to .210 by dload, go to settings - software update - viola you get the new update of .238 on your phone.
This method will only discuss through the method of dload.
Requirements;
- Phone sitting on any firmware; In this example my phone sitting on 9.0.0.238 firmware
- ONLY works with an Service Firmware such as 9.0.0.210 firmware, this is necessary to be download from;
https://androidhost.ru/Uqv
- Having an OTG usb stick minimum 8GB
Steps;
1. Download the firmware from Androidhost.ru to download an Service Firmware for your device. Sitting on .238, so lets download the full version .210 (3.6GB)
https://androidhost.ru/Uqv
2. Unzip the downloaded.
3. Put the whole: 'dload' directory on the OTG usb-stick;
dload\
├─update_sd_base.zip
├─update_sd_cust_LYA-L29_hw_eu.zip
├─update_sd_preload_LYA-L29_hw_eu_R1.zip
4. Update / execute the update;
There are 2 ways to execute the software update is by doing the enter *#*#2846579#*#* -, and the ProjectMenu page will be displayed. Go to 4. Software Upgrade > 1. Memory card Upgrade> OK.
OR
Power off the phone, insert OTG disk, and press the VOLUME UP ,VOLUME DOWN key, and the POWER key at the same time. The phone enters the automatic upgrade mode, and the upgrade is started.
Give it time and voila, your are successfully downgraded and Safetynet gives all green passed.
CAUTION; USE ONLY AN SERVICE FIRMWARE, do not try any other firmware's.
Thanks me later.
Reserved.
Reserved.
Verstuurd vanaf mijn LYA-L29 met Tapatalk
I don't get it, why service firmware?
What stops from simply relocking in bootloader using same code that was used for unlock?
dimon222 said:
I don't get it, why service firmware?
What stops from simply relocking in bootloader using same code that was used for unlock?
Click to expand...
Click to collapse
An service firmware allows you to downgrade. It contains 3 package instead of 1.
Is causing the phone to get bricked by relocking the bootloader through the adb while being on the same firmware.
Verstuurd vanaf mijn LYA-L29 met Tapatalk
I was on 9.0.0.210 for months and stuck there. It depends on your region code whether it will work. On my region code it did not work and I could not do anything except load another dload version that was not compatible with my region. When 9.1 came out, Huawei manually flashed mine to a certified version for my region and I am back on track now. No more flashing for me.