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.
Here's the story
1. this phone wouldn't boot up after the OTA update, the screen read "firmware upgrade encountered an issue.
please use software repair assistant & try again."
2. used odin 3.09 to reflash pit and the latest nc4 official firmware (I know it can't be rooted, but that's the only choice I have).
3. phone came back alive, worked for t-mobile and verizon sim cards.
Problem:
after a few hours or maybe a day, or maybe a restart, phone won't detect sim card, baseband version shows unkwown, hardware
version is empty, imei, network, MIN, PRL version, ERI version, imeisv, iccid are all "unknown".
What I have done:
phone will be back to normal if I flash the firmware again, I've use odin 3.09 and kies 3 many times.
I also tried flashing different modems, for ex, MI9, MJE, NC2 even NC4. But phone will keep restarting, sometimes the phone is working after
a few restarts. But eventually I will have the same problem again.
I was wondering if someone could point me to the right direction?
nicedog said:
Here's the story
1. this phone wouldn't boot up after the OTA update, the screen read "firmware upgrade encountered an issue.
please use software repair assistant & try again."
2. used odin 3.09 to reflash pit and the latest nc4 official firmware (I know it can't be rooted, but that's the only choice I have).
3. phone came back alive, worked for t-mobile and verizon sim cards.
Problem:
after a few hours or maybe a day, or maybe a restart, phone won't detect sim card, baseband version shows unkwown, hardware
version is empty, imei, network, MIN, PRL version, ERI version, imeisv, iccid are all "unknown".
What I have done:
phone will be back to normal if I flash the firmware again, I've use odin 3.09 and kies 3 many times.
I also tried flashing different modems, for ex, MI9, MJE, NC2 even NC4. But phone will keep restarting, sometimes the phone is working after
a few restarts. But eventually I will have the same problem again.
I was wondering if someone could point me to the right direction?
Click to expand...
Click to collapse
When you flashed the different modems, did you check settings/about the phone to verify that the modem flash " took"? Recommend entering Odin from power off, especially when flashing modems. FWIW, I'm not at all sure this will fix your problem, but it's worth a shot.
cam30era said:
When you flashed the different modems, did you check settings/about the phone to verify that the modem flash " took"? Recommend entering Odin from power off, especially when flashing modems. FWIW, I'm not at all sure this will fix your problem, but it's worth a shot.
Click to expand...
Click to collapse
Yes I did. The baseband version showed MI9 when my phone was still working properly.
nicedog said:
Yes I did. The baseband version showed MI9 when my phone was still working properly.
Click to expand...
Click to collapse
OK. Hopefully someone else will chime in with some suggestions.
one more thing I've done many times so far is, sometimes a full reset will bring it back to normal too.
settings -> backup and reset -> factory data reset.
I don't mind bricking my phone, but maybe someone knows other possible way, say, flashing EFS? I don't even know what that is.
I've been searching for the right solution but I haven't found one yet.
Never ever give up!
I'm the OP and I finally got it working. I simply ran EFS Professional v2.1.73, did a backup and restore of the EFS. That's it!
Did you figure out what efs is?
Sent from my SM-N900V using XDA Premium 4 mobile app
It didn't last long, and using EFS profession for EFS backup/restore never worked again.
I then saw this page the other day,
http://forum.xda-developers.com/showthread.php?t=2610757
So I used odin to flash
pit
official kitkat rom
I also checked these two,
erase nand
erase EFS
the phone booted up fine, I then turned it off and entered recovery mode, did a data and cache wipe, then booted up the phone again, that brought back my imei, my sim card worked again.
Unfortunately I'll lose it again once I flash a custom rom, or perhaps even a reboot.
I'm still searching for a permanent solution. But at least now I can use my sim card with a stock rom
Rom based on which region?
nicedog said:
It didn't last long, and using EFS profession for EFS backup/restore never worked again.
I then saw this page the other day,
http://forum.xda-developers.com/showthread.php?t=2610757
So I used odin to flash
pit
official kitkat rom
I also checked these two,
erase nand
erase EFS
the phone booted up fine, I then turned it off and entered recovery mode, did a data and cache wipe, then booted up the phone again, that brought back my imei, my sim card worked again.
Unfortunately I'll lose it again once I flash a custom rom, or perhaps even a reboot.
I'm still searching for a permanent solution. But at least now I can use my sim card with a stock rom
Click to expand...
Click to collapse
Can you please tell the stock rom based on which CSC ? or country ?
I'm having the same issue. Lost baseband and imei, but never got it recovered. even with stock.
I use this one,
ALL_VZW_N900VVRUCNC4_N900VVZWCNC4_1487472_REV03_user_low_ship_MULTI_CERT.tar.md5
http://www.trueandroid.com/2014/05/n900vvrucnc4-android-442-kitkat.html
Same boat brother, this is what I've posted. So far I'm a week in this situation, battery pull brings it back, any mod like Xposed with module where you have to reboot looses the baseband, IMEI etc. I have backup of the EFS and restored it multiple time with no joy.
Need some advice guys for Verizon my Note 3, I'm currently stock NC4 ready to. flash this bad boy ROM, after root access with TowelRoot, installation of BusyBox and Supersu no SafeTrap yet. Once I reboot in this state, I have the Baseband unknown under Settings-About Phone status all unknown info on IME etc etc. Off course I loose 4G signal all together. I may reboot again and it comes back. I know about EFS partition corruption and have multiple backup of My note 3 EFs partition. Even with restore it would still happen. I have exhausted all my knowledge learned throughout the years from you guys. But, I'm asking some help again. I am very familiar with all the terms about flashing/rooting so please feel free to throw some genius on how I can fix this thing.
Sent from my SM-N900V using Tapatalk
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.
This is a good one. Let a friend borrow my VS980 (Verizon LG G2), ofcourse it was modified with TWRP, etc. He like me knows how to handle roms, etc. However, he seems to have flashed a Korean G Pro 2 firmware of some sort and while the phone was booting properly with actual Verizon roms, wifi, signals, etc did not work. So upon attempting to revert to stock I noticed Download Mode did not work. So I used AutoRec for the vs980 and it caused the phone to get into fastboot mode. Using the following guide, I fixed the fastboot issue:
http://forum.xda-developers.com/showthread.php?t=2681089
Now I am still detected as a F350K, this is usually due to that information being stored in the build.prop, which I couldnt wipe since the fastboot loop would ban booting into DL mode or TWRP.
I have also read about the generic .dll file, but it is a no go, assumingly because were talking about two different phones.
Any suggestions? Will a .kdz restore be more better than a .tot restore?
:crying: I got desperate and permabricked it. Tried flashing the Korean G Pro 2 firmware and now it will not power on. No download mode, not detected, etc. Eventually it will show the notification LED flashing colors like it wants to boot, and nothing more. I guess this is the end for my VS980.
I Have same Problems facing bos! Now what can i do! Help Me Plzzzz...........
Youtube:
Hello XDA. I recently revived my G6 after it sat in my drawer for years and was delighted to see HavocOS on Oreo still running on it. I popped in my T-Mobile SIM and voila, service. My only issue was horrible data speeds. I tried every network settings and apn fix that is relevant to my device but I was still stuck with virtually no 4G data. So, my last resort was to flash back to stock. Now, I dont know if there is a specific method for this device as I forgot how complicated the root exploit was. But I went ahead and downloaded the latest stock .kdz (20g), LGUP and the drivers and proceeded as normal to flash the kdz over. I had SEVERAL issues getting my device model to be recognized and finally grabbed the right LGUP version that worked. I proceeded to flash the kdz when it gave me an error round 31%. I did much troubleshooting research and came up empty, finally decided to try flashing the stock version it was on (20a) to just restore it.
This worked. I thought I was saved until the phone froze on the T-Mobile logo while booting and didnt budge for an hour. Much more googling and I found a thread that looked promising and seemed to help. At first. It flashed the kdz, gave me the error, and when I tried to flash the dz, nothing. I retried LGUP with 20a stock, unknown model. I tried to go back through the whole rooting process again and stick it out with minimal service. The FWUL/lglaf portion of the guide is where I got stuck. My device would not be recognized in FWUL, I couldnt get wifi so plugged in my ethernet. And then I kept getting "USB configuration not set" and "input/output" errors, and I noticed that while booting FWUL, the step "Loading Kernel Modules" fails. So I assumed that FWUL was not loading any modules, including USB's (which explained the errors), so I booted up my own Manjaro install and cloned the same project there. Knowing all my modules work now, I still get the "Input/Output" error.
So now I'm led to believe this phone is hard-bricked. It registers as a port in Window's Device Manager, "LG AndroidUSB SerialNet" or something like that. I tried following the unknown model guide again to no avail. I'm at a loss. Whatever info is needed for debugging I'll provide. I'm dualbooting Win10 and Manjaro so any methods are viable.
Which specific stock KDZ(s) did you try to flash on your phone (full kdz name)? You need to seperate flashing and rooting as two separate tasks because from your post I can't tell if you are able to boot after flashing stock kdz or not. First, if your phone is not booting, you gotta recover from that and flash a stock kdz.
Also, try using the Dev patched LG UP from this post (thank the dev while you are there): https://forum.xda-developers.com/lg...ssflashing-t3780969/post76510671#post76510671
Try the 'Partition DL' option when you flash and select all partitions in the next window.
Once you are able to boot a stock rom, you can try using a VMWare such as virtual box, install/mount FWUL in a virtual environment and use that to root the phone. I think the process is somewhere here on the runningnak3d's guide or on another post, I will try find a link later.