Helo all - I could really use a hand here. This is the second time I have faced this issue.
When trying to make a call on my 614c when the battery is low, it crashes. Upon reboot, the radio no longer works and I cannot make any calls. It just goes into a permanent "Seaching" mode.
What I've tried:
Reboots - warm and cold
Removing the battery for 30 mins
Reset to defaults
Multiple different ROMs including upgrading and downgrading the Radio
No luck.
Last time (3 months ago) I ended up sending it to ipaqrepair to be fixed.
They said:
"the un-official hacked ROM installed in combination with a corrupt / mismatched GSM Radio ROM, these are the root cause of the issues"
I had actually NOT installed a non-official ROM until after it stopped working in a desperate attempt to fix it. But when they got it, it was a 6.5 ROM.
This time, I had upgraded it to 6.5....but I have since downgraded to the official ROM an installed the. .89 Radio update.
It wont work at all and I can't justify mailing it away for another expensive repair.
Any ideas or assistance would be greatly appreciated. Thanks.....
Any ideas? How can I effectively "blow away" all the software/drivers and set the device up as new? IpaqRepair said it was corrupt software last time....
I've installed different ROMs via flash.dio and I tried the HP radio upgrade RUU_1.8.0_081208_MP_M089_WWE. Are their files or settings that the installs I am doing do not affect - and if so, how do I repair/replace them?
Using Sim Manager, it says the phone is not ready. It's just like the phone radio won't initialize...
This phone originated overseas (Europe) - could that be somehow causing this issue since I'm using it in the USA? Something locking or changing and no longer compatible?
Not sure what else I can do and am missing my phone. Any ideas or assistance would be greatly appreciated.
Still fighting with this....maybe onto something now?
When I get the asset viewer information for the phone it shows the radio is present and the firmware number.
the Stack Version, Bootloader Version, Filesystem Verions and Radio GDFS versions are blank.
It does show the IMEI.
I'm guessing I'm missing file/data for the radio....but reinstalling the Radio ROM HP offers has not helped (maybe not complete - just an upgrade?)
Thoughts?
Anyone have a copy of the original ROM and .81 Radio ROM?
Maybe rolling it all the way back might get it operational again....
Official Drivers/Rom/Radio for 614c
Hi,
You can download official drivers from HP website. The forum does not allow me to post the link. Just search for "official 614c drivers" in google and you wil get the link.
Also note, please install using WINDOWS XP os as installing this using other os such windows 7, windows vista etc is not possible.
Okay - I tried installing the software from the HP Website using XP - but it still isn't working. It's just like the software for the radio is corrupted and it won't replace it (does not list the versions like it should when you look at the software inventory).
Is there any way to manually do this? Any advice or help would be greatly appreciated.
If anyone can help me get this resolved, I'm definitely buying them a beer.
Basically the GSM just seems to be bricked. Last time a software fix resolved it, but I'm not sure what software needs to be installed to get the radio working again.
What is the best way to blow it all away and start over? Is there a way to manually delete the radio files - or to look at them for versions/dates to see what is corrupt or mismatched.
-Alpha- said:
If anyone can help me get this resolved, I'm definitely buying them a beer.
Basically the GSM just seems to be bricked. Last time a software fix resolved it, but I'm not sure what software needs to be installed to get the radio working again.
What is the best way to blow it all away and start over? Is there a way to manually delete the radio files - or to look at them for versions/dates to see what is corrupt or mismatched.
Click to expand...
Click to collapse
Just bumping this thread...would love to have this phone back.
Bumping once again - still in hopes of fixing this phone. Can anyone help?
-Alpha- said:
Bumping once again - still in hopes of fixing this phone. Can anyone help?
Click to expand...
Click to collapse
I guess, you will get enlightenment for the problem on your device at http://forum.xda-developers.com/showthread.php?t=455840
Bump.....
Still hoping for a solution. I have gone to a Glisten now, but do not like it as much as the 614c.
I'm open to any suggestions.
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.
Alright, Wow a lot has changed here since I got the Note 4!! I no longer use it since I got the A9 from HTC after this one went kaput. Heres the sitch'.....I am super frustrated since the issue I have is a lot like many others ive read all over the internet with just one difference...the USB is not being recognized so I can't use Odin....yes I have tried many different computers, cables etc....the thing was and is still new bout 6 months old before i messed it up so I cant believe that something would or could have easily fried the USB port already. Nothing I have done comes to mind where that could have occurred and could be bad luck getting bad port from the start but unlikely...SO....making it worse is I can boot to stock recovery and the weirdest thing happens when I try to pick any option other than wipe cache or factory reset....it comes up and says dm verity failed, whatever option i chose is disabled!! WTH??? I have been in this awhile so this isnt my first rodeo by far and I have yet to see this.
My question is....HOW can this be fixed...counting out replacing the USB port(that may not be the major cause), I am not sure JTAG will work....most other options all require some sort of PC to Mobile connection to be working and I can't ever get QPST through QXDM to see it( i may be doing it wrong or missing a step....possible since Ive found most instructions to be missing vital information, especially for some of us who may be more green), AND Ive tried creating bootable sd card to use in download mode. The latter option is also very hard to find complete information on process and files needed to properly do so pertaining to this specific variant. The stock recovery i think woukld be the best bet but HOW CAN I ENABLE the options in recovery that are now disable???
I apologize to anyone annoyed if I am asking a question that is often asked.....bear in mind I have another handset I am working on that is completely different that takes up way more time lol, I have searched for weeks on this issue and nothing substantial can be found thanks to to much incomplete information given out AND no one seems to know how to fixed the recovery issue or even had it. Any help will be totally appreciated.....Thanks
Hello, guys! It's now my 2nd post asking the exact same help. I'm very desperate to fix my phone : Asus Zenfone 5.
I have been looking for solutions for a long time, I'm not easily quit on googling. So far, this problem is one that haven't been fixed and very unlikely to be fixed
I have contacted many people including that Taiwan guy who is an expert on Zenfone 5 (forgot the name) and I'm EXTREMELY DESPERATE
I know this problem might be similiar with other case, but this one seems to be rare, because I have not found the solution.
Here is the timeline before my device got soft-bricked :
1. I upgraded to Lolipop with a different version of it's recovery, but still worked.
2. One day, ANR Keeps reporting that SystemUI has stopped. Rebooted and the phone went bootloop.
3. (probably the problem) I flashed wrong version of recovery (I think it was kitkat's recovery) and after then, I'm not able to get into DROIDBOOT.
I have tried several ways :
1. Sending package to my phone over ADB Sideload (It says something like error mounting blabla)
2. Flashing with xFSTK (It says something about driver, and I googled it. Found everyone with the same problem, endless solutions)
3. Downloaded about 1 gig of files (DEBRICK Files) and still, gets stuck somewhere.
So anyone have a solution for me, please?? I'm totally desperate right now, I lost hope. Never had this kind of problem, the thing is that so far, I never had such never-solved case in my life, I will always
find a solution from Google even that would take a long time. I have been searching passively for about 8 months, and I got none of those works
I will be very thankful if anyone would try to help this problem, I will bring detailed information you want, because I don't have solutions left.
Sorry for bad English
Thank You so much!
Christ, I was sure that I ticked it as a Q/A.
how to help? you are just telling about softbrick.
Hey guys,
I've bought my MX4 Pro almost a year ago, but decided only now to ask for your help. Hope you'll be able to guide me to fixing the several problems i have.
First of all, phone came with Flyme 4.5.7I and right from the start there were some features not working. Most important, the fingerprint screen unlock isnt working. After capturing my fingerprint, when i try to enable it to unlock screen it just takes me back to the home screen.
Another issue is getting sometimes (it happens randomly) a no sim error. Sometimes restarting is enough, sometimes i need to take out the sim card and insert it back.
Ever since i've tried to update firmware, hoping it would solve my problems. Nothing has worked.
Dowloaded the update.zip (no matter which version) and placed it in root directory. When i try to open it with the document app i get two options, view and extract. Can't update. Also starting the phone using volume+ and power button (update screen) has always produced the same results: Firmware corrupt. Tried doing it with clearing data, without that, no difference. Tried with a .bin file, same thing.
As far as i know the bootloader is locked, and i remember checking if the device is properly rooted and IT IS NOT.
So, the more android savvy people here can help? I'm lost and i really enjoyed the phone so far, but i dont really know what to do from now on. Is it a faulty device? (This would be the worse, since the phone was bought from China).
I can provide any additional details if needed.
Thanks in advance
P.S. I remember trying every tutorial/solution out there, nothing has seemed to work. I also may be dumb, not sure.