How to Unlock Bootloader if Device Have no emeiMy device Honor 5x KIW-L24 Bootloader is Locked I am unable to unlock Bootloader official and unofficial because i restored
(wrong backup) KIW-L22 TWRP backup on KIW-24 after restore backup my bootloader is locked and emei and serial also formatted.
now my device become KIW-L22 with locked bootloader,no emei . anyone please help me to unlock bootloader without emei
or fix emei or root without unlock bootloader or restore orignal firmware on KIW-24.
OMG . we have almost same issue with different member !
@gopinaidu77 . see if u can do something with the OEM. img
anilsrj said:
How to Unlock Bootloader if Device Have no emei
My device Honor 5x KIW-L24 Bootloader is Locked I am unable to unlock Bootloader official and unofficial because i restored
(wrong backup) KIW-L22 TWRP backup on KIW-24 after restore backup my bootloader is locked and emei and serial also formatted.
now my device become KIW-L22 with locked bootloader,no emei . anyone please help me to unlock bootloader without emei
or fix emei or root without unlock bootloader or restore orignal firmware on KIW-24.
Click to expand...
Click to collapse
There is a trick, log into your Google account you were using on your phone, go into settings and dashboard and Android, you can find all your devices listed there with IMEI numbers. For device id there is a tool mentioned in
http://forum.xda-developers.com/honor-6/general/bricked-honor-6-honor-7-phone-id-t3468334/page2
Tested with honor 6, 7 and 4x as working. Give it a try.
For the serial, connect your phone to PC in fastboot mode and fire
Fastboot devices
The number shown there is your serial (at least that is the case for my honor 7).
Hope it all helps or even a part of it.
(Might wanna google "how to get to Google dashboard" first, I am not 100% sure how to get there).
here is the dashboard link
https://myaccount.google.com/dashboard
as said by @muradulislam follow the procedure, you might have a chance.. or consider your phone cannot be used with any sim cards..
muradulislam said:
There is a trick, log into your Google account you were using on your phone, go into settings and dashboard and Android, you can find all your devices listed there with IMEI numbers. For device id there is a tool mentioned in
http://forum.xda-developers.com/honor-6/general/bricked-honor-6-honor-7-phone-id-t3468334/page2
Tested with honor 6, 7 and 4x as working. Give it a try.
For the serial, connect your phone to PC in fastboot mode and fire
Fastboot devices
The number shown there is your serial (at least that is the case for my honor 7).
Hope it all helps or even a part of it.
(Might wanna google "how to get to Google dashboard" first, I am not 100% sure how to get there).
Click to expand...
Click to collapse
Thanks for reply, I have a mobile box thats contains serial number and emei but you don't read my thread carefully.
my emei is lost after i restore twrp backup KIW-L22 ON KIW-L24. my bootloader is also locked. my issue is now device model is KIW-L24 and firmware is KIW-L22 after this my serial number and product id change with no emei.
anilsrj said:
Thanks for reply, I have a mobile box thats contains serial number and emei but you don't read my thread carefully.
my emei is lost after i restore twrp backup KIW-L22 ON KIW-L24. my bootloader is also locked. my issue is now device model is KIW-L24 and firmware is KIW-L22 after this my serial number and product id change with no emei.
Click to expand...
Click to collapse
That was insensitive of me. I was a bit of annoyance instead of helping. My apologies. Why don't you contact Huawei customer service representative by mail or chat to get unlock code.
anilsrj said:
Thanks for reply, I have a mobile box thats contains serial number and emei but you don't read my thread carefully.
my emei is lost after i restore twrp backup KIW-L22 ON KIW-L24. my bootloader is also locked. my issue is now device model is KIW-L24 and firmware is KIW-L22 after this my serial number and product id change with no emei.
Click to expand...
Click to collapse
you were the same guy, then.. trying from that day??
anilsrj said:
How to Unlock Bootloader if Device Have no emei
My device Honor 5x KIW-L24 Bootloader is Locked I am unable to unlock Bootloader official and unofficial because i restored
(wrong backup) KIW-L22 TWRP backup on KIW-24 after restore backup my bootloader is locked and emei and serial also formatted.
now my device become KIW-L22 with locked bootloader,no emei . anyone please help me to unlock bootloader without emei
or fix emei or root without unlock bootloader or restore orignal firmware on KIW-24.
Click to expand...
Click to collapse
Flash full stock ROM first for safety purposes.
gopinaidu77 said:
Flash full stock ROM first for safety purposes.
Click to expand...
Click to collapse
When i am trying to flash stock rom on my KIW-L24 it's giving error and failed but KIW-L22 stock rom flashed sucessfully,but it is wrong because my device is KIW-L24 and software is flashed on L22.
this is wrong done by me i restore L22 oem info on L24 and stock recovery installing only L22 firmware.
anilsrj said:
When i am trying to flash stock rom on my KIW-L24 it's giving error and failed but KIW-L22 stock rom flashed sucessfully,but it is wrong because my device is KIW-L24 and software is flashed on L22.
this is wrong done by me i restore L22 oem info on L24 and stock recovery installing only L22 firmware.
Click to expand...
Click to collapse
your problem is the biggest i ever found bro, maybe there is no sollution..
anilsrj said:
When i am trying to flash stock rom on my KIW-L24 it's giving error and failed but KIW-L22 stock rom flashed sucessfully,but it is wrong because my device is KIW-L24 and software is flashed on L22.
this is wrong done by me i restore L22 oem info on L24 and stock recovery installing only L22 firmware.
Click to expand...
Click to collapse
Flash system, boot, and recovery of L22. After that, flash the other partitions.
gopinaidu77 said:
Flash system, boot, and recovery of L22. After that, flash the other partitions.
Click to expand...
Click to collapse
My bootloader is locked so i am unable to flash any .img files in fastboot mode.
anilsrj said:
My bootloader is locked so i am unable to flash any .img files in fastboot mode.
Click to expand...
Click to collapse
Oh man. That's really hard.
gopinaidu77 said:
Oh man. That's really hard.
Click to expand...
Click to collapse
If it is easy i sloved by myself, you give me a idea to unlock bootloader or root system.
Device is working fine without network signal with wrong model number, wrong product id, wrong serial number with no emei.
Oh too familiar
Same problem happened to me, accidentally flashed over the EFS file losing my serial number and IMEI's. Then before noticing the lost info I restored the stock OS and recovery, and the bootloader locked behind me, so there's no way for me to actually access that even though I have all the physical numbers from the box. It still does accept the SIM card that was into it prior to the lock and works perfectly fine as a phone, able to send/receive texts and calls as well as use my data, it's just no fun anymore. So I reached out to US customer support, already knowing the answer would be that since the bootloader was unlocked and flashed it was no longer under warranty and they were unable to help, so I have come to the conclusion that there is not much I can do and picked up a new Honor 5x. I've attempted to put in the correct information for my old Honor in the bootloader unlock process, however I believe the product ID generated from my phone is no longer valid as my IMEI's are 0 and my serial number is 0123456789ABCDEF. I will post if I find anything else that might possibly work and would appreciate the same if you by chance happen to come across something that works. Thanks.
andryazt said:
Same problem happened to me, accidentally flashed over the EFS file losing my serial number and IMEI's. Then before noticing the lost info I restored the stock OS and recovery, and the bootloader locked behind me, so there's no way for me to actually access that even though I have all the physical numbers from the box. It still does accept the SIM card that was into it prior to the lock and works perfectly fine as a phone, able to send/receive texts and calls as well as use my data, it's just no fun anymore. So I reached out to US customer support, already knowing the answer would be that since the bootloader was unlocked and flashed it was no longer under warranty and they were unable to help, so I have come to the conclusion that there is not much I can do and picked up a new Honor 5x. I've attempted to put in the correct information for my old Honor in the bootloader unlock process, however I believe the product ID generated from my phone is no longer valid as my IMEI's are 0 and my serial number is 0123456789ABCDEF. I will post if I find anything else that might possibly work and would appreciate the same if you by chance happen to come across something that works. Thanks.
Click to expand...
Click to collapse
I solved eveything Bro, i used dc-unlocker and hcu client service and my all issue is solved so please you checked.
andryazt said:
Same problem happened to me, accidentally flashed over the EFS file losing my serial number and IMEI's. Then before noticing the lost info I restored the stock OS and recovery, and the bootloader locked behind me, so there's no way for me to actually access that even though I have all the physical numbers from the box. It still does accept the SIM card that was into it prior to the lock and works perfectly fine as a phone, able to send/receive texts and calls as well as use my data, it's just no fun anymore. So I reached out to US customer support, already knowing the answer would be that since the bootloader was unlocked and flashed it was no longer under warranty and they were unable to help, so I have come to the conclusion that there is not much I can do and picked up a new Honor 5x. I've attempted to put in the correct information for my old Honor in the bootloader unlock process, however I believe the product ID generated from my phone is no longer valid as my IMEI's are 0 and my serial number is 0123456789ABCDEF. I will post if I find anything else that might possibly work and would appreciate the same if you by chance happen to come across something that works. Thanks.
Click to expand...
Click to collapse
Refer to what OP did. He fixed it.
anilsrj said:
I solved eveything Bro, i used dc-unlocker and hcu client service and my all issue is solved so please you checked.
Click to expand...
Click to collapse
You should put up a thread in the guide section and post the exact steps for solving your problem, many will be glad to see it.
andryazt said:
Same problem happened to me, accidentally flashed over the EFS file losing my serial number and IMEI's. Then before noticing the lost info I restored the stock OS and recovery, and the bootloader locked behind me, so there's no way for me to actually access that even though I have all the physical numbers from the box. It still does accept the SIM card that was into it prior to the lock and works perfectly fine as a phone, able to send/receive texts and calls as well as use my data, it's just no fun anymore. So I reached out to US customer support, already knowing the answer would be that since the bootloader was unlocked and flashed it was no longer under warranty and they were unable to help, so I have come to the conclusion that there is not much I can do and picked up a new Honor 5x. I've attempted to put in the correct information for my old Honor in the bootloader unlock process, however I believe the product ID generated from my phone is no longer valid as my IMEI's are 0 and my serial number is 0123456789ABCDEF. I will post if I find anything else that might possibly work and would appreciate the same if you by chance happen to come across something that works. Thanks.
Click to expand...
Click to collapse
You easly repair your serial number and emei . first you have to buy DC-unlocker 4 credits ( 1 credit=1 euro)
then go to http://hcu-client.com/ and download http://hcu-client.com/HCU_0099.zip
http://hcu-client.com/huawei-phone-imei-repair-tutorial/
Related
Hi there.
I wanted to unlock my bootloader, root and flash a custom rom. So I first flashed the global fastboot rom 7.2.5, later flashed the s-twrp recovery and flashed the lineageOs 7.1. I realised that my sim cards weren't working so therefore switched to resurrection remix. Even then, I couldn't get the network even though wifi was working. So I flashed the global fastboot rom again. I still couldn't get the network. Then I realised that my IMEI number might've been erased while flashing even though I followed every step correctly. I dialed *#*#4636#*#* and found out that my IMEI numbers were now unknown. I got to know that my IMEI numbers were definitely wiped. I tried flashing recoveries, boot images, modem files, etc and now I can't even use WiFi. I tried using the WriteDualIMEI application but unfortunately it isn't finding the COM10/20/9/11 port. I have no clue what to do as of now. Can somebody help me with necessary links and details?
Thanks in advance.
Had this problem yesterday. You may refer to my thread on MIUI forum and see if it can help you. Assuming you have Kenzo variant like I do, refer to this and this first to recover IMEI number as well as EFS, then read the rest of my thread to get signal once you recover the IMEI.
slaveration said:
Had this problem yesterday. You may refer to my thread on MIUI forum and see if it can help you. Assuming you have Kenzo variant like I do, refer to this and this first to recover IMEI number as well as EFS, then read the rest of my thread to get signal once you recover the IMEI.
Click to expand...
Click to collapse
Hey there! Thanks for the quick response! It really means a lot.
The EFS thing makes sense now since all my details such as MAC Address, Baseband, IMEI number, etc are all unavailable or unknown. I tried flashing the modem files but are still unknown. Any tips?
keshavkd said:
Hey there! Thanks for the quick response! It really means a lot.
The EFS thing makes sense now since all my details such as MAC Address, Baseband, IMEI number, etc are all unavailable or unknown. I tried flashing the modem files but are still unknown. Any tips?
Click to expand...
Click to collapse
Did you try this guide to restore baseband/IMEI/MAC etc first? You may also use this QCN in case the XQCN in the guide didn't work. Follow carefully the guide. Then after you get everything, you may change the IMEI using tool found here . After that, follow my thread to flash everything possible to get all the connection back.
slaveration said:
Did you try this guide to restore baseband/IMEI/MAC etc first? You may also use this QCN in case the XQCN in the guide didn't work. Follow carefully the guide. Then after you get everything, you may change the IMEI using tool found here . After that, follow my thread to flash everything possible to get all the connection back.
Click to expand...
Click to collapse
That QCN file was vital! Thank you so much! Now all there's left to do is fix the signal! I've successfully got my IMEI numbers back and the baseband!
keshavkd said:
That QCN file was vital! Thank you so much! Now all there's left to do is fix the signal! I've successfully got my IMEI numbers back and the baseband!
Click to expand...
Click to collapse
Yes that's great! Follow my thread and flash some needed files. Next time please make a full nandroid backup before doing anything okay
Kindly i need a help for this, i have a KII-L21 phone model, i flashed a custom rom then wanted to go back to the stock rom, i followed a guide here that mentioned to restore from TWRP, i did so but the simm didn't want to work and i wasn't able to flash TWRP again or unlock the bootloader as the serial no. of the phone changed so it didn't match with the IMEI also the update from the settings didn't install, can some one help please to solve that issue
No one here to reply!!!! where are the huawei developers or experts kindly help
hazemnada said:
Kindly i need a help for this, i have a KII-L21 phone model, i flashed a custom rom then wanted to go back to the stock rom, i followed a guide here that mentioned to restore from TWRP, i did so but the simm didn't want to work and i wasn't able to flash TWRP again or unlock the bootloader as the serial no. of the phone changed so it didn't match with the IMEI also the update from the settings didn't install, can some one help please to solve that issue
Click to expand...
Click to collapse
R u on stock recovery...
Yes i'm on stock recover.
Let me tell u exactly what happened i restored a backup that was here for my phone and i checked that the backup is for my region, when i restored it asked me for the puk code i entered it but it didn't want to accept, then i checked again the version from about the phone it was correct and it informed me from the updater that there is an update i downloaded but it told me installation failed i then tried to factory reset from both the phone and the recover it did but also everything was the same, so i tried to flash TWRP denied even tried the dload method installation failed also, at the i discovered that the bootloader is locked so i had the lock key and it told me incorect then i discovered that when connecting with ADB it gives a serial number different than mine although when i check through the phone the serial number is my old one. Now i'm stuck and don't know what to do
why no one here replies where r the experts here
hazemnada said:
Yes i'm on stock recover.
Let me tell u exactly what happened i restored a backup that was here for my phone and i checked that the backup is for my region, when i restored it asked me for the puk code i entered it but it didn't want to accept, then i checked again the version from about the phone it was correct and it informed me from the updater that there is an update i downloaded but it told me installation failed i then tried to factory reset from both the phone and the recover it did but also everything was the same, so i tried to flash TWRP denied even tried the dload method installation failed also, at the i discovered that the bootloader is locked so i had the lock key and it told me incorect then i discovered that when connecting with ADB it gives a serial number different than mine although when i check through the phone the serial number is my old one. Now i'm stuck and don't know what to do
Click to expand...
Click to collapse
Which firmware number you tried via dload??
hassanjavaid8181 said:
Which firmware number you tried via dload??
Click to expand...
Click to collapse
first i restored the backup in the Repository that mentioned my phone model
GR5 KII-L21
GR5+TWRP+backup_KII-L21C185B130.rar Thanks to Under World
and it changed everything then
'Morning all,
I would really appreciate some advice on a couple of things about my MATE 10 Standard.
I bought this phone online from an online shop in Manchester around April last year. I got the Mate 10 ALP-AL00 which was rebranded by the shop to ALP-L29. Its currently on 8.0.0.136(C636).
My aim is to unlock and root my device with Magisk and of course get TWRP working as well. From what I have read, there seems to be quite a high level of success but there are still things i'm not sure about. Huawei phones are a bit fragile, software wise and can easily brick. Plus, the fact that the phone itself is the Chinese variant, I don't expect any kind of help from Huawei Customer services if it does get bricked. Hence i'm being very cautious. (Past bad experience with a Honor 9 STF-AL10).
1. my phone is on ALP-L29 8.0.0.136(c636) 1 June security patch. Bootloader Version: Chipset-boston8.0.0.001(02M8)_FASTBOOT
I've refused all attempts to upgrade via OTA as I've read about the 01 and 02 bootloaders fiasco.
2. I've got an unlock code from DC-Unlocker, but I've not tried it yet. I never was able to get a code from Huawei's official site due to the fact that it was rebranded, which lead me to believe the online shop I bought it from used Funky to rebrand. (Apparently, FunkyH messes up something on the bootloader thus preventing unlocking with official unlockcode. AFIK). BUT, the info displayed by phone is exactly the same as what is on the box, imei 1&2, S/N, device Id code, etc...
Basically my questions are:
With the current firmware version I'm on, can I unlock my bootloader, install the unofficial TWRP then root with Magisk? AFIK its on xloader 01.
Is there anything to look out for when doing the above?
and, If I do a full backup immediately after installing TWRP, can this be used to recover the phone if it fails to boot up for any reason.?
I'm not really interested in being on the latest EMUI version etc, just wan't a phone with full root and an easy method to unbrick it.
thank you all,
ums1405 said:
'Morning all,
I would really appreciate some advice on a couple of things about my MATE 10 Standard.
I bought this phone online from an online shop in Manchester around April last year. I got the Mate 10 ALP-AL00 which was rebranded by the shop to ALP-L29. Its currently on 8.0.0.136(C636).
My aim is to unlock and root my device with Magisk and of course get TWRP working as well. From what I have read, there seems to be quite a high level of success but there are still things i'm not sure about. Huawei phones are a bit fragile, software wise and can easily brick. Plus, the fact that the phone itself is the Chinese variant, I don't expect any kind of help from Huawei Customer services if it does get bricked. Hence i'm being very cautious. (Past bad experience with a Honor 9 STF-AL10).
1. my phone is on ALP-L29 8.0.0.136(c636) 1 June security patch. Bootloader Version: Chipset-boston8.0.0.001(02M8)_FASTBOOT
I've refused all attempts to upgrade via OTA as I've read about the 01 and 02 bootloaders fiasco.
2. I've got an unlock code from DC-Unlocker, but I've not tried it yet. I never was able to get a code from Huawei's official site due to the fact that it was rebranded, which lead me to believe the online shop I bought it from used Funky to rebrand. (Apparently, FunkyH messes up something on the bootloader thus preventing unlocking with official unlockcode. AFIK). BUT, the info displayed by phone is exactly the same as what is on the box, imei 1&2, S/N, device Id code, etc...
Basically my questions are:
With the current firmware version I'm on, can I unlock my bootloader, install the unofficial TWRP then root with Magisk? AFIK its on xloader 01.
Is there anything to look out for when doing the above?
and, If I do a full backup immediately after installing TWRP, can this be used to recover the phone if it fails to boot up for any reason.?
I'm not really interested in being on the latest EMUI version etc, just wan't a phone with full root and an easy method to unbrick it.
thank you all,
Click to expand...
Click to collapse
You could just test the code in fastboot: fastboot oem unlock UNLOCKCODE
If the code is incorrect, for some reason, it will say Password incorrect. Else it will bring you to the yes/no unlock screen on phone. DCs unlock code should always work as it doesn't need the correct imei/imei2/sn/product combo when generating unlock code.
There's no real point in staying on xloader 01 anymore, every update (except a few unapproved firmware) after 02 started appearing has been 02.
Downside is that you can't downgrade, but you could replace fastboot in latest fw with the one from may/June and you'd have DC working again. But there's also service firmware available for free on androidhost.ru which can be used if phone should brick. There's also testpoint (only one person has tested this) which can be used to downgrade to any firmware (even xloader 02 to 01).
Before unlocking, backup everything as unlocking will wipe data.
ums1405 said:
'Morning all,
I would really appreciate some advice on a couple of things about my MATE 10 Standard.
I bought this phone online from an online shop in Manchester around April last year. I got the Mate 10 ALP-AL00 which was rebranded by the shop to ALP-L29. Its currently on 8.0.0.136(C636).
My aim is to unlock and root my device with Magisk and of course get TWRP working as well. From what I have read, there seems to be quite a high level of success but there are still things i'm not sure about. Huawei phones are a bit fragile, software wise and can easily brick. Plus, the fact that the phone itself is the Chinese variant, I don't expect any kind of help from Huawei Customer services if it does get bricked. Hence i'm being very cautious. (Past bad experience with a Honor 9 STF-AL10).
1. my phone is on ALP-L29 8.0.0.136(c636) 1 June security patch. Bootloader Version: Chipset-boston8.0.0.001(02M8)_FASTBOOT
I've refused all attempts to upgrade via OTA as I've read about the 01 and 02 bootloaders fiasco.
2. I've got an unlock code from DC-Unlocker, but I've not tried it yet. I never was able to get a code from Huawei's official site due to the fact that it was rebranded, which lead me to believe the online shop I bought it from used Funky to rebrand. (Apparently, FunkyH messes up something on the bootloader thus preventing unlocking with official unlockcode. AFIK). BUT, the info displayed by phone is exactly the same as what is on the box, imei 1&2, S/N, device Id code, etc...
Basically my questions are:
With the current firmware version I'm on, can I unlock my bootloader, install the unofficial TWRP then root with Magisk? AFIK its on xloader 01.
Is there anything to look out for when doing the above?
and, If I do a full backup immediately after installing TWRP, can this be used to recover the phone if it fails to boot up for any reason.?
I'm not really interested in being on the latest EMUI version etc, just wan't a phone with full root and an easy method to unbrick it.
thank you all,
Click to expand...
Click to collapse
U can check unlock code by dialing *#*#2846579#*#* and goto veneer informations>Verify key> Input boot unlock code. If it is correct it will show Success in toast notification.
Hi all,
Appologies for late reply as I've been lumbered with bored kids on their midterms plus a backlog of work.
I've verified the key I go from DC, and success it got verified OK.
Now to prepare and read through again all the important bits for TWRP nstallatuon and magisk.
Quick question, is there a way or method that is 100% foolproof to recover your device via unofficial TWRP.
Noobish questions, I know but please bear with me.
Thanks for your time and patience and best regards....
ums1405 said:
Hi all,
Appologies for late reply as I've been lumbered with bored kids on their midterms plus a backlog of work.
I've verified the key I go from DC, and success it got verified OK.
Now to prepare and read through again all the important bits for TWRP nstallatuon and magisk.
Quick question, is there a way or method that is 100% foolproof to recover your device via unofficial TWRP.
Noobish questions, I know but please bear with me.
Thanks for your time and patience and best regards....
Click to expand...
Click to collapse
There are a few methods to recover your device from an eventual soft-brick, i wouldn't call them foolproof, not because are hard to follow/use, but only because it seem that no matter how easy a guid, a method or a tool is, there are still some people that fail to do it properly.
If your only goal is to install TWRP and Magisk, my advice is to read a bit on these forums and you shoul be fine.
Another advice, that people seem to ignore completely after they acquire root, is to backup your partitions. I recommend Partitions Backup (by Wanam) from Playstore. Backup all partitions beside system, vendor and userdata then transfer the backup on PC, Cloud, etc.
Good luck!
debbuger said:
U can check unlock code by dialing *#*#2846579#*#* and goto veneer informations>Verify key> Input boot unlock code. If it is correct it will show Success in toast notification.
Click to expand...
Click to collapse
Thanks, that's worth the entrance fee alone as they say.
Pretoriano80 said:
There are a few methods to recover your device from an eventual soft-brick, i wouldn't call them foolproof, not because are hard to follow/use, but only because it seem that no matter how easy a guid, a method or a tool is, there are still some people that fail to do it properly.
If your only goal is to install TWRP and Magisk, my advice is to read a bit on these forums and you shoul be fine.
Another advice, that people seem to ignore completely after they acquire root, is to backup your partitions. I recommend Partitions Backup (by Wanam) from Playstore. Backup all partitions beside system, vendor and userdata then transfer the backup on PC, Cloud, etc.
Good luck!
Click to expand...
Click to collapse
Thank you for taking the time to put me right.
I'll go back to your Unofficial TWRP post and go through it A to Z.
Hi all,
thanks for the all the help with my issues.
I've unlocked the bootloader and even got the unofficial TWRP working.
I've also backup my partitions and kept them on my PC and Cloud.
Now the problem I'm having is with Magisk. I can't seem to get it installed.
When I flashed it in TWRP I got an error that /system and /Vendor are not mounted. Mounted them manually and retried the instalation and it worked. When I check the APP, it shows as not installed.
I've tried magisk 16.0 and 17.1 both failed to install. Tried the one in the HWOTA zip and it failed too.
Anyone please advise...
ums1405 said:
Hi all,
thanks for the all the help with my issues.
I've unlocked the bootloader and even got the unofficial TWRP working.
I've also backup my partitions and kept them on my PC and Cloud.
Now the problem I'm having is with Magisk. I can't seem to get it installed.
When I flashed it in TWRP I got an error that /system and /Vendor are not mounted. Mounted them manually and retried the instalation and it worked. When I check the APP, it shows as not installed.
I've tried magisk 16.0 and 17.1 both failed to install. Tried the one in the HWOTA zip and it failed too.
Anyone please advise...
Click to expand...
Click to collapse
Which device and build do you have? First uninstall Magisk with Magisk Uninstaller, by flashing it with TWRP. Then try again to install latest Magisk.
And btw, your partitions backup is not completely done, not untill you install Magisk and use that app, Partitions Backup!
Solved!
I ran the magisk_uninstall twice then ran the magisk.bat again.
Got 16.0 to work, now updated to 17.1 via the app and all is good.
worked like a CHARM.
full root & TWRP + Magisk 17.1 installed
Christmas has come early for me!
Now to way the pros and cons of updating to xloader2 (infact anything above B136)
Much respect to all and best regards.....
:good:
ums1405 said:
Solved!
I ran the magisk_uninstall twice then ran the magisk.bat again.
Got 16.0 to work, now updated to 17.1 via the app and all is good.
worked like a CHARM.
full root & TWRP + Magisk 17.1 installed
Christmas has come early for me!
Now to way the pros and cons of updating to xloader2 (infact anything above B136)
Much respect to all and best regards.....
:good:
Click to expand...
Click to collapse
Well, you can't stay on xloader01 forever, at least not if you want to update your device.
The cons is that once on xloader02, you can't go back to xloader01.
Pretoriano80 said:
Which device and build do you have? First uninstall Magisk with Magisk Uninstaller, by flashing it with TWRP. Then try again to install latest Magisk.
And btw, your partitions backup is not completely done, not untill you install Magisk and use that app, Partitions Backup!
Click to expand...
Click to collapse
All sorted now boss......I'm about to do the backups now.
I'm presented with heaps of partions, anyone in particular or just back the whole lot?
ums1405 said:
All sorted now boss......I'm about to do the backups now.
I'm presented with heaps of partions, anyone in particular or just back the whole lot?
Click to expand...
Click to collapse
All except userdata, system and vendor (these are large and can be found on stock firmwares, so can be skipped).
all done.
just restoring apps and data now.
if I was going to update to x2loader FW how would i do that?
Thanks again pal.
ums1405 said:
all done.
just restoring apps and data now.
if I was going to update to x2loader FW how would i do that?
Thanks again pal.
Click to expand...
Click to collapse
You can use HWOTA8 or HuRUpdater! Beware that if you update to a firmware with patch 01, simply flashing Magisk won't work anymore and you will have to patch the stock ramdisk with Magisk Manage (keep encryption and preserve dm_verity must be enabled) , then flash the patched image with fastboot.
Hi guys!
Can someone with Mate 10 ALP-L29 model to make a backup his phone's NVME and modem partition? I need this because l was hardbricked and l messed up with my NVME partition(lost). Thank you!
Please run this command with an external sd, and send me the resulting file:
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/external_sd/backup/nvme.img
####If you don't have external sd...
Please try something like:
(from computer with debugging turned on)
adb shell
su
(approve root request on phone)
mkdir /sdcard/backup
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/sdcard/backup/nvme.img
@and for modem:
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_backup of=/sdcard/backup/modemnvm_backup.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_img of=/sdcard/backup/modemnvm_img.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_system of=/sdcard/backup/modemnvm_system.img
OR,
Always with ROOT on mate 10 you can backup partition with Google Play market app : Partitions Backup & Restore 2.0.1 APK.
I need a all files NV:
Modemnvn_bakup
Modemnvm_factory
Modemnvm_system, etc.
I promise not to use your information or to make it public, and the file will be used only for my phone to make it work again
NVME
manager77 said:
Hi guys!
Can someone with Mate 10 ALP-L29 model to make a backup his phone's NVME and modem partition? I need this because l was hardbricked and l messed up with my NVME partition(lost). Thank you!
Please run this command with an external sd, and send me the resulting file:
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/external_sd/backup/nvme.img
####If you don't have external sd...
Please try something like:
(from computer with debugging turned on)
adb shell
su
(approve root request on phone)
mkdir /sdcard/backup
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/sdcard/backup/nvme.img
@and for modem:
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_backup of=/sdcard/backup/modemnvm_backup.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_img of=/sdcard/backup/modemnvm_img.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_system of=/sdcard/backup/modemnvm_system.img
OR,
Always with ROOT on mate 10 you can backup partition with Google Play market app : Partitions Backup & Restore 2.0.1 APK.
I need a all files NV:
Modemnvn_bakup
Modemnvm_factory
Modemnvm_system, etc.
I promise not to use your information or to make it public, and the file will be used only for my phone to make it work again
Click to expand...
Click to collapse
So in other words you need all the information that would be required to clone someones phone. I doubt that a "promise" would be sufficient. Just using their backups would basically be cloning their device and using their information.
revjamescarver said:
So in other words you need all the information that would be required to clone someones phone. I doubt that a "promise" would be sufficient. Just using their backups would basically be cloning their device and using their information.
Click to expand...
Click to collapse
At first sight seems to be something like that... but is not my intention to have a functional phone which is a clone. If my phone will work again with NV partition from other same model l will continue to find a way to restore back my phone.... I am not a pirate lol ????
manager77 said:
At first sight seems to be something like that... but is not my intention to have a functional phone which is a clone. If my phone will work again with NV partition from other same model l will continue to find a way to restore back my phone.... I am not a pirate lol ????
Click to expand...
Click to collapse
You would have to rewrite it using HCU, but that only works on firmware prior to June 2018. I have done this when I too messed with my NVME. NVME on Mate 10+ is encrypted and can't be edited without decrypting it first (I guess)
I have a mate 10 Pro and I don't think my NVME would be great for your phone
ante0 said:
You would have to rewrite it using HCU, but that only works on firmware prior to June 2018. I have done this when I too messed with my NVME. NVME on Mate 10+ is encrypted and can't be edited without decrypting it first (I guess)
I have a mate 10 Pro and I don't think my NVME would be great for your phone
Click to expand...
Click to collapse
HCU client works only with xloader01 firmwares. I am on xloader02 and for now nothing seems to be working. I tried today with sigma key too... but it doesn't work either. Chinese firmwares are all xloader01, Evan Android 8.1. (f''king chinese???)
About NV partition l think mate 10 and mate 10 pro should have the same one. I not sure it will work but l can give it a try if you help me( nothing to lose)
In fastboot mode after fastboot oem get-psid command.... it shows me in cmd my 2 imeis and serial number. But in normal mode l have 0000000 imei and with no services... and NCK prompt with sim!
manager77 said:
HCU client works only with xloader01 firmwares. I am on xloader02 and for now nothing seems to be working. I tried today with sigma key too... but it doesn't work either. Chinese firmwares are all xloader01, Evan Android 8.1. (f''king chinese???)
About NV partition l think mate 10 and mate 10 pro should have the same one. I not sure it will work but l can give it a try if you help me( nothing to lose)
In fastboot mode after fastboot oem get-psid command.... it shows me in cmd my 2 imeis and serial number. But in normal mode l have 0000000 imei and with no services... and NCK prompt with sim!
Click to expand...
Click to collapse
Yep, I know that. But it didn't work on, for example, C432B145 either which was Xloader 01. So it was patched before the new bootloader was introduced
It may have the same NVME/modems. I flashed NV partitions from a BLA-L09 and mine is a L29. After this it turned into L09, and gained the IMEI/IMEI2 and serial of the donor phone. This was easily fixable in HCU though... But it's up to you. If you were up to no good it should only block the imei/imei2 on the network you use the phone on. And besides, I will probably switch to another brand soon. It seems Huawei patched something else now in latest Pie for C432 so you can't boot with a custom kernel (Built directly from their source without modifications, tried both COL and BKL source). It was fine on the build prior to this new one. I like disabling most of their kernel logging and **** which they seem to need for some reason. Can't disable all as kernel won't build then and I'm not in the mood of trying to completely remove it
Going to test signing it if avb is causing problems, it hasn't before but you never know with Huawei...
In fastboot it shows the info that's in OEMINFO. In booted mode it loads the info from modem.
But I will send you a pm in a bit.
NV partitions
manager77 said:
At first sight seems to be something like that... but is not my intention to have a functional phone which is a clone. If my phone will work again with NV partition from other same model l will continue to find a way to restore back my phone.... I am not a pirate lol
Click to expand...
Click to collapse
The NV partitions contain the IMEI, ESN, and serial numbers along with other information, using those partitions to bring your phone back from the dead is cloning the phone, weather that is your intent or not. The only way to do it without "cloning" is to edit the information in the "donated" partition so that the information would be the same as the the information in your original partitions. You have to change the IMEI, ESN, serial number, and modem id numbers.
revjamescarver said:
The NV partitions contain the IMEI, ESN, and serial numbers along with other information, using those partitions to bring your phone back from the dead is cloning the phone, weather that is your intent or not. The only way to do it without "cloning" is to edit the information in the "donated" partition so that the information would be the same as the the information in your original partitions. You have to change the IMEI, ESN, serial number, and modem id numbers.
Click to expand...
Click to collapse
"edit the information in the "donated" partition "..... where is that?
manager77 said:
"edit the information in the "donated" partition "..... where is that?
Click to expand...
Click to collapse
It's encrypted. Or should be at least. Not sure if serial is
NV backup
https://cloud.mail.ru/public/Gv2o/aVrY2P5rz
geogsm_1 said:
NV backup
https://cloud.mail.ru/public/Gv2o/aVrY2P5rz
Click to expand...
Click to collapse
Thanks! I restored with Partition Backup and Restore all 3 partition that you upload here. But nothing is change for me... I mean l am in the same situation. I guess l need all modem partitions like in this pic:
manager77 said:
Thanks! I restored with Partition Backup and Restore all 3 partition that you upload here. But nothing is change for me... I mean l am in the same situation. I guess l need all modem partitions like in this pic:
Click to expand...
Click to collapse
I was just checking my logs and I had to flash modemnvm_backup, modemnvm_cust, modemnvm_fw, modemnvm_img from BLA-L09 when fixing my device. But, after flashing those I would get No service. SIM was recognized. I had to restore my imeis/serial using HCU. After this it would switch between No service and my network rapidly. After this I did a factory reset in stock recovery and that solved it.
I'm not sure it was due to it being L09 modem and my device was L29 or something else, but HCU seems to be key to getting it back. I guess you could try downgrading partitions manually to pre-june firmware, all but xloader and fastboot. Downgrading xloader would only cause a brick and fastboot might too.
I guess you would also have to have a phone that boots to system, which I'm not sure yours does.
I could only use fastboot when this happened to me.
ante0 said:
I was just checking my logs and I had to flash modemnvm_backup, modemnvm_cust, modemnvm_fw, modemnvm_img from BLA-L09 when fixing my device. But, after flashing those I would get No service. SIM was recognized. I had to restore my imeis/serial using HCU. After this it would switch between No service and my network rapidly. After this I did a factory reset in stock recovery and that solved it.
I'm not sure it was due to it being L09 modem and my device was L29 or something else, but HCU seems to be key to getting it back. I guess you could try downgrading partitions manually to pre-june firmware, all but xloader and fastboot. Downgrading xloader would only cause a brick and fastboot might too.
I guess you would also have to have a phone that boots to system, which I'm not sure yours does.
I could only use fastboot when this happened to me.
Click to expand...
Click to collapse
My phone works in all modes: normal, fastboot, erecovery, recovery. Only problem is 0000000 imei and no services
flash via fastboot then factory reset, it work for me.
code : fastboot flash modemnvm_system modemnvm_system.img
So I managed to downgrade to successfully unlock my bootloader however I am now stuck on 8.0.0.046(092Y) and am unable to OTA update. I have installed magisk and TWRP and they are both currently working however I am curious as to why I cannot update to a newer 8.0 OTA firmware. Any suggestions? The device is an ANE-LX3 single sim.
Because you used wrong firmware.
(092y) or similar numbers are here because wrong firmware..
At least that was case for me, when I installed single SIM firmware over dual SIM phone, and of course, that build number not exist in update servers, so no updates here, till you fix your firmware
Arnys said:
Because you used wrong firmware.
(092y) or similar numbers are here because wrong firmware..
At least that was case for me, when I installed single SIM firmware over dual SIM phone, and of course, that build number not exist in update servers, so no updates here, till you fix your firmware
Click to expand...
Click to collapse
This is what I feared, thanks for confirming. I am hoping flashing this will solve my issues. Any advice before doing so?
metalfangs said:
This is what I feared, thanks for confirming. I am hoping flashing this will solve my issues. Any advice before doing so?
Click to expand...
Click to collapse
HM.. in link you gave here, is writed about ane-lx1, you mentioned your phone are ane-lx3 single sim, so, I'm not sure it can fix your problem..
And I'm not used that files, and can't say anything about that.
And more important, what was full build number for your phone, aka ane-lx3c779, something like that, can you find it? Then I maybe be able to help.
And ,wulda be great if you type down all you did with phone, what used, etc.
Arnys said:
HM.. in link you gave here, is writed about ane-lx1, you mentioned your phone are ane-lx3 single sim, so, I'm not sure it can fix your problem..
And I'm not used that files, and can't say anything about that..
Click to expand...
Click to collapse
I noticed the file name is LX1 however in the description it says its for all models which is confusing. Any idea where I could find an official firmware download for LX3? Even a functional custom rom compatible with my device would be fine if I could find one.
I used hisuite to first downgrade and then used the firmware from this post to dload downgrade again in order to unlock the bootloader. I then factory reset after successfully unlocking the bootloader which left me at build 046.
To be honest I cannot remember what the original build number was although c779 does sound very familiar.
metalfangs said:
I noticed the file name is LX1 however in the description it says its for all models which is confusing. Any idea where I could find an official firmware download for LX3? Even a functional custom rom compatible with my device would be fine if I could find one.
I used hisuite to first downgrade and then used the firmware from this post to dload downgrade again in order to unlock the bootloader. I then factory reset after successfully unlocking the bootloader which left me at build 046.
To be honest I cannot remember what the original build number was although c779 does sound very familiar.
Click to expand...
Click to collapse
Hm, did you tried erecovery method ? Maybe that can fix your problem
metalfangs said:
So I managed to downgrade to successfully unlock my bootloader however I am now stuck on 8.0.0.046(092Y) and am unable to OTA update. I have installed magisk and TWRP and they are both currently working however I am curious as to why I cannot update to a newer 8.0 OTA firmware. Any suggestions? The device is an ANE-LX3 single sim.
Click to expand...
Click to collapse
Hello there brother. May I humbly ask how did you get your bootloader unlocked after downgrading? Can you share some steps please if you don't mind. Thank you