Cm11 "cannot connect to camera", permanent fix? - Galaxy S III Q&A, Help & Troubleshooting

Hi,
I'm currently running CM11 nightly (20141206) and haven't been running stock since at least a year and a half (read: I don't remember the last stock version I were running).
I have the common issue where Android cannot connect to the camera. The often posted "camera restart" does the trick, but I've read various places that flashing the latest stock rom and opening the camera once fixes this issue permanently, even after flashing custom roms again. Since my phone is laggy and I've been dirty flashing for a long time I figure it is time for a clean flash anyways. Is it correct that this would fix the issue?
If so, how should I go about doing it? I remember reading about an upgraded EFS partition in newer roms that aren't compatible with certain modems etc. My current baseband version is I9300XXEMB6. Is this something I need to take into account? (if I backup the current EFS and something goes wrong in upgrading to the newer version, will I be able to restore it afterwards?)
Also, does the latest stock roms contain Knox (or what it's called)? I suppose I don't want that?
I know there are bits and pieces spread around on the forum, but if someone could outline the process for me, or even better, point me towards some step by step guide covering the above, that would be much appreciated.
In advance, thanks a bunch!
-AndyGizzle

Trying a tiny little bump on this one

Related

Internet not working after flashing RR Rom

i have flashed the latest version of RR 5.0.8 rom but for some reason my internet is not working though wifi is connecting properly ..i have tried factory reset and re installing the rom but the problem still persists ..can someone please help me out ?
hej
try full wipe
A longer friendly answer
tr!ckst3r said:
i have flashed the latest version of RR 5.0.8 rom but for some reason my internet is not working though wifi is connecting properly ..i have tried factory reset and re installing the rom but the problem still persists ..can someone please help me out ?
Click to expand...
Click to collapse
ROMs are tricky things in my experience.
I've tried most of them and most of the ones I tried have really bad flaws - for my phone.
When one doesn't go so well for you - like the RR ROM, it's time to move on and try another.
After following the instructions of course, like full wipe, cache, blah blah blah. Try it twice, the second time following instructions really closely.
I found the PA and offspring to work really well - for my phone.
In the end, play and learn. It's fun and really difficult to completely wreck your phone.
Pete
^^^
Might be a longer friendlier answer but the answer is essentially nonsense. The OP has a specific problem. Posting waffle like you just did smacks of wanting to get your post count up because it doesn't help the OP one bit.
OP - You haven't given us anywhere near enough info to help you. Connectivity normally just doesn't go away all of a sudden unless you've made changes to your setup, or there's a carrier-side issue causing the problem.
What have you done with the phone recently setup-wise, have you been messing around with RIL's or modems ? If it's the latter, then you need to try more modems. If it's neither, I'd be going back to stock (a rom for your carrier, so you get a modem that should work), then reinstall the rom you're using. If that doesn't work, flash the 3 part firmware in Hopper8's 'Odin troubleshooting' thread stickied in General (this will wipe your phone, backup first), then flash stock for your carrier, then reinstall custom rom.
If the problem persists after all that, then you're looking at carrier-side issues or perhaps even a hardware issue. WiFi working & data not have no bearing on each other as WiFi drivers are in the kernel & separate to data connectivity.
We would need more information as to how did you flash the new ROM? Are you using a separate Kernel? Which GAPPS version did you flash?
I am also on the RR 5.0.8 with Dorimanx kernel. Also, I used the light version of GAPPS for flashing. Try using the light version if you have not used it.

[Q] Problematic s4 (4.4.2)

Hi. I've got a challenge for the experts
I have a galaxy s4 (i9505) and currently on cyanogenmod 11-20140414-nightly so its running on 4.4.2
The minute i got my phone, i put foxhound rom and was on4.2.2 that time and everything was fine. It was about june last year. A couple of weeks ago, i decided to have a go at other roms or update to 4.4.2 so i tried foxhound rom that ran on4.4.2. This is when the problems started. The first problem was the signal was greatly affected that i could not get any signal indoors. So i tried several other roms like omega rom, cyanogenmod, wanamlite, wicked, virgin rom and several others but none of them perfectly worked. I always cleared cache and restore factory settings but still there were problems. On some roms the camera wont work as if there is another app using it. On others, i cant get any signal even though im in an area where i used to get strong signals. Another big problem is that i cant make a call! The screen goes black and can't do anything until the call gets disconnected. I can't use voice services like skype, ym, everything that uses the mic as if there is an app or service using it. When i put the jack to use the headset, i dont get the notification that im on headset unlike before.
So i decided to use stock rom on 4.3. Now i have even bigger problems. In addition to the previous problems stated, the wifi won't turn on but i can get a signal outside. Even though i have already removed the microsd card and wiped cache and restore to factory settings, the phone still says that the device was modified so i can't really return it even though it is still under warranty.
So now i decided to root it again and temporarily use cyanogenmod since the wifi works, texts and the internet works.
Btw, youtube doesnt work also. It doesnt play.
Sorry for the vrry long post but i just want to give much info as possible..
Thanks so much
Noypi14 said:
Hi. I've got a challenge for the experts
I have a galaxy s4 (i9505) and currently on cyanogenmod 11-20140414-nightly so its running on 4.4.2
The minute i got my phone, i put foxhound rom and was on4.2.2 that time and everything was fine. It was about june last year. A couple of weeks ago, i decided to have a go at other roms or update to 4.4.2 so i tried foxhound rom that ran on4.4.2. This is when the problems started. The first problem was the signal was greatly affected that i could not get any signal indoors. So i tried several other roms like omega rom, cyanogenmod, wanamlite, wicked, virgin rom and several others but none of them perfectly worked. I always cleared cache and restore factory settings but still there were problems. On some roms the camera wont work as if there is another app using it. On others, i cant get any signal even though im in an area where i used to get strong signals. Another big problem is that i cant make a call! The screen goes black and can't do anything until the call gets disconnected. I can't use voice services like skype, ym, everything that uses the mic as if there is an app or service using it. When i put the jack to use the headset, i dont get the notification that im on headset unlike before.
So i decided to use stock rom on 4.3. Now i have even bigger problems. In addition to the previous problems stated, the wifi won't turn on but i can get a signal outside. Even though i have already removed the microsd card and wiped cache and restore to factory settings, the phone still says that the device was modified so i can't really return it even though it is still under warranty.
So now i decided to root it again and temporarily use cyanogenmod since the wifi works, texts and the internet works.
Btw, youtube doesnt work also. It doesnt play.
Sorry for the vrry long post but i just want to give much info as possible..
Thanks so much
Click to expand...
Click to collapse
So, which type of rom do you want to be on, assuming most of the things work properly? I don't want to try to address all those issues because there are different ones for the different setups and would take forever. Most likely signal issues are from not using a matched modem with the firmware / rom you are running. Do you know the original carrier / region the phone is from so we can make sure you get the right stuff installed?
Please provide details on the the currently installed baseband version. Also, what is the last official version of Samsung's software that you installed via Odin or OTA (not via custom rom)?
es0tericcha0s said:
So, which type of rom do you want to be on, assuming most of the things work properly? I don't want to try to address all those issues because there are different ones for the different setups and would take forever. Most likely signal issues are from not using a matched modem with the firmware / rom you are running. Do you know the original carrier / region the phone is from so we can make sure you get the right stuff installed?
Please provide details on the the currently installed baseband version. Also, what is the last official version of Samsung's software that you installed via Odin or OTA (not via custom rom)?
Click to expand...
Click to collapse
Thanks for your reply.
The current cyanogenmod is fine although i prefer the virgin rom. but i can go back to virgin once the problems have been rectified.
I agree that the signal issue has something to do with the modem so i tried different modems using odin but the XXUBMEA wouldnt change despite trying several modems and several times.
The phone is on three network (uk) with its current baseband 19505XXUBMEA.
The official rom i tried was on 4.3 and kies said it was the latest
Thanks again
Alright, I'm with ya so far. I'll look into the rom situation when I get back in front of the PC, but the trick with updating the modem is you gotta flash it twice in a row before you reboot unless you flash official firmware.
es0tericcha0s said:
Alright, I'm with ya so far. I'll look into the rom situation when I get back in front of the PC, but the trick with updating the modem is you gotta flash it twice in a row before you reboot unless you flash official firmware.
Click to expand...
Click to collapse
Thanks again for replying.
What i havent actually tried (which i'm reading at the moment) is the formatting of data under the advanced options on twrp. I dunno if it will make a difference say i try a new rom. I don't mind trying and starting from scratch. Like format data then install a new rom. Do u think this will make a difference? (will this be similar to formatting a dard drive on a pc before installing windows?)
What i suspect is there is nothing wrong with the roms i've tried but something in the installation got messed up and remains there even after wiping the data.
I think i have tried doing it twice only to find out that it didnt change the modem despite odin saying pass.
Should i format data then install a fresh rom?
Hard
but challeng refused
Ok, so there is something odd here. If you had flashed the official 4.3 via Odin, your modem would have changed to a newer one. The one you have is still a 4.2.2 one. Or were you referring to the last stock rom that you loaded with a custom recovery? Also, which recovery are you using?
Try this modem via Odin:
http://d-h.st/Kwv
Install Guide:
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Reference thread: http://forum.xda-developers.com/showthread.php?t=2192025
Let's see if that doesn't help anything and go from there.
If you have issues with wifi, there is a wifi fix to be had in the reference thread. Remember to flash that through the Phone slot if needed.
thanks again.
i can't exactly remember what modem i had when i flashed it with the official 4.3 using odin. but my guess would be the XXUBMEA. most of the custom roms i've tried had this modem anyway. some had no problems with 3g signal.
i am using twrp.
i don't want to play around with the modem yet as the 3g and wifi signals are working fine on cyanogenmod. its the call and video that's not working that i want to sort out.
do u think if i reflash by formatting data would clear out the problems i specified earlier? i don't mind trying this if u think it will make a difference.. tthanks.
es0tericcha0s said:
Ok, so there is something odd here. If you had flashed the official 4.3 via Odin, your modem would have changed to a newer one. The one you have is still a 4.2.2 one. Or were you referring to the last stock rom that you loaded with a custom recovery? Also, which recovery are you using?
Try this modem via Odin:
http://d-h.st/Kwv
Install Guide:
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Reference thread: http://forum.xda-developers.com/showthread.php?t=2192025
Let's see if that doesn't help anything and go from there.
If you have issues with wifi, there is a wifi fix to be had in the reference thread. Remember to flash that through the Phone slot if needed.
Click to expand...
Click to collapse
Noypi14 said:
thanks again.
i can't exactly remember what modem i had when i flashed it with the official 4.3 using odin. but my guess would be the XXUBMEA. most of the custom roms i've tried had this modem anyway. some had no problems with 3g signal.
i am using twrp.
i don't want to play around with the modem yet as the 3g and wifi signals are working fine on cyanogenmod. its the call and video that's not working that i want to sort out.
do u think if i reflash by formatting data would clear out the problems i specified earlier? i don't mind trying this if u think it will make a difference.. tthanks.
Click to expand...
Click to collapse
The custom roms you've been using don't install a modem with them, so that would be why you've been on the same one for a bit. Often times the stock rom is a little more picky about which modem it likes best, though this varies by phone and update. What call issues are you having? There were so many issues listed for various things on the first post that I had trouble sorting which problem for which rom (not criticizing, just making sure we're on the same page). And as far as videos go, is it just YouTube that isn't working right or any type of video playback? If it is just YouTube - is it force closing, not loading searches or videos, or some other problem?
es0tericcha0s said:
The custom roms you've been using don't install a modem with them, so that would be why you've been on the same one for a bit. Often times the stock rom is a little more picky about which modem it likes best, though this varies by phone and update. What call issues are you having? There were so many issues listed for various things on the first post that I had trouble sorting which problem for which rom (not criticizing, just making sure we're on the same page). And as far as videos go, is it just YouTube that isn't working right or any type of video playback? If it is just YouTube - is it force closing, not loading searches or videos, or some other problem?
Click to expand...
Click to collapse
thanks again for your interest.
the issue about the modem is somehow clear. thanks for clearing that up.
i think it is better to tackle the problems i have in my current setup rather than the previous problems. so, as previously mentioned, i am on cyanogenmod 11 (on 4.4.2). here are some of the problems i am aware of or rather, those that i have experienced:
1. calls - whenever i dial a number, the screen goes black as if the phone is next to my ear (could there be something wrong with the proximity sensor? i haven't done anything to rectify this yet though. when this happens, i can't do anything as the seems to hang although i could see the call timer working. during that call however, i can't hear a sound nor the person i just rang. same thing happens when someone calls me. my phone vibrates (because there is another problem with the sound which i will discuss next) and when i answer it, i hear no sound and the screen goes black and i couldn't do anything with the phone. i have to wait till the caller disconnects before the phone becomes useable again.
i tried calling using viber and the same thing happens.
2. sound - phone is muted even though all the volume controls are midway or almost 100%. i tried changing the ringing tone but i don't hear any sound at all. normally, when i switch to a different ringtone, it should give me a preview of what the chosen sound is like.
3. videos - it doesn't work. when i go to youtube, it opens up the site, opens the selected youtube clip, tries to play it but pauses then tries to play again then pauses until i get a message saying "there was a problem while playing. touch to retry."
so far these are the problems i have faced.
sorry for the long post again.
Hmm. Seems weird that you are having so many issues that most others aren't having, at least not since some of the earlier builds. During the install of CM, did you wipe /system? If not, I definitely would just start fresh. Install the most up to date modem. Wipe everything (system, data, cache, dalvik). Use the most up to date CWM (I like TWRP most of the time, but since CM says you should try CWM before reporting issues, it's one of those things...) Some Samsung proximity sensors aren't that accurate and really don't work well with CM. Other users reported that issue i the main CM thread for your phone, but was definitely not prevalent. I had a Samsung phone that I couldn't use a tempered glass screen protector with as they had an app to install to test to see how sensitive it was and mine didn't pass the test, though it worked for everything else.
As far as the video bug. It affected some earlier builds and other roms based off of CM but I hadn't seen anyone commenting about it for a bit so can't imagine it still being a common issue as that's a deal breaker for most. It might just be easier at this stage to either go back to stable CM 10.2 or try another rom altogether, such as Slim.
es0tericcha0s said:
Hmm. Seems weird that you are having so many issues that most others aren't having, at least not since some of the earlier builds. During the install of CM, did you wipe /system? If not, I definitely would just start fresh. Install the most up to date modem. Wipe everything (system, data, cache, dalvik). Use the most up to date CWM (I like TWRP most of the time, but since CM says you should try CWM before reporting issues, it's one of those things...) Some Samsung proximity sensors aren't that accurate and really don't work well with CM. Other users reported that issue i the main CM thread for your phone, but was definitely not prevalent. I had a Samsung phone that I couldn't use a tempered glass screen protector with as they had an app to install to test to see how sensitive it was and mine didn't pass the test, though it worked for everything else.
As far as the video bug. It affected some earlier builds and other roms based off of CM but I hadn't seen anyone commenting about it for a bit so can't imagine it still being a common issue as that's a deal breaker for most. It might just be easier at this stage to either go back to stable CM 10.2 or try another rom altogether, such as Slim.
Click to expand...
Click to collapse
i know. i don't really want to blame these issues i've mentioned to the rom i am using or have tried. perhaps there was something i did not do or overdid that messed it all up. the cynagenmod 10 (the stable version for my s4 model) had similar issues as the cm11. so i suspect the problem i've created still lingers within my phone that messes up a lot of things.
during installation, i did wipe the system, data, cache and dalvik which i found in the advanced menu.
the thing is, everything else worked fine when i was on 4.2.2 (like the proximity sensors, videos, sounds, etc) so as i said earlier, i don't want to blame it on the roms.
i might have another go on the slim rom tonight but use CWM instead of TWRP.
thanks again for your interest and help
Noypi14 said:
i know. i don't really want to blame these issues i've mentioned to the rom i am using or have tried. perhaps there was something i did not do or overdid that messed it all up. the cynagenmod 10 (the stable version for my s4 model) had similar issues as the cm11. so i suspect the problem i've created still lingers within my phone that messes up a lot of things.
during installation, i did wipe the system, data, cache and dalvik which i found in the advanced menu.
the thing is, everything else worked fine when i was on 4.2.2 (like the proximity sensors, videos, sounds, etc) so as i said earlier, i don't want to blame it on the roms.
i might have another go on the slim rom tonight but use CWM instead of TWRP.
thanks again for your interest and help
Click to expand...
Click to collapse
Do you have a screen protector or anything like that? Sometimes if it isn't laying on the screen right or dirt gets around it, it can cause issues. There's also a way to pop out the actual proximity sensor and clean between the part and the little piece of clear glass on the back of the front piece of glass that can help too if it ends up being hardware related.
es0tericcha0s said:
Do you have a screen protector or anything like that? Sometimes if it isn't laying on the screen right or dirt gets around it, it can cause issues. There's also a way to pop out the actual proximity sensor and clean between the part and the little piece of clear glass on the back of the front piece of glass that can help too if it ends up being hardware related.
Click to expand...
Click to collapse
I put the screen protector when i got the phone and i don't see any visible dirt so i wouldn't want to blame it either. Although i did read about the screen protectors causing problems. But the thing is, even youtube or any videos do not play. Even any sound.
I've tried the slimkat rom by following the developers' instructions and still no youtube, no sound, can't make a call as i can't hear the person i'm calling nor can that person hear me.
Any other suggestions on what to do? I don't mind going back to stock as long as i get all the features back. I went to official 4.3 before but had more severe issues. Or perhaps i did it wrong?
Thanks..
Videos are another issue, but I still think the call problems and such are modem related. What I would do would be to wipe everything, then use Odin to install official Kit Kat, then test this stuff out and see if it works. If so, then you can do a nandroid and redo recovery and try the roms again, then if they still have that issue then your phone just doesn't cooperate with CM roms or something weird like that. If it doesn't work even after official 4.4.2, then there's probably something else going on, possibly hardware related.
es0tericcha0s said:
Videos are another issue, but I still think the call problems and such are modem related. What I would do would be to wipe everything, then use Odin to install official Kit Kat, then test this stuff out and see if it works. If so, then you can do a nandroid and redo recovery and try the roms again, then if they still have that issue then your phone just doesn't cooperate with CM roms or something weird like that. If it doesn't work even after official 4.4.2, then there's probably something else going on, possibly hardware related.
Click to expand...
Click to collapse
Thanks.
Got hold of the official 4.4.2 and flashed it via odin. Failed. But tried again and now working fine. Sound is back, video is back as well as calls. Just the annoying google search failing all the time.
The baseband it has is I9505XXUFNC9. i didn't install any modem in odin though. Just flashed in the pda section the tar file
Now i don't know whether to root this again and try custom roms or leave it as it is. I saw knox by the way but haven't installed it. Or is it pre installed? I have little knowledge about knox

[Q] Cannot Install new ROM, Status 7 error

So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?

Ordered i9300 from eBay - need help to understand what's going on

Hi guys,
I've ordered a new, unlocked i9300 from eBay, and I had some adventures with it:
I've unpacked it, inserted my SIM, powered it on, and found out that the phone always thinks that I'm roaming. Instead of trying to understand what's going on, I though: "I'll just install CyanogenMod and everything will be good".
I've installed CyanogenMod 10.2 (latest stable build), only to find out that my SIM is not being detected at all. It says that Baseband is unknown, IMEI and related are unknown as well.
After trying lots of stuff, I gave up and decided to return to stock ROM (4.3). While trying to do that, I bricked my phone, and the only thing I could do is enter Odin mode.
After reading dozens of tutorials and trying lots of stuff, I ended up flushing GT-I9300_mx_20120329.pit, and that unbricked my phone.
I successfully flashed Android 4.3. This version detected my SIM, displayed the Baseband/IMEI, but it didn't connect to the cellular network. I could scan for available networks, but when I chose my network manually, it said "Selected network not available ".
I tried to flush alternative modems, but all it did is making things worse. Usually it made the phone behave like with CyanogenMod, i.e. Baseband/IMEI are unknown.
Again, after trying lots of stuff, I tried to flush Android 4.1.2. That made no change until I've stumbled on this thread. Flushing Patched_Modem_I9300XXEMG4.zip made my networking work again, and restored it to behave exactly like it did initially. Again, the phone thinks that I'm roaming all the time, but at least it works.
So currently, I have two issues:
My phone always thinks I'm roaming. Is there a fix for it?
And more important: currently, I cannot install anything other than Android 4.1.2!
Could you please shed some light on the situation? What happens with my phone? Why does it think I'm roaming? Why does the SIM work only with Patched_Modem_I9300XXEMG4? How can I make other ROMs (e.g. CyanogenMod) work?
Thanks, any help is much appreciated!
9999 :) said:
Hi guys,
I've ordered a new, unlocked i9300 from eBay, and I had some adventures with it:
I've unpacked it, inserted my SIM, powered it on, and found out that the phone always thinks that I'm roaming. Instead of trying to understand what's going on, I though: "I'll just install CyanogenMod and everything will be good".
I've installed CyanogenMod 10.2 (latest stable build), only to find out that my SIM is not being detected at all. It says that Baseband is unknown, IMEI and related are unknown as well.
After trying lots of stuff, I gave up and decided to return to stock ROM (4.3). While trying to do that, I bricked my phone, and the only thing I could do is enter Odin mode.
After reading dozens of tutorials and trying lots of stuff, I ended up flushing GT-I9300_mx_20120329.pit, and that unbricked my phone.
I successfully flashed Android 4.3. This version detected my SIM, displayed the Baseband/IMEI, but it didn't connect to the cellular network. I could scan for available networks, but when I chose my network manually, it said "Selected network not available ".
I tried to flush alternative modems, but all it did is making things worse. Usually it made the phone behave like with CyanogenMod, i.e. Baseband/IMEI are unknown.
Again, after trying lots of stuff, I tried to flush Android 4.1.2. That made no change until I've stumbled on this thread. Flushing Patched_Modem_I9300XXEMG4.zip made my networking work again, and restored it to behave exactly like it did initially. Again, the phone thinks that I'm roaming all the time, but at least it works.
So currently, I have two issues:
My phone always thinks I'm roaming. Is there a fix for it?
And more important: currently, I cannot install anything other than Android 4.1.2!
Could you please shed some light on the situation? What happens with my phone? Why does it think I'm roaming? Why does the SIM work only with Patched_Modem_I9300XXEMG4? How can I make other ROMs (e.g. CyanogenMod) work?
Thanks, any help is much appreciated!
Click to expand...
Click to collapse
When the phone gets upgraded from 4.1 to 4.3 your efs changes from efs v1 to efs v2 sometimes this upgrade does not go smoothly (as in your case) so then you need to always use a patched modem from version mg4 onwards (not a normal one) if you flash a rom which changes the baseband to anything less than 4.3 then it will not work.You need to keep on mg4 or later to keep signal and because your efs is not fully upgraded properly you need to always use a patched modem and preferably kernel as well.
I am not sure about the roaming issue but if you try patched modem and patched kernel together that might help.Take a look here for some patched modems and kernels and remember you always need to use them >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << You should also be able to use 4.3 roms as long as you use the patched files above ie baseband and kernel.
In general, It would be great if I could use CyanogenMod 10.2.
Should I proceed in the following order? Flush CM -> flush patched kernel -> flush patched modem.
Which of the patched versions should I choose?
Also, what do these versions change? What functionality was patched in these files? Can I read about it somewhere?
Thanks for the help.
9999 :) said:
In general, It would be great if I could use CyanogenMod 10.2.
Should I proceed in the following order? Flush CM -> flush patched kernel -> flush patched modem.
Which of the patched versions should I choose?
Also, what do these versions change? What functionality was patched in these files? Can I read about it somewhere?
Thanks for the help.
Click to expand...
Click to collapse
No the kernel will only work for 4.3 roms not CyanogenMod roms but the patched modems will work.You can try flashing CyanogenMod then the patched modem but CyanogenMod does not include a modem so whatever modem you where on when you flashed CyanogenMod you will keep.
tallman43 said:
No the kernel will only work for 4.3 roms not CyanogenMod roms but the patched modems will work.You can try flashing CyanogenMod then the patched modem but CyanogenMod does not include a modem so whatever modem you where on when you flashed CyanogenMod you will keep.
Click to expand...
Click to collapse
I tried installing CyanogenMod, then flushing some of the patched modems you've linked. Unfortunately, nothing changes - Baseband/IMEI are always unknown.
9999 :) said:
I tried installing CyanogenMod, then flushing some of the patched modems you've linked. Unfortunately, nothing changes - Baseband/IMEI are always unknown.
Click to expand...
Click to collapse
You mean flash not flush.
Also you should be careful to by things like this off ebay, There is a very high chance you brought the phone broken like this but did not notice straight away.
Don't hang around on 4.1.2 as you might get SDS.
Upgrade to 4.3 stock of higher using custom roms with a patched modem of mg4 or higher as stated by tallman43.
Read here for what you or the previous owner has done. Also on stock make sure your csc is correct.
http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289
If you cannot get it to work you need to take it in for repair. Make sure it works on 4.3 before paying.

What is currently the most stable and most current Rom available for the DNA?

I currently have a lollipop rom version 5.1 (3.4.10-Nuk3rn3l) that has many quircks which make my DNA fairly unpleasant to use. I'd like to flash a build that is solidly reliable, even if it means downgrading.
What are my options? It is extremely daunting to wade through the endless posts of this development forum to find one that is stable.
What quirks are you having? Are you on the latest firmware and used the recommended recovery to flash? These HTC phones are very picky and can cause some undesired effects when flashing against recommendations of OP. I would assume you are running @santod040's GPE rom. His roms are pretty darn stable if installed correctly. If you did follow install procedure exactly as recommended and still have issues, try his nusense rom.
Yeah, I'd love to hear what instability issues("quirks") you might be having with my GPE port...I'm unaware of any.
Those who have issues and don't ask about them with logs or details, can't expect much.
You can always go back to a stock Kitkat Rom if the hard work of others isn't appreciated.
Sent from my HTC6525LVW using Tapatalk
santod040 said:
Yeah, I'd love to hear what instability issues("quirks") you might be having with my GPE port...I'm unaware of any.
Those who have issues and don't ask about them with logs or details, can't expect much.
You can always go back to a stock Kitkat Rom if the hard work of others isn't appreciated.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I appreciate all you do and it probably does have something to do with not having the most up to date software. I am experiencing a lot of little things that combine to be very frustrating in day to day use. In no particular order; I cannot send consecutive text messages without cycling airplane mode, the restart option when holding the power button has disappeared, every few days the phone will shut off and will be unable to be turned back on without plugging in a power cable (this has something to do with user input but I have yet to recognize the pattern that causes it), apps will frequently crash, the phone no longer automatically connects to wifi networks, and a few other things.
I don't know what info you would need, my kernel is 3.4.10-NuK3rn3l-dlx-GPE-Lollipop_v2.00 . Build number is LMY470.H6
I love that people are still developing for this phone, I just think a lot of this custom firmware business goes over my head.
Those issues sound like firmware outdated and some odd stuff that only an ruu can fix. Below is the most up to date ruu for this phone. Before you flash, be sure to back everything up to an external storage device (PC, USB otg, etc). After you ruu, flash the recommended recovery in the rom thread and then clean flash the rom (wipe data, cache, system). Do not restore the nandroid backup. It could be something software that is causing the app FCs.
http://forum.xda-developers.com/showthread.php?t=2935556
Edit: I know for a fact the Wi-Fi issue is because of outdated firmware, others might be wrong recovery, but to save the hassle, just ruu to be safe.
Do me a favor: Run "fastboot getvar all" and take a look at line three and six. I am having the exact same issues as you. My line 3 for baseband was version 1.02.01.0818, NOT the 1.02.01.0207 that the latest firmware thread stated it should be. My line 6 (version-main) was blank. After flashing the latest radio zip it now shows a 1.02.01.0207 for baseband and 4.09.605.1 for version-main. This isn't my main phone anymore so its not activated in a way that i can test it. However it may be a starting point for you. I'd be curious if you have the same radios that my phone did.

Categories

Resources