Related
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.
So like a dummy I flashed the wrong firmware on my P40 Pro. LGRP6 instead of LGRP4. Now when booting it says "Your device has loaded a different operating system" and then goes straight to erecovery. In eRecovery, downloading and restoring the system doesn't work because it fails to retrieve package info.
I already tried everything possible with HiSuite Proxy, too. I read bricking a P40 Pro this way requires to replace the motherboard, but not sure how true that is. My phone is still under warranty, but I'd prefer to fix it myself, if possible.
Any ideas? Thanks.
Tried eRecovery without any sim card in it?
Superbia said:
Tried eRecovery without any sim card in it?
Click to expand...
Click to collapse
Yes, I just get retrieving package info failed. Every time
Then it seems motherboard replacement is the only known option left.
Same issue with me
I spent a month to fix it and didn't find a way.
I tried Chimera Mobile and it didn't helped.
The only thing that probably can help is SigmaKey software. If anybody has it please check and say did it helped or not.
Huawei don't want to replace it by warranty for me, that is why I try everything.
Alex.Novikov said:
I spent a month to fix it and didn't find a way.
I tried Chimera Mobile and it didn't helped.
The only thing that probably can help is SigmaKey software. If anybody has it please check and say did it helped or not.
Huawei don't want to replace it by warranty for me, that is why I try everything.
Click to expand...
Click to collapse
Any update? I'm in the same situation :/
sonybes said:
Any update? I'm in the same situation :/
Click to expand...
Click to collapse
I can't find anybody with SigmaKey. Probably I'll go to replace the motherboard in the nearest future.
Other methods definetely don't help.
Do you have any update? Please share if yes.
Hi all! My device is finally fixed! It was fixed by disassembly, hardware testpoint and flashing of Android 11 via SigmaKey!
You have to find a very expirienced person to do this work. I can recommend one person in Moscow, Russia in private messages.
Disassembly is probably necessary
Alex.Novikov said:
Hi all! My device is finally fixed! It was fixed by disassembly, hardware testpoint and flashing of Android 11 via SigmaKey!
You have to find a very expirienced person to do this work. I can recommend one person in Moscow, Russia in private messages.
Disassembly is probably necessary
Click to expand...
Click to collapse
Thanks for the update!
After 4 days trying everythingI found also a guy who told me exactly what you are saying. disassembly is required because of the test point. No other way currently.
SoI will go to a phone shop tomorrow to disassemble the back cover of my P40Pro+. Then the guy will do the whole flashing process via remote. But it's paid service for 30$. I decided to do or because I wanna use this phone.
sony_bes said:
Thanks for the update!
After 4 days trying everythingI found also a guy who told me exactly what you are saying. disassembly is required because of the test point. No other way currently.
SoI will go to a phone shop tomorrow to disassemble the back cover of my P40Pro+. Then the guy will do the whole flashing process via remote. But it's paid service for 30$. I decided to do or because I wanna use this phone.
Click to expand...
Click to collapse
The only other way is to try to replace the motherboard by warranty.
However, in my case Huawei refused me this.
I think 30$ is a good price because it was very difficult for me to find a person good enough to do it.
Hi guys. Just posting a small update here. I found a xda user who accepted to help me unbrick my P40 Pro for a donation via remote desktop. He will be using paid tools and hopefully it will unbrick the device. I'll post another update soon, to let you guys know the outcome. Fingers crossed!
jericho246 said:
Hi guys. Just posting a small update here. I found a xda user who accepted to help me unbrick my P40 Pro for a donation via remote desktop. He will be using paid tools and hopefully it will unbrick the device. I'll post another update soon, to let you guys know the outcome. Fingers crossed!
Click to expand...
Click to collapse
It is not always possible without disassembly. (Like was in my case)
I wish you good luck but be ready for disassembly.
Another update. First of all big thanks to @oslo83 for accepting to help me with my bricked P40 Pro. Unfortunately things didn't go our way and the device is still bricked. The problem is that I flashed LGRP6 EMUI 11, with EMUI 10.1 preload & cust. A ****ty situation but it is what it is. @oslo83 advised me to take the device to Huawei repair center (it's still under warranty) and that's what I'm going to do.
However if anyone has a bricked P40 Pro, I still recommend oslo83 services, there's a chance your brick is different from mine and that he will be able to unbrick it. If not, he will issue a refund like he did for me.
Hi guys, I have a brilliant update for you guys:
The guy I was working on this issue was able to fix my phone remotely with SigmaKey. After hours of tries he made it!
There is no software solution yet - so the back cover has to be dissembled. I went to a phone shop at the corner and let them open it. After removing ca. 10 screws you can reach the "Test Point". There are some videos on YouTube which can support you. Its not easy but its makable.
The genius guy gives a step by step instruction what to do via WhatsApp.
So at the end my P40Pro+ works again and I am so happy! I will start the downgrade now (to install gms)and I will DEFINITELY use the correct FW this time
I can share the contact - send me a private message.
Another update hopefully the next one will be the FINAL one.
So like @oslo83 suggested, I contacted Huawei via chat on their official site. They accepted to repair my device for free with no problem. I sent my phone to the repair center and now I simply have to wait. The person in the Huawei chat told me it could take up to two weeks. And another thing, they let me know the phone will be updated to the latest firmware, so I probably won't be able to downgrade and install GMS, unless there is a way to install it on EMUI 11 (not sure). But at least I'll have a working P40 Pro again
I have the same problem. I'm tryingto fix it with hsuite proxy and the phone in fastboot&rescue mod
In HiSuiteConfig.xml I added to be able to enter the recovery mode
<rule type="ELS-N29" cnName="HUAWEI P40 Pro" enName="HUAWEI P40 Pro" option="" ></rule>
I'm testing to flash this:
Base version: ELS-LGRP4-OVS 10.1.0.176
Custom version: ELS-N29-CUST 10.1.0.8(C432)
Preload version: ELS-N29-PRELOAD 10.1.0.2(C432R5)
Checked "Recovery OS", CUST PKG and Preloaded PKG
So far it connects
I can download and unpack the firmware on the phone
but then I have an error-message on (Installing 0%) telling me, that on this phone the recovery mode is not available. I'm trying with different base firmware - but every attempt takes a lot of time.
muetter said:
I have the same problem. I'm tryingto fix it with hsuite proxy and the phone in fastboot&rescue mod
In HiSuiteConfig.xml I added to be able to enter the recovery mode
<rule type="ELS-N29" cnName="HUAWEI P40 Pro" enName="HUAWEI P40 Pro" option="" ></rule>
I'm testing to flash this:
Base version: ELS-LGRP4-OVS 10.1.0.176
Custom version: ELS-N29-CUST 10.1.0.8(C432)
Preload version: ELS-N29-PRELOAD 10.1.0.2(C432R5)
Checked "Recovery OS", CUST PKG and Preloaded PKG
So far it connects
I can download and unpack the firmware on the phone
but then I have an error-message on (Installing 0%) telling me, that on this phone the recovery mode is not available. I'm trying with different base firmware - but every attempt takes a lot of time.
Click to expand...
Click to collapse
Update: It's always the same error message after unpacking the files. So now I'm trying to install an EMUI11 rom.
Now testing with:
ELS-LGRP4-OVS 11.0.0.175
ELS-N29-CUST 11.0.0.3(C432)
ELS-N29-PRELOAD 11.0.0.3(C432R5)
Update: Failed to at 0% :-(
muetter said:
Update: It's always the same error message after unpacking the files. So now I'm trying to install an EMUI11 rom.
Now testing with:
ELS-LGRP4-OVS 11.0.0.175
ELS-N29-CUST 11.0.0.3(C432)
ELS-N29-PRELOAD 11.0.0.3(C432R5)
Update: Failed to at 0% :-(
Click to expand...
Click to collapse
It looks like I have flashed the following:
"FirmWare" : "ELS-LGRP4-OVS 11.0.0.170"
"FirmWare" : "ELS-N29-CUST 11.0.0.3(C301)"
"FirmWare" : "ELS-N29-PRELOAD 11.0.0.3(C635R2)"
Still trying to reflash ... any ideas?
I've built now my own dload
using the files downloaded by hsuite over hisuite proxy inside Hisuite\ROM/
and copy them on a USB-C-drive /dload
trying the usb-flashing method. So far it went only to 37%
The reason is to unlock the bootloader. I understand perfectly well that you just need to block the loader, but I don't need it. How do I find a fully unpacked firmware 9.0, to search for this inscription in the firmware files. I think it should be possible to change this inscription or remove it altogether. Or does someone know how to remove it?. No need to say that the inscription should be so, I just don't like it, so I decided that I need to change at least this text to my own, all this is definitely in the firmware files, but I can't unpack the firmware 9.0.
Device G8142
Firmware 47.2.A.10.107_R10C
Magisk and TWRP
Translated via Yandex translator
I was wanting to downgrade my P40 pro using method 2. But when I was using firmare finder to get the url it always shows an error message as in attached photo.
Is it still working? Any update for downgrade method 2?
Thanks a lot
Same error for me, please send help, heheh cant downgrade my huawei matepad t8
Same issue here...
was looking on other threads and found everyone posting URLs like http://update.dbankcdn.com/TDS/data/files/p3/s15/G5633/g1604/v409481/f1/ ... but all links to http://update.dbankcdn.com returning "An error occurred. " message. This is general nginx error, actual error is 404.
Does anyone know where can i get the ELS-LGRP4-OVS 10.1.0.131 firmware ? The lowest i can go in Hisuit is 10.1.0.176 and lzplay does not work on anything above 10.1.0.15x .
Please help guys... It's really frustrating to have such a beast of the device like P40 pro but not able to use it due to absence of a basic google services.
Thank you in advance.
Does this help: https://pro-teammt.ru/en/online-firmware-database/
gundammk2 said:
I was wanting to downgrade my P40 pro using method 2. But when I was using firmare finder to get the url it always shows an error message as in attached photo.
Is it still working? Any update for downgrade method 2?
Thanks a lot
Click to expand...
Click to collapse
Well it's official... I contacted the Team MT (firmware finder developers) and they acknowledged - Huawei moved all their firmware from http://update.dbankcdn.com to unknown location. Therefore there is no way to downgrade via Hisute proxy. I've tried to downgrade to 10.1.0.114 via OTG, but to no avail... I get error "incompatibility with current version" and update stops...
Did you have any success with downgrading ?
Same thing happens here too, "incompatibility with current version" sounds like wrong region or diff. hardware though. I could downgrade to 10.1.0.182 via HiSuite but nothing further down. There are some rebranding services or repairers they may have these resources but costs $$
Mifodiy said:
Well it's official... I contacted the Team MT (firmware finder developers) and they acknowledged - Huawei moved all their firmware from http://update.dbankcdn.com to unknown location. Therefore there is no way to downgrade via Hisute proxy. I've tried to downgrade to 10.1.0.114 via OTG, but to no avail... I get error "incompatibility with current version" and update stops...
Did you have any success with downgrading ?
Click to expand...
Click to collapse
Yes, I have dowgraded from 10.1.0.176(C432E8R6P1) to 10.1.0.131(C432E8R6P1) via OTG. I paid $17 to get the firmware though. But no notification for gmail and youtube. Can't sort it out so far
Mifodiy said:
Same issue here...
was looking on other threads and found everyone posting URLs like http://update.dbankcdn.com/TDS/data/files/p3/s15/G5633/g1604/v409481/f1/ ... but all links to http://update.dbankcdn.com returning "An error occurred. " message. This is general nginx error, actual error is 404.
Does anyone know where can i get the ELS-LGRP4-OVS 10.1.0.131 firmware ? The lowest i can go in Hisuit is 10.1.0.176 and lzplay does not work on anything above 10.1.0.15x .
Please help guys... It's really frustrating to have such a beast of the device like P40 pro but not able to use it due to absence of a basic google services.
Thank you in advance.
Click to expand...
Click to collapse
From easy-firmware, I paid $17 to download.....
Lyle-Wang said:
Same thing happens here too, "incompatibility with current version" sounds like wrong region or diff. hardware though. I could downgrade to 10.1.0.182 via HiSuite but nothing further down. There are some rebranding services or repairers they may have these resources but costs $$
Click to expand...
Click to collapse
"incompatibility with current version" in my case was due to insufficient disk space on my OTG USB dongle...
8Gb is not enough as it's unpacking entire dload contents to disk. 4.7 GB update package needs another 5.5 GB of space to unzip.
Another issue that can cause it is incorrect device/firmware... Check your build number but not the 10.1.0.xxx - check what is in brackets. For example (C432E8R5P2) and see first 4 characters. In my case it is C432, which means that i have global version of P40 pro. Then go to this thread https://forum.xda-developers.com/t/googlefier-install-gms-on-huawei-honor.4180485/#post-83769465 and find firmware with same 4 characters. In my case i downloaded 10.1.0.121(C432E8R5P2) and it worked flawlessly.
After you've downgraded, use googlifier method as described in aforementioned thread to set up google services.
I've been looking for a way to "fix" this phone for almost 1 week now. I've disassembled it and managed to note an alphanumeric sequence on its motherboard which I believe is its model.
First things first: this phone's touch screen is not working, but I've checked the motherboard and it seems just fine, which led me to believe there's a problem with the firmware, then I've checked the firmware using recovery mode and it seemed odd, it seemed like the phone isn't using its original firmware.
Here's the info that I found using recovery mode:
SW Ver.
alps-mp-m0.mp1-V2.39 _magc6580.we.c.m_P32
Custom Build Veno. :
V207IF3_QHD1200_M_V1.0_2_16_20200808_1758_V1.0.5_B125_HUAX_V50C3_WELCOME_S20_PLUS_PRO_DS
I'm attaching pictures too.
This phone was handed to me, so I have no reference at all. I've searched everywhere I could online and I couldn't find this model for sale, I couldn't even find a phone that looks exactly like this, but some were pretty close, like the Huawei P40 and the S20+ Pro clone, but after searching for that alphanumeric sequence, which I believe it's the actual model number, I've come across the WOLKI WS680, but I couldn't find its firmware for downloading.
FLASHING A FLASHY PHONE
I've downloaded and tried to flash the ROM MT6580__MFT__I7__I7__6.0__alps-mp-m0.mp1-V2.39_magc6580.we.c.m_P21, which seems to be the same that was in the phone, but the phone didn't turn on anymore after this (I believe it bricked). I didn't take backup before doing this, please don't blame me, It's been many years since I've done this kind of thing on a Chinese phone.
Any other rom that I tried just throws a DRAM error in SP Flash Tools, I'm also not able to format the phone (it also throws an error).
The error:
ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
WHAT I AM LOOKING FOR:1 - I need to find the right ROM firmware for this phone, please somebody give me a download link. A custom rom would be good too.
2 - I need to know which exactly is this phone's brand and model (because I need to know its hardware specs).
Please help me find at least the firmware.
Anyone?
Maybe it's the
Leioa Vapio Summilux (Mate 33 Pro) - Black Smart Phone 2021
but I don't know
xXx yYy said:
Maybe it's the
Leioa Vapio Summilux (Mate 33 Pro) - Black Smart Phone 2021
but I don't know
Click to expand...
Click to collapse
got the firmware with scatter file?
Just as it says on the sticker, this phone is a Leioa Vapio summlux h1. It looks like some kind of Chinese clone or something.
Cool, but how can I find its firmware? The phone here is bricked.
jackbauer said:
Cool, but how can I find its firmware? The phone here is bricked.
Click to expand...
Click to collapse
I don't know and that's the problem with exotic phones. Good luck with that.
This kind of copied / rebranded phones can also be found outside of China. So, whenever you buy a smartphone be sure to reach an authorized seller or take a closer look at the phone’s aspects.
My recommendation: Ask phone's seller for help.
"This phone was handed to me, so I have no reference at all."
There's nothing I can do about talking to a seller. I'm here just asking for a rom that might work with this mediatek, it doesn't mean that it needs to be the Stock ROM.
Can anyone tell me a workaround for this? it doesn't need to be the stock rom.
these fake phones are low end trash devices running android 6 no LTE. you bricked working ROM for no reason so what?
https://www.gem-flash.com/vb/threads/837178
https://androidfilehost.com/?fid=673791459329059944
https://androidhost.ru/Xe8
aIecxs said:
these fake phones are low end trash devices running android 6 no LTE. you bricked working ROM for no reason so what?
https://www.gem-flash.com/vb/threads/837178
https://androidfilehost.com/?fid=673791459329059944
https://androidhost.ru/Xe8
Click to expand...
Click to collapse
You really want to know why I'm still insisting in this phone? It's a pride thing. Some douche needs to see this working. That's why. After I "fix" this, I'll take some photos of it, send them to the person and then I'll just get rid of it.
What's the password for MT6580__Q_MOBILE__V15_PRO__V15_PRO__6.0__ALPS-MP-M0.MP1-V2.39_MAGC6580.WE.C.M_P30.RAR? I'm not finding it in the list.
https://drive.google.com/uc?id=1kjQZT6d8Yz2UBEERQnE68ZEm5h7uSLg7&export=download
You should try downloading this.
jackbauer said:
SW Ver.
alps-mp-m0.mp1-V2.39 _magc6580.we.c.m_P32
Click to expand...
Click to collapse
This is what I found from the sw ver.
notnoelchannel said:
https://drive.google.com/uc?id=1kjQZT6d8Yz2UBEERQnE68ZEm5h7uSLg7&export=download
You should try downloading this.
This is what I found from the sw ver.
Click to expand...
Click to collapse
This one is password protected.
sorry, seems one must pay $2 for password. however, I doubt any of this ROMs will work...
https://mafirmware.blogspot.com/2019/12/mt6580qmobilev15prov15pro60alps-mp.html
maybe this one will work?
Pineapple 6.0 alps-mp-m0.mp1-V2.39 Stock Firmware ROM (Flash File)
Download the official Pineapple 6.0 alps-mp-m0.mp1-V2.39 Stock Firmware ROM (Flash File) for your Unknown Mobile. We also provide all other Unknown Stock Firmware for free.
firmwarefile.com
notnoelchannel said:
maybe this one will work?
Pineapple 6.0 alps-mp-m0.mp1-V2.39 Stock Firmware ROM (Flash File)
Download the official Pineapple 6.0 alps-mp-m0.mp1-V2.39 Stock Firmware ROM (Flash File) for your Unknown Mobile. We also provide all other Unknown Stock Firmware for free.
firmwarefile.com
Click to expand...
Click to collapse
Download quota exceeded.
Please upload that file somewhere else. Google Drive is as*.
jackbauer said:
Download quota exceeded.
Please upload that file somewhere else. Google Drive is as*.
Click to expand...
Click to collapse
I'll mirror it to you (edit: i can't)
Here's another. they aren't password protected:
MT6580_____6.0__alps-mp-m0.mp1-V2.39_nb6580.we.m.7z | by GSM iNFO for Galaxy S6 Edge+
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
MT6580__X30__X30__X30__6.0__alps-mp-m0.mp1-V2.34_droi6580.weg.m_P29 Without Password - GSM-Forum
Download: Oppo Clone R11 Stock ROM Flash File. Oppo Clone R11 Flash File Without Password MT6580__X30__X30__X30__6.0__alps-mp-m0.mp1-V2.34_droi6580.weg
forum.gsmhosting.com