A week ago I bought a Huawei mate 10 with box, was second hand but the aesthetically was new, even with their stickers. The seller did not indicate that the phone had gone through a process of rebranding. Just when I get to my house look for a way to update it and I realized that I did not get the updates by OTA watching the version of the cell I realized that in compilation only appears System 8.0.0.38 (O2YJ) and not as usual. ALP-L29C185 for example. Searching the Internet I found out about everything that is the process of rebranding and what happens to my phone is that the person who did the rebranding did not complete the process, because in the end you have to flash the firmware twice and only once did , is there any way I'm going to do this flash without paying funkyhuawei? Since buying a package of 6 credits to only use one seems ridiculous. No matter if it is an advanced tutorial, I have years experience with Android and Xda Thank you wholeheartedly really need ota updates i have One of they first builds. My original phone model are alp-l29 So I think he rebrand did it to give him IMEI As it was probably a live demo model u.u
ed.ge_2d said:
A week ago I bought a Huawei mate 10 with box, was second hand but the aesthetically was new, even with their stickers. The seller did not indicate that the phone had gone through a process of rebranding. Just when I get to my house look for a way to update it and I realized that I did not get the updates by OTA watching the version of the cell I realized that in compilation only appears System 8.0.0.38 (O2YJ) and not as usual. ALP-L29C185 for example. Searching the Internet I found out about everything that is the process of rebranding and what happens to my phone is that the person who did the rebranding did not complete the process, because in the end you have to flash the firmware twice and only once did , is there any way I'm going to do this flash without paying funkyhuawei? Since buying a package of 6 credits to only use one seems ridiculous. No matter if it is an advanced tutorial, I have years experience with Android and Xda Thank you wholeheartedly really need ota updates i have One of they first builds. My original phone model are alp-l29 So I think he rebrand did it to give him IMEI As it was probably a live demo model u.u
Click to expand...
Click to collapse
Is bootloader still unlocked?
If it is this is a lot easier.
If not you'd have to use DC-unlocker/HCU to get unlock code, then you can rebrand manually to your desired cust.
I think you need 4 credits for that, which is $4 and is a lot cheaper than FH.
ante0 said:
Is bootloader still unlocked?
If it is this is a lot easier.
If not you'd have to use DC-unlocker/HCU to get unlock code, then you can rebrand manually to your desired cust.
I think you need 4 credits for that, which is $4 and is a lot cheaper than FH.
Click to expand...
Click to collapse
How do I know if it's unlocked
ed.ge_2d said:
How do I know if it's unlocked
Click to expand...
Click to collapse
Power off phone, hold volume down and plug in usb c cable from computer to phone.
It will enter fastboot mode and should say "Phone unlock" and hopefully "FRP Unlock".
ante0 said:
Power off phone, hold volume down and plug in usb c cable from computer to phone.
It will enter fastboot mode and should say "Phone unlock" and hopefully "FRP Unlock".
Click to expand...
Click to collapse
Phone Locked, frp unlock.
ed.ge_2d said:
Phone Locked, frp unlock.
Click to expand...
Click to collapse
You can get unlock code then through HCU-client (dc-unlocker). It's the only way to get unlock code, but price is only $4 (4 credits) compared to FH which is $40ish.
After you have unlocked phone (from fastboot, 'fastboot oem unlock ##unlock_code##') you could use TWRP by Pretoriano80 (https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904) and HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to finish rebrand (If you know the intended cust), or use HWOTA to rebrand again to your desired cust (HWOTA: https://mega.nz/#!oeATEQQb!qiP3mYlQQgZYlaS3dbY_QCwNJ-urTKyLQ2zKOA9KP8g).
I have lost instructions to HWOTA though, but it should be doable with the command prompt instructions.
If you're unsure about what cust the seller was planning to rebrand to you can dump OEMINFO from TWRP (Advanced -> Terminal -> dd if=/dev/block/platform/ff3c0000.ufs/by-name/oeminfo of=/sdcard/oeminfo.bin )
then transfer to computer and open it in a hex editor. Then search for the string: 'BLA-', and Search for next until you find one which has Cust in it (For example: BLA-L29 8.0.0.127 (C432) says mine at second result.)
Related
Hi all,
Wishing you all a happy New Year in arrears and the very best for the next 12 months.
I've got a problem with my device, its a STF-AL10 model with international rom bought during the November Sales.
It came with STF-L09C432B150 installed, I got the bootloader unlocked, TWRP installed and rooted with Magisk and was working fine except the capacitive buttons.
I thought I could live without capacitive buttons but I didn't work out and I had the urge to find a solution. After some intensive reseach (48hrs on a weekend in my 'lab') it seems the B120 firmware had no issues with the capacitive buttons, so I tried to downgrade to that and thats when the problems started.
Coming from an ancient Sony Z2, I never had issues flashing ROMS, Kernels and the sort as it was almost always easily done in TWRP or CWM (I had a Multi boot thing going, so I chose which recovery I fancied!). Anyway this are my issues now:
- Obviously, my phone was rebranded at origin as I know for sure AL-10 is not for EU market
- I tried restoring the same STF-L09C432B150 (rollback package found on XDA) with DC-Unlocker (wasted 19 Euro) but did not work. Always stops at 5% near end of flashing.
- Tried B130. same error.
- Tried Chinese STF-AL10C00B110. Same error.
- Tried full board flash for STF-AL10 with all DC Phoenix files. Same error.
- Tried forced method with files on a Sandisk SDcard (64GB) formatted to exFAT. Fails, wrong files.
- I noticed that in ADB, it said my bootloader was unlocked but FRP locked.
- After board flash, ADB said Bootloader unlocked (nothing about FRP) but in Muli-tool it says LOCKED.
- Now all ADB commands the write to the phone give errors.
DC-unlocker support keep on saying I should use the correct firmware for my phone, ok but the phone was rebranded at source...do use a Chinese firmware first then update ?
in desperation I did another full board flash but this time I think I wiped oeminfo and Vendor partions. ( I think this is what caused the HARD-BRICK!). Now no Honor logo, no Recovery, No eRecovery, nothing but a blank black screen. ADB still works but no status about bootloader or FRP.
IMEI has changed to 0123456789ABCDEF
You can all laugh and shake your heads which I will take as my punishment but is there a solution to all this, I'm willing to pay another 19 EUR for DC-Phoenix if it helps to fix my phone and if possible get it rooted with all buttons and functions working. That was my intension all along (I'm not really interested in custom Roms, just root access!).
HCU tool for some reason does not install on my computer, and besides, the phone does not boot into an OS to be able to change OEM and VENDOR data.
I even tried the HOTA.zip in the ReBRAND HONOR 9 thread but the file is missing (link down).
And to top it all there is no UK service center.
Please advise...
I think DC unlock is not supported for thì this model. Did Did you try Huawei Funky???
Apparently all versions of Honor 9 are supported by DC-unlocker and DC-Pheonix....
ums1405 said:
Hi all,
Wishing you all a happy New Year in arrears and the very best for the next 12 months.
I've got a problem with my device, its a STF-AL10 model with international rom bought during the November Sales.
It came with STF-L09C432B150 installed, I got the bootloader unlocked, TWRP installed and rooted with Magisk and was working fine except the capacitive buttons.
I thought I could live without capacitive buttons but I didn't work out and I had the urge to find a solution. After some intensive reseach (48hrs on a weekend in my 'lab') it seems the B120 firmware had no issues with the capacitive buttons, so I tried to downgrade to that and thats when the problems started.
Coming from an ancient Sony Z2, I never had issues flashing ROMS, Kernels and the sort as it was almost always easily done in TWRP or CWM (I had a Multi boot thing going, so I chose which recovery I fancied!). Anyway this are my issues now:
- Obviously, my phone was rebranded at origin as I know for sure AL-10 is not for EU market
- I tried restoring the same STF-L09C432B150 (rollback package found on XDA) with DC-Unlocker (wasted 19 Euro) but did not work. Always stops at 5% near end of flashing.
- Tried B130. same error.
- Tried Chinese STF-AL10C00B110. Same error.
- Tried full board flash for STF-AL10 with all DC Phoenix files. Same error.
- Tried forced method with files on a Sandisk SDcard (64GB) formatted to exFAT. Fails, wrong files.
- I noticed that in ADB, it said my bootloader was unlocked but FRP locked.
- After board flash, ADB said Bootloader unlocked (nothing about FRP) but in Muli-tool it says LOCKED.
- Now all ADB commands the write to the phone give errors.
DC-unlocker support keep on saying I should use the correct firmware for my phone, ok but the phone was rebranded at source...do use a Chinese firmware first then update ?
in desperation I did another full board flash but this time I think I wiped oeminfo and Vendor partions. ( I think this is what caused the HARD-BRICK!). Now no Honor logo, no Recovery, No eRecovery, nothing but a blank black screen. ADB still works but no status about bootloader or FRP.
IMEI has changed to 0123456789ABCDEF
You can all laugh and shake your heads which I will take as my punishment but is there a solution to all this, I'm willing to pay another 19 EUR for DC-Phoenix if it helps to fix my phone and if possible get it rooted with all buttons and functions working. That was my intension all along (I'm not really interested in custom Roms, just root access!).
HCU tool for some reason does not install on my computer, and besides, the phone does not boot into an OS to be able to change OEM and VENDOR data.
I even tried the HOTA.zip in the ReBRAND HONOR 9 thread but the file is missing (link down).
And to top it all there is no UK service center.
Please advise...
Click to expand...
Click to collapse
Try stock service B130 firmware:
https://forum.xda-developers.com/honor-9/how-to/stf-l09c432b130-capacitive-buttons-100-t3729106
Instead of step 4 do forced upload: VOLUME UP + VOLUME DOWN + POWER
Hi,
I've managed to re flash b150. In doing so I got back recovery and erecovery but when you reach that final stage of the process the phone stops at 5%. When I reboot to recovery, factory reset stops at 35%
Any ideas
?
Sent from my [device_name] using XDA-Developers Legacy app
ADB now showing BOOTLOAD UNLOCKED but there is no FRP status.
Sent from my [device_name] using XDA-Developers Legacy app
ums1405 said:
ADB now showing BOOTLOAD UNLOCKED but there is no FRP status.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
FRP status is not only on Chinese phones
you need to sew firmware for al10
The phone was rebounded by the shop I bought it from.
It said STF-L09B150 indexical info when the phone was working.
So if I'm going to repair this brick what update files should I use?
Original Chinese or the b150 used when rebranded?
Sent from my [device_name] using XDA-Developers Legacy app
Hi all,
FYI, I've sent the phone back to the shop I bought it from.
I'll take my chances, better than paying money for something that may not work.
Thanks everyone for showing interest in my situation, I let you all know how I get along with this issue.
Ps.: As a community, lets push Huawei/Honor to release Kernel Sources for this model and others like the P10 Plus.
Ps: Huawei/Honor have to realise that a strong developer community adds value and desirability to a product. That's how a product becomes 'Cool' translating into more revenue/customers/profit - eg OnePlus.
.
Hi all, a quick update .....
Sent the phone back and from what I gather the phone actually had an issue with the main board.
Now enjoying a brand new MATE 10 (Non-pro with 6/128gb) in beautiful Obsidian black.
Wonderful.
Back in december/january some users reported a glitch while rebranding STF-AL10 to STF-L09 with the old nougat hwota (at oem bin flashing step).
After editing hwota script, then rebranded : they ended with a FRP locked status.
Their only way to unlock frp was with dcunlocker or funkyhuawei I don't remember.
After frp unlocked, their bootloader wasn't seen through fastboot.
I think this could be solved by regedit a value in registry.
To my knowledge the only public firmware files working with the dload way (3 buttons + usb connected) are the one titled "service repair", the others one won't work dload as they are. They are for hwota or forcing "official" ota.
Hello together,
today i wanted to rebrand my honor 9 from STF-L00 to STF-L09 and everything worked fine for me at the beginning. I unlock my bootloader and then i used the update.bat and follow the instructions. It installed TWRP. After a while nothing happened and i was still in the fastboot mode. In the fastboot mode i saw that my bootloader is locked again.
Now i have no OS and cannot used adb via fastboot, it does not recognize any device detected.
I downloaded MultiTool and it says i have installed STF-L09 now on my phone.
Info:
According to MultiTool is STF-L09 installed
Bootloader and FRP are locked
I just have Huawei eRecovery, but this is not working (Pacakge info fails)
I have no rom, because my phone is booting only in eRecovery
adb fastboot does not get recognized my phone.
Have all drivers needed on pc for adb to work.
HiSuite doesn't support recovery on this device.
Please help me, i don't know what i should do and i really start to despair. :crying::crying::crying:
Thank you very much
I have pretty much the exact same problem. The only difference is I was trying to rebrand from AL10 to L09. Got the same error in the same stage of rebranding, can access the exact same things as you, same goddamn FRP lock etc. Same all the way through except for starting from AL10 in stead of L00.
I have not found any free solution, the best I could find is DC Phoenix whose program claims that it "Can write firmware by fastboot with locked bootloader and locked FRP!" The thing is, it will cost 15 Euros to use this function in their program, and after paying etc. it is only available for 72 hours. At this moment I don't have access to a computer for the next 72 hours, so I have decided to wait a short while until I have a computer available for a 72-hour period. While I guess it would only take a short time, I realise now that nothing is ever as easy as it seems with Huawei and their absolute **** software... hence I want to wait for being able to use all 72 hours before paying.
This link has their guide to what needs to be done:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
If you want to give it a try, it's the one possible solution I've found after MUCH googling. Though I remain hopeful that someone else on this forum might have a better (free) solution!
Hello Sanktgoran,
at first thank you very much for your help.
I have a question about the DC Unlocker. When i use this and write a new firmware by DC Unlocker, then i don't have to rebrand again?
Which rom do i should use to write on my phone?
Should i use the STF-AL00 rom or STF-L09 rom or it doens't matter?
Multitool says that i have STF-L09 on my phone, but my phone have no OS, because it doesn't boot.
Thanks
I'm not sure actually which one to use. I think you should go with the L09, since that is what the phone "thinks" it is at the moment. If it works to instll the L09 Firmware via DC unlocker, I think that would be the rebranding done as well. The way I understand this situation we are both in, our phones are rebranded to L09, just the actual L09 OS isn't really installed properly, and the FRP lock prevents us from unlocking bootloader, which in turn prevents us from completing the installation of L09. So by using the DC Unlocker to bypass the locks and installing the firmware, the process should then be complete.
I'm not sure about this though, it's just how i think it is. It might be that using DC will install the firmware stably and all is well, and it might be that it will install some of it and then the phone can at least boot into an incomplete OS where we could disable the FRP and bootloader locks, and thus be able to use the Update function in the HWOTA script to get things finished. Either way, I'm 99% sure that using the DC Unlocker will get us further along the path to a european Honor 9 than we are at this stage. I'm going to attempt it later today or perhaps tomorrow I think. After all, 15 euros is a small amount to spend compared to the cost of the actual phone...
Did you also copy an OEMinfo file for L09 into your adb/fastboot folder and run this command before using the HWOTA script?
ADB push oeminfo /tmp/oeminfo
ADB shell "dd if=/tmp/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
I did, I'm not 100% sure what it does/is supposed to do, but I think it has made it so that the phone thinks it's done and rebranded, and tries to boot into L09, but since the L09 installation wasn't completed in the HWOTA script, it can't boot because firmware stuff is missing. That has me thinking that it's the L09 and not AL00 which you should use with DC Unlocker.
Did you check https://forum.xda-developers.com/honor-9/help/soft-bricked-honor-9-trying-to-root-t3737967 ?
Finally, it worked for me everything fine.
Here is one tip from me:
I downloaded at first the rom from a website and started to flash, but it failed.
After a long time of searching and asking, i got help.
You have to download directly from the DC Phoenix the rom (with the custominization file) and flash.
When you don't know how, just post here and i will write a short guide.
Thanks for helping. :good:
That's great, glad things worked out for you! Was it the full firmware file you downloaded from DC Phoenix, the ~4 gigabyte update.app file? Or the three .zip files, update.zip, update_data_full_public.zip and update_full_stf-L09_hw_eu? Do you download it from their website or through the DC Unlocker program? How big was the entire download? I'm on a limited monthly data kind of thing, just curious how big the download is.
Sanktgoran said:
That's great, glad things worked out for you! Was it the full firmware file you downloaded from DC Phoenix, the ~4 gigabyte update.app file? Or the three .zip files, update.zip, update_data_full_public.zip and update_full_stf-L09_hw_eu? Do you download it from their website or through the DC Unlocker program? How big was the entire download? I'm on a limited monthly data kind of thing, just curious how big the download is.
Click to expand...
Click to collapse
I use the download function from DC Phoenix.
When you open DC Phoenix, just click "Download Files" and a website will open, where you can search for the rom.
Search for "STF-L09" and you will get all roms for the STF-L09. I prefer to use this rom:
Stanford-L09_C432B130_Firmware_Belgium_Germany_France_Netherlands_Portugal_Switzerland_Spain_Italy_Aus
And for every rom you should download the customization file. They are directly together:
Stanford-L09_C432B130_update_data_customization_hw_eu.APP
You have to download both .APP files and the both files are in total almost 3,2 GB.
You open DC Phoenix and open the files there.
The Firmware you open in "Update File"
The customization file you open in "Customization File (optional)"
You connect your phone via fastboot and then you can start to update.
I don't know from which country you are, so i don't know which version of rom do you need.
When you download the rom which i downloaded before, you have just the B130 Version. But theres is already B182 existing. You can download the new rom via your phone in the settings.
Here is also the same guide from DC Unlocker (except of the part how you can download the rom).
https://www.dc-unlocker.com/huawei-phone-flashing-in-fastboot
Somehow its possible to flash firmware in dc Phoenix and having a locked Bootloader.
Shouldnt it be possible to use config.txt and flash twrp as recovery and then flash ur full stock?
Im asking cause i m not able to unlock the bootloader. The V+ Button is broke ( Mainboard related) and i cant agree to unlock after entering my code.
I'll try and keep this short, basically I rebranded ALP-L29 to L09 but now I'm looking to root, I found my bootloader unlock key but I keep getting the incorrect password prompt, is there any way round this?
Did you rebrand via Funky Huawei? If so I believe it alters the bootloader in some way so that the original key no longer works. There may be another way, but if not you may have to pay the 4ish EUR to get the new code via DC Unlocker. (I've not done this myself, but was considering rebranding so looked into it)
Thanks, that's exactly what I did
gonzo99 said:
Did you rebrand via Funky Huawei? If so I believe it alters the bootloader in some way so that the original key no longer works. There may be another way, but if not you may have to pay the 4ish EUR to get the new code via DC Unlocker. (I've not done this myself, but was considering rebranding so looked into it)
Click to expand...
Click to collapse
This is exactly why.
It flashes an included oeminfo (that's disguised as well) that has its own imei, meid etc so unlock code won't work anymore after flashing it.
A better way would actually be to just edit your own backed up oeminfo or use mankindtws rebrand tool, it won't make your single sim phone to dual sim though.
ante0 said:
This is exactly why.
It flashes an included oeminfo (that's disguised as well) that has its own imei, meid etc so unlock code won't work anymore after flashing it.
A better way would actually be to just edit your own backed up oeminfo or use mankindtws rebrand tool, it won't make your single sim phone to dual sim though.
Click to expand...
Click to collapse
If fukny Huawei is flashing a standardized IMEI I wonder if one unlock code would work on phones that have been rebranded to the same model/custID if said phones have the same IMEI number?
Might save some people some coins if it worked and those who have already paid were willing to share.
wbrambley said:
If fukny Huawei is flashing a standardized IMEI I wonder if one unlock code would work on phones that have been rebranded to the same model/custID if said phones have the same IMEI number?
Might save some people some coins if it worked and those who have already paid were willing to share.
Click to expand...
Click to collapse
Product ID is still the same as when you bought the phone, which it uses to generate the unlock code.
So it won't work unless you happen to have the same product ID as the "donor" phone that the oeminfo was taken from.
SOlved:
so I was unaware that the bootloader unlock was going to be a problem before I purchased this phone... I did some research before making the purchase and it seemed all was good.
I spent $17 with DC for an unlock... all I got was some nonsense "temporary unlock" SO once I run the temp unlock the phone says "unlocked" on both the phone and the FRP.
FYI.. I also tried HCU client... and it can find the phone but then when I hit "unlock" it says something about a COM error and cant get the code... I tried this with 2 different PCs as well.
I was able to then push the TWRP recovery to it via fastboot. I then did fastboot reboot and went straight into the recovery... and no luck. it brings me right into the EMUI recovery.
is there anyway that I can at least get into TWRP temporarily since I do have the temporary bootloader unlock? or any other way that I can push supersu via fastboot?
this is very frustrating...
Ok so I CAREFULLY re read the directions for HCU... HCU is to be run while the phone is still on in the OS. not in fastboot which was my mistake all along.
so the key is to go into the dialer and enable manufacure mode... then run HCU while the phone is still on.
another key is to disable the Huawei software ... IM not sure if this is necessary but I think its a good idea because I noticed that the software itself causes the phone to go back to Hisuite mode instead of manufacturer mode. so I went into windows services and disabled hisuite... and closed out of it.
Hope this helps someone else
and do not waste your money on the DC program!!! you have to purchase your credits from DC but dont use the DC client. I am currently working on getting a refund for my first wasted credits. also they charge 15 credits for this unlock which is $18 USD! but thats not so bad considering I got this phone for $499 from newegg brand new
ilmar72 said:
SOlved:
so I was unaware that the bootloader unlock was going to be a problem before I purchased this phone... I did some research before making the purchase and it seemed all was good.
I spent $17 with DC for an unlock... all I got was some nonsense "temporary unlock" SO once I run the temp unlock the phone says "unlocked" on both the phone and the FRP.
FYI.. I also tried HCU client... and it can find the phone but then when I hit "unlock" it says something about a COM error and cant get the code... I tried this with 2 different PCs as well.
I was able to then push the TWRP recovery to it via fastboot. I then did fastboot reboot and went straight into the recovery... and no luck. it brings me right into the EMUI recovery.
is there anyway that I can at least get into TWRP temporarily since I do have the temporary bootloader unlock? or any other way that I can push supersu via fastboot?
this is very frustrating...
Ok so I CAREFULLY re read the directions for HCU... HCU is to be run while the phone is still on in the OS. not in fastboot which was my mistake all along.
so the key is to go into the dialer and enable manufacure mode... then run HCU while the phone is still on.
another key is to disable the Huawei software ... IM not sure if this is necessary but I think its a good idea because I noticed that the software itself causes the phone to go back to Hisuite mode instead of manufacturer mode. so I went into windows services and disabled hisuite... and closed out of it.
Hope this helps someone else
and do not waste your money on the DC program!!! you have to purchase your credits from DC but dont use the DC client. I am currently working on getting a refund for my first wasted credits. also they charge 15 credits for this unlock which is $18 USD! but thats not so bad considering I got this phone for $499 from newegg brand new
Click to expand...
Click to collapse
Temp unlock lets you flash anything (stock images) from fastboot. So essentially you could flash a whole firmware using only images in Fastboot mode.
Twrp don't work as you need to be unlocked to use it, even if you have Twrp it will reboot to sec_recovery when you are locked.
Do you remember wich firmware was in your phone before you unlock your bootloader?
basty95 said:
Do you remember wich firmware was in your phone before you unlock your bootloader?
Click to expand...
Click to collapse
It was c567. The latest one for the bla-a09
how temp unlock for flashing firmware in fastboot not twrp ... i need command thanks in advance
Hi, @ante0 , @Pretoriano80 and everyone else!
Been lurking on these forums ever since mate 10 Pro was released, but due to being one of the folks to downgrade from emui 9 to brick I had to take my phone to service for board swapping as I wasn't in a situation to do the testpoint fix myself.
Now, I'm looking to get the bootloader unlock code again and to my surprise even the 3rd party sites are down.
There's a guy at minstryofsolutions that offers bootloader unlock code using testpoint but he asks for 40$ + access to pc for 2 hours + refuses to describe in any way what he's doing to the device and why will the device end up rebranded + new imei and with it new bootloader code ( Obviously device in that condition can't be taken into a Huawei service center) .
So, upon searching and trying to find if anyone had found a way to unlock using testpoint I stumbled upon this : https://forum.xda-developers.com/mediapad-m5/how-to/downgrade-unbrick-huawei-device-methods-t3915693
Op and several others seem successful with downgrading their devices and using dc unlocker to get the code once the security patch is no more.
Op even mentions that for kirin 970 it's probably the same process but I haven't seen anyone sharing their experience doing the same on 979 devices.
Couple users are having issues as well and while op was quite helpful he and several others that were helping out seem to have been gone missing. There's a guy helping out with issues regarding this process but it seems rather finicky when even after doing all this and flashing with dload certain parts like lte modem remain present on a WiFi only tablet.
Does anyone have passes for easy firmware or dc unlocker firmware database? Is anyone willing to give these a try and see if the process will work on our devices or if it will ask for verification of some kind for images being flashed?
It looks quite promising, so if anyone has a bricked device ( Maybe someone that was refused at the Huawei repair center during the wave of downgrades ) would you be willing to give it a try?
I've got no tools, no passes and no other device to use while playing with this.
Obviously, I'm not asking for you guys to go out of your way and brick the device so I can know whether this is a viable option or not lol.
Just thought about sharing and seeing if anyone more knowledgeable has anythiny they'd like to add to this as a tip or personal experience trying this method.
This might be what we are looking for when it comes to unlocking device / downgrading to lower versions.
Hopefully the post I linked helps someone, in case anyone has experience with this please share as well!
Anyways thanks in advance!
Rstment ^m^ said:
Hi, @ante0 , @Pretoriano80 and everyone else!
Been lurking on these forums ever since mate 10 Pro was released, but due to being one of the folks to downgrade from emui 9 to brick I had to take my phone to service for board swapping as I wasn't in a situation to do the testpoint fix myself.
Now, I'm looking to get the bootloader unlock code again and to my surprise even the 3rd party sites are down.
There's a guy at minstryofsolutions that offers bootloader unlock code using testpoint but he asks for 40$ + access to pc for 2 hours + refuses to describe in any way what he's doing to the device and why will the device end up rebranded + new imei and with it new bootloader code ( Obviously device in that condition can't be taken into a Huawei service center) .
So, upon searching and trying to find if anyone had found a way to unlock using testpoint I stumbled upon this : https://forum.xda-developers.com/mediapad-m5/how-to/downgrade-unbrick-huawei-device-methods-t3915693
Op and several others seem successful with downgrading their devices and using dc unlocker to get the code once the security patch is no more.
Op even mentions that for kirin 970 it's probably the same process but I haven't seen anyone sharing their experience doing the same on 979 devices.
Couple users are having issues as well and while op was quite helpful he and several others that were helping out seem to have been gone missing. There's a guy helping out with issues regarding this process but it seems rather finicky when even after doing all this and flashing with dload certain parts like lte modem remain present on a WiFi only tablet.
Does anyone have passes for easy firmware or dc unlocker firmware database? Is anyone willing to give these a try and see if the process will work on our devices or if it will ask for verification of some kind for images being flashed?
It looks quite promising, so if anyone has a bricked device ( Maybe someone that was refused at the Huawei repair center during the wave of downgrades ) would you be willing to give it a try?
I've got no tools, no passes and no other device to use while playing with this.
Obviously, I'm not asking for you guys to go out of your way and brick the device so I can know whether this is a viable option or not lol.
Just thought about sharing and seeing if anyone more knowledgeable has anythiny they'd like to add to this as a tip or personal experience trying this method.
This might be what we are looking for when it comes to unlocking device / downgrading to lower versions.
Hopefully the post I linked helps someone, in case anyone has experience with this please share as well!
Anyways thanks in advance!
Click to expand...
Click to collapse
You can as I've done it.
Use testpoint (this will void warranty as you have to remove back of the phone) and flash bootloader files from DC Phoenix, there are several Kirin970 to choose from but only one should work. DC will tell you when phone is in fastboot mode after flashing.
Then I used IDT (Image Download Tool) to flash board firmware. Boot to board firmware and used HCU to repair imeis and all that. Then used HCU to get an unlock code. After this flash dload firmware back to Oreo (needs to be a new dload because of updated bootloader).
HCU fix guide for BLA:
1)Flash oeminfo (own backup) from fastboot OR dump existing oeminfo using adb pull (adb pull /dev/block/bootdevice/by-name/oeminfo) then flash it from fastboot.
2)Backup modemnvm_system, modemnvm_factory and modemnvm_backup using adb pull from a command prompt (/dev/block/bootdevice/by-name/modemnvm_system and so on)
3)Flash backed up modemnvm_system, modemnvm_factory and modemnvm_backup from fastboot
3)Modify and brand with HCU in the CDMA tab (check everything but those that erase/flash empty board) (remember to fill vendor and cust)
4)Unlock sim 'Direct SIM Unlock'
5)Read Bootloader code if you ever used HCU to get code before or if you need unlock code
6)Download and flash Oreo service firmware from androidhost.ru using a OTG cable and a memory stick. Pick the latest Oreo one you find for your cust
If you fail to do any of the steps above you will end up with no IMEIs or 'No Network' and/or Sim lock
So you'd need: DC/HCU pass and unencrypted board firmware (gem-flash and easy-firmware has them but they're paid.).
I have not tested using DCs own board firmware.
ante0 said:
You can as I've done it.
Use testpoint (this will void warranty as you have to remove back of the phone) and flash bootloader files from DC Phoenix, there are several Kirin970 to choose from but only one should work. DC will tell you when phone is in fastboot mode after flashing.
Then I used IDT (Image Download Tool) to flash board firmware. Boot to board firmware and used HCU to repair imeis and all that. Then used HCU to get an unlock code. After this flash dload firmware back to Oreo (needs to be a new dload because of updated bootloader).
HCU fix guide for BLA:
1)Flash oeminfo (own backup) from fastboot OR dump existing oeminfo using adb pull (adb pull /dev/block/bootdevice/by-name/oeminfo) then flash it from fastboot.
2)Backup modemnvm_system, modemnvm_factory and modemnvm_backup using adb pull from a command prompt (/dev/block/bootdevice/by-name/modemnvm_system and so on)
3)Flash backed up modemnvm_system, modemnvm_factory and modemnvm_backup from fastboot
3)Modify and brand with HCU in the CDMA tab (check everything but those that erase/flash empty board) (remember to fill vendor and cust)
4)Unlock sim 'Direct SIM Unlock'
5)Read Bootloader code if you ever used HCU to get code before or if you need unlock code
6)Download and flash Oreo service firmware from androidhost.ru using a OTG cable and a memory stick. Pick the latest Oreo one you find for your cust
If you fail to do any of the steps above you will end up with no IMEIs or 'No Network' and/or Sim lock
So you'd need: DC/HCU pass and unencrypted board firmware (gem-flash and easy-firmware has them but they're paid.).
I have not tested using DCs own board firmware.
Click to expand...
Click to collapse
Thanks a lot!
Will any of this process leave bootloader unlocked / relocked along the way?
I'm experiencing screen burn in due to outdated firmware and was gonna get the code, apply new adhesive I buy online and have them replace the device's screen + seal it properly in the process so the water resistance remains - kinda essential to hide any signs of tampering like bootloader unlock '-' ( 2nd burn in on Oreo firmware now, both happened within few months of the device running old firmw )
Thanks for the guide as well!
I'm not completely sure how to do the whole process yet but I'll try getting all the software I can right now and try figuring it out.
One question tho, do you have any screenshots you can share of which firmware will work out of those several that you mentioned and is there any possibility of brick by flashing wrong xload, etc.?
I'm on 8.0.0.156 c432 and was gonna drop to 142 or 143 - will have to check which one is the latest without security patch.
Glad to know this is a possibility! Will order the tools required for this and when / if I'm successful I'll create seperate thread under guides as there prolly are peps still trying to unlock.
Rstment ^m^ said:
Thanks a lot!
Will any of this process leave bootloader unlocked / relocked along the way?
I'm experiencing screen burn in due to outdated firmware and was gonna get the code, apply new adhesive I buy online and have them replace the device's screen + seal it properly in the process so the water resistance remains - kinda essential to hide any signs of tampering like bootloader unlock '-' ( 2nd burn in on Oreo firmware now, both happened within few months of the device running old firmw )
Thanks for the guide as well!
I'm not completely sure how to do the whole process yet but I'll try getting all the software I can right now and try figuring it out.
One question tho, do you have any screenshots you can share of which firmware will work out of those several that you mentioned and is there any possibility of brick by flashing wrong xload, etc.?
I'm on 8.0.0.156 c432 and was gonna drop to 142 or 143 - will have to check which one is the latest without security patch.
Glad to know this is a possibility! Will order the tools required for this and when / if I'm successful I'll create seperate thread under guides as there prolly are peps still trying to unlock.
Click to expand...
Click to collapse
I doubt that the burn-in is because of the old firmware, probably the oled panel it's getting old.
You should do the other way around, first send it to Huawei for a display replacement and then get the unlock code.
The procedure it's not really easy and the water resistant part it's the last of your problem, first you must make sure that you don't break the glass back cover when you open it up. xD
Probably Huawei's repair center won't even bother to replace the display only, but they will replace almost everything, so you would endup with a locked bootloader again.
Pretoriano80 said:
I doubt that the burn-in is because of the old firmware, probably the oled panel it's getting old.
You should do the other way around, first send it to Huawei for a display replacement and then get the unlock code.
The procedure it's not really easy and the water resistant part it's the last of your problem, first you must make sure that you don't break the glass back cover when you open it up. xD
Probably Huawei's repair center won't even bother to replace the display only, but they will replace almost everything, so you would endup with a locked bootloader again.
Click to expand...
Click to collapse
The display literally burned in couple months after I boguht the device and and we still had the emui 8 only. Replaced it and switched to the 9 the same month. All was good for a year or so untill they replaced motherboard. Now the same thing all over again, few months have passed - literally 2/3 months and the screen burned in again at the same spot - navigation bar.
The opening part doesn't look that complicated, was thinking of buying a heating plate, heat phone to 120°C and go back and forward cutting adhesive then heating the phone again. Should be fast and efficient this way.
The finicky part that I'm worried about has to do with bricking the device or shorting the motherboard in some way '-' Maybe service also uses some repair stickers that aren't present on any of the guides and will get dmged when I open the device - after all, I took the device for repairs under warranty at least 5+ times by now
Last time for the replacement they indeed replace almost everything - display, battery, back cover, new frame - essentially a new device w same motherboard.
Pretoriano80 said:
I doubt that the burn-in is because of the old firmware, probably the oled panel it's getting old.
You should do the other way around, first send it to Huawei for a display replacement and then get the unlock code.
The procedure it's not really easy and the water resistant part it's the last of your problem, first you must make sure that you don't break the glass back cover when you open it up. xD
Probably Huawei's repair center won't even bother to replace the display only, but they will replace almost everything, so you would endup with a locked bootloader again.
Click to expand...
Click to collapse
Rstment ^m^ said:
The display literally burned in couple months after I boguht the device and and we still had the emui 8 only. Replaced it and switched to the 9 the same month. All was good for a year or so untill they replaced motherboard. Now the same thing all over again, few months have passed - literally 2/3 months and the screen burned in again at the same spot - navigation bar.
The opening part doesn't look that complicated, was thinking of buying a heating plate, heat phone to 120°C and go back and forward cutting adhesive then heating the phone again. Should be fast and efficient this way.
The finicky part that I'm worried about has to do with bricking the device or shorting the motherboard in some way '-' Maybe service also uses some repair stickers that aren't present on any of the guides and will get dmged when I open the device - after all, I took the device for repairs under warranty at least 5+ times by now
Last time for the replacement they indeed replace almost everything - display, battery, back cover, new frame - essentially a new device w same motherboard.
Click to expand...
Click to collapse
Also, if they do replace stuff the code you get through DC will not work.
It works by modifying some strings in the oeminfo partition, so if they were to wipe and reflash everything your code would be lost.
If they replace motherboard you will need a new unlock code.
There is a sticker on one of the screws you need to remove, so they will know you did open it anyway.
Bricking is no problem as you can unbrick using testpoint. Shorting shouldn't be a problem. I tried all the visible points and only 1 or 2 actually send current back so USB devices in computer restarted xD But none of them shorted my phone.
ante0 said:
Also, if they do replace stuff the code you get through DC will not work.
It works by modifying some strings in the oeminfo partition, so if they were to wipe and reflash everything your code would be lost.
If they replace motherboard you will need a new unlock code.
There is a sticker on one of the screws you need to remove, so they will know you did open it anyway.
Bricking is no problem as you can unbrick using testpoint. Shorting shouldn't be a problem. I tried all the visible points and only 1 or 2 actually send current back so USB devices in computer restarted xD But none of them shorted my phone.
Click to expand...
Click to collapse
I see on pictures online that there are some points exposed with the shield on. Will take a look at picture you posted earlier for testpoint location to determine if indeed you can access it without removing the shield - hence not touching the stickers you mentioned - ty!
Wdym by losing dc unlocker code tho?
Does it not read the bootloader code of the device - meaning after they wipe / flash their stuff I can use the same code again to unlock via fastboot?
Or can it not read the code and just modifies the nvme files or whatev inside the partition to allow for a custom bootloader code?
Thanks for all the info! Will go look now for the picture then decide whether I'll open before or afterwards depending on the position of test point.
Rstment ^m^ said:
I see on pictures online that there are some points exposed with the shield on. Will take a look at picture you posted earlier for testpoint location to determine if indeed you can access it without removing the shield - hence not touching the stickers you mentioned - ty!
Wdym by losing dc unlocker code tho?
Does it not read the bootloader code of the device - meaning after they wipe / flash their stuff I can use the same code again to unlock via fastboot?
Or can it not read the code and just modifies the nvme files or whatev inside the partition to allow for a custom bootloader code?
Thanks for all the info! Will go look now for the picture then decide whether I'll open before or afterwards depending on the position of test point.
Click to expand...
Click to collapse
When you use HCU to get code it writes stuff to oeminfo, replacing 2 strings with "DC-UNLOC". So that's used in calculation of code. If you flash back stock, unmodified, oeminfo after using HCU you won't be able to use the code it generated.
Testpoint is located under the shield, so it's not possible to get to it without removing the shield. I have my phone with shield on infront of me. And I can't remember which screw had the sticker on it. If it's on one of the corners I guess you could try to bend it up to get to testpoint.
I just can't understand why the won't release the bootloader unlock at this point? The phone is now 'outdated' and old.... where is the harm?
ante0 said:
When you use HCU to get code it writes stuff to oeminfo, replacing 2 strings with "DC-UNLOC". So that's used in calculation of code. If you flash back stock, unmodified, oeminfo after using HCU you won't be able to use the code it generated.
Testpoint is located under the shield, so it's not possible to get to it without removing the shield. I have my phone with shield on infront of me. And I can't remember which screw had the sticker on it. If it's on one of the corners I guess you could try to bend it up to get to testpoint.
Click to expand...
Click to collapse
Thanks but I'm still having hard of a time following ?
After you use hcu it modifies the oeminfo to get strings it needs for calculations - You get the code aftwerards and your oeminfo is modified, right?
What I don't get is how flashing stock makes code unusable tho?
Is it not original bootloader code we'd get if Huawei site was still up? That code should be usable even after all modifications were reflashed with stock, no?
Or is it a custom code that depends on modified oeminfo to work?
Rstment ^m^ said:
Thanks but I'm still having hard of a time following ?
After you use hcu it modifies the oeminfo to get strings it needs for calculations - You get the code aftwerards and your oeminfo is modified, right?
What I don't get is how flashing stock makes code unusable tho?
Is it not original bootloader code we'd get if Huawei site was still up? That code should be usable even after all modifications were reflashed with stock, no?
Or is it a custom code that depends on modified oeminfo to work?
Click to expand...
Click to collapse
It's a custom code. If you use HCU to generate a code it invalidates your stock code. If you flash back stock oeminfo you can use the code Huawei gave you but not the HCU code (until you use HCU again to generate code).
Iirc on Kirin960 (and probably below it) you can use both HCU and stock code, so it uses another way of generating it I guess
Has anyone tried this approach for a MATE 10? or would you recommend it?
FUHuawei said:
Has anyone tried this approach for a MATE 10? or would you recommend it?
Click to expand...
Click to collapse
What method are you talking about?
If through testpoint, then yes!
Everything works perfectly
geogsm_1 said:
What method are you talking about?
If through testpoint, then yes!
Everything works perfectly
Click to expand...
Click to collapse
Yes, of course, I meant through test point. Do you know of any good step by step guide on how to do it? I want to try it and post here my results, if everything goes well I hope everyone ditches huawei software.
Also, I have searched around for options regarding ROMs, does anyone recommend anything in particular?
FUHuawei said:
Yes, of course, I meant through test point. Do you know of any good step by step guide on how to do it? I want to try it and post here my results, if everything goes well I hope everyone ditches huawei software.
Also, I have searched around for options regarding ROMs, does anyone recommend anything in particular?
Click to expand...
Click to collapse
Yes, I know the method) and have long written instructions on another forum with the permission of my teacher.
Decision made
On Huawei Mate 10 / Mate 10 Pro /, you can get the bootloader unlock code using a testpoint. But you need to have a programmer such as MRT / SIGMA / HDE / HCu-Client