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
Related
Hi,
I used Android 4.1.2 and CM10.1 - on Samsung Galaxy S II model I9100.
During a phone conversation it was hanged up, and the phone could not connect to the network anymore.
I got an error when tried to manually search for network operator, which lead me, after a research in the net, to find out that the IMEI of the phone is empty. I see also that the Baseband version is 'unknown'.
I have a backup of the efs folder and tried to restore it by manual overwrite it - with no success.
I also followed the guide to recover manually the IMEI from here: http://forum.xda-developers.com/showthread.php?t=1264021 with no success.
I tried to get back to a backup of the original ROM I used before (this time using ODIN), and now I get NULL/NULL in the IMEI and I still get Baseband 'unknown'.
Also re-installing the radio did not help. now when looking for network operator the error is different - now it is telling me that there is no SIM card.
the NULl/NULL IMEI and Baseband version is 'unknown' are still here and I still can't connect to the network.
last input: after 2 days of phone being unused - it suddenly got back to work, the original IMEI got back in, and it connected to the network. this happened without me doing anything, and it held for half a day, then the phone got back to the non-functioning mode as described above, again in the middle of a phone conversation.
I am out of new ideas, all related threads in here did not help.
Can anybody help ?
Does anybody know the reason for this issue?
Can tell what is the thing that is probably corrupted, and in case that the problem is with the files in efs folder - why doesn't a restore of the efs folder (including chown for nv_data.bin to user radio) did not help?
Thanks !
-- Amit.
amita74 said:
Hi,
I used Android 4.1.2 and CM10.1 - on Samsung Galaxy S II model I9100.
During a phone conversation it was hanged up, and the phone could not connect to the network anymore.
I got an error when tried to manually search for network operator, which lead me, after a research in the net, to find out that the IMEI of the phone is empty. I see also that the Baseband version is 'unknown'.
I have a backup of the efs folder and tried to restore it by manual overwrite it - with no success.
I also followed the guide to recover manually the IMEI from here: http://forum.xda-developers.com/showthread.php?t=1264021 with no success.
I tried to get back to a backup of the original ROM I used before (this time using ODIN), and now I get NULL/NULL in the IMEI and I still get Baseband 'unknown'.
Also re-installing the radio did not help. now when looking for network operator the error is different - now it is telling me that there is no SIM card.
the NULl/NULL IMEI and Baseband version is 'unknown' are still here and I still can't connect to the network.
last input: after 2 days of phone being unused - it suddenly got back to work, the original IMEI got back in, and it connected to the network. this happened without me doing anything, and it held for half a day, then the phone got back to the non-functioning mode as described above, again in the middle of a phone conversation.
I am out of new ideas, all related threads in here did not help.
Can anybody help ?
Does anybody know the reason for this issue?
Can tell what is the thing that is probably corrupted, and in case that the problem is with the files in efs folder - why doesn't a restore of the efs folder (including chown for nv_data.bin to user radio) did not help?
Thanks !
-- Amit.
Click to expand...
Click to collapse
EFS is corrupt.This was a bomb waiting to explode.I suggest you to go back to stock JB 4.1.2 ROM (see my signature),and flash Apolo kernel.Go to recovery and restore backup.Do not overwrite it manually.Do it in Recovery.
New inputs
GamingDj said:
EFS is corrupt.This was a bomb waiting to explode.I suggest you to go back to stock JB 4.1.2 ROM (see my signature),and flash Apolo kernel.Go to recovery and restore backup.Do not overwrite it manually.Do it in Recovery.
Click to expand...
Click to collapse
Hi GamingDj,
First thanks for the reply.
I want to add more inputs and few questions:
Right now, after more then another day that the phone was not functioning - it got back to operate again, and again, without me doing anything that will cause that to happen.
During the last time that it happened, this held the pone in a working state for about half a day until it hanged up on me during a phone conversation I had - and the phone stopped working again, so I am not very optimistic about the phone getting back to work for good right now....
I have a bit more data that I forgot to mention before:
1. About a day before this problem happened, Avast anti virus offered me to update the Avast Anti theft software, this required root access and I don't know if it has something with the reported problem or not.
2. The efs folder was "handled" by GalaxSim Unlock, after the phone got locked due to official upgrade to JB. Originaly this was an O2 locked phone, then it was unlocked with a code, but due to the upgrade to JB it got SIM locked again and the codes did not work anymore, which caused me to use the GalaxSim Unlock application - that indeed unlocked my phone. I know that the GalaxSim Unlock application changed some data in the nv_data.bin in efs folder, but after it unlocked my phone it was working fine for about a month or more, so I can't tell that this is the cause for the suspected corruption in the efs folder.
I have both backup of the efs folder before and after the unlock operation by GalaxSim unlock application.
Can you explain in more details:
1. Why you suggest to flush Apolo kernel? is it in order to have the phone rooted? can you give a link for this kernel?
2. Restore backup from where? should I have a backup file that you point to? not sure what backups I have that may have data that I don't already use.
3. Does the new data help with debugging this issue?
Thanks again.
-- Amit.
amita74 said:
Hi GamingDj,
First thanks for the reply.
I want to add more inputs and few questions:
Right now, after more then another day that the phone was not functioning - it got back to operate again, and again, without me doing anything that will cause that to happen.
During the last time that it happened, this held the pone in a working state for about half a day until it hanged up on me during a phone conversation I had - and the phone stopped working again, so I am not very optimistic about the phone getting back to work for good right now....
I have a bit more data that I forgot to mention before:
1. About a day before this problem happened, Avast anti virus offered me to update the Avast Anti theft software, this required root access and I don't know if it has something with the reported problem or not.
2. The efs folder was "handled" by GalaxSim Unlock, after the phone got locked due to official upgrade to JB. Originaly this was an O2 locked phone, then it was unlocked with a code, but due to the upgrade to JB it got SIM locked again and the codes did not work anymore, which caused me to use the GalaxSim Unlock application - that indeed unlocked my phone. I know that the GalaxSim Unlock application changed some data in the nv_data.bin in efs folder, but after it unlocked my phone it was working fine for about a month or more, so I can't tell that this is the cause for the suspected corruption in the efs folder.
I have both backup of the efs folder before and after the unlock operation by GalaxSim unlock application.
Can you explain in more details:
1. Why you suggest to flush Apolo kernel? is it in order to have the phone rooted? can you give a link for this kernel?
2. Restore backup from where? should I have a backup file that you point to? not sure what backups I have that may have data that I don't already use.
3. Does the new data help with debugging this issue?
Thanks again.
-- Amit.
Click to expand...
Click to collapse
Follow my guide to flash ICS official.Then root and sim Unlock it(if needed).Then flash Apolo kernel via Recovery.In apolo kernel Recovery go to EFS menu,and click restore.Now restore your backup.
status update
GamingDj said:
Follow my guide to flash ICS official.Then root and sim Unlock it(if needed).Then flash Apolo kernel via Recovery.In apolo kernel Recovery go to EFS menu,and click restore.Now restore your backup.
Click to expand...
Click to collapse
Hi,
Just want to update that its been about a week that the phone works without me doing anything, therefore not proceeding with the recovery process you suggested.
I will update if the problem will be back.
Thanks.
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/
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
Hi!
I have a big problem to return to stock after trying the Elemental v. 1.1.
I have tried the full backup from here: https://forum.xda-developers.com/ma...other-development/oeminfo-collection-t3762385 but it says that it is rooted when I boot it.
I then tried: https://forum.xda-developers.com/ma...evelopment/stock-rom-rne-l21c185b142-t3764065 (I know it is the wrong localization, but I was desperate, sorry ) and this actually booted with no problem, no notice of being rooted BUT now I faced that the unit had been turned into a NEO-L21.
I thought that I could fix that with the first links change of OEM, but it would not work...what am I doing wrong?
And does anyone have a backup without root, or a way to fix it using the newly published Full-OTA that have started to come for our device?
Thanks in beforehand!
davurleon said:
Hi!
I have a big problem to return to stock after trying the Elemental v. 1.1.
I have tried the full backup from here: https://forum.xda-developers.com/ma...other-development/oeminfo-collection-t3762385 but it says that it is rooted when I boot it.
I then tried: https://forum.xda-developers.com/ma...evelopment/stock-rom-rne-l21c185b142-t3764065 (I know it is the wrong localization, but I was desperate, sorry ) and this actually booted with no problem, no notice of being rooted BUT now I faced that the unit had been turned into a NEO-L21.
I thought that I could fix that with the first links change of OEM, but it would not work...what am I doing wrong?
And does anyone have a backup without root, or a way to fix it using the newly published Full-OTA that have started to come for our device?
Thanks in beforehand!
Click to expand...
Click to collapse
to remove the NEO-L21 phone settings.
you should restore the boot backup only.
Backup BOOT RNE-L21C432B133 clean
** https://mega.nz/#F!s4s1WKIQ!kDwYTMP9YmGan1thThXRfA
and restart.
boot
Chisetdel31260 said:
to remove the NEO-L21 phone settings.
you should restore the boot backup only.
Backup BOOT RNE-L21C432B133 clean
** https://mega.nz/#F!s4s1WKIQ!kDwYTMP9YmGan1thThXRfA
and restart.
Click to expand...
Click to collapse
I don't know what goes wrong, but it does not boot with this boot partition. Could it be because the NEO-L21 backup I restored is Android 6.0?
davurleon said:
I don't know what goes wrong, but it does not boot with this boot partition. Could it be because the NEO-L21 backup I restored is Android 6.0?
Click to expand...
Click to collapse
It's not Android 6.0. The info in "About Phone" is just wrong. You are on android 7.0. I would recommend you to do what I have done for myself.
https://forum.xda-developers.com/ma...pilation-firmware-flasheables-huawei-t3761483
Follow the instruction in this topic which is:
(Remember to get the unlock code for bootloader before you flash anything !!)
1.Flash the OEM info from cust432 or whatever cust you want.
2.Unlock the bootloader and flash TWRP
3.Flash the firmware proper for your cust from the above topic and everything should work. I did this for my phone that was cust c738 before and it works like a charm now and I am on cust432. The only thing for me is that I can't do an OTA update to B133. I am on full stock without root, but I have unlocked BL. I tried to relock it to see if it changes anything but then my phone is stuck on bootloop.
So since I'm here can anyone tell me...Do I have to be on locked BL in order to perform an OTA update ?
If yes how do i relock it ? Because if i do "fastboot oem relock code" then my phone is stuck on bootloop....
We can't back to stock rom, since huawei not release online, we can go to customer service thay 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.
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