Hello,
I received a at&t galaxy s6 edge, it was rooted and kept popping up knox warnings, so I looked at the baseband version and it was G925AUCU6EQCF, I googled that + stock rom which lead me to this thread.. which I downloaded and flashed using Odin, afterwards my touchkeys/softkeys just no longer work. They were working before flashing.
I've tried, wipe cache, factory reset, safe mode booting, *#2663# -> sensorhub fw update is grayed out, I also tried multiple new charging ports.
Little background, I don't know much about rooting and android roms, but I run a repair shop and do bunch of hardware repairs. I recently received a dozen or so assorted s6, s5, s6 edge, note3, note5 which all appeared to have been throwing KNOX warnings (among other issues, broken screens, charge ports, etc..). Now I'm not completely oblivious to this stuff, but I've flashed stock roms and installed twrp +root before on samsungs. For 10 of the phones I googled the baseband +stock rom and was able to flash it back to stock and KNOX warnings went away and all were fully functional, not sure If I'm doing it right but it works, perhaps unrooting would have been easier/quicker?
I opened up the phone and tried a working charging port from another s6 edge which I know the softkeys work, but I still got no touch on them, they only light up but no function or vibrate, so I did some googling and noticed I may not be the only one. I've seen some threads here but for other samsung phones, some mention something about "flash some idlekernel that will update the touchkey's FW", another mention build.prop and other "qemu.hw.mainkeys=".
Now, I am not all too technical with this so I was hoping some handsome generous person could help me out or point me somewhere, anywhere
Thanks!
Related
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?
Hello XDA, I'm having a problem with my grandmother's phone, and I'm in a hurry to get this fixed because she needs it for business. Her phone is an AT&T Galaxy Note 3 SM-N900A unlocked to T-Mobile. It was running Android 4.4.2 KitKat, and I tried to update the phone as I did with my grandpa's, who has the same exact phone before we switched to T-Mobile. Because it was unlocked, the phone couldn't receive the OTA Lollipop update due to the SIM card not being AT&T.
After spending 4 hours searching and trying solutions, I came down to one thread on XDA Forums here. I saw it and I ended up using Odin 3.09 to flash the All-In-one/Non-Wipe Tar file onto it, now my phone is stuck in a boot-loop. Strangely, the Lollipop update seems to be installed as when I plug her phone into my PC/charge it, the battery screen is different than the old one which looked shiny and not flat and material like the Lollipop one. Knox has not been tripped, system status is OFFICIAL, and every time I turn on the phone, it proceeds to boot until the AT&T logo screen, where it freezes mid-way vibrates 2 times and boots the same way over and over again.
Is there anything I can do aside from doing a wipe or factory reset, as I mentioned before she has to use the phone for a business she works for and she had somewhat important work on the phone. The worst part of it all is I was stupid and ignored the warning to back my data up first in the firmware thread. Please help, I'm in a very big hurry to solve this and finish the updating/problem.
P.S If it's not a boot loop and it's called something else, whatever. xD
Did you try using Smartswitch to see if it can see and repair and/or reflash? A factory reset may be the only way to fix it because I believe the file layout for KK and LP and different.
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
I'm sure there are several possibilities that could be software related. However, I've had this issue on a couple of my older phones and it just turned out that the power button was sticking. Just had to pull the phone apart and clean it.
If nothing else seems to work for you, it wouldn't hurt to check this.
PS: I have 4 boys who like to play on the devices with sticky fingers.
The story
Hi everyone, thanks for reading me and thanks for your time.
I am stuck with this galaxy S5.
I got a S5 in the past, a beautiful SM-G900F on which I run lineageOS no problem whatsoever.
I bought another S5 from ebay, turns on it's a G900A.
Had problems from the start, the phone seemed to often restart instead of turning off normally, and I had severe battery drain both while on and while turned off. So I went to this section and looked at Root, Roms and other cool stuff and followed the guide to put up a custom ROM.
The problem
The first step, installing the experimental firmware, seemed to work but after reboot no OS would install, instead I got "MODEM CRASH".
So from there, I tried to roll back to stock.
I put on BOF3, which works, but since then I have baseband null and IMEI unknown.
Panicking, I tried to install COI5, but same problem there and also multiple bugs, so I went back to BOF3 and it's all functional, but same baseband/IMEI problem.
I have tried to reset to the oldest stock G900AUCU1ANCE but ODIN fails at the very start. I seem to understand I'm on android 5 and cannot rollback now, somehow.
If anyone has any idea on what I can do realistically.
I have no EFS backup as when I started I didn't know what EFS was.
Thank you all for your help.
I have seen many topics with this problem but I have only been confused more by them so forgive me for posting here.
Bump!
Can anyone help?
So I have a Galaxy S10 verizon that was working fine, was up to date with all updates and etc and all of a sudden it decided to keep on freezing then reboot. Figuring it was a software issue I already have done the following with no luck
-Wiped cache
-Ran in safe mode
-Full wipe restore of the system
None of them have worked so I then proceeded to obtain the combination files and have reloaded the phone fresh using Odin new figuring it was a corruption in the software.
After it successfully finished loading the problem is still present after about 30 seconds after rebooting the phone. I don't know what else I can do next besides playing around with a custom rom maybe to see if the reboot loop is still present.
Any Ideas what else I can do or try?
Phone is in perfect condition, never dropped, no water damage, never flashed anything to the phone and was running just the stock verizon firmware. Phone doesn't even has a scratch in it...
Any ideas would be greatly appreciated!
If a data factory reset in recovery didn't work nor flashing stock firmware with ODIN, then it's probably hardware related and thus you will need to claim insurance if you have it with your carrier or warranty thru Samsung if it's still in warranty.