Related
Hi All,
Im on the Official ICS ROM INDIA...4.0.3 DDLP4
Yesterday, when i checked kies, there was an update waiting (No Update on OTA). The downloading of firmware was taking ages to download(3.2mbps connection) and after about 70 percent the downloading stopped and Kies said "Connection stopped"....
Any body who has downloaded the F/W can you please post the change log (If you find any).. I mainly wanna know, if the laggness of the lock screen and slowness to open contact's and capturing pics has been rectified.
Ramith123
Ah glad that i have company.sad at the same time!! Even i have the same problem after the 7mb OTA update. The andriod process closes often and hangs the phone.The phone was literally unusable. Hence i tried to install custom gingerbread rom on it. Now its almost completely bricked.How irresponsible is samsung to roll these things out without testing it thoroughly.
***PLEASE DON'T INSTALL THE 7MB ICS OTA UPDATE***
hopefully we can save some.
I also tried to update through OTA but it was failed and message popped up that do update through Kies. Now I got update through Kies and my firmware changed from DDLP4 to DDLPA. However I lost Root.
I also received the update notification. Downloaded the 7.8 mb update within a minute and asked for reboot. Everything worked fine and nothing special noticed. It just changed the build no. from IML74K.DDLPA to IML74K.DDLP8
dushy4 said:
I also received the update notification. Downloaded the 7.8 mb update within a minute and asked for reboot. Everything worked fine and nothing special noticed. It just changed the build no. from IML74K.DDLPA to IML74K.DDLP8
Click to expand...
Click to collapse
you mean LP8 to LPA? check your kernel version date. if it shows 12 June then fine, else your kernel has not been updated.
Hey guys basically its stability update. my phone feels much smoother now. i updated OTA via wifi, i also faced update not installed issue and i found out the problem, basically we all root our device that means we change SU binaries so when updating phone OTA it checks for those binaries and if these binaries are not official OTA update get aborted. i solved this problem like this,
1) I have downloaded STOCK LP8 firmware from samobile.com when it released
2) As my phone is rooted my SU binaries are changed so OTA update is aborted.
3) So FLASHED Stock rom LP8 from PC ODIN which kept my all DATA, APPS intact i just lost my root and some mods like 15toggles status bar and so..
4)then i started updating my phone using S/W update in settings, its 7.85MB file.
5)In few minutes my phone is updated to LPA
6)Now i again rooted my phone and my all data apps are intact and mob is much improved in stability.
Hope this will help you guys.
anjath said:
you mean LP8 to LPA? check your kernel version date. if it shows 12 June then fine, else your kernel has not been updated.
Click to expand...
Click to collapse
It still shows 12 may,,, But i read in some other thread that kernel was not updated in this update.
dushy4 said:
It still shows 12 may,,, But i read in some other thread that kernel was not updated in this update.
Click to expand...
Click to collapse
kernel is definitely updated in LPA. just flash LPA ROM file using Odin.
I also agree with what mullarameez has pointed out. rooting might be the reason for kernel being skipped. because if u flash LPA with odin you will lose root and hence get the new kernel.
Is there a way to update Kernel without flashing the whole 650 mb rom?
with all the issues in ICS, i think it would be safest if you would flash using the whole LPA ROM. I know its a pain to download but worth it in the end.
OMG! just a 7Mb update took 2hrs to download.. Hmmmm...
My main prob was with Lock screen, camera and contacts.. Noting has been resolved on this new Update!!!
what is the issue? is it lag?
This is confusing..
I have everything stock on my phone..All updates done OTA since i bought the phone..Not rooted..
Still the kernel says 12 May after the 7mb update..Why?? Although the deep sleep issue (sore point for me) seems to have been resolved after this update...
PS: The build info after *#1234# says 12 June, if that matters..
yes, almost all the users who updated OTA have the same issue. you may flash the new LPA using PC Odin from doc's post (anyways you're not rooted so no problem)
[Q&A] [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Pac
Q&A for [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Package]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Package]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hi everyone,
This ROM is great. every things are working well.
But I don't know how to change the "Right hard key's function. I don't want it show the "recent apps" when we press.
It should be a menu key when we using App.
Please support!
Thanks,
lamhcmute said:
Hi everyone,
This ROM is great. every things are working well.
But I don't know how to change the "Right hard key's function. I don't want it show the "recent apps" when we press.
It should be a menu key when we using App.
Please support!
Thanks,
Click to expand...
Click to collapse
In post# 1 under the downloads section, below version 03 you will find revert longpress to recents & menu. You can download and flash this zip through recovery and menu key will be as before.
no root after flashign WizCyan
After flashing WizCyan 4 with update 1 I don't have root access. I've tried reinstalling several times and I've also tried to install superSU on it's own using CWM, both the latest version and older versions, with no success. I've also tried to install just v4 but the problem persists. Does anybody have any clue on what could be wrong? I've had root on the phone using other ROMs. I use the latest CWM.
And yes, I chose no when promted to fix superuser in CWM. Although I have also tried to pres yes during one installation.
What version of cwm are you having? Also when you click on the supersu app what message do you get?
I used version 6.0.3.5. Today I installed 6.0.5 and redid the flashing of the update and also of superSU 2.16 by it self from CWM. No difference
When i press the superSU app I dont get any message really. Looking at the log it's as if though the app denies all apps access without asking. I tried changing the settings in superSU to allow all requests and then the phone passed the check with root checker and root apps also seem to work. No app is added to the SuperSu applist.
Gudiol said:
I used version 6.0.3.5. Today I installed 6.0.5 and redid the flashing of the update and also of superSU 2.16 by it self from CWM. No difference
When i press the superSU app I dont get any message really. Looking at the log it's as if though the app denies all apps access without asking. I tried changing the settings in superSU to allow all requests and then the phone passed the check with root checker and root apps also seem to work. No app is added to the SuperSu applist.
Click to expand...
Click to collapse
I would suggest that you do a clean install of the ROM, now that your recovery has been updated
Excessive consumption of battery
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
srDosaps said:
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
Click to expand...
Click to collapse
Will suggest to do a clean install and check and if not then report back. Anyone else facing this issue.. kindly report
srDosaps said:
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
Click to expand...
Click to collapse
Ok, did some testing and found that some of the init.d scripts were eating battery therefore have posted an update in the OP removing these and battery consumption should be better after flashing this update.
can i install
i have 4.4.2 NE5 but DBT not PHN,can i install this rom on my firmware and do i need install first version 4 and then flash version 4 update 02?and how much memory i have after flashing this rom is ih still around 12 gb or less?
s4active user said:
i have 4.4.2 NE5 but DBT not PHN,can i install this rom on my firmware and do i need install first version 4 and then flash version 4 update 02?and how much memory i have after flashing this rom is ih still around 12 gb or less?
Click to expand...
Click to collapse
Sure, you can install on any firmware, but if you have wifi issues then you may need to flash modem or some other workaround. Just wipe data/factory reset and install version 04 followed by update 02. I am not sure on what you mean by memory but presume that you are referring to internal sd card. This will depend on what apps/features you install from the addon package and playstore. The ROM will not affect your internal sdcard space as it will be installed on the reserved system space.
Problem with Rom Super Wizcyan - S5 Style
Hello, first sorry by my english, its sucks, but ill try to explain my problem, i install the rom wizcyan - s5 style in my I9295 (of course), and follow all the instruction, like de developer says, starts normaly, but for example, when i push the screen mirroring button, the phone freeze an restart, and occasionally shows a message like "android core process stoped". do all the wipes, and install the 6.0.5 rom manager, all the proces finish ok, install the update, and occurs the same problem, i like this rom its cool , faster and light, without all the samsung crap, someone can help me please, thanks in advance.
Kaitenx said:
Hello, first sorry by my english, its sucks, but ill try to explain my problem, i install the rom wizcyan - s5 style in my I9295 (of course), and follow all the instruction, like de developer says, starts normaly, but for example, when i push the screen mirroring button, the phone freeze an restart, and occasionally shows a message like "android core process stoped". do all the wipes, and install the 6.0.5 rom manager, all the proces finish ok, install the update, and occurs the same problem, i like this rom its cool , faster and light, without all the samsung crap, someone can help me please, thanks in advance.
Click to expand...
Click to collapse
In case you want to use screen mirroring then you would need to install allshare from the addon package
I've been tinkering with trying to get WizCyan totally working on my device for a couple of days, but I can't for the life of me get Wifi working (at first it was root access, but that was fixed by upgrading CWM). Here is the exact process I've followed:
Updated CWM to 6.0.5 (PhilZ's version)
Did a factory reset from recovery (I didn't use the "Clean to install new ROM" function)
Installed WizCyan version 4, followed by update 2
Rebooted, attempted to configure WiFi -- failed.
Flashed the NE5 modem package from the links in the dev thread, using Odin 3.07 -- twice each, as instructed
Still can't get my Wifi to enable. The flash was successful, as I can see the correct baseband on the "about" screen, but it refuses to enable. I'm in Australia, but I believe this phone came from UAE -- would that make a difference to the way the modem interacts with the Wifi hardware? I pulled this info from logcat:
Code:
I/WifiManager( 1084): setWifiEnabled : true
I/WifiService( 882): setWifiEnabled: true pid=1084, uid=10008
E/WifiHW ( 882): ##################### set firmware type 0 #####################
E/WifiHW ( 882): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 882): ==========[WIFI] Station firmware load ===========
E/WifiHW ( 882): return of insmod : ret = -1, Exec format error
E/WifiStateMachine( 882): Failed to load driver
E/WifiStateMachine( 882): sendErrorBroadcast code:10
E/WifiController( 882): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
In the mean time, I'm going to try to source either a local radio, or one from the original region, to see if that helps.
andycore said:
I've been tinkering with trying to get WizCyan totally working on my device for a couple of days, but I can't for the life of me get Wifi working (at first it was root access, but that was fixed by upgrading CWM). Here is the exact process I've followed:
Updated CWM to 6.0.5 (PhilZ's version)
Did a factory reset from recovery (I didn't use the "Clean to install new ROM" function)
Installed WizCyan version 4, followed by update 2
Rebooted, attempted to configure WiFi -- failed.
Flashed the NE5 modem package from the links in the dev thread, using Odin 3.07 -- twice each, as instructed
Click to expand...
Click to collapse
Can't get anything much from the logcat, it refers to a file that gets created on 1st boot you can try doing a factory reset from settings--> backup & restore--> factory data reset. Only backup your internal sd card before doing this as it will wipe your entire phone including internal sdcard and then reflash the modem.
JASONRR said:
Can't get anything much from the logcat, it refers to a file that gets created on 1st boot you can try doing a factory reset from settings--> backup & restore--> factory data reset. Only backup your internal sd card before doing this as it will wipe your entire phone including internal sdcard and then reflash the modem.
Click to expand...
Click to collapse
Well if I'm going to go that far, I may as well do it properly and completely restore the phone to stock and start again. When I bought it, the first thing I did was root, flash CWM and a CM based ROM -- it's probably worth starting fresh anyway, I'm only going to be using it for a couple more weeks until it's replacement arrives.
I'm currently downloading the latest firmware for my region (XSA), a 4.2.2 based MK3 build from the end of last year -- do you think I'd have better chances if I restored to a 4.4.2 build (like NE5), or should it not matter if I completely reset the phone to factory settings/software?
andycore said:
Well if I'm going to go that far, I may as well do it properly and completely restore the phone to stock and start again. When I bought it, the first thing I did was root, flash CWM and a CM based ROM -- it's probably worth starting fresh anyway, I'm only going to be using it for a couple more weeks until it's replacement arrives.
I'm currently downloading the latest firmware for my region (XSA), a 4.2.2 based MK3 build from the end of last year -- do you think I'd have better chances if I restored to a 4.4.2 build (like NE5), or should it not matter if I completely reset the phone to factory settings/software?
Click to expand...
Click to collapse
Generally doing a factory reset from the phone resets the entire firmware and is helpfull to resolve such issues. if you want to install the entire firmware, I would recommend flashing the 4.4.2 PHN firmware you can get the download link in post# 13. But then there were wifi issues after flashing the PHN firmware for which a factory reset from the phone happened to be the solution.
JASONRR said:
Generally doing a factory reset from the phone resets the entire firmware and is helpfull to resolve such issues. if you want to install the entire firmware, I would recommend flashing the 4.4.2 PHN firmware you can get the download link in post# 13. But then there were wifi issues after flashing the PHN firmware for which a factory reset from the phone happened to be the solution.
Click to expand...
Click to collapse
Thanks for that mention of the firmware, I had the radio from that link but forgot you'd also linked the full package. Google Drive is much faster than the websites I'd been trying to get files from, it took 15 hours to download the XSA firmware I was originally going to use.
You were totally correct, resetting the phone was the solution. I got the PHN firmware, flashed it via ODIN only to find it still hadn't fixed the WiFi problem -- even after a factory reset -- however the process of flash/reset/re-flash fixed it for me -- it seems unnecessary to me, but I guess times have changed since I last tinkered with unlocked devices. I'm happy to say that I now have WiFi working under WizCyan now, just wanted to check back in just in case anybody else was facing similar issues. As painful as it is to have to back up and totally restore, sometimes starting completely fresh is the best solution.
Now I'm off to rebuild my SD Card, lol.
andycore said:
Thanks for that mention of the firmware, I had the radio from that link but forgot you'd also linked the full package. Google Drive is much faster than the websites I'd been trying to get files from, it took 15 hours to download the XSA firmware I was originally going to use.
You were totally correct, resetting the phone was the solution. I got the PHN firmware, flashed it via ODIN only to find it still hadn't fixed the WiFi problem -- even after a factory reset -- however the process of flash/reset/re-flash fixed it for me -- it seems unnecessary to me, but I guess times have changed since I last tinkered with unlocked devices. I'm happy to say that I now have WiFi working under WizCyan now, just wanted to check back in just in case anybody else was facing similar issues. As painful as it is to have to back up and totally restore, sometimes starting completely fresh is the best solution.
Now I'm off to rebuild my SD Card, lol.
Click to expand...
Click to collapse
Glad to know that you managed to get the wifi working.
Personally, I did not face the wifi issue after flashing PHN firmware, but know that quite a few have faced this issue as reported in this thread
Normally my understanding and experience is that when you flash different modems / firmware some corruption occurs and factory reset from within the phone resets the partition & firmware. 1st time I experienced this was when I was using a MTK 6575 based device and had amended the EBR, MBR and scatter files to modify the partition sizes, even though these were flashed through mobiuncle tools (similar to odin), the revised partitions did not get changed until I did a factory reset from within the phone. I know that this is irrelevant here but thought that I would share this.
Straight to the content, new mirrors appreciated. I will update this thread as soon as a new update comes out.
Links to Odin are from sammobile, and the ADB drivers are on Github. All links are clean and untouched.
Odin 3.11.1
ADB for Windows
===========================
Untouched side loadable update zips downloaded from xdmd.sl.attcompute.com (sideload using ADB):
7.0 branch:
2017 Mar security level Android 7.0 (G920AUCU5EQB8 to G920AUCU6EQC9)
2017 Mar security level Android 7.0 (G920AUCU5DQB3 to G920AUCU6EQC9)
2017 Feb security level Android 7.0 (G920AUCU5EQA8 to G920AUCU5EQB8)
2017 Feb security level Android 7.0 (G920AUCU5DQB3 to G920AUCU5EQB8)
2017 Jan security level Android 7.0 (G920AUCS5DPK5 to G920AUCU5EQA8) | Credit goes to Mohit0144
6.0 branch:
2017 Feb security level Android 6.0.1 (G920AUCS5DPK5 to G920AUCU5DQB3)
2017 Feb secruity level Android 6.0.1 (G920AUCS5DPK3 to G920AUCU5DQB3)
2017 Jan security level Android 6.0.1 (G920AUCS5DPK3 to G920AUCS5DPK5)
2016 Dec security level Android 6.0.1 (G920AUCS5DPK1 to G920AUCS5DPK3)
2016 Nov security level Android 6.0.1 (G920AUCS5DPJ1 to G920AUCS5DPK1)
===========================
Official complete Odin images (flash using Odin):
2016 Oct security level Android 6.0.1 (G920AUCS5DPJ1)
Current update path to most current build:
G920AUCS5DPJ1 (odin flash) -> G920AUCS5DPK1 (sideload) -> G920AUCS5DPK3 (sideload) -> G920AUCS5DPK5 (sideload) -> pre-release G920AUCU5EQA8 (sideload) -> pre-release G920AUCU5EQB8 -> pre-release G920AUCU6EQC9
If you are on a version more recent than DPJ1, you can start from a later sideload update.
Disclaimer: You are responsible for what you do to your phone
How to flash using Odin (will wipe phone):
1. Extract complete firmware
2. Extract Odin software
3. Shutdown phone
4. Press BL, AP, CP, and CSC buttons in-order in Odin and load files, Odin may freeze during this, just wait it out. Don't touch other options
5. Press Volume down, home, and power together to go into download mode
6. Plug in phone to laptop, and press start to flash
How to sideload using ADB (will wipe phone):
1. Install ADB, reboot
2. Using cmd, cd into the folder of the sideload update zip
3. Shutdown phone, press Volume up, home, and power together to go into download mode
4. Select "apply update from adb", use power button to confirm
5. Using the command "adb devices", verify that the phone is detected after plugging in, if it is detected, proceed
6. Type in command "adb sideload SIDELOADZIPNAME"
7. Wait, it takes a bit for the update to work, and the phone may appear frozen during this process.
If confused, see this thread: http://forum.xda-developers.com/att...ating-to-android-6-0-1-g920aucu3cpd6-t3371884
did exactly what u said with the odin and i keep getting a fail...
Billfromnj05 said:
did exactly what u said with the odin and i keep getting a fail...
Click to expand...
Click to collapse
Well, the file is the exact same as that from this thread. And it is working for those people, so not sure why this is happening to you without more details.
Thank you for these updates.
would this fix the reboot issue? clearing cache doesnt help with previous update (oct)
drek_67045 said:
would this fix the reboot issue? clearing cache doesnt help with previous update
(oct)
Click to expand...
Click to collapse
I have absolutely no idea about why your phone is crashing.
Installing an update may fix it, just by virtue of clearing the /data partition and resetting it to stock in the process. But personally I doubt it (unless google fixed a denial of service bug that you were somehow triggering?).
Not really a diagnosis thread, so do you mind creating a new post with USB debugging turned on and logcat output so the community can help?
See here: http://android.wonderhowto.com/how-...ture-logcat-for-detailed-bug-reports-0167774/
drek_67045 said:
would this fix the reboot issue? clearing cache doesnt help with previous update (oct)
Click to expand...
Click to collapse
Not sure as to specifics of your reboot issue, but I had an S6 that started giving me multiple random reboots per day. Luckily I was inside warranty by a couple weeks - it was a hardware issue. Ended up with a new main board, plus a new display since the tech broke the original somehow changing the board.
That's funny. I never got Dec update for my AT&T S6 variant over OTA. I guessing, it's time to sideload it again.
supersmilers said:
That's funny. I never got Dec update for my AT&T S6 variant over OTA. I guessing, it's time to sideload it again.
Click to expand...
Click to collapse
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
sand_bit said:
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
Click to expand...
Click to collapse
Man can you tell me, how do you flash in adb sideload the latest firmwares?, my s6 send me an error
E: Error in /sideload/package.zip
(status 7)
sand_bit said:
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
Click to expand...
Click to collapse
December update has been pushed out OTA. Is PK3.
Sent from my SAMSUNG-SM-G920A using Tapatalk
GilbertoXDA17 said:
Man can you tell me, how do you flash in adb sideload the latest firmwares?, my s6 send me an error
E: Error in /sideload/package.zip
(status 7)
Click to expand...
Click to collapse
Not sure, but probably need to flash this with Odin
worked fine, note of caution.
my att gs6 was on oj9. flashed went through fine initially then an error came up "can't open the serial(com)port" and FAIL in red above the blue part.
however, the phone progress meter kept going and eventually the flash was successful.
My g920a is stuck at g920aucs5dpi1 and on ota it says my software is up to date. I don't know what's happening or is it because I am not using at&t sim? But it's already unlocked.
wiltaf said:
My g920a is stuck at g920aucs5dpi1 and on ota it says my software is up to date. I don't know what's happening or is it because I am not using at&t sim? But it's already unlocked.
Click to expand...
Click to collapse
I would bet that it's because you're not on an AT&T sim. I don't think they feel responsible to update the phone if it's not on their network. Not sure if you can throw someone's sim in there to update it or if you just ODIN flash it to update it.
Edit: You can also try to use Smart Switch to see if it'll pull the update, or try a Samsung Experience at a BestBuy to see if they can push the update.
Thanks. Now my phone is up to date.
This is the only way I can apply updates. For some reason I never get the OTA updates.
Thanks my phone updated to latest.
will my unlocked galaxy s6 become locked if i update using this?
Could someone tell me if the encryption menu items are available on your GS6, and what build you are on?
I encrypted my phone about 2 builds back, and after the December update, upon reboot it no longer asks for my PIN/PW and encryption is no where to be seen in the settings, or at least I (and search) can't find it. I don't want to factory reset to see if it reappears...yet.
If AT$T removed encryption from the device in the next update, I'm going to be real pissed.
Also, I think (at the moment) my battery life is worse on the latest build, but I have been using my phone a little more lately. But last night I went from 100% at 7:05pm to 5% at 11:30pm. 4.5 hours is not way to quick for a battery to die. Wakelock Detector (no root) didn't give much info, and the system menu for battery gave 3 of the top 4 to Android OS, Google Play services, Android System.
TIA
Is this for phones already with root access?
Hey guys,
I'm on a stock Samsung Galaxy S6, SM-G920A, Android Version 6.0.1, Security Patch Level December 1, 2016, Build Number: MMB29K.G920AUCS5DPK3. I have an AT&T Go-Phone account (pre-paid). Do I have to root my phone before following this procedure? I have never tried to root this phone before. I have been researching the topic for a long time and just wanted to make sure I understand everything thoroughly before I pull the trigger. Don't want to trip KNOX or brick my phone. Any help would be much appreciated. Thanks fellas.
Matt
---------- Post added at 11:42 AM ---------- Previous post was at 11:31 AM ----------
Zero4 said:
Could someone tell me if the encryption menu items are available on your GS6, and what build you are on?
I encrypted my phone about 2 builds back, and after the December update, upon reboot it no longer asks for my PIN/PW and encryption is no where to be seen in the settings, or at least I (and search) can't find it. I don't want to factory reset to see if it reappears...yet.
If AT$T removed encryption from the device in the next update, I'm going to be real pissed.
Also, I think (at the moment) my battery life is worse on the latest build, but I have been using my phone a little more lately. But last night I went from 100% at 7:05pm to 5% at 11:30pm. 4.5 hours is not way to quick for a battery to die. Wakelock Detector (no root) didn't give much info, and the system menu for battery gave 3 of the top 4 to Android OS, Google Play services, Android System.
TIA
Click to expand...
Click to collapse
I'm on AT&T Galaxy S6, SM-G920A, Android Version 6.0.1, Build #: MMB29K.G920AUCS5DPK3. My phone is stock, no root. I have the encryption settings and am currently using them. Everything seems to be working fine.
---------- Post added at 06:22 PM ---------- Previous post was at 05:42 PM ----------
mjr4281 said:
Hey guys,
I'm on a stock Samsung Galaxy S6, SM-G920A, Android Version 6.0.1, Security Patch Level December 1, 2016, Build Number: MMB29K.G920AUCS5DPK3. I have an AT&T Go-Phone account (pre-paid). Do I have to root my phone before following this procedure? I have never tried to root this phone before. I have been researching the topic for a long time and just wanted to make sure I understand everything thoroughly before I pull the trigger. Don't want to trip KNOX or brick my phone. Any help would be much appreciated. Thanks fellas.
Matt
---------- Post added at 11:42 AM ---------- Previous post was at 11:31 AM ----------
I'm on AT&T Galaxy S6, SM-G920A, Android Version 6.0.1, Build #: MMB29K.G920AUCS5DPK3. My phone is stock, no root. I have the encryption settings and am currently using them. Everything seems to be working fine.
Click to expand...
Click to collapse
They did change it up though. Whatever you choose as your screen lock i.e., pattern, pin, password, is what will be used for unencryption at start-up. The one thing that doesn't make sense to me is that they now give you an option to use one of these methods or none at all during start-up. I don't see the point in using encryption if you can't password protect it, but I haven't fully researched all the options yet.
the latest August 2020 update
has broken LOCAL vpn on my (Brzailian) s10+
PDA G975FXXU8CTG4
CSC G975FOWO8CTG4
result : no more Adguard (nor Blokada)
for info Windscribe vpn works (but this does not resolve my AD-annoyances ...)
now, I tried to go back to an earlier ROM but of corse Samsung made that impossible (flashing via Odin I get the message on the phone-screen that the ROM is not compatible)
is there a workaround to get back to an earlier ROM ?
thanks
Bas
You can only go back to an earlier stock ROM if it's on the same bootloader you're currently on. Bootloader 4 can't go back to bootloader 3. However, bootloader 4 and roll back to an earlier bootloader 4 version.
ok, thanks for the info
in the end I rooted with magisk
now using AFWall+ (firewall) and Adaway, having much more control
Lord i was just abt to upgrade... Samsung screwed up. again. guess you gotta wait for the patch.
for those using AdGuard...
Try the latest nightly: 3.5 nightly 6
Their changelog says: * [Fixed] Fix For Device With A Restrictive Account #3299
after updating the app, use adb as described here:
https://kb.adguard.com/en/android/faq#restrictedaccount
This worked for me
Help - my S20FE is driving me to the point where I'll reactivate my 15 year old nokia...
Here's what I have:
S20FE (german t-mobile, SM-G780G DS), latest OS image (G780GXXU3DVK5), rooted with the latest Magisk version.
What I'm experiencing: the UI freezes up, then eventually restarts, every 5 to 10 minutes. Visually the only indication that it's not an actual reboot is the fact that it goes directly to the screen that only has "SAMSUNG" on it, without the screen with the "bootloader is unlocked" warning that you'd normally see first.
I'm pretty sure it is not a hardware issue, when it first started I did a full wipe / reflash, and then the phone worked fine for about a week or two, now it's doing it again.
Is there ANY way to actually see WHAT is crashing, and maybe even why? I already wiped the cache of that oneUI, and the whole cache from recovery, that did not help.
I guess I'm the only one here who has a S20FE.
Hi, did you manage to solve the issue? I'm currently on Android 11 One UI 3.1 but thinking about updating but I want to know everything first. I was reading that you can update without loosing root but I want to know that is safe first.
I am not completely sure yet but I believe I have it narrowed down to two apps.
I actually went back to the previous major version which was a pain all in itself, it's not easy to find downloads for older Samsung images... anyway, I am back on Android 12, and one UI 4.1, when the crashes start again....
eventually, I uninstalled greenify and kde-connect and the crashes have stopped so far.
kaliko1991 said:
Hi, did you manage to solve the issue? I'm currently on Android 11 One UI 3.1 but thinking about updating but I want to know everything first. I was reading that you can update without loosing root but I want to know that is safe first.
Click to expand...
Click to collapse
I have done updates w/o loosing root or data on magisk-rooted samsung devices, but it is a manual process.
1. use samfirm or frija to get the latest rom image zipfile for your device
2. unpack the firmware zip, you'll get 5 image files.
3. update the magisk app on your device
4. out of the 5 files from the firmware zip, copy the one that starts with AP_ to your device
5. use the magisk app on your device to apply magisk to that file
6. copy the file resulting in that patch back to your computer
up to here the process is the same as the initial install of magisk on a samsung, minus the unlocking of the bootloader.
7. get your device into download mode, and use odin to flash all four parts (BL, CP, AP, and this is important HOME_CSC). by flashing HOME_CSC instead of CSC into the appropriate slot you retain all user data!!
So far this was worked for me on a Tab S2, and a S20fe. Haven't tried on any other yet. YMMV.
I did everything just as described and I'm currently with a boot loop and eventually boots into stock recovery and ask me to do a factory reset. I guess it's over then, I'm loosing all my data.