Related
Can any developer please please help me out quickly? i'm out of time seriously I need help but quick.
I'm trying to unlock my device Redmi Note 3 Snapdragon varient. All the other commands like
* adb devices
* adb reboot edl
* fastboot devices
* fastboot oem device-info
everyone of it is working fine but when I write
* fastboot oem unlock-go
I get the above mentioned error.
Does anybody know the solution to it? Before answering please consider that other commands are working except this one, I didn't found any proper solution that's why posted the problem here and I already did revoke USB debugging permissions and turned it on again but that didn't helped.
So please give me a working solution as quick as possible or else any help is appreciable.
enable oem unlock in developer options
Enable OEM Unlock option in Developer Options.
caesar13th said:
enable oem unlock in developer options
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
superboy123 said:
Enable OEM Unlock option in Developer Options.
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Gurkirat_Singh said:
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Click to expand...
Click to collapse
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
superboy123 said:
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
Click to expand...
Click to collapse
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Gurkirat_Singh said:
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Click to expand...
Click to collapse
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
superboy123 said:
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
Click to expand...
Click to collapse
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Gurkirat_Singh said:
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Click to expand...
Click to collapse
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
Thanks for all the support and help you gave me.
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
caesar13th said:
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Gurkirat_Singh said:
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Click to expand...
Click to collapse
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
superboy123 said:
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
Click to expand...
Click to collapse
I appreciate your help but the post you gave me is for non-asian countries so it will not work for me. As you already know I'm an Indian so that's why. Are you an Indian, only asking cause in that way you may already faced the problems i'm having.
I'm only familiar with only 2 4G networks for now. One is Airtel 4G, what they say have FDD LTE network, I don't what that is, but that's why it's not working on my phone, I contacted them and they said that my phone doesn't support it, I don't know why cause it support much more LTE Bands other than any smartphone in that price range. Second is Jio 4G, my sim gets detected, shows network in manual selection but doesn't get registered on them. I see only the message of 'No Service' or 'Emergency calls only' when I insert it.
@Gurkirat_Singh
It worked for me.
I had the same problem!
superboy123 said:
@Gurkirat_Singh
It worked for me.
I had the same problem!
Click to expand...
Click to collapse
What worked for you and how? Can you please answer/clarify my questions/doubts please also?
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
superboy123 said:
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
Click to expand...
Click to collapse
OK I'll try when got time and will update you with the 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
I successfully upgraded to miui 12 , after that i did some try to get back in miui 11 grobal rom . now the phone is not responding. no screen on, no vibration. but when I connect the phone with mi flash tool, here it is showing com3 . Is there any way to get back the phone? please help with some suggestion .!!!!!!!!:crying::crying::crying::crying:
royk9635 said:
I successfully upgraded to miui 12 , after that i did some try to get back in miui 11 grobal rom . now the phone is not responding. no screen on, no vibration. but when I connect the phone with mi flash tool, here it is showing com3 . Is there any way to get back the phone? please help with some suggestion .!!!!!!!!:crying::crying::crying::crying:
Click to expand...
Click to collapse
Hardbricked because of ARB..
Just send it to mi center to fix it..i guess it still have warranty
You will lost your warranty if you try to tear it down
getsuga92 said:
Hardbricked because of ARB..
Just send it to mi center to fix it..i guess it still have warranty
You will lost your warranty if you try to tear it down
Click to expand...
Click to collapse
Thank you brother it has warranty. but is there any chance to void warranty ,cause I unlocked bootloader. if they refuse to give me free servicing after they fix the phone. casue they will understand bootloader unlock after they fix the phone and ask for money
royk9635 said:
Thank you brother it has warranty. but is there any chance to void warranty ,cause I unlocked bootloader. if they refuse to give me free servicing after they fix the phone. casue they will understand bootloader unlock after they fix the phone and ask for money
Click to expand...
Click to collapse
If it hardbricked, then there will flash all the system via edl mode, all the data will be gone, but i don't know if the bootloader get lock again or not..anyway, unlocked bootloader not a big issue i think
Maybe interesting for this topic:
https://www.xda-developers.com/xiaomi-india-clarifies-bootloader-unlocking-does-not-void-warranty/
You must Use the fastboot version
https://mirom.ezbox.idv.tw/en/phone/joyeuse/
unzip *.tgz via winrar, 7-zip etc.
The folder with the extracted files must be on the root of a partition, otherwise there are error messages
Then switch on the cell phone via
power + volume down <---(Edit: sorry, down not up)
start in fastboot mode
- Connect phone via USB cable
- Start the MiFlash tool.
- Use "Select" to set the path to the folder or immediately paste the path previously copied in the file manager into the address bar of the flash tool.
- Select "clean all" below
- Refresh once
- now "flash" at the top right
PS:
bootloader is normally not locked again unless you select "clean and lock".
but if it should be blocked for whatever reason, that's no problem.
Once unlocked there is no longer a waiting time when unlocking again.
Simply start the "miflash unlock" tool, sign in and unlock again
Hi
So I'm new to this forum and I don't know if I'm in the right place but my Redmi Note 9S had contact with water and now the screen has lines on it and is unresponsive to touch.There are also layers of water and some part of the screen is darker than the rest but no hardware was affected....just the screen
Any help is appreciated
hello .... I have a sister redmi note 4 who has a bootloop ... on the screen with the MI logo it keeps restarting .... it goes to fastboot but not to recovery ... the bootloader is locked and I still can't unlock it because what I looked so unlocked in the system by logging into my MI account ... but I can't get to the system ... I tried my flash but it says that it did something for 4 seconds and nothing still the same .... I tried to put it into download mode - by connecting contacts on the board and miflash download ROM to the phone but bootloop still continues
do you have any ideas?
the phone was so stupid that it kept restarting but always after several restarts it started but now even after two days of restart it didn't start ...
thanks sorry for my english
I had a stroke reading this.
Unlocked bootloader is the basic requirement of flashing. If you don't have it, then sorry you're out of options.
Your only option is to flash stock ROM through test-point method. DO IT ON YOUR OWN RISK.
You can find Xiaomi stock ROMs of your device here (MTK) or here (MIDO).
Of course you can always just send your device to a repair center and change it there.
Goodluck.
test point method is lint two pins od board and run mobile to download mode? I try it ... flashing was succesfull but mobile ist still bootloop
johnyfly1 said:
test point method is lint two pins od board and run mobile to download mode? I try it ... flashing was succesfull but mobile ist still bootloop
Click to expand...
Click to collapse
You need to flash stock ROM not any other ROM.
As in the same ROM you had before any issue. Because your bootloader is locked it will refuse to run any boot image that isn't registered in it.
If you have a backup maybe you can flash it through download mode.
I try ROMs from your link and not working...always bootloop I try a lot of ROMs - global, china, stable, weekly and not working....flash is succesfull around 190seconds.... but still bootloop
johnyfly1 said:
I try ROMs from your link and not working...always bootloop I try a lot of ROMs - global, china, stable, weekly and not working....flash is succesfull around 190seconds.... but still bootloop
Click to expand...
Click to collapse
Do you know what ROM you had before the issue started?
I dont know is sister phone... but she have original stock rom... i think global because phone was buy on slovakia
johnyfly1 said:
I dont know is sister phone... but she have original stock rom... i think global because phone was buy on slovakia
Click to expand...
Click to collapse
I Can't help you there mate.
Maybe there is a way to get system info from bricked phone. Maybe through a hex editor or something. That way you know exact version of the ROM you had.
So instead of that maybe you can unlock your bootloader, just request from Xiaomi unlock code with your XIaomi account and unlock it. It usually takes 30-60 days for the request to go through.
Where I find old way to unlock bootloader? because in new unlocker I unlock phone butt I must log in to my account in system... thanks
johnyfly1 said:
Where I find old way to unlock bootloader? because in new unlocker I unlock phone butt I must log in to my account in system... thanks
Click to expand...
Click to collapse
There is no other way to unlock bootloader. Unless you know a guy, know what I'm sayin?
I just bought Realme 7 Pro 8/128 from Amazon.de warehouse (EU version) and when I started it, I found that the fingerprint sensor doesn't work - it doesn't allow to scan any fingerprints, only message "Add a fingerprint" is blinking, without even showing the place to put the finger.
Video of the problem
I Googled this problem and found that it usually happens when somebody unlocks the bootloader (and probably flashes magisk), which someone might do before sending it back to Amazon, but I didn't find any resolution to it. I have seen that OEM unlock in Developer options was enabled, but the bootloader was locked.
I have seen hints that it couls fix flashing the full OFP firmware, so I unlocked the bootloader, downloaded a few OFP firmwares, Realme Flash Tool can't flash any of them - it throws error "Cannot find central directory". I didn't have any luck also with MsmDownloadTool - version 1.x or 2.x that is bundled with the firmware asks for login and password. Version 4.x or 5.x says that no file is found or that it doesn't match the tool version.
I was able to flash OZIP firmware from stock recovery and lock the bootloader again, but it didn't solve the problem.
Any ideas how the fingerprint scanner can be fixed?
I have exactly the same problem
nirmago said:
I have exactly the same problem
Click to expand...
Click to collapse
Did you have it also from the beginning, or it started after you unlocked the bootloader? Did you try flashing some custom ROM, or Android 11, if it works there?
So in the end I sent the phone to Realme service for warranty repair and they fixed it by reflashing the firmware. Pity that we can't do it by ourselves, as Realme Flash tool doesn't work and MsmDownloadTool requires login credentials of authorized service..
lapist said:
So in the end I sent the phone to Realme service for warranty repair and they fixed it by reflashing the firmware. Pity that we can't do it by ourselves, as Realme Flash tool doesn't work and MsmDownloadTool requires login credentials of authorized service..
Click to expand...
Click to collapse
Where are u from bro
i bought the phone too and i had the same problem.
I couldn't flash the firmware in bootmode or recovery because it didn't display the install from storage item.
I sent the phone for assistance and when I returned everything worked fine: finger print and install from storage in recovery mode.
The firmware installed in assistance is RMX2170EU_11_OTA_0380_all_ePoA62jksSTW.ozip (check the download if it is suitable for your region)