Hey guys, I want to root my pad. Is the warranty important?
I know if I root it, I won't be able to use Samsung Pass and Secure Folder, but I still want to root it.
Nightmare0 said:
Hey guys, I want to root my pad. Is the warranty important?
I know if I root it, I won't be able to use Samsung Pass and Secure Folder, but I still want to root it.
Click to expand...
Click to collapse
Pad?
jhill110 said:
Pad?
Click to expand...
Click to collapse
I tried rooting the Tab S7 with magisk with no luck.
After flashing patched AP magisk doesn't show as installed
itzik16 said:
I tried rooting the Tab S7 with magisk with no luck.
After flashing patched AP magisk doesn't show as installed
Click to expand...
Click to collapse
I've successfully rooted it. Try to patch boot instead of AP
itzik16 said:
I tried rooting the Tab S7 with magisk with no luck.
After flashing patched AP magisk doesn't show as installed
Click to expand...
Click to collapse
Extract boot.img.lz4 and tar it. Use magisk to patch it. Flash it by using AP slot and then wipe data.
jhill110 said:
Pad?
Click to expand...
Click to collapse
I mean Galaxy Tab
Nightmare0 said:
Extract boot.img.lz4 and tar it. Use magisk to patch it. Flash it by using AP slot and then wipe data.
Click to expand...
Click to collapse
It didn't work for me can you send me the TAR file you used?
itzik16 said:
It didn't work for me can you send me the TAR file you used?
Click to expand...
Click to collapse
https://drive.google.com/file/d/1vkAcCLa2PDTsall2Q97hfnJs6jPC-kIv/view?usp=sharing
It is too large so I cannot upload it. This is the Google Drive link. (Only for T970 ver. TH1)
Where do you guys find the official firmware to root it with magisk?
Sammobile doesn't have it
Sapiens said:
Where do you guys find the official firmware to root it with magisk?
Sammobile doesn't have it
Click to expand...
Click to collapse
Samfirm
CSC code XSP Singapore Open
Nightmare0 said:
https://drive.google.com/file/d/1vkAcCLa2PDTsall2Q97hfnJs6jPC-kIv/view?usp=sharing
It is too large so I cannot upload it. This is the Google Drive link.
Click to expand...
Click to collapse
It does work, I patched it, flashed as AP, and root is present.
However, I have a weird issue now — when the display is turned off, either using the power button, or automatically after the timeout set in settings — it doesn’t turn back on for me now. When I press the power button now, the Tab goes on, but the display stays off.
Thought it was due to turning off autobrightness, think I’ve seen historically somewhere such behavior. But no, even when I turned autobrightness on now, it won’t come back on now. Every time it goes off, I have to force reboot, to make it turn back on.
Any idea what can be causing this?
白い熊 said:
It does work, I patched it, flashed as AP, and root is present.
However, I have a weird issue now — when the display is turned off, either using the power button, or automatically after the timeout set in settings — it doesn’t turn back on for me now. When I press the power button now, the Tab goes on, but the display stays off.
Thought it was due to turning off autobrightness, think I’ve seen historically somewhere such behavior. But no, even when I turned autobrightness on now, it won’t come back on now. Every time it goes off, I have to force reboot, to make it turn back on.
Any idea what can be causing this?
Click to expand...
Click to collapse
I've tested, and I haven't got this issue. Try to turn on the "Magisk Core Only Mode" and reboot. It may be caused by some module.
By the way, the boot file I uploaded is only for Galaxy Tab S7+ T970, software version TH1. What's the model and software version of your device?
OK, that's the reason, I've got T976B. Will have to wait for the firmware for it and patch it then — currently not yet on sammobile…
I thought I checked that yours was the same version, but apparently not…
Thanks
Downloading
白い熊 said:
OK, that's the reason, I've got T976B. Will have to wait for the firmware for it and patch it then — currently not yet on sammobile…
I thought I checked that yours was the same version, but apparently not…
Click to expand...
Click to collapse
I've found the firmware for T976B. Use Samfirm to search SM-T976B, region DBT. Flash the latest firmware and then patch the boot file and flash it.
Thank you very much! )
I'm surprised — never used samfirm, thought it was obsolete, only always downloaded from the sammobile site…
You know, the tab s6 is the first device I've owned and not rooted.
I have instead installed samsung package disabler, pushed through a couple of ADB commands for shortcutter and gsam battery monitor. Honestly in practical terms I don't believe root is an advantage any more, infact it causes more problems than it solves.
There are apps avaliable now on the play store that with the granting of permissions can do most of if not all of what only rooted apps could do in the past eg. Xposed edge has been replaced with Edge gestures.
Granted there are some notable exceptions such as backup apps and kernel tweakers but nothing game changing.
I won't be rooting my tab s7 plus when it arrives for aforementioned reasons.
mikedavo said:
You know, the tab s6 is the first device I've owned and not rooted.
I have instead installed samsung package disabler, pushed through a couple of ADB commands for shortcutter and gsam battery monitor. Honestly in practical terms I don't believe root is an advantage any more, infact it causes more problems than it solves.
There are apps avaliable now on the play store that with the granting of permissions can do most of if not all of what only rooted apps could do in the past eg. Xposed edge has been replaced with Edge gestures.
Granted there are some notable exceptions such as backup apps and kernel tweakers but nothing game changing.
I won't be rooting my tab s7 plus when it arrives for aforementioned reasons.
Click to expand...
Click to collapse
I have a TabS6 rooted and I don't have any problems at all.
jhill110 said:
I have a TabS6 rooted and I don't have any problems at all.
Click to expand...
Click to collapse
Yes you do, you just haven't come across one yet but you will. Widvine l1 support, losing your warranty after unlocking your bootloader are just two obvious ones.
I would like to know what you gain from rooting an 855 soc apart from what I have already mentioned? Not being sarcastic, honestly would like to know. Even true full custom roms probably will be very limited on a tablet, I'm guessing DEX is a pain to incorporate bugfree.
I can confirm it is working fine in a S7+ (SM-T970 EUX). At least in my case.
-Unlock OEM (under developer options)
-Boot in download mode (with the tablet powered down, press volume up + volume down and connect usb cable to PC)
-Long press volume up to unlock bootloader (you will lose all your data!)
-Download the original firmware (Using SamFirm),
-Flash it using ODIN in donwload mode (Optional, just to make sure you are using the same image you are going to patch)
-Extract boot.img.lz4 from AP_xxxx tar file.
-Decompress the lz4 to get the uncompressed boot.img
-Copy the file to the tablet
-Patch it using the latest Magisk Manager.
-Copy the patched boot image back to the PC.
-Recompress it as boot.img.tar
-Flash it using AP slot in Odin and reboot tablet.
You are done! Magisk manager shloud say now it is rooted. (you will also have a BIG warning every time the tablet is powered on, telling you how irresponsable and despicable you are by modifying the device)
Thanks to Nightmare0 and all the others that pointed the tools and hints to do it!
RedCrowx
Related
This is for both US Cellular Samsung S6 and S6 Edge variant. Thanks also goes to @g.lewarne for his work on Unikernel as a couple of their ramdisk/kernel commits were needed to get this going. Also, thanks to @datajosh for this template And @bpdev for testing the 925R4 version...
This will trip KNOX. It will. Trip. KNOX. IF YOU HAVE NOT TRIPPED KNOX YET - THIS WILL TRIP IT. ALSO - you CANNOT downgrade after you take the OTA so be sure you want it.
I hope that's clear enough?
Instructions:
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Reboot in to download mode (Power + Home + Volume Down)
Use ODIN to flash 925R4root.tar or 920R4root.tar (depending on your device)
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent.
Downloads
925R4 - http://1drv.ms/1HeDWXO
925R4 Source
920R4 - http://1drv.ms/1NUVJ8B This is untested...I did not have a tester for this version....
920R4 Source
The 925R4 version may or may not work with the Sprint 925P variant...no working data confirmed!
ENJOY!
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
cpfeifer said:
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
Click to expand...
Click to collapse
You could go back to the stock kernel, but you would loose root. Also as stated above you would trip knox.
someone on a sprint s5 edge said the only thing they noticed didnt work was data..just posting for them since they under 10 post..so thats awesome! if we could get data goin..we can have root!!
---------- Post added at 03:29 PM ---------- Previous post was at 03:17 PM ----------
this kernel has working data on the edge...if you could port the data stuff in yours it should be fine http://forum.xda-developers.com/spr...t/5-1-1-stock-of7-kernel-root-7-4-15-t3150350
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
borxnx said:
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
Click to expand...
Click to collapse
It should be flashed using ODIN...I believe I updated the link in the OP to fix that issue since I derp'd...
Sent from my SM-G920P using Tapatalk
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
sintro said:
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
Click to expand...
Click to collapse
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
cpfeifer said:
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
Click to expand...
Click to collapse
I reflashed back to stock, then installed supersu. Then opened it up, obviously it said "supersu binary not installed". Next, I flashed this kernel and once booted up supersu still repeats the previous message. In addition, root checker shows that phone is not rooted.
The only thing in the .tar file, for 920r4 at least because that's all I downloaded, is a modified kernel. Nothing about SuperSU or its binaries. This method alone does not root. This merely installs a modified SELinux permissive stock kernel. More steps are necessary to obtain root. You must flash either CF Auto Root or a custom kernel + SuperSU.zip.
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
borxnx said:
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
Click to expand...
Click to collapse
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
Thank you for redoing the ramdisk.
Will try out and let you know.
Anyone experiencing issues with 925r4? I have service but see no signal bars no matter where I go.
https://youtu.be/y7EpSirtf_E
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
This does indeed work. Thank you so much!
Edit...Added instructions I used to complete the root process.
First of all, I wanted to thank the OP of this thread for posting this guide and getting me headed in the right direction.
Credit to @djvoleur
I just wanted to share the method I used to root my USC Galaxy S6 with the Android 5.1.1 update. You will notice that the instructions are similar in the beginning. I added the extra steps that I used to complete the root process. I do not know if this method works for the Edge version.
As the OP states: This will trip knox. Personally, it doesn’t matter to me. I am too impatient and too much of a flash-a-holic to wait for a method that doesn’t trip knox.
Also, I am not a dev and I am unable to answer any questions other than how I obtained root. I am not responsible for any damage that might happen to your phone. Follow this procedure at your own risk.
Having stated these disclaimers, it really isn’t very difficult to implement. I’ve done it twice and both times worked perfectly.
Files you will need for flashing in Odin:
Odin 3.10.7 found here: http://tinyurl.com/puyq4v9
Rooted kernel 920R4root.tar found in the OP.
TWRP 2.7.8.0 (Sprint version, but I can confirm it worked for me. YMMV.) Here: http://tinyurl.com/phvrkaf
Files for flashing in TWRP:
Updated V-Kernel 920R4-071615.zip found here: http://tinyurl.com/o2h8rv4
Super SU v2.49 (beta) found here: http://tinyurl.com/or6mmqr
Now, PLEASE read these instructions before starting so that you will have a good understanding of what to do. After reading, you may begin.
Don’t forget to put the files for flashing in TWRP on your SD card (phone) before beginning this process.
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Boot into download mode (Power + Home + Volume Down)
Use ODIN to flash 920R4root.tar
Use ODIN to flash TWRP and make sure that reboot is NOT checked in options.
Unplug the phone and hold the Power + Volume Down key to reboot. When the screen goes blank, quickly hold the Power + Home + Volume Up key to boot into TWRP. If it doesn’t boot to TWRP, you may have to start over.
In TWRP flash the updated V-Kernel file first, then the Super SU file, and then reboot.
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent. (Worked for me.)
You now should be able to install Chainfire's Super SU app from the Play Store, and you can also use Root Checker to confirm you are rooted.
Good Luck!
Would this work on G920R7... J4 (rather than OF7) 5.1.1? That's what I have.
I see there is a PC1 update available also for my G920R7 which is 6.0 marshmallow.
Hard to believe I've had this device for a year with no root... Anyone can help me get this rooted? Thanks!
so after installing the intial kernel that did not work I scrolled through and saw the updated version...you should probably update the link for the untested r4 to the working version later posted...
my problem is that Im unable to load in anything but download mode due to kernel not seandroid enforcing basically not enabling me to load into recovery mode so I need the zipped version of the kernel to install via odin in download mode if possible otherwise im waiting on a 2 hour download of the stock kernal to install
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
en11gma said:
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
Click to expand...
Click to collapse
Use TB to remove the update apps - green phone icons in TB. That's how it always gets stopped on any samsung.
This is a custom Rom I made for the Samsung Galaxy Tab A 7.0 LTE (SM-T285), which suits my tastes.
If you have suggestions, send me a PM.
UPDATE 09/07/2016
================
A newer version that runs "root" (sepolicy constrained) scripts can be found here:
http://forum.xda-developers.com/android/development/rom-samsung-galaxy-tab-7-0-lte-2016-sm-t3455788
Use the above version instead if you want to experiment with features like apps 2 sdcard.
Modifications:
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
Installation Instructions:
Odin or Heimdall Required.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Link:
Download from Mega
jaritico said:
thanks, but what does after download zip? recovery mode or download mode? and how got it? this root t285?
Click to expand...
Click to collapse
Thanks, but what does after download zip? recovery mode or download mode? and how got it? this root t285?
Click to expand...
Click to collapse
You have to go to download mode and then use Odin to flash. Unfortunately this does not root the T285.
jedld said:
This is a custom Rom I made for the Samsung Galaxy Tab A 7.0 LTE (SM-T285), which suits my tastes.
If you have suggestions, send me a PM.
Modifications:
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
Installation Instructions:
Odin or Heimdall Required.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Link:
Download from Mega
Click to expand...
Click to collapse
Says I need the encryption key and if I do not have it to contact the developer ......
TopTongueBarry said:
Says I need the encryption key and if I do not have it to contact the developer ......
Click to expand...
Click to collapse
Sorry, updated links, try again and see if it works.
jedld said:
Sorry, updated links, try again and see if it works.
Click to expand...
Click to collapse
Yes, downloading now. Thanks.
Hi,
Anyone tried Pokemon Go update 0.37 with this ROM? The update fails to start for me. It prompts device/os version is incompatible.
I reverted back to version 0.35 and it works fine.
venomrat said:
Hi,
Anyone tried Pokemon Go update 0.37 with this ROM? The update fails to start for me. It prompts device/os version is incompatible.
I reverted back to version 0.35 and it works fine.
Click to expand...
Click to collapse
Yeah the newest version checks for xposed and a bunch of other things. Actually a lot of people were pissed that they did this. You'd probably need to revert back to stock if you want to play. Only systemless root and xposed with magisk works for Pokemon go now.
jedld said:
Yeah the newest version checks for xposed and a bunch of other things. Actually a lot of people were pissed that they did this. You'd probably need to revert back to stock if you want to play. Only systemless root and xposed with magisk works for Pokemon go now.
Click to expand...
Click to collapse
Also if you want more details on what is going on search google for "pokemon go safetynet". Basically most custom roms and not just this device should fail the test.
jedld said:
This is a custom Rom I made for the Samsung Galaxy Tab A 7.0 LTE (SM-T285), which suits my tastes.
If you have suggestions, send me a PM.
UPDATE 09/07/2016
================
A newer version that runs "root" (sepolicy constrained) scripts can be found here:
http://forum.xda-developers.com/android/development/rom-samsung-galaxy-tab-7-0-lte-2016-sm-t3455788
Use the above version instead if you want to experiment with features like apps 2 sdcard.
Modifications:
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
Installation Instructions:
Odin or Heimdall Required.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Link:
Download from Mega
Click to expand...
Click to collapse
Hello and thank you for your work with this device. Currently I am looking for a bypass for the factory reset protection on my sm t280. I have flashed the stock md5 file 3+ times attempting to do a complete data wipe and reset, and this doesnt remove the lock. Any ideas?
BadReligion420 said:
Hello and thank you for your work with this device. Currently I am looking for a bypass for the factory reset protection on my sm t280. I have flashed the stock md5 file 3+ times attempting to do a complete data wipe and reset, and this doesnt remove the lock. Any ideas?
Click to expand...
Click to collapse
To FRP unlock you have to go to developer settings and switch oem unlock to false. The stock rom should have it unless you are using a carrier locked version that I a! not aware of.
jedld said:
To FRP unlock you have to go to developer settings and switch oem unlock to false. The stock rom should have it unless you are using a carrier locked version that I a! not aware of.
Click to expand...
Click to collapse
please excuse my ignorance, but am i able to do this with out being able to login? the person i purchased it from doesnt have the original owners gmail and pw.
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
BadReligion420 said:
please excuse my ignorance, but am i able to do this with out being able to login? the person i purchased it from doesnt have the original owners gmail and pw.
Click to expand...
Click to collapse
I just downloaded a stock recovery for a sm t285, and was going to attempt to flash to the 280. havent yet, do you feel that would be a safe thing to attempt? not looking to brick.
BadReligion420 said:
please excuse my ignorance, but am i able to do this with out being able to login? the person i purchased it from doesnt have the original owners gmail and pw.
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
I just downloaded a stock recovery for a sm t285, and was going to attempt to flash to the 280. havent yet, do you feel that would be a safe thing to attempt? not looking to brick.
Click to expand...
Click to collapse
FRP is specifically designed to prevent flashing if you can't login to the device. You won't be able to flash unless the person has turned off oem unlock beforehand. I am not aware of any method to bypass this on this device.
Also the T280 and T285 have slightly different hardware so using a different recovery image is not recommended. Also since both devices have a locked bootloader, I highly doubt you can even change the recoveries from stock as I would imagine samsung using different keys for both. At the worst case it still always possible to reflash them back to stock if you do want to try
AARGH! If I had only waited and not sold my so difficult to get SM-T285M (to TTB)....sheesh never thought there would be this much progress
bang head live and keep learning
mac231us said:
AARGH! If I had only waited and not sold my so difficult to get SM-T285M (to TTB)....sheesh never thought there would be this much progress
bang head live and keep learning
Click to expand...
Click to collapse
And thank you so much for selling it. I don't speak enough Spanish to make the ordeal of getting one of the T285M's from so america worthwhile. I was planning on sticking with my T239M for awhile, then I saw your T285M on ebay.
I've dirty flashed jedld's T285 debloated rom, then dirty flashed his T285 tinker rom on top of that. Both onto my T285M. Working flawlessly. Wished he'd kept the mail app, but without touchwiz I guess that wasn't possible.
Something else they blocked in the kernel or with SElinux on the T285M is screen mirroring. Can only cast directly from apps.
Still I am happy overall. Now looking for a castrated version of daemonsu!
TTB
TopTongueBarry said:
And thank you so much for selling it. I don't speak enough Spanish to make the ordeal of getting one of the T285M's from so america worthwhile. I was planning on sticking with my T239M for awhile, then I saw your T285M on ebay.
I've dirty flashed jedld's T285 debloated rom, then dirty flashed his T285 tinker rom on top of that. Both onto my T285M. Working flawlessly. Wished he'd kept the mail app, but without touchwiz I guess that wasn't possible.
Something else they blocked in the kernel or with SElinux on the T285M is screen mirroring. Can only cast directly from apps.
Still I am happy overall. Now looking for a castrated version of daemonsu!
TTB
Click to expand...
Click to collapse
no need for a castrated version. Full ROOT is available soon now.
http://forum.xda-developers.com/showpost.php?p=68777842&postcount=27
Double Aargh...salt on my wounds ttb
Now my contact in S. America will not even reply to me
Contemplating on getting the Samsung J max 7.0 dual sim...yes no U.S lte but has an 8mp camera and a flash...similar to the T285 otherwise...can't say how many times I needed the flash for photos or even if for looking at labels peering into dim areas behind a monitor or tv..maybe end up in same pickle of no root...will see (number is SM-T285YD so it is based off the T285 it seems-maybe a Latin American version soon?)
Also trying to get the T705M from another source but taking forever...low hopes think it will come through
TopTongueBarry said:
And thank you so much for selling it. I don't speak enough Spanish to make the ordeal of getting one of the T285M's from so america worthwhile. I was planning on sticking with my T239M for awhile, then I saw your T285M on ebay.
I've dirty flashed jedld's T285 debloated rom, then dirty flashed his T285 tinker rom on top of that. Both onto my T285M. Working flawlessly. Wished he'd kept the mail app, but without touchwiz I guess that wasn't possible.
Something else they blocked in the kernel or with SElinux on the T285M is screen mirroring. Can only cast directly from apps.
Still I am happy overall. Now looking for a castrated version of daemonsu!
TTB
Click to expand...
Click to collapse
got another one - white color ...as a gift...God Bless - great device battery life is just incredible - nothing fancy but does its job...keeping this one (had it since early November) gave up on the 705m
Is this ROM compatible with Google Safetynet? I can't seem to log into Pokemon GO since I installed Tinker edition, so I'm thinking to switch to this one instead.
Haven't tried it but it should work.
Is the root part contained in boot.img or in system.img? In other words, when using Heimdall I should flash both system.img and boot.img, isn't it?
I'm getting bootloops with CM13, Omni and I don't know how I got Tinker working, I kind of remember flashing boot.img, then wiping, then flashing system.img, then wiping again.
EDIT: got this one working too by flashing boot.img (Heimdall complains it cannot receive confirmation msg) reboot into download again, then flashing system.img (this time heimdall does reboot the phone). however, pokemon go still wont connect due to google's safetynet compliance.
I'll try flashing recovery in case it is TWRP the one clashing with Safetynet.
PD: I didn't backup stock at the beggining of the process so I'm pretty much screwed with Pokemon until I can afford a new phone. But if someone has a stock ROM for T285MUBU0API2, please ping me.
EDIT2 Got pokemon working. I reinstalled TWRP (this ROM's recovery is the stock one, of course), then flashed unSU. It removed SuperSU binary and Google SafeNet got working again. I can't believe that, after so much hours I've put into finding the best custom ROM for this crappy phone, 95% of the time was spent in trying to get Pokemon GO running. I'm close to 40, FML.
If you have been hit with the 60% Battery Limit Update for the AT&T Note 7 SM-930A
Please use the following guide to fix it.
USE AT OWN RISK, I CAN CONFIRM WORKING FOR ME, FOLLOW INSTRUCTIONS EXACTLY AS DESCRIBED.
NOT RESPONSIBLE FOR ANY FAILURE TO FOLLOW INSTRUCTIONS, BASIC RESEARCH, BRICKED PHONES.
FIRST:
Download the firmware provided by
Miguelina Betty
A HUGE SHOUT OUT AND THANK YOU TO THIS USER FOR HER WONDERFUL SERVICE AND ADDITION TO THE COMMUNITY. BECAUSE OF HER WE HAVE OUR NOTE 7 BACK FOR AT&T
h t t p s ://drive.google(DOT)com/open?id=0B0OZuhSvD25GSDBtZ0xuRk9oRHM
SECOND:
Now that you have downloaded the BL, AP, CP, CSC Files, Follow the instructions Layed out in this Post:
www(DOT)n7r(DOT)co/topic/103-restore-to-100-back-from-60-battery-using-old-firmware-step-by-step-guide-n7r-approved/
FOR AT&T NOTE 7 USERS (SM-N930A) USE ODIN VERSION 3.12.3 (LATEST VERSION OF ODIN)
THIRD:
As a safety precaution, BACK UP EVERYTHING!
FOURTH:
IN ODIN, ONLY LOAD THE AP FILE. IF YOU LOAD ALL THE OTHER FILES, YOU WILL HAVE ALL YOUR DATA ERASED.
FIFTH:
If you have followed the instructions, your phone will reboot and you will have 100% charge capabilities. If you have the original Note 7, you will have 1 or 2 warnings while startup or charger plug in. If you have the replacement Note 7, you will have the green battery icon and your good to go. Both will get the 100% charge capability.
SIXTH:
If you want all your data erased and start with a clean phone, use all the files in ODIN as described in the post.
SEVENTH:
I have just performed this myself and confirm that it is working.
EIGHT:
Use either EZ Disabler or Package Disabler PRO to disable anything that would cause the phone to software update again. Follow instructions for this by researching, searching google, reading the forums etc.
FLASHING ONLY THE AP FILE WILL KEEP YOUR DATA INTACT BUT CAUSE SAMSUNG APPS TO STOP WORKING. YOU WILL STILL HAVE EVERYTHING ELSE WORKING AND 100% BATTERY. BUT FLASHING ALL THE FILES BL, AP, CP, CSC WILL ERASE ALL YOUR DATA, START WITH A BRAND NEW FACTORY STOCK WITH SAMSUNG APPS WORKING. YOU CAN ALWAYS FULL FLASH YOUR PHONE AT A LATER TIME AS LONG AS YOU MAKE SURE TO DISABLE ANY FUTURE UPDATES
Thanks to ALL THAT HAVE MADE THIS POSSIBLE!
Special Shout out to
Vito Nobile Fidanza
For making this guide possible!
Works great!!!
11/12/16 - I can verify that this works great! I was hit with the 60% cap and i just flashed only the AP file, then made sure to disable the OTA updates using Package Disabler Pro. Nothing on my phone was erased and I just successfully charged my phone to 100%. Thank you so much for this! My note 7 gets less hot than my wifes s7, so not worried at all. Glad to have my phone back to normal!!
Anyone getting the "this phone's security policy has been compromised, S health and Samsung Pay have been disabled message?"
Yeah i got it no Samsung pay
Sent from my SAMSUNG-SM-N930A using XDA-Developers mobile app
phucksamsung said:
Anyone getting the "this phone's security policy has been compromised, S health and Samsung Pay have been disabled message?"
Click to expand...
Click to collapse
Yes, from what I have learned so far, which I am still trying to investigate:
Flashing ONLY the AP file will save all the data, give back 100% charge capability with everything working perfectly.
EXCEPT SAMSUNG APPS. (S Health, Samsung PAY etc)
Flashing ALL the files, BL AP CP CSC will erase all the data, overwrite bootloader, firmware, modem and basically perform a factory data reset for original home and phone settings. This method allows you to start with a brand new phone, with samsung apps working.
I am waiting on confirmation with someone who flashed all the files.
But for now, its not a great loss because we get 100% battery back.
Worse comes to Worse, you can always back up your data, repeat the process and flash ALL the files and have your samsung apps back. Either way, data gone samsung apps......or data intact with no samsung apps.....100% battery is back.
CONFIRMED: A friend with SM-N930A who followed my method but FLASHED ALL THE FILES: BL, AP, CP, CSC Lost ALL HER DATA, Started with a fresh brand new phone....WITH SAMSUNG APPS WORKING.
Now comes personal choice
Anyone know if it works with the replacement device from AT&T
djkrush2010 said:
Anyone know if it works with the replacement device from AT&T
Click to expand...
Click to collapse
If your talking about the 2nd note 7 (replacement models). Yes it does
Sent from my SAMSUNG-SM-N930A using XDA-Developers mobile app
Thank you got it to work. Can anyone tell me what you are supposed to disable with the package disabler app?
Could anyone help me how to turn off the OTA on Package Disabler Pro, I used with the AP and it still get me updated.
quansulong said:
Could anyone help me how to turn off the OTA on Package Disabler Pro, I used with the AP and it still get me updated.
Click to expand...
Click to collapse
I disabled com.policydm, com.sec.android.soagent and com.ws.dm. This is for AT&T
phucksamsung said:
I disabled com.policydm, com.sec.android.soagent and com.ws.dm. This is for AT&T
Click to expand...
Click to collapse
The latest version of Package Disabler Pro has hided the com.ws.dm, how could I make it disable?
quansulong said:
The latest version of Package Disabler Pro has hided the com.ws.dm, how could I make it disable?
Click to expand...
Click to collapse
Looks like the latest version of Package Disabler has taken away the ability to stop updates. When I flashed my phone it immediately went to auto download the battery update and I was back where I started. Though I really want this phone its becoming more hassle than its worth. If someone knows how to stop the update I'm all ears.
stevenkeywest said:
Looks like the latest version of Package Disabler has taken away the ability to stop updates. When I flashed my phone it immediately went to auto download the battery update and I was back where I started. Though I really want this phone its becoming more hassle than its worth. If someone knows how to stop the update I'm all ears.
Click to expand...
Click to collapse
After the battery update, my battery show over 60% in white color instead of 60% below; with the popup of Safety Warning. Is my battery level showing fake or it still keeping the original?
stevenkeywest said:
Looks like the latest version of Package Disabler has taken away the ability to stop updates. When I flashed my phone it immediately went to auto download the battery update and I was back where I started. Though I really want this phone its becoming more hassle than its worth. If someone knows how to stop the update I'm all ears.
Click to expand...
Click to collapse
Here. this version will show those packages.
http://forum.xda-developers.com/note-7/help/dont-update-package-disabler-pro-want-t3489243/page3
phucksamsung said:
Here. this version will show those packages.
http://forum.xda-developers.com/note-7/help/dont-update-package-disabler-pro-want-t3489243/page3
Click to expand...
Click to collapse
I installed and it kept the pop up saying Logging in at "Please wait for license activation" and nothing else to do
Tog have to manually add the last package to the list
Just tried this method and i can confirm it is working.
Does anyone have previous version rom so we could get rid of the nagging popup on original phones?
Also, your SECOND should be FORTH, because after second the FORTH is too late, heck the THIRD is too late...
hi guys
newest firmware is out, completely solved the constant flash of the screen during sleep mode (as a result, battery will last much longer)
as usual, flash with stock recovery (WW-5.17.44.68 is recommanded) and than go back to TWRP, if you didn't unlock your bootloader just wait till
you can trigger the update via the Settings -> Software Update option.....
So far I can confirm it boots alright, still on Android 7.0 and the security patch is updated to 5 Feb 2018 (which is pretty cool, no KRACK or BLUEBORNE exploits....)
discussion?
Chaosruler said:
hi guys
newest firmware is out, completely solved the constant flash of the screen during sleep mode (as a result, battery will last much longer)
Click to expand...
Click to collapse
Interesting, was this an issue with the WW-5.17.44.68 update or has this been an ongoing issue? I didn't bother with the previous one because it didn't seem to do a whole lot, but never noticed this issue.
Chaosruler said:
as usual, flash with stock recovery (WW-5.17.44.68 is recommanded) and than go back to TWRP, if you didn't unlock your bootloader just wait till
you can trigger the update via the Settings -> Software Update option.....
Click to expand...
Click to collapse
I hate doing this juggle. Big part of why I don't try to update unless it's significant :/
Chaosruler said:
So far I can confirm it boots alright, still on Android 7.0 and the security patch is updated to 5 Feb 2018 (which is pretty cool, no KRACK or BLUEBORNE exploits....)
Click to expand...
Click to collapse
Thanks for the heads up on this. I check the release thread often in hopes of Oreo, but they don't bother putting this information on their small updates. I think I'll update just because of that really, although Oreo would have been nice too :silly:
Chaosruler said:
discussion?
Click to expand...
Click to collapse
I feel like there's probably only 2 or 3 people who check these forums often nowadays, which is a shame because the phone is quite nice, and even has the bootloader unlocked as well. But ASUS seems to have too many phones that need updates and we're left in the dust waiting. Both XDA and Zentalk forums have people complaining and talking about this being their last device, which is reasonable and align with my thoughts as well. Really though, I want to go and make my own ROM for this phone, but don't really have the time, resources, or experience to tackle it just yet. Maybe I can use it in the future for practice
Update Impressions
Happy to report that the update has improved my phone's performance. Before, when I would go to the gym, listening to Spotify via Bluetooth would drain the battery from 95%->60%. Post update, battery stayed above 80% from full charge. It also feels a bit faster overall. It's a bit too early to tell if it's for better or for worse, but right now I'm leaning towards better. Negative would be it reinstalls the bloatware, but after rerooting and using Titanium Backup, they were removed without issue.
If you're rooted with TWRP installed, I'll list the update procedure I did, since we don't get the OTA updates. I'm also writing it up just to have it for reference. I have the ZS570KL @ 2.15GHz so make sure if you're Pro(2.4GHz) you make adjustments. You'll also need a computer (I use Win10 but any computer with fastboot installed will work really) with fastboot in order to reflash TWRP.
Part 1: Returning to stock recovery and updating
1. Downloaded update from Here. 2.15GHz should be the second one down.
2. Downloaded stock recovery from Here. /u/Ryder. has pointed out the Zentalk forum has the latest recoveries available, so check there first. At the time of writing, I was pushed to login to view that forum, so instead I just grabbed the latest available from AndroidFileHost, 5.15.44.2562.
3. Move both to SD card. I don't think this might be necessary, but I know it works. I think stock recovery only reads off the SD card, but I can't recall. If you can't navigate to the files during the update, try doing this step.
4. Reboot into TWRP by turning the phone off, and then powering on while holding the Volume Down button.
5. In TWRP, hit Install, navigate to the SD card, and select the stock recovery. Swipe to flash it.
6. Reboot into recovery again. Once you see the ASUS logo, spam the volume keys. I had an issue where it would boot into a "No Command!" screen. Pressing the volume keys while it's loading up the recovery pushes it to load properly. If you get stuck in the "No Command" screen for more than 2 minutes, reboot by pressing and holding VolumeDown+Power buttons.
7. Once in stock recovery, select apply update, navigate to the update file and flash.
8. Reboot into updated firmware!
Part 2: Reinstalling TWRP
1. On your fastboot enabled computer, download TWRP 3.2.1* from Here. Rename the file something short to make it easier to flash (I renamed it to TWRP.img). *3.2.1 is available in the Mega. At the time of writing, I only checked the AndroidFileHost link and didn't check to see if there was an updated build for it. It is Oreo compatible, so when they finally get around to giving us Oreo, you'll have a suitable recovery to go along with it. Thanks to /u/Ryder. for the heads up.
2. Open a command window. Make sure you either move the file to the directory it opens to, or navigate to the folder it's in.
3. Put your phone into fastboot by shutting it down, then powering on while holding the volume up button. It should say FASTBOOT on the screen.
4. Plug phone into computer.
5. Run the command "fastboot flash recovery [TWRP.img]" where [TWRP.img] is whatever your file name is.
6. Reboot into recovery to test it!
Part 3: (Optional) Rooting your phone with Magisk
1. Download the Magisk Manager APK from Here. Only grab it from here, I don't think the PlayStore one is legitimate.
2. Open Magisk Manager, and hit install. It should prompt you to download Magisk 16. Hit install in the popup. Let it download.
3. Reboot into TWRP. Hit install, and navigate to the file (should be something like InternalStorage/MagiskManager/Magisk-v16.zip). Install it. Before rebooting, I recommend wiping Dalvik/Art and Cache.
4. Open Magisk Manager to check if it's installed. Enjoy root!
Hope this helps someone out there. With the infrequent, non-OTA updates, I have to remember how to do this every time I update. It's easier to have it written down for reference.
Awesome guide!
I think its worth to mention that Win10 is not a must, you can use any Windows from XP forwards as long as you install the android adb driver and software, you can also use Linux (most package managers handles symlink to adb) as well as Mac....
Also the adjustment done between the snapdragon 820 and snapdragon 821 version is not just around the update file downloaded but it's super important to make sure to not do that mistake, not all recoveries handle checking and if you flash the wrong file you might brick your device, even though its likely you could fastboot your fw slowly, youd lose all your data, so its better to back up your data on your sd card
Error when I try to download.
This the response I get from ASUS's website:
An error occurred while processing your request.
Reference #132.563d717.1520889776.1930fb2f
asianflipboy said:
Happy to report that the update has improved my phone's performance. Before, when I would go to the gym, listening to Spotify via Bluetooth would drain the battery from 95%->60%. Post update, battery stayed above 80% from full charge. It also feels a bit faster overall. It's a bit too early to tell if it's for better or for worse, but right now I'm leaning towards better. Negative would be it reinstalls the bloatware, but after rerooting and using Titanium Backup, they were removed without issue.
If you're rooted with TWRP installed, I'll list the update procedure I did, since we don't get the OTA updates. I'm also writing it up just to have it for reference. I have the ZS570KL @ 2.15GHz so make sure if you're Pro(2.4GHz) you make adjustments. You'll also need a computer (I use Win10) with fastboot in order to reflash TWRP.
Part 1: Returning to stock recovery and updating
1. Downloaded update from Here. 2.15GHz should be the second one down.
2. Downloaded stock recovery from Here. I just grabbed the latest available, 5.15.44.2562.
3. Move both to SD card. I don't think this might be necessary, but I know it works. I think stock recovery only reads off the SD card, but I can't recall. If you can't navigate to the files during the update, try doing this step.
4. Reboot into TWRP by turning the phone off, and then powering on while holding the Volume Down button.
5. In TWRP, hit Install, navigate to the SD card, and select the stock recovery. Swipe to flash it.
6. Reboot into recovery again. Once you see the ASUS logo, spam the volume keys. I had an issue where it would boot into a "No Command!" screen. Pressing the volume keys while it's loading up the recovery pushes it to load properly. If you get stuck in the "No Command" screen for more than 2 minutes, reboot by pressing and holding VolumeDown+Power buttons.
7. Once in stock recovery, select apply update, navigate to the update file and flash.
8. Reboot into updated firmware!
Part 2: Reinstalling TWRP
1. On your fastboot enabled computer, download TWRP 3.1.1 from Here. Rename the file something short to make it easier to flash (I renamed it to TWRP.img).
2. Open a command window. Make sure you either move the file to the directory it opens to, or navigate to the folder it's in.
3. Put your phone into fastboot by shutting it down, then powering on while holding the volume up button. It should say FASTBOOT on the screen.
4. Plug phone into computer.
5. Run the command "fastboot flash recovery [TWRP.img]" where [TWRP.img] is whatever your file name is.
6. Reboot into recovery to test it!
Part 3: (Optional) Rooting your phone with Magisk
1. Download the Magisk Manager APK from Here. Only grab it from here, I don't think the PlayStore one is legitimate.
2. Open Magisk Manager, and hit install. It should prompt you to download Magisk 16. Hit install in the popup. Let it download.
3. Reboot into TWRP. Hit install, and navigate to the file (should be something like InternalStorage/MagiskManager/Magisk-v16.zip). Install it. Before rebooting, I recommend wiping Dalvik/Art and Cache.
4. Open Magisk Manager to check if it's installed. Enjoy root!
Hope this helps someone out there. With the infrequent, non-OTA updates, I have to remember how to do this every time I update. It's easier to have it written down for reference.
Click to expand...
Click to collapse
It's better to use everytime the latest stock recovery from the latest firmware. You can find it here: https://www.asus.com/zentalk/tw/thread-185884-1-1.html?_ga=1.231834332.2123005859.1491423435
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
I also suggest the latest twrp which is the 3.2.1-0 version now and is compatible with oreo
Chaosruler said:
Awesome guide!
I think its worth to mention that Win10 is not a must, you can use any Windows from XP forwards as long as you install the android adb driver and software, you can also use Linux (most package managers handles symlink to adb) as well as Mac....
Click to expand...
Click to collapse
You're right about that. I've updated my post to reflect it.
Chaosruler said:
Also the adjustment done between the snapdragon 820 and snapdragon 821 version is not just around the update file downloaded but it's super important to make sure to not do that mistake, not all recoveries handle checking and if you flash the wrong file you might brick your device, even though its likely you could fastboot your fw slowly, youd lose all your data, so its better to back up your data on your sd card
Click to expand...
Click to collapse
This 100%. I think that it's important to backup any data that isn't already backed up. I can only hope that those who do have to go through this update process (as opposed to OTA updates) are careful with which versions they install.
Ryder. said:
It's better to use everytime the latest stock recovery from the latest firmware. You can find it here: https://www.asus.com/zentalk/tw/thread-185884-1-1.html?_ga=1.231834332.2123005859.1491423435
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
I also suggest the latest twrp which is the 3.2.1-0 version now and is compatible with oreo
Click to expand...
Click to collapse
Thanks, didn't realize there were updates for either. I've updated the post I made to reflect both changes. In regards to the Zentalk forum, I kept getting asked to login, so that's why I opted to use the AndroidFileHost link instead. I think it may have been because I was on mobile at the time. In any case, I dodn't have to login when viewing the forum on my laptop (might be adblocker?). Even though the older stock recovery worked fine for me, I think others should use the updated stock recovery to avoid any issues.
I didn't check the Mega for the updated TWRP. Didn't really expect it to be updated since we don't have Oreo yet, but it's nice to see that it's been made available. I've updated my own recovery to 3.2.1 and it's working fine.
indiana99 said:
This the response I get from ASUS's website:
An error occurred while processing your request.
Reference #132.563d717.1520889776.1930fb2f
Click to expand...
Click to collapse
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
asianflipboy said:
You're right about that. I've updated my post to reflect it.
This 100%. I think that it's important to backup any data that isn't already backed up. I can only hope that those who do have to go through this update process (as opposed to OTA updates) are careful with which versions they install.
Thanks, didn't realize there were updates for either. I've updated the post I made to reflect both changes. In regards to the Zentalk forum, I kept getting asked to login, so that's why I opted to use the AndroidFileHost link instead. I think it may have been because I was on mobile at the time. In any case, I dodn't have to login when viewing the forum on my laptop (might be adblocker?). Even though the older stock recovery worked fine for me, I think others should use the updated stock recovery to avoid any issues.
I didn't check the Mega for the updated TWRP. Didn't really expect it to be updated since we don't have Oreo yet, but it's nice to see that it's been made available. I've updated my own recovery to 3.2.1 and it's working fine.
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
Click to expand...
Click to collapse
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
asianflipboy said:
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
Click to expand...
Click to collapse
No. Thank you very much for asking. I downloaded from a different location.
indiana99 said:
No. Thank you very much for asking. I downloaded from a different location.
Click to expand...
Click to collapse
Good to hear.
Chaosruler said:
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
Click to expand...
Click to collapse
Hmm, I think I'll do that. I'll make some small zip files for each.
---------- Post added at 09:56 PM ---------- Previous post was at 09:16 PM ----------
indiana99 said:
No. Thank you very much for asking. I downloaded from a different location.
Click to expand...
Click to collapse
Chaosruler said:
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
Click to expand...
Click to collapse
Ryder. said:
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
Click to expand...
Click to collapse
Sorry for re-quoting all of you, but do you guys see the update anymore? It might have been why /u/indiana99 couldn't find it. I went to check while making the zip packs and it's not there... Maybe there was some issue with the build? It's got me a bit shook that it's suddenly not on the website.
Link for WW-5.17.44.87 (newest firmware) for the 821 variant (sorry 820 variant, I didn't download what's not mine)
https://drive.google.com/open?id=1XkqFVIMzyGnUxHIf5btu1uoyjTRxah1C
if anyone happened to did download the 820 variant, please share?
Chaosruler said:
Link for WW-5.17.44.87 (newest firmware) for the 821 variant (sorry 820 variant, I didn't download what's not mine)
https://drive.google.com/open?id=1XkqFVIMzyGnUxHIf5btu1uoyjTRxah1C
if anyone happened to did download the 820 variant, please share?
Click to expand...
Click to collapse
Sorry. I misread the OP. I am unable to locate WW-5.17.44.87 for the 820 variant. I would appreciate someone sharing.
Chaosruler said:
if anyone happened to did download the 820 variant, please share?
Click to expand...
Click to collapse
indiana99 said:
Sorry. I misread the OP. I am unable to locate WW-5.17.44.87 for the 820 variant. I would appreciate someone sharing.
Click to expand...
Click to collapse
That's weird to me though. I just checked again and both variants are missing the current update, 5.17.44.87. Did they pull it for some reason? As far as I can tell, my phone is behaving pretty normally. Anyone that's updated notice anything weird?
I've removed the link. This article claims that we're finally getting the update by the end of March!
https://www.phonearena.com/news/Asu...-ZenFone-3-Deluxe-receive-Oreo-March_id103395
Finally!
YOU CAN FIND THE FULL G930AUCU8CSA3 FIRMWARE HERE:
https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-oreo-8-0-stock-att-odin-files-t3869871
G930AUCU4CRE4 to G930AUCS4CRG5:
Download link: https://drive.google.com/file/d/1MoJ0be2exLMoji2ZURR6tbEiHCqWSszG/view
G930AUCS4CRG5 to G930AUCU4CRI2:
Download link: https://drive.google.com/file/d/1Fdrcy4m49Qtl-__dUE0Etuqmyn8UhYbe/view
G930AUCU4CRI2 to G930AUCS8CRJ2
Download link: https://drive.google.com/file/d/1bhVx5Rt_CTXmG5YQrY5azS10RO3lWj1r/view
G930AUCS8CRJ2 to G930AUCS8CRK1
Download link: https://drive.google.com/file/d/1lepPXVZIiZM4i_VMOUOvDvVHvGY4ifwv/view
G930AUCS8CRK1 to G930AUCS8CRL1
Download link: https://drive.google.com/file/d/1CUJOVWnDsk3LL378vxLO0vp8y3AdQjmr/view
If i helped you don't forget to hit thanks button
G930aucu4cri2
friend you have the security patch of August 1 the new update its version is G930AUCU4CRI2 weighs between 456MB or 472MB
Juliowwwe said:
friend you have the security patch of August 1 the new update its version is G930AUCU4CRI2 weighs between 456MB or 472MB
Click to expand...
Click to collapse
Link is UP
thank you very much
thank you very much
New October update is UP
Hello,
How to install these updates ?
I've succeed to install the 8.0 update with ODIN and with 4 files : AP & BL & CP & CSC.
But here there is no such files into the updates you uploaded.
lahlah said:
Hello,
How to install these updates ?
I've succeed to install the 8.0 update with ODIN and with 4 files : AP & BL & CP & CSC.
But here there is no such files into the updates you uploaded.
Click to expand...
Click to collapse
1.) Turn off the phone. Hold down Volume Up + Home + Power until you see a little Android guy. It will say Applying System Update or something like that possibly, and just let it do it's thing until a menu comes up.
2.) Select "Apply update from ADB". You can scroll using the volume buttons and select using the power button.
3.) Make sure you have ADB and the proper drivers installed on your PC:
http://dl.adbdriver.com/upload/adbdriver.zip
4.)Put the firmware in the ADB folder. You can rename it to anything easy to remember like "FIRMWARE".
5.) In the ADB folder, hold SHIFT + right mouse click and choose "Open command window here". Then type the command "adb sideload FIRMWARE" (where FIRMWARE is how you named your file).
6.) Wait patiently.
7.) The phone will reboot and will hang at AT&T logo. This can take another 10 minutes, just wait until it's done
Ok, so I'm a novice at best on flashing with Odin... just flashed my AT&T S7 for the second time today, loading the SM-G930U version of Oreo (G930UUEU8CRJ2).
My understanding is that the 8 in the firmware version (G930UUEU8CRJ2) indicates that it is bootloader v. 8. I also understand that once you update the bootloader, it is impossible to downgrade it... So when I realized I couldnt enable Wifi calling on SM-G930U firmwares I thought I would flash back to the AT&T firmware, and then debloat it to improve the performance. But i cant find an SM-G930A Oreo Rom with BL v. 8.
I thought this one might be, but the 3 files seem to be independant of each other, and the 3rd file that lloked like it might be BL8, is less than 50MB...
So Im hoping you can provide some guidance, and im hoping i didnt shoot myself in the foot with this SM-G930U firmware.
Thank you
Sam
samhnky said:
Ok, so I'm a novice at best on flashing with Odin... just flashed my AT&T S7 for the second time today, loading the SM-G930U version of Oreo (G930UUEU8CRJ2).
My understanding is that the 8 in the firmware version (G930UUEU8CRJ2) indicates that it is bootloader v. 8. I also understand that once you update the bootloader, it is impossible to downgrade it... So when I realized I couldnt enable Wifi calling on SM-G930U firmwares I thought I would flash back to the AT&T firmware, and then debloat it to improve the performance. But i cant find an SM-G930A Oreo Rom with BL v. 8.
I thought this one might be, but the 3 files seem to be independant of each other, and the 3rd file that lloked like it might be BL8, is less than 50MB...
So Im hoping you can provide some guidance, and im hoping i didnt shoot myself in the foot with this SM-G930U firmware.
Thank you
Sam
Click to expand...
Click to collapse
The bootloader binary was updated to 8. After you flash this you'll be stuck on Oreo.
Full firmware for G930A G930AUCS8CRJ2 will be uploaded later today.
stek-kravari said:
The bootloader binary was updated to 8. After you flash this you'll be stuck on Oreo.
Full firmware for G930A G930AUCS8CRJ2 will be uploaded later today.
Click to expand...
Click to collapse
Awesome! Thank you, thank you!
I actually really like Oreo, just trying to get Oreo and WiFi calling working on my phone (My Office at work fights all day for 1 bar of cell signal), I had hoped that WiFi calling worked in the SM-G930U variant since everyone talked about it running so much better, but alas, it still doesn't support WiFi Calling (Stupid me for thinking it might have had support added recently).
Thank you again
(My Wife is sure to get upset with me once again working on my phone again today... whoops)
Thanks , G930AUCS8CRJ2 is working fine so far. Do you mind sharing how you go about 'converting' a set of ODIN files to a flashable adb zip? Do you just unextract every single archive in the .md5 files? and then zip it all up? And would rooting to G930AUCU4CRI2 brick my phone now that I am on CRJ2? My bad for all of the questions.
bnn0 said:
Thanks , G930AUCS8CRJ2 is working fine so far. Do you mind sharing how you go about 'converting' a set of ODIN files to a flashable adb zip? Do you just unextract every single archive in the .md5 files? and then zip it all up? And would rooting to G930AUCU4CRI2 brick my phone now that I am on CRJ2? My bad for all of the questions.
Click to expand...
Click to collapse
You mean about G930AUCS8CRJ2 sideload with adb? Im just pulling the update from AT&T servers and uploading it here. I don't know how to make sideload zip. And for the rooting part I don't know if its possible now because the bootloader binary was updated to 8, try to search here on xda and see if you can find root methods for this firmware
new update, check first post
----
I can ask you a question? please. My baseband is SMG930AUCU4CRE4 can i update to G930AUCS8CRK1? :/
Maury Yarik said:
I can ask you a question? please. My baseband is SMG930AUCU4CRE4 can i update to G930AUCS8CRK1? :/
Click to expand...
Click to collapse
First you need to install this:
https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-oreo-8-0-stock-att-odin-files-t3869871 (G930AUCS8CRJ2)
Then you need to go from G930AUCS8CRJ2 to G930AUCS8CRK1, G930AUCS8CRK1 to G930AUCS8CRL1 and you will have the latest update.
I actually have a S7 G930A. Rooted before, not rooted now.. Is there a way to do any of these updates without hooking up to a PC? I actually have no charge port functions and can only use wireless charger to charge the phone till i get the port fixed someday to do these features. I am on Android 8.0 oreo that i installed to sd card and updated from there like a year ago? Is that possible to do? Use SD card update.. Or. Would love to root the phone again, but cent seem to find a one click root app that will work with this phone..
Josh
Josh13400 said:
I actually have a S7 G930A. Rooted before, not rooted now.. Is there a way to do any of these updates without hooking up to a PC? I actually have no charge port functions and can only use wireless charger to charge the phone till i get the port fixed someday to do these features. I am on Android 8.0 oreo that i installed to sd card and updated from there like a year ago? Is that possible to do? Use SD card update.. Or. Would love to root the phone again, but cent seem to find a one click root app that will work with this phone..
Josh
Click to expand...
Click to collapse
Yes, you can update your phone without pc, just download the update you need from your phone, put the update in your sd card, go to recovery and select the option "Apply update from SD card"
stek-kravari said:
Yes, you can update your phone without pc, just download the update you need from your phone, put the update in your sd card, go to recovery and select the option "Apply update from SD card"
Click to expand...
Click to collapse
I was thinking something like that was possible. I have baseband version G930AUCU4CRB5 Android 8.0.0 on the AT&T Gal S7 as mentioned, I never saw any updates from this version to go up to a newer version or get into regular updates from OTA. 2 issues I would like to also fixed, that came with the manual update to 8.0 oreo on my phone was the HR heart rate sensor on the back by your flash(red LED) always goes off.. And have tried to go to Samsung health and do some settings to turn it off, but seems to show back up eventually. Also, the issue of not having a working LED indicator, works fine when the phone is POWERED off. and charges. But in OS, it won't work, screen off or on bc of the update. If anyone knows how those issues could be fixed and if there is a possible newer update from my baseband mentioned below. And thanks for the response.
HI, Help needed
Hi,
I wanted to check if it is possible to flash the latest Oreo firmware you have here for downloading dirrectly to my samsung s7 that is currently running on 7.0? Current BaseBand is G930AUCU4BQK2
Basically what happened was that i lost all my contacts on my phone, I ended up download Dr.Phone to my laptop, which i used to try and recover my numbers. What i didnt know was that dr.phone rooted my device which has caused me nothing but headaches.
I now want to flash my phone and get updated to oreo and have my phone working normally again. Since dr.phone did whatever it did to my phone I lost use of my finger print scanner, had to disable samsung health as it kept trying to open on its own, my phone is lagging and freezing constantly..
I just want my phone to be normal again and unrooted and updated.
Lastly my phone is an AT&T device, that i bought second hand in Dubai, if i flash stock firmware is it going to carrier lock my device to AT&T again?
Any advice and help with this matter would be greatly appreciated.