[Q] cannot connect to the camera error problem - T-Mobile, Samsung Galaxy SIII

Am so sorry mods if i didn't post this in the right section, I have limited sections i can paste owing to the fact that am still a junior member and my posts aren't up to 10. I have an sgh-t999 samsung galaxy s3, that is the snapdragon chipset type. I would love to update the whole firmware to 4.3 boatloader, baseband and so on just dat i've only succeeded in updating the baseband to the latest but not the boatloader cos it will involve downloading the whole firmware and am scared of this knox security stuff imbeded in 4.3 and another thing is that i have a slow network which might cause broken and corrupt downloads. My main problem is that when ever i flash any kitkat custom rom, that is all this weekly, nightlies and so on roms, am always having this persistent cannot connect to the camera error which i have searched for a fix to no avail. Ok look at how I have tried to fix it, i copied the camera data of a touchwhiz rom to replace the kitkat own but no changes, have tried restarting and wiping but still same problem. I happened to come across this beautiful rom ie [D2LTE]
~~AICP~~4.4.4----{5.0}---(RELEASE)-JUN-25 rom which i so much love and discovered that it has same problem. Seriously if it were just the bluetooth, i wouldn't have any problems but the camera is ab essential somethhing i can't stay with. Is this problem because am flashing a kitkat custom rom without an updated boatloader or is it particular to the rom? I need some help plz. How do i have a long standing solution to it?

dikachik1 said:
Am so sorry mods if i didn't post this in the right section, I have limited sections i can paste owing to the fact that am still a junior member and my posts aren't up to 10. I have an sgh-t999 samsung galaxy s3, that is the snapdragon chipset type. I would love to update the whole firmware to 4.3 boatloader, baseband and so on just dat i've only succeeded in updating the baseband to the latest but not the boatloader cos it will involve downloading the whole firmware and am scared of this knox security stuff imbeded in 4.3 and another thing is that i have a slow network which might cause broken and corrupt downloads. My main problem is that when ever i flash any kitkat custom rom, that is all this weekly, nightlies and so on roms, am always having this persistent cannot connect to the camera error which i have searched for a fix to no avail. Ok look at how I have tried to fix it, i copied the camera data of a touchwhiz rom to replace the kitkat own but no changes, have tried restarting and wiping but still same problem. I happened to come across this beautiful rom ie [D2LTE]
~~AICP~~4.4.4----{5.0}---(RELEASE)-JUN-25 rom which i so much love and discovered that it has same problem. Seriously if it were just the bluetooth, i wouldn't have any problems but the camera is ab essential somethhing i can't stay with. Is this problem because am flashing a kitkat custom rom without an updated boatloader or is it particular to the rom? I need some help plz. How do i have a long standing solution to it?
Click to expand...
Click to collapse
Are you getting force close?
Sent from my GT-I9100G using XDA Premium 4 mobile app

dikachik1 said:
Am so sorry mods if i didn't post this in the right section, I have limited sections i can paste owing to the fact that am still a junior member and my posts aren't up to 10. I have an sgh-t999 samsung galaxy s3, that is the snapdragon chipset type. I would love to update the whole firmware to 4.3 boatloader, baseband and so on just dat i've only succeeded in updating the baseband to the latest but not the boatloader cos it will involve downloading the whole firmware and am scared of this knox security stuff imbeded in 4.3 and another thing is that i have a slow network which might cause broken and corrupt downloads. My main problem is that when ever i flash any kitkat custom rom, that is all this weekly, nightlies and so on roms, am always having this persistent cannot connect to the camera error which i have searched for a fix to no avail. Ok look at how I have tried to fix it, i copied the camera data of a touchwhiz rom to replace the kitkat own but no changes, have tried restarting and wiping but still same problem. I happened to come across this beautiful rom ie [D2LTE]
~~AICP~~4.4.4----{5.0}---(RELEASE)-JUN-25 rom which i so much love and discovered that it has same problem. Seriously if it were just the bluetooth, i wouldn't have any problems but the camera is ab essential somethhing i can't stay with. Is this problem because am flashing a kitkat custom rom without an updated boatloader or is it particular to the rom? I need some help plz. How do i have a long standing solution to it?
Click to expand...
Click to collapse
As you have installed custom recovery so I feel it might have increased your warranty count and as far flashing 4.3 rom, I don't think if you flash root66 of latest NC2 build is going to harm as only thing that you will not be /should not flash older firmware in Odin as it will brick your device but you will be able to flash older custom Rom in recovery without any issues
With this you will be enjoying latest bootloader and modem and use all 4.4 Rom without issues.
For camera issue, you download other camera from play store and try as I used Google camera without issues on this Rom but I am on latest bootloader and modem.

Something like a force close
captaindeep said:
Are you getting force close?
Sent from my GT-I9100G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not exactly cos when i tap on the camera icon, the error message just appears ie cannot connect to the camera, restart camera or ok. When u click on restart, the camera just restarts but does same thing but if u click on ok, the camera just closes.

Related

wifi do not turn on

Strange things happen to my i9195... suddenly out of the blue,wifi won't turn on neither from quick settings panel nor the settings itself...
Everything else works as it should(data,bluetooth,airplane,gps,sound etc) but the wifi setting tries to turn on but immediately turns of. anyone had this problem?
and more important... a solution??????????
Which rom are you on? You could try reflashing a rom to clear any possible software issues
yes try reflash rom
Whosat said:
Which rom are you on? You could try reflashing a rom to clear any possible software issues
Click to expand...
Click to collapse
citymen34 said:
yes try reflash rom
Click to expand...
Click to collapse
thanks guys for your replies...
i was on stock rooted xxuamf4, i flashed both xxuamh3 and xxuamg8 (these two i had already downloaded) but problem remained. just to eliminate software issue , as a last resort i flashed CM 10.1.3 and magically my device was fully functional again( by the way ..:good: to CM...).
So WTF? i 'll try later to flash a stock non rooted fw and see what will happen...
p.s : anyone know how to change baseband? in my sgs3 mini i used to flash different modem for that. what works for this device?
p.s 2 : thanks again for your time guys!:good:
flashing back stock firmware , problem reappeared! it seems something has to do with knox , because every time i try to open wifi a toasted notification appears "prevention information... the device as detected...bla...bla...bla"
the thing is that if i root my phone and completely delete knox,knox agent,store and container agent, the notification stops but the wifi setting still cannot be enable.
any ideas????
flashing back stock firmware , problem reappeared! it seems something has to do with knox , because every time i try to open wifi a toasted notification appears "prevention information... the device as detected...bla...bla...bla"
the thing is that if i root my phone and completely delete knox,knox agent,store and container agent, the notification stops but the wifi setting still cannot be enable.
any ideas????
Back to report that re-rooting with arco's method but with rootkit v2 (that includes kernel) seems to solve the issue! the steps i follow was :
1) gain root
2) install cwm recovery
3) with es explorer delete knox store,knox agent, container agent (both apk and odex files)
4) reboot to cwm recovery
5) clear cache and davlik cache
6) reboot and RESURRECTION!!!:good:
WiFi and Modem Issue
hi guys. i'm sorry for asking my question here,i have i9192 & my wifi do not turn on. i flash various version of official rom, but i cant solve this problem. I flash (MH2 ,MF7 ,MF9 and MJ2...) build number & CSC are change but Baseband version remain constant and don't change.
how can i flash modem( NON_HLOS.bin)...?
i root my phone so many time with Rootkit v2 and do all wipes for clean flash... but no successive achieve
how can i repair my WiFi and Bluetooth?
tighoory said:
hi guys. i'm sorry for asking my question here,i have i9192 & my wifi do not turn on. i flash various version of official rom, but i cant solve this problem. I flash (MH2 ,MF7 ,MF9 and MJ2...) build number & CSC are change but Baseband version remain constant and don't change.
how can i flash modem( NON_HLOS.bin)...?
i root my phone so many time with Rootkit v2 and do all wipes for clean flash... but no successive achieve
how can i repair my WiFi and Bluetooth?
Click to expand...
Click to collapse
i think it's a kernel related issue. But first in order to eliminated hardware problem possibility, try to flash a cm rom. If your wifi and bluetooth works then you can be sure it's not a hardware failure. in my case flashing a different kernel solved the issue.
p.s : if you find a way to change baseband version ,please share the way!!!
tighoory said:
hi guys. i'm sorry for asking my question here,i have i9192 & my wifi do not turn on. i flash various version of official rom, but i cant solve this problem. I flash (MH2 ,MF7 ,MF9 and MJ2...) build number & CSC are change but Baseband version remain constant and don't change.
how can i flash modem( NON_HLOS.bin)...?
i root my phone so many time with Rootkit v2 and do all wipes for clean flash... but no successive achieve
how can i repair my WiFi and Bluetooth?
Click to expand...
Click to collapse
you need flash same version Kernal file, example: when you finished flash MH2 stock firmware, if wifi shotdown, just flash MH2's Kernal file, file size around 7MB
hey hi
even i have the same error while turning on wi-fi prevention information blah blah
can you be brief how did you solved dat issue. it ll be very helpful
saiprasadap92 said:
hey hi
even i have the same error while turning on wi-fi prevention information blah blah
can you be brief how did you solved dat issue. it ll be very helpful
Click to expand...
Click to collapse
the solution for me was more or less "flashing rooted arco's kernel" . but my model is 9195. i honestly don't know if there is one for 9192 ,but if i were you i would search for one!
vriz27 said:
the solution for me was more or less "flashing rooted arco's kernel" . but my model is 9195. i honestly don't know if there is one for 9192 ,but if i were you i would search for one!
Click to expand...
Click to collapse
yeah thanks fa the reply . ill search for my phone and if you get the same for my phone do let me know
I have problem whith my s4 mini.. I9192 dual sim
Baseband : Nd1
When i want to connectt to wifi i enter password.. As soon as i hit the connectt button wifi signal will desappear... I updated the frameware but no sucsess...
How to solve?
Is it hardware issue?
Same problem for me (1st post): new i9195 with latest XXUCNK1, never flashed before,
install twrp and make a backup, install CM-12.1 and CM-13 without any issue,
After restore to KK using my twrp backup I can't turn on wifi,
solution was to flash Modem_I9195XXUCNK1.tar from modem thread.
I notice that twrp doesn't restore previous modem I update to XXUCOL1

Wifi issue on AOSP Roms

Hi guys,
I have had the s2,s3,galaxy nexus,original note and i am used to flashing and modifying,but i have a serious issue with the note 2.
The problem is whenever i flash AOSP rom(cm,aokp,pa) my wifi would not connect.It shows the name of the network and when i click conenct nothing happens.Flashing back TW rom fixes it,wifi works like a charm. I've done full wipes but it doesn't seem to resolve the issue.I tried different kernels,but that doesn't help either.
So I am stuck at TW roms and i hate that.Anyone has any ideas?
You can try options 2 and 3 from this thread.
Thanks for your reply,but i tried this and it didn't solve my problem.
Anyone?
spookhc said:
Anyone?
Click to expand...
Click to collapse
I Have the same problem...
Not sure that it will help you but I read something yesterday about this issue.
The solution was to NOT restore your Google profile during first boot so you should full wipe and try again.
Primokorn said:
Not sure that it will help you but I read something yesterday about this issue.
The solution was to NOT restore your Google profile during first boot so you should full wipe and try again.
Click to expand...
Click to collapse
This actually has nothing to do with the problem.
After a few days I finally found the cause ,and therefore,a decision to the problem.
It is the bootloader from 4.3 sammy leaks.It seems that this new leaks(probably the reason being KNOX) cause malfunction of wifi in aosp roms.What i did was ODIN flash stock MG1 from sammobile .This brought back stock recovery so i had to flash TWRP again and it solved the issue for me.
Before that i had tried changing roms,kernels,recovery,modems and nothing worked so I am pretty sure it is the new 4.3 leaks bootloader.
Some people will say that it can\t be the issue because they are using 4.3 sammy and do not experience the same problem on aosp roms,but i think thats because they flash it through CMW ,which doesn't change bootloader,while flashing through ODIN does.
With my Note2 this is not the solution. I've tried everything. What you said, move file "pit" ..... but nothing. I can not connect wifi. The connection does not appear region Spain, and have opted to choose europe, but neither. I do not know to do. CM 10.1 also does not work WIFI. In Stock ROM or Custom ROM works fine fine, but in ROM CM 10.1, 10.2, AOKP don't work.
spookhc said:
This actually has nothing to do with the problem.
After a few days I finally found the cause ,and therefore,a decision to the problem.
It is the bootloader from 4.3 sammy leaks.It seems that this new leaks(probably the reason being KNOX) cause malfunction of wifi in aosp roms.What i did was ODIN flash stock MG1 from sammobile .This brought back stock recovery so i had to flash TWRP again and it solved the issue for me.
Before that i had tried changing roms,kernels,recovery,modems and nothing worked so I am pretty sure it is the new 4.3 leaks bootloader.
Some people will say that it can\t be the issue because they are using 4.3 sammy and do not experience the same problem on aosp roms,but i think thats because they flash it through CMW ,which doesn't change bootloader,while flashing through ODIN does.
Click to expand...
Click to collapse

[Q] Need to downgrade, how?

Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.
nelson2006 said:
Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.
Click to expand...
Click to collapse
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.
snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
I haved tried the first two steps and no luck at all. Maybe this weekend I'll try the third one. Thank you for the reply.
snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
RoyaLKurTx3 said:
On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.
Click to expand...
Click to collapse
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.
nelson2006 said:
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.
Click to expand...
Click to collapse
The problem, in fact is a fault in the hardware problem. If it's still under warranty, request a new phone.

GPS not working on SlimKat 4.4.4

Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.

Need help on Flashing a recovery for sprint L520

Someone showed me the thread with the 12.1 cm rom and the .img for the recovery is it okay if I use flashify to put the recovery on my phone instead of using odin after rooting? Or does someone have a .tar recovery for the L520 in a drop box somewhere? also do I need to update my firmware before flashing a rom? I think I'm on firmware na7 on 4.2.2
it's fine, trust me use flashify. Odin doesn't flash .img files. No, you don't need to update your firmware, it's going to be flashed over anyways.
Seemed to work fine. That cm 12.1 rom still working okay for you?
There's a few little annoyances but it's working okay otherwise. I get an exclamation point by my bars sometimes and have to reset the apn to fix it. GPS has some issues so it's become more a roadmap than actual guidance and I can't send mms but that's not really an issue as I have unlimited data and can just facebook messenger as a workaround. I hope that these issues get fixed but I understand that alot of 5.1 roms have issues with the exclamation point thing and even some unrooted 5.1 phones have the problem. It would be nice to see a fix for these issues but I don't see anyone making any more roms for this phone and the guy that made this rom seems to have landed a job with cyanogenmod and is too busy to update this rom. What a shame but at least I have 5.1 now.
Hmm I suppose I'll stay at 4.2.2 till I feel like flashing 12.1 thanks for all the info. You don't have any overheating issues or random restarts right? Also how does the GPS not work well?
No overheating or random restarts. All things considered its a pretty smooth rom if just a little incomplete. I only tried using the GPS once and it came up with my location and the route for where I needed to go but when i was driving along the GLS was not updating my location. It may have been just a one time thing, idk, I havent needed to use GPS since.
Cool do you know a way to go back to stock if I don't like the cm 12.1 rom?

Categories

Resources