I am trying to troubleshoot a phone issue for a co-worker and their phone goes a blank yellow screen and then reboots randomly. Anyone have any suggestions on how to fix this?
What is the story behind the problem?
Sent from my SGH-I717D using xda app-developers app
Murmur95 said:
I am trying to troubleshoot a phone issue for a co-worker and their phone goes a blank yellow screen and then reboots randomly. Anyone have any suggestions on how to fix this?
Click to expand...
Click to collapse
I'd like some more info if you know.
What version android is it running?
Is the phone rooted or running a custom rom?
Does the phone boot up and run at all?
What version android is it running?
I have tried different roms the current one is supernexus 4.2.2 and the last was PA 3.5#. PA seemed to run the best so far
Is the phone rooted or running a custom rom?
Rooted w/ custom rom
Does the phone boot up and run at all?
Yes and for the most part it worked fine, it just rebooted randomly.
I have tried a bunch of other ROMs as well but they seem to crash a lot / random reboot more.
I installed the ROMs myself (I know how to do it) and he never touched the system, when I installed I used TWRP 2.5.0.0 deleted cache, system, factory reset installed rom and cleaned cache afterwards.
He has a bell Galaxy Note - i717 which is calle QunicyATT i believe.
One partially unresolved issue with the 4.2.2 roms are random reboots, due to the kernel they have been building with.
There are some stable rom-kernel combinations available.
rangercaptain said:
One partially unresolved issue with the 4.2.2 roms are random reboots, due to the kernel they have been building with.
There are some stable rom-kernel combinations available.
Click to expand...
Click to collapse
Any you suggest?
I use stock, for greatest stability. I value that above all the other features.
No opinion on 4.2.2.
rangercaptain said:
I use stock, for greatest stability. I value that above all the other features.
No opinion on 4.2.2.
Click to expand...
Click to collapse
It doesn't need to be 4.2.2, just anything stable and minus TW crap.
What TouchWiz crap?
You can use the debloated stock and change to any launcher.
I have to chime in and say ... ics Gubment Cheeze was ALWAYS as stable as stock for me ... yes I am very partial to it But it is fact .. but any ics rom should do the trick for you ... (but Cheeze is best) .. best of luck
rangercaptain said:
What TouchWiz crap?
You can use the debloated stock and change to any launcher.
Click to expand...
Click to collapse
I concur.
Related
Ok, so ive had a couple of problems with my recently bought Sgs2, ive got all the other problems fixed except this one: when i turn on the camera app, the flash goes on and off once, the same happens when i turn off the camera. Its a very fast flash that occurs.. it doesnt matter what camera app i use, it does it everytime.. the flash does work properly during camera use if needed, and works normally as a torch.
It doesnt bother me much, but would be nice to get fixed..
Any ideas?
If your using a custom jb rom then it's normal. It's a known bug.
Sent from my Galaxy SII
*boy*racer* said:
If your using a custom jb rom then it's normal. It's a known bug.
Sent from my Galaxy SII
Click to expand...
Click to collapse
Im using SlimICS 4.2+ Siyah 5.0.1
So he said.... That if You using not stock rom flash bug be...
Looks like he said: if its a custom JB rom, the bug occurs. Im using ICS and the same thing happened before i even flashed a custom rom. The phone was running a stock Samsung GB rom then..
"He" has a name
And if u said it happened before flashing roms, Then it must be a hardware issue.
Sent from my Galaxy SII
I have the same problem, that the flash will light up shortly when the camera app closed, and when I read the last comments it seems that this is a known issue for quite a while.
How does it come that this is not fixed yet. I'm using custom roms now for a few month now and from the beginning I was wondering about the strange flash behaviour compared to the stock rom.
Is it because there is still no official release from Samsung for JB or why is it so difficult to fix? Are the camera drivers closed source?
*boy*racer* said:
"He" has a name
And if u said it happened before flashing roms, Then it must be a hardware issue.
Sent from my Galaxy SII
Click to expand...
Click to collapse
I feared this was the issue.. oh well, i guess ill just have to live with it until i change my phone again, no biggie
elfrawg said:
I have the same problem, that the flash will light up shortly when the camera app closed, and when I read the last comments it seems that this is a known issue for quite a while.
How does it come that this is not fixed yet. I'm using custom roms now for a few month now and from the beginning I was wondering about the strange flash behaviour compared to the stock rom.
Is it because there is still no official release from Samsung for JB or why is it so difficult to fix? Are the camera drivers closed source?
Click to expand...
Click to collapse
It happened to you after switching to custom roms?
elfrawg said:
I have the same problem, that the flash will light up shortly when the camera app closed, and when I read the last comments it seems that this is a known issue for quite a while.
How does it come that this is not fixed yet. I'm using custom roms now for a few month now and from the beginning I was wondering about the strange flash behaviour compared to the stock rom.
Is it because there is still no official release from Samsung for JB or why is it so difficult to fix? Are the camera drivers closed source?
Click to expand...
Click to collapse
Mongopusher42 said:
I feared this was the issue.. oh well, i guess ill just have to live with it until i change my phone again, no biggie
Click to expand...
Click to collapse
Guys, it has got nothing to do with the hardware, its a random one that happens with all ICS and JB based custom roms
@Sun90
If you read the whole thread , i had the problem before custom roms with a 100% stock Samsung GingerBread rom..
Mongopusher42 said:
@Sun90
If you read the whole thread , i had the problem before custom roms with a 100% stock Samsung GingerBread rom..
Click to expand...
Click to collapse
have u tried flashing a Stock ICS rom (v4.0.3) and seen for the issue
if not give it a try and see, just to confirm whether its really a hardware issue or a software one
nothing to loose though, if the problem gets resolved for u it would be fine right
do a clean wipe before installing.
Sun90 said:
have u tried flashing a Stock ICS rom (v4.0.3) and seen for the issue
if not give it a try and see, just to confirm whether its really a hardware issue or a software one
nothing to loose though, if the problem gets resolved for u it would be fine right
do a clean wipe before installing.
Click to expand...
Click to collapse
Nope. Okk , ill try this when i have some spare time :thumbup:
Sun90 said:
Guys, it has got nothing to do with the hardware, its a random one that happens with all ICS and JB based custom roms
Click to expand...
Click to collapse
I used to get that on my x10i with certain roms.Definitely a software problem.
Same issue here, came about randomly day before yesterday. LED flashes once, quickly, whenever something tries to activate it.
Only ever used stock soft/firmware, and Chainfire's kernel. Cleared all caches, tried factory reset, problem persisted.
Flashed to whatever the latest ICS is for H3G today, problem still persists, I shall try official kernel tomorrow, see if that fixes it -- I don't hold much hope.
*boy*racer* said:
If your using a custom jb rom then it's normal. It's a known bug.
Sent from my Galaxy SII
Click to expand...
Click to collapse
I'm using hellybean 4.2.1 and I don't have this bug!!
Not sure exactly what to ask to really get a good answer, so I'll just lay a bit of history out and explain my thoughts.
Okie doke. So I have an Optimus G, yes, the E970, but it was apparently a test phone - not for sale on the side of the back casing, all that jazz. At first, this didn't cause any trouble at all, really. I've flashed ROMs and kernels up flawlessly without experiencing problems outside the normal ones that others had. I noticed difficulty in doing this more and more as after I flashed houstonn's RB ROM. I found I could use 4/20 and below versions with no problem.
List of ROMS I can flash successfully and use for indefinite amount of time:
SnowJB
SnowJB's Carbon ROM
CFX ROM
Any RootBox ROM before 4/26
CM 10.1 from OA Dev
Liquid Smooth
So I've been thinking it has to be a kernel issue. But that's also weird, because up until recently, I was able to flash any kernel on all of those ROMs. So I tested it out. If I use those those ROMs without flashing kernels, I'm good to go. I can even flash radios fine. However, I CANNOT flash the houcha kernel on any of those ROMs, or I can't boot (LG splash, then backlit blackness for indefinite amount of time). Same with MysteryEmtotionz -- ROMs will not boot with 5.1.1. Haven't tried any before that. Houcha kernels before the "geeb" updates, like v12 and below, I was able to use.
I have LGNPST'd so many times to wipe my phone of any kind of data I think would interfere. I've used the kernel cleaner script before flashing kernels too to see if it works to no avail. I've formatted my internal AND external in case anything may have been left over and interfering.
I would appreciate any kind of help or direction with this because I'm totally lost. I enjoy all of these ROMs, I really do. However, I like the sound of the features of the kernels, like the amplified sound and awesome variety of governors being added and would LOVE (practically begging) to have this issue solved.
Btw, using TWRP v2.5.0.0 for all of this. Tried CWM when it first occurred and somehow lost my recovery and had to LGNPST, so I've been avoiding it.
N12X93R said:
Not sure exactly what to ask to really get a good answer, so I'll just lay a bit of history out and explain my thoughts.
Okie doke. So I have an Optimus G, yes, the E970, but it was apparently a test phone - not for sale on the side of the back casing, all that jazz. At first, this didn't cause any trouble at all, really. I've flashed ROMs and kernels up flawlessly without experiencing problems outside the normal ones that others had. I noticed difficulty in doing this more and more as after I flashed houstonn's RB ROM. I found I could use 4/20 and below versions with no problem.
List of ROMS I can flash successfully and use for indefinite amount of time:
SnowJB
SnowJB's Carbon ROM
CFX ROM
Any RootBox ROM before 4/26
CM 10.1 from OA Dev
Liquid Smooth
So I've been thinking it has to be a kernel issue. But that's also weird, because up until recently, I was able to flash any kernel on all of those ROMs. So I tested it out. If I use those those ROMs without flashing kernels, I'm good to go. I can even flash radios fine. However, I CANNOT flash the houcha kernel on any of those ROMs, or I can't boot (LG splash, then backlit blackness for indefinite amount of time). Same with MysteryEmtotionz -- ROMs will not boot with 5.1.1. Haven't tried any before that. Houcha kernels before the "geeb" updates, like v12 and below, I was able to use.
I have LGNPST'd so many times to wipe my phone of any kind of data I think would interfere. I've used the kernel cleaner script before flashing kernels too to see if it works to no avail. I've formatted my internal AND external in case anything may have been left over and interfering.
I would appreciate any kind of help or direction with this because I'm totally lost. I enjoy all of these ROMs, I really do. However, I like the sound of the features of the kernels, like the amplified sound and awesome variety of governors being added and would LOVE (practically begging) to have this issue solved.
Btw, using TWRP v2.5.0.0 for all of this. Tried CWM when it first occurred and somehow lost my recovery and had to LGNPST, so I've been avoiding it.
Click to expand...
Click to collapse
ME's kernel b18c1 or w/e is for stock roms only, and houcha is for AOSP roms only. Have you done JellyBean OTA?
N12X93R said:
Not sure exactly what to ask to really get a good answer, so I'll just lay a bit of history out and explain my thoughts.
Okie doke. So I have an Optimus G, yes, the E970, but it was apparently a test phone - not for sale on the side of the back casing, all that jazz. At first, this didn't cause any trouble at all, really. I've flashed ROMs and kernels up flawlessly without experiencing problems outside the normal ones that others had. I noticed difficulty in doing this more and more as after I flashed houstonn's RB ROM. I found I could use 4/20 and below versions with no problem.
List of ROMS I can flash successfully and use for indefinite amount of time:
SnowJB
SnowJB's Carbon ROM
CFX ROM
Any RootBox ROM before 4/26
CM 10.1 from OA Dev
Liquid Smooth
So I've been thinking it has to be a kernel issue. But that's also weird, because up until recently, I was able to flash any kernel on all of those ROMs. So I tested it out. If I use those those ROMs without flashing kernels, I'm good to go. I can even flash radios fine. However, I CANNOT flash the houcha kernel on any of those ROMs, or I can't boot (LG splash, then backlit blackness for indefinite amount of time). Same with MysteryEmtotionz -- ROMs will not boot with 5.1.1. Haven't tried any before that. Houcha kernels before the "geeb" updates, like v12 and below, I was able to use.
I have LGNPST'd so many times to wipe my phone of any kind of data I think would interfere. I've used the kernel cleaner script before flashing kernels too to see if it works to no avail. I've formatted my internal AND external in case anything may have been left over and interfering.
I would appreciate any kind of help or direction with this because I'm totally lost. I enjoy all of these ROMs, I really do. However, I like the sound of the features of the kernels, like the amplified sound and awesome variety of governors being added and would LOVE (practically begging) to have this issue solved.
Btw, using TWRP v2.5.0.0 for all of this. Tried CWM when it first occurred and somehow lost my recovery and had to LGNPST, so I've been avoiding it.
Click to expand...
Click to collapse
Sounds like you need either OTA to 4.1.2 or LGNPST to it. Or you need to use teenybin to update your partitions. I believe on rootbox page it says that anything after a certain date (I believe it's 4/26) you need to be running off 4.1.2 firmware.
Sent from my Optimus G using xda premium
Drock is correct. That's your problem. You need to use lgnpst to flash teeny bin.
Sent via LG E970 with houstonn aokp 4.2.2
UUUUKK SUCH UUU1 I UUUU 2U U U2 U S
Sent from my LG-E980 using TapatalkKAJ 2
nygfan760 said:
ME's kernel b18c1 or w/e is for stock roms only, and houcha is for AOSP roms only. Have you done JellyBean OTA?
Click to expand...
Click to collapse
drock212 said:
Sounds like you need either OTA to 4.1.2 or LGNPST to it. Or you need to use teenybin to update your partitions. I believe on rootbox page it says that anything after a certain date (I believe it's 4/26) you need to be running off 4.1.2 firmware.
Sent from my Optimus G using xda premium
Click to expand...
Click to collapse
I've always OTA'd to 4.1.2. so I assume my rpm/tz to be updated. Is there any definite way I can check after being OTA updated to 4.1.2?
N12X93R said:
I've always OTA'd to 4.1.2. so I assume my rpm/tz to be updated. Is there any definite way I can check after being OTA updated to 4.1.2?
Click to expand...
Click to collapse
If you've OTA'd then it is updated.
It seems that if I format data with TWRP, as in select format data and type yes to proceed, I can flash those ROMs with only slight difficulty and confidently flash other kernels with no problem. Odd issue it seems, but at least there's a fix. Thanks for your help!
Unfortunately it seems like UPDATED ROM selection (atleast TouchWiz anyways) is a little slim now a days with this phone being all locked down and such. I have been running Hyperdrive forever, but was thinking about trying something else. I like something that has everything working and similar to stock (TWRP or AOSP)...just seeing what you guys recommend
CC268 said:
Unfortunately it seems like UPDATED ROM selection (atleast TouchWiz anyways) is a little slim now a days with this phone being all locked down and such. I have been running Hyperdrive forever, but was thinking about trying something else. I like something that has everything working and similar to stock (TWRP or AOSP)...just seeing what you guys recommend
Click to expand...
Click to collapse
Ive tried every rom in here and honestly the latest update mj7 rooted is the smoothest I've used. (No theme hub but I prefer reliability and speed, your not gonna get that unless you have the latest samsung kernel)
I am still on Hyperdrive 10.2, which is 4.2.2 I think. Hopefully sbreen comes out with a 4.3 or a 4.4 ROM soon that we can play with.
matt1733 said:
Ive tried every rom in here and honestly the latest update mj7 rooted is the smoothest I've used. (No theme hub but I prefer reliability and speed, your not gonna get that unless you have the latest samsung kernel)
Click to expand...
Click to collapse
Hmm....I may check that out
I am assuming you are referring to this??
http://forum.xda-developers.com/showthread.php?t=2517611
Hi, I have a problem with my s3, since the upgrade to version 4.3 from 4.1 via OTA wifi it stopped working in 4.1 worked fine and when I upgrade to 4.3 stopped working, I flash, wipes, back to 4.1 , 4.2, put custom ROMS as omega, cyanogenmod and not work, it always stays at Turning on and ever on, not how to solve this problem try everything really, I am currently in version 4.3 and I still have the problem, here attached an image.
Did you try flashing back to a stock TW rom? Some signal issues were fixed for me when I restored back to stock, let gps lock, then set up custom rom.
Sgh-i747
Quantum style
aircooledbusses said:
Did you try flashing back to a stock TW rom? Some signal issues were fixed for me when I restored back to stock, let gps lock, then set up custom rom.
Sgh-i747
Quantum style
Click to expand...
Click to collapse
I put the stock rom and the same thing happens with the custom also, you say that you install rom?
Somneus said:
I put the stock rom and the same thing happens with the custom also, you say that you install rom?
Click to expand...
Click to collapse
when some of the lte builds I was running played havock on my signal setting, reception and such, the only fix was to revert back to stock (for my phone), update the boot loader and modem, then try the custom again. Im speaking from the experience of the ATT I747, but I imagine it could be similar with the international version of the s3.
You did everything, flash a lot of roms and none is solved
Hey guys! I'm using a Galaxy Note with a Bell board (was originally AT&T but that bricked because at the time I thought flashing an N7000 ROM would work, D'oh!) and I want to upgrade to a Jelly Bean Rom. I'm using Blackstar XI, a 4.0.4 ROM, and I'm looking for a lightweight JB rom. It can lack stylus/pen support, I found myself not using that feature as much as I thought I would.
Would I run into any issues using a QuincyATT Cyanogenmod 10.1.3 ROM, considering it's a Bell note board? Would I need to unlock my SIM first? And I recall there being a trick with Notepad++ I needed to do in order to make it work, even on my AT&T board.
I just have an issue with heavy RAM usage at boot and I can't even run some apps, since I know touchwiz is stupid.
Anyone willing to help me get it running on my note? Any help would be appreciated!
MoronDroid said:
Hey guys! I'm using a Galaxy Note with a Bell board (was originally AT&T but that bricked because at the time I thought flashing an N7000 ROM would work, D'oh!) and I want to upgrade to a Jelly Bean Rom. I'm using Blackstar XI, a 4.0.4 ROM, and I'm looking for a lightweight JB rom. It can lack stylus/pen support, I found myself not using that feature as much as I thought I would.
Would I run into any issues using a QuincyATT Cyanogenmod 10.1.3 ROM, considering it's a Bell note board? Would I need to unlock my SIM first? And I recall there being a trick with Notepad++ I needed to do in order to make it work, even on my AT&T board.
I just have an issue with heavy RAM usage at boot and I can't even run some apps, since I know touchwiz is stupid.
Anyone willing to help me get it running on my note? Any help would be appreciated!
Click to expand...
Click to collapse
If you like blackstar, I would just flash Blackstar Blackjelly after doing a backup. It's what I've been running as my go-to on my Telus note. The other jb's are great too, but cm comes with the odd small bug like echo on speaker phone. Most of the customizations make them worth trying though.
Sent from my SAMSUNG-SGH-I717
Sweet. I could give that a try if the Cyanogenmod ROM doesn't work. Is there anything I need to do in preparation, since this is technically a Bell note? Or can I just go ahead and flash the ROM without any changes to the ZIP?
MoronDroid said:
Sweet. I could give that a try if the Cyanogenmod ROM doesn't work. Is there anything I need to do in preparation, since this is technically a Bell note? Or can I just go ahead and flash the ROM without any changes to the ZIP?
Click to expand...
Click to collapse
I'm assuming you have an unlocked bootloader already since you are running cm. Just be sure to have latest cm recovery or gimmeitorilltell's twrp (although other versions work with Jellybean, if you try kitkat or lollipop you'll have problems). Make sure you are flashing a quincyatt rom.
I have been using SGH-I717ATT-UCMD3-Modem with great success for a radio. Your mileage may vary.
If you get no signal, before blaming the rom, first check your mobile networks access point names and settings to be sure they match your carrier. (A good idea is to take a couple screenshots of your settings now before you flash any new roms as there are quite a few numbers involved)
Sent from my SAMSUNG-SGH-I717
Good news! I tried the CM10.1.3 ROM and it worked well minus two small gripes:
1. Occasional freeze/hang on lock screen, causing it to reboot
2. Random artifacting/crashes during video playback/browsing through gallery
I'm gonna say this is the best performing ROM I've tried so far, but I'm going to give BlackJelly a try! I'll keep you posted. Just figured I'd give Cyanogenmod a proper shot now that I know how to install ROMs!
developweb said:
I'm assuming you have an unlocked bootloader already since you are running cm. Just be sure to have latest cm recovery or gimmeitorilltell's twrp (although other versions work with Jellybean, if you try kitkat or lollipop you'll have problems). Make sure you are flashing a quincyatt rom.
I have been using SGH-I717ATT-UCMD3-Modem with great success for a radio. Your mileage may vary.
If you get no signal, before blaming the rom, first check your mobile networks access point names and settings to be sure they match your carrier. (A good idea is to take a couple screenshots of your settings now before you flash any new roms as there are quite a few numbers involved)
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Time for BlackJelly! Downloading now.
I also may need some help getting the SIM to work once this ROM is on. So that way, I can use this stock-rom based OS for actual phone things instead of it just being a tiny tablet! Yay!
Can you point me in the direction of the latest TWRP recovery that I can flash through Odin?
MoronDroid said:
Time for BlackJelly! Downloading now.
I also may need some help getting the SIM to work once this ROM is on. So that way, I can use this stock-rom based OS for actual phone things instead of it just being a tiny tablet! Yay!
Can you point me in the direction of the latest TWRP recovery that I can flash through Odin?
Click to expand...
Click to collapse
I'm not sure about Odin, but I flashed the latest TWRP to my device using Rashr from Google Play store.
Other install methods are described here:
https://twrp.me/devices/samsunggalaxynote1att.html
Sent from my SAMSUNG-SGH-I717
developweb said:
I'm not sure about Odin, but I flashed the latest TWRP to my device using Rashr from Google Play store.
Other install methods are described here:
https://twrp.me/devices/samsunggalaxynote1att.html
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Upgrading my recovery now, yay! I also have the Phase kernel because I've heard a lot of good things about it.
MoronDroid said:
Upgrading my recovery now, yay! I also have the Phase kernel because I've heard a lot of good things about it.
Click to expand...
Click to collapse
Backup, backup, backup. If TWRP successfully installs then backup. If something goes wrong you can revert everything or just the boot partition. (Kernel)
Sent from my SAMSUNG-SGH-I717