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?
Related
I have a rooted GT-P6210 that was working perfectly fine and last night I updated Busy Box Free from Google Play. Busy Box Free reported an error with the install and shortly after I noticed that my Wi-Fi would no longer connect. It just reports "Error" after trying to connect to Wi-Fi.
I tried re-rooting my device but that didn't fix my Wi-Fi issues. I researched everywhere I could think of to unroot my device but all the threads seem to refer to guides that I don't see and firmware links that no longer work. I managed to find a copy of Odin3-v3.04 but I still don't have instructions on how to do it nor do I have the firmware that I need.
I decided I would try going back to factory settings by powering off the device and booting into system recovery. I have done a wipe data/factory reset multiple times but Wi-Fi still doesn't work and I don't even know if that removed the root job I did.
When I plug my device into my PC and run Samsung Kies it reports that I have the latest firmware PDA:LA3 / CSC:LA3 (XAR)
So I am stuck and not sure what to do at this point. I have a pretty useless device that won't connect to Wi-Fi. I don't know if I wait around for ICS and install that if it will fix my problem.
Is there anyone that could help me restore my device to factory settings with actual guides, and provide working links to the firmware I would need?
Thanks for your help,
Bryson
You are in the wrong forum.
This is Galaxy Tab 7" not plus.
Might be better asking at the right place
http://forum.xda-developers.com/forumdisplay.php?f=1426
I have an SCH-i800 that I have CM9 (p1c 9.1.0) installed on. I have been using it for several weeks with no problem. Since I am planning on going on a trip, I decided to active pre-paid Verizon service for the tablet. At first, I attempted to activate the device. It went through the phone call but after a minute, it just sat at activating. That is when I noticed that the radio state in the status bar had an X on it. I rebooted the tablet to try again and got "com.android.phone has topped unexpectedly". I re-flashed CM9 (at the time I was using 9.0.0) and it worked again. Activation was not necessary. After a day, the error came up again and radio state went to off with an X. I tried 9.1.0, same problem after a day. I even tried a nightly CM10, same problem. Reboots, cache wipes, permission fixes do not make it work. The error persists until a re-flash of CM. I see on the Support Downloads for the Verizon Tablet, there are two modem files. My baseband version is currently S:I800.0.3V.EI04. I have attempted to "flash" these both via Odin (which failed after a couple minutes) and ZIP (which looked like it worked) to the EC02 on the site, but my baseband doesn't seem to change.
So my first question is, is there a how-to on flashing as I have searched high and low on one for the Verizon Tab specifically, and have yet to find one. Is there a ZIP file that is specifically meant for the i800? I am almost certain this is my problem and that a downgrade (this tablet when stock was updated to the latest Verizon image).
My second question is, has anyone else experienced this? Is there someone that is using a CM9 Verizon tab with EI04 baseband and not have this problem?
Is there a way I can track down what crashed the program? I have tried logcat, but it doesn't appear to give me much detail other than to tell me that it stopped.
And if you ask, no I did not use the Verizon service with this tablet before putting CM9 on it, so I wouldn't know if it worked before.
Any input that someone could provide would be useful. Thanks!
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?
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,
So my Moto X (1st gen, 2013, XT1058) used to work fine on KitKat but after it auto-updated to Lollipop it started messing up more and more every day. The phone is fully stock and locked. Here's a brief list of problems:
random freezes and crashes of apps and the OS itself
random screen freezes (doesn't respond to touches) or completely blank screen apart from the notification bar, often times nothing help but a reboot
random reboots, "optimizing apps" every so often on boot, especially when on charger
flaky and unreliable WiFi, not connecting when it should or disconnecting at random including when screen goes off (despite having "always on" selected)
GPS would sometimes have difficulty acquiring lock and would lose lock randomly (worked just fine before)
I'm not quite sure what to do at this point. It's the AT&T variant which means the bootloader is not unlockable. It is also updated to the latest OTA (build LPAS23.12-21.7-1) which means no rooting method works, or at least I haven't been able to find any. So I can't get even a temproot. I tried everything I could find, nothing worked and I'm running out of options. I love this phone and I'd like to get it back to working order. I'm wholeheartedly hoping someone here will have some good advice or some resource I haven't tried.
Here's what I tried so far:
multiple factory resets, both from system settings and through recovery
didn't help, works for a while but all the issues reappear soon after
rooting with KingRoot
failed, rooting method not available
rooting using this method
failed (not surprising, it does mention it doesn't work on OTA)
unlocking BL via Moto's official unlock service
device not supported
installing moforoot
failed, mofoverify just quits silently and the phone shows a message about some missing fastboot var
unlocking BL using Sunshine
says the device should be supported but then fails acquiring temproot, the phone just reboots
reflashing stock KitKat from here (file: ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip) via fastboot
failed, OS/BL downgrade not allowed
reflashing stock Lollipop from here (file: ATT_XT1058_5.1.0_LPAS23.12-21.7-1_cid1_CFC.xml.zip) via fastboot
partial success, managed to flash a few parts, however it fails on all relevant partitions (gpt, boot, system), reports "downgrade not allowed" just like with KitKat which is surprising, this version/build should be exactly the same as what's currently on the phone
wiping userdata and cache via fastboot
didn't help
I might have tried some other things/methods too, this is just what I could remember right now.
Again, I'd very much appreciate if someone could help me revive this phone. I enjoyed using it while it was working well and I'd like to get it back to that state. Any help is very much appreciated.
Cheers!
I'm having exactly the same issues on my wife's moto x. The only thing I've been able to do for a temporary fix is to enter stock recovery and clear cache. Is there really no root/custom rom method for this device?