Hey guys! I flashed viper xl and beastmode and camfix to my device. Now my g-sensor doesn't work so I reflashed viper xl boot.img again and the g-sensor works. Problem is my camera wont work now because I flashed the cam fix which was for beastmode not the stock kernel. So I want to know how to get the stock camera back without restoreing from a nandroid? Any help as always is appreciated.
ImagioX1 said:
Hey guys! I flashed viper xl and beastmode and camfix to my device. Now my g-sensor doesn't work so I reflashed viper xl boot.img again and the g-sensor works. Problem is my camera wont work now because I flashed the cam fix which was for beastmode not the stock kernel. So I want to know how to get the stock camera back without restoreing from a nandroid? Any help as always is appreciated.
Click to expand...
Click to collapse
flash the cam fix again
Camera still doesn't work.
EDIT: Restored via nandroid.
I flashed viper 2.1 last night, and camera didn't work. Didn't flash beastmode or cam fix. Just did OTA update to 2.1.2 and camera still doesn't work. So if you, or anyone is able to find a fix please let me know.
Sent from my HTC One XL using xda app-developers app
Myrder said:
I flashed viper 2.1 last night, and camera didn't work. Didn't flash beastmode or cam fix. Just did OTA update to 2.1.2 and camera still doesn't work. So if you, or anyone is able to find a fix please let me know.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
first off did you do a clean install?
try to wipe cache/dalvik cache
I'm having the same issues. I've tried wiping my device numerous times along with trying to restore my nand with no luck. If I re-install Viper XL that's when my camera works (if i try to go to any other ROM I'm S.O.L)
Beastmode 4 fix the issue for me
Related
I installed the JB ROM JellyTime Beta 7 fine. When I installed JellyTime Beta 8, it hung on the Jellybean boot screen. The OP of the JellyTime thread told someone else with the same problem to update their ADSP firmware for new kernels. I searched and searched, but I couldn't find a reference to how do do that or what it even really was. Could anyone help point me in the right direction?
bananagranola said:
I installed the JB ROM JellyTime Beta 7 fine. When I installed JellyTime Beta 8, it hung on the Jellybean boot screen. The OP of the JellyTime thread told someone else with the same problem to update their ADSP firmware for new kernels. I searched and searched, but I couldn't find a reference to how do do that or what it even really was. Could anyone help point me in the right direction?
Click to expand...
Click to collapse
Sure wish i could get some help with this too.
Have you guys tried the latest releases? When full wiping include format all partitions except sd card.
Sent from a dream.
What latest releases are you referring to? Could you please be more specific?
EDIT: I did a full wipe and reformat of everything, including system, data, and cache.
Right now they are on beta 10. Funny thing, I don't recall anyone mentioning a need to do a adsp firmware update. I don't even know what it is.
Sent from a dream.
I upgraded my radio and ril and it still would not work. I then flashed a stock htc ROM that had sense 3 and then it would take beta 10.
Sent from my Desire HD using xda app-developers app
jlochamy said:
I upgraded my radio and ril and it still would not work. I then flashed a stock htc ROM that had sense 3 and then it would take beta 10.
Click to expand...
Click to collapse
Are you referring to this one?
bananagranola said:
Are you referring to this one?
Click to expand...
Click to collapse
That is the one. But if you don't do a full wipe before you do beta 10 it will have errors. It would still boot but have lots of errors.
Sent from my Desire HD using xda app-developers app
In case anyone is looking for a solution and finds this thread, I can confirm that flashing the stock ROM, wiping, and flashing Beta 10 works.
bananagranola said:
In case anyone is looking for a solution and finds this thread, I can confirm that flashing the stock ROM, wiping, and flashing Beta 10 works.
Click to expand...
Click to collapse
It worked for me as well.
along the same discussion I'd like to ask another question about the new 3.0 kernel.
I'm a weekly ROM changer and usually run IceColdSandwich. Once I switch back to ICS and want to reflash JT to check out the latest improvements/updates, do I have to re-flash the GizRoot_v_2 with the 3.0 kernel then flash JellyTime? Would it work If I did a backup of JellyTime and tried to restore it when a new update comes out or does it become non flashable once I've returned to the older ICS kernel?
In other words, can I flash between ICS and JT without having to go through all the steps to reload the 3.0 kernel?
Thanks in advance to a great community!
uss..p8triot said:
It worked for me as well.
along the same discussion I'd like to ask another question about the new 3.0 kernel.
I'm a weekly ROM changer and usually run IceColdSandwich. Once I switch back to ICS and want to reflash JT to check out the latest improvements/updates, do I have to re-flash the GizRoot_v_2 with the 3.0 kernel then flash JellyTime? Would it work If I did a backup of JellyTime and tried to restore it when a new update comes out or does it become non flashable once I've returned to the older ICS kernel?
In other words, can I flash between ICS and JT without having to go through all the steps to reload the 3.0 kernel?
Thanks in advance to a great community!
Click to expand...
Click to collapse
Nope. You only need to flash the stock once; after that, flash back and forth to your heart's content.
uss..p8triot said:
In other words, can I flash between ICS and JT without having to go through all the steps to reload the 3.0 kernel?
Thanks in advance to a great community!
Click to expand...
Click to collapse
IceColdSandwich runs on a 2.6.5 kernel, and will not work with a 3.0 kernel. Jellytime runs on a 3.0 kernel and will not work with a 2.6.5 kernel. Both of those ROMS have their respective kernels included. You only have to flash the ROM. I'd also recommend a full wipe before each flash as well.
sent from my IceCold Inspire 4G
fatboyRICH said:
IceColdSandwich runs on a 2.6.5 kernel, and will not work with a 3.0 kernel. Jellytime runs on a 3.0 kernel and will not work with a 2.6.5 kernel. Both of those ROMS have their respective kernels included. You only have to flash the ROM. I'd also recommend a full wipe before each flash as well.
sent from my IceCold Inspire 4G
Click to expand...
Click to collapse
usspatriot is actually referring to a separate question. Some of us need to update our firmware to run JB, which can only be done by flashing the latest stock before flashing JB. He wanted to know if the updated firmware would be overwritten by flashing ICS, requiring a reflash of stock before reflashing JB. The ICS and JB kernels are not at issue.
I wonder if this has anything to do with my issue with JB on a Desire HD:
I came from SmartDroid_Reloaded_wwe_1.5.2, did a full wipe, installed, everything works fine for me except for cellular data.
I'm wondering if it's something to do with JB not liking my phone? I've also tried a couple of ICS roms.. See below:
SmartDroid_Reloaded_wwe_1.5.2 = cell data works
Sabsa_Prime_v5.0 = cell data works
TrickDroid_v1.1.1 = cell data works
cm-cfX-20120925-OFFICIAL-ace = no cell data
cm-JellyTime_R10 = no cell data
cm-JellyTime_R10.1 = no cell data
cm-JellyTime_R11 = no cell data
i set my APN's to suit my network (crazy johns in australia) but nothing works..
If i connect to wifi, both the wifi signal and cell signal turn blue, if i disconnect from wifi, both turn grey.
MMS, SMS, Phone calls work fine..
Click to expand...
Click to collapse
OK I purchased my HOX and it came with 4.0.4 ICS 2.20 I unlocked the bootloader a rooted it via the new method. I have flashed a couple roms and now my camera freezes the second it opens up and will not work. Any Help please?
Do you happen to be using the beastmode kernel?
What rom are you using as well?
Sent from my HTC One XL
absolutelygrim said:
Do you happen to be using the beastmode kernel?
What rom are you using as well?
Sent from my HTC One XL
Click to expand...
Click to collapse
I started with venom XL and flashed Beastmode, then I flashed Nocternal had some issues so I restored my original back up. Thats when I noticed the camera freezing so I flashed Clean ROM and it is still doing it.
The_new_user said:
I started with venom XL and flashed Beastmode, then I flashed Nocternal had some issues so I restored my original back up. Thats when I noticed the camera freezing so I flashed Clean ROM and it is still doing it.
Click to expand...
Click to collapse
Did you do a clean install before flashing cleanrom?
absolutelygrim said:
Did you do a clean install before flashing cleanrom?
Click to expand...
Click to collapse
Yes I did a clean install, I Fixed it. I had to flash the Clean ROM Kernel to remove the beastmode kernel I had on there and now it works fine. Thanks to all who tried to help.
If you wanted to use Beastmode Kernel though, you could use the cam fix
http://forum.xda-developers.com/showpost.php?p=33364974&postcount=8
Has anyone tried using this camera: http://forum.xda-developers.com/showthread.php?t=1966339
With Venom XL and Beastmode?
area51avenger said:
If you wanted to use Beastmode Kernel though, you could use the cam fix
http://forum.xda-developers.com/showpost.php?p=33364974&postcount=8
Has anyone tried using this camera: http://forum.xda-developers.com/showthread.php?t=1966339
With Venom XL and Beastmode?
Click to expand...
Click to collapse
LOL I didn't see that thanks.
Hello there, i am having some interesting issues with my att xl.
Stock ICS ROM rear camera works perfect.
Any custom JB sense rom, rear camera doesn't work.
Liquidsmooth cm 10.1 JB rom rear camera works perfect.
stock JB 3.18 att rom, rear camera doesn't work.
Before anyone gets all froggy, yes i read this post: http://forum.xda-developers.com/showthread.php?t=1911847&page=3 and it doesn't really pertain to my situation as I am able to get my camera working on different roms.
It seems as though it may be a driver issue, so i tried copying the camera libs from the working cm 10.1 rom into the appropriate folders on both the custom and stock sense jb roms but i just get stuck at boot screen and have to reflash.
Any help will....help... maybe i didnt grab all the files or something.
Thanks ahead of time.
Anyone with any ideas what so ever? Ill try anything at this point.
try to check the md5 of the download jb files and the ones mentioned in the OP and do not try using cm 10.1 libs on sense roms its different , else did u try wiping cache of ur camera and see .. just try some other sense JB Rom and see if u get the same error !
S-on? Did you remember to flash boot.img for every ROM?
Sent from my HTC One X using xda app-developers app
Sorry forgot to mention, phone is s-off and I have tried multiple sense roms. Sadly on ics sense roms will alow rear camera to work.
Sent from my HTC One X using xda premium
What recovery are you using? A couple of us have had a problem where our dialer would fc if we flashed a sense rom using TWRP after using CWM.
Sent from my One X using xda app-developers app
sweeterman said:
What recovery are you using? A couple of us have had a problem where our dialer would fc if we flashed a sense rom using TWRP after using CWM.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I have tried both cwm and twrp. And have also tried flashing the boot.img.
I think what I will have to try next is reflashing back to ics then starting over...this sucks, it must be a different camera on my particular device...it is a refurbished unit they gave me. Thanks for all the ideas so far, and any more are welcomed.
Ok, I completely re-ruu 'ed... If that makes any sense, to the newest cingular evita rom.. . And... Same exact problem, front camera works, rear doesn't. So my question now is, can I get the camera libs from an ics rom and throw them into the jb rom ? It looks like that will have to be my next venture. This blows
Sent from my HTC One X using xda premium
unforseenenemy said:
Hello there, i am having some interesting issues with my att xl.
Stock ICS ROM rear camera works perfect.
Any custom JB sense rom, rear camera doesn't work.
Liquidsmooth cm 10.1 JB rom rear camera works perfect.
stock JB 3.18 att rom, rear camera doesn't work.
Before anyone gets all froggy, yes i read this post: http://forum.xda-developers.com/showthread.php?t=1911847&page=3 and it doesn't really pertain to my situation as I am able to get my camera working on different roms.
It seems as though it may be a driver issue, so i tried copying the camera libs from the working cm 10.1 rom into the appropriate folders on both the custom and stock sense jb roms but i just get stuck at boot screen and have to reflash.
Any help will....help... maybe i didnt grab all the files or something.
Thanks ahead of time.
Click to expand...
Click to collapse
Good day. I have a problem on my htc hd2 leo. The camera does not focus and is making a strange noise like a beating heart and jumps like a speaker spoiled. This all original
Someone help me?
Thank you
Davrafa said:
Good day. I have a problem on my htc hd2 leo. The camera does not focus and is making a strange noise like a beating heart and jumps like a speaker spoiled. This all original
Someone help me?
Thank you
Click to expand...
Click to collapse
You need to ask in the correct forum for your device, this is the HTC One XL forum.
Sent from my Evita
Hello everyone.
Sorry I'm new to the forum, so I can't post in Dev thread.
I'm on Rogers, One X, Hboot 2.14, SuperCID, S-on, CleanROM 7.0.P1, Beastmode 4 (test2) kernel and Zoe mod.
Everything seems to working great, the only thing that is kinda frustrating is camera focus (both autofocus and manual). It seems to be focusing good on far objects, but all the closeups, on all the modes are blurry.
Did anyone else had this problem ? maybe there is a solution.. Zoe feature is very cool and going back to stock camera up is sad.
Would appreciate suggestions and possible solutions. Unfortunately I'm not a dev and all I can really do is follow steps.
Thank you in advance.
You need to flash Beastmode 3.5 version kernel, you're on the first test release. Flash 3.5 and your camera will focus perfectly.
Sent from my Evita
timmaaa said:
You need to flash Beastmode 3.5 version kernel, you're on the first test release. Flash 3.5 and your camera will focus perfectly.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your reply.
Just tried flashing 3.5. First reboot, started, no signal, no wifi, same focus problem. Next reboot it started in boot loop.
The kernel didn't take then. Go to settings > about > software > more and post the kernel version.
Sent from my Evita
[email protected] #30 SMP PREEMPT
I restored from backup so I can get the phone running.
If the kernel flash works it should look like this.
Sent from my Evita
Sorry, totally forgot about the screenshot.
So you're on 3.5 now and you're still having issues?
Sent from my Evita
That is so strange, I flashed the kernel several times, it didn't boot, so I restored from backup, last time I restored, my phone it does look it has 3.5 and the camera started working, so many, many thanks, will also click the thank you btn.
But now wifi is broken and I'm having some strange issues rooting the phone so I cant replace the wifi file, but this probably will be another thread.
Thanks again :good:
I'm gonna sound like a moron for asking this, but it's because I'm new to this, I need help fixing my WiFi from saying error on my HOXL that's running the ViperXL rom 4.2.0(which btw is awesome) & Beastmode kernel 3.5. I know someone is going to say "just put the prima_wlan.ko file in my system/lib/modules & change the permissions to 744", well I did that and that didn't work. I hope that I'm just doing something wrong, so if someone could help me out or walk me through it I would very much appreciate it!
ViperXL Rom 4.2.0
Beastmode Kernel 3.5
S-ON
I am not an expert but I will try to share what has just happened to me. I just flashed the stock 4.2.2 turge version and then flashed the beastmode 3.5 because I keep getting random reboot. After kernel install my WiFi came up with error and no connection at all. So I reflashed the Rom again and it works. Now it can be just coincident. I am not saying that is the way but it works on mine so far. I am sure some more experience user can correct me and give better answer.
Sent from my HTC One XL using Tapatalk 2
ardabelati said:
I am not an expert but I will try to share what has just happened to me. I just flashed the stock 4.2.2 turge version and then flashed the beastmode 3.5 because I keep getting random reboot. After kernel install my WiFi came up with error and no connection at all. So I reflashed the Rom again and it works. Now it can be just coincident. I am not saying that is the way but it works on mine so far. I am sure some more experience user can correct me and give better answer.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
By flashing the ROM again you've overwritten the Beastmode kernel with the stock kernel.
Sent from my Evita
So the rom actually flashing the kernel as well?
Hmm...so may be my random reboot is still not fix then.
I am also curious on how to fix this WiFi error on the beastmode 3.5
Sent from my HTC One XL using Tapatalk 2
Yes, each ROM zip has a kernel built in. Otherwise if you only flash a ROM and no custom kernel the phone wouldn't boot. I've seen people fix the WiFi error on the Beastmode kernel in the thread but I can't remember which page it's on.
Sent from my Evita
ardabelati said:
So the rom actually flashing the kernel as well?
Click to expand...
Click to collapse
Yes, flashing a ROM flashes the kernel. The only time flashing a ROM does not flash the kernel, is if s-on and hboot 1.14 or higher. And this is only due to protections placed by HTC.
Normally a ROM will always flash the kernel.
Sorry if this is kind of hijacking the post. But how do you put the prima_wlan.ko file in my system/lib/modules & change the permissions to 744?
I searched but did not find any guide for this?
Sent from my HTC One XL using Tapatalk 2
Navigate to /system/lib/modules using root browser or a similar app, copy the file to that location, long press on the file, select permissions, and set like this screenshot.
Sent from my Evita
timmaaa said:
Navigate to /system/lib/modules using root browser or a similar app, copy the file to that location, long press on the file, select permissions, and set like this screenshot.
Sent from my Evita
Click to expand...
Click to collapse
See I did that, but my error still occurs, could it be the file or something else?
ViperXL Rom 4.2.0
Beastmode Kernel 3.5
S-ON
Just fyi, some people have been reporting problems with flashing Beastmode 3.5 right away. Recommended to try to flash Beastmode 2.0 and then 3.5 over top of that. Worked well to fix my signal issues. :good:
mitsurugidgb said:
Just fyi, some people have been reporting problems with flashing Beastmode 3.5 right away. Recommended to try to flash Beastmode 2.0 and then 3.5 over top of that. Worked well to fix my signal issues. :good:
Click to expand...
Click to collapse
I actually started using Beastmode 2.0, I have I nice little fix for the wifi on that, so I'm no longer stressing about anything but my proximity sensor(which I could fix but I'm just being lazy lol)
ViperXL Rom 4.2.0
Beastmode Kernel 2.0
S-ON