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?
Related
OK, I have searched for this, but have not found it in this context. I did a flawless OTA and install of 4.3 on my S4 Active. After install I had an image of an open padlock and the word "custom" show up on a boot screen, Used to get this in the early root days, but not for several month after following some tips elsewhere in these forums.
I also had trouble connecting WiFi unless I rebooted. Whether I needed or not, I did a complete factory restore, which seems to have cleaned up the WiFI thus far, but not the lock/custom situation.
Any ideas or suggestions?
So I think I messed up my phone.
TL;DR: Messed up phone by removing stock rom, Costume roms don't work except 1 and in that one IMEI is set to zero and I can't connect to any network.
several month ago I had the stock xperia z Lolipop and made a decision to root the device. I unlocked it's bootloader and did the rooting... all as planned. about a month later my phone started acting funny, so I decided to reset it, the problem is I had installed TWRP and as noob in using the app, I accidentally wiped the entire device. I thought I had bricked the thing so I left it aside.
I had been using an older phone as replacement until last week when I thought I'd give the Z another chance. I looked around this forum, found a bunch of stuff, tried a lot of roms and after failing to make 4 roms work (Cyan nougat, Cyan MM, Costumised sony 5.1.1 and a stock one I found here) I managed to find a fifth one that worked (http://forum.xda-developers.com/xperia-z/general/android-5-1-available-yuga-pabx-t3054304). I always followed the tutorials but I may have done a lot of mistakes... for example I'm not even sure what kernel is and if I needed to change it for any of the roms or if I needed to like wipe the entire system or not before flashing ( I did all the time), and what about rooting? does the system require a previous rooted rom to install new ones? don't we simply format the entire device?.
Now the major problem of the working rom is that my phone can't connect to it's simcard network, the simcard is working since it requires pincode on start and the phone can find the networks by manual search, it simply gives an error "network XXX unavailable". I looked around and saw that my IMEI is set to all zero's in the phone about section. this could be unrelated to the network problem... but I don't have much expertise in these stuff.
So right now it seems like I can't install any other roms (they won't even start up, most get stuck during boot) and the only one I can install doesn't give me network access.
Any Ideas?
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.
Hello, I had tried posting this where I assume it belongs but I can't seem to post anywhere but here. Anyways, today me and a friend rooted his ROG Phone 2 via rooted ROM we had found here. Everything had gone to plan, unlocked the boot loader with Asus's tool, fastboot the custom ROM, ran Magisk and let it update, confirmed root with it and a cheapo Play Store root checker, all was good.
First issue, WiFi didn't work, but no big deal, unlimited data. Then he discovered that sound didn't work, so I immediately looked it up, didn't find a post specific to his phone but someone mentioned the mic not working in the one I read, gut feeling I told him to check the mic, loe and behold, not working.
He doesn't want to have to reset to factory ROM and lose the root. Ant idea what's wrong? I could find the post we followed if requested before I find and post it anyways.
As mentioned it's the new Asus ROG Phone 2
Model
ZS660KL
The 512GB/12GB RAM
As far as I'm reading is there shouldn't be any exact issues and is no particular reason. We read later on in the comments, someone had the WiFi issue but the OP assured his didn't have the issue.
WiFi isn't a major need, again, data. But the sound and mic is a huge issue as it's his daily. I'm familiar with rooting and custom ROMs, mainly Samsung's. I'm quite confused, I've never had a major issue with a ROM that doesn't have a simple work around.
What firmware version is he on? He has to make sure that the magisk-patched boot image matches the firmware he has installed or he will have issues like the ones you describe with WiFi, sound, and possibly abnormally long boot times.
This is a boot image issue
Had the same issue when rooted.. i flashed the ww rom again to unroot my device now everything works. Hopefully someone can give a solution
He's working on patching a fresh ROM from Asus, that's the only idea he can make right now.