I've been jumping lately between various AOSP Jellybean roms, and Lollipop roms without issue on my I747m. Now, I'm upgrading my phone and want to give my S3 to my dad. He will just make basic calls and take pics. I want him to be on Touchwiz as i think the camera will be best for him in that regard.
I've tried 3 TW roms in a row, and they all give me the same error, "cannot connect to camera", as if another app is using the camera. Going back to my usual AOSP/CM roms in between attempts show the camera to work just fine. While on the touchwiz roms, I've cleared the camera cache, pulled the battery, etc etc... all the usual stuff. These are full wipes, clean installs with absolutely nothing being done to the phone (not even downloading an app). I install the ROM, wait a few minutes, then try the camera to no avail.
Any thoughts on what could be doing this? I have gone to touchwiz roms in the past (briefly) with no issue, but haven't tried in quite some time. I'm on the MK5 bootloader, if it matters.
Thanks.
Holmes108 said:
I've been jumping lately between various AOSP Jellybean roms, and Lollipop roms without issue on my I747m. Now, I'm upgrading my phone and want to give my S3 to my dad. He will just make basic calls and take pics. I want him to be on Touchwiz as i think the camera will be best for him in that regard.
I've tried 3 TW roms in a row, and they all give me the same error, "cannot connect to camera", as if another app is using the camera. Going back to my usual AOSP/CM roms in between attempts show the camera to work just fine. While on the touchwiz roms, I've cleared the camera cache, pulled the battery, etc etc... all the usual stuff. These are full wipes, clean installs with absolutely nothing being done to the phone (not even downloading an app). I install the ROM, wait a few minutes, then try the camera to no avail.
Any thoughts on what could be doing this? I have gone to touchwiz roms in the past (briefly) with no issue, but haven't tried in quite some time. I'm on the MK5 bootloader, if it matters.
Thanks.
Click to expand...
Click to collapse
I can think of a couple of things that may help.
MK5 is a 4.3 bootloader and modem. Were the TouchWiz ROMs you flashed Android 4.3 or KitKat ROMs? If they were Kitkat, Android 4.4.2, then the fix may be as simple as flashing the ROM and then flashing one of the custom kernels, either ibuddler's, found in the OP of the Likewise ROM, or the TW kernel by ktoonsez.
If you were flashing a 4.3 TW ROM, or if the custom kernel did not help with a 4.4.2 ROM; then you may need to flash a stock MK5 ROM, followed with a factory reset from the stock recovery. After that flash the custom recovery of your choice, root, and flash the TW ROM you like best.
dawgdoc said:
I can think of a couple of things that may help.
MK5 is a 4.3 bootloader and modem. Were the TouchWiz ROMs you flashed Android 4.3 or KitKat ROMs? If they were Kitkat, Android 4.4.2, then the fix may be as simple as flashing the ROM and then flashing one of the custom kernels, either ibuddler's, found in the OP of the Likewise ROM, or the TW kernel by ktoonsez.
If you were flashing a 4.3 TW ROM, or if the custom kernel did not help with a 4.4.2 ROM; then you may need to flash a stock MK5 ROM, followed with a factory reset from the stock recovery. After that flash the custom recovery of your choice, root, and flash the TW ROM you like best.
Click to expand...
Click to collapse
I had tried both 4.1 and 4.4 rom. Thanks for the tips though. I'll def look into all of that. I appreciate it!
Related
First off, a little background info:
Rom: CM 10.1 (5/22)
Kernel: stock cm
Recovery: twrp 2.5.5.0
Anyway.. I've noticed this issue for probably two months now. Whenever I try to flash ANY kernel on my device, I don't get past the initial boot screen. I do make sure that I'm flashing the correct kernel (that is, one that's compatible with the rom that I'm using) and no matter what, I can't get past the startup screen. Even if I flash the stock kernel, it won't boot.
Conclusion (that will help troubleshoot):
-It can't be recovery, unless an update caused a fluke. I've flashed kernels using twrp before.
-I would suggest that it's the rom, but even if I go back to the roms (RootBox to be more specific) that were over clocked, it won't get past the boot screen with third party kernel. It will boot with just rom however.
-it can't be incorrect flashing methods.. I've done this for years without (many) issues.
I'm beginning to think ill have to Odin stock 4.x.x, but I would like to take another route if at all possible. Any suggestions?
Gfrt94yn said:
First off, a little background info:
Rom: CM 10.1 (5/22)
Kernel: stock cm
Recovery: twrp 2.5.5.0
Anyway.. I've noticed this issue for probably two months now. Whenever I try to flash ANY kernel on my device, I don't get past the initial boot screen. I do make sure that I'm flashing the correct kernel (that is, one that's compatible with the rom that I'm using) and no matter what, I can't get past the startup screen. Even if I flash the stock kernel, it won't boot.
Conclusion (that will help troubleshoot):
-It can't be recovery, unless an update caused a fluke. I've flashed kernels using twrp before.
-I would suggest that it's the rom, but even if I go back to the roms (RootBox to be more specific) that were over clocked, it won't get past the boot screen with third party kernel. It will boot with just rom however.
-it can't be incorrect flashing methods.. I've done this for years without (many) issues.
I'm beginning to think ill have to Odin stock 4.x.x, but I would like to take another route if at all possible. Any suggestions?
Click to expand...
Click to collapse
What kernel are you trying to flash?
ROOTBOXED!
roughneckboren said:
What kernel are you trying to flash?
ROOTBOXED!
Click to expand...
Click to collapse
I've tried many kernels (again, with various ROMs)
Kernels:
King Kanger's
SOAP
some AOSP kernel (don't think there was a specific name)
And something else by ManelScout
I've tried using ROMs:
PA
PACMAN
RootBox
CM 10.1
LiquidSmooth (with its 2.16ghz kernel, still unsuccessful)
Jedi
And DevientXone
.. Mixing and matching, but using the correct kernel with its base; no luck whatsoever. If you haven't noticed, I stay away from stock-based roms, as I like the more streamlined, slicker software that AOSP has to offer. I can't say that I've tried reverting to stock I317 TW based roms. Though, I wouldn't see that AOSP is the issue.. It's almost like a piece is missing since it just happened out-of-the-blue and I can't seem to remedy the problem no matter how many different combinations I try and how many times I download it.
You may have a corrupted device...
I suggest a full wipe...then a fresh install of a rooted stock rom via odin...
then push a fresh recovery via odin...use the UCAMA4 build from mr. Robinson's thread...(development section)
Then attempt the rom of choice..
but first verify the stock build will boot properly...
many devices get corruption within the partitions...especially with the large amount of flashing you have done...
my .02....g
I was afraid of that.. Oh well, it was worth asking. Can I use mobile Odin to flash all of these things or would you suggest using a computer? I've never used Mobile Odin, but I'm familiar with how all of that stuff works (on pc), so I assume it's similar.
PC....
Mobile Odin is a fine program ...but why risk flashing the device, with a possible corruption issue ??
Eliminate the risk ...IMHO ...g
Hey guys i have a samsung i747 from rogers and i'm trying to install custom roms. I've obviously rooted it and installed CM recovery and downloaded roms and gapps. So far i've tried liquidsmooth 2.8. Avatar Rom. Cyanogen. but nothing seems to be working. Every single one of the them keeps telling me that my setup wizard had crashed and my gapps weren't working. I earlier had a Status 7 error installing cyano and avatar so i flashed d2att's 07.05.13 kernel, but that didn't seem to help. I tried running a different version of the clockworkmod recovery too. I've hardly ever "dirty" flashed. Someone help me out here i hate custom roms!!!
Wipe
Data
Cache
Delvik Cache
and Factory Reset.
Make sure you're flashing the correct GApps for android 4.2.x
Flashing a kernel has nothing to do with a status 7 error.
A status 7 error points to a outdated recovery or bootloader.
You should get ANY errors.
If you hate flashing why do it??
I honestly don't get that...
If you're here to make your phone to look "cool" you're in the wrong place.
Galaxy S3 / AoCP / V4A / Turbocharged
duoblade said:
Hey guys i have a samsung i747 from rogers and i'm trying to install custom roms. I've obviously rooted it and installed CM recovery and downloaded roms and gapps. So far i've tried liquidsmooth 2.8. Avatar Rom. Cyanogen. but nothing seems to be working. Every single one of the them keeps telling me that my setup wizard had crashed and my gapps weren't working. I earlier had a Status 7 error installing cyano and avatar so i flashed d2att's 07.05.13 kernel, but that didn't seem to help. I tried running a different version of the clockworkmod recovery too. I've hardly ever "dirty" flashed. Someone help me out here i hate custom roms!!!
Click to expand...
Click to collapse
I would get TWRP recovery.. wipe dalvik / factory reset. and re-flash your rom.. I'm on Rogers as well and the status 7 error means that your recovery / bootloader is outdated.
So start by getting the most recent TWRP. I got it from goo.
btw: if you don't like custom rom, i suggest going to the sammobile site and getting your factory firmware. Use Odin to reflash back to stock. That should solve your hiatus towards custom roms...
correction
thanks guys but idk i just tried flashing a custom rom at 4.1.2 and then went up from the there and it was fine... for the status 7 i just adjusted the coding for it so it didn`t have to check the model and this was typed up like at like 2 in the morning where i`m from i meant to say i hate stock roms LMAO:silly:
duoblade said:
thanks guys but idk i just tried flashing a custom rom at 4.1.2 and then went up from the there and it was fine... for the status 7 i just adjusted the coding for it so it didn`t have to check the model and this was typed up like at like 2 in the morning where i`m from i meant to say i hate stock roms LMAO:silly:
Click to expand...
Click to collapse
sure but its fine custom Roms can be a Pain in the A$$ thats why am running stock rooted stable, great battery life, fast like custom roms, everything is perfect give a try with stock rooted no issues or problems like custom roms
Synergy Rom 4.1.2 w/ Ziggy Kernel using ATT Galaxy S3
HAPPY ROOTIN :cyclops:
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
jinxzn said:
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
Click to expand...
Click to collapse
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Zachinater said:
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did flashed SOAPKernel along with aosp roms.
wase4711 said:
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Click to expand...
Click to collapse
I flashed BeanStalk, SlimBean, CyanogenMod 10.1 official nightlies, FSC rom, and IllusionRom.
I have CWM Philz_Touch 5.07.1. Every time install a new rom, I wiped Caches + Data / Factory Reset 2x.
I flashed rom only, then flashed rom and GAPPS, those 2 didn't work, I even tried rom w/ SOAPKernel and still didn't work.
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
wase4711 said:
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
Click to expand...
Click to collapse
Switched to TWRP, and did all the wipes, install rom and GAAPS. Same thing.
Planning to flash stock rom, and redo all the root/recovery procedures all over again. Do you think I should do that?
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
wase4711 said:
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
Click to expand...
Click to collapse
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
jinxzn said:
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
Click to expand...
Click to collapse
good luck, and post back if you get it working properly
flashed stock rom and rooted and installed boot recovery, after all that, it's still not let me install any AOSP roms. Really don't why I can only flash TW roms but not AOSP roms.
Hi there, I am not new to installing Roms in any way but I accidentally installed a d2lte Liquid smooth ROM instead of what my phone is, a d2att. So when installing the above ROM I did everything what I was supposed to do (clean install, format system). However, whenever I go on any ROM (Such as Quantum or Omni) I get an error as soon as it boots up, and my signal keeps turning on and off. I wiped data, cache and dalvik twice and go to a new ROM and the problem persists. For some odd reason, Carbon ROM works but I need a different one due to battery drain. I've never experienced this problem ever and I was hoping someone could please help me out?
Have you tried re-flashing the modem?
audit13 said:
Have you tried re-flashing the modem?
Click to expand...
Click to collapse
Yes i tried that earlier but still no luck. It's weird though how there was no problem on carbon rom and yet there was a problem when i went back to the Quantum Rom. Something happened on the LiquidSmooth Rom but i don't know what. I will again try reflashing the modem though thank you.
EDIT: Re-flashing modem did not help
Is it possible to use Odin to get back to a completely stock rom? If you have a 4.3 bootloader, you can't use Odin to flash a stock ROM.
A way to get back to a stock ROM for those on the MJB bootloader has been provided by enewman17. See AT&T I747 UCUEMJB Stock Restore in the development forum.
hello everyone,
My phone is a T999v model.
I originally had 4.3 Stock Rom on it. All the custom ROMs i've installed lose audio the immediately i insert any headphone, and even after removing the headphones i still have loss of audio.
I have tried SlimROM 9.0, CM10, Beanstalk and CM12. All have the same results.
I used slim gapps on all the custom ROMS
When i go back to stock ROM i dont have the issue.
I used TWRP 2.8.6.0 to flash the ROM.
Please help.
Make sure everything is the latest, recovery, rom, gapps. Also make sure you install no mods to troubleshoot the issue, even different gapps
Done as you asked. Switched recoveries, used the most up to date. Same for the roms and gapps.
Same issue. Even in lollipop the only issue I have is the audio, I don't have issued with camera. I would rather have camera problems.
Should I flash a different kernel?
You can try. That is really unusual