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
Related
i just got another hd2 which worked fine but after i hspl'd it n flashed a rom i lost my weather and gps location. ive changed settings w no luck. so i went back to a stock 2.10 rom and still have no weather and i still cant get my gps location.
if anyone has any ideas im lost at this point.
worst case i have insurance so ill get another new phone but id like to try fixing it.
thanks for the look and ideas..
Did you try a hard reset? That should bring it back for sure.
tried hard reset, wipe device, format sd card, no sd card, even a different sim card and still nothing. i flashed an energy rom which i like n i have flashed to many other hd2's without any issues at all but for whatever reason this one is giving me a hard way to go.
You did update your QuickGPS info after flashing to the different ROM(s), correct? Other than that, are you still using the same radio as you originially were or did you change that when you changed ROM's?
it's a known sense issue, moves from state to state....usually happens when tmobile is updating to hspa+..it'll come back, just give it time .
sirphunkee said:
You did update your QuickGPS info after flashing to the different ROM(s), correct? Other than that, are you still using the same radio as you originially were or did you change that when you changed ROM's?
Click to expand...
Click to collapse
did the update tried everything i can think to do w no results and i am using the original radio. ive never had this problem w any other hd2 ive flashed thats why im curious if ive got a defective phone or if something went wrong when i hspl'd everything else works just like it should.
see post #5.
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.
Hi
Sorry if this has been cleared up in another thread, but I cannot find the answer to this problem.
I am running Gingerbread 2.3 (Cynogen) on my phone via the file manager method. Everything was fine until one day after I booted back into Android after a normal soft reset - The keyboard would keep hitting "Q" no matter what I pressed. I could not open The browser as I would get an error message.
I thought maybe it was the extended battery I was using, so I reformatted my sd card, re booted gingerbread and everything was back to normal.
Then last week it happened again. I dont remember installing anything new. It is also not the build Im sure, because this did happen a while ago on another Cynogen mod I used.
I am pulling my hair out wondering what to do. There is no point in reinstalling it because it will happen at a seemingly random time again.
Does anyone have any clue or suggestions on how to fix this??
Thanks
Frosty1148 said:
Hi
Sorry if this has been cleared up in another thread, but I cannot find the answer to this problem.
I am running Gingerbread 2.3 (Cynogen) on my phone via the file manager method. Everything was fine until one day after I booted back into Android after a normal soft reset - The keyboard would keep hitting "Q" no matter what I pressed. I could not open The browser as I would get an error message.
I thought maybe it was the extended battery I was using, so I reformatted my sd card, re booted gingerbread and everything was back to normal.
Then last week it happened again. I dont remember installing anything new. It is also not the build Im sure, because this did happen a while ago on another Cynogen mod I used.
I am pulling my hair out wondering what to do. There is no point in reinstalling it because it will happen at a seemingly random time again.
Does anyone have any clue or suggestions on how to fix this??
Thanks
Click to expand...
Click to collapse
Maybe it's a bug in the ROM
Try different rom and see if this problem still persists, if yes, maybe a hardware problem related issue
Cheers
There are a few roms with 100% support for the official extended batteries(s). Your best bet is to go with one of them.
Sent from my HD2 using XDA App
So when I first rooted my phone I put Fresh on there. I installed the ROM and the 2 radio files. I then got the 3d and gave the evo to my gf, but fresh was very slow for me so I installed the CM7 ROM.
CM7 was very buggy for her, especially since she was new to Android I decided Sprint Lover's ROM on there and flashed a newer update on it since.
The problem is that she has been having problems with 3g. She has so many problems and errors with 3g data. It shows that she has 3g, but she gets errors when she tries to access the internet.
My question is, how can I get it back to stock or a nice rooted stock rom to try and fix this problem? Do I just flash a stock rom? I'm guessing the fresh radio's might be messing something up. If there is a simple solution to this without having to do a full erase I'm sure she prefers that, being that we've fully erased her phone like 4 times already, lol.
Thanks guys.
Get the Sprint Lovers all-in-one package from here: http://forum.xda-developers.com/showthread.php?t=830153
It's flashed through hboot (it's a PC36IMG.zip) and will flash not just the rom but also the radios. This will wipe everything.
Alternately you can go here http://forum.xda-developers.com/showthread.php?t=715485 and get just the latest radios and flash those. Flashing this will not wipe everything.
If the problem is with the radios then that should fix it. If it doesn't, then it's likely that the issue lies somewhere else.
thanks, just installed the new radio's. Will see how it works.
I would definitely just get the app mybackup root and back everything up apps/data , sms etc.. Then just restore everything after you flash a new ROM.
Then just do a fresh install of what ever ROM you want then test out different radios till you find the best ones that work for you I'm on old radios because the newer ones didn't work great for me not all evos work the same .
I hope that helps you out some.
Sent from my PC36100 using XDA App
I got simalar problem like u.
I installed new radios, try different roms like MIUI, CM6, CM7, Miks, Minn, OMJ's, etc...... finally I go back to stock rom but still got the same problem.
I almost crazyy
the phone never got 3G signal, it only works 1G no matter what I did.
I've reserched couple days but looks like nobody got my problem.
now I fixed my problem btw... well I'm not sure this thing works to u or not
anyway try it if u still got 3G problem.
*I don't even remember where this posted originally,,, somewhere this forum or not,,
huge thanks to original author btw
download 'MSL reader' at market n get the numbers. it's 6 digits.
go to your phone and type ##3282#
tap 'edit mode'
type that 6 digits from MSL reader
tap 'data profile'
open menu n tap 'restore'
then the phone will be reboot.
when booting is done, your phone will start resistering to network.
after that, if something popup n ask update (mayb PRL update), 'cancel' it.
mine works perfectly now.
hope this work to u.
ok thanks, i'll try it out. I do get "3g" at the top though, but always get an error while trying to retrieve data.
Also, what files in the SD card are necessary? Is there a list? I think there are so many junk files in there taking up space, I don't know whats necessary and whats not.
Please help slow EVO 4G after flashing Sprint Lovers All In One
Obvious Noob here.
having issues with my Evo 4G after flashing Sprint Lovers All in one
phone seemed very fast immediatly after flashing SL but since then has become just overall slow.
in fact, i'm downloading an update to ROM Manager right now (a 2.27MB file) and it's taken literally 20 minutes to get to 75%. it's painful!
when i go in to manage applications...says "computing" on space, data and cache etc.
before i flashed SL all in one i ran factory reset 3x in a row prior to flashing - i did NOT re-format my SD card but had it removed (after unmounting).
Should i try to wipe and re-flash or just go to CM7? Are there any things i can try before re-flashing or moving to another rom? Please help..
thank you OB1B
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
TommyQuid said:
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
Click to expand...
Click to collapse
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
kanesglove said:
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
Click to expand...
Click to collapse
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
kanesglove said:
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
Click to expand...
Click to collapse
you guys offer little information at all so this is why no one helps you. Maybe tell what firmware version you flashed what root version you did etc. There is a big difference between bootloader revB/11 and the others
Holy ****. Did I just get constructive suggestions from jrkruse?! Dude if you told me I could fix my phone by sucking a fart out of a wallaby's ass I'd do it cuz the advice came from you, and if there's one thing I know it's that you know your ****. You're ****in' awesome. I feel so special now. Ok sorry about that...
Well, I'm not too sure about the OP but I can tell you about the phone I have that seems to have the same issue.
My S7 Edge is a SM-G935V on android 7.0 on update 4BQK2. Prior to rooting I put everything to stock then I did a NAND erase and repartition. No issues with any of that.
I rooted my phone from this post
G935V Root Method. No Lag! No Heat!
G935V Root Method. No Lag! No Heat!
I AM NOT RESPONSIBLE FOR ANY OF YOUR ISSUES! ALL I CAN DO IS RECOMMEND A GOOD PSYCHOLOGIST! Hey guys. Stumbled on this by accident. I HAVE ABSOLUTELY NO IDEA WHY IT WORKS, BUT IT DOES. THE METHOD HAS BEEN TESTED BY ME AND A FEW OTHER PEOPLE HERE...
forum.xda-developers.com
which directs to your older method for gaining root privileges.
[DISCONTINUED] ROOT Method For Nougat
DISCONTINUED New Thread Found Here This Root Method For S7 Nougat Nougat_S7_Root_2_82_All_Carriers_V2.zip Includes Fingerprint Fix [Latest Verison] Nougat_S7_Root_2_81_All_Carriers_V2.zip Includes Fingerprint Fix Nougat_S7_Root_2_79_All.zip...
forum.xda-developers.com
I also flashed Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.
Then I flashed the BL file in the BL slot from the G935U firmware with odin checking "Phone Bootloader Update". I used the BL file from G935UUES4BRA1 since it's the closest update for the U brand to the firmware this phone is on (G935VVRU4BQK2)
I'm aware that there are newer methods for gaining root access but I chose this method cuz I used it back in 2017-2018, I had read all the posts in the thread, and I knew it worked.
I currently have 3 S7 Edge phones all on the same firmware and build and are all rooted with the same combo method I just explained. The other 2 phones also have xposed installed and they both work well.. expect mine says weird stuff instead of the callers information. I think it only does it if they're a contact but in the notification tab it says an example like this 5556661234;verstat=No-TN-Validation. No clue how to fix that.
The phone that is having the same issue as the OP still had access to the private/secure folder when it was rooted; which I thought was weird cuz mine doesn't and from what I understood private mode gets disabled if the phone's rooted. Maybe it only gets disabled if you install xposed? I don't know. My son had the phone with the issue and it was his first smart phone and he dropped it a few times (with a case) so I was thinking it's an effect from something he downloaded from the play store (he's 20 now but pretty still very ignorant with android). Now I'm not sure if it's a software or hardware issue since the problem persisted after the NAND erase.
Something to note about my sons old phone also is that it has 2 thin pink lines running down one side of the screen (defective/dead pixels) and when the screen turns off it it flashes once before actually turning off. One time over the phone I tried troubleshooting the issue with him and he ended up being able to use his camera immediately after rebooting the phone though once he exited the camera app it wouldn't open again. We were trying a bunch of things, force closing any app I thought would be related to the issue. Not sure what allowed it work when it did, but even now right after a reboot the camera app still crashes.
This was long ago, I've since lost the phone. But, I was on the A bootloader and on OREO rooted using @/billa's method using an ENGboot file. I tried everything possible to get the camera to work including flashing back to stock but nothing helped. I just gave up finally. @kanesglove maybe try safely updating the firmware. Hope it helps