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.
I rooted to 4.4.2 and it went fine- then I realized I had lost wi-fi.
I have tried to restore and tried using odin and zip files to install a stock rom after I found a similar problem with link on
Sprint forums saying it will fix the ""button won't stay on" but the fix only works if the device is in stock rom.
answer on Sprint forum says baseband version was mk2 needs to be nae.
Return the phone to stock, run the fix for the wi-fi and then re-root.
I have downloaded and ran several roms that say they are stock- I've factory reset, cleared cache, no matter what I do,
I end up with a rooted device in 4.4.2 and no wi-fi. If I could just get the wi-fi back I would take it at this point
This was just a little quick upgrade that turned bad and long
The Sprint forum had a link to get it to nae, but wont work if rooted., so need to put the phone back to stock- run the patch and then can upgrade to kit kat again
TLDR: I cannot get my Sprint s4 back to any version that isn't rooted. I have tried several (lots) of roms that say" stock-unrooted" rom,
Never goes back to stock- stays rooted without wifi-
Ran a rom VPUAMDC_L720SPTAMDC_SPR but when I install I get msge "ifooter is wring signature invalid" - and it fails.
reformatted the sd card, tried different roms and get some message and it stays rooted and no wifi.
TLDR: need to get stock rom so I can get back wi-fi and then root the whole thing. as 4.4.2 Or 4 , if it exists)
Any options and any ideas as to where or what to do?
EDIT: for clarity cause I am not making much sense at this point
Thanks
Heh... a TL;DR for a TL;DR... the internet is becoming one crazy place.
thousandwatts said:
The Sprint forum had a link to get it to nae, but wont work if rooted.
Click to expand...
Click to collapse
Maybe a dumb question, but why not just unroot first, then?
Hey guys. I know for sure there is another thread about a similar problem but the biggest problem I'm having is figuring out what to do next, or better yet, what did I even mess up?
I made a thread a couple days ago here asking about the LTE option on my phone and how there was none. It's an Intl' phone and therefore I guess doesn't work on Canadian LTE networks.
Before we start, I'm using TWRP 2.7.0.0 . My phone is the UAE version of the D802, which is the D80220C. My current custom rom is Liquidsmooth MS3.2 .
So I found a list of modems and flashed the one for Bell. It was for the D803, but the thread I was looking at said it was cross-compatible so I assumed that meant it's okay for me to flash it on my phone.
Even so, I backed up my EFS partitions just to be 100% sure. I even used the .zip file that automatically backs up the current modem files. So I thought there was definitely a way out if it didn't work.
I will give you the full story of what was done and maybe I can get some guidance on maybe something I did wrong.
1) I flashed the D803 Bell modem.
2) Reboot to system, LS3.2 hangs on start up. Tried a hard restart to see if it wasn't a fluke. Nothing. Still hanging.
3) Figured the EFS files were toast, so I ran the restore .zip for my EFS. Reboot, and still hanging.
4) Said WTF? and restored my first stable rooted stock rom. It booted into the rom fine, but when it got to the lock screen I saw the "Service Disabled" and the phone quickly crashed.
5) Didn't even attempt to restart on that rom. So I tried a couple terminal commands to copy the modems1.img and modemst2.img files to corresponding partitions. Copied both just fine, but no change. Still screwing up.
So, this is where I am so far. I am in the process of downloading the D80220C UAE .kdz file so I can try to flash that one first. If that doesn't work, I'm really at a loss.
When I read into this some more, all I see is people who have totally wiped their EFS files and having to spend a whole bunch of time using a bunch of different programs to get in an recover the IMEI number.
What do you guys think?
Some good news right off the bat. I found a KK baseband for D802 and flashed it. So now I was able to restore my LS3.2 rom and boot into it fine. I see my IMEI and MAC address and can get WiFi at last!
Mods, you can delete this thread if you wish.
I have searched everywhere with no luck. My I337Z was 4.4.2 (after OTA) working well, no root, no unlock. Suddenly IMEI and Baseband go null. So what I did first was to restore it to factory settings, which didnt work and also some native apps like Contacts stopped working (not opening). I tried to restore it through KIES, it put my phone in Emergency mode, no escape there...I then went to the Factory files http://forum.xda-developers.com/showthread.php?t=2448794 which got my phone back to 4.2.2 and working...but still no Signal nor IMEI nor Baseband. I flashed MODEM and now it doesn't have any sound, wifi either....I went through KIES again and was able to catch the files it downloads when initializing the device, flash the System, MODEM and CSC, but same results and it is still on 4.2.2. Also when trying to flash Bootloader I get FAIL(Auth) code (I suppose because my BL is not unlocked)
My request:
I am thinking if someone can make a backup of System partition, I could put it into my phone as RESTORE through TWRP (not installed yet) I might be able to revive this device.
EDIT: I am looking build i337ztuubne2 since my bootloader is now ne2 because of the OTA
Suggestions are welcome!! Thanks!!!
MAGICPERF said:
I have searched everywhere with no luck. My I337Z was 4.4.2 (after OTA) working well, no root, no unlock. Suddenly IMEI and Baseband go null. So what I did first was to restore it to factory settings, which didnt work and also some native apps like Contacts stopped working (not opening). I tried to restore it through KIES, it put my phone in Emergency mode, no escape there...I then went to the Factory files http://forum.xda-developers.com/showthread.php?t=2448794 which got my phone back to 4.2.2 and working...but still no Signal nor IMEI nor Baseband. I flashed MODEM and now it doesn't have any sound, wifi either....I went through KIES again and was able to catch the files it downloads when initializing the device, flash the System, MODEM and CSC, but same results and it is still on 4.2.2. Also when trying to flash Bootloader I get FAIL(Auth) code (I suppose because my BL is not unlocked)
My request:
I am thinking if someone can make a backup of System partition, I could put it into my phone as RESTORE through TWRP (not installed yet) I might be able to revive this device.
Suggestions are welcome!! Thanks!!!
Click to expand...
Click to collapse
KIES 2.6 or 3? You had to be root to get to TWRP. Did the Z model ship with 4.2? I would be surprised, but don't really know. try 3. Start in download mode. I use cricket as well but never a cricket device. I will be in our cricket retailer today, the guys are pretty much ignorant to anything more than activating but possibly one may have a Z/s4 we could pull a nandroid from. Doubtful.
Sounds like you need a warranty replacement. Lesson learned? Always backup EFS!
halfevildruid said:
KIES 2.6 or 3? You had to be root to get to TWRP. Did the Z model ship with 4.2? I would be surprised, but don't really know. try 3. Start in download mode. I use cricket as well but never a cricket device. I will be in our cricket retailer today, the guys are pretty much ignorant to anything more than activating but possibly one may have a Z/s4 we could pull a nandroid from. Doubtful.
Sounds like you need a warranty replacement. Lesson learned? Always backup EFS!
Click to expand...
Click to collapse
First, the phone came with 4.2.2, so I used the files that kies 2.6 downloaded (haven't tried with kies 3) but the phone had 4.4.2 when it started acting up. It was updated OTA. As of now, I am rooted with twrp installed, no issues there. Now, if you could extract a nandroid from one of them, would be great! I do want to be on KitKat and not JB. I can flash it through odin 4.2.2 with no WiFi, sound nor calls. I think because the baseband is for KitKat and not for JB