Help ! Imei and Serial number corrupted G620S-L01 - Honor 4x Questions & Answers

Hello everyone
I don't know if this is the right place to post it but I have a problem with my Huawei G620S-L01
I got it from a friend with Stock Rom 4.4.4. Everything was fine for 2 months until it starts bootlooping. I never tried to root this or something like that... After googling a bit, I found the solution to the bootloop in flashing Stock Rom via Sdcard/dload method. Everything was fine again... Then I noticed that the Lineage 14 (7.1.2) was out and I wanted to get it. But in order to flash it, I had to unlock the bootloader and flash a custom recovery. It wasn't a problem for me since I've already done it with other phones. The problem was to get the bootloader code from Huawei because I noticed that my IMEI changed and my Serial Number changed and shrinked ..... so I used those who are on the battery to obtain a bootloader code from Huawei (because the corrupted ones doesn't exist in the IMEI database even if they seems to be real). I thought that will finally work.... But no, the fastboot command to unlock the bootloader says : FAILED (remote: invalid key, unlock fail)...
So this is where I'm stucked. What should I do ? Did I flash the wrong firmware at the first time even if it seems to work like a charm?How can I get my IMEI and S/N back ? Does flashing another stock firmware will help me? please help me :crying:
I'm still unrooted
Thanks in advance

Please help me ! Anyone... :crying:

It seems that there is no solution...

Related

[Q] all software on my moto x is gone. please help.

so i tried to update to the new sprint update that fixes the 4.4 battery issues. i was on twrp recovery and i flashed back to stock recovery and tried to dirty flash the update on top. i had xposed framework installed so was pretty sure that wasn't going to work. and it didn't. now i decided to use the moto x toolkit to flash back to stock. it booted up just fine then i downloaded the update from 4.2.2 to 4.4 and the update failed. now i'm stuck with basically nothing on my phone at all. i can get to fastboot mode but thats it. cant power up cant enter recovery can't do anything.. also i had a unlocked bootloader and now its reading locked again. here is the error i'm getting.
failed to hab check for gpt_nain: 0x35
failed to hab check for gpt_gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. contact Dealer: 0xdead
No SP partition found
Fastboot Reason: Invalid CID
I've been working on this for about 7 hours and have looked up everything i could think of to try and get this fixed. i may just be missing something.. does anyone know how i could fix this?
What version is your bootloader, you can see it in the fastboot screen.
30.71(*) (sha-913941e, 2013-07-31 10:46:37)
is that was your looking for?
OK, that is the 4.2.2 bootloader. Your bootloader is locked in that screen shot - so how did you install twrp recovery?
Also your avatar shows AT&T but you mention you tried using the Sprint update, can you confirm the phone you have is a Sprint model?
Steve-x said:
OK, that is the 4.2.2 bootloader, so you should be fine to try flashing the phone again. I'd download the Sprint 4.4 package and try a full flash using rsdlite if possible. Everything on the phone will be wiped/erased of course. Then take the update to 4.4.2. Once that is done you can reinstall the latest version of twrp and root the phone again.
Click to expand...
Click to collapse
thanks for the reply! well i already tried that and i can't get rsd to flash. are there some special drivers i'm supposed to install? i got the motorola drivers from their web-sight. and it won't flash. it sees that there is a phone but all catagories read n/a and it just comes up with flash fails..
i'm not sure how the bootloader got locked again.. it wasn't locked before i'm pretty sure the moto x toolkit i used to flash back to stock relocked it?.. or maybe not. but i do know it was unlocked and now its locked. and when i try to get the unlock code like last time it doesn't work.
yes this is a sprint phone.
Edit: thank you for pointing that out, never changed it from years ago
If you were able to relock the bootloader and have the phone report status code 0 then you'd be the first to have done it. You can relock the bootloader but it requires a specific procedure to be followed and the phone will never indicate status code 0 again.
Review this guide - the first flashing option you should work for you, remember to remove the getvar line
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
i'm a idiot. i must have looked at that guide 15 times today and never read through all of it. just needed to deleate that one file and it all worked. thanks everyone for you help!
the status code 0 must have been incorrect. its back to status code 3 and unlocked. thank you all for your help!

How to get out off a full brick?( i have tried it all so far)

I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Still stucked?
Cesarisg said:
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Click to expand...
Click to collapse
Salik Iqbal said:
Still stucked?
Click to expand...
Click to collapse
Sadly yes, I haven't figured out, I can't unlock bootloader, I can't flash a rom without unlocking bootloader, I've tried 5.1, 4.2.2 and 4.4.4, none of them work without unlocking bootloader, RSD Lite wont work, gets fail message, I'm really running out of ideas, still reading lots of threads from all over the world, even translating some foreign languages.
Download this:
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Make sure your battery is charge enough, and you are getting battery ok, unrar the folder, and flash the . xml from rsd lite, hope your device boot again.
Best of luck.
Cesarisg said:
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Click to expand...
Click to collapse
Cesarisg said:
Sadly yes, I haven't figured out, I can't unlock bootloader, I can't flash a rom without unlocking bootloader, I've tried 5.1, 4.2.2 and 4.4.4, none of them work without unlocking bootloader, RSD Lite wont work, gets fail message, I'm really running out of ideas, still reading lots of threads from all over the world, even translating some foreign languages.
Click to expand...
Click to collapse
Salik Iqbal said:
Download this:
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Make sure your battery is charge enough, and you are getting battery ok, unrar the folder, and flash the . xml from rsd lite, hope your device boot again.
Best of luck.
Click to expand...
Click to collapse
OH WOW, it worked, I tried dozens of gpt files and none of them worked, THANK YOU so much!!, saved my butt from buying a new phone, I will retire from flashing my moto x, stock rom for ever.
I am ARSH and Iive in india if some one is having brazzers membership p lzz give me for one day p lzz share with me my e-mail [email protected] plzzzzzz
No problem..
Cesarisg said:
OH WOW, it worked, I tried dozens of gpt files and none of them worked, THANK YOU so much!!, saved my butt from buying a new phone, I will retire from flashing my moto x, stock rom for ever.
Click to expand...
Click to collapse
I'm glad your phone is working again. Just curious, what were the issues you had with LOS 13 (ghost)?
I've been considering putting that on my phone, but would hold off or find another option if something won't work right. I'm still on stock 5.1.
mwaterbu said:
I'm glad your phone is working again. Just curious, what were the issues you had with LOS 13 (ghost)?
I've been considering putting that on my phone, but would hold off or find another option if something won't work right. I'm still on stock 5.1.
Click to expand...
Click to collapse
There was 2 main reasons why I had to go back to stock, the main one was that the OS would not let me uninstall any app, I tried everything I read online to try to fix it, even flashing the rom again, nothing work and the other reason was the phone app would not let me hear from the earpiece, it got fixed after getting back to 5.1 and many other bugs and sudden restarts, some of them might be cause by my phone or not, but since 5.1 everything is a lot more stable.

Can't restore Huawei P9

Hi, I have a P9 device, concretely EVA-TL00 model.
The owner unlock the bootloader via DC-Unlocker I think and then flash some ROM (he think that he flash another model ROM).
So, the problems are: the bootloader is unlocked but flashing TWRP give me a "Remote: image verification failed", the IMEI is 000000000000000 and only shows one IMEI when it's Dual-SIM. Some partitions are unable to flash too, giving a partition sizing error via fastboot.
Updating from dload didn't work.
Could be that it hasn't unlock good or give her some error during the unlock?
How can I put this phone working well again if I don't have any backup?
Sorry for my poor English.

P10 Oreo - Boot problem

Hi
I have a BIG problem with my P10 (L29C432) on Oreo 365.
Tried downgrade to nougat through Firmware Finder but update failed. Now i have this warning at every reboot.
I have LOCKED bootloader (never rooted phone). And i cant get bootloader unlock code (website not working).
Also cant enter fastboot mode because of that error.
Is there anyway to RESTORE phone with locked bootloader? I have tried to flash previous firmware with sdcard method (hold power,+,- keys) but update fails everytime.
Is there other way to flash new firmware?
I can use phone but at every reboot i get this message?
If there is no other way to flash new firmware than with unlocked bootloader... Where to get code for unlocking bootloader?
Thanks.
Edit:
I can enter fastboot mode but my bootloader is locked.
you have to unlock bootloader by sending all the needed info per email.
you need to send them IMEI, model version, S/N number, and product id and request for bootloader unlocking code this email: [email protected]
next time read about how to rollback to nougat...
Thank you. So I need to unlock bootloader.
Will try to get code.
tomzzi said:
Thank you. So I need to unlock bootloader.
Will try to get code.
Click to expand...
Click to collapse
If you don't have your "product id", you can't have the code for unlock the bootloader :/
The "Product ID" is a code into the system info on android :s
I am waiting for code from Huawei. They will send me code in next days...
you can get product id on imei24. com by typing your imei.
Now i have another problem. I think phone is "dead" now. Unuseable.
Tried to root phone and now nothing works.
Phone does not recognize SIM card at all.
If I go into settings and system information there is no IMEI number?
Can i restore this?
Or need to take it to service center? Or dead phone?
send the device against wall. Buy another one and forget averything about rooting and unlocking bootloader. Its for your safety, trust me.
I have experience with rooting and flashing phones (Sony). Never had problem.
So there is no way to restore phone?
maybe in repair store. Never heard about bricked device without imei. You can still try to flash original firmware.

I have a Huawei Mate 10 wich after hard brick (COM1) 6 mounth ago wake up himself!!!

I have a Huawei Mate 10 wich after hard brick (COM1) 6 mounth ago wake up himself!!!
Fastboot is works
Bootloader locked
eRecovery works
Stock recovery works
I have a my phone bootloader key
But DC Phoenix not flash any update.app or board.dgtks file (DC gives evrytime ERROR... device not supported, flashing incomplet). Flashing stops befor DC phoenix can open backdoor.
In fastboot works only one command, that is FASTBOOT DEVICES, and result is 123456789ABCDEF
I can*t flash nothing in fastboot vommand line: gives me error for example:
FASTBOOT FLASH OEMINFO OEMINFO.IMG
sending `oeminfo` 378kb...
OKAY
Writing `oeminfo`...
FAILED remote: Command not allowed
Any fastboot command ends with that error
eRecovery get errors after try flash WIFI DNS firmware finder.
Device lost all: oeminfo, vendor, IMEI, model
And only founded information by DC/HCU/fastboot is device name 0123456789ABCDEF
What i can to do to fix that?
Thanks
Have you tried an update via erecovery?
mikaole said:
Have you tried an update via erecovery?
Click to expand...
Click to collapse
Yes, of course i tryed. But i said...nothing is works. All methods gives error
I know my bootloader code, but i dont change to use it for open.
OEMINFO is damaged, lost all device information parameters
Edkalax said:
Yes, of course i tryed. But i said...nothing is works. All methods gives error
I know my bootloader code, but i dont change to use it for open.
OEMINFO is damaged, lost all device information parameters
Click to expand...
Click to collapse
You should try the test point method that wr are discussing here - > https://forum.xda-developers.com/mate-10/how-to/discussion-hard-brick-infos-t3789044/page28
Pretoriano80 said:
You should try the test point method that wr are discussing here - > https://forum.xda-developers.com/mate-10/how-to/discussion-hard-brick-infos-t3789044/page28
Click to expand...
Click to collapse
YES, i can access to testpoint, but what i can do next? DC phoenix and board with COM1? Thats no working, or works?
Edkalax said:
YES, i can access to testpoint, but what i can do next? DC phoenix and board with COM1? Thats no working, or works?
Click to expand...
Click to collapse
Yes, you must flash the board with DC Phoenix. And if you don't have the nvme backup, then avoid flashing that when you flash the board.
Follow the latest posts from that thread, to understand how to put it in COM1 with the test point.
Pretoriano80 said:
Yes, you must flash the board with DC Phoenix. And if you don't have the nvme backup, then avoid flashing that when you flash the board.
Follow the latest posts from that thread, to understand how to put it in COM1 with the test point.
Click to expand...
Click to collapse
Ok, yes i know about all that you say me, but 6 month ago if my phone is hard bricked, i tryed with COM1 and over world i think trying with my 10 000 peoples or more do that, but DC Phoenix gives ERROR: Bootloader flashing incompleted
Today, my phone wake up, that is amazing, but still have problem about wghat UP my post im starting
Edkalax said:
Ok, yes i know about all that you say me, but 6 month ago if my phone is hard bricked, i tryed with COM1 and over world i think trying with my 10 000 peoples or more do that, but DC Phoenix gives ERROR: Bootloader flashing incompleted
Today, my phone wake up, that is amazing, but still have problem about wghat UP my post im starting
Click to expand...
Click to collapse
That COM1 was kind of "fake" and Phoenix couldn't flash anything. With test point it should work just fine.
Pretoriano80 said:
That COM1 was kind of "fake" and Phoenix couldn't flash anything. With test point it should work just fine.
Click to expand...
Click to collapse
For knowing to all. Testpoint not help, tryed
@Edkalax
Did you tryed a working dload image for your model in dload-firmware mode?
-with a build GREATER than the one you previously were on with your ALP ?
I don't know if your cust was blanked like boardnumber and imeis in your previous doing with your phone and what it does imply for dload images which are normally not cross cust compatible...
If bootloader is locked that's the reason why you can't flash. You'd have to unlock it.
Also, oeminfo can not be flashed with fastboot with "regular" unlock.
oslo83 said:
@Edkalax
Did you tryed a working dload image for your model in dload-firmware mode?
-with a build GREATER than the one you previously were on with your ALP ?
I don't know if your cust was blanked like boardnumber and imeis in your previous doing with your phone and what it does imply for dload images which are normally not cross cust compatible...
Click to expand...
Click to collapse
Yes i tried DLOAD with SD card and 3 buttons Vol +; Vol -; Power...not flashed, getting information failed
ante0 said:
If bootloader is locked that's the reason why you can't flash. You'd have to unlock it.
Also, oeminfo can not be flashed with fastboot with "regular" unlock.
Click to expand...
Click to collapse
I have bootloader code for my phone, but i cant use it. How i do that?
Edkalax said:
I have bootloader code for my phone, but i cant use it. How i do that?
Click to expand...
Click to collapse
Well, it's fastboot oem unlock UNLOCK_CODE, but if you tried that already it won't work.
If your oeminfo is corrupt that might be why, as it reads imei and SN from oeminfo to calculate unlock code.
return in warranty if bootloader locked
the only fix is to send it to huawei service what ever bootloader locked or unlocked
i received my mate 10 ( hard brick ) today from huawei service ,, they replaced Motherboard cos still under warranty
---------- Post added at 11:43 PM ---------- Previous post was at 11:38 PM ----------
one more thing ,, tried to fix it with all paid &free tools available but No .
the only solution is to send it to huawei service and do not mention any thing about unlocked bootloader . and they will fix it

Categories

Resources