Related
Get PRE ROOTED from Here
Flashed Leaked 4.3
Rooted successfully
It does have Knox suite But bootloader is not included so thats used for appl security, shouldn't make issue regarding warranty, though it's primary report, use at your own risk
Who are not in hurry to Root wait, let me study and understand better
THIS ROM IS WIPE ROM YOU WILL LOSE EVERYTHING ON DEVICE AS WELL INT SD CARD
Changes noted so far
Who can't hold to root follow this - TESTED by ME
How to Root :
Flash Philz recovery
Flash SuperSu1.65 (older won't work)
How to Rest Flash CounterTESTED by ME
-Download Stock Recovery
and copy to SD card Int/Ext
- Download MultiTool Advanced version (see My signature)
-Reboot to CWM, select MultiTool zip, Look for Recovery Menu - Select flash recovery from SD card (int/ext depend on location of stock recovery you put as in step1
-Flash
-Use Triangle away 3.05 to reset counter.
How to get USB debugging (Dev option)
Multiple time tap on setting - more - about device - Build number to unlock devlopment option
Titanium backup tested working
Directory Bind Working - You may need to describe path again backup may not work
First Mod created MultiWindow for all app - + CSC Features + Xposed Battery Module here
Don't Install Widget Locker
Someone reported Mobile Odin works - I personally didn't checked
Xposed framework working (I am using only two module both worked)
Lockscreen Widget (multiple) available
CSC features you can use with my MultiTool Advanced version, but don't select messege folder view, it will crash messeging app. Backup is highly recommended
-Someone reported No issue to downgrade
Bew leaked ROM doesn't have bootloader so Knox security may be just as suite but not related with warranty (These all are assumption now and follow at you own risk)
Also you should able to downgrade (DIDN'T TRIED YET)
No issue in downgrade
No issue in downgrade. This is how i have tested before public relelase
-Leaked 4.3 installed and rooted -> unrooted from SU -> rooted with prerooted ->No issue -> downgraded to MG1 (I had to wipe after downgrade, but no other issue) -> again flashed prerooted
So i have tested for both downgrading as well prerooted have no issue in root.
Found one weired thing with Knox
If remove knox related app, getting issue to use secured sites
I was unable to use banking sites (wifi/Mobile network disconnects), then i have restored knox app and then it is fine now,
If Anyone have notice some persistent notification with some application, it is due to 4.3
google have made persistent icon mandatory for application running in foreground. some developer makes their application running in foreground to make it non killable. they have to recode application.
Updating soon
Stock modem and kernel Recovery from 4.3 leaked
Stock Modem And Kernel
How to Flash
Download Stcok Kernel and copt boot.img to SD card. Use My MultiTool (Advanced)to flash kernel from SD card option
Download Modem.rar and Extract it to modem.bin Then copy modem.bin to SD card. Use My MultiTool (Advanced)to flash modem from SD card option
Download Stock Recovery and copy to SD card. Use My MultiTool (Advanced)to flash recovery from SD card option
Reserved
Reserved too
Last
KNOX ??
does it contains knox suite??
if yes then pls write about knox counter pls.
KNOX discussion in s4 must look they got it before us
Good news !!
so it is an authentic leak !
Damn Dr. K That was quick!
Well done.
There is Knox security
let me study some more
Who are not in hurry hold your horse to root
dr.ketan said:
There is Knox security
let me study some more
Who are not in hurry hold your horse to root
Click to expand...
Click to collapse
**** its in way flashing i f**** up.
s4 thread about knox
I love this Forum, Go Doc Go.
Will it be rooted if I use mobile Odin and inject supersu?
Sent from my GT-N7100 using Tapatalk 4
Give me some time to answer
How to root ?
Can we flash CWM (for example: philz) via odin and then flash any mods from note3 (snote3, launcher, etc ...)?
hold your horses, thats what the Doc said...this is LIVE coverage of a new release
mods come last in the list of priorities
dr.ketan said:
Give me some time to answer
Click to expand...
Click to collapse
give please instruction for root.I think this procese not hard.
rraaka said:
hold your horses, thats what the Doc said...this is LIVE coverage of a new release
mods come last in the list of priorities
Click to expand...
Click to collapse
i mean mods and also SU zip via CWM, it should be simpler with CWM, no?
I know some guys have rooted successfully.
Idiots worship phones like hell♡♥
How to root already updated half an hr ago on OP
UPDATE 14.05.2017: Chainfire has released autoroot for Galaxy S5 Mini G800F based on firmware 6.0.1. It can be downloaded from the official CF Autoroot website (direct link to the G800F file). It is by far the easiest and fastest method for getting root access on your device without the need for TWRP.
Procedure for rooting with CF autoroot:
1. Charge your S5 Mini's battery to at least 80% and make sure you have Samsung USB drivers installed on your PC
2. Enable USB debugging on the S5 Mini
3. Download the CF autoroot file from the link above and unpack the zip archive
4. Open ODIN as administrator (right click -> Run as administrator)
5. Put the S5 Mini in download mode and connect it via USB cable to the PC
6. After ODIN recognizes the device, click "AP" and select the autoroot file
7. Click "Start" and wait for the process to finish - shouldn't take more than a few seconds
8. When the log in ODIN says "Disconnected", unplug the USB cable from the phone and wait for it to restart itself
9. Verify proper root with a tool like Root Checker
If you want to have TWRP recovery and Xposed framework, use the guide below.
This method applies only to the S5 Mini G800F variant running Android 6.0.1. Trying this on other variants may result in bricking your device. I used this procedure to get root access and Xposed working on my European S5 Mini G800F using a German (DBT) Marshmallow firmware. Use at your own risk, I'm not responsible for anything that happens to your device. Note that this procedure voids your warranty. This guide assumes that you already have TWRP recovery or know how to flash it.
Backup everything important like contacts and photos before you begin.
Requirements for this method to work:
unrooted Samsung Galaxy S5 Mini G800F running official stock Android 6.0.1 Marshmallow
Samsung USB driver
enable USB debugging
charge your phone's battery to 100% just in case
TWRP Recovery 3.0.2 installed Official TWRP Recovery 3.1.1 is available now - check out this thread for download links
IMPORTANT NOTE ABOUT RECOVERY: Official TWRP now available
Procedure for getting root access:
1. Download Chainfire's SuperSU v2.78 SR5 [link] and store the zip file in the phone's internal memory or SD card.
2. Boot into TWRP recovery, navigate to the SuperSU zip and flash it, reboot after it finishes.
3. You should now see the SuperSU icon, open it and update the binary. Verify proper root with a tool like Root Checker.
Congratulations, you have successfully rooted your G800F! If you only want root - stop here, you're done.
Procedure for getting Xposed Framework:
1. After rooting your S5 Mini, download Xposed v87.1 built by wanam [link], Xposed uninstaller [link], and Xposed Installer APK [link]. Put all 3 files on the phone's internal memory or SD card.
2. Boot into TWRP recovery, navigate to the file named "xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125.zip" and flash it.
3. After the flashing is finished, wipe cache and dalvik then reboot.
4. Using a file manager, navigate to where you put the Xposed Installer APK and install it.
5. Open it and confirm that Xposed is installed properly.
weird enough all those files where already on my pc. i just wanted to know if it would work
it says no root
Zakipoophead27 said:
it says no root
Click to expand...
Click to collapse
Which firmware version are you trying to root and did you use the exact files I've linked?
kom-pakt said:
Which firmware version are you trying to root and did you use the exact files I've linked?
Click to expand...
Click to collapse
The netherland marshmallow firmare. And i have used all the files you linked. I even tried other one's. None work
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Tomislav3383 said:
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Click to expand...
Click to collapse
Same for me - rooting (Germany DBT) according to your instructions didn't work
Gesendet von meinem kminilte mit Tapatalk
Zakipoophead27 said:
The netherland marshmallow firmare. And i have used all the files you linked. I even tried other one's. None work
Click to expand...
Click to collapse
Tomislav3383 said:
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Click to expand...
Click to collapse
Helius61 said:
Same for me - rooting (Germany DBT) according to your instructions didn't work
Gesendet von meinem kminilte mit Tapatalk
Click to expand...
Click to collapse
When you flash the SuperSU observe the log during the process, does it reboot by itself after posting this?
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
If it reboots after this, turn off your phone and boot into recovery, go to "Wipe" and wipe cache and dalvik. Immediately after that try to flash the SuperSU again, if successful it should post this:
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
and then some more lines, at the end it should say "Done!" and then give you the option to reboot. Remember if the flashing is successful you should reboot manually, if the phone reboots by itself then the flashing failed.
Note that I always recommend to start with a freshly installed firmware i.e. wipe the entire phone, flash new firmware, flash TWRP 3.0.0 and then flash SuperSU.
Thank you very much for your instant support. I'm currently traveling and I'll try your solutions once I'm back home again. Then, I'll provide an update whether it works or not.
kom-pakt said:
When you flash the SuperSU observe the log during the process, does it reboot by itself after posting this?
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
If it reboots after this, turn off your phone and boot into recovery, go to "Wipe" and wipe cache and dalvik. Immediately after that try to flash the SuperSU again, if successful it should post this:
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
and then some more lines, at the end it should say "Done!" and then give you the option to reboot. Remember if the flashing is successful you should reboot manually, if the phone reboots by itself then the flashing failed.
Note that I always recommend to start with a freshly installed firmware i.e. wipe the entire phone, flash new firmware, flash TWRP 3.0.0 and then flash SuperSU.
Click to expand...
Click to collapse
Wiped cache and dalvik, got the same lines you posted, rebooted, but root is still not working.
Tomislav3383 said:
Wiped cache and dalvik, got the same lines you posted, rebooted, but root is still not working.
Click to expand...
Click to collapse
Same for me
Does this root trigger the knox counter?
Hello, had the same problem . No root after reboot.
You need to use an older twrp.
With 2.8.1.0 it all works
i did it!
it works but you gotta have twrp 3.0.2-0 and then flash the zip file.
pop ups where blocked so i just changed it from always ask to always allow.
you gotta install twrp 3.0.0-0 and then flash the twrp 3.0.2-0 .img to recovery.
after that just flash the superSU zip and your done.
hope it works for you
Helius61 said:
Thank you very much for your instant support. I'm currently traveling and I'll try your solutions once I'm back home again. Then, I'll provide an update whether it works or not.
Click to expand...
Click to collapse
Glad I can help, also check out the other solutions posted in the meantime.
Dark_Horse said:
Does this root trigger the knox counter?
Click to expand...
Click to collapse
Yes.
Snowgay said:
Hello, had the same problem . No root after reboot.
You need to use an older twrp.
With 2.8.1.0 it all works
Click to expand...
Click to collapse
Zakipoophead27 said:
i did it!
it works but you gotta have twrp 3.0.2-0 and then flash the zip file.
pop ups where blocked so i just changed it from always ask to always allow.
you gotta install twrp 3.0.0-0 and then flash the twrp 3.0.2-0 .img to recovery.
after that just flash the superSU zip and your done.
hope it works for you
Click to expand...
Click to collapse
It seems that the culprit for the failed rooting were the different versions of TWRP you were using. I will add links to 2 versions of TWRP and a note about this in the main post.
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Scharnhorst1939 said:
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Click to expand...
Click to collapse
What version of twrp do you have?
Scharnhorst1939 said:
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Click to expand...
Click to collapse
I keep updating the first post with additional information and links, read it again and follow the instructions carefully without skipping any of the steps.
thanks for answer. Now it work with Version 2.8.0
Scharnhorst1939 said:
thanks for answer. Now it work with Version 2.8.0
Click to expand...
Click to collapse
Good to hear, version 3.0.2 works too and is more up to date.
Below you will find my procedure to root the SM-G532F/G532G/SM-G532M Galaxy J2 GRAND PRIME PLUS/ Mediatek MT6737T.
This will root your device with SR3-SuperSU-v2.79-SR3-20170114223742
This procedure may work for previous and future firmware releases or it may not, however it is intended for the firmware versions as posted below. If you encounter issues simply flash the stock boot image included with the download.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.
STATUS: Tested working
DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Instructions:
◘ 1. Download the respective files below:
For SM-G532F based on AQD1 firmware- root_and_boot_sm-g532f
For SM-G532G based on AQC4 firmware - root_and_boot_sm-g532g
For SM-G532M based on AQD2 firmware - SuperSU-v2.79-SR3_rooted_boot_sm-g532m_AQD2_31517
ODIN 3.12
SAMSUNG_USB_Driver_for_Mobile_Phones
◘ 2. Install the USB driver and ODIN to Windows.
◘ 3. Boot your device to DOWNLOAD mode then connect your USB cable.
◘ 4. Run ODIN and place either SuperSU-v2.79-SR3_rooted_boot_sm-g532f_AQD1.tar or SuperSU-v2.79-SR3_rooted_boot_sm-g532g_AQC4.tar or SuperSU-v2.79-SR3_rooted_boot_sm-g532m_AQD2_3151 as is in the AP slot. Don't change any options and hit START.
◘ 5. Wait for the device to flash and reboot.
◘ 6. Install the SuperSU apk from Play store and you should be rooted.
◘ 7. Have fun!
Credits: ME, @Chainfire and my tester @ShaDisNX255
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU
I wish I could try this out
I've got the M variant, but it's good to know a recognized contributor is somewhat interested in this device.
Keep up the good work!
ShaDisNX255 said:
I wish I could try this out
I've got the M variant, but it's good to know a recognized contributor is somewhat interested in this device.
Keep up the good work!
Click to expand...
Click to collapse
There isn't actually any difference between models except region, so it's likely any one of these boot images may work.
However I will look at the M variant also.
ashyx said:
There isn't actually any difference between models except region, so it's likely any one of these boot images may work.
However I will look at the M variant also.
Click to expand...
Click to collapse
I'd totally test it out if you include a file for the M variant.
I would flash newest firmware first, flash the file that you would upload and see if it works.
I am currently rooted on "G532MUMU1APIG" firmware.
I think the newest available firmware for me is "G532MUBU1AQA3"
ShaDisNX255 said:
I'd totally test it out if you include a file for the M variant.
I would flash newest firmware first, flash the file that you would upload and see if it works.
I am currently rooted on "G532MUMU1APIG" firmware.
I think the newest available firmware for me is "G532MUBU1AQA3"
Click to expand...
Click to collapse
AQD2 is the latest.
Leave it with me.
ashyx said:
AQD2 is the latest.
Leave it with me.
Click to expand...
Click to collapse
Aaaah yes, that is correct.
Sorry, I was looking at my carrier's specific firmware update (TCE G532MUBU1AQC1 is the last update they have sent out)
Count me in for testing
ShaDisNX255 said:
Aaaah yes, that is correct.
Sorry, I was looking at my carrier's specific firmware update (TCE G532MUBU1AQC1 is the last update they have sent out)
Count me in for testing
Click to expand...
Click to collapse
Follow the procedure above: https://www.androidfilehost.com/?fid=745425885120735954
NOTE: Not always required, but if your device is using encryption it may be be necessary to format the /data partiton AFTER flashing the boot image for the device to boot.
.
ashyx said:
Follow the procedure above: https://www.androidfilehost.com/?fid=745425885120735954
NOTE: Not always required, but if your device is using encryption it may be be necessary to format the /data partiton AFTER flashing the boot image for the device to boot.
.
Click to expand...
Click to collapse
I'm fully backing up and will proceed to test this root method.
I will be back in a few minutes
---------- Post added at 06:22 PM ---------- Previous post was at 05:37 PM ----------
After installing SuperSU apk from the play store, I open it up (expecting to get something regarding updating binary) but instead I get a message: SuperSU Binary occupied
I'm guessing this means I am not rooted?
ShaDisNX255 said:
I'm fully backing up and will proceed to test this root method.
I will be back in a few minutes
---------- Post added at 06:22 PM ---------- Previous post was at 05:37 PM ----------
After installing SuperSU apk from the play store, I open it up (expecting to get something regarding updating binary) but instead I get a message: SuperSU Binary occupied
I'm guessing this means I am not rooted?
Click to expand...
Click to collapse
Are you using magisk or some other root application?
I also suggest to install V2.79 apk as the latest Supersu updates are having issues.
http://www.apkmirror.com/apk/coding...79-release/supersu-2-79-android-apk-download/
ashyx said:
Are you using magisk or some other root application?
I also suggest to install V2.79 apk as the latest Supersu updates are having issues.
http://www.apkmirror.com/apk/coding...79-release/supersu-2-79-android-apk-download/
Click to expand...
Click to collapse
Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.
---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------
ShaDisNX255 said:
Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.
Click to expand...
Click to collapse
Also, this seems to have broken my IMEI. I got IMEI unknown
ShaDisNX255 said:
Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.
---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------
Also, this seems to have broken my IMEI. I got IMEI unknown
Click to expand...
Click to collapse
The problem is once the bad version has been installed it doesn't automatically get removed by rolling back and the binary won't update, but you should still have root.
All this has been documented in the supersu beta thread.
https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
To start afresh delete su.img from /data then just reboot or wipe the /data partition in recovery.
Regarding the IMEI issue. This is related to a kernel/firmware mismatch.
You should be running the AQD2 firmware.
Which firmware are you currently running?
Not work for my phone
Everybody help me please
AlexEvans6 said:
Not work for my phone
Everybody help me please
Click to expand...
Click to collapse
What does that actually mean?
ashyx said:
The problem is once the bad version has been installed it doesn't automatically get removed by rolling back and the binary won't update, but you should still have root.
All this has been documented in the supersu beta thread.
https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
To start afresh delete su.img from /data then just reboot or wipe the /data partition in recovery.
Regarding the IMEI issue. This is related to a kernel/firmware mismatch.
You should be running the AQD2 firmware.
Which firmware are you currently running?
Click to expand...
Click to collapse
I am running (or was) AQA3 since that is the firmware I have downloaded to my computer at the moment. I am trying to download the firmware from samsung-firmware (AQD2) but it seems my download keeps getting cancelled and sammobile doesn't have AQD2 yet.
Went ahead and took it a step forward and re-flashed stock AQA3 via Odin, set it up again and flashed your file and same thing happened. It asked me to update binary, tried updating binary and states that it fails, not before, once again, requesting me to remove Knox.
I will once again try to download AQD2 firmware but I don't think it would make much a difference (or it could, you never know)
Tried it also with the APIG firmware I have that I originally rooted with and asked me for a password after booting your file even with OEM unlocking turned on.
ShaDisNX255 said:
I am running (or was) AQA3 since that is the firmware I have downloaded to my computer at the moment. I am trying to download the firmware from samsung-firmware (AQD2) but it seems my download keeps getting cancelled and sammobile doesn't have AQD2 yet.
Went ahead and took it a step forward and re-flashed stock AQA3 via Odin, set it up again and flashed your file and same thing happened. It asked me to update binary, tried updating binary and states that it fails, not before, once again, requesting me to remove Knox.
I will once again try to download AQD2 firmware but I don't think it would make much a difference (or it could, you never know)
Tried it also with the APIG firmware I have that I originally rooted with and asked me for a password after booting your file even with OEM unlocking turned on.
Click to expand...
Click to collapse
Is your data partition using encryption?
Im also a little confused regarding the binary update. It doesn't usually ask to disable Knox unless you have root.
Do you have root irrespective of updating the binary or not?
ashyx said:
Is your data partition using encryption?
Im also a little confused regarding the binary update. It doesn't usually ask to disable Knox unless you have root.
Do you have root irrespective of updating the binary or not?
Click to expand...
Click to collapse
I am not sure about how to answer both questions as I'm not sure how to check if the data partition is using encryption or I do not know what exactly do you mean if I have root irrespective?
ShaDisNX255 said:
I am not sure about how to answer both questions as I'm not sure how to check if the data partition is using encryption or I do not know what exactly do you mean if I have root irrespective?
Click to expand...
Click to collapse
OK what I mean is, regardless of whether the binary updates or not do you have root?
Do any root checkers or apps gain root privileges?
Unless you've disabled it then it is highly likely your device is encrypted. Encryption causes all sorts of issues with root.
It can be removed by wiping data in recovery but this will wipe everything on internal storage.
ashyx said:
OK what I mean is, regardless of whether the binary updates or not do you have root?
Do any root checkers or apps gain root privileges?
Unless you've disabled it then it is highly likely your device is encrypted. Encryption causes all sorts of issues with root.
It can be removed by wiping data in recovery but this will wipe everything on internal storage.
Click to expand...
Click to collapse
By wiping everything on the internal storage, you mean everything including media and such, correct?
I always thought that wiping the /data partition only meant everything related to the operating system, not the actual "internal" sd card, though in this phone's case I think they're one in the same.
This phone doesn't have a custom recovery and flashing the firmware I have (AQA3) for some reason has no recovery at all!
Anyway, yeah I tried a root checking app and it didn't detect root.
I will try once again with a root checker app and flashfire to see if either detects root with SuperSU 2.79 and without updating binaries and then try them again after I've tried to update binaries and failing.
My AQD2 download keeps getting interrupted again and again, do you know any other reliable source to download it beside samsung-firmware?
Let me give it a try and I'll give you a heads up.
BTW, how can I disable encryption?
ShaDisNX255 said:
By wiping everything on the internal storage, you mean everything including media and such, correct?
I always thought that wiping the /data partition only meant everything related to the operating system, not the actual "internal" sd card, though in this phone's case I think they're one in the same.
This phone doesn't have a custom recovery and flashing the firmware I have (AQA3) for some reason has no recovery at all!
Anyway, yeah I tried a root checking app and it didn't detect root.
I will try once again with a root checker app and flashfire to see if either detects root with SuperSU 2.79 and without updating binaries and then try them again after I've tried to update binaries and failing.
My AQD2 download keeps getting interrupted again and again, do you know any other reliable source to download it beside samsung-firmware?
Let me give it a try and I'll give you a heads up.
BTW, how can I disable encryption?
Click to expand...
Click to collapse
Data is the internal storage. It's separate from the system partition where the OS resides. Wiping data basically makes your device factory fresh as it wipes all user apps, settings and media.
In stock recovery it's labelled factory reset.
Every firmware has a recovery even the one you mentioned or your device just wouldn't boot.
If root apps are reporting not rooted then there is an issue somewhere. Quite likely it's encryption on the data partition that's causing the issue.
To remove encryption it is required to wipe data in recovery after flashing the boot image.
If it still doesn't work without encryption then I'm a little unsure of what the issue is as this procedure works just fine on Snapdragon and Exynos devices. It may be some kind of mediatek weirdness.
In any case I have an alternative method which should work, but involves an extra step.
At some point I will be looking at compiling twrp for this device, but I'd like to work out this root issue first.
For fast downloads go to updato.com
ashyx said:
What does that actually mean?
Click to expand...
Click to collapse
Idk help me please
Software info:
Android 8.1
Samsung Experience: 9.5
Security patch level: Aug 2018
No Treble
Build version: J727PVPU4BRH5 or J727PVPS6BSK1 for SM-J727P
Build version: J727VVRU2BRH1 for SM-J727V
Build version: J727VPPVRU2BRH1 for SM-J727VPP
Build version: J727AUCU3BRH2 for SM-J727A
Build version: J727R4TYU1BRH5 for SM-J727R4
Build version: J727TUVU3BRH3 for SM-J727T
Build version: J727T1UVU3BRH3 for SM-J727T1
I have only tested magisks on SM-J727P, When you flash it you need to format your data again and then manually patch via the magisks manager then it will work properly.
SM-J727P (Galaxy J7 Perx)
J727PVPS6BSK1 (Newer)
Full rom download:
https://www.androidfilehost.com/?fid=8889791610682942431
J727PVPU4BRH5 (Older)
Full rom download:
https://www.androidfilehost.com/?fid=1322778262904004250
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904004263
SM-J727V (Galaxy J7 V)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904007457
SM-J727VPP (Galaxy J7 V Prepaid)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904007456
SM-J727A (Galaxy J7 2017 AT&T)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904007526
SM-J727R4 (Galaxy J7 2017 US Cellular)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904007527
SM-J727T (Galaxy J7 2017 T-Mobile)
full rom download:
https://www.androidfilehost.com/?fid=1322778262904011167
SM-J727T1 (Galaxy J7 2017 MetroPCS)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904011170
Credits: @dbreed53 for the newer J727PVPU4BSK1 firmware
this can be ported to others J7? ?
J727P update
deadman96385 said:
I have gotten the 2 available firmware packages from easy firmware, One is a full rom package and the other is a traditional 4 file package. I have uploaded both but have only tested the full rom package.
Software info:
Android 8.1
Samsung Experience: 9.5
Security patch level: Aug 2018
No Treble
Build date: Aug 23rd
I have tested magisks, When you flash it you need to format your data again and then manually patch via the magisks manager then it will work properly.
Full rom download:
https://www.androidfilehost.com/?fid=1322778262904004250
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904004263
Click to expand...
Click to collapse
can you add in a how to Root 8.1.0 for this phone for all of us ! Thank you !!
Hi,
Is there Rom also for SM -G610F .
Magisk
So I flashed it and everything is working fantastic but I still can't get root. I don't have twrp anymore and can't flash twrp over again Odin keeps say fail so how would I format data?? Sorry I'm a noob...
J727P
Shaddow313 said:
So I flashed it and everything is working fantastic but I still can't get root. I don't have twrp anymore and can't flash twrp over again Odin keeps say fail so how would I format data?? Sorry I'm a noob...
Click to expand...
Click to collapse
Use the stock recovery an do a factory reset then flash twrp !
??
peter couniaz said:
Use the stock recovery an do a factory reset then flash twrp !
Click to expand...
Click to collapse
thanks for your quick reply.
So I tried started from scratch I re-flashed the 8.1 rom file, then went in to stock recovery performed data factory reset, tried to flash twrp 3.2.1-1 using odin 3.13.1 said it work but I'm still stuck with stock recovery. So I tried flashing twrp once more and odin says operation failed...
peter couniaz said:
Use the stock recovery an do a factory reset then flash twrp !
Click to expand...
Click to collapse
Wjat is meant by recovery? Is it not flashing factory rom?
Now, I don't think I understand TWRP fully, What it does. Is it used to fix root or system problems?
Thanks
---------- Post added at 11:22 PM ---------- Previous post was at 11:00 PM ----------
peter couniaz said:
Use the stock recovery an do a factory reset then flash twrp !
Click to expand...
Click to collapse
If I flash this update, will I be able to activate the phone, I am outside Sprint and legacy carrier's network. I'm in Africa.
My phone is unusable right now, I flashed August nougat update, I couldn't go past activation screen
Help please
Added AT&T, Verizon, Verizon Prepaid, US Cellular 8.1 firmwares to OP
J727P update
deadman96385 said:
Added AT&T, Verizon, Verizon Prepaid, US Cellular 8.1 firmwares to OP
Click to expand...
Click to collapse
Ok this is what worked for me to get Root !
#1 go into stock recovery data factory reset the phone pull battery !
#2 boot download mod using Odin 3.13.1 install latest twrp make shore before flashing twrp to unlock auto reboot in odin options then flash twrp pull battery again !
#3 boot into twrp wipe data in advanced options then mount system an flash magisk 17.1 zip wipe data again an boot phone setup phone an install magisk manager open manager in popup click yes it run threw an go away after that when ever you open magisk manager the popup will there an just click no thanks ! You should have no reason to open again it should just keep granting your root app access ! Hope this works for you all !!
A note about root; Magisk 17.1 will sometimes lose root. If this happens simply reflash magisk and reboot. The devs are working on it. We aren't the only one's with this problem. There is now a magisk 17.2 canary build which is in testing to bring better support for Oreo/Pie. I've tried it and had very good success so far.
Amazing!!
peter couniaz said:
Ok this is what worked for me to get Root !
#1 go into stock recovery data factory reset the phone pull battery !
#2 boot download mod using Odin 3.13.1 install latest twrp make shore before flashing twrp to unlock auto reboot in odin options then flash twrp pull battery again !
#3 boot into twrp wipe data in advanced options then mount system an flash magisk 17.1 zip wipe data again an boot phone setup phone an install magisk manager open manager in popup click yes it run threw an go away after that when ever you open magisk manager the popup will there an just click no thanks ! You should have no reason to open again it should just keep granting your root app access ! Hope this works for you all !!
Click to expand...
Click to collapse
You sir, are awesome another successful root...
I just have a question on twrp I flashed TWRP 3.2.2-0 because I couldn't get TWRP 3.2.3-0 to work for some reason. But now if I try and make a Back-up, my Data partition is empty and won't successfully back-up.. I can't figure out what I'm doing wrong I formatted Data and flashed no-dm-verity still no luck. Any idea's??
J727P
Shaddow313 said:
You sir, are awesome another successful root...
I just have a question on twrp I flashed TWRP 3.2.2-0 because I couldn't get TWRP 3.2.3-0 to work for some reason. But now if I try and make a Back-up, my Data partition is empty and won't successfully back-up.. I can't figure out what I'm doing wrong I formatted Data and flashed no-dm-verity still no luck. Any idea's??
Click to expand...
Click to collapse
Yes I know we are still having a problem with twrp even twrp 3.2.3.0 ! PS they should be fixing soon with the next update of twrp !
Shaddow313 said:
You sir, are awesome another successful root...
I just have a question on twrp I flashed TWRP 3.2.2-0 because I couldn't get TWRP 3.2.3-0 to work for some reason. But now if I try and make a Back-up, my Data partition is empty and won't successfully back-up.. I can't figure out what I'm doing wrong I formatted Data and flashed no-dm-verity still no luck. Any idea's??
Click to expand...
Click to collapse
Currently TWRP lacks quota storage support, so it can't read the Oreo /data partition. You can remove quota storage from the fstab by using the patch found here. After flashing it TWRP will be able to mount the data partition. There are some downsides though. Disabling quota storage is slightly slower than having it on. And TWRP still won't be able to make/restore a backup unless the partition is less than 649mb in size. There were changes to the bootloader in Oreo that prevents making a backup. You'll reboot midway. TWRP 3.2.3-1 should fix this when it gets released.
J727P update
Spaceminer said:
Currently TWRP lacks quota storage support, so it can't read the Oreo /data partition. You can remove quota storage from the fstab by using the patch found here. After flashing it TWRP will be able to mount the data partition. There are some downsides though. Disabling quota storage is slightly slower than having it on. And TWRP still won't be able to make/restore a backup unless the partition is less than 649mb in size. There were changes to the bootloader in Oreo that prevents making a backup. You'll reboot midway. TWRP 3.2.3-1 should fix this when it gets released.
Click to expand...
Click to collapse
Ok has anyone tried flash empire tweaks zip V1.3 on to the 8.1.0 system yet ? Using current twrp build ?
I'll be adding T-mobile and MetroPCS firmware to op hopefully tonight
J727P update
deadman96385 said:
I'll be adding T-mobile and MetroPCS firmware to op hopefully tonight
Click to expand...
Click to collapse
Can you post the firmware for Virgin mobile an Boost ? Thank you !!
peter couniaz said:
Can you post the firmware for Virgin mobile an Boost ? Thank you !!
Click to expand...
Click to collapse
They are included in the sprint firmware
J727P update
deadman96385 said:
They are included in the sprint firmware
Click to expand...
Click to collapse
Ok thank you wasn't shore about that !
peter couniaz said:
Ok this is what worked for me to get Root !
#1 go into stock recovery data factory reset the phone pull battery !
#2 boot download mod using Odin 3.13.1 install latest twrp make shore before flashing twrp to unlock auto reboot in odin options then flash twrp pull battery again !
#3 boot into twrp wipe data in advanced options then mount system an flash magisk 17.1 zip wipe data again an boot phone setup phone an install magisk manager open manager in popup click yes it run threw an go away after that when ever you open magisk manager the popup will there an just click no thanks ! You should have no reason to open again it should just keep granting your root app access ! Hope this works for you all !!
Click to expand...
Click to collapse
Did this work on the usc variant or....
Hi!
I had Magisk v23 working fine with Magisk hide but then I upgraded to v24. Magisk app successfully installed and shows Magisk not present. And when I try to DirectInstall Magisk, I get verification failed error. Attached both screenshots.
Now, I have installed and confirm TWRP is working but do not know how to make Magisk working again and it seems it gonna be a wipe. Any help appreciated.
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html
Issue is that on my other phone, Sony Xperia XZ Premium G8142, the same in-app upgrade weas successful with out any issues. I lost Magisk Hide but an extension recovered that function. But it all went haywire on this S8
xabu said:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
This guide expects me to know what ROM I have. Thing is, I do not know what my device really is. It's running a ROM that I do not recognize (My post: https://forum.xda-developers.com/t/...l-and-odin-cannot-flash.4372669/post-86069051). I do not have the sources for it so I cannot acquire the required two files. Ramdisk is Yes as per my screenshot but I cannot follow the rest of the guide without the files.
try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .
xabu said:
try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .
Click to expand...
Click to collapse
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!
Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Maybe only European ?
xabu said:
Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!
Click to expand...
Click to collapse
I just TWRP it. It went smoothly. I love a new ROM but need to know what device is it.
Download mode say it is SM-G950N
Android say it is SM-950FD
Both SIM slots have the same IMEI number. This part is beyond my understanding.
I have Odin and know the basics. Just need to find a ROM I can go for: What official I should flash first and what custom. Any recommendation?
As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.
xabu said:
Maybe only European ?
Click to expand...
Click to collapse
Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Just found out:The "famous" secret codes only work on stock based ROMs ¯\_( ͡❛ ͜ʖ ͡❛)_/¯
xabu said:
As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.
Click to expand...
Click to collapse
I have been trying to make the total backup but I do not see any boot.img:
And I do not see the file in the Device/TWRP/Backups:
Again, I must be missing something obvious. And as per the Magisk guide, I need the boot.img
magisk 24 is ****, it's bricking MediaTek powered Samsung phones
Boot.img from TWRP backup
In clockworkmod kernel and recovery are backed up as IMGs. But in TWRP it is boot.emmc.win Anybody know how to convert jt to boot.img? Help will be really appereciated. Sent from my HTC One X using xda app-developers app
forum.xda-developers.com
I must tell you that my custom rom for the s7 gives me the boot.img as the first file as soon as i open the zip.
the boot.img can also be reached by downloading the right stock rom for your phone. In that case it is the best practice to patch the whole
AP file by using Magisk.