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.
Related
Let me just start off by saying I have tried everything (free) under the sun to unlock my S3 (I9300). I have learnt more in the last 2 days about my phone than I have in the past 2 years of owning it. From rooting and trying unlock apps to downgrading and trying the service mode glitch, I've tried it. It is more of a quest at this point. I would have paid to unlock it by now if it wasn't for my stubbornness.
From what I understand, since I am on version 4.3 and have EFS v2 (with no EFS v1 backup), there is no way to network unlock my phone without getting an unlock code from my network or a website, both of which require payment.
I can understand how the network is able to get an unlock code but what I don't understand is how various websites can 'calculate' unlock codes for my device, especially without the device at hand.
In theory, why can't I calculate the unlock codes myself? If I can, how?
No, codes aren't calculated -they come from a database that you can't access. Give up and buy a code.
BPate said:
I can understand how the network is able to get an unlock code but what I don't understand is how various websites can 'calculate' unlock codes for my device, especially without the device at hand.
In theory, why can't I calculate the unlock codes myself? If I can, how?
Click to expand...
Click to collapse
I actually have the codes that Vodafone provides free of charge with it's Network unlocking tool, unfortunately these codes don't work and they have yet to give me a reason why. The only thing I can hope for is a way to flash back to efs v1 but so far as I know it's impossible.
I bought a sgh-t399n at a garage sale recently and quickly rooted the phone and installed TWRP Recovery and CM12 on it. I called Metro and T-Mobile ( After flashing their firmware) for the unlock code but of course they refused to give it to me. So i tried 2 or 3 different unlock by IMEI websites as well as every single unlock app and software I could find while running logcat. The best lead I've gotten was the S.G.S. Unlock Tool app. It says it found the code but the results are null. In the logcat the system denies permission saying that the app was sending request as -2 when it was 0 and that it needed "android.permission.INTERACT_ACROSS_USERS_FULL" to accsess the info. Now I'm not a Dev by any definition of the term, nor am I any kind of hacker but I have learned a good bit from these forums over the last couple of years and my gut tells me this can be done with a little patients and some help from the good folks at XDA. Any imput on the subject is greatly appreciated.
You won't be able to unlock on CM12, have to have the stock firmware and OS installed.
yeah install stock system and any code should work without issue
If you unlock on stock system and then flash cyanogen, will it be fine?
-Tofu- said:
If you unlock on stock system and then flash cyanogen, will it be fine?
Click to expand...
Click to collapse
Yes.
es0tericcha0s said:
Yes.
Click to expand...
Click to collapse
The unlock code must be hidden on one of the partitions of the device it's self though right? Possibly in the EFS partion? Also how would i change thepermissions of an app to allow in to interact acroo all users?
Whether or not the code is in EFS, you still can't unlock on CM.
No I understand that. It is currently on the T-Mobile stock T399 firmware flashed with odin but still could not get an unlock code . Also i would like to learn to unlock these phones for future devices.
So it is not requesting an unlock code when you have a non T-Mobile SIM card installed? How odd... It should. If not, either it's already unlocked, or something else is going on. Have you tried both the Metro and Tmo firmware? Only the newest T-Mobile and Metro phones are not supported by unlocking via code as they use the Unlock app. As far as unlocking yourself, your best bet would be to get an unlock box like z3x or Octopus if you plan on doing a lot of them. If it's just 1 every year or 2, then it wouldn't make sense. Some phones have ways to unlock via root and hacks, but not all and it is becoming less common now as more manufacturers are making the ways to unlock more difficult either via encryption or other means.
The unlock companies I tried were unable to get a code by imei. Therefore I was never able to put in a real code. I've looked in to the z3x but it is way outta my price range as I am only a novice tinker. I just figured since the code must be in the programing of the phone somewhere then it was just a matter of locating the partition and file in which it was hidden and then decoding it. Is it possible to change an apps or users permissions? If so how?
rkey1000 said:
The unlock companies I tried were unable to get a code by imei. Therefore I was never able to put in a real code. I've looked in to the z3x but it is way outta my price range as I am only a novice tinker. I just figured since the code must be in the programing of the phone somewhere then it was just a matter of locating the partition and file in which it was hidden and then decoding it. Is it possible to change an apps or users permissions? If so how?
Click to expand...
Click to collapse
I believe the app Root explorer allows you to change permissions on items.
It does, but nothing Root Explorer can do will help you find an unlock code, unfortunately. If the phone does not ask for a code when inserting another carrier's SIM, then that's the issue that would need to be resolved before anything else.
Sorry if I've been unclear. The phone dose ask for a code when a sim from a different carrier is put in but after trying 3 unlock by IMEI companies none of them were able to generate a code by IMEI. As for the permissions issue, I have an app that claims to find the codes but only says "null" in the results column. After going through the log cat it says the app is running as user 0 but is requesting info as user -2 and that it needs the permission " INTERACT_ACROSS_USERS_FULL" to show the info. So i was hoping to learn how i grant said app that permission and see if it would show the code?
solidus636 said:
yeah install stock system and any code should work without issue
Click to expand...
Click to collapse
can you paste a link to the stock system?
Could anyone PLEASE PLEASE PLEASE PLEASE PLEASE give me a working unlock code for my metro pcs phone email me [email protected] or [email protected] thank you.
Running into the same problem only im on a non rooted system. I need a solution to get the codes needed to unlock it from T-mobile and need them without running hardware as all i have is hardware from the old days. Software would be a choice if anyone knows of anything reliable. Services I am also willing to pay for if cheap and working.
Why does each of us have to pay to unlock their phone model from a network when only one of us could unlock and then help others ?
Thats why I think we need to understand how phone unlocking works. I've searched and could not find any tutorial. I suggest this to be general advice and not any specific device.
So questions:
When I insert the unlock code into an android device, what files or partitions are modified ? Then could we not clone that and share the image with other users ?
It doesn't work like that. Each IMEI gets its own code by the carriers. It's not even an Android thing as all software come to the carrier unlocked and the carrier then adds in its own stuff excluding then lock codes.
We all know that each phone has its own IMEI. But to be more clear in byte-code language, we need to understand, how does the phone itself know "am I a locked phone or an unlocked one ?" Or in other words, do those who own websites to unlock code break the algorithm themselves or do they buy it from producers ?
Actually some have discovered that it's mmcblk0p6 in their case that changes when applying the unlock code, and using tools such as "string -n 8" to read that partition. But we need to uncover more than that, we don't know the partition name that need to be changed in other cases.
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.)
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