Develop Bugs

How to Root Galaxy S6 Edge Tmobile on Android Marshmallow

So as we know Tmobile just Rolls out latest android Marshmallow update here is a complete tested method to get root on your device.
1: Download and flash TWRP from Link Below and flash it via Odin AP
2: Then download SuperSU beta 2.71 ZIp file from the link below
3: Transfer the SuperSU zip file above to your device’s storage.
4: Boot your device into TWRP recovery.
5: Tap on “Install” and select the SuperSU zip file that you transferred to your device in Step 1.
6: After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the flashing process.
7: Once SuperSU is flashed, you’ll get “Reboot System” option, select it.
Congratulations! Your device should be rooted now. Look for the SuperSU app in app drawer.
Link to Download TWRP: http://arter97.com/browse/S6/kernel/13.1/g925fi/arter97-recovery-g925fi-13.1-twrp_3.0.2-0.tar.md5
Link to Download SupeSU: https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
In Case of Any Problem drop down you comments below

You didn't mention OEM unlock?
Shouldn't that be on?
Pp.
Sent from my stone stock S6E using teleconetik impulses.

PanchoPlanet said:
You didn't mention OEM unlock?
Shouldn't that be on?
Pp.
Sent from my stone stock S6E using teleconetik impulses.
Click to expand...
Click to collapse
OEM unlock should be checked on in developer mode.

Any bugs?

TheErroristt said:
So as we know Tmobile just Rolls out latest android Marshmallow update here is a complete tested method to get root on your device.
1: Download and flash TWRP from Link Below and flash it via Odin AP
2: Then download SuperSU beta 2.68 ZIp file from the link below
3: Transfer the SuperSU zip file above to your device’s storage.
4: Boot your device into TWRP recovery.
5: Tap on “Install” and select the SuperSU zip file that you transferred to your device in Step 1.
6: After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the flashing process.
7: Once SuperSU is flashed, you’ll get “Reboot System” option, select it.
Congratulations! Your device should be rooted now. Look for the SuperSU app in app drawer.
Link to Download TWRP: dl.twrp.me/zeroltetmo/twrp-3.0.2-0-zeroltetmo.img.tar.html or arter97.com/browse/S6/kernel/....0.2-0.tar.md5
Link to Download SupeSU: downloadmirror.co/android/1iLL/BETA-SuperSU-v2.68-20160228150503.zip
In Case of Any Problem drop down you comments below
Please Put HTTP before links as XDA do not allow me to put outside link because I am new here. or just copy paste the links into address bar it will work too..
Click to expand...
Click to collapse
Does in call audio work?

aswintorch said:
Does in call audio work?
Click to expand...
Click to collapse
Yes In Call audio works perfect. No bugs at all..

alex007600 said:
Any bugs?
Click to expand...
Click to collapse
No bugs at all

Recovery does not start :S

same here. Odin says Succeed but still stock recovery.

alex007600 said:
Recovery does not start :S
Click to expand...
Click to collapse
Some manufacturers will restore stock recovery if you reboot device after you Odin a custom recovery.
Try Odin > (uncheck "reboot") TWRP
then vol down + home + power when screen goes black, keep holding power and home button but slide your finger to volume up. It should boot into TWRP

bad_HABIT said:
Some manufacturers will restore stock recovery if you reboot device after you Odin a custom recovery.
Try Odin > (uncheck "reboot") TWRP
then vol down + home + power when screen goes black, keep holding power and home button but slide your finger to volume up. It should boot into TWRP
Click to expand...
Click to collapse
Still not work

alex007600 said:
Recovery does not start :S
Click to expand...
Click to collapse
http://arter97.com/browse/S6/kernel/13.1/g925fi/arter97-recovery-g925fi-13.1-twrp_3.0.2-0.tar.md5
Download from this link and flash via Odin it will solve the problem.

cfcryme said:
same here. Odin says Succeed but still stock recovery.
Click to expand...
Click to collapse
http://arter97.com/browse/S6/kernel/13.1/g925fi/arter97-recovery-g925fi-13.1-twrp_3.0.2-0.tar.md5
Download this file and flash via odin Tested... I will replace the Link now as the official TWRP link have some patch problem..

alex007600 said:
Recovery does not start :S
Click to expand...
Click to collapse
If you will still face any issue do let me know.

alex007600 said:
Recovery does not start :S
Click to expand...
Click to collapse
TheErroristt said:
If you will still face any issue do let me know.
Click to expand...
Click to collapse
same thing. What Odin version are u using?

cfcryme said:
same thing. What Odin version are u using?
Click to expand...
Click to collapse
Have you downloaded the arter version of twrp?? With the link i provided later?
Sent from my SM-G925T using XDA-Developers mobile app

TheErroristt said:
Have you downloaded the arter version of twrp?? With the link i provided later?
Sent from my SM-G925T using XDA-Developers mobile app
Click to expand...
Click to collapse
Good new here: I can boot to custom recovery now

cfcryme said:
Good new here: I can boot to custom recovery now
Click to expand...
Click to collapse
Good to go. Now just install SuperSu via twrp and you are done with rooting..
Sent from my SM-G925T using XDA-Developers mobile app

I was able to enter recovery but when I choose to rw (all access I supposed to) it brings me bootloop, now Im repairing with Smart Switch all my stuff gonna be deleted

alex007600 said:
I was able to enter recovery but when I choose to rw (all access I supposed to) it brings me bootloop, now Im repairing with Smart Switch all my stuff gonna be deleted
Click to expand...
Click to collapse
You should have put SuperSu before into your device storage, allow modification when twrp ask you to and then install SuperSu. Installing SuperSu will take you out of the bootloop. Installing only twrp and allowing modifications always gets you to bootloop until you install SuperSu.
Sent from my SM-G925T using XDA-Developers mobile app

[RECOVERY][Official] TWRP 3.4.0-6 [T83x][mtp][otg]

TWRP 3.4 for Android 10 SM-T83x
This build of TWRP is now Official.
Official TWRP web link
Built using OMNI source
TWRP v3.4
See post #2 for install steps
Changelog...
1.0
Initial build
MTP, OTG and SDcard all working
4.0
Now in portrait mode
Brightness fixed
5.0
Updated for Android 10
TWRP Downloads
Download folder
Official device tree on twrp.me
--------------------->
Kernel Source
Source
Device Tree
Source
--------------------->
Beer fund

You can flash TWRP two ways, either directly from an existing TWRP install, using the linked TWRP.img file. Or you can flash using Odin and the TWRP.tar file.
You will need a custom kernel with dm-verity disabled to be able to boot up afterwards. You will also need to disable encryption and format data to be able to read from the sdcard (encryption isn't supported).
The flashing process is as follows.
Get yourself onto stock Pie firmware, using Odin to flash the complete package. Before proceeding. Boot up and make sure you have OEM unlock switch and its activated.
1. Boot into Download mode and Flash TWRP (Download) using Odin (use AP)
2. Immediately boot into TWRP after flashing takes place, hold vol up and power.
3. Format data partition (wipe/format data)
4. Reboot recovery
5. Copy WETA Kernel + Encryption disabler + Magisk zip to device. - (Download Kernel - Encryption disabler)
6. Flash WETA Kernel + Encrypt disabler + Magisk zip.
7. Boot up system, if it hangs on Samsung logo after 3min perform hard reboot.
8. Connect to internet and go to dev settings and check oem unlock is present before any rebooting.
** Custom kernel is universal for all bootloader v4 firmware.
--->

problem download
From croatia I cannot access this link. Can you upload on mega.
Thanks

macakfelix said:
From croatia I cannot access this link. Can you upload on mega.
Thanks
Click to expand...
Click to collapse
Your kidding? Usually people say upload anywhere but mega because of access.. haha. But sure. I'll mirror it to mega
Sent from my SM-N9600 using Tapatalk

macakfelix said:
From croatia I cannot access this link. Can you upload on mega.
Thanks
Click to expand...
Click to collapse
Mega mirrors are up,
Sent from my SM-N9600 using Tapatalk

Tested and working on T835 Pie. Finally good to have a TWRP with MTP & adb working. Thanks mate.

Mentalmuso said:
TWRP 3.3.0 for PIE SM-T83x
--------------------->
Beer fund
Click to expand...
Click to collapse
Hi friend, i flashed with odin but seems not to work, same as without flashing... im on pie now, but when on oreo was not so easy to flash twrp as this... i remember had to flash 1 or 2 more files, but not sure... any help?
EDIT im talking about TabS4_oreo_forced_encryption_disabler... do you get it work just flashing twrp or do you need any extra procedure?
Thanks in advance
My device is a SM-T835N

wallyhenderson said:
Hi friend, i flashed with odin but seems not to work, same as without flashing... im on pie now, but when on oreo was not so easy to flash twrp as this... i remember had to flash 1 or 2 more files, but not sure... any help?
EDIT im talking about TabS4_oreo_forced_encryption_disabler... do you get it work just flashing twrp or do you need any extra procedure?
Thanks in advance
My device is a SM-T835N
Click to expand...
Click to collapse
Sorry, I completely forgot that
Flash TWRP with Odin
Reboot straight to twrp.
Flash encryption disabler.
Format data.
Reboot recovery.
Mount data make sure you can read it .
Then you can flash a rom, kernel etc. I'll update the op in a bit
Sent from my SM-N9600 using Tapatalk

macakfelix said:
From croatia I cannot access this link. Can you upload on mega.
Thanks
Click to expand...
Click to collapse
https://mega.nz/#F!TZNgRYyB!7wa-W3moNILsezgkuj3nKA

Mentalmuso said:
Sorry, I completely forgot that
Flash TWRP with Odin
Reboot straight to twrp.
Flash encryption disabler.
Format data.
Reboot recovery.
Mount data make sure you can read it .
Then you can flash a rom, kernel etc. I'll update the op in a bit
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
Friend i have
Flash "TWRP-ODIN_Pie_3.3.0_sm-t83x_mentalmuso.tar" with Odin OK
Reboot straight to twrp OK
Flash encryption disabler "T83x_PIE_encrypt_disabler_+++.zip" OK
Format data OK
Reboot recovery OK
Mount data make sure you can read it OK (think ok, didnt know what to do)
And now im in a loop boot... can you help me i use phone to work and sadly will have to solve today or have to flash stock pie rom
Thanks in advance
Restored stock pie rom... seems to work fine without twrp but when trying to flash TWRP-ODIN_Pie_3.3.0_sm-t83x_mentalmuso and it says "only official released binaries allowed to be flashed (recovery)

wallyhenderson said:
Friend i have
Flash "TWRP-ODIN_Pie_3.3.0_sm-t83x_mentalmuso.tar" with Odin OK
Reboot straight to twrp OK
Flash encryption disabler "T83x_PIE_encrypt_disabler_+++.zip" OK
Format data OK
Reboot recovery OK
Mount data make sure you can read it OK (think ok, didnt know what to do)
And now im in a loop boot... can you help me i use phone to work and sadly will have to solve today or have to flash stock pie rom
Thanks in advance
Click to expand...
Click to collapse
What version of Android are you on?
Sent from my SM-N9600 using Tapatalk

wallyhenderson said:
Friend i have
Flash "TWRP-ODIN_Pie_3.3.0_sm-t83x_mentalmuso.tar" with Odin OK
Reboot straight to twrp OK
Flash encryption disabler "T83x_PIE_encrypt_disabler_+++.zip" OK
Format data OK
Reboot recovery OK
Mount data make sure you can read it OK (think ok, didnt know what to do)
And now im in a loop boot... can you help me i use phone to work and sadly will have to solve today or have to flash stock pie rom
Thanks in advance
Click to expand...
Click to collapse
Have you flashed a custom kernel? Or at least flashed magisk?
You cant boot using a stock kernel, when you have any other custom features on your device.
Sent from my SM-N9600 using Tapatalk

Mentalmuso said:
Have you flashed a custom kernel? Or at least flashed magisk?
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
it is mandatory to flash a custom kernel? will do if nessesary... i didnt... and didnt flashed magisk
---------- Post added at 11:05 PM ---------- Previous post was at 10:57 PM ----------
Mentalmuso said:
What version of Android are you on?
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
im on pie T835NKOU2BSD1

wallyhenderson said:
it is mandatory to flash a custom kernel? will do if nessesary... i didnt... and didnt flashed magisk
---------- Post added at 11:05 PM ---------- Previous post was at 10:57 PM ----------
im on pie T835NKOU2BSD1
Click to expand...
Click to collapse
Kernel - pre rooted should boot. https://nextcloud.justbeca.us/s/JMgdcpt6kxdwNzo
Sent from my SM-T830 using Tapatalk

What are the steps for flashing the twrp 3.3.0 img via an existing twrp install?

hpc305 said:
What are the steps for flashing the twrp 3.3.0 img via an existing twrp install?
Click to expand...
Click to collapse
install - img - select the img file - select recovery
Sent from my SM-N9600 using Tapatalk

Encryption Disabler was broken
Updated to V2, please use this or there will be problems.
See post #2 for downloads.
--->

Mentalmuso said:
You can flash TWRP two ways, either directly from an existing TWRP install, using the linked TWRP.img file. Or you can flash using Odin and the TWRP.tar file.
You will need a custom kernel with dm-verity disabled to be able to boot up afterwards. You will also need to disable encryption and format data to be able to read from the sdcard (encryption isn't supported).
The flashing process is as follows.
Get yourself onto stock Pie firmware, using Odin to flash the complete package. Before proceeding. Boot up and make sure you have OEM unlock switch and its activated.
1. Boot into Download mode and Flash TWRP (Download) using Odin
2. Immediately boot into TWRP after flashing takes place, hold vol up and power.
3. Format data partition (wipe/format data)
4. Reboot recovery
5. Copy Encryption disabler and WETA_Kernel or WETA_Rom to device - (Download Enryption disabler) (Download WETA_Kernel)
6. Flash Encryption disabler, Flash WETA_Kernel or WETA_Rom
7. Boot up system, if it hangs on Samsung logo after 3min perform hard reboot.
8. Connect to internet and go to dev settings and cheeck oem unlock is present before any rebooting.
**Custom kernel is pre-rooted with magisk.
**You will need to manually install magisk manager app.
--->
Click to expand...
Click to collapse
Some things to note:
0. Requirements are:
USB Cable (Samsung Tab S4 default cable recommended)
A computer where Odin works (ie. my AM4 X370 Ryzen 7 system did not work, maybe some driver issue?)
Best is to put encryption disabler & Kernel onto the micro SD card in the Tab S4 already, you can flash from SD card in TWRP!
1. Flash TWRP in AP slot - beware if you did not untick Auto Reboot, it will immediately restart and you miss 2.
2. Hold those buttons before the vibration kicks in, otherwise you are too late
4. I couldn't do that from TWRP itself for some reason (it just shut off), but button combo worked perfectly
5. [Edit] Do that before hand, I recommend the micro SD card you can put into the Tab S4
6. I flashed encryption disabler (V2) first, then you have to flash the kernel image, flash it to BOOT!
7. Don't just wait 3 min, my Tablet booted after 10 min without issue! I had this before aswell, you just need to give it more time!
Question: Can I update Magisk with this?

neuer31 said:
Some things to note:
0. Requirements are:
USB Cable (Samsung Tab S4 default cable recommended)
A computer where Odin works (ie. my AM4 X370 Ryzen 7 system did not work, maybe some driver issue?)
Best is to put encryption disabler & Kernel onto the micro SD card in the Tab S4 already, you can flash from SD card in TWRP!
1. Flash TWRP in AP slot - beware if you did not untick Auto Reboot, it will immediately restart and you miss 2.
2. Hold those buttons before the vibration kicks in, otherwise you are too late
4. I couldn't do that from TWRP itself for some reason (it just shut off), but button combo worked perfectly
6. I flashed encryption disabler (V2) first, then you have to flash the kernel image, flash it to BOOT!
7. Don't just wait 3 min, my Tablet booted after 10 min without issue! I had this before aswell, you just need to give it more time!
Question: Can I update Magisk with this?
Click to expand...
Click to collapse
Yeah flashing magisk should be fine once your data partition is unencrypted.
Sent from my SM-N9600 using Tapatalk

Mentalmuso said:
install - img - select the img file - select recovery
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
F###, thanks, bro.
Just flashed it as recovery and have this now.
Can you delete this suggestion? It should be flashed as Boot, GOD!

Pre-rooted Boot Image OP7T Global HD65AA 10.0.6

Hello,
I have seen few requests about providing pre-rooted boot image file for OP7T Global (not Indian or European) version for firmware 10.0.6 so here you go.
Steps :
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
Also attaching the stock boot file in case anything goes wrong.
P.S : I don't own Global OP7T.
Link : https://androidfilehost.com/?w=files&flid=302500

has anyone tried this one yet?

xrelic7 said:
has anyone tried this one yet?
Click to expand...
Click to collapse
I would if I could update to the Global rom. Local update fails on rooted Indian 10.0.6. Anyone can advise me on this?

damn i want to do it but i am afraid some of my apps will stop working cause idk if magiskhide will work at current time

xrelic7 said:
has anyone tried this one yet?
Click to expand...
Click to collapse
Yes, I tried on my 7t and it booted successfully!Thanks OP's work!!! By the way , I also flash Blu kernel via fk app and it also worked fine. But I don't test any magisk mondule.

23333 said:
Yes, I tried on my 7t and it booted successfully!Thanks OP's work!!! By the way , I also flash Blu kernel via fk app and it also worked fine. But I don't test any magisk mondule.
Click to expand...
Click to collapse
ty for the reply i might grow a few and give it a shot hopefully magiskhide is working so certain apps cant detect that i am rooted

I tried the method above it booted the first time without problems however when i installed magisk canary and tried it did not have the option to direct install idk if i did something wrong not sure

xrelic7 said:
I tried the method above it booted the first time without problems however when i installed magisk canary and tried it did not have the option to direct install idk if i did something wrong not sure
Click to expand...
Click to collapse
Are you using Global or Indian HD65AA ? Not getting an option to directly install means somehow the patched image did not boot and the original imaged booted.

imakul8 said:
I would if I could update to the Global rom. Local update fails on rooted Indian 10.0.6. Anyone can advise me on this?
Click to expand...
Click to collapse
You need to download the global 10.0.6 OTA not fastboot image in order to do the local update.

zeusofyork said:
You need to download the global 10.0.6 OTA not fastboot image in order to do the local update.
Click to expand...
Click to collapse
Yes, that's what I have.

1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
---------- Post added at 02:02 AM ---------- Previous post was at 01:18 AM ----------
ricksrod said:
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
Click to expand...
Click to collapse
When you run step 2, it boots the phone. Step 3 says to reboot. Not sure if that is correct? Rebooting would just boot to the stock boot image again?

ricksrod said:
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
---------- Post added at 02:02 AM ---------- Previous post was at 01:18 AM ----------
When you run step 2, it boots the phone. Step 3 says to reboot. Not sure if that is correct? Rebooting would just boot to the stock boot image again?
Click to expand...
Click to collapse
You're right. Just skip that step 3.

imakul8 said:
You're right. Just skip that step 3.
Click to expand...
Click to collapse
I did assume that so that's the step I followed.
Just to confirm, when I boot the patched image and install Magisk Manager and launch it, it should show that it is already installed? So I press "install" next to Magisk and direct install, this looks like it works. Then I reboot and I am not rooted, if I open Magisk Manager it shows that Magisk is not installed.

ricksrod said:
I did assume that so that's the step I followed.
Just to confirm, when I boot the patched image and install Magisk Manager and launch it, it should show that it is already installed? So I press "install" next to Magisk and direct install, this looks like it works. Then I reboot and I am not rooted, if I open Magisk Manager it shows that Magisk is not installed.
Click to expand...
Click to collapse
Right. Magisk said it was installed. I direct installed again, rebooted and Magisk was still installed. No idea to help you. ?

imakul8 said:
Right. Magisk said it was installed. I direct installed again, rebooted and Magisk was still installed. No idea to help you.
Click to expand...
Click to collapse
I've tried extracting the boot_img from my device and then patching that directly in Magisk and that does not work also, even though it reports a success, it doesn't appear to work.
When you install Magisk, what do you have ticked in the Advanced Settings out of:
Preserve Force Encryption
Preserve AVB 2.0/dm-verify
Recovery Mode
?

ricksrod said:
I've tried extracting the boot_img from my device and then patching that directly in Magisk and that does not work also, even though it reports a success, it doesn't appear to work.
When you install Magisk, what do you have ticked in the Advanced Settings out of:
Preserve Force Encryption
Preserve AVB 2.0/dm-verify
Recovery Mode
?
Click to expand...
Click to collapse
Just the first two. Not recovery mode.

imakul8 said:
Just the first two. Not recovery mode.
Click to expand...
Click to collapse
I've got it working now by using the Canary version of Magisk. I thought the stable version was now working?

ricksrod said:
I've got it working now by using the Canary version of Magisk. I thought the stable version was now working?
Click to expand...
Click to collapse
Stable is working for me, but good that you got it working. ?

Can someone check if magisk hide is working properly? Thanks

Jeens99 said:
Can someone check if magisk hide is working properly? Thanks
Click to expand...
Click to collapse
It works. Snapchat and my banking app don't like root. They're working fine.

Samsung S9 UNABLE TO BOOT UP after flashing SuperSU

Dear all,
I (newbie who trying to root for the first time) have tried to root my Samsung S9 with SuperSu via Odin. My device is now stuck at the S9 loading screen which will not boot up anymore.
Source of learning:
https://www.youtube.com/watch?v=g3IppGISkP0
Here's what I have done:
Stage 0 - Download all needed files
1. Odin 3.13.1
2. no-verify-opt-encrypt-6.0-star
3. RMM-state-ByPass_Mesa.zip
4. Samsung-anti-removal.2.4.zip
5. SupserSu-v.2.82.201705271822.zip
Stage 1 (Setup environment)
1. Enable Developer mode - OEM unlock enabled & USB Debugging enabled
2. Turn off my device, enter download mode (volume down button + bixby button + power button)
3. Connect my S9 device to my laptop
4. Launch Odin 3.13.1 on my laptop (S9 device recognized!) - Select AP, choose TWRP 3.3.1.1, press on start. (Device turn off itself)
5. As soon as device begins to boot, I enter recovery mode (volume up button + bixby button + power button)
Stage 2 Managed to entered TWRP
1. Swipe to Allow Modification
2. Tap on Wipe > Format Data > type in YES
3. Back to Menu
4. Tap on Install, (no-verify-opt-encrypt-6.0-star) - success
5. Reboot - Recovery
6. Tap on Install - (RMM-state-ByPass_Mesa.zip) - success
6. Hit back button
7. Tap on (SupserSu-v.2.82.201705271822.zip) - success
8 . Hit back button
9. Tap on (Samsung-anti-removal.2.4.zip) - success
10. Reboot system
11. Device begins reboot (Device stuck at Samsung S9 Screen)
Any advice what should I do now? Am I making any mistakes?
Please help. Appreciate!

CounteReborn said:
Dear all,
I (newbie who trying to root for the first time) have tried to root my Samsung S9 with SuperSu via Odin. My device is now stuck at the S9 loading screen which will not boot up anymore.
Source of learning:
https://www.youtube.com/watch?v=g3IppGISkP0
Here's what I have done:
Stage 0 - Download all needed files
1. Odin 3.13.1
2. no-verify-opt-encrypt-6.0-star
3. RMM-state-ByPass_Mesa.zip
4. Samsung-anti-removal.2.4.zip
5. SupserSu-v.2.82.201705271822.zip
Stage 1 (Setup environment)
1. Enable Developer mode - OEM unlock enabled & USB Debugging enabled
2. Turn off my device, enter download mode (volume down button + bixby button + power button)
3. Connect my S9 device to my laptop
4. Launch Odin 3.13.1 on my laptop (S9 device recognized!) - Select AP, choose TWRP 3.3.1.1, press on start. (Device turn off itself)
5. As soon as device begins to boot, I enter recovery mode (volume up button + bixby button + power button)
Stage 2 Managed to entered TWRP
1. Swipe to Allow Modification
2. Tap on Wipe > Format Data > type in YES
3. Back to Menu
4. Tap on Install, (no-verify-opt-encrypt-6.0-star) - success
5. Reboot - Recovery
6. Tap on Install - (RMM-state-ByPass_Mesa.zip) - success
6. Hit back button
7. Tap on (SupserSu-v.2.82.201705271822.zip) - success
8 . Hit back button
9. Tap on (Samsung-anti-removal.2.4.zip) - success
10. Reboot system
11. Device begins reboot (Device stuck at Samsung S9 Screen)
Any advice what should I do now? Am I making any mistakes?
Please help. Appreciate!
Click to expand...
Click to collapse
I believe you need magisk.

Instead of using SuperSU try using Magisk, it's more simple has has more features compared to SuperSU.
Also I think the reason why you stuck at the bootscreen is that after you format your phone, that means your phone got no rom/ system. Maybe you can try installing the ROM from the custom one which you can find in the cross device section in Here (Exynos Only).
And each of them has the instruction on how to install Magisk to root your phone
Edit: The video you refered to I believe is for the android 9 version, if your phone is on android 10 then it's outdated for your phone

TheMadScientist said:
I believe you need magisk.
Click to expand...
Click to collapse
I actually tried with Magisk.. but it stays the same. Basically I replace stage 2, step 7 with Magisk instead of Supersu.
Flashing only Magisk does not mean I have any system in place correct?
B1nz said:
Instead of using SuperSU try using Magisk, it's more simple has has more features compared to SuperSU.
Also I think the reason why you stuck at the bootscreen is that after you format your phone, that means your phone got no rom/ system. Maybe you can try installing the ROM from the custom one which you can find in the cross device section in Here (Exynos Only).
And each of them has the instruction on how to install Magisk to root your phone
Edit: The video you refered to I believe is for the android 9 version, if your phone is on android 10 then it's outdated for your phone
Click to expand...
Click to collapse
My device was on Android 9 actually.. so I have the exact same version as the video shown. Today I have flashed back my device with Stock ROM on Android 10. Im not sure with the steps Im doing it is right, when should I actually flash a custom rom? Please correct me if im wrong, my stage 1 should be all correct. Stage 2, before step 10 rebooting system, I should actually flash Custom ROM? Because after formatting my device and installing Magisk on Stage 2 step 7, my device still got no rom right?

After flashing back my device with Stock ROM on Android 10, I tried to root my device again with the steps give in video (still failed, device stuck at Samsung Logo again).
Flashing back again with Stock ROM. Tried to enter download mode to start TWRP via Odin.
Then I was given a message "Only official release binaries are allowed to be flashed (RECOVERY)" in Download Mode
Now what? Does that mean I can't go flash anymore? :crying:

CounteReborn said:
My device was on Android 9 actually.. so I have the exact same version as the video shown. Today I have flashed back my device with Stock ROM on Android 10. Im not sure with the steps Im doing it is right, when should I actually flash a custom rom? Please correct me if im wrong, my stage 1 should be all correct. Stage 2, before step 10 rebooting system, I should actually flash Custom ROM? Because after formatting my device and installing Magisk on Stage 2 step 7, my device still got no rom right?
Click to expand...
Click to collapse
Yes, the steps that I did on my own by coming from stock ROM:
1. Flash TWRP from odin, disable the automatic reboot
2. If success, then manually reboot to TWRP
3. Then I formated my phone
4. Follow the custom ROM installation steps
5. Done!
note:
- Steps 1 & 2 is basically the same as what you've done.
- If you still want to running the stock ROM, you have to flash the modified one or you'll stuck on the boot screen.
My suggestion is using the Alexis ROM, which is more updated (already on oneUI 2.1), more light, has alot of features (which you can choose in the aroma installer), and built in Magisk. so you don't have to install magisk manually
---------- Post added at 12:55 PM ---------- Previous post was at 12:51 PM ----------
CounteReborn said:
After flashing back my device with Stock ROM on Android 10, I tried to root my device again with the steps give in video (still failed, device stuck at Samsung Logo again).
Flashing back again with Stock ROM. Tried to enter download mode to start TWRP via Odin.
Then I was given a message "Only official release binaries are allowed to be flashed (RECOVERY)" in Download Mode
Now what? Does that mean I can't go flash anymore? :crying:
Click to expand...
Click to collapse
is it written "Prenormal"?
there's this stage called prenormal where you failed to modified your phone for the firstime, basically you have to wait like 7 days until you can modify your phone again.
and if still failing, it will back to the prenormal stage.
so far that's what i know, correct me if i'm wrong
if not then you can try to flash TWRP to see if it works
Also the thing i realize is that to be able to flash TWRP in Odin you have to finished doing the first time setup on the ROM, idk why but that's what i'm facing back then

Are you on Android 10? If yes, i followed this video.
https://m.youtube.com/watch?feature=youtu.be&v=HSqam9CYNGU
---------- Post added at 09:19 AM ---------- Previous post was at 09:13 AM ----------
CounteReborn said:
After flashing back my device with Stock ROM on Android 10, I tried to root my device again with the steps give in video (still failed, device stuck at Samsung Logo again).
Flashing back again with Stock ROM. Tried to enter download mode to start TWRP via Odin.
Then I was given a message "Only official release binaries are allowed to be flashed (RECOVERY)" in Download Mode
Now what? Does that mean I can't go flash anymore? :crying:
Click to expand...
Click to collapse
Because you flashed the stock firmware, you might forgot to enable oem bootloader unlock?

B1nz said:
Yes, the steps that I did on my own by coming from stock ROM:
1. Flash TWRP from odin, disable the automatic reboot
2. If success, then manually reboot to TWRP
3. Then I formated my phone
4. Follow the custom ROM installation steps
5. Done!
note:
- Steps 1 & 2 is basically the same as what you've done.
- If you still want to running the stock ROM, you have to flash the modified one or you'll stuck on the boot screen.
My suggestion is using the Alexis ROM, which is more updated (already on oneUI 2.1), more light, has alot of features (which you can choose in the aroma installer), and built in Magisk. so you don't have to install magisk manually
---------- Post added at 12:55 PM ---------- Previous post was at 12:51 PM ----------
is it written "Prenormal"?
there's this stage called prenormal where you failed to modified your phone for the firstime, basically you have to wait like 7 days until you can modify your phone again.
and if still failing, it will back to the prenormal stage.
so far that's what i know, correct me if i'm wrong
if not then you can try to flash TWRP to see if it works
Also the thing i realize is that to be able to flash TWRP in Odin you have to finished doing the first time setup on the ROM, idk why but that's what i'm facing back then
Click to expand...
Click to collapse
Not sure what actually happened, but the message is now gone after restart.
Anyway, Do you know this website (https://desktop.firmware.mobi/) instead, can I just use the ROM here to flash my device?
Not sure if I could just do the same, downlaod the recovery and boot img, then flash via Odin?
mkl.xda said:
Are you on Android 10? If yes, i followed this video.
https://m.youtube.com/watch?feature=youtu.be&v=HSqam9CYNGU
---------- Post added at 09:19 AM ---------- Previous post was at 09:13 AM ----------
Because you flashed the stock firmware, you might forgot to enable oem bootloader unlock?
Click to expand...
Click to collapse
Not sure what I did again, but the message "Only official release binaries are allowed to be flashed (RECOVERY)" is now removed. I just recall I did a restart I think. I tried your video, it didn't work. I end up in the same screen which I now think this is expected case? Because once we completely wipe the phone, the device has no more ROM. So in the video, we only flash back Magisk and Disable Verify.
Do you know this website (https://desktop.firmware.mobi/) instead, can I just use the ROM here to flash my device?
Not sure if I could just do the same, downlaod the recovery and boot img, then flash via Odin?

CounteReborn said:
Not sure what actually happened, but the message is now gone after restart.
Anyway, Do you know this website (https://desktop.firmware.mobi/) instead, can I just use the ROM here to flash my device?
Not sure if I could just do the same, downlaod the recovery and boot img, then flash via Odin?
Click to expand...
Click to collapse
Never knew that before tho, but if you want to download the official one I would recomend you downlaod from the SamMobile, which I highly recommend and is already trusted by alot of users here, just choose the right model number and country and you're done!, or if you want a faster download then I recommend you to use either Frija or SamFirm which is the same, and both are tools to download firmware from SamMobile.
It will download a zip of firmware, you just have to extract it and flash it by using Odin, also for the CSC file choose the HOME_CSC don't choose the normal CSC,
if you able to get into the normal rom, then you can do the instruction that i give before
hope it works

[Metro][Stock] SOFIAP-T QPRS30.80.64.6.2

100% Stock ROM for the Metro by T-Mobile Moto G Stylus
Requirements:
ADB & Fastboot from here:
https://developer.android.com/studio/releases/platform-tools
ADB & Fastboot set into your OS environment
(This allows adb to be used in any folder)
Instructions here:
https://wiki.lineageos.org/adb_fastboot_guide.html#installing-adb-and-fastboot
7-Zip to extract the .7z file:
https://www.7-zip.org/
Download:
QPRS30.80.64.6.2
Older Downloads:
QPRS30.80.64.6
QPRS30.80.64.3
Flashing Instructions:
1. Extract the zip using 7-Zip
2. Boot into Fastboot
3. Run the flash-all.bat this should automatically start flashing all the partitions
This will wipe everything. If you want to keep your data, before running open the .bat file with a text editor and remove -w from
Code:
fastboot -w reboot
​
(If on another platform than Windows you'll need to change the .bat file to your OS)
Looking for the Retail variant Stock ROM?
See Here:
https://forum.xda-developers.com/mo...t/stock-rom-motorola-g-stylus-retail-t4104451

QPRS30.80.64.6
https://mega.nz/file/nQkRHByR#md9YeMeAS4Vp6_lhL3pm9Bbqx1JrCeMHW8Lbkzr1RQo

cbc0201 said:
QPRS30.80.64.6
https://mega.nz/file/nQkRHByR#md9YeMeAS4Vp6_lhL3pm9Bbqx1JrCeMHW8Lbkzr1RQo
Click to expand...
Click to collapse
Thanks for the download. I added to the OP with the flash-all.bat

DMedina559 said:
Thanks for the download. I added to the OP with the flash-all.bat
Click to expand...
Click to collapse
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
---------- Post added at 03:13 AM ---------- Previous post was at 03:09 AM ----------
LinuxAndroidAlwys said:
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
Click to expand...
Click to collapse
I have QPR30.80.64.6 model XT2043-4

LinuxAndroidAlwys said:
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
---------- Post added at 03:13 AM ---------- Previous post was at 03:09 AM ----------
I have QPR30.80.64.6 model XT2043-4
Click to expand...
Click to collapse
You should be able to tell in the about phone menu in the settings. And the S might be a typo I'm not sure I'll have to check

DMedina559 said:
You should be able to tell in the about phone menu in the settings. And the S might be a typo I'm not sure I'll have to check
Click to expand...
Click to collapse
I figured it out but I'm still confused about the s

LinuxAndroidAlwys said:
I figured it out but I'm still confused about the s
Click to expand...
Click to collapse
The s is just a typo on my end. I'll fix asap

Not sure If I'm in the rightr thread or not but need serious help !!! I had twrp on my phone was trying to reboot system and hit a slot phone went black and will not boot into fastboot turn on, nothing! It is as dead as a dorrnail ie hard bricked . I have loaded all the drivers for phone and qualcomm. Computer only recognizes phone as Qualcomm 9008 mode not bulk mode. Anyone know how to restore phone at least to be able to get into fadtboot? Anyone help would be very much appreciated this is my daily driver and I am screwed without it.

worked great

QPR30.80_64_6_2
https://mega.nz/file/2UMGDb7B#4OZmO_DMUXiJnSkuyf4Y1w3LHVxoXM-P7umpRUWqaAQ

LinuxAndroid4evr said:
Not sure If I'm in the rightr thread or not but need serious help !!! I had twrp on my phone was trying to reboot system and hit a slot phone went black and will not boot into fastboot turn on, nothing! It is as dead as a dorrnail ie hard bricked . I have loaded all the drivers for phone and qualcomm. Computer only recognizes phone as Qualcomm 9008 mode not bulk mode. Anyone know how to restore phone at least to be able to get into fadtboot? Anyone help would be very much appreciated this is my daily driver and I am screwed without it.
Click to expand...
Click to collapse
i did the same thing, booting into slot b got me into the device normally

cbc0201 said:
QPR30.80_64_6_2
https://mega.nz/file/2UMGDb7B#4OZmO_DMUXiJnSkuyf4Y1w3LHVxoXM-P7umpRUWqaAQ
Click to expand...
Click to collapse
Hey man this is my current version as well, but it doesnt have the flashall bat file, do you know if i could just use one from the links in the OP? i am new to flashing roms in this manner and i dont really know how it works

Updated OP with build QPRS30.80.64.6.2

CorporalCactus said:
Hey man this is my current version as well, but it doesnt have the flashall bat file, do you know if i could just use one from the links in the OP? i am new to flashing roms in this manner and i dont really know how it works
Click to expand...
Click to collapse
Yeah using the old flash-all.bat file works with newer builds, just put all the flahsing files in /Recovery-Files/ with the flash-all.bat outisde that folder

Is any way to completely delete Metro PCS bloatware? I have rooted phone. No success to delete bloatware. Can I replace Metro PCS ROM with retail ROM? Is that possible? Any ideas? Thank you

Hello please I used the Moto g stylus as well, using MetroPCS with QPRS30.80-64-6-2, I want to know if this rom is unlocked , will it remove the sim lock on my device as the remote unlock fails. Thanks

Hi new guy here. Got couple moto g stylus (2020 pro). Mine Ive tried out arrow, havoc cr stag, bliss and resurrection. My wife's exact same phone she decided to have me install resurrection remix and magisk root it. ADB installed until last step which was fastboot -w. Had error about not auto formatting RAW format. I managed to fix that but still boot looped or twrp 35. Sofia will load but can't install any rom from zip. Stag logo bootlooeded.. hard to even explain.. damn. Anyway
Any suggestions?

Where is the flash-all.bat ?

MotoLindvall said:
Hi new guy here. Got couple moto g stylus (2020 pro). Mine Ive tried out arrow, havoc cr stag, bliss and resurrection. My wife's exact same phone she decided to have me install resurrection remix and magisk root it. ADB installed until last step which was fastboot -w. Had error about not auto formatting RAW format. I managed to fix that but still boot looped or twrp 35. Sofia will load but can't install any rom from zip. Stag logo bootlooeded.. hard to even explain.. damn. Anyway
Any suggestions?
Click to expand...
Click to collapse
If you still need to figure out the crazy flashing procedure for our device...best answer is make sure you are on STOCK Android 10...if you have updated to Android 11 you will not be able to flash custom ROMs or have a fully functional TWRP recovery...and Magisk root is not good with A11..You can flash GSI on Android 11 Stock firmware or use the DSU loader to install the Beta of Android 12...and the GSI situation is 50/50 if it will boot or not....what I do is flash the A10 stock final upload from the lionnet archive using the ever so awesome Moto flash tool...the tool does everything...and fixed your Beta partition so you can flash custom ROMs...once you finish with the tool reboot into STOCK recovery and format data..reboot to Stock Android 10 once you get to the Android setup welcome screen reboot to boot loader and flash TWRP recovery to both recovery slots...reboot to recovery...and format data...then reboot to fastbootd...your first custom install is recommended to be flashed from fastbootd on both slots...now when you finish reboot to Stock 10 recovery and format data...boot the rom first before and mods installed...then once you boot the rom you can flash mods with TWRP..get in a habit of after new system install format data in stock 10 recovery...now any custom ROM flash at this point forward do from TWRP and before flashing format data in TWRP after format again in stock 10 recovery...gapps install after first boot...Magisk install only after you fully go through the flashing procedure and setup the Rom make sure to enable dev options or it won't boot..and again flash Magisk after full setup and reboot..this procedure works...I keep a copy of stock recovery and TWRP recovery on my sdcard and platform tools on pc...you can flash stock 10 and TWRP in mobile if your rooted with any root kernel mgr so that way you don't have to use pc...the moto flash tool is the best way to setup the phone for custom ROMs.....