Database Info

[TUTORIAL]How to update EVA-L09C636 (Asia-Pacific) model to B361 (EMUI 5)

I had been searching for a way to update my EVA-L09C636 (Asia-Pacific) model to EMUI 5.0. During the previous month I tried to install EVA-L09C636B361 firmware via either dload and Huawei Updater, but such means of direct installation never worked out.
Now the problem is solved, and the solution is quite simple, though a little bit unexpected: using Huawei Updater to install EVA-L19C636B190 before installing EVA-L09's own B361 firmware. I mean, it is interesting that we have to "borrow" the B190 firmware from the Dual SIM L19 model in order to update to EMUI 5.
(I'm not the first person to find the solution. I just found out that in a Taiwanese forum a tutorial is already posted. )
So there are two steps to install B361:
1.
Install EVA-L19C636B190 via Huawei Updater
Use Custom ROM URL
Copy and paste the link to EVA-L19C636B190:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v64578/f1/
Use the HiSuite on PC to finish the installation of B190 (Set its proxy to 127.0.0.1 and the port to 41279)
2.
Repeat the previous process, but this time, replace the link with the one to EVA-L09C636B361:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1256/g104/v73928/f1/
Again, use the HiSuite to finish the installation of B361
Note that the C636B190 version firmware for L19 model does run on L09 without the support of the L09-exclusive NFC. I think there should be a thread discussing this. Anyways, before official update comes out, the two steps above seem to be the only way to install EMUI 5 on the Asia-Pacific EVA-L09C636 version without losing data.

That is interesting, I dont have a C636 but I would assume just doing step 2 without the need to flash a L19B636 would do the trick.

whyhowie said:
I had been searching for a way to update my EVA-L09C636 (Asia-Pacific) model to EMUI 5.0. During the previous month I tried to install EVA-L09C636B361 firmware via either dload and Huawei Updater, but such means of direct installation never worked out.
Now the problem is solved, and the solution is quite simple, though a little bit unexpected: using Huawei Updater to install EVA-L19C636B190 before installing EVA-L09's own B361 firmware. I mean, it is interesting that we have to "borrow" the B190 firmware from the Dual SIM L19 model in order to update to EMUI 5.
(I'm not the first person to find the solution. I just found out that in a Taiwanese forum a tutorial is already posted. )
So there are two steps to install B361:
1.
Install EVA-L19C636B190 via Huawei Updater
Use Custom ROM URL
Copy and paste the link to EVA-L19C636B190:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v64578/f1/
Use the HiSuite on PC to finish the installation of B190 (Set its proxy to 127.0.0.1 and the port to 41279)
2.
Repeat the previous process, but this time, replace the link with the one to EVA-L09C636B361:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1256/g104/v73928/f1/
Again, use the HiSuite to finish the installation of B361
Note that the C636B190 version firmware for L19 model does run on L09 without the support of the L09-exclusive NFC. I think there should be a thread discussing this. Anyways, before official update comes out, the two steps above seem to be the only way to install EMUI 5 on the Asia-Pacific EVA-L09C636 version without losing data.
Click to expand...
Click to collapse
I was searching for this for months. I bought my p9 EVA-L09C636 in the US (I'm european) and I never had the chance to update, even at 4.1.1. I went crazy because I tried several times to unlock the bootloader first, installing twrp and flashing updates but with no success. It's unbelievable that I need to fake the version with huawei updater to obtain the updates for my phone. Now I've Nougat, without factory reset, with everything working, from nfc to all stock apps and services. Thank you very much

Z-Blade said:
That is interesting, I dont have a C636 but I would assume just doing step 2 without the need to flash a L19B636 would do the trick.
Click to expand...
Click to collapse
Well, in that case it keeps failing at 1%. I saw some previous posts talking about this as well.

Need Help
My model is Huawei P9 EVA-L09C636
I tried to update like this, it's started updating and got an error while updating then phone rebooted with new update,
but there's lot of errors,
Built Number displays as - NRD90M test-keys
Updater missing in settings
Camera missing
Flash Light not working
Clock missing
File Manger missing
and few more default huawei apps missing.
How do I fix it or downgrade to previous version back?

Thanks finally I was able to update my P9 to Nougat using this steps. The only difference is that there is a EVA-L09C636B190 available now so i didnt have to use the version for any other cell, I was afraid to do it. So following this steps i was able to upgrade from 168 to 190 and finally to 361 version.

My Phone is Huawei P9 EVA-L09C636
Even though my phone is L09 I've flashed L19 by following the steps on this thread -
(https://forum.xda-developers.com/mate-8/general/nxt-l09c636b521-official-firmware-guide-t3544729/)
2016.12.29 - EVA-L19C636 - EVA-L19C636B361
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1583/g104/v74666/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...ll/hw/spcseas/update_data_full_hw_spcseas.zip
it's still NRD90M test-keys. but i'm cool with it.

Works on AL00 as well?
I was wondering if I can get the most current european rom on my AL00 with that method as well?

Holy cow thank you for this tutorial.
I spent six hours following every tutorial I could find on the web and my P9 staunchly refused to install ANY update from the very next one after the one it came with all the way up to the latest!
After hours and hours of trying this method is the one that worked.
Edit: This firmware is a developer build.
There have been several updates installed since it was released.
After you this firmware it you should immediately install Huawei Firmware Finder from the Play Store and install the latest full OTA.
The developer build changes the device ID of your phone so you have to manually add the model of your phone in Firmware Finder as:
EVA-L19C636
Otherwise Firmware Finder would tell you there are no firmwares available for your model.
If you can't install the latest OTA immediately after installing this firmware, first install the next one available (38 if I recall correctly) then install the latest OTA -- 38 will say it failed to install but it actually installs just fine, then install the latest full OTA.
That will give you all the bug fixes and the security patches from Google.
Also note that this firmware works on both the dual sim and single sim models (it's built for the single sim but my device is dual sim and the sim configuration in settings works).

snjflame said:
My model is Huawei P9 EVA-L09C636
I tried to update like this, it's started updating and got an error while updating then phone rebooted with new update,
but there's lot of errors,
Built Number displays as - NRD90M test-keys
Updater missing in settings
Camera missing
Flash Light not working
Clock missing
File Manger missing
and few more default huawei apps missing.
How do I fix it or downgrade to previous version back?
Click to expand...
Click to collapse
The build number is normal.
As for the disappearing apps, it sounds like you have faulty flash storage.
That will cause files and apps to randomly disappear.

[Honor 8] update from NRD90M test-keys 5.0 to 5.1

I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico

Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
Thanks in advance,
Federico
Click to expand...
Click to collapse
This Should Help You.
https://forum.xda-developers.com/honor-8/how-to/to-emui5-custom-roms-tested-openkirin-t3638445

I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs

SharxX8 said:
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
can you tell me what rollback package to use? i tried "(FRD-L19&L09, from Android 7.0, EMUI 5.0 to Android 6.0 EMUI 4.1, C900B300, Western Europe)" and didn't work

If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs

SharxX8 said:
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?

Federico Cervelli said:
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Click to expand...
Click to collapse
If you are on a regular version of MM, as I understand it, you can update normally, yes

SharxX8 said:
If you are on a regular version of MM, as I understand it, you can update normally, yes
Click to expand...
Click to collapse
but last time i did it it brang me to test keys .-.
EDIT: i tried and it's all working, Thanks!

Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Click to expand...
Click to collapse
I am in a very similar situation and unable to solve this. Could some one help in this?
I had unlocked bootload, TWRP and Root. I decided to unroot and lock the bootloader. So, by following the steps mentioned in a different thread, I could successfully flash Marshmallow B130 through Force Update.
Steps followed:
1. Flash Rollback package
2. Flash Full OTA (Marshmallow on B130) from Huawei website which flashed
Now, the real problem started while trying to upgrade to Nougat.
I tried downloading B350 firmware from Firmware Finder. After slow download, it installs fine. But, after reboot I face below problems.
1. The OS is very sluggish and crashes so often
2. The build number says NRD***-test keys
3. No keyboard installed, so not able to login to Google as well.
4. At this point, Factory Reset, Wipe Cache Partition, rollback everything fails.
I had to unlock the bootloader and again force update Rollback Package and then to Marshmallow B130.
Now, I am stuck with B130. I tried downloading B340 and B361 thru Firmware Finder. Both of them installed but with the same result. I mean No keyboard, Test-keys build, Crashes
My Honor 8 model: FRD-L02
What should I do upgrade to Nougat? I have no confidence in Firmware Finder method. Any help appreciated

It's EMUI 5.0.1 not 5.1, I think.

Successfully rebranding Chinese COL-AL10 to European COL-L29: report

Dear community,
I recently bought a Honor 10 (AL-10 C00) with 6GB RAM and 128 GB flash memory from China. Since I did not want to use Chinese apps and some of these were really resistant to my attempts to remove them (like the voice search attached to the home button), I researched xda-developers quite extensively for ways to rebrand the phone to a European version (more precisely, L29 C432). In particular, I read the tutorials made for "related" models such as P10, P20, Mate 10, Honor 9, and HonorView 10.
In detail, my plan was to move from firmware COL-AL10 8.1.0.139 (C00GT) to firmware COL-L29 8.1.0.131 (C432), noting that the L29 firmware had a somewhat lower version number than the AL10 but was the most recent available at the time of trying the rebranding. My concern was therefore that the rebranding might brick the phone similarly to what was observed on the Mate 10 (https://forum.xda-developers.com/mate-10/how-to/discussion-hard-brick-infos-t3789044). Fortunately, the xloader-check tool from https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241 displayed "02 XLOADER" for both firmwares, so I decided to proceed.
I obtained all firmware files using HuaweiFirmwareFinder (https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder), paying attention to the fact that only full OTAs can be used for the branding. In the following description, I used 3 ZIP archives containing the L29 8.1.0.131 software, renamed to match the scheme "update.zip, update_data_public.zip and update_all_hw.zip".
My first attempt was to imitate the approach from the tutorial https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283 made for the P20. I followed the procedure with the following exceptions:
- Magisk and TWRP were already on the phone thanks to the tutorials from the Honor 10 section.
- I took the nocheck-recovery for the View 10 instead of the one for the P20, more precisely I installed "recovery_ramdisk_BKL-L04_nocheck.img" from https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085.
- In Step 17, I said ./oeminfo COL-L29 C432 hw/eu
(By the way, the oeminfo binary is a great tool that allows you to change only the relevant portions of your oeminfo partition related to model number etc. It keeps things such as IMEI intact, so that the bootloader unlock code does not change by the rebranding, contrary to FunkyHuawei's procedure, as it seems.)
After booting to nocheck-recovery, an EMUI update screen was shown and slowly counting up, but after a while an error message of the kind "Installation failed" popped up and forced me to make a factory reset. Still, the bootloader was unlocked afterwards and I could reflash TWRP. The state of the phone now was that it had rebranded oeminfo, an unlocked bootloader, a working TWRP but no real operating system.
The second and final attempt was to use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279). I rebooted to Recovery, placed the 3 ZIP files and the HuRUpdater ZIP in the top directory of the internal memory (accessed via USB), chose "Install" with respect to the HuRUpdater ZIP, waited some minutes and saw the phone rebooting to EMUI 8.1 with many preinstalled Google apps. Success.
I think it should have been possible to skip the step using nocheck-recovery that failed anyway, provided that the oeminfo binary is executed from TWRP before flashing via HuRUpdater. Any further information would be helpful.
This morning, the firmware update COL-L29 8.1.0.143 (C432) arrived. I downloaded the full OTA and installed it via HuRUpdater as described above. The phone runs very smoothly so far. A scrreenshot of the "About phone" page is attached. Note the 6GB RAM that comes from the Chinese version.
I am happy to answer questions and would like to read more about your experiences with rebranding the Honor 10.

mrspeccy said:
Dear community,
- In Step 17, I said ./oeminfo COL-29 C432 hw/eu
(By the way, the oeminfo binary is a great tool that allows you to change only the relevant portions of your oeminfo partition related to model number etc. It keeps things such as IMEI intact, so that the bootloader unlock code does not change by the rebranding, contrary to FunkyHuawei's procedure, as it seems.)
.
Click to expand...
Click to collapse
Can you share me the link to OEM info binary tool ?

It's linked from the thread I used for the first attempt. Direct access: https://mega.nz/#!X0AjASKS!KvXMfbtd8S3kPNZZO1Lm6bKHDyXGqXlBi0SDZdzJwfo

the problem its how to get the bootloader unlock code ?

sweetjuice said:
the problem its how to get the bootloader unlock code ?
Click to expand...
Click to collapse
Correct. I received the code from Huawei before they stopped handing out the unlock codes. At the moment, I do not know of any alternatives.

mrspeccy said:
Dear community,
(...)
The second and final attempt was to use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279). I rebooted to Recovery, placed the 3 ZIP files and the HuRUpdater ZIP in the top directory of the internal memory (accessed via USB), chose "Install" with respect to the HuRUpdater ZIP, waited some minutes and saw the phone rebooting to EMUI 8.1 with many preinstalled Google apps. Success.
I think it should have been possible to skip the step using nocheck-recovery that failed anyway, provided that the oeminfo binary is executed from TWRP before flashing via HuRUpdater. Any further information would be helpful.
This morning, the firmware update COL-L29 8.1.0.143 (C432) arrived. I downloaded the full OTA and installed it via HuRUpdater as described above. The phone runs very smoothly so far. A scrreenshot of the "About phone" page is attached. Note the 6GB RAM that comes from the Chinese version.
I am happy to answer questions and would like to read more about your experiences with rebranding the Honor 10.
Click to expand...
Click to collapse
Hey, thanks a lot for this thread!
Soo I am about to maybe do the same as you did – would you suggest/think that just doing the second Part will do the trick for me?
Can't really tell if the first part contained something that's relevant for the second/final part to work.
Furthermore – did you encounter any issues yet, now that you've used the eu rom for a bit?
(And does your device show up as certified within the Play Store?)
Oh and of what I understood, you'll have to do OTA Updates manually?
Thanks again for the effort!

Hi,
if I were you, I would try only the "second part" involving HuRUpdater, but would make sure that the oeminfo partition is modified before HuRUpdater is called. What about the following:
1. You copy the zip files belonging to the update along with the oeminfo binary to the top of the sdcard
2. You boot into TWRP recovery and start a terminal. There you say:
mkdir /data/local/tmp
cp /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo COL-L29 C432 hw/eu
3. You "install" the HuRUpdater zip from within TWRP.
If it fails, maybe make a factory reset and try again. Re-flashing TWRP might become necessary.
Regarding your questions: I have not experienced any issues with the EU ROM yet. The device passes Safetynet and is shown as certified in PlayStore (possibly thanks to Magisk, which I installed from TWRP, did not test it without). Magisk and TWRP are also the reason why I have to update manually. Huawei ROMs seem to deny OTA updates when a custom recovery and/or root are detected.

mrspeccy said:
Hi,
if I were you, I would try only the "second part" involving HuRUpdater, but would make sure that the oeminfo partition is modified before HuRUpdater is called. What about the following:
1. You copy the zip files belonging to the update along with the oeminfo binary to the top of the sdcard
2. You boot into TWRP recovery and start a terminal. There you say:
mkdir /data/local/tmp
cp /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo COL-L29 C432 hw/eu
3. You "install" the HuRUpdater zip from within TWRP.
If it fails, maybe make a factory reset and try again. Re-flashing TWRP might become necessary.
Regarding your questions: I have not experienced any issues with the EU ROM yet. The device passes Safetynet and is shown as certified in PlayStore (possibly thanks to Magisk, which I installed from TWRP, did not test it without). Magisk and TWRP are also the reason why I have to update manually. Huawei ROMs seem to deny OTA updates when a custom recovery and/or root are detected.
Click to expand...
Click to collapse
Great. I can assure you that without magisk but stock recovery it passes safety net as well.

mrspeccy said:
Hi,
if I were you, I would try only the "second part" involving HuRUpdater, but would make sure that the oeminfo partition is modified before HuRUpdater is called. What about the following:
1. You copy the zip files belonging to the update along with the oeminfo binary to the top of the sdcard
2. You boot into TWRP recovery and start a terminal. There you say:
mkdir /data/local/tmp
cp /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo COL-L29 C432 hw/eu
3. You "install" the HuRUpdater zip from within TWRP.
If it fails, maybe make a factory reset and try again. Re-flashing TWRP might become necessary.
Regarding your questions: I have not experienced any issues with the EU ROM yet. The device passes Safetynet and is shown as certified in PlayStore (possibly thanks to Magisk, which I installed from TWRP, did not test it without). Magisk and TWRP are also the reason why I have to update manually. Huawei ROMs seem to deny OTA updates when a custom recovery and/or root are detected.
Click to expand...
Click to collapse
I'm the same device and is annoying chinese stuff, but i have some fear to do that. I already have the unlock code, but did not unlocked yet.

Same procedure for AL 10 c675?

Hi mine has this L29 Sp6c200 any chance changing roms?

Boorifee said:
Hi mine has this L29 Sp6c200 any chance changing roms?
Click to expand...
Click to collapse
Yes follow same procedure
.
First of all have a root access to your L29

Great find sir!!
mrspeccy said:
Dear community,
I recently bought a Honor 10 (AL-10 C00) with 6GB RAM and 128 GB flash memory from China. Since I did not want to use Chinese apps and some of these were really resistant to my attempts to remove them (like the voice search attached to the home button), I researched xda-developers quite extensively for ways to rebrand the phone to a European version (more precisely, L29 C432). In particular, I read the tutorials made for "related" models such as P10, P20, Mate 10, Honor 9, and HonorView 10.
In detail, my plan was to move from firmware COL-AL10 8.1.0.139 (C00GT) to firmware COL-L29 8.1.0.131 (C432), noting that the L29 firmware had a somewhat lower version number than the AL10 but was the most recent available at the time of trying the rebranding. My concern was therefore that the rebranding might brick the phone similarly to what was observed on the Mate 10 (https://forum.xda-developers.com/mate-10/how-to/discussion-hard-brick-infos-t3789044). Fortunately, the xloader-check tool from https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241 displayed "02 XLOADER" for both firmwares, so I decided to proceed.
I obtained all firmware files using HuaweiFirmwareFinder (https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder), paying attention to the fact that only full OTAs can be used for the branding. In the following description, I used 3 ZIP archives containing the L29 8.1.0.131 software, renamed to match the scheme "update.zip, update_data_public.zip and update_all_hw.zip".
My first attempt was to imitate the approach from the tutorial https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283 made for the P20. I followed the procedure with the following exceptions:
- Magisk and TWRP were already on the phone thanks to the tutorials from the Honor 10 section.
- I took the nocheck-recovery for the View 10 instead of the one for the P20, more precisely I installed "recovery_ramdisk_BKL-L04_nocheck.img" from https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085.
- In Step 17, I said ./oeminfo COL-L29 C432 hw/eu
(By the way, the oeminfo binary is a great tool that allows you to change only the relevant portions of your oeminfo partition related to model number etc. It keeps things such as IMEI intact, so that the bootloader unlock code does not change by the rebranding, contrary to FunkyHuawei's procedure, as it seems.)
After booting to nocheck-recovery, an EMUI update screen was shown and slowly counting up, but after a while an error message of the kind "Installation failed" popped up and forced me to make a factory reset. Still, the bootloader was unlocked afterwards and I could reflash TWRP. The state of the phone now was that it had rebranded oeminfo, an unlocked bootloader, a working TWRP but no real operating system.
The second and final attempt was to use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279). I rebooted to Recovery, placed the 3 ZIP files and the HuRUpdater ZIP in the top directory of the internal memory (accessed via USB), chose "Install" with respect to the HuRUpdater ZIP, waited some minutes and saw the phone rebooting to EMUI 8.1 with many preinstalled Google apps. Success.
I think it should have been possible to skip the step using nocheck-recovery that failed anyway, provided that the oeminfo binary is executed from TWRP before flashing via HuRUpdater. Any further information would be helpful.
This morning, the firmware update COL-L29 8.1.0.143 (C432) arrived. I downloaded the full OTA and installed it via HuRUpdater as described above. The phone runs very smoothly so far. A scrreenshot of the "About phone" page is attached. Note the 6GB RAM that comes from the Chinese version.
I am happy to answer questions and would like to read more about your experiences with rebranding the Honor 10.
Click to expand...
Click to collapse
Hi OP,
Is it possible if you could post a step to step procedure how you rebranded your phone. I have tried what you said but it turned my phone into a "beta" firmware with model number of "FTY-L29". Very weird. I have have missed something along the way now that I can't undo. If you could please help me out. Thank you very much.

tinguyen said:
Hi OP,
Is it possible if you could post a step to step procedure how you rebranded your phone. I have tried what you said but it turned my phone into a "beta" firmware with model number of "FTY-L29". Very weird. I have have missed something along the way now that I can't undo. If you could please help me out. Thank you very much.
Click to expand...
Click to collapse
Becareful , what was your previous build number and the firmware build number you tried to flash.
Can you also share more details asked in this thread .
https://forum.xda-developers.com/honor-10/how-to/discussion-hard-brick-infos-t3824022
I hard bricked a device after flashing another firmware over this same build fty l09 after flashing one firmware.

miststudent2011 said:
Becareful , what was your previous build number and the firmware build number you tried to flash.
Can you also share more details asked in this thread .
https://forum.xda-developers.com/honor-10/how-to/discussion-hard-brick-infos-t3824022
I hard bricked a device after flashing another firmware over this same build fty l09 after flashing one firmware.
Click to expand...
Click to collapse
I was in COL-AL10 like yours as well because I bought it from 3rd party site. Now I'm just waiting for someone to post a proper procedure of how to undo or install new firmware over the existing one. My phone is still usable but it's just not the right firmware that I wanted and its back to EMUI 5.1 too. zzzzzzz

tinguyen said:
I was in COL-AL10 like yours as well because I bought it from 3rd party site. Now I'm just waiting for someone to post a proper procedure of how to undo or install new firmware over the existing one. My phone is still usable but it's just not the right firmware that I wanted and its back to EMUI 5.1 too. zzzzzzz
Click to expand...
Click to collapse
5.1??

tinguyen said:
I was in COL-AL10 like yours as well because I bought it from 3rd party site. Now I'm just waiting for someone to post a proper procedure of how to undo or install new firmware over the existing one. My phone is still usable but it's just not the right firmware that I wanted and its back to EMUI 5.1 too. zzzzzzz
Click to expand...
Click to collapse
Can you provide me build number before flash and build number you flashed they are important here to solve the case.

vampirian said:
Great. I can assure you that without magisk but stock recovery it passes safety net as well.
Click to expand...
Click to collapse
Soo I just managed to rebrand my col-al10 to col-l29 (will share my whole experience soon).
But now it says my device is uncertified in the Play store (said so before Magisk & TWRP were installed and still says so, now that I've installed both and Magisk says SafetyNet is passed).
Any suggestions?

vollkornbaguette said:
Soo I just managed to rebrand my col-al10 to col-l29 (will share my whole experience soon).
But now it says my device is uncertified in the Play store (said so before Magisk & TWRP were installed and still says so, now that I've installed both and Magisk says SafetyNet is passed).
Any suggestions?
Click to expand...
Click to collapse
Can you use Google Pay after rebanding to EU version?

Johnson Chen said:
Can you use Google Pay after rebanding to EU version?
Click to expand...
Click to collapse
Hey, no I can't - and I am pretty sure it's because of the uncertified status in Google Play.
I think so because when trying to add my mastercard for contactless payment as described in my Google Pay thread, it doesn't work either but this time it's a different error message.

I need to rollback (Honor 8), HELP!

I have a seemingly stupid but still annoying problem. As many of you know Android 8 + EMUI 8 came out this summer and I have updated my Honor8. Everything works well, even better (especially with regard to the battery) apart from a problem, quite annoying. I have seen that everyone around complains about the same problem, so it is clear that both a build bug and not a local problem.
Basically ... the bluetooth link with the multimedia system of my car doesn't work as it should, while it worked well with the 7.0.
Tracknames, music infos disappears, sometimes it connects regularly, starting the music, sometimes nothing happens, sometimes the music passes from the car speakers to smartphone (!!)... in short, manage the music in the car It has become a big problem!
I tried all possible options; reset pairing, reset bluetooth, clear cache, activate the developer options to control some low-level aspects of bluetooth, and finally installed Bluetooth Auto Connect which also has several advanced options. Nothing works. In the meantime an update of 8.0 has been released (mine is the buiold 521). The update came out in September ... maybe (MAYBE) this update fixes all bluetooth issues (but i don't have any detailed info about). Until today I have not received any updates and normally I check new version regularly every day. At this point I decided to return to Nougat!
And here the adventure begins!
I CANNOT IN ANY WAY do the downgrade.
What I tried:
- through HiSuite. The "back to previous version" option appears random (rarely); normally the program tells me "the system is up to date". Once appeared I tried to run the procedure, but after the decompression it gives me an error "error updating".
- by standard Rollback procedure. Using a microSD and putting the full version of Nougate in the dload folder. The installation starts but stops almost immediately with the same "update cannot be applied" error.
At this point I am desperate. I cannot update Oreo, I can't go back to Nougat and meanwhile the bluetooth still doesn't work with my car. Remember that before Oreo, everything worked very well!
What can I do? Can you help me?
Thank you

hi / i can help u / pls say me this:
your region(Ru/Eu/Cn.......)
your model( FRD-L09/L19/L04........)
Your Build number
and which build you upgrade to emui 8

m2relax said:
hi / i can help u / pls say me this:
your region(Ru/Eu/Cn.......)
your model( FRD-L09/L19/L04........)
Your Build number
and which build you upgrade to emui 8
Click to expand...
Click to collapse
Region: EU
Model: FRD-L09
Build: 8.0.0.521 (C432)
Previous Build: don't remember. It was Nougat, and I've upgraded around the first week of September. From that day I haven't received/applied any patch, because nothing appears until now.
This morning I've tried again with HiSuite. As usual it says I'm running the latest version and it doesn't offer any downgrade option .

Thelothian said:
Region: EU
Model: FRD-L09
Build: 8.0.0.521 (C432)
Previous Build: don't remember. It was Nougat, and I've upgraded around the first week of September. From that day I haven't received/applied any patch, because nothing appears until now.
This morning I've tried again with HiSuite. As usual it says I'm running the latest version and it doesn't offer any downgrade option .
Click to expand...
Click to collapse
dont worry/ do u change region of your phone past?

m2relax said:
dont worry/ do u change region of your phone past?
Click to expand...
Click to collapse
Never. And never jailbroken or rooted...

Thelothian said:
Never. And never jailbroken or rooted...
Click to expand...
Click to collapse
ok / pls do this work step by step :
1-Get Unlock Code for your Phone
2-Unlock your phone with Unlock Code
3-install TWRP recovery
4-after install TWRP notice me to send a file for u ( u must flash it from recovery TWRP )
5-after flashing u most install recovery stock
6-End and your problem is done! :fingers-crossed:

m2relax said:
ok / pls do this work step by step :
1-Get Unlock Code for your Phone
2-Unlock your phone with Unlock Code
3-install TWRP recovery
4-after install TWRP notice me to send a file for u ( u must flash it from recovery TWRP )
5-after flashing u most install recovery stock
6-End and your problem is done! :fingers-crossed:
Click to expand...
Click to collapse
I Heard TWRP doesn't work well on Oreo...

CurlyApple said:
I Heard TWRP doesn't work well on Oreo...
Click to expand...
Click to collapse
no if you use multi tools 8 for install twrp its work perfectly on oero

m2relax said:
no if you use multi tools 8 for install twrp its work perfectly on oero
Click to expand...
Click to collapse
The more you know...

Finally I've decide to try updating to 8.0.0.562. After a month of tries, fails (damn Huawei and his stupid update system), errors and a lot of other stupid things, I was finally able to update my Honor hoping the latest version will fix all the problems. It was a enormous waste of time (searching around internet)... but in the end I found a method described here: https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085#4And if you go ahead you should find the correct firmware link (on a Russian site). Although, IMHO, failing with the classic method was due to the impossibility or some bugs in the update system, to unpack the update files on sdcard. So the solution seems to be to leave both the zip and the unpacked folder.The problems with bluetooth remain, but I hope that now there is not to be crazy applying next updates. ATTENTION: the method above is NOT valid for rollback! If you try, you'll brick your Honor.
And finally I've taken an important decision... for me this is the last Huawei/honor device. Next time I'll go to another brand, with a serious update system.

Hello,
I have the same problem whit my honor, bluetooth lost signal random times, and my battery is faster get low, on android 7 i dont feel thees problems. Anyone have an idea how can i downgrade to nougat or marshmallow? My phone infos:
-FRD-L09 8.0.0.521(C432), I bought it in Hungary (i think its an EU modell), the phone have an unlocked bootloader, and flashed whit TWRP recovery
Who know the solution, pls reply here or, write me an email. Big thanks

scseke said:
Hello,
I have the same problem whit my honor, bluetooth lost signal random times, and my battery is faster get low, on android 7 i dont feel thees problems. Anyone have an idea how can i downgrade to nougat or marshmallow? My phone infos:
-FRD-L09 8.0.0.521(C432), I bought it in Hungary (i think its an EU modell), the phone have an unlocked bootloader, and flashed whit TWRP recovery
Who know the solution, pls reply here or, write me an email. Big thanks
Click to expand...
Click to collapse
flash this file with twrp and install stock recovery and do reset factor / finally use hisuite to rollback

Question xiaoxin pad 11 pro

Good morning
So I've a xiaoxin pad 11 pro:
Model: tb-j706f
android version: 10
software version: tb-_706f_rf01_201229
ROM: TB-J706F_S240073_201229_ROW
kernel: 4.14.117 from 2020
Widevine: L1
And I whant to update to TB-J706F_S620150_211226_ROW. So my questions are many
-Can i use lenovo sofware to update?
-Do i need to lock or unlock oem bootloader from settings?
-Can only be done using QFIL or other softwares?
-Do i need to find out if it's region lock?
-How to backup this img, if everything goes wrong?
-Do i have to install the original chinese version, or can i just update the international one?
I see alot of threats talking about going from international to chinese, but I like to have play store and keepping widevine lv.1. Without having to do a lot of "work".
I've tried to use the OTA function, but downloads the update (just after my current version) it restart's and gets to the lenovo logo on the screen and reboots. Like a boot loop. I've to manually shutdown the tablet and it's back to normal.
After readding this forum, i still dont see a uniform way to update this device, and more importantly a easy way to do it. Can all of you help me?

- yes
- no
- yes
- even CN versions can be flashed with global rom
- you could still flash an img you download online if something wrongs happen
- it's on your own, if you have L1 with global unless you want latest updates no need to go CN, stay global.
if OTA update doesn't work maybe reset the device or even flash the newest rom available from lolinet then update with OTA.

@melones22 Thanks for the aswers.
Do you know if i download the newest global rom from lolinet, and force install, if i keep my lv1?

if you relock bootloader, likely. personally with natsafety patch + hde etc still l3
be absolute sure that you didn’t modified anything else than flashing before relocking

front3 said:
Good morning
So I've a xiaoxin pad 11 pro:
Model: tb-j706f
android version: 10
software version: tb-_706f_rf01_201229
ROM: TB-J706F_S240073_201229_ROW
kernel: 4.14.117 from 2020
Widevine: L1
And I whant to update to TB-J706F_S620150_211226_ROW. So my questions are many
-Can i use lenovo sofware to update?
Click to expand...
Click to collapse
Yes, but I nver used it
front3 said:
-Do i need to lock or unlock oem bootloader from settings?
Click to expand...
Click to collapse
If you flash stock ROMs CN or Global you do NOT need to unlock bootloader
front3 said:
-Can only be done using QFIL or other softwares?
Click to expand...
Click to collapse
To flash a ROM you can use QFIL, I never used Lenovo softwaare so I am not sure if you can flash form there only last version or if you have a choice.
Normally you should not be required to use QFIL and you should be able to update with OTA updates.
front3 said:
-Do i need to find out if it's region lock?
Click to expand...
Click to collapse
If you are having problems updating I guess it doesn't hurt finding that out.
front3 said:
-How to backup this img, if everything goes wrong?
Click to expand...
Click to collapse
You should backup QCN with QFIL and all partitions (you can probably exclude vendor and userdata) with QFIL or edl, there is a guide for both methods (I use edl) https://forum.xda-developers.com/t/two-ways-to-backup-tb-j706f-without-unlocking-bootloader.4402799/
front3 said:
-Do i have to install the original chinese version, or can i just update the international one?
Click to expand...
Click to collapse
You should be able to update your global ROM but since you are having problems I don't exclude you might need to go back to CN ROM before flashing again the Global ROM.
front3 said:
I see alot of threats talking about going from international to chinese, but I like to have play store and keepping widevine lv.1. Without having to do a lot of "work".
I've tried to use the OTA function, but downloads the update (just after my current version) it restart's and gets to the lenovo logo on the screen and reboots. Like a boot loop. I've to manually shutdown the tablet and it's back to normal.
After readding this forum, i still dont see a uniform way to update this device, and more importantly a easy way to do it. Can all of you help me?
Click to expand...
Click to collapse
I am not sure what's the problem with your OTA update.
I would suggest to:
Backup your QCN and all partitions first
Open your QCN with QCNView and check the region in NV Item 6858
If your region is 02 is Global and OTA update should work, so maybe try a factory reset and see if after OTA update works.
If it's 00 (region unlocked) or 01 (China) that might be the reason OTA updates are not working.
Edit
I read again the version you have now and it's quite old, that probably does not have any region lock.
In the one tablet I had from the shop with Chinese ROM I flashed TB-J706F_S250260_210804_ROW, that set it as global region and then from that I run OTA updates.
So I think you should backup as I said before and then flash TB-J706F_S250260_210804_ROW, make sure to select the right settings in QFIL and NEVER check "Reset state machine".

MrCrayon said:
Yes, but I nver used it
If you flash stock ROMs CN or Global you do NOT need to unlock bootloader
To flash a ROM you can use QFIL, I never used Lenovo softwaare so I am not sure if you can flash form there only last version or if you have a choice.
Normally you should not be required to use QFIL and you should be able to update with OTA updates.
If you are having problems updating I guess it doesn't hurt finding that out.
You should backup QCN with QFIL and all partitions (you can probably exclude vendor and userdata) with QFIL or edl, there is a guide for both methods (I use edl) https://forum.xda-developers.com/t/two-ways-to-backup-tb-j706f-without-unlocking-bootloader.4402799/
You should be able to update your global ROM but since you are having problems I don't exclude you might need to go back to CN ROM before flashing again the Global ROM.
I am not sure what's the problem with your OTA update.
I would suggest to:
Backup your QCN and all partitions first
Open your QCN with QCNView and check the region in NV Item 6858
If your region is 02 is Global and OTA update should work, so maybe try a factory reset and see if after OTA update works.
If it's 00 (region unlocked) or 01 (China) that might be the reason OTA updates are not working.
Edit
I read again the version you have now and it's quite old, that probably does not have any region lock.
In the one tablet I had from the shop with Chinese ROM I flashed TB-J706F_S250260_210804_ROW, that set it as global region and then from that I run OTA updates.
So I think you should backup as I said before and then flash TB-J706F_S250260_210804_ROW, make sure to select the right settings in QFIL and NEVER check "Reset state machine".
Click to expand...
Click to collapse
Hi Mr. Crayon,
Is there any guide in how to do as what you mentioned above ? I'm quite new to this 'manual update' and still learning. Would really appreciate your help on this. My Xiaoxin Pad Pro 2020 (TB-J706F_S268018_210731_ROW) is still running on android 10 and my device is not certified by play protect. T.T

Hello.
Thanks @MrCrayon, but i never has able to use qfil to backup my device. To complicated for me. But thanks for the help.
So what i did to update my tablet. After feeling the same way @shaoki92 , i just tried to use lenovo tools. And... puff... update done.
No problems what so ever,
Did not lose L1
And did not have to mess with bootloader or region lock.
But i understand that i took a big risk. The tablet could've become just a paper weight. But until now working fine. With new android and everything.

front3 said:
Hello.
Thanks @MrCrayon, but i never has able to use qfil to backup my device. To complicated for me. But thanks for the help.
So what i did to update my tablet. After feeling the same way @shaoki92 , i just tried to use lenovo tools. And... puff... update done.
No problems what so ever,
Did not lose L1
And did not have to mess with bootloader or region lock.
But i understand that i took a big risk. The tablet could've become just a paper weight. But until now working fine. With new android and everything.
Click to expand...
Click to collapse
Hi front3,
May i ask how do you update using lenovo tools ? Thanks

Im no expert that so ever. But i can tell you that i did.
Install lenovo assistance, on windows.
Used the charging cable of the tablet to connect to pc.
Launch the app
Connect to the device via app
(And i dont remember now, but i think its recue my device, and update, inside the app)
The app gives you a warning about using the tool on CH devices, and i took the risk.
Check the firmware version that the app gives you, and what it the lastest that has been deploid. Just to be sure. And do it if you dont mind taking the risk, do it.
In my case, the version that the app recomended has not on lolinet at that time. It only show up there, weeks later. But because the app connects to lenovo servers directly, i think it was safe.
Be careful because you can brick the device. And like @MrCrayon explained, i had one very old firmware, so xiaoxin didnt have the same "security" feactures has the newer devices. So maybe that is why it worked.