Title says all, i have already re-flashed and checked the md5 to make sure it wasn't a bad flash...
I wish i would have backed up my original BL ever since i flashed the OA1 BL i have had screen flickering issues and have to push my power button 5 to 12 times in a row to tun the screen ON from waking up..
The screen will flicker really bad when i set it to low dim but bump it up and it works fine.. When i'm actually using the phone it works flawless no screen issues but run into trouble every single times when i try to turn the screen ON from a wake.
That's why i believe it's not a hardware issue. it's something in the firmware not working correctly in my revision model of the g900a.
Can i please get some new boot loaders to try out that someone might have???
I will try anything at this point i really need some help!
Bootloader Version:
G900AUCU2AOA1
Specs: G900A / Kit Kat 4.4.2 Stock
Thank you a lot,
-JBriZzeL
Related
I just received a new Captivate from Amazon.com and it has a very annoying problem.
Frequently the home screen button or back button are activated without actually being physically touched. At times I can even watch the home screen button flicker as it is "pressed" repeatedly and the home screen is cycled through.
As you can imagine this is a very annoying problem. A Google search shows that others have had this issue as well but their only solutions have been to return the phone for an exchange. As I am unable to do that at the moment (US phone, and I am overseas temporarily), I was wondering if anyone had any success fixing this problem by using the Odin package to 'reflash' the phone. I'm going to attempt the stock Eclair installation outlined in the Development section.
Any other ideas or suggestions would be welcomed!
Had the same problem and returned it got a new one and haven't had that issue [email protected]!
After upgrading my firmware to JH3 (h t t p://forum.xda-developers.com/showthread.php?t=758176) the problem has gone away!
After upgrading my firmware to JH3 (h t t p://forum.xda-developers.com/showthread.php?t=758176) the problem has gone away!
Click to expand...
Click to collapse
Does this firmware upgrade require rooting??
Btw I was also having same problem I just performed factory reset method and boom...everything is fine since then...reset is the simple solution to most of problems..!
No it does not. But you need the version of Odin that allows you to select specific firmware and the firmware file of course. The One Click Odin won't work.
I tried that first as well but it didn't help.
glio1337 said:
After upgrading my firmware to JH3 (h t t p://forum.xda-developers.com/showthread.php?t=758176) the problem has gone away!
Click to expand...
Click to collapse
Thanks for the update on this.
Hi there,
the proximity sensor on my i9000 isn´t working anymore. Everytime I place a call/get called the screen turns black and freezes. I have to pull the battery and restart it.
Testing the sensor on the LCD-test the screen turned green and the i9000 startet vibrating. Here, too only pulling the battery made it stop.
Here is what I tried so far:
- flashing different stock fw (Android 2.2 / 2.3.x)
- applied handicapped settings
- Using Proximity_Screen_Off App and Sanity-App on stock fw
- blowing air into the USB jack/vacuuming the jack
- opened the device to mechanically clean the sensor
All of the above failed!
The only way I can get it to work is when running android 2.3.7 Joker´s MiUi and run the Proximity_Screen_Off App.
Are there any other suggestions as to what can be tried?
Else I will have to get a new motherboard, because wouldn´t want to be restricted to using only one particular rom.
Any input is greatly appreciated
Thanks Christine
if i recall good (but kill me ive drinked some atm) the greensih issue was showing with voodoo color kernels and all the sensor peoblems came with badly assembled kernel.
so i would advice you to reflash pure 3 file firmware (repartition pit and all that jazz)
and if your sensors still would not work just reflash to your carrier or stock formware for your region and push it to repair center with proper dwscription (do no mentions miui or other crap)
Thanks for answering!
I flashed 3-part firmware, pretty much everything available and a CF-Root kernel.
So it couldn´t have been a bad kernel.
Can´t take it back to service, no warranty left.
I just flashed 2.3.5 and CF-Root and now I am fooling around with it some more.
I just think it´s weird that it would work with that and only that MiUi.
impossible unless youve got some other galaxy variaant than i9000
I'm trying to install the DK Zen RLS2 ROM here:
http://forum.xda-developers.com/showthread.php?t=2309928
I figured they wouldn't want me mucking the thread up with my personal problems.
What happens when I install the ROM is that it will start up and get as far as the lock screen. Instead of going into the whole new-phone-setup business, it just stays on the lock screen and doesn't respond to any touch input. I can turn the screen on and off with the power button and I can change the volume, but I can't unlock, pull down the status bar, or open the volume settings. Holding the power button won't bring up the power menu (no real surprise) but it will reboot the phone after 10 seconds.
I'm fairly certain I've used this ROM before, but I recently formatted my phone and relocked it and everything in an attempt to fix other issues. I'm able to use other ROMs just fine without getting this issue. So far I've tried Stock with Goodies (http://forum.xda-developers.com/showthread.php?t=2301672) and SuperBLUE (http://forum.xda-developers.com/showthread.php?t=2520499). It seems, from reading the threads, that each of these ROMs is based on 4.3, but considering the way DK Zen rearranges my SD card, I have a feeling it's different (it adds the "0" folders; does that mean that it's a downgrade from or an upgrade to 4.3?).
Any thoughts? The one thing I can see from this ROM is that it gives me a full 4G signal, whereas the other ROMs only get me a few bars. Maybe the ROM isn't being honest, but if it is I'd really like to get it working for this alone (also volume rocker to skip tracks).
Reading through this thread (http://forum.xda-developers.com/showthread.php?t=2470569) it sounds like going with a 1.31 firmware (which DK Zen is based on) will have touchscreen issues if my phone's firmware doesn't match. Checking the Bootloader screen, I have 3.04.651.2 on the OS line. Is that the cause of my problems? Is it possible to downgrade my firmware, and would that be advisable anyway?
I feel like not many people run into this issue, or if they do they already know why, but I might as well post what I did here.
The touch panel firmware in 3.04 isn't compatible with earlier ROMs (or at least 1.31 ROMs). So, I had to go back to an older firmware. To do that, I just used Rum Runner to get s-off which I hadn't done at any point before. That was a very simple process, though I couldn't do it on my work computer, probably because of all the server and network security software that's installed here.
Once I got s-off, I was able to flash a 1.29 firmware using fastboot. From there, I flashed the DK Zen ROM that I was looking at and the touchscreen worked just fine.
Yay for learning!
It happens randomly when using the phone (it doesn't happen when it's locked). The phone just freezes then restarts randomly.
I tried to find a pattern when this is happening, and found there isn't much of a pattern, but it won't let me add a fingerprint lock (crashes after the 3rd / 4th reading).
I've tried to factory reset and clear cache. I'm running out of options and am preparing to flash a stock ROM via Odin. I'd like to avoid this, since it'll trip knox and this is a new phone so I wanted to avoid flashing anything for now.
Any suggestions, ideas?
I'd say this is a kernel related crash, since it doesn't give any error, just goes out. But I hope I'm wrong.
Baseband: N920CXXU2BPD5
Build Number: MMB29K.N920CXXU2BPD6
Knox untripped.
EDIT: This seems to be a rule: it always crashes when I get to 32% of adding a fingerprint lock.
Here's an update:
Tried flashing other stock ROMs for other regions, still the same problem.
Flashed a custom kernel, still the same problem. -> Not a kernel problem
Flashed TWRP and used it for some time (to test if the phone will do the same). No problem whatsoever. I'm convinced that this is a firmware issue then.
Tried flashing every possible combination of everything. Nothing seems to have any effect. This isn't a software problem.
It's probably a faulty motherboard. The rebooting subsided though.
I'd also like to add that the S Pen holding area (the place where the S Pen is kept inside the phone) has a specific electronic smell (kindda like the soldering smell, but not quite). Really weird.
I voided my warranty by flashing stuff, so I'll probably be looking at a motherboard replacement if anyone's wondering.
Do u have xposed install?
Nah.
I've been running the stock rom for 90% of the time.
RexGrammer said:
Nah.
I've been running the stock rom for 90% of the time.
Click to expand...
Click to collapse
U solved it already? Mine used to have this problem before but its xposed that cause (in my case :highfive
Still haven't.
I'm almost certain it's a faulty motherboard.
Hey all,
Looking for some assistance here. I apologize in advance for not having specifics on everything, but it's been a couple years since I've needed to do anything with this phone (SM-G900A). I picked it up used a couple years ago and shortly after, I did a NOX unlock and rooted the phone for two reasons - using Titanium Backup and to unlock the WiFi hot spot. I recently noticed that something had happened and my root access wasn't working correctly- guessing from one of the OTA updates that was attempting to occur on my phone. I say attempt, because I don't believe they ever successfully installed since they always seemed to error out. I'm currently on StraightTalk, not an AT&T customer. Something weird was up with it though, because I could never uninstall the Xposed Framework or app, yet Pokémon Go was recognizing it was rooted and blocking my access. I should also mention that I had towelroot running on the phone and it's showing the custom unlocked padlock on startup.
Fast forward to last night- I wanted to return it back to the stock ROM so I did my research, found a couple different tutorials that included the correct ROMs and applied one - G900AUCU1ANCE_G900AATT1ANCE_ATT.zip. After flashing, the phone will not boot and freezes halfway through the swirls around the Samsung logo, then goes blank. The blue notification light also stays lit on the phone.
Thinking it was most likely bootloader related, I found another ROM that included separate AP, BL, CSC files. I attempted to flash the bootloader, which failed and I got the following error on the phone - SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
At any rate, it seems like my boot loader somehow got corrupted or isn't compatible with this ROM, but I was hoping some of you experts out there could provide some answers. At this point my phone is dead, so I'm hoping I can get it restored very soon.
Thanks in advance guys!
The issue identified in this thread (http://forum.xda-developers.com/galaxy-s5/help/g900a-stuck-samsung-logo-black-screen-d-t3050369) seems very similar to mine as well as what's described on this website- http://www.galaxys5update.com/fix-black-screen-with-pulsating-blue-led-on-galaxy-s5-g900a/
I'm seeing the pulsing blue light as well. How do I find the 4.4.4 OA1 Kernel identified in the first link?