Related
I don't know why the person asking about an accelerometer failure had their thread closed after a single response suggesting banging the G1. In fact, failure of the accelerometer usually *is* a software failure, and is usually fixed with a factory reset. I just went though this on my unit two days ago!
I just did a wipe yesterday to rid that same issue.
I am not so fortunate. My accel and compass sensors have remained non-working despite several wipes and re-flashes. Here is my thread, if anyone has any ideas for me.
http://forum.xda-developers.com/showthread.php?t=533749
And yes, the hardware is fine, as they both work great in pre-cupcake firmwares (RC29 and RC33), but not at all in any (ADP, JF 1.51, Cyan's mod, etc) cupcake build.
Any help is appreciated!
way to fix without wipe?
well is there? i dont feel like wiping and then reseting my settings from b4. the issue just happened when u updated to cyraogen 3.6.8.1 with the help of the download like from the kspec kustom threAD to get the rom update, theme, and htc music in one flash.
Fixed it! (All by my self....... kinda)
pistol4413 said:
well is there? i dont feel like wiping and then reseting my settings from b4. the issue just happened when u updated to cyraogen 3.6.8.1 with the help of the download like from the kspec kustom threAD to get the rom update, theme, and htc music in one flash.
Click to expand...
Click to collapse
I should have searched his thread.... ran the script in the fq to fiv my issues.
During an update, (PASSIMG.zip) in hboot I selected yes (to install) then about a second later, my screen
turned black and now, the only thing I can do is to boot in the installed stock rom (FRG33).
My english is not perfect, i'm sorry for that.
1. I Removed my battery after a while. (about 10 minutes)
2. Inserted the battery back in his place
3. Power down + vol down and I'm stock, I can navigate in
the menu but I can't see anything...
Anyone know how I can get my screen back ? OLED vs SLCD ?
Note: I can boot in my rom, the rom is unrooted, my phone is unlocked.
(And yes, I tried to flash recovery and another rom without success. And I can't
find a way to flash hboot again (bad signature)
I'm using the last version of hboot and radio.
If anyone have an idea of how I can fix this, this will be really appreciated.
Thanks.
I'm starting to think than my /dev/mtd/mtd0 is screwed up.
Anyone know where I can get/or generate a image of a normal mtd0 ?
At the moment I'm running debian sid dand SuperOneClick seem to freeze
after trying to chmod rageagainstthecage or psneu..
Note: Yes my screen work when the boot is completed. (but not in hboot/recovery)
bad spl ?
fblodroid
Ok, sorry for the noise, I was able to perform an update via 766a101ae02c.signed-passion-ota-60505.766a101a.zip (renamed to update.zip) and I powered off my phone.
Removed the battery to be sure there is no power at all.
and using some screenshot found on the web.
I was able to perform the update (blindly, this word exist ?) and the phone rebooted
and asked me if I want to update again (google update) I selected yes, the phone rebooted
and, VOILA, I can see again the crappy X logo with an open lock at the bottom.
Thanks again (ok for nothing, but if than can help some people...)
Yes, shame on my english again.
fblodroid
My guess is that you have an SLCD Nexus One, and the passimg installed the .33 HBOOT which doesn't work for them.
I had the same problem when flashing the MIUI-AU rom, screen went black,removed battery and replaced but the phone was dead,I was already thinking which phone to buy then when I connected the N1 to my laptop miraculously the X logo appeared and the rom launched ok
At the moment my phone is working again but I'm still having a camera issue.
About a 1 1/2 month ago I experienced this problem, no flash, no camera, just
a black screen when I try to run anything than use the camera.
Then a day, I was walking on the street and I checked to see if the flashlight was
working and obscured magic occured, the flash was working again but not the camera,
I wiped my phone again, repartitionned my SD card and installed a new rom and the
camera was back to normal.
Now, about a month later, (the problem started yesterday) i'm having the same issue.
I'm persuaded than this problem is related to a firmware problem, something related to
my /dev/mtd/mtd0 (hboot, perpaps ?) I don't know exactly where the camera firmware
is writed in the phone memory (nand)
I wiped and flashed again and again a lot of rom last night and today and the problem
still exist.
No camera/flash at all.
I'm thinking about returning the phone for warranty issue but like I said before, the
phone is unlocked... perpaps I will try to black the screen again and send the phone for
warranty... this way they cannot see (without fastboot) if the phone is locked or not.
If anyone have an idea of what I can do... a rom to recommend ?
Today I tryed to revert hboot without success...
EDIT: At the moment I'm running a rooted rom based on FRG83G.
fblodroid...
Related to my camera/flash problem:
Hum, I think I found the problem, this is hardware related, something seem to be
badly connected in the phone, I tryed too apply some force on the right border of the
phone with the flashlight ON (I previously looked on the web to see where the "contacts/plugs"
are located on the pcb (teardown pictures) and after applying some pressure, the light came ON
and now I can open and stop the "flashlight" mode.
teardown on the way ? I'm thinking about it... but i'll try to flash another rom again to see
if my camera is back.. (like in the past)
EDIT: No camera for the moment and the flashlight app light on the LED only if I select
the option "High Brightnes", ON/OFF are working with this option selected.
fblodroid
FIXED
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
http://img121.imageshack.us/i/icedqlubgg4zzbv2huge.jpg/ (in the red circles, the two pink dots)
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Hi, I have a HTC Desire GSM PVT4 (HTC__203), with the exact same issue as what is described in the original post. When I boot in hboot or recovery the screen is completely black. When I boot in the normal rom the screen works fine. I reflashed a number of RUU's successfully, but the problem remains.
The misc partition is not part of the RUU images, and I did re-flash the misc partition in an attempt to downgrade. Any idea where I can get an image for the misc partition for my device, or where I can generate one?
Thanks,
Hans
fblodroid said:
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
/link/
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Click to expand...
Click to collapse
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
soylapinta said:
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
Click to expand...
Click to collapse
Did you managed to fix it ? Be sure to check all the plugs, at best unplug everythings
and disassemble the phone entirely.
Mine is still working perfectly after two years.
fb
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!
Had this phone for about 1 week now. Everything been fine until today. I tried to take a few pictures, but I couldn't. Received an a pop up with "Cannot connect to camera" I'm not sure what's causing this issue, I cleared the data/cache on it and still occurs. Is there any solution to this issue?
Thank you.
I have exactly the same situation.. But it's weird - ported LGCamera works without errors, other apps (market or aosp based) throw error. Sometime clear app data help, but only sometimes..
It could be hardware problem?
I've had this happen when I was on an older CM11 nightly.I did have to preform a clean install to fix the problem.
xxxrichievxxx said:
I've had this happen when I was on an older CM11 nightly.I did have to preform a clean install to fix the problem.
Click to expand...
Click to collapse
18/03? It didn't helped.. I was testing old and newest ROMs - same situation I think it could be some hardware problem - currently I have version from Singapore build at 02/2014
EDIT#1
Weird.. I will go back to stock - test, then install custom ROM.. Something go wrong - when I'm using ported LGCamera.apk in CM/Slim/PA it's working, other camera apps - don't..
I guess I found out the issue of why it was being caused. I also have a Nexus 5 and both had the APP Flashlight by Go Launcher. Seems to me when I downloaded and used it couple of times it caused my camera not to work on both phone. Uninstalled it and now it's working fine with now issues. I'm not sure if you guys also have a flashlight app, but maybe you can give it a try.
I got a replacement g2 from my insuarance and from the box mine done the same thing i tried every app i could find one day i flashed a diffrent rom and was bored. Clicked on my cam and it worked went back to my stock backup for my updatez and it wouldnt connect found out its was a software isse broken software from the factory i put a new stock rooted rom on and good as new. Mine was down. For about a month whrn i notticex what was wrong i thouvht i had a hardware failure but it wasnt there is always a chance of a bad cam but also some app like certain flashlights do take over your hardware if uve rooted and the phone is new goback stock unroot and have swapped
I'm on stock KK right now = 0 problems, so I think it's not hardware. LG camera and other apps always working fine.
Now I will go back to AOSP and test apps again
zg85 said:
I'm on stock KK right now = 0 problems, so I think it's not hardware. LG camera and other apps always working fine.
Now I will go back to AOSP and test apps again
Click to expand...
Click to collapse
Hello,
Did you go back to aosp ? Is the camera ok now ?
Thanks
Here's a thought. After a new rom anybody feel there is a dial pad code to bridge the connection gap.
help, question
TheMadScientist420 said:
I got a replacement g2 from my insuarance and from the box mine done the same thing i tried every app i could find one day i flashed a diffrent rom and was bored. Clicked on my cam and it worked went back to my stock backup for my updatez and it wouldnt connect found out its was a software isse broken software from the factory i put a new stock rooted rom on and good as new. Mine was down. For about a month whrn i notticex what was wrong i thouvht i had a hardware failure but it wasnt there is always a chance of a bad cam but also some app like certain flashlights do take over your hardware if uve rooted and the phone is new goback stock unroot and have swapped
Click to expand...
Click to collapse
hardware if uve rooted and the phone is new goback stock unroot and have swapped[/QUOTE]
hey, i also got a replacement phone via assurant insurance. can u dumb it down, what exactly did you do to get the camera working back again?... ROM?... i dont really have any apps for the camera, only whatsapp...
ill be waiting for your answer, thanks
THANKS，I got the same problem and after I deleted the Go Flashlight the camera worked again!
Same issue. Go flashlight solved thanks to this thread.
Having similar issue. Flashed a new bootstack and camera stopped working. Factory reset, fresh install tot, then kdz, then cloudy g3. Camera still force closes and other camera apps can't connect. I can take one picture after a fresh install (which I did three times flashing from tot...).
Camera not working
reeper250 said:
Having similar issue. Flashed a new bootstack and camera stopped working. Factory reset, fresh install tot, then kdz, then cloudy g3. Camera still force closes and other camera apps can't connect. I can take one picture after a fresh install (which I did three times flashing from tot...).
Click to expand...
Click to collapse
hi i have also the same problem.. have you any solution ??
umair_hashmi said:
hi i have also the same problem.. have you any solution ??
Click to expand...
Click to collapse
Nothing worked. Just gave away the phone and bought an LG G3
Hi, I never root my phone or flash a custom ROM.
The problems was started when I flashed a new ROM from sammobile of another country, my phone comes with 4.2 and I flashed a 4.3.
I flashed newer ROM from only Vodafone-Spain (only those really are my official supplier), and then I update ever with Samsung KIES, (no Knox counter)
So, with Andorid 4.3 I had more problems than now with 4.4, now the only problem is with WIFI
I can use normally, with screen ON, the problem is when sleep for a long time (more than 1 hour) when I touch a button I see the unlock screen, but does not seem to work the touch screen, and screen go off after a seconds, if I touch other button the screen don't go on. And then, after aprox 30s it reboot itself, and show a window telling that the Process System is not responding, do you want to close?, and two buttons, close or wait.
I tried to start my phone in Secure Mode and I have the same problem, so it is not an app, it is the ROM.
I do at least 2 Factory Reset, but the problem is still there.
I think it is a software problem and not a hardware problem, because the problem start when I update to Android 4.3
I tried the trick WIFI Power save Mode OFF (on dialer, *#0011# -> WIFI -> Power save mode OFF) and never reboot automatically, so the problem I think it is with this power save mode. But if I turn off, when WIFI is ON, the battery drain fast.
In the samsung shop they tell me that first will format my phone to see if the problem solve and try for a time, if not solve, then I have to send by mail... and I will not send it because I know the time it will take to repair it is about 1-2 months and I need the phone for my work.
So is there another solution or something to try?
Napalm Candy said:
So is there another solution or something to try?
Click to expand...
Click to collapse
Try reflashing the Firmware once again mate and Here you can follow the tutorial from here
Repulsa said:
Try reflashing the Firmware once again mate and Here you can follow the tutorial from here
Click to expand...
Click to collapse
Since the first ROM (4.2) I flashed 3 or 4 ROMs from SamMobile, so I am not very optimistic. But I don't lost nothing, I will try it
I flash again the ROM, and after 2 days testing, the problem is still there.
Any other thing to try before send to samsung?
Please, give me another idea to try. I really have a problem with WIFI
This is how Wifi (some times) drain my battery when are not connected to a network. But the problem is worst when is connected, because it freeze and reboot.
Hello! You could fix the problem? I took suffering the same problem as your months, and I have not been solved, I'm for kicking the **** mobile! As may give so many problems with the wifi?
regards
manguila said:
Hello! You could fix the problem? I took suffering the same problem as your months, and I have not been solved, I'm for kicking the **** mobile! As may give so many problems with the wifi?
regards
Click to expand...
Click to collapse
Yes I solve. So.. I don't solve it, it solve it self. One day I saw that I don't had wifi connection, then I saw that I don't any WIFI names stored, all was erased automatically, I don't know how.
But the result it, I don't have anymore a freeze or a reboot because wifi. ALL, absolute ALL run fine now. I had a lot of WIFI names stored, about 30-50, maybe this was the problem, a conflict with some of these names, but I'm not sure
No one update, reflash, factory reset, or start in safe mode was solve any problem, the problem solve it self... very strange.
If you try a factory reset, then don't restore all your mobile config. Try to install all apps manually, one by one. I ever restored my backuped config, and I think this was the problem.
Hope you can solve it
Napalm Candy said:
Yes I solve. So.. I don't solve it, it solve it self. One day I saw that I don't had wifi connection, then I saw that I don't any WIFI names stored, all was erased automatically, I don't know how.
But the result it, I don't have anymore a freeze or a reboot because wifi. ALL, absolute ALL run fine now. I had a lot of WIFI names stored, about 30-50, maybe this was the problem, a conflict with some of these names, but I'm not sure
No one update, reflash, factory reset, or start in safe mode was solve any problem, the problem solve it self... very strange.
If you try a factory reset, then don't restore all your mobile config. Try to install all apps manually, one by one. I ever restored my backuped config, and I think this was the problem.
Hope you can solve it
Click to expand...
Click to collapse
Thank you very much for answering so quickly.
Happens to me exactly what you do, but seems to have no solution.
I have tried more than 8 roms, stock or mods, and always fails.
At first I thought it would issue the modem or kernel, but after many tests, I do not ****ing know what is causing the problem.
I'm running out of solutions, anyway thanks for telling your case...
I'm glad that in the end one way or another, you have it fixed.
:good:
manguila said:
Thank you very much for answering so quickly.
Happens to me exactly what you do, but seems to have no solution.
I have tried more than 8 roms, stock or mods, and always fails.
At first I thought it would issue the modem or kernel, but after many tests, I do not ****ing know what is causing the problem.
I'm running out of solutions, anyway thanks for telling your case...
I'm glad that in the end one way or another, you have it fixed.
:good:
Click to expand...
Click to collapse
What happens when you fully wipe, flash a 4.4.2 rom, don't restore anything, not even your google account and don't install any apps.
Lennyz1988 said:
What happens when you fully wipe, flash a 4.4.2 rom, don't restore anything, not even your google account and don't install any apps.
Click to expand...
Click to collapse
Thanks for your interest! The truth is that it is very strange ...
If I remember correctly, already try what you mention me, but I kept going ... It's like at some point something had happened which change roms not seem to solve..
I'm considering installing a rom with 4 files and pit file, but do not know if this will help in something
Let's see if I can come up with the bug because it is becoming a pain in the ass
:good:
I would try what say Lenny1988. So the only change before solution and after solution, was a big crash on WIFi drivers/app/modem (don't sure) it self, and was deleted all my stored wifi access points that I had. It was a problem related to Wifi power save, if I disabled it then I had no reboots/freezes.
So, I would try a factory wipe and DON'T restore anything, and try for a couple days. If work, then you know a way to solve it.
Tell us if it works.
Hello there! I will update with the latest news!
I tried the recommended advice, but no luck...Not seem to affect him leave without restoring.
The only thing that seems to work and keep it running, is to disable wifi power saving system
you know....
Code:
1. Go to your phone dialer
2. Dial *#0011#
3. When you see the "ServiceMode" screen, press the left menu button
4. Select "WiFi"
5. See that "Wifi Power Save Mode" button that is "ON" - well turn it "OFF"
But this way drain your battery much faster,so it does not seem a good solution to the problem.
Curiously, the same phone, some people suffer this problem and others do not....
It may be hardware? or software?
If I find something, I'll note here.
Regards