This problem has been posted before but I haven't been able to find any solution yet.
I have a UK T-mobile G1.
I started getting the error "Unable to start Wi-Fi", tried updating to JF v1.51 and the latest radio rom installed as well. Don't have any apps as I've tried wiping the handset as well.
Any help would be appreciated
Absolutely sure you have the latest radio? Try wiping and loading a different ROM, as well. If a 2nd ROM still has that issue, it sounds like hardware failure - exchange it.
Related
Hi all, i have been having a very bazaar problem lately...When my phone boots up i get a pop-up message indicating that the gapps process shutdown unexpectedly...and sometimes i may even get a acore crash too. Applications from the market do not download...when i select my download i will end up getting a gapps crash and then the supposed download just sits there saying "starting...". Google talk doesn't even open! It will just say that the process quit unexpectedly. Even after a fresh install with factory data reset all these problems will continue. The initial boot up screen/tutorial will even show a gapps crash. I have tried with 3 different versions of cyanogenmod all with the exact same problem..Each version i've tried with a2sd enabled and disabled, formatting the partition each time before a new install to ensure no data carry-over issues. I don't know what to do. To me it seems like it make be something on googles side...but i can't for the life of me figure out whats causing these wild problems. Help would be very much appreciated.
ANDROID Market problems
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
six6star said:
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
Click to expand...
Click to collapse
I have searched and it seems many people have the Market/Gtalk problem.
I have the same problem (with an Eclair 2.1 Cyanogenmod rom) and I've not been able to find a solution. Wiping the cache makes nothing.
Anyone knows how to solve it?
Huh. I had a problem with the market at first with cyan 5.0.8 . I went in the terminal and ran fix_permissions after su and haven't had any problems since. Might try that
Sent from my HTC Magic using XDA App
Hi guys
I'm a NRG rom user, com5 build and suddenly I'm experiencing the wierdest problem, which I can't solve by myself. Let me explain what happened.
I flashed the latest rom but also went back a couple of versions. I always flash with the flash util which has the task29 feature build in. What happens is that when I flash a rom, all goes well, the complete process including the XDA_UC auto install process. After that everything is okay and everything works. But when I restart the phone all processes are starting to fail loading. Strange thing is that when I remove the storage card and reboot the phone everything is back to normal again. But as soon as I boot the phone with the storage card in everythings fails. I even had white screens of death when booting with a storage card mounted. I also tried dutty's latest rom and mirri's latest, all have the same problem. This problem appeared all of a sudden, all the cabs etc worked like a charm before, so the problem doesn't lie in the cabs or the files autoinstalled during the xda_uc.
A weird solution to this problem is to flash the latest dutch official stock 1.66 rom which is available for the hd2. With that one everything works, also after a reboot. So I can't use a custom rom anymore. Could this be due to a hardware problem? And if so, how can I explain this to HTC if I want to try to send it to them for repair?
Ow and of course I tried it with several other microsd card, all having the same error, so it's not a sd card issue.
I would relock and the re-unlock your hspl and see what happens. That is indeed a weird problem (that you can't send your phone in for).
Good luck
TheWizzard2203 said:
Hi guys
I'm a NRG rom user, com5 build and suddenly I'm experiencing the wierdest problem, which I can't solve by myself. Let me explain what happened.
I flashed the latest rom but also went back a couple of versions. I always flash with the flash util which has the task29 feature build in. What happens is that when I flash a rom, all goes well, the complete process including the XDA_UC auto install process. After that everything is okay and everything works. But when I restart the phone all processes are starting to fail loading. Strange thing is that when I remove the storage card and reboot the phone everything is back to normal again. But as soon as I boot the phone with the storage card in everythings fails. I even had white screens of death when booting with a storage card mounted. I also tried dutty's latest rom and mirri's latest, all have the same problem. This problem appeared all of a sudden, all the cabs etc worked like a charm before, so the problem doesn't lie in the cabs or the files autoinstalled during the xda_uc.
A weird solution to this problem is to flash the latest dutch official stock 1.66 rom which is available for the hd2. With that one everything works, also after a reboot. So I can't use a custom rom anymore. Could this be due to a hardware problem? And if so, how can I explain this to HTC if I want to try to send it to them for repair?
Ow and of course I tried it with several other microsd card, all having the same error, so it's not a sd card issue.
Click to expand...
Click to collapse
sounds like a defective phone!!!!
Yeah, that was my idea too. I tried relocking and reunlocking it with HSPL, but that doesn't matter.
But the problem is, how do I explain this to HTC if I want to send the phone to them for repair? I can't tell them that the problem only occurs when I install a custom made rom.
Pfff okay, I found the solution. It wasn't a hardwareproblem after all. I went through a terribly long trial and error procedure but finally pinned the problem down to only one cabfile, named HD2MemTweak found in the registry tips and tricks section of the general forum of the HD2.
I'd installed the lastest official 3.14 rom and installed all the cabs I was used to. But noticed, after several reinstalls, that when I installed that specific cab and rebooted the phone, everything went wrong. So I installed it without that cabfile and allw as working fine again. Then reinstalled HSPLv3 and installed the latest NRG Cookie Classic rom, which works fine again.
So that was the problem indeed. But one thing is strange of course, is that the mentioned cabfile used to work and suddenly stopped working. Could this maybe have something to do with the fact that the latest roms were build on the new 3.14 official rom? Who knows.....
Hello All,
I have an HTC HD2 (TMOUS) that hangs once it gets warm. I got it a couple of days ago. The first thing I tried to do was to update the rom (there was an old stock rom) to the latest version from t-mobile. But when I tried to do that the update process failed at 8% with "error[262] update error". I tried to flash it again, but got the same result.
I tried both the approaches: to flash via usb and via SD card, but the results were the same. Flashing via SD card gave me "RSA fail" error. I have found some related info, but that is not the case since I could flash the radio later. Also I've noticed that after a couple of iterations the phone were vibrating 7 times during the rom update process. Some guys are telling that it could be a motherboard issue (http://forum.xda-developers.com/showthread.php?t=797179 and http://forum.xda-developers.com/showthread.php?t=826119).
Today I tried to update rom again and got it successfull. But the phone has hanged on botting. Taking into account that the phone has been turned off for the whole night I decided to try to put it into a cool place. I put it to the balcony for 5 minutes and the turned it on again. It has loaded successfully and I was able to test wifi and to make a couple of calls. But after some time when it has got warm it hanged.
I have found that some guys had the same problem but couldn't fix it (http://forum.xda-developers.com/showthread.php?t=701349).
It seems to me now that this is a hardware issue (maybe with the internal flash memory module).
Was anybody able to fix the isssue?
Could this problem be caused by my attempts to flash?
Thanks in advance.
Guys,
I'm kindly asking to share your thoughs on any of the questions. It is very important for me since I don't know whether it is my fault or the phone was already damaged.
The rom I tried to flash was a stock rom and the flashing process hasn't been interrupted.
Thank you!
had this issue and indeed it was the motherboard so i had to send it back to htc.
good luck.
az_registration said:
Hello All,
I have an HTC HD2 (TMOUS) that hangs once it gets warm. I got it a couple of days ago. The first thing I tried to do was to update the rom (there was an old stock rom) to the latest version from t-mobile. But when I tried to do that the update process failed at 8% with "error[262] update error". I tried to flash it again, but got the same result.
I tried both the approaches: to flash via usb and via SD card, but the results were the same. Flashing via SD card gave me "RSA fail" error. I have found some related info, but that is not the case since I could flash the radio later. Also I've noticed that after a couple of iterations the phone were vibrating 7 times during the rom update process. Some guys are telling that it could be a motherboard issue (http://forum.xda-developers.com/showthread.php?t=797179 and http://forum.xda-developers.com/showthread.php?t=826119).
Today I tried to update rom again and got it successfull. But the phone has hanged on botting. Taking into account that the phone has been turned off for the whole night I decided to try to put it into a cool place. I put it to the balcony for 5 minutes and the turned it on again. It has loaded successfully and I was able to test wifi and to make a couple of calls. But after some time when it has got warm it hanged.
I have found that some guys had the same problem but couldn't fix it (http://forum.xda-developers.com/showthread.php?t=701349).
It seems to me now that this is a hardware issue (maybe with the internal flash memory module).
Was anybody able to fix the isssue?
Could this problem be caused by my attempts to flash?
Thanks in advance.
Click to expand...
Click to collapse
Before you go trying to replace the mother board or any hardware such as that. I suggest you run a task 29 on your HD2 and reflash the stock ROM. A task 29 totally wipes the current ROM on the HD2 so if it is a problem from you trying so many timez to flash the ROM this will clear that up. Here is a link to the task 29 thread so you can learn more and decide if you want to do it or not.
Thank you for your replies!
T-Macgnolia said:
Before you go trying to replace the mother board or any hardware such as that. I suggest you run a task 29 on your HD2 and reflash the stock ROM. A task 29 totally wipes the current ROM on the HD2 so if it is a problem from you trying so many timez to flash the ROM this will clear that up. Here is a link to the task 29 thread so you can learn more and decide if you want to do it or not.
Click to expand...
Click to collapse
Yes, that's a useful tool, but I'm afraid that I might damage the existing rom and will not be able to flash it agian. Also it requires to flash HSPL before which also potentially might brick the device ( I mean the flashing process).
sike222 said:
had this issue and indeed it was the motherboard so i had to send it back to htc.
good luck.
Click to expand...
Click to collapse
So it was a factory defect, wasn't it?
If I did something wrong during the stock rom flashing process, could be the reason of the problem?
Thank you.
After reading forums it seems to me that the issue appears mostly for T-Mobile US version..
If it is a hardware problem, does anybody know what part of hardware is damaged?
Thanks!
Looking for some advise and guidance.
Flashed ROM Virtuous Fusion MT4G v1.0.2
Everything was working fine. With some of the great responses I've seen from the leaked radio 26.09.04.26, decided to test and take it for a spin.
No problems during the radio update. I'm now struggling to get any sort of data. It shows full bars of 3G and H (H majority of the time). However, just about anything that requires syncing or a data connection is failing.
Rolled back to radio 26.03.02.26 and have the same issue as the .26 radio. Also tried radio 26.08.04.30 with the same results. Tried fixing permission and still nothing. Wondering if I'm missing something or if I'm f-ed?
Have you tried another fresh flash or factory reset? Other than that don't know what else to tell you. I haven't messed with the radio due to reading some have encountered your same issue.
Okay so I am currently on MPH24.49-18 and all my stuff is working okay.
However, whenever I try and upgrade my ROM I can never get my cellular radio to work. I tried using TWRP to update the ROM MPH24.107-58-1 located here http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
Every time I do though the initial activation always fails and then when I try and go to the cellular settings it gives me the error com.android.phone has stopped working. I tried clearing data and cache of the phone app but that did not work. I also tried flashing a different modem but that has also failed. The ROM I am trying to flash should already come with the modem I need baked in so I don't think it's that.
I did manage to succesfully get my phone activated with Pure Nexus ROM but I didn't like the lack of Moto features. I would just try TruePureX but that one always hangs at "Extracting System" when installing. If I could even get that working then I might be okay.
Does anybody have a suggestion? Any help is much appreciated.
Thanks
wildwill2002 said:
Okay so I am currently on MPH24.49-18 and all my stuff is working okay.
However, whenever I try and upgrade my ROM I can never get my cellular radio to work. I tried using TWRP to update the ROM MPH24.107-58-1 located here http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
Every time I do though the initial activation always fails and then when I try and go to the cellular settings it gives me the error com.android.phone has stopped working. I tried clearing data and cache of the phone app but that did not work. I also tried flashing a different modem but that has also failed. The ROM I am trying to flash should already come with the modem I need baked in so I don't think it's that.
I did manage to succesfully get my phone activated with Pure Nexus ROM but I didn't like the lack of Moto features. I would just try TruePureX but that one always hangs at "Extracting System" when installing. If I could even get that working then I might be okay.
Does anybody have a suggestion? Any help is much appreciated.
Thanks
Click to expand...
Click to collapse
AICP 7.0 has been great on my Sprint phone.