Related
[Guide] Huawei P10 Plus Debrand/Rebrand/Update for Oreo&Nougat "Updated 25.03.2018"
[Guide] Huawei P10 Plus Debrand/Rebrand/Update for Oreo&Nougat
This thread will be discontinued, because Huawei refuses to provide unlock codes in the future, because of security reasons.
A shame that after the support end of the device it will be quite useless, cause you don´t get any security updates and have no chance to make secure again, by flashing someting else.
I recommend you not buy any Huaweidevices in the future cause of that.
Here´s my P10 Guide, the steps are the same for the P10 Plus: Huawei P10 Plus Debrand/Rebrand/Update for Oreo&Nougat
Just use the following files for the P10 Plus instead:
TWRP for P10 Plus
@AndroidFilehost: HWOTA_VKY-L29C432_B365.zip (Oreo) MD5: 0858c05a98053ad5043dfaf7041ec54e
@Mega: HWOTA_VKY-L29C432_B360.zip (Oreo)
@Mega: HWOTA_VKY-L29C432_B177.zip (Nougat)
Doesn't work on a converted single sim UK P10 plus to dual sim. Used this method to go back to B123 to get the phone to work. It was showing a different model number each time I tried to update to B177 using this method.
abdulhamid1978 said:
Doesn't work on a converted single sim UK P10 plus to dual sim. Used this method to go back to B123 to get the phone to work. It was showing a different model number each time I tried to update to B177 using this method.
Click to expand...
Click to collapse
Did you already use this method before? Seems you messed up with the 1 of the 3 updatefiles. Especially the update_all_hw.zip which is only for the l29 or l09.
Did you try to update via firmware finder and did you make check with imei in that tool? That should fix your problems, if you use the FullOTA.
LwannaCM said:
Did you already use this method before? Seems you messed up with the 1 of the 3 updatefiles. Especially the update_all_hw.zip which is only for the l29 or l09.
Did you try to update via firmware finder and did you make check with imei in that tool? That should fix your problems, if you use the FullOTA.
Click to expand...
Click to collapse
The FULLOTA in firmware finder says 'The firmware is not approved for installation'.
I have VKY-L09C432 which I converted to VKY-L29C432 and was on B170. I used the 3 update files from the the link you provided in step 2 'HWOTA_VKY-L29C432_B177.zip'. Was I supposed to change any of these files?
abdulhamid1978 said:
The FULLOTA in firmware finder says 'The firmware is not approved for installation'.
I have VKY-L09C432 which I converted to VKY-L29C432 and was on B170. I used the 3 update files from the the link you provided in step 2 'HWOTA_VKY-L29C432_B177.zip'. Was I supposed to change any of these files?
Click to expand...
Click to collapse
No, i think you just haven´t read the guide carefully. In firmwarefinder choose an older one, that is approved for installation.
LwannaCM said:
No, i think you just haven´t read the guide carefully. In firmwarefinder choose an older one, that is approved for installation.
Click to expand...
Click to collapse
I am back on L29C432B170 via normal OTA.
Probably messed up on 2. Run the update.bat file from a preopended CMD with adminrights, It will ask you if you copied the files. Press any key to continue.
I just ran update.bat file as an administrator. That was the only thing I did differently to the guide.
Hello guys!
So I recently bought a "Huawei P10 Plus VKY-AL00 6GB RAM 128GB Dual-Sim" from China. I want to rebrand this model to "Huawei P10 Plus VKY-L29 6GB RAM 128GB Dual-Sim". Ive unlocked bootloader. So what shall I do now ? This tutorial above is for the european model. Please help me thx!
No connection to the mobile network after rebranding
Hi
I went through all your described steps and everything worked fine. However, I've got a strange problem.
I have different SIM cards available (multiple mobiles), but only one (prepaid from croatia) is working after the procedure. The ones from Vodafone Germany and Swisscom do not work.
They work fine on other mobiles. Everything else is working fine on the P10+. The SIMs not working, are displayed in the phone, but will not connect to the mobile network of any provider.
No available networks are listed. Both SIM-slots tested.
Any idea, where the problem could come from?
Thanks for your help.
how to convert VKY-L09C432 dual sim to single sim?
Sorry for stupid question. I'm having VKY-AL00 with B217 firmware. I guess soon I will update it to Oreo. Am I still capable for rebranding?
yukato said:
Sorry for stupid question. I'm having VKY-AL00 with B217 firmware. I guess soon I will update it to Oreo. Am I still capable for rebranding?
Click to expand...
Click to collapse
You can still rebrand, but AL00 is already dual sim if that's what you were after.
---------- Post added at 10:05 PM ---------- Previous post was at 10:03 PM ----------
Gamkutopolowk said:
how to convert VKY-L09C432 dual sim to single sim?
Click to expand...
Click to collapse
There's a walkthrough for using HWOTA to rebrand to the L29 model: https://forum.xda-developers.com/p1...nvert-to-dualsim-huawei-p10-plus-vky-t3605071 Works very well, changed my Fido/Rogers L09 without any issues. The instructions can be a little confusing but you should be ok if you've flashed phones before.
singularoctopi said:
You can still rebrand, but AL00 is already dual sim if that's what you were after.
Click to expand...
Click to collapse
I'm thinking to go from chinese to european firmware may be The reason is I can't turn my location history ON in Google Maps And It seems I'm still having some notification problems.
TWRP not working
Hi,
I can't get TWRP to work on my VKY-L29. Everytime I try to get in TWRP, I get into the normal Huawei recovery again. Phone's Bootloader is definitely unlocked and it also says that writing the TWRP was sucessful. I followed all the steps as they're written. Any thoughts on how to fix this?
Rommco05 said:
Unplug phone from cable and turn off. Turn on with holding vol up+power button, when u feel vibration release power button and vol up
Click to expand...
Click to collapse
when I do that i get to the screen saying: phone is unlocked an can't be trusted... If I then prss volume up to enter TWRP I still get into the Huawei eRecovery.
I have p10 plus VKY-L09 with C55B140 (Tim IT brand) and with firmware finder i check for C432B175 and firmware finder say it's aproved for installation...
So, it's fine to update/instal?
bondaru18 said:
I have p10 plus VKY-L09 with C55B140 (Tim IT brand) and with firmware finder i check for C432B175 and firmware finder say it's aproved for installation...
So, it's fine to update/instal?
Click to expand...
Click to collapse
I don't know what to tell you...I got firmware finder as well but my latest update was 2 days ago and now i got B177.The chinese phones already got Oreo update (yesterday,two days ago). I recomand you to not update yet,use HiSuite and connect your phone to your pc.I did get B170 using the cable and having installed on my pc HiSuite,so good luck.
Hello,
Tried following the guide but now my phone VKY-L09 shows up as a NRD90M with 2GB of RAM. followed the procedure many times now but still with the same results.
Doing the rebrand seems to work (if i do it twice on the update script it shows VKY-L29C432 but after booting up it still is NRD90M.
I can boot to fastboot/twrp/erecovery without issues.
Used this file HWOTA_VKY-L29C432_B177.zip
I am from Portugal and only need for the phone to have Dual Sim
Mike69pt said:
Hello,
Tried following the guide but now my phone VKY-L09 shows up as a NRD90M with 2GB of RAM. followed the procedure many times now but still with the same results.
Doing the rebrand seems to work (if i do it twice on the update script it shows VKY-L29C432 but after booting up it still is NRD90M.
I can boot to fastboot/twrp/erecovery without issues.
Used this file HWOTA_VKY-L29C432_B177.zip
I am from Portugal and only need for the phone to have Dual Sim
Click to expand...
Click to collapse
Guys I really need some help on this please. It's the only phone I have.
Mike69pt said:
Guys I really need some help on this please. It's the only phone I have.
Click to expand...
Click to collapse
Had a similar issue. Got round it by following this guide to rebrand then used the firmware finder app to install the latest available vky-l29 update. After that I unlocked bootloader again and flashed twrp and installed magisk.
baddesthad said:
Had a similar issue. Got round it by following this guide to rebrand then used the firmware finder app to install the latest available vky-l29 update. After that I unlocked bootloader again and flashed twrp and installed magisk.
Click to expand...
Click to collapse
Could you please give me some more details on how to do this? When i rebrand using this guide and boot it's got the nrd90m
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!
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
My huawei p9 Eva l19 keeps restarting and fail software. Please help.
Phone unlocked.
The video https://streamable.com/71z5e
Thanks.
danro28 said:
My huawei p9 Eva l19 keeps restarting and fail software. Please help.
Phone unlocked.
The video https://streamable.com/71z5e
Thanks.
Click to expand...
Click to collapse
Bootloop doesn't happen by itself - to get help you must describe which stock/custom firmware you had, were you flashing another firmware and which or trying to root, or you were changing something under root before it started to happen
Solution to unbrick highly depends on the firmware, etc - for firmware is needed full model, cust and number
Btw, does it boot to Fastboot, EMUI Recovery (or you flashed custom Recovery TWRP) or eRecovery?
The Phone model is Eva l19.
The software is shown în The video
The bootloader is unlocked and s-o is The frp.
I tried various versions of The software but The result was The same. Using The method update.app it was working to 5%, The says 6% and then back 5 % and then erron instalation.
danro28 said:
The Phone model is Eva l19.
The software is shown în The video
The bootloader is unlocked and s-o is The frp.
I tried various versions of The software but The result was The same. Using The method update.app it was working to 5%, The says 6% and then back 5 % and then erron instalation.
Click to expand...
Click to collapse
Too small and not sharp - can you write what is your firmware version on your phone
Eva-l19c432b388
You say you were installing various firmwares - if you did, specially if you maybe combined various custs, then it was a road to mess
I would suggest you to carefully study posts OP #1 and #2 from HWOTA7 thread
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Forget (at the moment - later you could do if you wish but once you solve your Nougat) about changing cust and upgtading to Chinese Nougat.
Use the HWOTA7 method instead to change the cust/location to c432 (to clean up) and to install one of the latest FullOTA-MF stock firmwares, eg L19c432b505 or so
Be careful, use L19 only if your P9 is dual SIM, otherwise must be L09
Follow every detail (but adapted to your case), including Factory Reset and Wiping Cache at the end
I tried this method but i can't recover bootloader Code because hcu client doesn't work on my pc.
Win 10 64 bit.
Could you conect to my pc and help ME fix my Phone?
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.