Related
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Seriously???
pastorbob62 said:
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Click to expand...
Click to collapse
Not to be negative or anything but I think this is the least responsive forum on this site. I have spent hours searching for possible solutions to various problems I've encountered over the past several months, asked several questions and received little if any help. I was only able to get back from a bricked phone to where I am now by using information found on other websites. Pretty sad if you ask me.
In contrast, whenever I have asked a question on my tablet's forum I've received fast workable solutions/answers to my problems/queries. The threads are informative, well organized and contain answers to any situation I have encountered.
Granted, my current problem with my phone is my own fault for trying to customize it. And I suspect part of the problem is due to the age of this phone thus most of the "experts" have moved on to other ventures. It is also hindered by the lack of information available from Huawei and the service providers.
All of that said, if anybody has any suggestions for how I can repair the ESF partition or whatever is causing this lack of mobile service issue I would be extremely grateful. It isn't the end of the world since i have a new phone (Consumer Cellular) that I am currently using but it would be great to get this one working since it's much faster and more streamlined than my stock Consumer Cellular version.
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
Thank you very much for your reply. It seems that you have found the answer to my problem. But unfortunately, I don't have a copy of the original stock ROM. My phone is the -51 version and any links I have found to the stock ROM are broken. There is a version I found but it is for Venezuela and I don't think it will work. I am leery to try it and totally brick my phone. My backup is apparently corrupted. I backed up my new working phone with Disk Image and attempted to restore it to the broken phone but all that did was cause it to come up to the ATT logo screen for a few seconds and then shut down. It wouldn't do anymore than that. So I restored the Stallion 3.5 image I made and am back to a great fast tablet with no phone service. I also tried backing up my IMEI on the working phone and restoring it to the broken phone but that had no effect.
It is my understanding that the -Pro version of the ROM will work, but I don't have the stock image of that either. I suspect it work might since I was able to use the -Pro version of GB on it. All of my internet searches have only turned up custom ROMs and other desperate people looking for fixes for similar problems or worse. I agree 100% with your assessment of Huawei's lack of meaningful support. It really is a shame, because these phones aren't half bad when they have been customized and OC'ed a little.
I have just about given up on it and resigned myself to using it as an MP3 player for my car system. I have learned my lesson and am leaving the working phone stock. It is rooted and I have cleaned off all of the bloatware, and set it up so most apps run from my SD card, so it really isn't half bad. At least it works.
Again, thank you for your reply and advice.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
ggunzio said:
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
Click to expand...
Click to collapse
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Blefish said:
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Click to expand...
Click to collapse
i have exactly the same phone than you, because i installed that backup too. After installed it, the IMEI SV is 36, after installing B518 it says it is 18, but before it was 17, and i had 3g signal, but not now.
My question is, wich SV is your phone reporting?
Thank you
I also have a problem like this, but I think it's a bit more severe. My phone got stuck while charging. Couldn't reboot. Was getting stuck on the aurora loading screen(using DZO 5u20). Than reinstalled whole rom. But now I don't any signal and the phone doesn't even see a SIM card. Showing 'baseband unknown' and the IMEI and IMEI SV are also unknown. Not 0's but just unknown. Is this is a similar problem? And can something be done to fix it.
I had some backups on my sd card, untill the sd-card got fried in the phone a couple of months ago.
Hi all, I am a first time poster
I own a galaxy S3 (GT I9300)
first problem...
i flashed a rom called CrDroid and it wiped my EFS and IMEI so i couldnt make or receive sms or calls and got a generic 0049 IMEI
2..
Upon trying to fix the issue, i tried to flash CWM recovery touch and my touchscreen stopped working. so, its a software issue, not hardware
i have tried flashing many different roms, kernels etc but nothing will fix my problems.
is there someone who can assist me in fixing my problems? (flash touchscreen drivers and restore EFS data [in that order])
or
Can someone give me information on how to reflash EVERYTHING on my phone including system and root (and any other) partitions?
i am NOT interested in sending my phone back to samsung or to a repair centre
PLEASE HELP!
Here >>>> http://forum.xda-developers.com/showthread.php?t=2344125
..everything you want to know steps by steps tutorial from flashing to rooting.
Sent from my GT-I9300 using Tapatalk
thank you so much sir but i can't find the solution to my problem
my touchscreen was not working after i flash by wrong recovery n7100
and now i want to fixe it but how?
You'll need a new touchscreen, nothing you can do with software as you've blown the controller.
Hello,
I have this problem with my phone and i don't know how to fix it, the IMEI is Null and when i enter "*#0011#" the ServiceMode is Blank !!
I tried to use GS5_EFS_Backup but it doesn't work ! Also the phoe get hot a lot, and when i put it in charge the battery level of charge is stuck in 10% always.
My phone is rooted.
Help me Please.
Thank you
Sounds like you wiped your EFS partition without backing it up first
Phone is dead if that is the case
Some people have had success backing up another S5 EFS, then restoring it to the dead phone
Otherwise, take it to a repair shop, next time backup before messing about
*Detection* said:
Sounds like you wiped your EFS partition without backing it up first
Phone is dead if that is the case
Some people have had success backing up another S5 EFS, then restoring it to the dead phone
Otherwise, take it to a repair shop, next time backup before messing about
Click to expand...
Click to collapse
Thank you Detection for your answer. So where can i find another S5 EFS, and how can i restore it.
Help me Please because i tried already to take it to a repair shop but they don't know how to fix it, that's why I wanna try to repair it myself, and i think its one of the repair shops who wiped the EFS partition without making a backup (because i give to 3 repair shops and they don't know how to fix it).
You'll need another S5, no-one here will give you their EFS backup as it is specific to their S5
A trusting friend / family member or an old 2nd hand S5 if you can find one, is your only choice
*Detection* said:
You'll need another S5, no-one here will give you their EFS backup as it is specific to their S5
A trusting friend / family member or an old 2nd hand S5 if you can find one, is your only choice
Click to expand...
Click to collapse
There is no other solution like flashing the PIT file using Odin and reinstate the stock rom or any other solution !
Nope, not if you've deleted the EFS partition - that contains the IMEI and Radios
Ok thank you, ill try to contact samsung after sales service.
Hi everybody,
I have same issue:
I needed to update SU-binaries and tapped accidentally on CWM/TWRP-Mode instead of normal. After this IMEI is null, Service Mode blank, sudden reboots and unable to install any Apps (always saying no free memory). uninstalling App causes reboot.
I have efs backup made with (PhilZ Touch) CWM, but I'm not able to fix the problem with it.
What I tried:
flashing Stock ROM + updating Bootloader in Odin
this Guide (except Samsung Tool and Terminal Emulator steps, as I can't install any App)
CWM script
I really don't know what else I can do. Does anybody have some other ideas?
Also backing up is not possible, now. EFS Professional says specified PIT file does not exist, even when I choose all partitions.
FIXED. Possible solution.
Fixed. Went to a shop to repair IMEI/EFS.
It seems there is something called "IMEI NV Generator", this should also do the magic and would have saved me some money.
samsung S5 Imei Proplem
zicozack said:
There is no other solution like flashing the PIT file using Odin and reinstate the stock rom or any other solution !
Click to expand...
Click to collapse
I have the same problem after trying to change the original IMEI>>> any help please
Please take a look here and here.
Hi everyone,
Google messed up ! I received the OTA for the 7.1.2 uptdate last thursday. After it my phone was unable to detect my SIM card, my IMEI number disappeared, neither base band.
The first thing i've tried is to get a new SIM card, with no result, then I tried a soft reset, an hard reset (factory reset+wipe data), and wiping the cache without any positive result either. I've contacted Google, the phone was from Google Store and my 1 year warranty expired on 25/03/17 (the update was installed on 05/04/17, exactly two week later), they refused to take it back, nor RMA, a shame! I think it will be the last Google phone I buy!
I've tried to flash the full factory image of 7.1.1. but nothing positive from it. I think the OTA corrupted my EFS data files but no idea on how to fix it. The thing is when i'm going to the bootloader, under barcodes menu i still find an IMEI number.
I don't know what to do now, I'm little bit desperate, if anyone have an advice here.:crying::crying:
Thank you in advance.
Nexus 6P
7.1.2 build N2G47H
kernel 3 .10.73-g0a21e4c
Bootloader locked
Unrooted
blckhwkone said:
Hi everyone,
Google messed up ! I received the OTA for the 7.1.2 uptdate last thursday. After it my phone was unable to detect my SIM card, my IMEI number disappeared, neither base band.
The first thing i've tried is to get a new SIM card, with no result, then I tried a soft reset, an hard reset (factory reset+wipe data), and wiping the cache without any positive result either. I've contacted Google, the phone was from Google Store and my 1 year warranty expired on 25/03/17 (the update was installed on 05/04/17, exactly two week later), they refused to take it back, nor RMA, a shame! I think it will be the last Google phone I buy!
I've tried to flash the full factory image of 7.1.1. but nothing positive from it. I think the OTA corrupted my EFS data files but no idea on how to fix it. The thing is when i'm going to the bootloader, under barcodes menu i still find an IMEI number.
I don't know what to do now, I'm little bit desperate, if anyone have an advice here.:crying::crying:
Thank you in advance.
Nexus 6P
7.1.2 build N2G47H
kernel 3 .10.73-g0a21e4c
Bootloader locked
Unrooted
Click to expand...
Click to collapse
Hello...
Unless you have a TWRP EFS backup, there's not much you can do...
I already saw some people saying that a restore from someone else EFS backup solved the problem and their proper IMEI, etc were back. I never had the issue, so I can't confirm it really works.
Now you need to find someone who can give it to you.
Otherwise you can RMA...
Good luck...
Is there any personal info in the efs backup? I would be happy to help but am not going to jeopardize privacy...
Sent from my Nexus 6 using XDA-Developers Legacy app
CyberpodS2 said:
Is there any personal info in the efs backup? I would be happy to help but am not going to jeopardize privacy...
Click to expand...
Click to collapse
Hello...
Since his IMEI disappeared, there must be infos about it somewhere in the EFS. I don't know what else...
Cheers...
CyberpodS2 said:
Is there any personal info in the efs backup? I would be happy to help but am not going to jeopardize privacy...
Click to expand...
Click to collapse
I think giving someone a copy of your efs partition essentially gives them the information needed to clone your phone, so it's not something you would want to do for a stranger.
blckhwkone said:
Hi everyone,
Google messed up ! I received the OTA for the 7.1.2 uptdate last thursday. After it my phone was unable to detect my SIM card, my IMEI number disappeared, neither base band.
The first thing i've tried is to get a new SIM card, with no result, then I tried a soft reset, an hard reset (factory reset+wipe data), and wiping the cache without any positive result either. I've contacted Google, the phone was from Google Store and my 1 year warranty expired on 25/03/17 (the update was installed on 05/04/17, exactly two week later), they refused to take it back, nor RMA, a shame! I think it will be the last Google phone I buy!
I've tried to flash the full factory image of 7.1.1. but nothing positive from it. I think the OTA corrupted my EFS data files but no idea on how to fix it. The thing is when i'm going to the bootloader, under barcodes menu i still find an IMEI number.
I don't know what to do now, I'm little bit desperate, if anyone have an advice here.:crying::crying:
Thank you in advance.
Nexus 6P
7.1.2 build N2G47H
kernel 3 .10.73-g0a21e4c
Bootloader locked
Unrooted
Click to expand...
Click to collapse
Google's been messing up along recently
blckhwkone said:
Google messed up !
Click to expand...
Click to collapse
Several people have been able to recover from this by wiping both the EFS partitions, but because your bootloader is locked (and USB debugging probably not enabled), I don't believe there is any way forward. See the link for the method used: http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Yah, I'm serious! I'll tell you in detail.
Weeks ago, when I tried to flash stock rom, I made a big mistake that made my deivice hard bricked and then I found the reason in this thread: https://in.c.mi.com/thread-1095941-1-0.html.
I immediately brought my device to Mi Support Center, they made it alive but other problems came and I posted this thread: https://forum.xda-developers.com/mi-a1/help/help-soft-brick-t3860620 (thanks for people who tried to help me)
I found that my device lost persist partition, so that I flashed it, done, however, I relized that my device lost IMEI and BASEBAND, too.
I tried to restored my IMEI by QCN file but I only got sim 1 IMEI, I flashed BASEBAND and my deivice stuck in bootloop.
After a long time, I asked for someone to help but they couldn't do anything and then I found some problems.
1. IMEI dosen't show anything now and BASEBAND is unknown.
2. I can't flash Android 8.1 or higher versions on my device, it only accepts 8.0 and lower versions. If I flash 8.1, it continuously reboot when Android One logo shows up. But nothing happens when I flash 8.0.
Three days ago, I brought my device to Mi Support Center again, they said my mainboard is broken, it need replacing but I denied because the cost is too expensive, about $145. I took it back, tried to flash 8.0 version and installed update, sadly, my device is locked now and I can't flash anything. I think I can flash 8.0 via testpoint method, but the important thing is that I don't know what's exactly happenning with my device.
Why I can't flash 8.1 version and can I take my IMEI back?
I'm tired to find the answers days and I'm thinking to sell my death device with a cheap price about $40 for screen and camera only.
Someone help me, please!
By the way, I'm in Vietnam.
manhnl311 said:
Yah, I'm serious! I'll tell you in detail.
Weeks ago, when I tried to flash stock rom, I made a big mistake that made my deivice hard bricked and then I found the reason in this thread: https://in.c.mi.com/thread-1095941-1-0.html.
I immediately brought my device to Mi Support Center, they made it alive but other problems came and I posted this thread: https://forum.xda-developers.com/mi-a1/help/help-soft-brick-t3860620 (thanks for people who tried to help me)
I found that my device lost persist partition, so that I flashed it, done, however, I relized that my device lost IMEI and BASEBAND, too.
I tried to restored my IMEI by QCN file but I only got sim 1 IMEI, I flashed BASEBAND and my deivice stuck in bootloop.
After a long time, I asked for someone to help but they couldn't do anything and then I found some problems.
1. IMEI dosen't show anything now and BASEBAND is unknown.
2. I can't flash Android 8.1 or higher versions on my device, it only accepts 8.0 and lower versions. If I flash 8.1, it continuously reboot when Android One logo shows up. But nothing happens when I flash 8.0.
Three days ago, I brought my device to Mi Support Center again, they said my mainboard is broken, it need replacing but I denied because the cost is too expensive, about $145. I took it back, tried to flash 8.0 version and installed update, sadly, my device is locked now and I can't flash anything. I think I can flash 8.0 via testpoint method, but the important thing is that I don't know what's exactly happenning with my device.
Why I can't flash 8.1 version and can I take my IMEI back?
I'm tired to find the answers days and I'm thinking to sell my death device with a cheap price about $40 for screen and camera only.
Someone help me, please!
Anyway, I'm in Vietnam.
Click to expand...
Click to collapse
Do a data format, then install anything.
justboryata said:
Do a data format, then install anything.
Click to expand...
Click to collapse
How to flash something when bootloader is locked? Anyway, that's not point, I can flash via testpoint method, the point is why I can't use 8.1 and can I take my IMEI back, thanks!
manhnl311 said:
Yah, I'm serious! I'll tell you in detail.
Weeks ago, when I tried to flash stock rom, I made a big mistake that made my deivice hard bricked and then I found the reason in this thread: https://in.c.mi.com/thread-1095941-1-0.html.
I immediately brought my device to Mi Support Center, they made it alive but other problems came and I posted this thread: https://forum.xda-developers.com/mi-a1/help/help-soft-brick-t3860620 (thanks for people who tried to help me)
I found that my device lost persist partition, so that I flashed it, done, however, I relized that my device lost IMEI and BASEBAND, too.
I tried to restored my IMEI by QCN file but I only got sim 1 IMEI, I flashed BASEBAND and my deivice stuck in bootloop.
After a long time, I asked for someone to help but they couldn't do anything and then I found some problems.
1. IMEI dosen't show anything now and BASEBAND is unknown.
2. I can't flash Android 8.1 or higher versions on my device, it only accepts 8.0 and lower versions. If I flash 8.1, it continuously reboot when Android One logo shows up. But nothing happens when I flash 8.0.
Three days ago, I brought my device to Mi Support Center again, they said my mainboard is broken, it need replacing but I denied because the cost is too expensive, about $145. I took it back, tried to flash 8.0 version and installed update, sadly, my device is locked now and I can't flash anything. I think I can flash 8.0 via testpoint method, but the important thing is that I don't know what's exactly happenning with my device.
Why I can't flash 8.1 version and can I take my IMEI back?
I'm tired to find the answers days and I'm thinking to sell my death device with a cheap price about $40 for screen and camera only.
Someone help me, please!
By the way, I'm in Vietnam.
Click to expand...
Click to collapse
These files were dangerous dude and they brick parts of your motherboard like imei and baseband. So if you need a fix replace it
billis2020 said:
These files were dangerous dude and they brick parts of your motherboard like imei and baseband. So if you need a fix replace it
Click to expand...
Click to collapse
I can buy a new one with the cost to replace to the whole mainboard. In fact, I accept the thing that I can't use SIM anymore, I just don't know why I can't upgrade to 8.1 or higher