Update is out for SGH-i337 12/09/2015 - AT&T Samsung Galaxy S 4 General

ATT says it is Security Enhancements. Have not seen it on my S4 as yet. http://www.att.com/esupport/article.html#!/wireless/KB419415

It's downloading on mine now. Hope it doesn't affect root.
---------- Post added at 08:08 PM ---------- Previous post was at 07:44 PM ----------
It failed due to root I'm sure. Guess I'll have to disable until someone figures out how to apply it with root.

Back key doesn't work after the update.

arobles said:
Back key doesn't work after the update.
Click to expand...
Click to collapse
Seems fine on mine...opened google Store apk went in to my apps then backed out all the way to home screen with the back key.

Wife's phone got the update this morning, looks like it is just the November security update.
-Chris

I did the update and now the menu and back button doesn't work. I tried factory reset with no result. What can I do?

arobles said:
I did the update and now the menu and back button doesn't work. I tried factory reset with no result. What can I do?
Click to expand...
Click to collapse
Same here. Soft keys became unresponsive. Was your screen replaced by any chance. There seems to be a link to this.

Animalistic503 said:
Same here. Soft keys became unresponsive. Was your screen replaced by any chance. There seems to be a link to this.
Click to expand...
Click to collapse
My screen has never been replaced and it wasn't rooted before the update.

Related

Root 1.85 help

I'm trying to root 1.85 on my mac because I just got a replacement phone but whenever it asks me to do a software update check, it tells me that there actually is a software update available. Is it still possible to root?
slaughtercolors said:
I'm trying to root 1.85 on my mac because I just got a replacement phone but whenever it asks me to do a software update check, it tells me that there actually is a software update available. Is it still possible to root?
Click to expand...
Click to collapse
I'm getting the same problem, I've tried numerous times, wifi on off, mobile data off on, nothing seems to be working.
ChefAnt said:
I'm getting the same problem, I've tried numerous times, wifi on off, mobile data off on, nothing seems to be working.
Click to expand...
Click to collapse
Use this link - http://forum.xda-developers.com/showthread.php?t=1671237
Should be able to successfully root because I just rooted my HTC One X (replacement)
Already there is post with similar query - Please use "search"
---------- Post added at 05:03 AM ---------- Previous post was at 04:45 AM ----------
ChefAnt said:
I'm getting the same problem, I've tried numerous times, wifi on off, mobile data off on, nothing seems to be working.
Click to expand...
Click to collapse
Did you try pushing your clock forward two days,

Return device to "Official" status after MF3

So this morning I was playing with menus I saw in other threads. After playing around, my device rebooted. I am no longer listed as custom in the device status menu, nor upon boot. The steps are below and hopefully someone can recreate what happened. I'm sure this would be useful for people who need warranty repair.
Dial *#9090#
Press menu, then key input.
Enter 1, press ok.
At this point my device rebooted, and bam custom status was gone. I'm not sure if it matters, but I was rooted with the new method for MF3 prior to me doing this in the service menu, and root was retained.
mcdevitt1985 said:
So this morning I was playing with menus I saw in other threads. After playing around, my device rebooted. I am no longer listed as custom in the device status menu, nor upon boot. The steps are below and hopefully someone can recreate what happened. I'm sure this would be useful for people who need warranty repair.
Dial *#9090#
Press menu, then key input.
Enter 1, press ok.
At this point my device rebooted, and bam custom status was gone. I'm not sure if it matters, but I was rooted with the new method for MF3 prior to me doing this in the service menu, and root was retained.
Click to expand...
Click to collapse
This worked for me as well!
This didn't work for me. I got the reboot but am now custom on both the lock screen and the device status. I previously had the custom on boot gone.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Soccer are you rooted? Not sure if it matters, just curious.
Sent from my SAMSUNG-SGH-I337 using xda premium
Yes I was rooted. And in fact, I just found out that it broke my root. I am no longer rooted.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Soccer1725 said:
Yes I was rooted. And in fact, I just found out that it broke my root. I am no longer rooted.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
That's odd indeed, I just double checked I am still 100% rooted.
I guess a bit more info to try and figure things out is needed.
When I updated to MF3 I had CWR on my device and it was rooted. Obviously MF3 took all of that away. Since then I was stuck with the Samsung Custom logo and the custom status within settings. A few days ago I performed the new root method. This morning I did the dialer and reboot and I kept my root and the custom status went away completely including the logo.
mcdevitt1985 said:
That's odd indeed, I just double checked I am still 100% rooted.
I guess a bit more info to try and figure things out is needed.
When I updated to MF3 I had CWR on my device and it was rooted. Obviously MF3 took all of that away. Since then I was stuck with the Samsung Custom logo and the custom status within settings. A few days ago I performed the new root method. This morning I did the dialer and reboot and I kept my root and the custom status went away completely including the logo.
Click to expand...
Click to collapse
Before MF3 I was rooted but couldn't stop the update. After the MF3 update I rooted with the new method. At that point I was rooted and the custom startup screen was gone but the device status was still custom. I tried your method and it broke root but I was back to secure and normal startup. I then re-rooted and tried your method. This time I retained root but I still have the custom startup and device status.
---------- Post added at 02:23 PM ---------- Previous post was at 02:05 PM ----------
Also odd that after I did this my notifications bar at the top of the homescreen no longer has a black background. It's just text on top of the wallpaper. Wonder what it changed.
Soccer1725 said:
---------- Post added at 02:23 PM ---------- Previous post was at 02:05 PM ----------
[/COLOR]Also odd that after I did this my notifications bar at the top of the homescreen no longer has a black background. It's just text on top of the wallpaper. Wonder what it changed.
Click to expand...
Click to collapse
Thats really odd. I haven't had any issues. We need more people to try it. Perhaps you just need to do a factory reset and then try it. Who knows, it's worked for myself and one other person so far, just need more people to try it.
I was just going to try a factory reset. I'll let you know.
For you guys on mf3, please be careful experimenting with your phones. If you Bork it there is no easy way to recover it. No odin back to stock! No nandroids! You may be waiting for ever for an odin flashable rom.
Did a factory reset but the notification bar at the top is still just text on top of the wallpaper. Any idea if this is just another setting I changed and didnt' know it?
---------- Post added at 03:16 PM ---------- Previous post was at 03:11 PM ----------
jd1639 said:
For you guys on mf3, please be careful experimenting with your phones. If you Bork it there is no easy way to recover it. No odin back to stock! No nandroids! You may be waiting for ever for an odin flashable rom.
Click to expand...
Click to collapse
Any idea if I could get it recovered at an AT&T store or something if that were to ever happen?
Soccer1725 said:
Did a factory reset but the notification bar at the top is still just text on top of the wallpaper. Any idea if this is just another setting I changed and didnt' know it?
---------- Post added at 03:16 PM ---------- Previous post was at 03:11 PM ----------
Any idea if I could get it recovered at an AT&T store or something if that were to ever happen?
Click to expand...
Click to collapse
I'm guessing you'd have a hard time. That's part of the reason they've locked it down so tight.
They are not going to fix it at the store. That is exactly the type of problems they are trying to avoid by locking the device down...
Sent from my SAMSUNG-SGH-I537 using Tapatalk 2
I performed this and my phone rebooted, but still says custom. but im not really sure what MF3 means lol
f4s7d3r3k said:
I performed this and my phone rebooted, but still says custom. but im not really sure what MF3 means lol
Click to expand...
Click to collapse
Don't be messing with your phone then.
Good news is after I did a factory reset I am now back to Secure and no custom boot screen even though I am still rooted.
The "custom" on booting takes an additional reboot to go away...if the conditions are right. In other words, it's a good bet the "custom" would have gone away even if you didn't mess with the service menu because it takes two reboots to make it go away.
There a lot of information about this throughout the forums already. Do yourselves a favor and search for "sysscope".
scott14719 said:
The "custom" on booting takes an additional reboot to go away...if the conditions are right. In other words, it's a good bet the "custom" would have gone away even if you didn't mess with the service menu because it takes two reboots to make it go away.
There a lot of information about this throughout the forums already. Do yourselves a favor and search for "sysscope".
Click to expand...
Click to collapse
I rebooted it 3 times before I did anything else. I tried everything that has been mentioned in other places (except sysscope) and they didn't work. Factory reset did work though for some reason.
Soccer1725 said:
Before MF3 I was rooted but couldn't stop the update. After the MF3 update I rooted with the new method. At that point I was rooted and the custom startup screen was gone but the device status was still custom. I tried your method and it broke root but I was back to secure and normal startup. I then re-rooted and tried your method. This time I retained root but I still have the custom startup and device status.
---------- Post added at 02:23 PM ---------- Previous post was at 02:05 PM ----------
Also odd that after I did this my notifications bar at the top of the homescreen no longer has a black background. It's just text on top of the wallpaper. Wonder what it changed.
Click to expand...
Click to collapse
This part confuses me. My notifications bar has never had a black background, its always been transparent over the wallpaper until i swipe down. Are you sure it used to be black?
cloudraker said:
This part confuses me. My notifications bar has never had a black background, its always been transparent over the wallpaper until i swipe down. Are you sure it used to be black?
Click to expand...
Click to collapse
No I'm not sure. Just thought I remembered having it. Please ignore if normal.

[Q] Screen Blacks out/unresponsive during calls

Blisspop 1.5
The off screen buttons are lit up but the screen is black and unresponsive.
I can hear ..they can hear me. But i can't hang up.
Any ideas?
ciriloistic said:
Blisspop 1.5
The off screen buttons are lit up but the screen is black and unresponsive.
I can hear ..they can hear me. But i can't hang up.
Any ideas?
Click to expand...
Click to collapse
I'm looking as well it just started today on mine. Grrrrrr
OPOfreak said:
I'm looking as well it just started today on mine. Grrrrrr
Click to expand...
Click to collapse
mine was fixed with update to the BlissPop-v1.5-bacon-Nightly-20150103-Rev1.zip update.
Mine started after trying the official 5.0 update from OPO I had to completely revert back to stock 44s unlock bootloader again and reroot
OPOfreak said:
Mine started after trying the official 5.0 update from OPO I had to completely revert back to stock 44s unlock bootloader again and reroot
Click to expand...
Click to collapse
same thing happend with me today...
siddheshvartak said:
same thing happend with me today...
Click to expand...
Click to collapse
When I used a toolkit and went back completely to stock it fixed it my device rocks again
I'm running 44s variant and I'm getting my screen off during calls. Started sometime today or last night.
Anyone know why it's happening?
---------- Post added at 07:45 PM ---------- Previous post was at 07:06 PM ----------
Okay, I did a factory reset and restored my initial nandroid backup. I re-rooted and I am still getting the screen blackout when calls come in.
Ideas?!?!?!?!?!?!?
So frustrated at this point. I'm traveling and do not have computer access for adb.
OPOfreak said:
When I used a toolkit and went back completely to stock it fixed it my device rocks again
Click to expand...
Click to collapse
which toolkit you are using...
can you give me the link....
siddheshvartak said:
which toolkit you are using...
can you give me the link....
Click to expand...
Click to collapse
Here
http://forum.xda-developers.com/showthread.php?t=2808987

Honor 8 bricked after failed unroot attempt. Please help!

Hey everyone. I rooted my Honor 8 yesterday using the following guide: https://www.xda-developers.com/honor-8-root-twrp-and-xposed/. Everything seemed to work fine at first, but soon my Bluetooth refused to turn on at random and apps constantly crashed (either on startup or when switching between them). It got annoying very quickly and after searching for hours and not finding any real solution, I decided root wasn't that important to me and I'd just unroot my phone and then hard reset. After using SuperSU's unroot function, my phone turned off and rebooted. But when it got to the blue screen with the honor logo, it froze. Nothing does anything. No matter which buttons I press/hold down. It's just stuck on that screen. I'd love to take out the battery, but with these new phones, it's sadly built in (who ever thought that was a good idea?). It's been this way for close to an hour. ADB doesn't recognize it anymore. The only way my PC seems to recognize it at this point is through the Device Manager, where it shows the yellow warning sign. Under Properties > General it reads "This device cannot start. (Code 10)". I've tried a few different things but none of them have worked. So this is where I'm at now. I'd hate to lose this phone since I just got it three months ago. I would really appreciate any sort of help, because I'm grasping at straws.
Rommco05 said:
Have you still access to twrp? When u trun on phone still is in bootloop. Which is your model and which was system last working?
Click to expand...
Click to collapse
Sorry, I might not have made this clear, but I can't even turn my phone off. It's literally stuck on the blue screen (how fitting). The model should be 51090QMF, but I don't know what you mean with the last part.
Rommco05 said:
51090QMF...??? Model must something like FRD-LxxCxxxBxxx
---------- Post added at 21:08 ---------- Previous post was at 21:08 ----------
Try reboot phone and hold vol +
Click to expand...
Click to collapse
My bad, I just looked it up on Amazon (where I bought it) and it said model number. This should be the real one: FRD-L09. The reboot worked, but it's still stuck on the honor logo. At least we know it's not hard-bricked now.
EDIT: I was able to get into eRecovery. Should I just press "Download latest version and reecovery"?
Rommco05 said:
Which system works last one? and for which region is your phone? Cxxx
Click to expand...
Click to collapse
I bought my phone from the German amazon site, so whichever one that is. I'm sorry, but I don't quite understand your system question. I used 7.0 if that's what you're referring to.
Rommco05 said:
Now understand so your model is FRD-L09?(32Gb ROM)/L19?(64Gb ROM)C432(EU)
So when phone rebooting u still se message your device is unlocked nad cat be trusted?
Click to expand...
Click to collapse
Yes, the 32GB one. And as I said, I was able to get into the Huawei eRecovery. I'm guessing I should just hit "Download latest version and recovery" at this point, but I was waiting just to be sure.
Rommco05 said:
You have still unlocked bootloader?
Try this:
1.create dload folder on inter. storage or sdcard
2.unzip zips which I here posted
3.put uziped separately to float
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v73856/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...3856/f1/full/hw/eu/update_data_full_hw_eu.zip
Click to expand...
Click to collapse
I do still have unlocked Bootloader, but at the moment I have no way to use it. My PC (ADB included) doesn't recognize the phone.
Rommco05 said:
What about two is still in your phone? Unplug phone from usb and reboot, + hold vol up but must be unluged after try dload method with sdcard
Click to expand...
Click to collapse
holding vol up just brings me to the eRecovery menu, where I can't do much. I'm not sure how much of twrp is still on my phone. Before I tried to unroot, all of it was.
EDIT: Sorry, never mind. I got into TWRP.
Rommco05 said:
Try dload method with zips which I posted
---------- Post added at 09:00 PM ---------- Previous post was at 08:56 PM ----------
Bootloader is still unlocked? If yes I tomorrow extract update app send you all parties which u nees to flash over fastboot if dload dont work for you
Click to expand...
Click to collapse
I'm currently downloading your files, my bootloader is unlocked. After I have the files unzipped, do I just flash them? If so, in what order?
Edit: Welp, he went offline. Can someone else tell me what to do with these files?
Rommco05 said:
How wrote before, unzip this files and separately put each unzipped to dload on sdcard, first bigger one
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
If are this files in dload folder turn phone or reboot + hold vol down together with vol up
Click to expand...
Click to collapse
Thank god, it booted. Thank you so much. What would be the best way to go about getting rid of root now? I'm willing to do a factory data reset at this point for everything to work again.
Rommco05 said:
Good job man for properly root go to developer section and twrp 3.1.1-1 by OpenKirin all steps is there
Click to expand...
Click to collapse
I'm just gonna go back to not having root after this, haha. It was just something I wanted to try, I don't need it that much. I did a factory reset and will now get my most important data back on my phone (thankfully I have a backup). Still, thank you so much for your help. I don't know what I would've done without you. I "Thanked" all your posts here, which is the least I can do.

March Update

March updates are published.
https://developers.google.com/android/images
Nice
Looks like there are a lot of fixes this month.
https://support.google.com/pixelphone/thread/32079343?hl=en
Feature drop too.
https://9to5google.com/2020/03/02/pixel-feature-drop-march/
Anyone having problems with Magisk crashing while trying to patch the boot image? It crashes every time I try. Changed to stable, rebooted, nothing works. Thoughts?
gettinwicked said:
Anyone having problems with Magisk crashing while trying to patch the boot image? It crashes every time I try. Changed to stable, rebooted, nothing works. Thoughts?
Click to expand...
Click to collapse
Yep. I had to switch to stable magisk and it patched the boot fine for me. Odd it didn't work for you.
wolfeyes30 said:
Yep. I had to switch to stable magisk and it patched the boot fine for me. Odd it didn't work for you.
Click to expand...
Click to collapse
I reinstalled Magisk and it worked fine. Weird.
It Is just me or they have increased the maximum brightness ? It's like they have unlocked the High Brightness Mode
Had Problem with magisk but had franco kernel installed. You have to deactivate the modules for that kernel then magisk works again. Hole that helps
gettinwicked said:
Anyone having problems with Magisk crashing while trying to patch the boot image? It crashes every time I try. Changed to stable, rebooted, nothing works. Thoughts?
Click to expand...
Click to collapse
me too
Starting in Feb my phone no longer gets updates.. I'm not sure if it's because of Magisk or not. I search for update and for about 2 seconds it says preparing update and then it says you are up to date.
Anyone else? Any fix?
dave5777 said:
March updates are published.
https://developers.google.com/android/images
Click to expand...
Click to collapse
:good:
---------- Post added at 02:34 AM ---------- Previous post was at 02:31 AM ----------
murphyjasonc said:
Looks like there are a lot of fixes this month.
https://support.google.com/pixelphone/thread/32079343?hl=en
Click to expand...
Click to collapse
:good:
---------- Post added at 02:38 AM ---------- Previous post was at 02:34 AM ----------
troymz1 said:
Starting in Feb my phone no longer gets updates.. I'm not sure if it's because of Magisk or not. I search for update and for about 2 seconds it says preparing update and then it says you are up to date.
Anyone else? Any fix?
Click to expand...
Click to collapse
Use This guide: Do #4 'keep data' then #9 to root. It only takes 5 minutes.
Note: Before you start disable all your Magisk modules.
Balulo_007 said:
It Is just me or they have increased the maximum brightness ? It's like they have unlocked the High Brightness Mode
Click to expand...
Click to collapse
They unlocked High. Brightness. That was one of the features in this quarters drop.
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
troymz1 said:
Starting in Feb my phone no longer gets updates.. I'm not sure if it's because of Magisk or not. I search for update and for about 2 seconds it says preparing update and then it says you are up to date.
Anyone else? Any fix?
Click to expand...
Click to collapse
Just fastboot the factory image without the -w. It might just be personal preference but I think that's the easiest way to update if you are rooted.
murphyjasonc said:
Just fastboot the factory image without the -w. It might just be personal preference but I think that's the easiest way to update if you are rooted.
Click to expand...
Click to collapse
I'm aware of how to update but I used to be able to take the ota and re root with Magisk.. but now I don't even get the ota.
troymz1 said:
I'm aware of how to update but I used to be able to take the ota and re root with Magisk.. but now I don't even get the ota.
Click to expand...
Click to collapse
I have automatic system updates disabled in developer options. It's probably unlikely since you were getting updates but could you have disabled by accident? Not sure what else would suddenly cause you to stop getting them. I doubt it's something that simple but I've beat my head against the wall for something similar in the past....lol
troymz1 said:
I'm aware of how to update but I used to be able to take the ota and re root with Magisk.. but now I don't even get the ota.
Click to expand...
Click to collapse
I'm right there with you. Very annoyed that it won't do it through normal OTA. I waited it out through February and never got it.
murphyjasonc said:
I have automatic system updates disabled in developer options. It's probably unlikely since you were getting updates but could you have disabled by accident? Not sure what else would suddenly cause you to stop getting them. I doubt it's something that simple but I've beat my head against the wall for something similar in the past....lol
Click to expand...
Click to collapse
Disabling that toggle in developer options is a prerequisite for doing the OTA update option and retaining magisk.
wgrant said:
I'm right there with you. Very annoyed that it won't do it through normal OTA. I waited it out through February and never got it.
Click to expand...
Click to collapse
Have you tried doing the Magisk uninstall then tried taking the ota?
troymz1 said:
Have you tried doing the Magisk uninstall then tried taking the ota?
Click to expand...
Click to collapse
No, that'll be what I do this month if it doesn't pop up like it should.
wgrant said:
No, that'll be what I do this month if it doesn't pop up like it should.
Click to expand...
Click to collapse
I wanna try it but don't have time to fix right now if it goes wrong
I agree with a lot of others here: It's easier to dirty flash, no hassles and it works every time without having to figure out any secret handshakes.

Categories

Resources