Hey there guys,
I recently hit a problem on rooting and installing cm10 on an Xperia Active.
Here the actual facts:
Android 4.1.2,
CyanogenMod: 10-20131006-NGIHTLY-satsuma,
Kernel- Version: 2.6.32.61-MESA-HYBRID-v4.8 (seems to be the only kernel working since I receive a black screen using the kernel delivered in the cm10 Rom from above)
So here the Problem: There is no camera app on the device right now. Installing the Honami- Camera doesn't work either.
Any ideas? I'm pretty new in this Rooting/ Custom- ROM stuff, so please don't kill me if the solution is obvios.
Regards glu
super.glu said:
Hey there guys,
I recently hit a problem on rooting and installing cm10 on an Xperia Active.
Here the actual facts:
Android 4.1.2,
CyanogenMod: 10-20131006-NGIHTLY-satsuma,
Kernel- Version: 2.6.32.61-MESA-HYBRID-v4.8 (seems to be the only kernel working since I receive a black screen using the kernel delivered in the cm10 Rom from above)
So here the Problem: There is no camera app on the device right now. Installing the Honami- Camera doesn't work either.
Any ideas? I'm pretty new in this Rooting/ Custom- ROM stuff, so please don't kill me if the solution is obvios.
Regards glu
Click to expand...
Click to collapse
Hey,
me again. Fixed the problem by installing the "Googleeditioncamera" Thought it wasn't working, but I just forgot to reboot. Hope someone can use this information some day.
regards glu
Related
Hi Guys,
I'm new to this Forum so please pardon if i'm not following any rules and mistakenly posted the thread in the wrong location.
I had installed Clockworkmod Recovery from "theandroidsoul"
Then I have Samsung Galaxy S2 i9100. Recently i have installed a custom ROM on it provided by JellyBam ROM 20121023 – i9100 (courtesy: igio90.)
It has upgraded my phone to:
Android version: 4.1.2
Baseband: I9100DDLP8
Kernel Version:[email protected]
AOKP Version: JellyBam.AOKP.Build5
Build number: JellyBam AOKP 20121023
I have found it to be unstable as there were many functionality that have been lost including FM, 5.1 surround sound, MTP and mass storage connection, etc.
I would like to remove the ROM completely and install another of ROM
Please suggest me the following:
1. can i go back to ICS 4.0.1 by removing this rom and instaliling ICS from odin? what would be a recommended procedure for it?
2. Will i BRIK my phone in this process?
3. Can i install any other version of Jelly bean custom rom using ODIN, what would be a recommended procedure for it?
Guys i need your help ASAP as i cannot stay with this unstable ROM for long. any help is hugely appreciated.
Cyanogen Mod 10
Nitin_Zambre said:
Hi Guys,
I'm new to this Forum so please pardon if i'm not following any rules and mistakenly posted the thread in the wrong location.
I had installed Clockworkmod Recovery from "theandroidsoul"
Then I have Samsung Galaxy S2 i9100. Recently i have installed a custom ROM on it provided by JellyBam ROM 20121023 – i9100 (courtesy: igio90.)
It has upgraded my phone to:
Android version: 4.1.2
Baseband: I9100DDLP8
Kernel Version:[email protected]
AOKP Version: JellyBam.AOKP.Build5
Build number: JellyBam AOKP 20121023
I have found it to be unstable as there were many functionality that have been lost including FM, 5.1 surround sound, MTP and mass storage connection, etc.
I would like to remove the ROM completely and install another of ROM
Please suggest me the following:
1. can i go back to ICS 4.0.1 by removing this rom and instaliling ICS from odin? what would be a recommended procedure for it?
2. Will i BRIK my phone in this process?
3. Can i install any other version of Jelly bean custom rom using ODIN, what would be a recommended procedure for it?
Guys i need your help ASAP as i cannot stay with this unstable ROM for long. any help is hugely appreciated.
Click to expand...
Click to collapse
from what i can see you need a stable custom ROM with nice Features, i recommend you Cyanogen Mod 10 Jelly Bean... i Have it on my XPERIA ARC S and it works perfectly with no detected bugs, only one thing that i dont care about is that no more HDMI setting... the prcedure is quit easy and if you got stuck you can go back and ask for help, i dont think you can brick your phone if you follow steps and make a minor mistake.. if you would like to try, i can help you in everything, and please hit "THANKS" if i helped
Omessy7 said:
from what i can see you need a stable custom ROM with nice Features, i recommend you Cyanogen Mod 10 Jelly Bean... i Have it on my XPERIA ARC S and it works perfectly with no detected bugs, only one thing that i dont care about is that no more HDMI setting... the prcedure is quit easy and if you got stuck you can go back and ask for help, i dont think you can brick your phone if you follow steps and make a minor mistake.. if you would like to try, i can help you in everything, and please hit "THANKS" if i helped
Click to expand...
Click to collapse
Install Cm10, nice, no bugs so far, check forums for your device.
Hi there. I hope anyone could possibly answer my inquiry with JELLYBAM ROM. I have an S3 and clean installed it using JellyBAM 4.1.2 version. after the installation and setting it up with my gmail account, it shows an error message about the audio enhancement did not properly installed. then it won't play any audio at all.
I don't know what I missed during installation. Please advise.
Thanks in advance.
try to reinstall.if it still doesnt fix it,try to identify the problem by trying out stuff.if still nothing,try to search.last resort,try other ROMs.
your problem is an uncommon one so its hard to identify it without others experiencing it and fixing it.a simple reflash/reinstall usually does the trick.
Jellybam 4.1.2 ROMS vs PACman roms
Hi!
I've been trying a lot of different roms, and lately been running Jellybam 4.1.2 - versions and currently running PACman. As it seems, Jellybam roms are getting updated all the time (with both issues being solved, and new problems occuring), where PACman v 18 hasn't been updated since Dec 23.
On to my question : Are there any major differences in the Jellybam 4.1.2 ROMS and PACman, and which one has the best "future"?
Rydder said:
Hi!
I've been trying a lot of different roms, and lately been running Jellybam 4.1.2 - versions and currently running PACman. As it seems, Jellybam roms are getting updated all the time (with both issues being solved, and new problems occuring), where PACman v 18 hasn't been updated since Dec 23.
On to my question : Are there any major differences in the Jellybam 4.1.2 ROMS and PACman, and which one has the best "future"?
Click to expand...
Click to collapse
The roms all have details its up to you to decide what you want .
Best Rom What rom are banned on XDA .
jje
Thanks guys for your feedback. Appreciate it.
Sent from my GT-I9300 using xda app-developers app
Guys,
I have been using codecROM for the past one month and i felt it was Superb. but i'm a viber user so viber isn't working on codecROM 9.1 so i had to revert back to stock ICS ROM. i have seen few posts regarding dual boot in Siyah Kernel. what i wanted to do now is as follows:
1st Boot: Stock ICS 4.0.4
2nd Boot : Any other custom ROM
is this possible..??
Currently my phone is Fully rooted.
also suggest me any ROM in which apps like viber which use wifi for calling will work for sure..
Thanks a lot guys i have learnt a lot from xda-developers
Great first post - not
Tip: Search for Siyah kernel
BPhild area
rahulbalmuri said:
Guys,
I have been using codecROM for the past one month and i felt it was Superb. but i'm a viber user so viber isn't working on codecROM 9.1 so i had to revert back to stock ICS ROM. i have seen few posts regarding dual boot in Siyah Kernel. what i wanted to do now is as follows:
1st Boot: Stock ICS 4.0.4
2nd Boot : Any other custom ROM
is this possible..??
Currently my phone is Fully rooted.
also suggest me any ROM in which apps like viber which use wifi for calling will work for sure..
Thanks a lot guys i have learnt a lot from xda-developers
Click to expand...
Click to collapse
my bad ... sorry guys.. just now i came across this thread.. http://forum.xda-developers.com/showthread.php?t=1709686 so according to tht dual boot is not supported by ICS... what if i update to 4.1.1(jelly bean)?? then how to dual boot??
Once you upgrade to jelly bean you will have to install siyah kernel, the latest version to be able to dual boot. Read through the siyah kernel thread under original android development, it'll explain everything.
Sent From My Omega'd Galaxy S3 ...
Sorry to bring up such a silly issue.
But I never encountered any problem like this. So, pls help me out....
I have a WT19i device which being modded with various custom rom at various time.
for more than 1.5 years I didn't got into any kind of problem. and it all messed up.
Yesterday I was trying to install Super jelly bean 8.0 rom.
to do that,
1. I flashed nAa's kernel
2. Wiped whatever needed.
3. Installed rom's zip and gapps
4. Reboot my device.
Everything working well except i don't have any touch response....!
Then I re-flashed my stock 4.0.4 rom, and then everything working fine. (including touch)
Again I flashed cm10 kernel and then installed Cm10 rom
Same problem again, no touch response.....
I really want to install jelly bean rom to my device.
So, pls give me a solution.
Sry if this [Q] is bothering.
Hello friends.
I am new to this wonderful community and very happy to be a part of it.
I am facing a very strange problem. I am trying to update my WT9i Live with walkman from Gingerbread to Ice cream sandwich. Problem is .. whenever I flash an ICS rom my touch doesn't work !! Everything else works fine (physical keys / network / audio). Then if I install GB rom again it works flawlessly.
I have unlocked bootloader.
I am using Flashtool to flash stock roms.
* WT19i_4.0.2.A.0.58_(1254-1868).ftf = works
* WT19i_4.0.2.A.0.62_(1254-1889).ftf = works
* WT19i_4.1.B.0.431_Generic.ftf = touch doesn't respond
* WT19i_4.1.B.0.587_Generic.ftf = touch doesn't respond
* WT19i_4.1.B.0.587_CUSTOMIZED CE3 WORLD I 1254-1889.ftf = touch doesn't respond
I have no idea what could be the reason. Any GB roms works smoothly. Any ICS roms bricks the touch screen. I have tried custom kernel (mesa .. kappa) and many custom ICS rom .. same problem. But at any moment I flash GB rom .. everything works.
I did all the research I could (for last 4 days) and read many threads .. tried many things. Nothing helped.
Please help me! Please Please Please.
I have seen many threads with problem "touch does't work because of flashing wrong rom or kernel".
I don't think that's my case. Because whenever I flash a stock GB rom .. it works just fine. Problem happens with ICS roms .. custom or stock.
I am going to try some custom GB rom with custom kernel. I'll post if that works.
This thread is most likely my last hope of finding a solution .. please help!
Just out of curiosity downloaded the 587 ICS generic rom from flasstool website then flashes it .. same touch problem.
Now downloading latest Nightly CM10 coconut. I'll try it. CM 9.1 stable did not worked .. same touch problem.
Please Help ! I dont see a clue ! Why ICS roms would freeze my touch when everything else works? I am on the verge of throwing my phone out of window !!!
Latest CM10 Nightly build = same problem .. touch screen is not working.
Flashed Stock GB = everything is fine !
:crying::crying::crying::crying::crying:
Now I am downloading every regional roms of stock ICS .. its all I can think of.
I know its a very old phone and update / development for it completely stopped. Its forgotten. Still I love this little cute handset and I would love to get ICS on it (for app support .. many app do not work on GB .. like google chrome).
So please help !
Hello there!
Quick question: has your LWW ever been repaired? Like, had it's touch digitizer replaced or manipulated in any way?
I know some replacement parts can conflict with non-stock (or "comes-out-of-the-box" to be precise) software. I bought a replacement display for my Mini Pro and it would just freeze on CM10.1 but worked (kinda) on stock ICS.
And yeah, it's and old phone, but a good one. Development for it and it's 2011 brothers has clearly slowed down but has absolutely not stopped
Pixelado said:
Hello there!
Quick question: has your LWW ever been repaired? Like, had it's touch digitizer replaced or manipulated in any way?
I know some replacement parts can conflict with non-stock (or "comes-out-of-the-box" to be precise) software. I bought a replacement display for my Mini Pro and it would just freeze on CM10.1 but worked (kinda) on stock ICS.
And yeah, it's and old phone, but a good one. Development for it and it's 2011 brothers has clearly slowed down but has absolutely not stopped
Click to expand...
Click to collapse
Hello. Thank you for replying. Its a second hand phone .. my brother purchased it from a friend then gave it to me. So it may have a replaced display or digitizer. I just checked with my brother and he said his friend never repaired the phone.
So GB and ICS use different digitizer drivers? Is it possible to use GB touch drivers with ICS?
No idea. Your problem is truly rare haha.
I'm out of ideas here, most of the time flashing a stock ftf does the trick, but not here.
if I were you, i'd sell that phone to someone who woulndn't care about software updates hehe.
Hello Friends.
I am posting this in case someone else face the same problem and find this thread. In my opinion ..this is a very rare and strange problem.
This problem should never happen with an original handset.
If your touch only works with Gingerbread stock roms and even after complete wipe other stock roms freeze your touch .. then you can be sure that your touch was replaced with a cheap one. Go to a servicing center and replace it with a good touch or sell the phone to someone else who doesn't care about updates.
I went to a servicing center today and replaced my touch. Now it works smoothly with stock ICS rom. I am sure it will work with CM too. It costed me around 25$.
1 tip to recognize low quality touch. Low quality touch will not have transparent bottom-left and bottom-right button. You wont be able to see the key lights through it. Good quality touch will have transparent button. Another warning .. after market touch is most probably not scratch resistant like the original touch .. so you may want to use a good screen protector (plastic film) on it.
This is not only for WT19i. Whenever you buy a secondhand set .. make sure its touch wasn't replaced and best to check if its upgraded and working properly.
Thanks to "Pixelado" for hinting me about the replaced touch issue. Then it made sense to me .. there was no other logical reason for the stock rom not working.
I am very happy with my upgraded ICS But kinda sad about the money loss ! Anyway loss is loss. This is a good handset and I hope it will serve me good. Now looking for a way to root it.
i'm always more than glad to help
Now, on the rooting issue, I strongly recommend unlocking your bootloader and flashing a pre-rooted kernel. Why, you ask? Well, you'll find out eventually
Custom kernels often pack a bunch of optimizations and the ability to overclock. I strongly recommend Rage kernel for stock ICS. Once you flash it, i'll take care of rooting your phone on first boot. If you're not able to unlock your bootloader/don't feel comfortable flashing kernels, rooting by exploits is your only choice.
By the way, I strongly suggest giving LegacyXperia CM10.1 a try. Its awesome
Pixelado said:
i'm always more than glad to help
Now, on the rooting issue, I strongly recommend unlocking your bootloader and flashing a pre-rooted kernel. Why, you ask? Well, you'll find out eventually
Custom kernels often pack a bunch of optimizations and the ability to overclock. I strongly recommend Rage kernel for stock ICS. Once you flash it, i'll take care of rooting your phone on first boot. If you're not able to unlock your bootloader/don't feel comfortable flashing kernels, rooting by exploits is your only choice.
By the way, I strongly suggest giving LegacyXperia CM10.1 a try. Its awesome
Click to expand...
Click to collapse
Thanks a lot Pixelado. I have unlocked bootloader and using mesa kernel 4.8. Would Rage 3.2 would be better than Mesa?
I'll try LegacyXperia CM10.1 .. appreciate the recommendation.
I've never tried mesa, so no comment there. Quie frankly, rage 3.2 seemed to be all i ever needed when using a stock rom. I tried lupus, but stopped using it when they switched from CWM to TWRP.
Angelina7 said:
Thanks a lot Pixelado. I have unlocked bootloader and using mesa kernel 4.8. Would Rage 3.2 would be better than Mesa?
I'll try LegacyXperia CM10.1 .. appreciate the recommendation.
Click to expand...
Click to collapse
i have same problem too
can u solve this problem?