Hello all, I bought a Titan off eBay to replace my trusty Apache (I'm with Verizon), and have flashed some self-cooked ROMs to it. I'm not too familiar with the ins and outs of flashing, but I've followed a few tutorials and it seems pretty straightforward with PPCKitchen. But the problem is, neither the ringer or camera work in any of the roms I've tried! I've even used several already-made ROMs.
I know both worked when I got the phone, so it must be something that I ****ed up. When I do a test call to my phone, I don't hear any ring (tried setting it to vibrate, doesn't vibrate either) but it does vibrate afterward letting me know I have a missed call. When I load up the camera application, all I get is a black screen instead of live camera feed. When I try to take a photo, I get the error "Unable to capture photo. Unable to get frame data from camera device."
Have I bricked my phone functions somehow or can this be fixed? Big thanks to anyone who can help a confused guy out
Ok well after a long ordeal and needing to get a new MicroSD card (Kingston cards dont work for flashing for whatever reason) getting the latest radio fixed everything.
Also I may have posted in the wrong sub-board (probably should have gone in the Titan upgrading etc. board) and I apologize for that.
Hey guys! I am on the new side myself. I flashed a rom and did not have the camera working either... sooo, I flashed another rom and my phone resets over and over and over (oh my god, and over and over!)..... I flashed the first cooked rom again and still my phone just keeps rebooting....... any ideas? I'm wondering if going back to the WM 6.1 would help........
yvettejudd said:
Hey guys! I am on the new side myself. I flashed a rom and did not have the camera working either... sooo, I flashed another rom and my phone resets over and over and over (oh my god, and over and over!)..... I flashed the first cooked rom again and still my phone just keeps rebooting....... any ideas? I'm wondering if going back to the WM 6.1 would help........
Click to expand...
Click to collapse
Are your OS ROM and Radio ROM compatible with each other? Maybe the flash screwed up (try again)? Perhaps the ROM you used was for the wrong device?
Related
Help Rom Flash Issue
--------------------------------------------------------------------------------
I had an issue with my GPS, trying to turn static navigation off. I thought I screwed it up so I reflashed the original O2 rom, worked no problem.
However after trying out the posted ROM's on here I like the Vanilla which is what I installed (then was messing with gps). Went back to original with the hope that the gps was fixed.
I then just tried to put the Vanilla 3.01 ROM back on and it fails out for corrupted ROM file ERROR 270.
To let everyone know, I installed, and unistalled both the full, lite, and vanilla several times the other day while deciding which I liked.
WHat could the problem be about I can't get any of these ROM's to flash now all after 3% the screen goes dim, and it says corrupted file.
ANY SUGGESTIONS?????????????
Switched computers ......
I found a thread after some serious searching about switching computers when you get an error 270 image corrupt...
Then after flashing original rom, uspl seems to have worked..
will update if thread if I get vanilla rom back on.
I have the Vanilla 3.01 ROM installed!!! I think it's great.
There are two things that I want to change, and need help.
One I actually did not mind the origianl phone dialer that came with the WM6 O2 ROM. Is there a way to just port that part back in ???
The function I liked was when I typed numbers it would choose contacts based on number. The Vanilla version choses contacts based on the letters.. Can I change??
Also is there another way to make the keyboard bigger, after selecting big font, I mean just a tad bit larger??
Thanks,
Burn
My phone has to be restarted about every other day. Stuff just starts disappearing off the home screen and taking forever to do anything. Would an upgrade to 6.1 help this?
Are you on a stock Rom?
Since an upgrade will install a brand new Radio and Rom... Yes, it should help this. (so might a hard reset) However if your issue is Hardware( doesn't sound like it) or some poorly written app you have installed (could be) then the upgrade wont help unless you replace the hardware, or dont install the bad app.
So.. Yeah go for it.. It should help. If you havent flashed before.. READ the instructions so you can avoid major headaches or a bricked phone.
My Stock Verizon Phone locked up often... (once or twice a day)
Upgraded with DCDs most excellent Rom, Now my phone is solid.
I am having some trouble getting the camera working on a mytouch3g I have been working on. I have Engineering SPL 1.33.2004 installed with CM-recovery 1.4 installed. Have tried several 32B roms but always get a force close. Have wiped, restored nandroid backup, used clean sd, and even tried pushing the stock camera and 3rd party camera apps. Is there something I'm missing? I have rooted a few Dreams, but this is the first Sapphire I have dealt with. Any suggestions?
try flashing the stock mytouch rom. its on here some where. if that works then just try a cyanogen rom. i refer the 4.0.4 rom. if this works then you had corrupt files on dl. if this is the case then try using a dif os. if continues then your sd and or file reader is trying to filter content. so use something else. let me know. rockin...
Thanks for the reply. I have tried cm 4.0.4 as well as several of the 32B roms from the Sapphire board. In fact 4.0.4 is what I flashed it to as soon as I finished the rooting process the first time. The camera worked fine that night, but has since crapped out. None combo of roms/spl/radio seem to do any good. Even wiped, and unrooted w/ sappimg.nbh and started over a time or two. Then I read earlier someone on the Dream board had a similar problem, and fixed it by re-formatting SD. So I gave that a shot (even used a different SD that is known to work fine) but still no luck.
So now I have put the phone back to stock. I figured since every partition we change by rooting has been wiped and rewirtten to it's original state, it's best to just call it a hardware issue & have t-mo swap it out. I don't see anyone else having these kind of issues on here. So I'm thinking this phone must have met the floor somewhere between the time I flashed it and the time camera issues started. Nothing else can seem to explain it. Hopefully I'll have better luck with the next one.
gurnted said:
Thanks for the reply. I have tried cm 4.0.4 as well as several of the 32B roms from the Sapphire board. In fact 4.0.4 is what I flashed it to as soon as I finished the rooting process the first time. The camera worked fine that night, but has since crapped out. None combo of roms/spl/radio seem to do any good. Even wiped, and unrooted w/ sappimg.nbh and started over a time or two. Then I read earlier someone on the Dream board had a similar problem, and fixed it by re-formatting SD. So I gave that a shot (even used a different SD that is known to work fine) but still no luck.
So now I have put the phone back to stock. I figured since every partition we change by rooting has been wiped and rewirtten to it's original state, it's best to just call it a hardware issue & have t-mo swap it out. I don't see anyone else having these kind of issues on here. So I'm thinking this phone must have met the floor somewhere between the time I flashed it and the time camera issues started. Nothing else can seem to explain it. Hopefully I'll have better luck with the next one.
Click to expand...
Click to collapse
Hate to say bro, but ya has to be hardware. Everyone has messed with cam software and had success. So you have done right and reverted to stock. Send that bad boy back and get a newer exchange. Sadly to say my orig. spl was broke and had to send back. I tried talkin tmobile service techs thru the steps but they only were like "ahhhh ummm" lol. do the dew and get a newer hardware softer g2. fosho. . . . .
Yeah that's what I figured. At least the folks at t-mobile didn't give much hassle. It was within the 14 days so they were pretty quick to agree to the swap out. New one will be here next week, and I'll give it another go. Thanks for the help.
camera force close
hey great guys
i have x18i (china clone) mtk 6573 mobile. recently camera is force closing
and its flash is also not working. i tried factory reset also .... fone is rooted
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
JustinHTC said:
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
Click to expand...
Click to collapse
Sounds like a dying battery to me.
It worked fine in the original Windows though so that's why I am a bit baffled.
what happens if you put your device in bootloader and try to flash to stock? Error 262 is a connection error. basically happens whenever some event interrupts the flashing process (a dead battery will cause this). If you haven't yet, try to flash to stock via the method in this post (bootloader and then flash)
Tried that, didn't work. Just gets to 31% and pops 262 no matter how I try to do it.
The odd thing is though that I can flash any other ROM just fine.
Would reformatting the SD card work?
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
JustinHTC said:
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
Click to expand...
Click to collapse
0.41 was reportedly having tons of issues, you should have started from there
Glad you got it working.
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!