[Q] need some serious help - T-Mobile Samsung Galaxy S 4

I have been using ai.keyboard for a long while. There's been an update and 2 more because the first "update" messed the app up, and 2 more Fixes have still not gotten things working right with the app. The phone now boots up and displays a box "Unfortunately, the process com.android.phone has stopped." and the pone won't boot any further.
I have reversed the system using CWM to an earlier version where it worked fine, and for a while things were ok. after a reboot, the updates took over and self updated many apps, and the phone requested a reboot.
Poof! same "unfortunately" message came up.
I reversed the system again to 4 previous KNOWN GOOD, Working well backups, and I still cannot boot the phone.
I can boot into recovery and do all that is allowed, but cannot get it to boot now without that message.
I wanted to fix permissions, but I notice it's no longer in CWM or in "Phills Touch" recovery.
I'm stuck at this point, and would appreciate any help.
I'm on Stock T-Mobile 4.2.2 Rooted and it's a Samsung Galaxy S4 - white
Thank you!
Aloha-
Update-
Flashed a CWM 6.0.3.2 which included "Fix Permissions" but it did not make any difference with the problem at hand.

Operation restored - Phew!
Since I had no alternatives left, I decided to return to stock and see what the results would be.
After restoring to an out-of-the-box bachup, I rebooted, and was getting the same message. I did a Factory restore so that all the Root-required apps would be removed, and after the phone rebooted, the message came out only one time and I reset the phone to work with my google profile, and set all the requirements to make calls via T-mo.
I used the phone for a whie, and having no problems, I decided to try rooting it and see if it would work.... It worked fine!
after a few minutes, I flashed CWM Restore and booted to recovery and recovered my nandroid backup I had made just before all the problems started happening. I got an update message for Ai.Keyboard and did it. BAD IDEA!!!!!!! It farkled up, and then searching the internet I saw already that many users were too, having the same problem I was having! I uninstalled the app, and rebooted and reinstalled the app to see if it would work. It was like I first installed it a loooong time ago, and seemingly, most of the problems except for backing up it's settings worked. So, I'm now re-conficuring the settings manually and the phone is acting normal.
Keeping my fingers crossed!
This is the SECOND time I have gone to such drastic measures. The first time, the problem was that I just could not make or get calls,
and the T-Mobile "Tech" in the store said it was not fixable, and suggested I call support and send it back to repair.
well, maybe the third time I'll have to.......

I am sure it has to do with app.
Sent from my HTC Flyer P510e using xda app-developers app

Related

weirdest bug ever? ET resets to how it was on certain day(like movie groundhog day)

Ok so i have one of the weirdest bugs ever.
Background:
I was running stock rooted rom w/out cwm for about a week. (i had rooted using cwm then installed superuser and then flashed a stock kernel over that so i was rooted, but stock.)
On October 4th i realized that any playlist i made in the music app were dissapearing after a reboot. While troubleshooting that, i realized that ANY changes i made to the phone (Installing apps, downloading files, text message and phone logs) would be erased after a reboot. Furthermore, any files i delete form internal sd reappear after a reboot.
Every time i reboot my phone it goes to the exact configuration it was on October 3rd. The phone still makes calls, uses web, texts, has the apps that were installed prior to oct 3rd etc... just it resets to that every time i reboot.
Things ive tried to fix it:
I have tried using Odin to go to flash a stock kernel, cwm kernel, and countless other kernels. The Odin flash goes through like normal, and it says success and the phone reboots; however, in about phone the kernel is the same and the config of the phone is still Oct 3rd. So that means that even though the odin says it flashed successfully, there is nothing actually being flashed.
Since i am stock i have also tried doing a factory reset and wiping cache through the stock android recovery, again these act like they have done the restore, but when the phone boots it is still in oct 3rd configuration.
I have just ordered a usb jig today, should have it by friday and i will update to see how that works.
I have posted this thread for informational purposes. I dont think anyone else has this problem, or what has caused this problem. It might very well be some user error on my part. Just posting this in case someone else encounters this in the future.
If you have any ideas/suggestion on how to fix this please let me know.
I know that i can just take to sprint and get exchanged but i first want to try to see if i can fix on my own, and since the phone still functions to make calls, texts and everything else its not a super major problem, except that any new stuff i add to my phone disappears.

[Q] I am absolutely stumped, please help

Hi All, I come begging for help after exhausting all of my options and searches for similar issues.
I have a CDMA Galaxy Nexus Stock 4.0.2 but rooted (I installed CWM).
I woke up to my phone stuck in the boot loading screen; it just kept looping over and over. I shut off the phone restarted it and the phone was practically unuseable, it ran very very slow. Now I haven't done anything recently or installed any apps. The only app I installed was a modified MMS app (one of the Inverted Black ones), but that was 2 weeks ago and everything was running fine since then. (However since I'm not on a deodexed Rom, I knew there could be issues).
Well I of course switched back to the stock MMS app that I had manually backed up and that did not help. Now my phone would load, it would get to my homescreen, but it would then say something along, "service is not working, wait, close, or ok?" I'd hit wait and within 2 minutes my phone would automatically reboot and then go into a a sort-of bootloop (it would just show the boot.img and loop).
I then tried to restore two Nandroid back-ups (which were basically bone stock and made months ago) and both worked, except it would say secure.img not found or something like that. I was still able to boot up and use these back ups, but then within 5 minutes I would get the same error and then the phone would reboot.
After retrying them I decided to to just go bone stock and wipe and do a factory reset. This worked and everything seemed fine until I went to turn on wi-fi.
I would wait for wi-fi to turn on and eventually it would just quit and then reboot the phone. I did this 3 times in a row to confirm that it was indeed wi-fi causing these rebooting issues.
Now here's the thing, right now my phone is working as I have purposely tried not to touch the wi-fi (I need to use my phone) . Data, voice, mms/sms all work. But I literally have no idea why wi-fi would be causing my OS to go crazy?
My last resort is to flash the stock toro.img but I was hoping you guys could help me before I get to that point.
As of right now even though I did a data wipe/factory restore my phone is still rooted (rooted apps all work) and my bootloader is still unlocked. (I renamed the secure.bootloader file as per the instructions when using fastboot to load CWM).
Please help me troubleshoot this, Thanks guys.
I don't know if you have tried but maybe try flashing a rom after a data wipe
angelino0919 said:
I don't know if you have tried but maybe try flashing a rom after a data wipe
Click to expand...
Click to collapse
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
JayBeezy802 said:
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
Click to expand...
Click to collapse
Well you can always relock the bootloader. I doubt you will have to go back to stock though

[Q] Stuck on bootloader after changing screen density with Rom Toolbox

Hey guys. As the title suggests, I can't boot my Note 2 (sgh-i317). It is stuck on the AT&T logo and while it's stuck there it vibrates slightly every 5-6 seconds. I tried changing my screen density to 240 and it worked for a bit but annoed me. then I went to change it back and got this problem. I accidentally set it to 360 I think though, instead of 320. I have wiped the cache. I have wiped the data. I have installed roms countless times already with Odin. I'd imagine my reset counter is at over 10 just from today.
I've been searching on google and these forums for hours and have seen many suggestions, but none of them have worked. The farthest I have gotten was to get the phone to boot, but once I start going through all the setup stuff I begin getting error popups saying that Touchwiz home has stopped responding. As soon as I push OK the error immediately pops up again. I seriously can not do anything with my phone.
Is there any way to get a stock build.prop file somewhere for this phone, and if so, how would I install it if I can't even boot into the device?
Any help would greatly be appreciated. I have no idea where else to turn here. Thanks!
-Mark
Do you have a backup to restore from recovery ??
If not....then power down the device and remove the SD card and place it into a PC card adapter...
Then download or copy over a suitable rom...
Then place the SD into the phone and boot into recovery...
Fully wipe the device and flash the rom of choice...
Reboot....set....profit....g
Edit:
Are you certain that your power button is not stuck ?
If the method I suggested fails... and rebooting occurs with vibration...then your power button is suspect....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks. Well I got it to boot finally, however there's been a couple issues since. It's on 4.1.2 right now...
1. Whenever I try to officially update to 4.3 through the settings, it downloads, then when installing it ALWAYS fails at 25%.
2. This is a big issue. My data connectivity is gone. I have no 4g access period. If I'm not using a wifi network, I can't do anything online, period. I've reflashed numerous times, and can't get it to recognize the network. I can make calls just fine, just no data.
I've tried wiping data and going to factory reset, but this doesn't help in any way whatsoever. I've popped out the battery and sim card and reinserted after a few minutes, still to no avail.
The funny thing also, last night my friend, who has the same phone, updated to 4.3 and got the EXACT issues I've been dealing with. The ONLY thing in common is that we have both rooted our phones in the past. When I first got 4.3 it worked fine. It wasn't until I rooted that these issues began. My friend's phone was not rooted, however it had been in the past. I'm thinking that this 4.3 update has an issue with phones that are rooted or have been at some time. I don't know how it can tell, but that's all I can think of. his phone now is also a doorstop, like mine.
K, fixed data connectivity from another thread here. For some reason, even if I wipe my system, it seems to still keep settings intact. In this case, nothing set in APN. Seems the more I try to fix my phone, the more problems show up.
If you updated to official 4.3...then yes ...a whole new host of problems are yours until the devs figure out the locked bootloader and it's knox flag...
Backups won't restore....and so forth...
Read around ....you'll see...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

[Q] Updated to 4.3, now GApps continuously force closes

I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.

No call connection until restart and no rom change

I have 2 problems.
First since a month mine and my wife's phone started to have no connection after dialing some number. We both have the same issue. Let's say I hit to call my friend Tony. SO after pressing name I see connection sceen, I see time of conversation, I see bars but no voice. The person I call to hears me. I tried with different people. Same issue on both phones.
After restart calling is normal. Airplane mode off/on doesn't help.
On June 2014 we finally decided to switch roms. So since then we have Cyanogenmod 10.2.0-hercules (4.3.1). It was alright, beside problems with camera, 30% of photos and videos have defects /artefacts.
SO I thought maybe changing rom will help.
I spent whole day on searching stock roms but all files are deleted and i can't find neither one of last 4 versions.
So I thought I will change rom to earlier version of Cyanogemod. It didn't help.
Today I spent few hours too and finally decided to change rom to 4.4.2 | HellKat (first that succesfully wanted to download).
Something went wrong.
I thought I was doing everything right and there are no tricky parts but I guess I forgot to do something or... maybe something is wrong with my phone.
So I'm using TWRP. First I hit "factory reset", then "advanced wipe" and and wiped everything beside sdcard.
Then I installed my new rom, after few seconds, it shows "failed"
So I wiped everything again and tried to restore my backed up rom.
It showed "failed"
SO I wiped everything again and installed my current rom.
It shows "failed".
I started to worry and to think that I just want my old phone back, at least it works... sometimes.
I hit reboot, wipe, and install again my current rom.
Success. (Maybe reboot after wipe is needed? or maybe it's coincidense)
Finally.
I hit reboot and installed gapps.
So I was almost happy that i could go back to where I was.
Not quite...
I started to download my apps.
On second one screen went black.
Actually it powered off.
I tried to turn it on but it was only showing Samsung logo and black screen after that.
I went to TWRP, wipe, install current rom 3 times.
It seems that restart after installing makes phone bad and I can only see black screen without even booting. Ewentually I found out that now I have 60% chance that if I hit reboot I won't be able to come back to my system.
I will have just black screen and the only way to have working phone is install new rom again and not restarting.
Or maybe it's just coincidence but I don't have time to play and spend another hour on wiping, installing rom and the gapps and apps.
I hope you guys see some stupidity or some detail in what i did wrong.
I hope that maybe one of you will actually will be able toi help me with chagning rom the right way or to fix that connection issue.
same, sort of.
I have similar issue. I cant make calls unless i reboot. And it seems when i open an amount of apps, the calls just dont work. I dont know what to do.
Make sure you're on the latest TWRP, earlier versions will not successfully flash newer roms.
As for the voice thing, did you have snapchat installed? It's been reported to occur when you have snapchat installed.
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app
DarkMatter_74 said:
Make sure you're on the latest TWRP, earlier versions will not successfully flash newer roms.
As for the voice thing, did you have snapchat installed? It's been reported to occur when you have snapchat installed.
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app
Click to expand...
Click to collapse
Funny fact, before you wrote we have been testing our phones and found out that it is actually snapchat who makes a problem wih calling. We uninstalled it from botrh phones and 3 days it is ok
I will install new TWRP , hopefully there is newer version.
Just a heads up, Google Hangouts Dialer has the same effect as Snapchat as well.
Is there any way to avoid this? i use snapchat often, and removing it would be a loss :/
blackwing102 said:
Is there any way to avoid this? i use snapchat often, and removing it would be a loss :/
Click to expand...
Click to collapse
There's an older version of Snapchat that works without booking your audio. Search the threads for it. If I come across it anytime soon, I'll return with the link.
Edit:
http://forum.xda-developers.com/showthread.php?p=57344868
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app

Categories

Resources