Related
Hello everyone. I received my Verizon SG3 shortly after it came out. I have been doing reading as I am very new to android. This is my first android phone. Previously I had an EnV Touch. Hated that thing, but it did the job. So any who I now have this awesome kick butt phone and it has all the Verizon crap on it I cannot get rid of. I have rooted and the bootloader is unlocked. I used a windows program to gain root and then used EZ unlocker to unlock the bootloader. I have been looking and looking to figure out what rom I want to start with, I want JB, but don't want a lot of bugs ATM as i don't have all that much time to play with flashing and being still so new I don't want to end up with a brick. I tried my harderst to figure this out by reading, but the info seams so spread out, I kinda want to try the CM10 9-6 as I have read it is stable and not many bugs. My main question is about kernels. Am I correct in thinking they will get flashed just like my rom will in ROM manager? Or do I need to flash through CWMR? How do I know what Kernel to use? I have been reading the CM10 takes a different kernel than say synergy or stock. Or will the stock kernel work till I load the proper kernel. If I knew about the kernel and how vital it was to go with the ROM maybe I wouldn't be so paranoid. I have a friend with a GS2 and he told me the kernel has to go with the ROM and if the two don't mach then you could brick. I can't afford a brick my first time around.
If you could give me some advice or point me in the direction of some more reading that would be great.
Thanks
JB
All ROMs come with a kernel in them. Typically you just stay with it unless you want some extra features or what not. There are aosp kernels and kernels based on the stock firmware. If you use a touchwiz based rom you need to use a touchwiz kernel.
I don't think it will brick it if you interchange them. It will just boot loop
Edit: you flash kernels in recovery just like a rom. if you change kernels without changing roms you need to wipe cache and dalvik cache through recovery also.
Sent from my Nexus S 4G using xda premium
Back up your IMEI before flashing anything, alot of horror stories floating around. Development has some fantastic guides. After that, most of the "big gun" rom's here have kernels, and are for the most part consistently the same flash method through recovery. Cwm recovery is solid and reliable, start with that until you feel comfortable enough to venture off. Make sure it's version 6.0.1.2 (regular or touch) for any jelly bean based rom.
Sent from my SCH-I535 using xda premium
I backed up the IMEI with the terminal emulator. So if the error occurred it would restore with the proper IMEI. Should I back it up any other way too?
Also I'm planning on using the Rom manager to flash the Rom. Do you not recommend that or should I do it manually with CWRM?
Thanks for the replies. I'm still getting my feet wet and know all about searching before asking. Used to program dish.
Sent from my Galaxy S3 using Tapatalk.
Your call, depends how paranoid you are! I would flash manually, it's a control thing for me, I know what/how/when all was done. Using 6.0.1.2 touch is awesome, speeds flashing up considerably.
Sent from my SCH-I535 using xda premium
I might have to try the touch. I have standard 6 on there. The one you listed. Rom manager gives me the option to load touch too. Friend uses Rom manager on his s2. Looks to just automate things a little.
What I don't know is if it wipes the appropriate areas first for a clean install or if it's doing it dirty.
Sent from my Galaxy S3 using Tapatalk.
Use the Synergy backup. If you lose your IMEI you just flash it again and it's back. Just make Nandroid backups and flash away. This is my first Android phone too and now I get why people become flash addicts, it's amazing what you can do. It's easy to relock and unroot if need be. Everything is easy if you take it smart and slow.
Sent from my SCH-I535 using Tapatalk 2
Here here!
Sent from my SCH-I535 using xda premium
Just stick to a couple rules and you will be fine. First is backup, backup and backup before flashing. Always stay within the Verizon SGS3 section, Sounds simple but others have made the grave mistake. When flashing kernels, stick to the software, ie flash a JB kernel to a JB rom, flash a ICS kernel to an ICS rom. You should not have any problems but if you do you always have a backup. There are many roms, just flash an try them, make sure to read through the threads to identify any issues that have been discussed. JB roms there are a couple, a TW based JB rom from a T-mobile leak that was ported to VZW SGS3 that works well, there are official and unofficial JB vanilla roms, ie CynogenMod. Stick to those rules, keep a back up, i usually will transfer a copy of my original backup to my pc just in case, and always backup to external sd card. Good luck and have fun.
You can also flash kernels via Odin I believe.
Hi,
I apologize in advance for any "noobish" questions, but I'm new to rooting... and if a solution to my issue is out there, please point me in the right direction - I've seen many people having different approaches to this type of issue, therefore I would like some help getting on the right track
I have a Samsung Galaxy S3 I747M which I have successfully rooted ( I think! ) and installed a custom recovery, but I am still encountering issues flashing custom ROMs...
To get in details to what I did ( chronological order )
- I followed all steps given in this site - http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3/
( looked simple enough in comparison to other processes I've found )
All went has planned until I had to install a custom ROM - CM10 wouldn't install at all and LiquidSmooth would install, but multiple apps wouldn't work properly.
Lucky me, I had done a backup of my current ROM before flashing a custom ROM, therefore I was able of going back to the Rogers ROM.
I assumed the issue would be due to the CWM version not being compatible with CM10 ( and maybe that ws the case with Liquid ) so I ended up installing GooManager and changing my Recovery Mod to TWRP. The issue of not being able of flashing custom ROMs persisted.
So I ended up following what Mr. Robinson posted on http://forum.xda-developers.com/showthread.php?t=1739426
-With Odin I flashed my phone with root66_RWC_I747MVLDLK4.tar.md5
-after reboot GooManager was still installed ( obvious ) so I attempted multiple times to flash custom ROMs without success.
I have removed my external SD card, rebooted and removed battery, etc.
I have been getting in most cases "Status 7" as a error message when trying to flash custom ROMs.
I have SU installed, I have done the "fix permissions",...
What am I doing wrong and/or what am I missing in this process to be able of flashing custom ROMs?
Help would be greatly appreciated!
Thanks in Advance!!
I've also noticed that I have multiple "0" folders in the SD card. For my understanding this is due to trying to install a 4.2 with an old CWM version...
Is it possible that this is what initiated the whole issue?...
So, after searching for a bit I resolved all my issues.. I'm going to post what I did and my current setup in hopes to help other people who have been having trouble getting their Canadian galaxy S3 rolling with a custom ROM. This should apply to any i747m devices, but I have the Rogers one...
For my understanding the beginning of my issues was flashing an old version of CWM. Try to always flash the latest version of CWM or TWRP. I'm currently using the TWRP 4.3.3 WITHOUT ANY ISSUES.
I then flashed AOKP on JB 4.2.1. My phone has been working perfectly since then (besides for some minor known bugs) - make sure to do all the wipes advised on any ROM instructions and you should be fine. You will also need to change the Internet provider settings to reflect your speed and provider.
Sent from my SGH-I747 using xda app-developers app
Just wanted to say thanks for posting a follow-up on how you solved your issue. I'm looking into rooting and custom-rom-ing my Koodo GS3 and so many threads are started and then abandoned. So cheers to you good-guy OP!
fishy007 said:
Just wanted to say thanks for posting a follow-up on how you solved your issue. I'm looking into rooting and custom-rom-ing my Koodo GS3 and so many threads are started and then abandoned. So cheers to you good-guy OP!
Click to expand...
Click to collapse
you can always just hit the "thanks" button
Cheers!
fishy007 said:
Just wanted to say thanks for posting a follow-up on how you solved your issue. I'm looking into rooting and custom-rom-ing my Koodo GS3 and so many threads are started and then abandoned. So cheers to you good-guy OP!
Click to expand...
Click to collapse
Something else. Consider changing your custom recovery from d2can to d2att. The number of ROMs out there for d2att is way higher that d2can ROMs.
Good luck!
Sent from my SGH-I747 using xda app-developers app
Headphone socket issue
There is no sound coming out from the headphones when i insert them....and when i unplug the sound on the speaker doesnt work too..It's NOT A HARDWARE ISSUE cuz i checked that it worked perfectly on the stock rom...but when i flash Roms it doesn't work at all...
PLS HELP!!!!
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Same problem
CZory91 said:
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Click to expand...
Click to collapse
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
bmanderle said:
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
Click to expand...
Click to collapse
It's an AOSP problem based on the firmware of your camera when getting the phone from what I've seen.
http://forum.xda-developers.com/showthread.php?p=37072484#post37072484
Here's the thread I was talking about, however I'm confused about how to go about zipping and unzipping these files. Or even how to get to them to place the files in to begin with considering internal SD card is the only thing that comes up for USB storage. Unless you're supposed to move them in and out from within android.
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
CZory91 said:
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
Click to expand...
Click to collapse
I had the camera problem on MIUI...
Before flashing, I made a backup of my system with CW
I extracted the SlimISP_ZH.bin from my backup and
copied it to my /data directory and it worked fine.
Link: d-h.st/dwx
(I can't post links yet)
maybe... someone post the fix in this forum and make it sticky... lol
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
CZory91 said:
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
Click to expand...
Click to collapse
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
Click to expand...
Click to collapse
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
Click to expand...
Click to collapse
Yes, that is the post. I also tried MB1 out of curiosity, no dice on either of them. I had a perfectly working CM10. I dun goofed :\.
That was my next step (rerooting, installing that firmware AIO, and then installing CM10). However my question is this, what happens when more firmware comes out? I have to re root and start over again?
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
dandydon414 said:
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
Click to expand...
Click to collapse
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
bbqsfire said:
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Hmm, over the past couple days I've tried out a few different ROMs on my girlfriend's S3 here, and on each one I would get this "Could not connect to the camera" error, every single time upon opening the camera app. One of the Paranoid Android ROMs, Liquid Smooth, and Synergy (even the Touchwiz camera was broken on that!).
I can restore to the original backup I made of the stock ROM, and the camera works fine again. But as soon as I try a different ROM, no camera.
I'd love to get an AOSP ROM running on this phone, but having a working camera is a requirement, and I can't figure out what I'm doing wrong. Searching the individual threads for the ROMs yields little help, and I'm getting exactly the same error on different ROMS, so I feel like I'm doing something wrong on a higher level. Any chance that switching from TWRP to CWM would make a difference? I don't see why it would, but I suppose it's something I could try.
bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
CZory91 said:
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
Click to expand...
Click to collapse
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Watanuki-Kun said:
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Click to expand...
Click to collapse
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
CZory91 said:
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
Click to expand...
Click to collapse
Probably best, that would be my first thing to try if I had that problem, restarting from scratch. If all else fails, restarting from scratch will wipe out everything. If that failed, I would probably suspect hardware issue.
Watanuki-Kun said:
Have you tried odin back to MB1...
Click to expand...
Click to collapse
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
dandydon414 said:
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Click to expand...
Click to collapse
Well I would recommend liquid 2.5 with the kernel that comes with it and I never change any of the overclocking settings. I don't have to pull the battery at all on this one.
Sent from my SCH-I535 using xda premium
TunedReference said:
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
Click to expand...
Click to collapse
Yep, that's what I tried. Nothing.
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
tfc87 said:
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
Click to expand...
Click to collapse
I'm going to go ahead and help myself out and respond to my own question. Upon even further research (yes, I know everyone says people don't look hard enough), I believe the issue relates to the Firmware version. Supposedly the newest firmware breaks the camera unless it's on the stock rom. There are modified firmwares out there that change the part that breaks the camera, but I believe I am going to downgrade the modem and all from what was pre-installed and see if it works.
tfc87 said:
I'm going to go ahead and help myself out and respond to my own question. Upon even further research (yes, I know everyone says people don't look hard enough), I believe the issue relates to the Firmware version. Supposedly the newest firmware breaks the camera unless it's on the stock rom. There are modified firmwares out there that change the part that breaks the camera, but I believe I am going to downgrade the modem and all from what was pre-installed and see if it works.
Click to expand...
Click to collapse
if its a custom Rom (Stock but maby some extras such as overclocking or somethin) they are Sometimes Broken They will try to fix it sometimes, upgrading to a higher android version it is sometimes is Quite hard to Fix everything.
Trozzul said:
if its a custom Rom (Stock but maby some extras such as overclocking or somethin) they are Sometimes Broken They will try to fix it sometimes, upgrading to a higher android version it is sometimes is Quite hard to Fix everything.
Click to expand...
Click to collapse
I downgraded the firmware to VRBMB1 and went back to that custom rom and the camera works flawlessly. I read in the firmware forum that the new firmware is doing this to a lot of people...I just happened to have one of the phones that came with it pre-installed. Problem solved and hopefully this post will help someone out...if not...it helped myself out at least.
tfc87 said:
I downgraded the firmware to VRBMB1 and went back to that custom rom and the camera works flawlessly. I read in the firmware forum that the new firmware is doing this to a lot of people...I just happened to have one of the phones that came with it pre-installed. Problem solved and hopefully this post will help someone out...if not...it helped myself out at least.
Click to expand...
Click to collapse
maby just wait till next firmware and they will fix it?
Trozzul said:
maby just wait till next firmware and they will fix it?
Click to expand...
Click to collapse
Yeah I'm sure it will be fixed. Either way, I don't recommend that newest firmware...signal seems to be the worst out of all of the ones I've tried...for me at least. Seems to be a lot of complaints out there with it anyways.
Similiar issue?
I am having a similiar issue with my US Cell GS3. I bought the donor version of mskip's Samsung Galaxy S3 Unified Toolkit and rooted my device yesterday now my camera is doing the same thing...fires up to a black screen, hangs a few seconds then says camera failed. I'm running Android 4.1.2, build R530UVXAMD4. I've read in a few places that I may have to either downgrade my kernel or flash with some sort of alternate firmware.
Any assistance provided is greatly appreciated!
Sterling8356 said:
I am having a similiar issue with my US Cell GS3. I bought the donor version of mskip's Samsung Galaxy S3 Unified Toolkit and rooted my device yesterday now my camera is doing the same thing...fires up to a black screen, hangs a few seconds then says camera failed. I'm running Android 4.1.2, build R530UVXAMD4. I've read in a few places that I may have to either downgrade my kernel or flash with some sort of alternate firmware.
Any assistance provided is greatly appreciated!
Click to expand...
Click to collapse
did you figure this out?
im having same problem
I had the same problem while flashing one of my friend's S3...i just did the whole process once again..and everything works fine
Sent from my Galaxy Note II using xda premium
tfc87 said:
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
Click to expand...
Click to collapse
I have had the same problem when I installed a certain custom rom (can't remember the name ) on my s3. But later I found that during installation of the rom, there was an option to choose one of four kernels, and if I chose Boeffla kernel (included in the options) my camera wouldn't work. So I just reverted back to the stock kernel and walah! My camera works again.
Hello, I am sorry if someone has made a thread like this I just have looked everywhere and not finding anything. I have installed I think three roms, all of them not having working WiFi. Everything else works flawlessly and i wish I could use it instead of the Software verizon has provided us with. I am using Safestrap, I have tried reflashing the roms several times, tried to flash the modem [I think this is only cell signal but it was worth a shot]. Does anyone have a solution here? Any help is greatly appreciated!
Download the VRUCML1 kernel modules from the Safestrap thread and flash them in recovery after flashing a rom. You need to flash these each time you flash a custom 4 3 the in order to have working wifi.
Sent from my SCH-I535 using Tapatalk 4