Hey guys. After rooting it, I messed up with xposed and my phone started rebooting. It was usable, but whenever I would open any audio file, it would reboot. So I tried wiping my data in recovery and now I can't leave the starting setup! It always reboots when I'm digiting my wifi password. Does anyone know how to fix this? Got my phone yesterday.
Update: Got it past the starting setup, and can use it. but it's still rebooting all the time.
Figured the problem was with the asus keyboard. Backed up my swiftkey and it works just fine. but still can't hear any music and who knows what else
Ksagrande said:
Hey guys. After rooting it, I messed up with xposed and my phone started rebooting. It was usable, but whenever I would open any audio file, it would reboot. So I tried wiping my data in recovery and now I can't leave the starting setup! It always reboots when I'm digiting my wifi password. Does anyone know how to fix this? Got my phone yesterday.
Update: Got it past the starting setup, and can use it. but it's still rebooting all the time.
Figured the problem was with the asus keyboard. Backed up my swiftkey and it works just fine. but still can't hear any music and who knows what else
Click to expand...
Click to collapse
Be aware that there are xposed modules that either don't work or could cause issues. If I was you I'd stop all the modules, see if it has the problem on reboot and if it doesn't, try them one at a time.
If that doesn't work you might need to do a factory reset to undo the bad thing you did...
ultramag69 said:
Be aware that there are xposed modules that either don't work or could cause issues. If I was you I'd stop all the modules, see if it has the problem on reboot and if it doesn't, try them one at a time.
If that doesn't work you might need to do a factory reset to undo the bad thing you did...
Click to expand...
Click to collapse
Yep. I knew about the modules. I was just dumb lol. All modules are off. Also already did a factory reset but it didn't work. It's not rebooting anymore, since um using SwiftKey, but I just don't have any sound. And it's like the sound can't be processed. When opening a song on poweramp it keeps going to other tracks until I close it, and the other players just get stuck. All the system sounds are also not working.
Just found out the calls work. Only in the loudspeaker though. Funny
flash stock ROM over and I don't see how that could not solve all your problems.
Fed4Lyfe said:
flash stock ROM over and I don't see how that could not solve all your problems.
Click to expand...
Click to collapse
Just did it and it solved everything. Thank you!
Related
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
I used to have the problem described in this thread (http://forum.xda-developers.com/lg-g3/help/wi-fi-bluetooth-fm-radio-d855-t3284582/) and it evolved to another problem so I've decided to create a new thread.
I've already factory reset my phone several times, had marshmallow, lollipop and kit kat (current version) and none of the versions seem to fix my problem.
My phone randomly has wifi and bluetooth and other times it just doesn't. When it has wifi, I can use the phone for a while and after that the phone will simply crash and start bootlooping or will boot and turn off right away or turn on and have no wifi(and IP adress unavailable on settings). When the phone has no wifi, I can use it as I want , it won't randomly crash or start bootlooping.
Trying to reboot the phone will, most of the times, result in a booloop which can only be solved by removing the battery(sometimes even that won't solve it, and I have to wait a bit before I can put the battery back again)
Is there any way I can find out what's causing the bootloop, like a log or something through adb?
Really hoping you can help since I'm running out of ideas. Thanks for your time.
myclarity said:
I used to have the problem described in this thread (http://forum.xda-developers.com/lg-g3/help/wi-fi-bluetooth-fm-radio-d855-t3284582/) and it evolved to another problem so I've decided to create a new thread.
I've already factory reset my phone several times, had marshmallow, lollipop and kit kat (current version) and none of the versions seem to fix my problem.
My phone randomly has wifi and bluetooth and other times it just doesn't. When it has wifi, I can use the phone for a while and after that the phone will simply crash and start bootlooping or will boot and turn off right away or turn on and have no wifi(and IP adress unavailable on settings). When the phone has no wifi, I can use it as I want , it won't randomly crash or start bootlooping.
Trying to reboot the phone will, most of the times, result in a booloop which can only be solved by removing the battery(sometimes even that won't solve it, and I have to wait a bit before I can put the battery back again)
Is there any way I can find out what's causing the bootloop, like a log or something through adb?
Really hoping you can help since I'm running out of ideas. Thanks for your time.
Click to expand...
Click to collapse
problem is that most logs get cleared at boot, last kmsg might have some info but why not just do a cse flash of the kdz ?
suljo94 said:
problem is that most logs get cleared at boot, last kmsg might have some info but why not just do a cse flash of the kdz ?
Click to expand...
Click to collapse
I'll get last kmsg and post it here in a bit.
already done cse flash, factory resets, etc., nothing works.
myclarity said:
I'll get last kmsg and post it here in a bit.
already done cse flash, factory resets, etc., nothing works.
Click to expand...
Click to collapse
and you tried diffrent versions I see it might be a hardware failure
suljo94 said:
and you tried diffrent versions I see it might be a hardware failure
Click to expand...
Click to collapse
I've attached some files after turning wifi on when ip adress is unavailable, hope this can help :/
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
anyone haveing issues with random reboot ? mostly happens when im playing pandora through blue tooth the screen screen wont turn on stays black and the music starts to skip and then boom it reboots when i installed mm i did it over the air then did a complete restore never did it before always worked perfect but since i installed mm this issue happens battery life is terrible as well and laggy anyone have this issue or know how to fix it?>?
ANYONE???
blaze86dubz said:
ANYONE???
Click to expand...
Click to collapse
Did you restore all your apps from 5.1? If you do, you need to do a factory reset, then restore only the apps without restore data. I would restore just a few and see if the reboot fixed.
the only thing i brought over from before was my caLL log and pics everything else i started fresh
Hi,
Not too sure if anybody else has had this problem. Every day morning, when I try to use my phone first time in the day, the phone app does not open. It opens and closes within half a second. It has been happening daily. A reboot fixes the issue for the moment.
However, need to check if anybody else has been facing this issue.
I am running stock 3.2.6.
To resolve the issue, I have tried hard reset, flashing stock OS, flashing 3.1.2 and then flashing the incremental OTAs, almost everything I have tried.
Looks like the issue has not been resolved at all. Tried switching off the doze mode as well. Not helping.
Anybody has any guidance/solution to this problem?
deepakmasthi said:
Hi,
Not too sure if anybody else has had this problem. Every day morning, when I try to use my phone first time in the day, the phone app does not open. It opens and closes within half a second. It has been happening daily. A reboot fixes the issue for the moment.
However, need to check if anybody else has been facing this issue.
I am running stock 3.2.6.
To resolve the issue, I have tried hard reset, flashing stock OS, flashing 3.1.2 and then flashing the incremental OTAs, almost everything I have tried.
Looks like the issue has not been resolved at all. Tried switching off the doze mode as well. Not helping.
Anybody has any guidance/solution to this problem?
Click to expand...
Click to collapse
try to reflash stock.. make sure its a clean flash...
never experienced this.. seems that your the only one experiencing this..
reyscott said:
try to reflash stock.. make sure its a clean flash...
never experienced this.. seems that your the only one experiencing this..
Click to expand...
Click to collapse
Thank you for responding.. I did all this and more.. still the issue persists. Not too sure what's the problem.
deepakmasthi said:
Thank you for responding.. I did all this and more.. still the issue persists. Not too sure what's the problem.
Click to expand...
Click to collapse
Make a clean install of the full 3.2.6 ie after wiping system, data and cache/Dalvic. Do not install the earlier version/s and update via OTA or flash the OTA.
Maybe you have some app that is conflicting with your phone app.
Sent from my ONEPLUS A3000 using Tapatalk
Seems like the issue was due to a specific app. U sure though.. I uninstalled a set of apps which I had installed before the issue started. Currently looks like it has been resolved.
Same thing is happening for me in 3.2.8 no matter what ... That too only in morning as Mr.Deepak said please help .. I have tried re-flashing ROM etc ... What could be the issue?
@deepakmasthi can u please let me know how did your issue get solved.. as I'm facing the same problem as u.. Please help