OK guys I got a question and I hope that someone can help me out here. I've been google-ing, looking for a similar issue and asking this question in couple of threads and after not getting an usable answer I decided to make a thread about my issue. My S3 emmc is the unfamous SDS affected one and I've been experiencing some lag and freezing so here's what I did with my phone at first:Flashed 4.1.2 XXELLA firmware, Rooted with-CF-Autoroot, flashed PhilZ Recovery v.4.35, Stock kernel.To get a clean installation I flashed the 4 file rescue firmware including PIT file and everything was working perfectly fine...no more freezes or random reboots just EVERY 2-3 days my notification bar used to get totally stuck/gone. Doing no matter what-restarting systemUI...etc,etc I couldn't pull the status bar down anymore until reboot.Tried stopping touchwiz home, clearing cache and dalvik, fixing permissions but it happens again in 2 days of mild-moderate use(web, games, texting, voice calls) Flashed again the XXELLA 4.1.2 firm.from sammobile.com.Changed the kernel as suggested by someone here on xda and it was ok for a while when using Siyah kernel v1.8.9+ until the next day when it happened again. It comes out of the blue just after doing whatever...at first I thought that is somehow related with the Triangle Away app that I used to reset the flash counter but it happened again even after I deinstalled the app. 2 days ago I wiped cache and dalvik, factory reseted the phone and updated it with the new I9300XXEMB1 uk firmware. It was running flawless until today when I faced the same frustrating issue. Out of nowhere after unlocking the screen I tried to pull down the notification bar to turn on wi-fi when..whoa!-there is no notification bar!again. I contacted Samsung U.S since there I got the phone this summer but they told me they don't have any tech support fot the I9300. It is driving me insane...what else should I try..tried hard resetting the device couple of times, tried different roms, different kernels all that is within my range of knowledge and this is my only hope that someone out there will give me an answer or suggestion. Any help will do good, thanks in advance.
Anyone?
Anyone out there please?
I experienced a similar issue, but it haa an explanation, Iwanted a black status bar, not the std dark gray one, then flashed a themed statusbar, when I rebooted, the status bar was gone, Ihad to reflash the rom (crdroid v 11), to recover the statusbar, finally found a theme with black background and white not light gray indicators, (LLC_XXEMA1_2_Jkay_framework_14_9blk statbar), and this one runs perfect, I now our problem is differnt, but give it a try, flash a statusbar theme, maybe, it will work for you, Im not giving you links, because it depends of your rom an framework, luck
Thanks I'll give it a try if I cannot stick to stock as close as possible then I'll try another custom rom like CM 10.1 or a themed status bar...For now the only "solution" to get back the notification bar is to use ROM Toolbox and with the rebooter to restart SystemUI-then it comes back. Uninstalled Dolphin Browser since I noticed that is the only app that I use prior losing the status bar (I might be just guessing idk for sure)
Finally I found a solution for my issue with the phone - SOLD IT! It was driving me insane with the constant status bar loss, no matter what stock firmware after the 4.1.2 jb update or kernel it used to run. Here on the forum I got no answer addressing the exact issue and I think that was the only solution. Bought a Nexus 4 and I really like it. Faster, smoother, better build quality, and I think I can live without the expandable memory and removable battery. Probably that was the last Samsung device I`ll ever buy until they start to manufacture a real quality products and start acknowledging and fixing the issues that follow them. Thanks to everybody here on this site for the help....
I think
I think it's the Custom ROM's SystemUI.apk problem reflashing with the same ROM would not help, i suggest to reflash the device to it's stock ROM and flash it again to your Desired ROM.
iAlexander said:
I think it's the Custom ROM's SystemUI.apk problem reflashing with the same ROM would not help, i suggest to reflash the device to it's stock ROM and flash it again to your Desired ROM.
Click to expand...
Click to collapse
Tried everything my friend...reflashed to stock million times, flashed recovery firmware with pit file. Reverted back to stock with kies, downgraded, upgraded, changed different stock ROMs - nothing helped, felt disappointed and started to hate the phone cause it was driving me nuts so I sold the device and got myself a Nexus 4. I never regret of doing so, much happier, more satisfied overall with this beautiful device. Faster, no bugs,no lag, more quality materials used...now what is left is to convince my girlfriend to follow my steps as she started to experience the very same issue on the newest XXEMB5 firmware on her SGS3.
Related
Hi, i've been experimenting this problem for 2 months. I've got CyanogenMod 9, but before I flashed Cyanogen Resurrection 4.0.3 and I formated everything as possible (Wipe Data, Cache, Dalvik and format /system). The battery doesn't lose charge when I restart it.
Thanks!
So, what is your question..?
Sent from the Matrix
If any of you have the same problem and know the solution. I've read other messages like mine, but I'm not in the same circumstances. I haven't got any apps except social (whatsapp, twitter...) none of my apps it's draining the battery I simply don't know why my phone shuts down by itself
You're running stock kernel right? Have you changed anything at the Performance-menu at Settings? And when do this reboots occur?
Have you tried flashing for example CM10.1 to see if the same problems come up? You could make a Nandroid backup to try this.
Sent from the Matrix
Thanks for the answers. I have the stock cm9 kernel. I don't touch anything at the performance settings. Actually, this problem comes from a couple of roms more. AOKP, ParanoidAndroid, and another one 4.2.1 which I don't remember the name. I've tried a stock ROM before but the performance was not good at all, freezes and slow work at general. Thanks.
Make a full wipe (4) and go as stock as you can. Try it for a day or two and then go back to custom.
You wanna see if it keeps going off on its own, don't worry about performance just yet.
If it does it on all roms you've tried its obviously a hardware issue.
Try a different battery, if that doesnt help then send it for repair.
SGS2 power off issue
Hiya,
I have been running and updating Resurrection Remix and Siyah/Dorimanx kernels for awhile now and this worked fine up until last week. After an update to Dorimanx 7.50 my phone started dropping its network connectivity and powering off randomly, i then updated the Kernel to a new verison hoping the issue had been address (8.3 to be specific) after which my phone wouldnt even go through the boot sequence properly.
After a bit of fiddling i have managed to install an Official JB ROM, (details in the image attached) and network connectivity now seems to be ok, but the phone still powers off...ALOT. Anyone else experience similar issues and find a solution?
Note: I have ordered a new battery in case that is the issue as suggested above, but just checking incase theres something im missing while I wait. Also, the phone is about 16 months old.
Sv: [Q] SGS2 turns itself off
Check your fuel gauge chip. Reset it with siyah or dorimanx kernel.
Skickat från min GT-I9100 via Tapatalk 2
hi, my samsung galaxy s2 started making problems, if i reboot, most of the times I get a black screen which, curiosly, if I press the menu and back buttons, they light up! still, I have to reboot it several times (removing the battery does not help) untill i get a "successful" boot. I'm rooted and I am using omega v13 AOKP, based on JB 4.2.2 but this problem started some time ago, when i was using Omega v24 based on 4.1.2.
My phone is in warranty, but I woud like first to determin if it is a software or hardware thing, because if it is a hardware problem, I have to figure out a way or restoring to stock without leaving traces, so I can use it...
any ideas what the problem might be? the kernels on both versions I used were different, so it has to be something different...
thanks
Clean install of stock first. Test for a few days. Problems persist, then you send it in for warranty service. If the problems go away, then it's obviously something on the firmware you were using side. Try different custom roms/kernels in that case & see if you can reproduce the problem. If you can't reproduce it with other custom firmware, then it's an Omega problem - talk to the dev.
thanks
MistahBungle said:
Clean install of stock first. Test for a few days. Problems persist, then you send it in for warranty service. If the problems go away, then it's obviously something on the firmware you were using side. Try different custom roms/kernels in that case & see if you can reproduce the problem. If you can't reproduce it with other custom firmware, then it's an Omega problem - talk to the dev.
Click to expand...
Click to collapse
thanks, that is was i was thinking, although i hate to waste such an amount of time.. anyway, thanks for the advice, I'll guess I'll have to do it.
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
having the same problem. Did you figure out?
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
illikkalshahid said:
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
Click to expand...
Click to collapse
Hi there,
I have exactly the same problem, have you fixed? How?
Thanks
Q] Galaxy S4 Custom ROM's Issues (no sound, black screen on call)
Omg I was getting to be a little nervous. Still gotta flash but fingers crossed. This is for an att galaxy s4
Hey guys,
I just went from 4.4 KitKat CyanFox back to 4.3 AllianceROM Sammy because it was a bit unstable in my opinion ( The connection to the camera always got lost). So after I did that, my phone freeze every time an have these pixels in red sometimes and also green but i couldnt explain myself why. after rebooting the rom it often doesnt start. Before I flashed the AllianceROM I flashed another Sammy Rom with the same problems.
I took a picture to make it easier for you to find out.
I am not sure whats wrong with it maybe you can help me. Google couldnt :/
Thanks!
Musti
Sounds like hardware, flash a full stock rom after a factory reset to test.
Sent from my GT-I9300 using Tapatalk
Just installed the stock ROM. Flashed it with Odin 3-part. Worked well. Then i put my SIM card and installed Whatsapp, also worked well.
But after starting the Play Store it was the same but now in blue.
You really think it is the hardware or Is it fixable?
thanks,
Musti
So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?