Database Info

Can not connect to the camera. Still no solution? CM10.0.

Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).

Same problem
CZory91 said:
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Click to expand...
Click to collapse
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix

bmanderle said:
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
Click to expand...
Click to collapse
It's an AOSP problem based on the firmware of your camera when getting the phone from what I've seen.
http://forum.xda-developers.com/showthread.php?p=37072484#post37072484
Here's the thread I was talking about, however I'm confused about how to go about zipping and unzipping these files. Or even how to get to them to place the files in to begin with considering internal SD card is the only thing that comes up for USB storage. Unless you're supposed to move them in and out from within android.

Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?

CZory91 said:
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
Click to expand...
Click to collapse
I had the camera problem on MIUI...
Before flashing, I made a backup of my system with CW
I extracted the SlimISP_ZH.bin from my backup and
copied it to my /data directory and it worked fine.
Link: d-h.st/dwx
(I can't post links yet)
maybe... someone post the fix in this forum and make it sticky... lol

Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.

CZory91 said:
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
Click to expand...
Click to collapse
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
Click to expand...
Click to collapse
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever

dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
Click to expand...
Click to collapse
Yes, that is the post. I also tried MB1 out of curiosity, no dice on either of them. I had a perfectly working CM10. I dun goofed :\.
That was my next step (rerooting, installing that firmware AIO, and then installing CM10). However my question is this, what happens when more firmware comes out? I have to re root and start over again?

If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium

bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch

dandydon414 said:
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
Click to expand...
Click to collapse
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium

bbqsfire said:
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time

Hmm, over the past couple days I've tried out a few different ROMs on my girlfriend's S3 here, and on each one I would get this "Could not connect to the camera" error, every single time upon opening the camera app. One of the Paranoid Android ROMs, Liquid Smooth, and Synergy (even the Touchwiz camera was broken on that!).
I can restore to the original backup I made of the stock ROM, and the camera works fine again. But as soon as I try a different ROM, no camera.
I'd love to get an AOSP ROM running on this phone, but having a working camera is a requirement, and I can't figure out what I'm doing wrong. Searching the individual threads for the ROMs yields little help, and I'm getting exactly the same error on different ROMS, so I feel like I'm doing something wrong on a higher level. Any chance that switching from TWRP to CWM would make a difference? I don't see why it would, but I suppose it's something I could try.

bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.

CZory91 said:
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
Click to expand...
Click to collapse
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?

Watanuki-Kun said:
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Click to expand...
Click to collapse
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.

CZory91 said:
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
Click to expand...
Click to collapse
Probably best, that would be my first thing to try if I had that problem, restarting from scratch. If all else fails, restarting from scratch will wipe out everything. If that failed, I would probably suspect hardware issue.

Watanuki-Kun said:
Have you tried odin back to MB1...
Click to expand...
Click to collapse
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/

dandydon414 said:
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Click to expand...
Click to collapse
Well I would recommend liquid 2.5 with the kernel that comes with it and I never change any of the overclocking settings. I don't have to pull the battery at all on this one.
Sent from my SCH-I535 using xda premium

TunedReference said:
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
Click to expand...
Click to collapse
Yep, that's what I tried. Nothing.

[Q] CM9.1 giving me headaches like no other....

I have an HTC Sensation which i S-Off'ed , rooted, and installed vanilla CM9.1 on last Friday. And for the past 3 days, it's been having TERRIBLE random battery drainage, and even turns off on it's own (which is really annoying me). I've had these problems on and off when i was using the original Stock ROM, so i thought that installing CyanogenMod 9.1 would fix it, but NOPE, it just wouldn't let me go. I have ClockWorkMod Recovery (the latest version) and i have wiped the battery stats, wiped dalvik cache, formatted the system partition, reset the phone, heck i even re-downloaded and re-installed the WHOLE thing over and over again, and it STILL can't set itself straight.
Can anybody help meh?!
By the way, i don't keep Wi-Fi always on, and i have no Mobile Data plan, so that's not on, plus i really don't use the phone every-day, which negates the possibility that my usage is the fault. And i checked online for help, one way was to update the firmware, didn't work. Another way was to put cut a part of a business card or paper and just stick it above the battery to hold it in place, which didn't work when i was on stock so I'm not trying that again (Also, HTC, if you're reading this, you made a beautiful phone with the Sensation.... SO WHY U HEFF TO GIFF ME TRABBOL?)
Something else to be noted is that i used the SAME methods and files on my bro's phone and his is perfect, although my guess is that it might be something to do with the fact that my phone was a Vodafone UK branded one and his was completely unbranded one....
Also, I'm trying to get my hands on an Anker battery, but until I get it, I've only got you all, so help me...... pretty please? lol....

moanismk said:
I have an HTC Sensation which i S-Off'ed , rooted, and installed vanilla CM9.1 on last Friday. And for the past 3 days, it's been having TERRIBLE random battery drainage, and even turns off on it's own (which is really annoying me). I've had these problems on and off when i was using the original Stock ROM, so i thought that installing CyanogenMod 9.1 would fix it, but NOPE, it just wouldn't let me go. I have ClockWorkMod Recovery (the latest version) and i have wiped the battery stats, wiped dalvik cache, formatted the system partition, reset the phone, heck i even re-downloaded and re-installed the WHOLE thing over and over again, and it STILL can't set itself straight.
Can anybody help meh?!
By the way, i don't keep Wi-Fi always on, and i have no Mobile Data plan, so that's not on, plus i really don't use the phone every-day, which negates the possibility that my usage is the fault. And i checked online for help, one way was to update the firmware, didn't work. Another way was to put cut a part of a business card or paper and just stick it above the battery to hold it in place, which didn't work when i was on stock so I'm not trying that again (Also, HTC, if you're reading this, you made a beautiful phone with the Sensation.... SO WHY U HEFF TO GIFF ME TRABBOL?)
Something else to be noted is that i used the SAME methods and files on my bro's phone and his is perfect, although my guess is that it might be something to do with the fact that my phone was a Vodafone UK branded one and his was completely unbranded one....
Also, I'm trying to get my hands on an Anker battery, but until I get it, I've only got you all, so help me...... pretty please? lol....
Click to expand...
Click to collapse
LOL...CM 9??? You should give CM 10.1 or CM 10 a try, but you have to update the firmware first. Did you follow the directions here: http://forum.xda-developers.com/showthread.php?t=1459767
If you flash firmware 3.33 you can flash CM 10/10.1
If you want a super rock solid ROM i would try Bruce's CM 10 here: http://forum.xda-developers.com/showthread.php?t=1782009
CM 10.1 is here: http://forum.xda-developers.com/showthread.php?t=1782009
ARHD (ICS) is awesome also: http://forum.xda-developers.com/showthread.php?t=1098849
Although I've never tried CM 9, CM 10/10.1 should be a huge update. I think it should improve battery life as well.

Thanks for the help
AndroidSupporter318 said:
LOL...CM 9??? You should give CM 10.1 or CM 10 a try, but you have to update the firmware first. Did you follow the directions here: http://forum.xda-developers.com/showthread.php?t=1459767
If you flash firmware 3.33 you can flash CM 10/10.1
If you want a super rock solid ROM i would try Bruce's CM 10 here: http://forum.xda-developers.com/showthread.php?t=1782009
CM 10.1 is here: http://forum.xda-developers.com/showthread.php?t=1782009
ARHD (ICS) is awesome also: http://forum.xda-developers.com/showthread.php?t=1098849
Although I've never tried CM 9, CM 10/10.1 should be a huge update. I think it should improve battery life as well.
Click to expand...
Click to collapse
So, I've tried the CM10.1 ROM by albinoman887, and everything's perfect so far!
No random turn-off's, smooth as HELL, and a long battery life... (and did i mention Google Now? )
Thanks a lot bro......
If anything new comes up i'll be sure to share it on here...

I'm really glad you like it
Sent from my HTC Sensation

[Q] Bizarre Sound Issue with New Phone??

Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!

Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..

lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...

sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable

vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.

sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.

econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.

Boot into recovery and factory reset from there. That should clear up the boot loop issue.

theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive:

[Q] Reboots 30 into loading ROM

From the beginning.
Unlocked
EVITA PVT SHIP S-ON RL
HBoot 1.14.002
Radio 0.19as.32.09.11_2
OpenDSP v29.1.0.45.0622
eMMC-boot
June 11 2012, 14:36:28
Click to expand...
Click to collapse
I was running a ViperRom my camera light was staying on, I tried everything to get it to turn off. I decided it been a few month it was time to get a new ROM anyways. I tried installing Gummy Nightly's was having problem with the install read about getting a different version of TWRP so I updated to 2.6.3.0 I believe I had 2.1.0.0. Gummy still won't work, so I changed plans and want for the Viper XL Rom 4.2.0 this led to a bootloop not getting past the Viper splash screen. I thought I might as well just with one of my backup. So, i wiped and loaded a backup. This is the problem, it will load up the ROM for about 30 seconds before the icon all appear it will reboot. I've now been working on this for 2 days. I've went through each post and tried the advice each person was given, I've tried to Flash a different Rom, the Viper Rom I had when I had the Camera Light Issue, each time I get about 30 second into the Rom Load and reboot. (One of the ROMs would let me access the SDCARD0 but found a work around that.) I've let the phone sit charged for 2 hours looping. I've turn it off and let it sit charging. The next thing I'm going to try to to downgrade the TWRP. If anyone can give me some advice, something new and different to try that would be great. Thanks!
Cheers
xDrFirefly

talked to one of my buddy and said the downgrade would be pointless so, i'm trying to flash a stock rom at the moment.

When you changed to TWRP 2.6.3.0 was it the official version or the unofficial modified version?
Sent from my Evita

Recovery: Custom TWRP 2.6.3.0 w/selinux support

And what errors did it give you when trying to install Gummy?
Sent from my Evita

The install failed. I tried it multi times, and even d/l it again to see if that would make a difference. Nope.
Here is what i've done so far. I factory reset everything. Found a stock rom flashed it on. For the two hours I used it seemed to work fine. I then flashed CleanRom everytime I would open Ti Backup the phone would reboot. I flashed another ROM, was getting the signal drop snagged the Beastmode Kernel it keep failing everytime I tried to flash it. Factory Wiped EVERYTHING again. Flashed the Stock, then Flashed ViperXL (then went to bed) in the morning still had signal bars, so far had two reboots, one when I was uninstalling apps using Manage apps feature, and another time when I was in the Venom HUB app. But at the moment the phone seems to be working. The battery life is ****. In the 30 mins I've had the phone unplug i've down to 89% and all I did was delete a few apps, and move some stuff to the home screens. Hopefully it will get better with time.
Side Note: To anyone reading this. I got the AT&T HTC XL preorder. I doubt I will ever do that again. In all the years I've been flashing and messing with phone. ( My first phone I messed with was a Sidekick ) I've never had so much trouble as I had with this phone. ( HTC Tilt, Fuze and Tilt 2 never had this kinda problem ) a friend of mine whom waited a year to get the XL has never had any of the problem I've had. Just my thoughts. Thanks and I hope I won't have to be asking anymore question.
When, I have more time and such I'm going to try to flash Gummy. If I get the same error message for it or anything else I will post it here.
Cheers
-Dr FF

I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita

You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.

jacobas92 said:
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
Click to expand...
Click to collapse
I will try this. Sounds like a very logical plan.

timmaaa said:
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".

xdrfirefly said:
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
Click to expand...
Click to collapse
Computer always says no for a reason. You need the right recovery installed to flash KitKat ROMs, you also need to check the md5 of every ROM you download before you flash it. What I'm saying is there's no reason Gummy wouldn't install if you have done everything correctly.

CM 10.2 "stable" build crashing

I love Cyanogenmod, very much so. I downloaded the stable 10.1 build for my phone and it was mostly rock solid. When 10.2.1 come around I was pumped. I downloaded it and immediately encountered force closes out the bum. I switched back and a month later tried again. It was a slightly better experience as I realized I forgot to flash the 4.3 Gapps with my original attempt, but force closes cluttered my screen daily. I want to be able to upgrade, but the ROM just seems completely unstable for my phone. Has anyone experienced these things on their phone? Has anyone fixed these problems? Can anyone recommend the most stable and most up-to-date ROM even though stable and up-to-date rarely go hand in hand.

stjake said:
I love Cyanogenmod, very much so. I downloaded the stable 10.1 build for my phone and it was mostly rock solid. When 10.2.1 come around I was pumped. I downloaded it and immediately encountered force closes out the bum. I switched back and a month later tried again. It was a slightly better experience as I realized I forgot to flash the 4.3 Gapps with my original attempt, but force closes cluttered my screen daily. I want to be able to upgrade, but the ROM just seems completely unstable for my phone. Has anyone experienced these things on their phone? Has anyone fixed these problems? Can anyone recommend the most stable and most up-to-date ROM even though stable and up-to-date rarely go hand in hand.
Click to expand...
Click to collapse
Look in the CM11 thread, the nightlies are pretty stable for the most part and most us using it use it as a daily driver. You MUST perform a full wipe when installing a ROM, even when moving between point releases. If not, you'll encounter problems. GApps must also be flashed after the ROM has been flashed (assuming you want to use Google)

CWGSM3VO said:
Look in the CM11 thread, the nightlies are pretty stable for the most part and most us using it use it as a daily driver. You MUST perform a full wipe when installing a ROM, even when moving between point releases. If not, you'll encounter problems. GApps must also be flashed after the ROM has been flashed (assuming you want to use Google)
Click to expand...
Click to collapse
Yeah I figured that I need to wipe everything and install the proper GApps after my first attempt at 10.2 which to my credit I did do on my second try. Is there a particular nightly release that seems more stable than the rest? To put this in more context, I travel alone from college to various other places often a bit and my college is situated in almost a black hole of service for Verizon so I tend to take reliability over cutting edge even though I very badly want the newest and greatest. I'm on spring break so I'll try the newest nightly and back up my phone. Luckily I have a ton of space on my phone so I can always have a stable back up ready to be flashed on the fly.

stjake said:
Yeah I figured that I need to wipe everything and install the proper GApps after my first attempt at 10.2 which to my credit I did do on my second try. Is there a particular nightly release that seems more stable than the rest? To put this in more context, I travel alone from college to various other places often a bit and my college is situated in almost a black hole of service for Verizon so I tend to take reliability over cutting edge even though I very badly want the newest and greatest. I'm on spring break so I'll try the newest nightly and back up my phone. Luckily I have a ton of space on my phone so I can always have a stable back up ready to be flashed on the fly.
Click to expand...
Click to collapse
By their very nature, Nightlies are not considered stable in the strictest sense of the word. For most of us, they have been. But if you need reliability over cutting-edge, I'd stick with 10.2 or one of the CM11 Milestone builds (however, the RAZR HD only has one that I know of, CM11-M2).
My personal take is that given you're in an area with poor reception, choosing CM11 over CM10.2 (for example) wouldn't give you any better results over the other. Signal is signal.
My suggestion, given your circumstances and criteria, would be to stick with 10.2 but do a FULL backup via Recovery of your stock ROM (or whatever you're using instead of CyanognMod) and then do a FULL wipe of the following (and only these):
- user data
- /system partition
- /cache partition
- dalvik cache (usually found under Advanced in CWM recoveries)
Your phone will be in an unusable state after this. From here, still in Recovery, flash CM10.2 and then the appropriate GApps (make sure you choose the right one; a 4.4.2 GApps isn't suitable for a 4.3 OS) and reboot. If memory serves, CM10.2 is Android 4.3.1
If you're still having problems, you can restore your backup in Recovery or worst case, RSDLite the appropriate SBF for your phone to return to the carrier-stock ROM. But be aware if you chose the RSDLite path, you will lose everything. Basically it'll be like day-1 when you got the phone

Unroot help!!!
Hi I am trying to figure out how to unroot my Droid Razr HD...I bought it used from my buddy who upgraded and before we met up to make the deal I didn't know till after; that he rooted it and won't tell me how to unroot. I have only ever rooted one phone with his help and that was my thunderbolt. This phone is running CM 11-20140218-NIGHTLY-xt926. I want to bring it back to stock rom but have yet to find anyway to do that...it would be awesome if you guys could help me!!

Lanevox said:
Hi I am trying to figure out how to unroot my Droid Razr HD...I bought it used from my buddy who upgraded and before we met up to make the deal I didn't know till after; that he rooted it and won't tell me how to unroot. I have only ever rooted one phone with his help and that was my thunderbolt. This phone is running CM 11-20140218-NIGHTLY-xt926. I want to bring it back to stock rom but have yet to find anyway to do that...it would be awesome if you guys could help me!!
Click to expand...
Click to collapse
Find the FXZ you want to flash and use RSD or House of Moto to flash it.