I was running liquid smooth, which was running nice and smooth.. but then the back camera just stopped working. it was always black and would just crash. So i wiped app data.. still didnt work. I factory wipe / wiped cache and everything, still it didn't work. I flashed a ton of new 4.3 roms like the new aokp, slim bean 4.3 , PA 3.99 , and still the camera didnt work..I dont know what else to do. I'm not super experienced so bear with me, please help me out.
try restoring your stock back up or flash the stock Rom and root again
chiefsfan645 said:
I was running liquid smooth, which was running nice and smooth.. but then the back camera just stopped working. it was always black and would just crash. So i wiped app data.. still didnt work. I factory wipe / wiped cache and everything, still it didn't work. I flashed a ton of new 4.3 roms like the new aokp, slim bean 4.3 , PA 3.99 , and still the camera didnt work..I dont know what else to do. I'm not super experienced so bear with me, please help me out.
Click to expand...
Click to collapse
Restore a completely 100% stock ROM. If it works, then there's a problem with the ROMs your trying to flash. If it does not work then you have a hardware issue.
I'm trying, but when it asks me to enter the S / N into kies it keeps saying that its incorrect even though im reading it right off the darn sticker..
cheifsfan645: Ive never learned about flashing with kies but try searching for "flashing stock rom with odin" This is the method I use and there is no serial numbers or any info needed. Make sure you use the correct image, it has to be for your carrier and phone or you could end up with troubles, even in some cases, bricking your phone. An even more foolproof method is to use "Samsung Toolbox" because it comes with detailed instructions and is a mostly automated process. I hope I may have pointed you in a helpfull direction, Im still new to this stuff.
Sent from my SGH-I747M using XDA Premium 4 mobile app
chiefsfan645 said:
I'm trying, but when it asks me to enter the S / N into kies it keeps saying that its incorrect even though im reading it right off the darn sticker..
Click to expand...
Click to collapse
Whoa, I've never heard of that one. I'm assuming you flashed a stock odin image? Maybe try to download the stock image from another source and see if that helps. I've never had that happen to me before.
What recovery are you using? If its TWRP make sure you have the latest. If its not then make sure you update to the latest. I got a replacement device. Rooted it and Rom'd it and my camera broke just like you are describing. I want back to full stock and camera worked. I then rooted it and camera worked. I then talked with friend and he advised me to flash the newest TWRP. I did and my camera came back.
Download TWRP from here http://techerrata.com/get/twrp2/d2att/openrecovery-twrp-2.6.3.0-d2att.tar
Download odin from here. http://forum.xda-developers.com/showthread.php?t=2189539
Install odin and run it. Reboot the phone to download mode make sure you have usb debugging checked in settings. Then check the PDA box and browse to that tar file and load it and then hit start it will flash your phone will reboot and the camera should be working.
Related
So I I've had 2 different recoveries so far that have worked fine.. both came from Rogue though. One was from the 1.5 kernel (Hitman) which installed CWM Touch recovery, the other came with the normal recoveries based off CW 5.0.2.7. They were working fine until I installed Calkulin's Rom(2.8.1). Not sure if they're just incompatible or what, but when I go to recovery it shows the background image of the recovery but none of the options show up. It shows for about half a second and then it goes back to the original boot screen, then to the 2nd screen and turns on. So it basically skips right through the recovery and reboots. Do I need a new Rom or can I fix this? I really like the battery life and visuals of Calkulin's Rom and would love to be able to keep it.
EDIT: One more thing.. Since I installed the ROM, I've been getting market error 492. It doesn't allow me to install anything in the market..
I haven't tried a full wipe yet, so I guess I'll try that and then see how that works with the recovery and Rom..
I did the same thing to my phone this week, and I'm running Blazer, so i'm sure it has nothing to do with either ROM.
Not sure how I caused it but with so many folks running both without this error, I'm guessing that your issue (like mine was) was probably some how self induced.
I flashed back to stock and started over, and things have been working great. Might be worth a shot flashing back, or restore a backup and start fresh.
Haven't seen the market error before. I'm sure someone here has
Good Luck
If you got it off here, could you show me which stock you flashed..?
Everything you need is in the Epic 4G Touch Android Development section
Here is the post I used from Sfhub
http://forum.xda-developers.com/showthread.php?t=1433101
Watch the videos by Qbking77 They walk you thru everything step by step. (I hear his video intro rif every time I close my eyes now so you've been warned) Makes it super easy.
I would read everything you can and watch the videos before you get in too deep. I've had this phone since December, and just flashed my 1st ROM this week cause I've been reading up, and learning all I could before I jumped in the pool.
Well I've done all this with 2 phones before but I've never had this happen.. normally I just get the Rom and I'm good to go..
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
premo1 said:
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
Click to expand...
Click to collapse
Try booting while holding the volume up and power button.
If that does not work, flash recovery from rom manager, and that should get you into recovery to flash whatever kernel/recovery u want.
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
premo1 said:
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
Click to expand...
Click to collapse
Good Luck.
Recovery and market are now working Thank you Adanorm!
Glad your back up and running
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
eternalcold said:
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
Click to expand...
Click to collapse
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
BWolf56 said:
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
Click to expand...
Click to collapse
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
eternalcold said:
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
Click to expand...
Click to collapse
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
BWolf56 said:
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
Click to expand...
Click to collapse
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
eternalcold said:
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
Click to expand...
Click to collapse
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
BWolf56 said:
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
Click to expand...
Click to collapse
Alright, i'll flash that one, i'll post to here when it's finished. Thanks!
Did you check your IMEI?
xBeerdroiDx said:
Did you check your IMEI?
Click to expand...
Click to collapse
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
eternalcold said:
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
Click to expand...
Click to collapse
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
BWolf56 said:
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
Click to expand...
Click to collapse
Understood, I wont mess with them.
I really just want to understand a couple things.
1. Why did the ROM I installed before work for everyone else except me? and i followed the instructions.
and 2. after flashing to stock, how am I unable to fix this?
mainly to just learn what went wrong.
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
hednik said:
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
Click to expand...
Click to collapse
Thanks,
Is there any way to repair it?
Alright, so....
I think i have figured out what the issue was. Or by random chance got it fixed.
I was going to try to install the Synergy Rom. And while going through the custom setup, i noticed "Install AOSP Messaging" and "Install TW Messaging"
I chose the TW messaging, and went through the rest of the installer.
For some reason i kept hanging at the "Samsung Galaxy S3" logo, and it would not boot.
(Honestly, i've used custom roms since the HTC Touch Pro 2, and i've NEVER had such issues. And i personally think the TP2 was way more difficult lol)
So I ONCE AGAIN flashed to stock. and randomly the messaging works!
I only can guess that even when flashing the stock rom, it doesnt change something regarding the messaging app. I'm not sure. All i know is that i'm on stock again and everything is working. I highly doubt i'm going to try another custom rom for a while until i have a full understanding of what happened.
But in case anyone else was having this problem, i hope this helped.
I have tried everything and I have not been able to find anyone else on this site (in any on the forums) reporting this. I have been trying out 4.2.2 ROMS for a while now...and they are getting pretty good. Especially sense it only officially came out a month ago. But there seems to be a ~bluetooth~ "issue" of some sort in all the ones I have tried (that I liked). I am running Liquid with the latest everything and it rocks! ~But~ it doesn't let my bluetooth sleep, so it drains fast it if I don't turn it off. It is a big enough issue for me to go back to 4.1.2 until they improve these glitches.
That is when I discovered this weird problem. No matter which 4.1.2 ROM I flash or try to recover, I get hit with an encryption password. I am not a very creative guy; I can count all the passwords I have used in the last 20 years on one hand. I have tried every password I can thing of and nothing works. I have tried formatting the entire phone with CWM. I have tried several versions of different custom recovery systems. I cannot install a 4.1.2 ROM nor can I recovery one previously backed up. Today I completely unrooted my phone. Yep, I reversed the whole process, then tried to ODIN the original stock (un-touched, straight out of the box) ROM. Yep, it asked me for encryption code
Where can this be coming from? Why does it only happen with 4.1.2 ROMs? Please help Do I need to replace the SIM card maybe? The SIM card is the only thing I can't format.
Go into your stock recovery and wipe data, factory reset the device....g
You are my hero! I want to kiss and hug you!:highfive: I am in rooted stock now (4.1.2); from here I should be able to get into a 4.1.2 ROM that I like. I wish AxisM was available for N2 ( :
Thank you, Thank you, Thank you!!!
gregsarg said:
Go into your stock recovery and wipe data, factory reset the device....g
Click to expand...
Click to collapse
LOL...
Always welcome my friend....It's no problem...
And of course...happy flashing...
Just remember to use that method when going back to full stock, or rooted stock.
It's the only way to completely clean the device for stock usage...g
Hi there!
I have a bit of a problem with my T-Mobile S4 and I was wondering if there was anything I could do to remedy the situation. So here is the problem;
Two days ago, I was playing PPSSPP and then I saved the state so I could eat lunch. When I came back to play, I loaded the state and then all of the sudden, my screen jumbled for a split second then went black. I tried to restart my phone, but it would always boot up and then go back to a black screen. I then reinstalled my ROM and was able to use my phone again. Thinking that it was over, I decided to re-flash my kernel. But then, it happened again, only this time, I could kind of turn my screen on but it was all messed up. See photo below. I re-flashed my ROM once more, made a titanium backup of my apps and then proceeded to wipe my whole phone through TWRP, going to wipe -> advanced wipe and then selecting every check box except for external sd and USB otg. Afterward, I re-flashed my ROM once more, booted my phone to make sure it worked then flashed the kernel same thing happened. SoI tried a couple different kernels but they all produced the same results. Just a jumbled screen. What could have went wrong? And is there a chance I can fix it?
ROM used - ParanoidAndroid 3.99 RC2
Kernel used - KT-SGS4
Other Kernels tried - Chronic Kernel, Blue ROM kernel
Anyone ever have this problem?
over16bit said:
Hi there!
I have a bit of a problem with my T-Mobile S4 and I was wondering if there was anything I could do to remedy the situation. So here is the problem;
Two days ago, I was playing PPSSPP and then I saved the state so I could eat lunch. When I came back to play, I loaded the state and then all of the sudden, my screen jumbled for a split second then went black. I tried to restart my phone, but it would always boot up and then go back to a black screen. I then reinstalled my ROM and was able to use my phone again. Thinking that it was over, I decided to re-flash my kernel. But then, it happened again, only this time, I could kind of turn my screen on but it was all messed up. See photo below. I re-flashed my ROM once more, made a titanium backup of my apps and then proceeded to wipe my whole phone through TWRP, going to wipe -> advanced wipe and then selecting every check box except for external sd and USB otg. Afterward, I re-flashed my ROM once more, booted my phone to make sure it worked then flashed the kernel same thing happened. SoI tried a couple different kernels but they all produced the same results. Just a jumbled screen. What could have went wrong? And is there a chance I can fix it?
ROM used - ParanoidAndroid 3.99 RC2
Kernel used - KT-SGS4
Other Kernels tried - Chronic Kernel, Blue ROM kernel
Click to expand...
Click to collapse
I have never heard of this problem. It seems you have tried your best to fix it...
My suggestion is to go back stock and see if the problem is still there. If it is then its a hardware problem.
If its not...re-root and flash a rom and go from there.
Sent from a Insane S4
SICK MADE DEVELOPMENT
alloycowboy said:
I have never heard of this problem. It seems you have tried your best to fix it...
My suggestion is to go back stock and see if the problem is still there. If it is then its a hardware problem.
If its not...re-root and flash a rom and go from there.
Sent from a Insane S4
SICK MADE DEVELOPMENT
Click to expand...
Click to collapse
This...but use Odin to go back to stock. Dont' just try to flash a stock ROM.
REALLY reset it hardcore by using Odin to flash the stock firmware package in its entirety.
That's what I was thinking about doing, but I can't download the stock image. The download never completes. I've thus far tried to download from the hotfile mirror and from stockROMs but they're always slow and never complete. What I'd really like is a torrent, but if anyone knows of any other mirror or what might be going wrong, I'd appreciate a point in the right direction.
Thanks!
over16bit said:
That's what I was thinking about doing, but I can't download the stock image. The download never completes. I've thus far tried to download from the hotfile mirror and from stockROMs but they're always slow and never complete. What I'd really like is a torrent, but if anyone knows of any other mirror or what might be going wrong, I'd appreciate a point in the right direction.
Thanks!
Click to expand...
Click to collapse
You need to use your pc to DL the firmware....it will fail trying to from your phone.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Flash the 10.16 AOSP 4.3 build of KT's kernel. Any build newer than that is for CM based ROMs compiled AFTER 10.20.
alloycowboy said:
You need to use your pc to DL the firmware....it will fail trying to from your phone.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am trying to download it from my PC. :/
Also, I tried the earlier KT kernel as that was the one I had on hand. Same thing happens.
over16bit said:
I am trying to download it from my PC. :/
Also, I tried the earlier KT kernel as that was the one I had on hand. Same thing happens.
Click to expand...
Click to collapse
Sounds like hardware problem. I hope im wrong.
Let us know how it goes after you odin back to stock
Sent from Insane S4
SICK MADE DEVELOPMENT
Ive tried several ROMs over the years on my ATT GS3. Lately Ive been using the Liquid Smooth ROM. About 4 months after install I started getting screen flashes/colors, random restarts, the phone was getting hot and Ext SD card errors so it was pretty much unusable. Went to try some other ROMs and cant get them to flash. Tried Beanstalk, ProBAM, and Goodness Reborn and they fail immediately. Ive downloaded from different mirrors and the file size is identical. Ive tried flashing from internal and still wont work. Also updated TWRP throughout this process and didnt fix it. The only one that does flash is Synergy but im not a fan of 4.1. Would rather have 4.2/4.3.
Any ideas on why these ROMs arent flashing? Ive tried multiple times.
I dont know the ins and outs all that well but it seems something is corrupted. Would it make sense to odin back to stock/unroot and start fresh? Follow this? http://forum.xda-developers.com/showthread.php?t=2186967
Or is this a fixable issue without going through all that?
Who Am I? said:
Ive tried several ROMs over the years on my ATT GS3. Lately Ive been using the Liquid Smooth ROM. About 4 months after install I started getting screen flashes/colors, random restarts, the phone was getting hot and Ext SD card errors so it was pretty much unusable. Went to try some other ROMs and cant get them to flash. Tried Beanstalk, ProBAM, and Goodness Reborn and they fail immediately. Ive downloaded from different mirrors and the file size is identical. Ive tried flashing from internal and still wont work. Also updated TWRP throughout this process and didnt fix it. The only one that does flash is Synergy but im not a fan of 4.1. Would rather have 4.2/4.3.
Any ideas on why these ROMs arent flashing? Ive tried multiple times.
I dont know the ins and outs all that well but it seems something is corrupted. Would it make sense to odin back to stock/unroot and start fresh? Follow this? http://forum.xda-developers.com/showthread.php?t=2186967
Or is this a fixable issue without going through all that?
Click to expand...
Click to collapse
From what it sounds, it could be a bootloader problem. Did you ever update to 4.1.2? All 4.3 ROMs require at least the 4.1.2 bootloader, which you can get without Odin'ing 4.1.2 from here:
http://forum.xda-developers.com/showthread.php?t=2321310
As always read, read and read. If this doesn't help, I recommend maybe trying out CWM (I'd restore back to your TouchWiz backup since that backups from TWRP and CWM aren't compatible.) If that still doesn't help, then by all means, Odin to stock, OTA to 4.1.2, root and go on. As always, this is just information from one member to another, so I am in no way, shape or form responsible for anything and everything that could go wrong.
The 4.1.2 ota update just came out today so no. I'll try that in the morning thanks!
Who Am I? said:
Ive tried several ROMs over the years on my ATT GS3. Lately Ive been using the Liquid Smooth ROM. About 4 months after install I started getting screen flashes/colors, random restarts, the phone was getting hot and Ext SD card errors so it was pretty much unusable. Went to try some other ROMs and cant get them to flash. Tried Beanstalk, ProBAM, and Goodness Reborn and they fail immediately. Ive downloaded from different mirrors and the file size is identical. Ive tried flashing from internal and still wont work. Also updated TWRP throughout this process and didnt fix it. The only one that does flash is Synergy but im not a fan of 4.1. Would rather have 4.2/4.3.
Any ideas on why these ROMs arent flashing? Ive tried multiple times.
I dont know the ins and outs all that well but it seems something is corrupted. Would it make sense to odin back to stock/unroot and start fresh? Follow this? http://forum.xda-developers.com/showthread.php?t=2186967
Or is this a fixable issue without going through all that?
Click to expand...
Click to collapse
Fail immediately? As in you're able to flash them but can't boot properly or you have glitches?
Sounds like a hardware issue to me. Hope you got warranty.
I click install, select the zip and it starts working for a couple seconds and fails.
Just updated the bootloader and ProBAM and Goodness failed. Tried Beanstalk and it completed fine. Gonna try it out for a bit. It is 4.3 so not sure what the issue it with the other ROMs yet
Beanstalk is up and running. Thanks drx!!
edit
Just dl'd Carbon ROM and CM 10.1.3. Both failed immediately when I used TWRP to flash them. Updated bootloader, updated SuperSU. Should I go back to CWM?
What am I missing? If there are no other ideas is my only option to ODIN back to stock and try again?
Who Am I? said:
Just dl'd Carbon ROM and CM 10.1.3. Both failed immediately when I used TWRP to flash them. Updated bootloader, updated SuperSU. Should I go back to CWM?
What am I missing? If there are no other ideas is my only option to ODIN back to stock and try again?
Click to expand...
Click to collapse
Try Task650's rom. It's the most stable and smooth I've used. Also, he has good instructions on what bootloader to use.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Moved to internal and flashed fine. Rebooting now.
Spent most of yesterday on AirDroid moving files back to my external. Came back and it looks like it killed the battery. Plugged in, rebooted and now my ext sd card wont show up. I bought a 64GB Samsung microcard off Ebay. Formatted on the phone and started tranferring files fine. Was going slow but working. Really dont want to format and start over but the phone wont even see it so I cant format it from the phone.