Note 3 remote media control problem - Galaxy Note 3 Q&A, Help & Troubleshooting

Hello everyone
It has been a while since I last started anything here.
I have had a few problems with my galaxy note 3, it freezes, sensors go crazy from time to time, things like that, but most of them I have been able to resolve or work around.
Now I have a new one that I was not able to resolve despite going for the last resort fixes. I have a galaxy gear 2 (not s2, just 2) that has this media control app. After using it, I found out that the app stops working a few hours after the device boots up. Right now all I know is this:
1. Everything works fine once system had a few minutes to load after start.
2. After unknown amount of time, the phone stops responding to gear, bluetooth headphones and cord headphones media control attempts.
3. Bug persisted after I flashed a new ROM and then rooted and used TWRP to get back my data partition (nothing else). Than I wiped cache and dalvik and booted up.
4. Currently trying to do the same but without rooting to see if that helps.
My phone before any attempts:
SM-N9005
4.4.2 Kitkat root stock ROM
TWRP
Ultimate kernel
Xposed framework (a few youtube modules xtorch and wanam)
I would appreciate any advice you have for me. I will update this if not rooting fixes the issue. If it does not I will root and reinstall xposed and others
UPDATE: Even no root no xposed system did not help. Flashing back my TWRP backup.

Wipe phone flash stock rom and test first .

I probably will, just not right now, it takes quite a long time to get phone into working order after a flash with no backup. Also if it helped I would have to wipe my gear too because of how pairing system works...

Related

[Q] Seems like I've got corruption of some kind...

ATT Galaxy S4 currently running Goldeneye 6.0 and TWRP 2.6.0.0 (never installed MF3 base, but have tried both MF3 and MDL modems)
First odd thing...
[About->Status->Device Status] is listed as "Sd card" instead of the more common "Official" or "Custom".
Anybody know what that means or is telling me?
This is the latest thing I've noticed with my phone, which has been having all sorts of issues lately that I cannot seem to figure out. My main problem is, I can reinstall a new ROM, boot into the ROM, change settings around, reboot just fine, but, as soon as I install anything from the Play Store, the next reboot will hang on the initial Samsung splash screen. Wiping is the only fix I've found, and fixing permissions in TWRP errors out with an error that it cannot chown one of the new/updated .apk files.
Both Goldeneye 5 and 6 are doing this now (5.0 was installed and rock solid for several weeks before this all showed up...it started sometime after I decided to try out a couple of the aroma roms and then came back to GE).
Used ODIN to go back to factory rom, re-rooted/installed TWRP, then reinstalled GE6.0, but the same thing happened. Everything looked good until I ran updates from the store, then I was stuck again (note: used Root Explorer to check to permissions on the updated apks before rebooting and they were all correct (755)).
Other things I've noticed are:
1. Sometimes, on any reboot, the startup locks at the initial Samsung screen and I have to long press the power button to get it to reboot. It usually boots the second time around (this is before I install any additional apps and am completely unable to reboot).
2. Sometimes when wiping cache, davlik, and/or data, TWRP will seem to hang for up to a minute when trying to initialize the partition. A couple of times it even hard reboot my phone when I did a cache+davlik wipe.
3. I rolled back to a recovery image just fine; however, it was a couple months old. Everything started off looking great, but once I updated to a new ROM, my issues returned.
Trying Heimdall to go back to factory; however, I'm having issue with my laptop and getting the Zadig drivers installed. While I'm working that out, figured I'd see if anyone else has any suggestions on what else I should be trying or looking out.
thx
I would flash your phone back to MDL stock with odin using the mdl tar. This should format your paritions correctly. You could also reinstall MDL using kies since they still don't support MF3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Easy Lollipop 5.1 downgrade to KitKat 4.4.2 with TWRP - maybe

If you want to read the below learning experience you may gain some knowledge but at this point I believe my method may have flaws. While it seemed fine at first the problem listed directly below could not be fixed without using Odin to flash a stock ROM back onto the phone. It had checked the hidden menu settings for MTP and ADB and PDA, CP etc and all were correct (I have another good working S5 to compare these values to). I tried an earlier restore of a TWRP backup and that just blew up with all sorts of FC's on boot. So thank goodness for Odin. After flashing the stock rom it booted fine and I can now write files from the PC to the phone again via USB. In the process right now of re-rooting, installing TWRP and doing a restore of my last backup.
Note : I have found one problem I am currently working on after using this method. I can hook up the phone to the PC and get a link, open folders on the phone and can copy file from the phone to the PC but can NOT copy files from the PC to the phone. More later .....
I've got a Samsung Galaxy S5 from US Cellular. Other than a few people in the Motorola subforum here trying this I haven't seen this exact method described here so apologies if I missed it somewhere - tried many searches. It seemed so easy - maybe it is just considered SOP for some - don't know so I'm going to run the details by here anyway in case it saves anyone some trouble. Do read my warnings below though before you attempt this.
1 - You want TWRP installed (or Philz CM Touch will probably work too - seems a bit more complex though) If you are flashing ROM's having TWRP or some other custom recovery is always a good idea and I'm sure most people have one of them.
2 - Always do a complete backup with TWRP before flashing anything new. You did a backup before going to Lollipop didn't you?
3 - So you are tired of the white screen, battery sucking, quirky Lollipop or maybe that Cyanogen Lollipop mod didn't quite work for you and you want the old Kitkat back. So fire up TWRP, go into Advanced wipe and wipe Dalvik Cache, System, Data and Cache. You aren't done wiping yet though. After you swiped to wipe those go back to the previous page and Swipe to Factory Reset. That may not actually make any difference but I just did it for good measure and my method worked great.
4 - Now without out even needing to reboot find your latest backup of Kitkat 4.4.2 that you have on your Internal SD or External SD card (you do keep one there don't you in case your phone glitches on you while you are out and about?)
5 - Do a Restore of everything - Boot, Recovery, System, Data, Cache.
6 - Reboot. You are done.
Firstly I need to add that I had flashed Cyanogen Mod 12.1 (Lollipop 5.1) after following directions here in the main Cyanogen subforum to flash that on my KitKat 4.4.2 Galaxy S5 phone. What may be noteworthy is that after flashing CM 12.1 I ran the App PhoneInfo Plus (made mostly for Samsungs) and the OS version showed as Lollipop 5.1 but some of the build numbers to my recollection showed 4.4.2. So this was not a stock Lollipop OTA - it was the Cyanogen mod of Lollipop made by developers here. I just assumed they started with Lollipop to make that latest 5.1 build but I haven't followed the Cyanogen mod much at all so I don't know if they have borrowed bits and pieces of Kitkat in their builds. If they have done that then this downgrade method may not work the same for an OTA Lollipop.
Another warning - I noticed in the Motorola subforum here that some people bricked their phone trying this type of downgrade with TWRP however I believe that is because they had Verizon phones with locked bootloaders and that is not the case for my phone (US Cellular) or any other phones beside VZ as far as I know. If you have a Verizon with locked bootloader beware! I will also add that on my first boot after restoring Kitkat 4.4.2 that the second the home screen was up I started quickly scanning through my app pages and the phone rebooted itself. I believe it wasn't fully done loading the OS and it just was a hiccup. It has not happened since after trying all sort of things. Everything is working great.
I saw most people recommending to use Odin to flash a stock Kitkat firmware back on the phone in order to downgrade from Lollipop. Then you need to re-install all your apps or maybe do a restore of a recovery but with this method using TWRP you bypass most of that and get it all done in one TWRP session.
Another note about what I read people having a problem with upon downgrading - some were losing their IMEI when using Odin to flash the original firmware. I still have my original IMEI with no problem. That is another reason I think this method may be better than using Odin for this downgrade. I'll add that there are a lot of people around here with a whole lot more knowledge about flashing and custom ROM's than me so don't take my ideas as hard fact without doing your own research for your particular phone and particular situation.
I can copy FROM the internal and external SD card to PC but not PC to either internal or external SD card and the permissions seem to be correct for the folders I'm trying to copy into. Anyone have any ideas on that? However I was able to use AirDroid (Wifi) to copy files to the phone from the PC - no real surprise there but it reaffirms that I can write to those folders - just not with the USB cable.
More info. I just decided to run the App KitKat external SD Card patch. It failed. I believe I ran that before flashing Lollipop and it worked but now it fails. ?? I don't know if it is related to this problem since both internal and external SD are having a problem - but only via USB.
I tried another Galaxy S5 with same computer and cable and that one works fine to copy to the SD cards so that eliminates the cable or computer. AirDroid - Wifi works but only a problem one way with USB - WTF?
droidzer1 said:
I tried another Galaxy S5 with same computer and cable and that one works fine to copy to the SD cards so that eliminates the cable or computer. AirDroid - Wifi works but only a problem one way with USB - WTF?
Click to expand...
Click to collapse
Well thanks to TWRP AND Odin all is well once again in Androidland

[Q] Safest way to load 5.0 on my rooted Note 4?

Hi guys,
Have just spent the last couple of hours trying to research this but still not quite sure what's the best (safest!!) way of upgrading to lollipop on my SM-910G. I am rooted and currently on 4.4.4 and when I try to do an OTA update, I get the msg "The operating system has been modified in an unauthorised way.... etc etc"
When I connect via Kies, I get a pop up msg telling me that lollipop is available however when I try to update it tells me that I have to be unrooted. I read an article where some guy messed up his rooted S4 while trying to update via Kies. Can't afford for that to happen on my phone, I've backed up all my apps and data via Titanium Backup but now need to know what the safest way is to upgrade and keep all my settings etc.
I've downloaded the right 5.0 ROM (N910GDTU1BOC5_N910GXSA1BOC5_XSA.zip) for my model - am I correct to say that if I flash via Odin, I will lose all my apps and settings (and root)?
If I want to update and keep all my settings, am I safe to unroot via SuperSU, then update via Kies? I've read about how unrooting via SuperSU isn't really a complete unroot?
At the end of the day unless I'm 100% certain I will probably stay on 4.4.4 since there has been some horror stories with battery drain and stuff on 5.0
Has anyone been in a similar situation?
highon2str said:
Hi guys,
Have just spent the last couple of hours trying to research this but still not quite sure what's the best (safest!!) way of upgrading to lollipop on my SM-910G. I am rooted and currently on 4.4.4 and when I try to do an OTA update, I get the msg "The operating system has been modified in an unauthorised way.... etc etc"
When I connect via Kies, I get a pop up msg telling me that lollipop is available however when I try to update it tells me that I have to be unrooted. I read an article where some guy messed up his rooted S4 while trying to update via Kies. Can't afford for that to happen on my phone, I've backed up all my apps and data via Titanium Backup but now need to know what the safest way is to upgrade and keep all my settings etc.
I've downloaded the right 5.0 ROM (N910GDTU1BOC5_N910GXSA1BOC5_XSA.zip) for my model - am I correct to say that if I flash via Odin, I will lose all my apps and settings (and root)?
If I want to update and keep all my settings, am I safe to unroot via SuperSU, then update via Kies? I've read about how unrooting via SuperSU isn't really a complete unroot?
At the end of the day unless I'm 100% certain I will probably stay on 4.4.4 since there has been some horror stories with battery drain and stuff on 5.0
Click to expand...
Click to collapse
highon2str said:
Hi guys,
Have just spent the last couple of hours trying to research this but still not quite sure what's the best (safest!!) way of upgrading to lollipop on my SM-910G. I am rooted and currently on 4.4.4 and when I try to do an OTA update, I get the msg "The operating system has been modified in an unauthorised way.... etc etc"
When I connect via Kies, I get a pop up msg telling me that lollipop is available however when I try to update it tells me that I have to be unrooted. I read an article where some guy messed up his rooted S4 while trying to update via Kies. Can't afford for that to happen on my phone, I've backed up all my apps and data via Titanium Backup but now need to know what the safest way is to upgrade and keep all my settings etc.
I've downloaded the right 5.0 ROM (N910GDTU1BOC5_N910GXSA1BOC5_XSA.zip) for my model - am I correct to say that if I flash via Odin, I will lose all my apps and settings (and root)?
If I want to update and keep all my settings, am I safe to unroot via SuperSU, then update via Kies? I've read about how unrooting via SuperSU isn't really a complete unroot?
At the end of the day unless I'm 100% certain I will probably stay on 4.4.4 since there has been some horror stories with battery drain and stuff on 5.0
Click to expand...
Click to collapse
hi
Just a few points ...First if you " dirty flash" official stock Rom with Odin, then you will lose root ( so to me there is no need to unroot first ) However you do not loose any 3 rd party apps or settings . Also i never use Kies as my personal experience is that it is a waist of time .Regarding Lollipop well i have flashed several newer " version"/changelog/dated of Lollipop 5.0.1 over the past months and all of them have been good to me...( ..overall.) No real battery drain ,no lag ( only recent button and one " Samsung bug in the setting " Accessibilty" .
All my "problems " on Lollipop, on and off, was caused by 3 rd party apps
eg.Past few days i had suddenly random reboots over and over .i reflashed Lollipol ,i factory reset ,but the random reboots continued .
i then started to install all my +_ 162 ..?? apps one by one and checked
Eventually found my culprit ..'Greenify " (the experimental paid ,bolt on package, which is meant mostly for Xposed module with few functions you can also use without Xposed eg "don't remove Notifications " and Greenify system apps l)
After using Greenify for months with no issues it suddenly started giving problems .
So i could have given Lollipop the blame for my woes but i did not .
Yes I do believe Lollipop has issues ,but overall i cannot complain .
yes ,Titanuim is the way to go .
Also i "unrooted " via SuperUser app once, no problem at all, but then why do this if you just flash over it and root is gone
Bottom line ,
you can be "stuck " on Android v4.4.4 hoping and waiting .......?
or faceup to Lollipop ?
its your choice ?
good luck
Hey willcor thanks for the reply! Good to hear your experiences with this. Interestingly I've had a similar problem of sluggishness, lag and random rebooting (multiple times a day) on my Note 4 running kitkat. This went on for about 2 or 3 days. Tried installing some recently installed apps thinking it might have caused it, and now it seems it's fixed itself, I think??
Even pulling the battery and restarting often took ages to boot. Took my 128GB SD card out and tried to boot thinking maybe it was the card but it still lagged and restarted by itself. Like I said it seems ok now and has been ok for the last few days, but now that you mention Greenify, I have that installed too along with a few exposed modules. This rebooting problem is what motivated me to think about upgrading to lollipop to see if it would fix it.
Going by what you said, if I am not going to lose apps, data and settings, then I might flash to lollipop, then re-root. Sounds like the way to go. Maybe...
willcor said:
hi
Just a few points ...First if you " dirty flash" official stock Rom with Odin, then you will lose root ( so to me there is no need to unroot first ) However you do not loose any 3 rd party apps or settings . Also i never use Kies as my personal experience is that it is a waist of time .Regarding Lollipop well i have flashed several newer " version"/changelog/dated of Lollipop 5.0.1 over the past months and all of them have been good to me...( ..overall.) No real battery drain ,no lag ( only recent button and one " Samsung bug in the setting " Accessibilty" .
All my "problems " on Lollipop, on and off, was caused by 3 rd party apps
eg.Past few days i had suddenly random reboots over and over .i reflashed Lollipol ,i factory reset ,but the random reboots continued .
i then started to install all my +_ 162 ..?? apps one by one and checked
Eventually found my culprit ..'Greenify " (the experimental paid ,bolt on package, which is meant mostly for Xposed module with few functions you can also use without Xposed eg "don't remove Notifications " and Greenify system apps l)
After using Greenify for months with no issues it suddenly started giving problems .
So i could have given Lollipop the blame for my woes but i did not .
Yes I do believe Lollipop has issues ,but overall i cannot complain .
yes ,Titanuim is the way to go .
Also i "unrooted " via SuperUser app once, no problem at all, but then why do this if you just flash over it and root is gone
Bottom line ,
you can be "stuck " on Android v4.4.4 hoping and waiting .......?
or faceup to Lollipop ?
its your choice ?
good luck
Click to expand...
Click to collapse
highon2str said:
Hey willcor thanks for the reply! Good to hear your experiences with this. Interestingly I've had a similar problem of sluggishness, lag and random rebooting (multiple times a day) on my Note 4 running kitkat. This went on for about 2 or 3 days. Tried installing some recently installed apps thinking it might have caused it, and now it seems it's fixed itself, I think??
Even pulling the battery and restarting often took ages to boot. Took my 128GB SD card out and tried to boot thinking maybe it was the card but it still lagged and restarted by itself. Like I said it seems ok now and has been ok for the last few days, but now that you mention Greenify, I have that installed too along with a few exposed modules. This rebooting problem is what motivated me to think about upgrading to lollipop to see if it would fix it.
Going by what you said, if I am not going to lose apps, data and settings, then I might flash to lollipop, then re-root. Sounds like the way to go. Maybe...
Click to expand...
Click to collapse
hi,
Just a quick remark. When i was on Android v4.4.4, most of my issues eg. Private mode S HEALTH... (yes i know there was quick fixes /patches , that you could apply) Play store not installing apps, lags from time to time etc was caused by Xposed Framework. As far as i can remember Xposed was never optimise for Android v4.4.4? As "good" as Xposed was, it gave me "terrible headache /problems" on my Note 4....... even after uninstalling Xposed it broke some apps functionality! (This is a fact for me) . but yet, on all my other devices, no issues ! As stated in my previous post, that Lollipop experience, has been over all, very good for me.,(I have accepted the few bugs, that comes with every software update be it Android v4.4.4 or Android v 5.0.1.)
Lollipop also enabled me to use other apps /features eg Network Toggle app (change network only to LTE or LTE/3G or 3G only.. root required)
Bottom line
for me is.... yes, Lollipop has issues, but most of mine was caused by 3rd party apps not optimised 100% , work smoothly on Lollipop.
good luck
..............................
post note....
Titanium, i forgot, you might have some minor issues at first. Titanium could not find backup folder on my ext sd same as on Android v4.4.4) , so i used NextApp Sdfix (Play store, free app) Titanium, then was able to locate back ups. Again yesterday, i factory reset my device because of a Nova launcher, toggle notification issue and because i also wanted to for a period of time.
Titanium could not write and above NextApp Sdfix said i had no write premisson after running NextApp. i formatted my ext sd on laptop and NextApp did its work and Titanium working 100%
Just thought to make you aware if issue arrived.
Thanks... I forget all these root features have to be redone. I've also given extsd access on kitkat after rooting. Will have to do it all over again I guess!
Ok just a quick update. Flashed to 5.0.1 with Odin and rooted with CFautoroot. Everything seems to be ok apart from after rooting and rebooting, I got a "could not do normal boot" msg, saying that the phone was in download mode and not to disconnect the target. I pulled the batt and booted up normally ok. Checked in Titanium and found root access ok, activated write to SD and all seems normal.
Things seem a bit sluggish with lollipop, so I uninstalled xposed (which now won't work on this version), greenify and some other apps, and booted into recovery to wipe cache partition. When it was done wiping the cache and said to reboot, I got the same "could not do normal boot" msg. Once again I pulled the battery and it booted ok.
Not sure what has happened or if anything is affected - should I re-flash 5.0 with Odin and re-root all over again?
highon2str said:
Ok just a quick update. Flashed to 5.0.1 with Odin and rooted with CFautoroot. Everything seems to be ok apart from after rooting and rebooting, I got a "could not do normal boot" msg, saying that the phone was in download mode and not to disconnect the target. I pulled the batt and booted up normally ok. Checked in Titanium and found root access ok, activated write to SD and all seems normal.
Things seem a bit sluggish with lollipop, so I uninstalled xposed (which now won't work on this version), greenify and some other apps, and booted into recovery to wipe cache partition. When it was done wiping the cache and said to reboot, I got the same "could not do normal boot" msg. Once again I pulled the battery and it booted ok.
Not sure what has happened or if anything is affected - should I re-flash 5.0 with Odin and re-root all over again?[/QUOTE
hi,
i am sure i read somewhere about.re: your remark, when you rooted and got a msg, with
"could not do a normal reboot... I am sure it could be ( @ Chainfire,) Cf autoroot website not sure.?
I would have search for a answer /reason!/ explanation Then i would afterwards, reflash Rom. (depends on you)
Just a quick question.... At what stage did you uninstall Xposed....? before /after flashing etc. i stated before that i found Xposed "broke /caused issues after i uninstalling it. (facts about two or three times it happened , in past )
Also i had no problem in using Greenify again (i have re installed it) its just the donation /paid / experimental package i am a bit hesitant with.
good luck
Click to expand...
Click to collapse
Hey guys, I have since reflashed and rerooted and now seem to have less problems, although the phone is still sluggish, randomly locking up and restarting , and sometimes restarting to the green android "could not do normal boot" screen.
Question now is, can I boot into stock recovery to do a factory reset? I've done some research but the views seem conflicting. Is this recommended, will I be stuck in a bootloop and will I still be rooted after the reset?
I never did a factory reset when flashing from 4.4 to 5.0.1 so I'm hoping this will fix the issues I've got now.
Sent from my SM-N910G using Tapatalk
Anyone?
Sent from my SM-N910G using Tapatalk

[Q] sgh 1337 UN stuck on Samsung splash screen (safe strap broken)

So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Ghujii said:
So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Click to expand...
Click to collapse
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Ghujii said:
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Click to expand...
Click to collapse
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
I will attempt to do this, since nothing since has work. I am about to get a new logic board for the system in the next 2 weeks. Towel root DOES typically work on this system, however the last time I attmpted it it failed to work outright. Im not sure what has changed with the device, but i believe reflashing stock is the best method. The phone now, will boot up, then skip the lock screen and go straight to the home screen, which is black with no pull down bar, or with no signal and there is no way to rectify it. Even if there were, it boots back down and launches back up and becomes locked at the ATT logo.
After a fair bit of messing with it, and recovery mode it will sometimes boot normally where it tells me that processes has failed and askes me to cancel the ''app''. This is the best option to update the phone and attempt root, but getting it here is so difficult because it reboots itself and the mode is rare to acquire. This problem either is due to the kernel, or the rom i believe. I also am to believe the powercell may have some issue, as i replaced the battery a few weeks back and it worked fine for about 1 week.
Booting into safemode doesnt work either as it skips over the lock screen straight to the home screen. Outsidce of replacing the logic board, or attempting another flash im at the end of the short rope i was already on in terms of options.
sway8966 said:
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
Click to expand...
Click to collapse
UPDATE: I found therein two methods to flashback to stock. I did so, then proceeded to attempt to flash from nb1 to nj4. Progress stopped there when it flung an error 7 at me. So this means either something in my phone is corrupted or the file i downloaded from the above mentioned forum is corrupted. I also attempted flashfire, but seen as it STILL crashes at random due to process errors thats almost impossible to attempt.

Galaxy s7 overheating ( xposed involved ? )

Hi,
I recepty run into a problem that I can not fix by myself.
My galaxy s7 started to overheat (it overheats during normal usage, browsing Web etc.)
1. I was using the phone rooted with CF autoroot without a problem for a month or so
2. I installed TRWP and then Xposed framework (all the correct files following guides from this forum) and it worked all OK.
3. 2 days after the above installation I decided to make a fresh clean install of ROM. I found a new updated ROM (June update) of the stock XEO ROM that I was using.
I made a data reset and factory reset with TRWP (wiping all) and then flashed the new ROM with Odin.
I rooted it and installed xposed.
4. Phone started to overheat during normal usage.
5. I tried to flash the new ROM without installing xposed, then trying flashing ROM without even rooting it later. I finally even flashed the "old" ROM from before the June update, with no rooting or touching anything, and it still overheats.
The clues I found as far:
1) i read somewhere that xposed can cause overheat like I described but I don't understand how it could be after I wiped de device so many times and running stock unmodified rom?
2) i read somewhere that there is some Google account backup bug that makes devices overheat which seems to be connected with the 3rd point
3) it seems that Android System battery usage is higher than normal
4) the device overheat mostly on the right middle part of the phone, along the right edge of the phone a little below the power button.
5) i don't belive it's user app related because the problem exist even after fresh install of rom without additional apps installed
I would really need some advice, because I ran out of ideas what to do.
Hello, our situation is similar... I've googled the issue and I've found no solution. My overheating problems started after I installed Xposed framework. Few minutes before, I rooted my phone with Odin and installed TWRP. After I used a module on Xposed, my phone began overheating on the right part of my phone below the power button as you described. I immediately uninstalled Xposed.... nothing worked, flashed my phone back to the stock rom....still the same. IF EVER FIND A SOLUTION, PLEASE SHARE IT WITH ME... I'M SO WORRIED. THANKS.
Possibly a long shot, but I would be opening the occulus app and seeing if it needs to update.
That issue was causing a bunch of phones to overheat last week. Solved by opening the app and letting it update.
Sent from my SM-G935F using XDA-Developers mobile app

Categories

Resources