Hey guys,
I have an unrooted HTC Desire that seems to have developed the dreaded motherboard issue.
Im trying to unroot in order to send it back in, but whenever I try installing an RUU (downloaded from shipped-roms.com) the Installshield gives me an error "-5001 : 0x80070002"
I can't seem to find out whats causing this error, but any help would be appreciated.
For what its worth, I'm running an MIUI ROM.
Downloaded another file and it worked. Unrooted and everything is working fine.
I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
robertlewisca said:
I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
Click to expand...
Click to collapse
I was having the same exact problem. I even changed phones thru warranty. The new phone did the same thing. New SIM card didn't help. I had a guy at tech support to push the update to me.
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
IDK, co-worker with a Skyrocket has had the same issue, but he doesn't care about the update, so he hasn't bothered to get it resolved.
If I didn't have a red GS3, I could goof around and tell you that is what the problem is...
Actually, if it were me having the issue, I'd walk into AT&T and have their guys mess around with it. No telling why some have more issues than others.
robertlewisca said:
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
Click to expand...
Click to collapse
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Not really a solution but you could install this http://forum.xda-developers.com/showthread.php?t=1902178 to be fully stock LH9 with Root. Or use the OTA zip from here http://forum.xda-developers.com/showthread.php?t=1896773.
aboveusonlysky said:
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Click to expand...
Click to collapse
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
78c10 said:
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
Click to expand...
Click to collapse
You mention in your signature that your phone is rooted. So, did you update OTA then root, or did you update after rooting through some other method? The challenge some of us are having is that we are not rooted, and cannot update OTA because of the 'server error' it gives us everytime we try.
Problem Solved - for me at least
Well, the problem is solved for me, and I thought I would share what I found out here in hopes it helps someone else.
First, I had the phone replaced under warranty. It appears to be a brand new phone. When I received the new phone, I started it up, went through the normal startup stuff - entered my Google account information, it backed up my info and settings. Before I loaded any apps, I went straight to the update screen, and tried to check for an update. I again got the 'communication failed' error. Bummer.
So, then, I did a factory reset on the new phone, but this time instead of entering the initial Google account info on the startup screens, I skipped through all of the initial screens, got to the home screen, then went straight to the update screen - and this time it worked! So, it must be something to do with the initial screens, and entering Google account information that caused the problem.
Then, I got to thinking - perhaps this might work on my old phone too. Since I just got the warranty phone today, I still had my old phone (which needs to be sent back). So, I did a factory reset on it, skipped all of the initial screens where it asks for Google account information, and it still didn't work on the old phone. So, I'm not sure what the original issue was.
By the way, after the update installed on the new phone, and I went through and entered all of the Google account settings, and then checked for the update again, and there was no error.
So, perhaps this might be helpful for others?
Hey,
I'm new to writing in the forum but have been viewing topics for quite some time.
In the past week I had my HTC One X crashing on me with 'com.google.process.gapps' / 'Android.process.acore' has stopped unexpectedly causign all the apps not to work.
I'm running Jelly beans (4.1.1) with Sense 4+.
I browsed the forums for a while and saw suggestions to cancel google internet sync and to clear to contacts cache.
I did both and after it did not help I tried factory reset and recovery boot.
Although things run a bit better i'm still encountering these errors every now and then (and I have to hard boot the device).
Any suggestions how to resolve this issue ? Could it be a hardware malfunction ?
Would love to hear any thoughts on the matter.
full wipe and reflash could solve the problem, or maybe you downloaded a corrupted zip but the ROM still managed to flash - happened to me before.
My phone is not rooted and does not use a custom ROM so I don't think a corrupted zip is the issue. Should I root it just for reflashing it ?
I've been having problems with the phone giving an error message saying that the SIM card was removed and then immediately it is recognized and the phone is restarted automatically to start using the network. It has been happening on full stock ROM (old and new versions), rooted and unrooted, locked and unlocked bootloader (FreeGee) and on custom ROMs. I've had the SIM card replaced multiple times without helping. I can't remember back to when it first started, but it started again after getting the phone back from repair (all they did was a software update, but that's another story) I have the issue until I reinstalled Cerberus and Tasker. Upon uninstall of both apps, I haven't had the issue for the last 5 days. Anyone else have issue with either of these apps on an E973 (Bell)? Is it even possible that they could be causing this issue or is the timing just a coincidence? I'll try adding the apps back one at a time and see if I can get the problem to start again with either one.
Sorry about the wrong thread, I could have sworn I was in Q&A when I posted. If anyone wants to move it that would be appreciated.
mike1767 said:
I've been having problems with the phone giving an error message saying that the SIM card was removed and then immediately it is recognized and the phone is restarted automatically to start using the network. It has been happening on full stock ROM (old and new versions), rooted and unrooted, locked and unlocked bootloader (FreeGee) and on custom ROMs. I've had the SIM card replaced multiple times without helping. I can't remember back to when it first started, but it started again after getting the phone back from repair (all they did was a software update, but that's another story) I have the issue until I reinstalled Cerberus and Tasker. Upon uninstall of both apps, I haven't had the issue for the last 5 days. Anyone else have issue with either of these apps on an E973 (Bell)? Is it even possible that they could be causing this issue or is the timing just a coincidence? I'll try adding the apps back one at a time and see if I can get the problem to start again with either one.
Sorry about the wrong thread, I could have sworn I was in Q&A when I posted. If anyone wants to move it that would be appreciated.
Click to expand...
Click to collapse
Anyone have solution for this issue ?
Hello, I have a 64 GB HTC One M9u, S-OFF with CID: HTC__001.
EDIT:
It seems that even after my sd card flash the phone still does reboot randomly (perhaps I am being silly and we can say that it is crashing), I just had it occour to me after using it for a while. I have no idea why this persists, maybe it's a faulty battery instead? I was unable to change the title, but decided to keep the thread. Any help about this behaviour is greatly appreciated.
When I was reverting to stock, here is what I did:
1. I used ARUWizard to flash 0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.12_Radio_01.01_U11440792_97.00.51203G_F_release_signed.zip
2. Then I did a OTA upgrade to latest 3.* firmware
3. after that I got a OTA to latest 4.* firmware
What happened then was that my device kept rebooting/crashing constantly even with the smallest of things happening like when I tried to setup the Play-account or used the music app, this occoured as weird to me.
There is only some quirks I noticed that seems odd:
The HTC Sense menus did not come in black with blue icons if activates as they did in normal stock, but they were instead black with red if activated, which seems suspicious. The background came out as hills one with the blue skies, while the one that was supposed to be there is the blue one with the yellow arrow (>)
So far I have proceeded to install RUU again, I did this by using the sd card method (since 4.* supports exFAT) I first put 0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.28.401.3_Radio_01.01_U114401011_117.00.61117G_2_F_release_498151_signed_2.zip on the sdcard, then after this was flashed I did another HTC update (maybe just some HTC apps update) I am now on 4.28.401.3 CL869604.
I want to know if possibly there is a corruption on my phone that causes the phone to crash and to crash and rebootconstantly for no apparent reason? The crash can be me just watching a YouTube video and nothing more.
I also want to check if the eMMC or the RAM is working as they should, because perhaps this mistake happened due to the eMMC corruption, but I do not know how this can be done with Android, if you know how please tell me
Here is an update to whom it may be of interest. I bought this device S-Off with a custom ROM used, so I am considering giving it back to this person for being faulty.
But then here is something interesting, it appears it has been modified from Asian firmware to EU firmware, when I checked the IMEI online I got the following information: DEF00,w/o SIM Lock,HIMA#UHL_64G-C9#ASIA
It appears it is set to HTC__001 incorrectly, any ideas for what will be the corred CID and/or firmware for the smartphone? Maybe the incorrect firmware is causing this crash, and a fix will be just to revert to the Asian firmware.