Warning:
Proceed with your own risk. I hold no responsibility if something goes wrong and you get killed.
Warranty void
KNOX tripped and some security feature won't be available
This guide based on @topjohnwu Magisk for Samsung. However, T510 is a bit different because it doesn't have Bixby button.
https://topjohnwu.github.io/Magisk/samsung
You need the latest Odin (I use 3.13). 3.12 or older won't work
***** NOTICE *****
Auto reboot must be disabled.
Download ROM matches your build number especially the last three characters. Unzip and only use AP and copy it to your tablet
Download ***special*** version Magisk Manager to your tablet and install it. "Install" Magisk using patch boot with AP file, and copy magisk_patched.tar to your host PC
https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Do not use normal Magisk to patch AP because it won't work
Bootloader Unlocked (read my guide)
Do not restore yet until this process is done.
STEPS:
1. Download your version of ROM. Make sure it matches your device Build Number
2. Unzip the ROM and copy AP to your tablet. Install Magisk Manager downloaded from link above. Normal Magisk Manager won't work.
3. Patch AP with Magisk Manager. The output file is "magisk_patched.tar". Copy the output file to your host computer.
4. Open Odin. Make sure Auto Reboot is disabled (unchecked)
5. Turn your tablet off. Press and hold Volume up and down buttons and connect your tablet to host computer. Press Volume up again to enter Download Mode.
6. Odin should show "Added". Locate your "magisk_patched.tar" and open as AP (it's AP after all). You don't have to flash others.
7. Wipe your tablet.
Disconnect your tablet.
Press and hold Power and Volume down.
As soon as the screen goes dark, immediately press and hold Power and Volume up until recovery screen appears.
Choose Factory Reset and press Power once, and confirm.
Reboot System Now
8. As soon as the screen turns dark, press and hold Power and Volume up buttons before screen shows bootloader warning. It will reboot again like brand new unit.
9. Do initial setup. Copy the Magisk Manager to your tablet and install if you don't see it
10. Setup internet connection and Magisk Manager will do some process, and it will reboot after it's done. You don't have to do button combo at this time.
11. Open Magisk Manager again to add other function including hide.
Your tablet should be rooted. However, here is something you should know.
Press Power button only: System with Magisk
[*]Press and hold Power and Volume up buttons before the screen shows bootloader warning and release: System with Magisk
Press and hold Power and Volume up buttons all the way: Stock recovery
That's it. Root is done.
***** IMPORTANT *****
If you want to do manual update, make sure you do steps 1-6 again. You don't have to wipe your tablet however.
Update: it appears "normal" Magisk (19.3) and Magisk Manager can simplify the entire rooting process.
Special instructions for Samsung is gone now.
Moreover, it appears normal boot can enter rooted system without button combo
mingkee said:
However, here is something you should know.
Press Power button only: System with no Magisk
Press and hold Power and Volume up buttons before the screen shows bootloader warning and release: System with Magisk
Press and hold Power and Volume up buttons all the way: Stock recovery
That's it. Root is done.
Click to expand...
Click to collapse
I must not be understanding something, as no matter how I press Power and Volume Up, I end-up in recovery. Otherwise it boots without magisk installed.
If I release buttons when I see the Samsung logo, before the warning, I can then press volume up to continue with boot, and it opens recovery.
If I release buttons after I see the warning, the warning goes away in a flash and I still end-up in recovery.
If I release the buttons as soon as I see the Samsung logo, same thing.
Any suggestions?
I did all the steps again, strangely Magisk gave me a different patched.tar file.
Flashed the patched, but I noticed in Odin:
<ID:0/008> recovery.img
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I get a red message saying only official release binaries... The tablet is unlocked though... I must be missing something.
EDIT:
Now the tablet says an error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software. Can't even turn it off!
Smart Switch says 'Unsupported device' and device does not appear in the list for emergency recovery. Tablet appears soft-bricked
Finally Odin managed to flash it, after failing at first. Flashing stock now. Will start over.
It appears the latest Magisk and Manager simplified everything.
The latest Magisk (19.3) is "normal" version, so you may no longer need "canary". Moreover, special instructions for Samsung disappeared (click the link on the first post and it doesn't work).
I also noticed normal boot (just press power button with no combo) and boot into "root mode"
mingkee said:
It appears the latest Magisk and Manager simplified everything.
The latest Magisk (19.3) is "normal" version, so you may no longer need "canary". Moreover, special instructions for Samsung disappeared (click the link on the first post and it doesn't work).
I also noticed normal boot (just press power button with no combo) and boot into "root mode"
Click to expand...
Click to collapse
I followed the original guide and using the button combo to boot with Magisk. How do I move to normal boot? Magisk installed version is 19.4-c, and I just received version 7.3.0 of the manager. Should I simply (re-)install Magisk 19.4-c to get normal boot?
3c said:
I followed the original guide and using the button combo to boot with Magisk. How do I move to normal boot? Magisk installed version is 19.4-c, and I just received version 7.3.0 of the manager. Should I simply (re-)install Magisk 19.4-c to get normal boot?
Click to expand...
Click to collapse
I will show you a screen cap later on because I don't carry it to work.
I used the "canary" build Manager and the root.zip
Now the root.zip is normal while Manager build number is still different.
As I mentioned on the edited post, the special instructions is gone, so it's possible topjohn has figured out solution for Samsung and integrated.
Yes, I boot it "normal" way and root is 100%
Noob Question
Hello and thanks for that guide!
There is (at least for now) one question:
Where do I get the stock ROM from?
mingkee said:
Warning:
STEPS:
1. Download your version of ROM. Make sure it matches your device Build Number
Click to expand...
Click to collapse
LeonardHofstadter said:
Hello and thanks for that guide!
There is (at least for now) one question:
Where do I get the stock ROM from?
Click to expand...
Click to collapse
You can find them on sammobile or samfrew
Thanks for this guide but I think I didn't do something right.
----------------
Reboot System Now
8. As soon as the screen turns dark, press and hold Power and Volume up buttons before screen shows bootloader warning. It will reboot again like brand new unit.
----------------
At this part, just after the factory reset, I reboot system and then I press Power and Vol+, but it goes again to Recovery. It never reboots like "brand new unit". It will always show the warning at start. Perhaps I misunderstood this part somehow.
Hantoniorl said:
Thanks for this guide but I think I didn't do something right.
----------------
Reboot System Now
8. As soon as the screen turns dark, press and hold Power and Volume up buttons before screen shows bootloader warning. It will reboot again like brand new unit.
----------------
At this part, just after the factory reset, I reboot system and then I press Power and Vol+, but it goes again to Recovery. It never reboots like "brand new unit". It will always show the warning at start. Perhaps I misunderstood this part somehow.
Click to expand...
Click to collapse
When you press Power and Vol+ the warning will only flash, that's when you need to release the buttons. If you keep pressing it goes in recovery. I had a hard time figuring this out.
3c said:
When you press Power and Vol+ the warning will only flash, that's when you need to release the buttons. If you keep pressing it goes in recovery. I had a hard time figuring this out.
Click to expand...
Click to collapse
Thanks!
I just tried releasing the buttons just afther the "warning flash". Then it showed up again. After initial settings and Magisk installation, again that screen.
I'll try to start from scratch with another T510 and report back as soon as I can. Thanks again.
I'm pretty sure rebooting to recovery with volume up and power is still needed on every boot. The link for Samsung devices has just been moved.
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Thanks for the guide.
Can someone confirm if i reboot, what do i have to press to keep it in root mode.?
So far the only way I've been able to do it, is to press power and volume up button and release when it flashes.
Root keeps disappearing unless I press combination of buttons.
Is there anyway to keep in root mode without pressing buttons?
test2006au said:
Thanks for the guide.
Can someone confirm if i reboot, what do i have to press to keep it in root mode.?
So far the only way I've been able to do it, is to press power and volume up button and release when it flashes.
Root keeps disappearing unless I press combination of buttons.
Is there anyway to keep in root mode without pressing buttons?
Click to expand...
Click to collapse
I believe this is the only method at the moment.
Thank you very much for the rooting method, after unlocking the bootlader and rooting I have expanded my ram and now my tablet works flawlessly
Has anyone had any luck using Odin on Linux? I'm using JOdin Casual on Linux Mint and it seems like the process hangs while sending the patched image to the tablet, I also tried using my Windows 10 VM, and it seems to just get stuck after hitting start in Odin
Triscuit said:
Has anyone had any luck using Odin on Linux? I'm using JOdin Casual on Linux Mint and it seems like the process hangs while sending the patched image to the tablet, I also tried using my Windows 10 VM, and it seems to just get stuck after hitting start in Odin
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using XDA Labs
Hey there, thank you for your guide!
I had a little problem when flashing with Odin though.
The tablet starts downloading, but when it gets to vbmeta.img, it shows the error "Custom Binary(VBMETA) Blocked by OEM Lock"
Before flashing, I disabled OEM Lock in the Developer Settings, but it did not help.
Any ideas would be greatly appreciated. Thx again!
Triscuit said:
Has anyone had any luck using Odin on Linux? I'm using JOdin Casual on Linux Mint and it seems like the process hangs while sending the patched image to the tablet, I also tried using my Windows 10 VM, and it seems to just get stuck after hitting start in Odin
Click to expand...
Click to collapse
I'm hitting a roadblock here, as well. I haven't tried using JOdin because I've seen discussions stating that you need 1.4.2 of Heimdall to flash these tablets, so I built that from source (JOdin includes 1.4.0). I unlocked the tablet, then patched the firmware with Magisk. Now I'm not sure what to do next.
Heimdall has its own package structure (which I'll read tonight), so it won't flash the AP file like Odin. It looks like it requires individually flashing each segment of the AP archive directly, and I really don't want to do that without some input from someone who can confirm that will work.
I'm acting based on this thread, on [RECOVERY][UNOFFICIAL] TWRP 3.3.1 for 2019 Galaxy Tab A 10.1 [SM-T510] and the Magisk install by patching file instructions.
Do I really need to extract each piece of the TAR per these instructions?
Also, the instructions to install TWRP here don't state that rooting must be done first, but based on the whole workflow, it seems it is required because this process flashes to AP and Magisk uses a stock AP when patching. It seems the work for TWRP would be obliterated by the Magisk root process.
Can anybody clear this up?
Kenaz Rune said:
I'm hitting a roadblock here, as well. I haven't tried using JOdin because I've seen discussions stating that you need 1.4.2 of Heimdall to flash these tablets, so I built that from source (JOdin includes 1.4.0). I unlocked the tablet, then patched the firmware with Magisk. Now I'm not sure what to do next.
Heimdall has its own package structure (which I'll read tonight), so it won't flash the AP file like Odin. It looks like it requires individually flashing each segment of the AP archive directly, and I really don't want to do that without some input from someone who can confirm that will work.
I'm acting based on this thread, on [RECOVERY][UNOFFICIAL] TWRP 3.3.1 for 2019 Galaxy Tab A 10.1 [SM-T510] and the Magisk install by patching file instructions.
Do I really need to extract each piece of the TAR per these instructions?
Also, the instructions to install TWRP here don't state that rooting must be done first, but based on the whole workflow, it seems it is required because this process flashes to AP and Magisk uses a stock AP when patching. It seems the work for TWRP would be obliterated by the Magisk root process.
Can anybody clear this up?
Click to expand...
Click to collapse
I honestly gave up trying to do this whole process on Linux, so I made a virtual machine with windows, made sure all my USB stuff was correct and used the official ODIN, worked like a charm
Sent from my Pixel 2 XL using XDA Labs
Related
Disclaimer: Do it with your own risk. Knox will be tripped!!!
DO NOT REBOOT THE UNIT AFTER ROOTED FOR AT LEAST 7 DAYS UNTIL OEM UNLOCK OPTION SHOWS UP AGAIN!!! Failure to do it will result losing root and you have to wait 7 days.
Preparation:
1. Install Samsung Smart Switch on host PC and unit to backup data and install required driver
2. ADB should be installed
3. Download Magisk and copy onto memory card.
4. Download Odin
5. Download TWRP from @ashyx and locate it to where Odin can be found. https://forum.xda-developers.com/ga...t-samsung-tab-8-0-2017-root-tutorial-t3730905
6. (Recommended) Download full ROM from sammobile.com just in case you need it with Odin. Model, version, and CSC should match your model.
7. There's a 7 day waiting to have OEM Unlock option shows up. This is a required step, and you have to wait 7 days after factory reset.
Operation:
1. Backup data with Smart Switch to both memory card and your host PC
2. Enter Download Mode
Use adb command
Code:
adb reboot bootloader
or Turn the unit off, and press and hold Home+Volume Down+Power
3. Make sure Auto Reboot disabled on Odin
4. Flash TWRP on AP slot.
5. Enter TWRP
You have to press and hold Volume Down+Power to reset, and as soon as the screen goes blank, press and hold Volume Up+Power. If you failed to do it, let the tablet boots normally and turn it off. After it's turned off, press and hold Home+Volume Up+Power to enter TWRP.
6. Format Data
This is a critical step to make sure root installed properly. On TWRP main screen, go to Wipe and Format Data and answer yes. After formatting, go back to main screen and choose reboot and reboot recovery
7. Install root of your choice
When you're back to TWRP, you can install root of your choice. Make sure it's copied onto memory card so you can install. You should see no error (no red line). Wipe cache if you want.
8. Reboot to system
It may take 10-15 minutes, and you will see Samsung flashes. Don't worry. You will see the initial setup screen and finish it.
9. Check root
For Magisk, you should see two checks. Make sure you install Safety Net check to complete.
10. Restore data
Congratulations! Your T380 is successfully rooted.
(Optional but recommended)
After rooted, use your root file explorer and do the following:
1. Edit build.prop
Change ro.security.vaultkeeper.feature=1 from 1 to 0
2. Remove RLC folder
Delete /system/priv-app/Rlc
There isn't any way of bypassing OEM unlock? I have this tab new and I want to be rooted now....
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I had a sm-t350 then I broke the charger port in the device so I updated to the sm-t380 and the OEM unlock thing I couldn't figure out why Odin and Heimdall wouldn't let me use twrp
no OEM Unlock option after 8 days
My tab has been on for 8 days and the OEM Unlock option hasn't shown up
Edit: after turning developer settings off and on again it showed up
DessertArbiter said:
My tab has been on for 8 days and the OEM Unlock option hasn't shown up
Edit: after turning developer settings off and on again it showed up
Click to expand...
Click to collapse
it did the same to me, I found another way of causing it to come up and immediatly (providing the 7 days have passed).
I tried setting time and date forward and that did nothing at all as if the tablet knew it was being tricked.
i did that on the 4th day as I too was impatient, set it forward 1 month and nothing.
then after 8 days it still hadn't shown up, so i connected to wifi and then went to settings, general management, date and time, flipped the automatic date and time to off and then back on again, rebooted the device (wifi still on when i rebooted) and then went to settings, developer options and it was visible.
hasn't helped me though, i still can't get my tablet to take TWRP.
Buying this tablet for someone as a gift but planned to root it first. Anything you guys would recommend as must have after root? And what would you recommend removing straight away?
nolajohnny said:
Buying this tablet for someone as a gift but planned to root it first. Anything you guys would recommend as must have after root? And what would you recommend removing straight away?
Click to expand...
Click to collapse
Titanium Backup Pro, RootExplorer, Rootbooter, about all you need for rooted tools and utilities really.
root booter is optional but it saves the finger gymnastics getting into TWRP.
I rooted one of these had it rooted for over a week and lost root on it, be very careful with this model, it can be very touchy, nice tablet though really.
For Oreo you need a custom kernel for full root because of Samsung Defex
Worked great!
This worked perfectly! Thank you so much. Wish it was as easy to root my S9+.
CSC?
Corwinder said:
This worked perfectly! Thank you so much. Wish it was as easy to root my S9+.
Click to expand...
Click to collapse
hello -
when you rooted, did you download firmware and if so how did you determine CSC?
mingkee said:
Disclaimer: Do it with your own risk. Knox will be tripped!!!
DO NOT REBOOT THE UNIT AFTER ROOTED FOR AT LEAST 7 DAYS UNTIL OEM UNLOCK OPTION SHOWS UP AGAIN!!! Failure to do it will result losing root and you have to wait 7 days.
Preparation:
1. Install Samsung Smart Switch on host PC and unit to backup data and install required driver
2. ADB should be installed
3. Download Magisk and copy onto memory card.
4. Download Odin
5. Download TWRP from @ashyx and locate it to where Odin can be found. https://forum.xda-developers.com/ga...t-samsung-tab-8-0-2017-root-tutorial-t3730905
6. (Recommended) Download full ROM from sammobile.com just in case you need it with Odin. Model, version, and CSC should match your model.
7. There's a 7 day waiting to have OEM Unlock option shows up. This is a required step, and you have to wait 7 days after factory reset.
Operation:
1. Backup data with Smart Switch to both memory card and your host PC
2. Enter Download Mode
Use adb command
Code:
adb reboot bootloader
or Turn the unit off, and press and hold Home+Volume Down+Power
3. Make sure Auto Reboot disabled on Odin
4. Flash TWRP on AP slot.
5. Enter TWRP
You have to press and hold Volume Down+Power to reset, and as soon as the screen goes blank, press and hold Volume Up+Power. If you failed to do it, let the tablet boots normally and turn it off. After it's turned off, press and hold Home+Volume Up+Power to enter TWRP.
6. Format Data
This is a critical step to make sure root installed properly. On TWRP main screen, go to Wipe and Format Data and answer yes. After formatting, go back to main screen and choose reboot and reboot recovery
7. Install root of your choice
When you're back to TWRP, you can install root of your choice. Make sure it's copied onto memory card so you can install. You should see no error (no red line). Wipe cache if you want.
8. Reboot to system
It may take 10-15 minutes, and you will see Samsung flashes. Don't worry. You will see the initial setup screen and finish it.
9. Check root
For Magisk, you should see two checks. Make sure you install Safety Net check to complete.
10. Restore data
Congratulations! Your T380 is successfully rooted.
(Optional but recommended)
After rooted, use your root file explorer and do the following:
1. Edit build.prop
Change ro.security.vaultkeeper.feature=1 from 1 to 0
2. Remove RLC folder
Delete /system/priv-app/Rlc
Click to expand...
Click to collapse
Thank you for posting this guide. I followed all steps exactly as written; installed magisk; obtained root. Problem is that when in TWRP I cannot mount data. External SD mounts fine, but internal storage reads 0MB. My device is T380 (2017) Oreo 8.1 . Any suggestions? Thanks.
jurisquo said:
Thank you for posting this guide. I followed all steps exactly as written; installed magisk; obtained root. Problem is that when in TWRP I cannot mount data. External SD mounts fine, but internal storage reads 0MB. My device is T380 (2017) Oreo 8.1 . Any suggestions? Thanks.
Click to expand...
Click to collapse
That's OK
Just let it be until you have done optional step to prevent the "lockup"
mingkee said:
That's OK
Just let it be until you have done optional step to prevent the "lockup"
Click to expand...
Click to collapse
I have the same issue and when I did try to do the optional recommended steps I couldn't find either step in build.prop or system folder.
Magisk Install Error
Doing just as you say, I got TWRP to take just fine but Magisk Manager reports that no Root is installed. The only red line I saw while installing Magisk simply said 'E:' and that's all... Any ideas out there why I'm getting that error?
Austcool said:
There isn't any way of bypassing OEM unlock? I have this tab new and I want to be rooted now....
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I had a sm-t350 then I broke the charger port in the device so I updated to the sm-t380 and the OEM unlock thing I couldn't figure out why Odin and Heimdall wouldn't let me use twrp
Click to expand...
Click to collapse
I have used a method where you remove the sim card (If your device has one) factory reset the device, then set it up without a sim card or connecting to the internet, then turn on developer options, then conntent to wifi or insternet a wrking sim card, then restart, than the opiton should be there
Magisk is not installed in Magisk Manager after flash with TWRP
hello, I've followed your instructions on how to root and everything seems to be fine and dandy at first, redlines during Magisk installation with TWRP and so on, exactly like your instructions. however after I finished flashing Magisk for root, I boot up my tab and when I want to check if my Magisk is flashed or not using Magisk Manager, it said that my Magisk wasn't installed/flashed? so then I checked with root checker to see if I have root access or not, and turns out I still don't have the root access/root is not installed, even though I clearly just flash magisk into my tab using twrp.
I've been searching for an entire day to find solution online but to no avail whatsoever.... and now I have a bad headache trying to figure out what iv'e been doing wrong during the flash process... yes I have OEM unlocked, yes I have USB Debugging checked during twrp flash using odin, yes I format under wipe option in twrp before flash Magisk. please help....
anyone know how to boot into twrp on the actual sm-t380?
DaricDarkFox said:
anyone know how to boot into twrp on the actual sm-t380?
Click to expand...
Click to collapse
For posterity if no longer for DaricDarkFox:
- Boot to TWRP from power-off using Power and Vol+ (Download Mode is Power and Vol-, TWRP is Power and Vol+)
- Boot from a running system by selecting Restart and then quickly pressing and holding Vol+ (nothing else, just Vol+)
- Boot to TWRP from Download Mode by pressing Power and Vol- (as usual to exit Download Mode) and when screen goes blank, quickly release Vol- (but still holding Power) and press and hold Vol+
All of these methods consistently work for me. Most guidance for the T380 says to also press and hold the Home button, but (again for me at least) the Home button is not needed at all.
My Tab S2 T713 is currently running the latest stock Samsung rom. I want to install Lineage 15.1
I've downloaded twrp-3.2.1-0-gts28vewifi.img.tar & Odin 3.12.7. I can boot into download mode, flash TWRP with Odin which says success & my tablet reboots normally. When I power down & reboot into recovery TWRP gets over written by the stock recovery.
If I uncheck Auto Reboot in Odin, after flashing success, I'm still in download mode - I've read that I need to boot directly into recovery from download mode - how do I do this?
In download mode pressing home + voldown + power reboots normally. Pressing home + volup + power does nothing
What am I doing wrong?
Gidders said:
My Tab S2 T713 is currently running the latest stock Samsung rom. I want to install Lineage 15.1
I've downloaded twrp-3.2.1-0-gts28vewifi.img.tar & Odin 3.12.7. I can boot into download mode, flash TWRP with Odin which says success & my tablet reboots normally. When I power down & reboot into recovery TWRP gets over written by the stock recovery.
If I uncheck Auto Reboot in Odin, after flashing success, I'm still in download mode - I've read that I need to boot directly into recovery from download mode - how do I do this?
In download mode pressing home + voldown + power reboots normally. Pressing home + volup + power does nothing
What am I doing wrong?
Click to expand...
Click to collapse
https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
Brilliant - thank you. Why they can't have they have that in the Lineage install instructions?
Now running Lineage 15.1 = happy bunny
boxcar8028 said:
https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
Click to expand...
Click to collapse
For the love of god, thank you. This wasn't in the LineageOS instructions. But I still can't install it, it says my bootloader isn't supported (T713XXU1APG1).
notmyidea said:
For the love of god, thank you. This wasn't in the LineageOS instructions. But I still can't install it, it says my bootloader isn't supported (T713XXU1APG1).
Click to expand...
Click to collapse
Did you go into your developer settings and make sure you toggled the option titled "OEM Unlock"?
sh0nuff said:
Did you go into your developer settings and make sure you toggled the option titled "OEM Unlock"?
Click to expand...
Click to collapse
Got that figured out, thanks. All installed now after much difficulty.
notmyidea said:
Got that figured out, thanks. All installed now after much difficulty.
Click to expand...
Click to collapse
Good to hear! Please make sure you give a thumbs up to anyone who helped. It really keeps the community alive and kicking!
I found that I had to do this from completely powered off state:
press home + volume up + power
wait until second "sentence" appears on screen in yellow (the first "sentence" is blue),
Then release all buttons
twrp now boots.
for some reason, my internal and external storage is showing 0 mb. Anyway to fix this?
Try formatting (not just wipe) data.
Should the Galaxy Tab S2 2016 be on TWRP 3.2.1.0 or the new 3.2.3.0 for Linage OS 15?
If so, can't you just flash the update using TWRP on the img file, or is ODIN on the tar needed?
OK, I updated to TWRP 3.2.3 using TWRP Recovery and the img file. Appears to work fine.
SvenHee said:
I found that I had to do this from completely powered off state:
press home + volume up + power
wait until second "sentence" appears on screen in yellow (the first "sentence" is blue),
Then release all buttons
twrp now boots.
Click to expand...
Click to collapse
Sorry to revisit this issue. I can't get TWRP going on my S2 Tablet. I understand these instructions, but at the end of the ODIN installation there are two possibilities that I can see. If you set the ODIN to automatically reboot then you cannot do the above because it says to do it from completely powered off.
If you don't set ODIN to reboot automatically I can't get the tablet to turn off. I can only get it to boot by holding home+volume down + power. How do I get the tablet to power off before booting??
I am using ODIN 3.14.4 and TWRP-3.7.0 9-0-gts28wifi.img.tar and my stock firmware is NRD90M.T713XXS2BSG1 with Kernel 3.10.84-14953299
Thank you.
Samsung Galaxy Tab S2
SM-T710 8.0" Wifi
Nougat with all the latest updates
Wife hands me her tablet the other day and it is stuck in safe mode. Using notification shade link to turn off safe mode simply reboots to safe mode. To make this worse, the other method of on/off safe mode is to hold vol down with power. It seems the volume down button has failed. When android is running, pressing volume up raises the volume as normal, pressing volume down does nothing. Same in recovery, volume up works, volume down does not.
Looking around for solutions, I stumbled on this:
http://forum.gsmhosting.com/vbb/f777/how-exit-safe-mode-samsung-phones-simple-solution-here-1727011/
which claims to allow safe mode disabling with root. Ok, so I figure I need to root the tablet, no big deal. Well I'm stuck, I can't get it to work.
I've follow every guide I can find. Most all of them start with rebooting to download mode. The standard method is to hold volume down again, can't do that. So instead I use adb (adb reboot download). The use Odin to flash TWRP - no go. Every instruction I can find also says to hold volume down after Odin finishes the flash. Just powering off, and then holding vol up + power + home doesn't get me anywhere. I can boot back to android, reboot recovery, and it is only the stock. Even tried flashing a nougat (supposed) version of CF autoroot. That does something more, because the boot screen warns me that SE Andriod is not enforcing. But even that simply ends with rebooting to Android, no root. Interestingly, the last step in the CF Autoroot says "Restoring Stock Recovery", not sure why.
Ok, so there it all is. I'm stuck. Anyone have any ideas
a) how to get safe mode off with no vol down button
b) how to actually successfully root the latest nougat (again, with no vol down button)
Any ideas are much appreciated. Thanks
hdad2 said:
Samsung Galaxy Tab S2
SM-T710 8.0" Wifi
Nougat with all the latest updates
Wife hands me her tablet the other day and it is stuck in safe mode. Using notification shade link to turn off safe mode simply reboots to safe mode. To make this worse, the other method of on/off safe mode is to hold vol down with power. It seems the volume down button has failed. When android is running, pressing volume up raises the volume as normal, pressing volume down does nothing. Same in recovery, volume up works, volume down does not.
Looking around for solutions, I stumbled on this:
http://forum.gsmhosting.com/vbb/f777/how-exit-safe-mode-samsung-phones-simple-solution-here-1727011/
which claims to allow safe mode disabling with root. Ok, so I figure I need to root the tablet, no big deal. Well I'm stuck, I can't get it to work.
I've follow every guide I can find. Most all of them start with rebooting to download mode. The standard method is to hold volume down again, can't do that. So instead I use adb (adb reboot download). The use Odin to flash TWRP - no go. Every instruction I can find also says to hold volume down after Odin finishes the flash. Just powering off, and then holding vol up + power + home doesn't get me anywhere. I can boot back to android, reboot recovery, and it is only the stock. Even tried flashing a nougat (supposed) version of CF autoroot. That does something more, because the boot screen warns me that SE Andriod is not enforcing. But even that simply ends with rebooting to Android, no root. Interestingly, the last step in the CF Autoroot says "Restoring Stock Recovery", not sure why.
Ok, so there it all is. I'm stuck. Anyone have any ideas
a) how to get safe mode off with no vol down button
b) how to actually successfully root the latest nougat (again, with no vol down button)
Any ideas are much appreciated. Thanks
Click to expand...
Click to collapse
I doubt it's failed. Your volume down button is probably just stuck down which is why it continually boots to safe mode.
Volume up would still work.
Pop the back off and check the contact under the button isn't stuck down or get the vacuum cleaner hose with the slim attachment , place it over the button and it MAY just be enough to release it.
ashyx said:
I doubt it's failed. Your volume down button is probably just stuck down which is why it continually boots to safe mode.
Volume up would still work.
Pop the back off and check the contact under the button isn't stuck down or get the vacuum cleaner hose with the slim attachment , place it over the button and it MAY just be enough to release it.
Click to expand...
Click to collapse
You could be right. Wouldn't know it by the feel of the button. It feels perfect. And being in safe mode won't let me load any app or anything that might tell me one way or another.
I'm trying to avoid cracking the tablet open because I'm not sure I'd be able to fix it at all once I did. Probably can't physically see any issue it might have with the button. Plus it looks like a royal pain to open. But in the end I might be forced to try.
Anyone know a root method that doesn't involve volume down?
Terrible to think that the whole device could be rendered useless by a button that isn't critical to its use. (can turn down volume by hitting vol up and then using the slider on screen)
hdad2 said:
You could be right. Wouldn't know it by the feel of the button. It feels perfect. And being in safe mode won't let me load any app or anything that might tell me one way or another.
I'm trying to avoid cracking the tablet open because I'm not sure I'd be able to fix it at all once I did. Probably can't physically see any issue it might have with the button. Plus it looks like a royal pain to open. But in the end I might be forced to try.
Anyone know a root method that doesn't involve volume down?
Terrible to think that the whole device could be rendered useless by a button that isn't critical to its use. (can turn down volume by hitting vol up and then using the slider on screen)
Click to expand...
Click to collapse
You can get root no problem just by flashing a rooted Magisk boot image, but I doubt going to help with booting into safe mode as that button combo is hard coded.
ashyx said:
You can get root no problem just by flashing a rooted Magisk boot image, but I doubt going to help with booting into safe mode as that button combo is hard coded.
Click to expand...
Click to collapse
Well if root does not allow disabling of safe mode, then I'm out of luck. But this link indicated that it could work. I've never tried so I'm just grasping at anything.
How exactly can I install a rooted boot images without the following:
- No ability to install a playstore or any other app (no magisk manager)
- Can't get TWRP to install (presumably because this is now blocked by latest firmware?? Not sure but it fails for me following the Odin instructions I find here and elsewhere) I think this requires vol down button - at least all the instructions call for it after flashing TWRP with Odin
I have ADB and Odin at my disposal, but I can't seem to get Odin to actually install TWRP. CF Autoroot (for Nougat) does nothing either.
Am stuck in safe mode please my volume is not working galaxy tab 4 please help
Did someone solve this issue? I am also stuck with a non functioning tab due to one stuck button...
Stuck button
I had a friend with this issue. I was able to use a sewing machine needle to pop the button up. Make sure you tape or protect the side from scratches. Also, you can try holding down the volume up button. It's a meaningless combo so it may boot.
Hi guys while searching the web and the forum to find a way to root our phone I found this guide https://topjohnwu.github.io/Magisk/samsung
you can do it by yourself if you want but I thought to edit it a bit to match our device. all credit goes to original developer I just copied what he did and it worked.
I don't take any responsibility if anything happens to device, brick ect. use the guide with your own risk!
make sure you have updated drivers and a good usb cable, I recommend Smart Switch for pc you can download in the samsung site, it will also install latest drivers and you can back up the phone with it to the pc.
just for your information rooting voids the waranty, trips knox and makes things complicated, but I can't have a phone without root, it reminds me the days with my old nexus 4.
this guide will also factory reset your phone so make sure to back up everything don't forget to back up whatsapp in the app itself.
I'm not a developer maybe there is an easier way to root, this is the only way I found, so if you want to wait until an experienced developer who knows english better then me release another way to root that's fine by me, I wont get upset.
the only downside I see in this kind of root that you can't normally enter the system. I mean that normal reboot and power up will boot your system without magisk, because the root sits on the recovery or something like that. so each time you power off your phone to power it up you need to hold the Volume up + Power button untill you see the bootloader unlocked warning and release, and everything will be working with root. even if you accidently powerd your phone without the way I mentioned you still have root don't panic like I did just turn off the phone and power it up like I mentioned and its all good.
also you can't normally update the phone through the phone settings and to update the phone with odin like I understand you'll need to have a patched version of the AP tar file with magisk, or something bad will happen to the phone, again I am not a developer I don't know the full risks.
so after the warnings and the long intro here is the edited guide:
Unlock the bootloader - this will wipe all your data so make sure to back up before you start anything!
Allow bootloader unlocking in Developer options → OEM unlocking
Power off your device. Volume Up + Volume Down + Power button and plug in your device to a PC to boot into download mode
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
the developer also mentions that sometimes it wont work because something called VaultKeeper. I didn't had that issue just make sure after the system boots after you unlocked the bootloader that the OEM unlocking option exists and grayed out in the developer options.
Instruction
1.Download the firmware for your device.
2.Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
3.Install Magisk Manager from the Canary Channel
4.In Magisk Manager: Install → Install → Select and Patch a File
5.Select the AP tar file. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
6.Copy the tar file to your PC, and boot your device to download mode. (Hold all 3 buttons Volume Up+Volume Down+Power Button and connect to PC cable)
I have downloaded the firmware with Samfirm I found it on the forum I'll upload it here. I will also upload the AP file I patched and write the firmware version I took it from. I'll also upload the full firmware for you if you can't find a good mirror online. and also the odin version I used.
the csc i look up is for ILO but I think the csc have multiple regions, you know better I'll upload it anyway maybe it will save time for someone.
7.Flash magisk_patched.tar as AP in ODIN (I flashed the entire firmware because I had some problems flashing without all the files try it the way you want. flash it with normal csc of you choose to flash the whol firmware)
Important: Uncheck “Auto Reboot” in Options!!!!
8.Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
9.We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power Button+Volume Up+Volume Down to exit download mode, and as soon as the screen turns off, immediately press Power Button+Volume Up to boot to recovery partition. Just as mentioned in the previous section, since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
10.In the stock recovery menu, use volume buttons to navigate through menus, and the power button to select the option. Select Wipe data/factory reset to wipe the data of the device.
11.This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press Power Button+ Volume Up. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
12.The device will automatically reboot for the first time it boots. This is completely normal and done by design.
13.After the device is booted up, do the usual initial setup. The following steps will need internet connection.
14.You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded in step 3 and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
15.Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
16.Baruh Ashem! enjoy magsik!
That's it I think if I forgot something I'm sorry I hope it worked for you! and maybe some real developers start to look at the device and start building costume roms andall the good stuff that comes with it!
meanwhile the files are uploading you can try get them by yourself here are the names of the files I used:
Odin3_v3.13.1_3B_PatcheD
Samfirm
firmware file: SM-A705FN_1_20190412140953_u5ql0uali6_fac
Magisk manager is linked the developer enterd the canary build but I'll also upload 7.1.2.apk version I found on the internet.
ALL CREDIT GOES TO THE ORIGINAL DEVELOPER, AND DEVELOPERS. if you have any question I can help you with my own expirence only.
Here is the download link, use at your own risk. if you are not sure the firmware uploaded is right for your device download yourself with samfirm that i also uploaded.
Download Link - Google Drive
Thanks for your research and this manual! I've been trying your steps for a few hours now, and after a few trial and errors, softbricks and reboots I'm still not able to succeed.
Magisk Manager won't show up in the apps after setup wizard. Installing it manually, it says Magisk is not installed
My phone: A70 from the Netherlands. I used Israel firmware from updato.com (https://updato.com/firmware-archive-select-model?record=440E12D670B911E9BE8CFA163EE8F90B) and your file (which is same size after patching). Unfortunately I can't find Dutch firmware, hence the Israel version.
Anybody else succeeded?
Captain Beretta said:
Thanks for your research and this manual! I've been trying your steps for a few hours now, and after a few trial and errors, softbricks and reboots I'm still not able to succeed.
Magisk Manager won't show up in the apps after setup wizard. Installing it manually, it says Magisk is not installed
My phone: A70 from the Netherlands. I used Israel firmware from updato.com (https://updato.com/firmware-archive-select-model?record=440E12D670B911E9BE8CFA163EE8F90B) and your file (which is same size after patching). Unfortunately I can't find Dutch firmware, hence the Israel version.
Anybody else succeeded?
Click to expand...
Click to collapse
thank you for the feedback!
did you flashed the whole firmware? with BL, patched AP,CP and CSC? on the google drive folder I have to full firmware try to download that.
maybe you do have it installed but you didn't boot corectly. try to turn off your phone then hold volume up+power button and hold them untill you see the galaxy a70 powered by android. and then check magisk! I hope it helped!
Will try and flash complete firmware with all your Drive files tomorrow! Hope it will succeed
Captain Beretta said:
Will try and flash complete firmware with all your Drive files tomorrow! Hope it will succeed
Click to expand...
Click to collapse
I wait for your success, because I'm trying to decide to buy or not this device (root is very important to me)
infearno said:
I wait for your success, because I'm trying to decide to buy or not this device (root is very important to me)
Click to expand...
Click to collapse
I have good hope that this device can be rooted considering my past Samsung devices, it is only a matter or time.
I'm downloading the files again now, and going to try! Will report back a.s.a.p.
Edit:
Installed everyhing from your files in Odin: BL, AP (patched), CP, CSC and:
It worked! Magisk installed, Magisk Manager updated. I could install AdAway and it asked for root permissions.
But... after reboot Magisk Manager said it is NOT installed anymore. Now what?
Edit 2:
It seems Magisk sometimes fails to load when booting. After some reboots, it is back again and AdAway works. So end of the story: IT WORKS, and it Magisk starts to nag that is it not installed, just reboot a couple of times, and enjoy your rooted phone
Edit3:
Screenshots:
https://i.postimg.cc/wMrbLSpZ/Screenshot-20190515-094200-Magisk-Manager.jpg
https://i.postimg.cc/WbDyTbmv/Screenshot-20190515-094205-Magisk-Manager.jpg
https://i.postimg.cc/wjLbRfb4/Screenshot-20190515-094325-Magisk-Manager.jpg
https://i.postimg.cc/BQdV69N1/Screenshot-20190515-094336-Ad-Away.jpg
Captain Beretta said:
I have good hope that this device can be rooted considering my past Samsung devices, it is only a matter or time.
I'm downloading the files again now, and going to try! Will report back a.s.a.p.
Edit:
Installed everyhing from your files in Odin: BL, AP (patched), CP, CSC and:
It worked! Magisk installed, Magisk Manager updated. I could install AdAway and it asked for root permissions.
But... after reboot Magisk Manager said it is NOT installed anymore. Now what?
Edit 2:
It seems Magisk sometimes fails to load when booting. After some reboots, it is back again and AdAway works. So end of the story: IT WORK, and it Magisk starts to nag that is it not installed, just reboot a couple of times, and enjoy your rooted phone
Click to expand...
Click to collapse
Yay I'm happy it worked!
Magisk isn't loading because of you want to boot with magisk you need to hold the volume up and power button together untill you see the bootloader unlocked warning and it asks your to press the power button to continue then release press the power button. I usually press volume up and power button again for 2 sec to make sure and that's it! Reboot won't boot with magisk sure make sure u use this method each time you need to reboot!
Avicohen21 said:
Yay I'm happy it worked!
Magisk isn't loading because of you want to boot with magisk you need to hold the volume up and power button together untill you see the bootloader unlocked warning and it asks your to press the power button to continue then release press the power button. I usually press volume up and power button again for 2 sec to make sure and that's it! Reboot won't boot with magisk sure make sure u use this method each time you need to reboot!
Click to expand...
Click to collapse
That's...unfortunate. Any way to unlock samsung fully?
infearno said:
That's...unfortunate. Any way to unlock samsung fully?
Click to expand...
Click to collapse
It's not that bad, even if you accidentally booted without magisk just turn off the phone and boot with the way I mentioned and magisk is back!
If you normally power up your phone just pressing the power button with this method just add the volume up and hold both button together for 4 to 5 sec.
Right now it's the only way to root that I found. Maybe with twrp things will get easier.
And one more thing if you install magisk module don't press reboot after your install just power off and boot the way I mentioned that's it.
Avicohen21 said:
Yay I'm happy it worked!
Magisk isn't loading because of you want to boot with magisk you need to hold the volume up and power button together untill you see the bootloader unlocked warning and it asks your to press the power button to continue then release press the power button. I usually press volume up and power button again for 2 sec to make sure and that's it! Reboot won't boot with magisk sure make sure u use this method each time you need to reboot!
Click to expand...
Click to collapse
I tested a few reboots, and this is how my A70 behaves:
X Reboot without pressing any buttons: no Magisk
X Reboot, pressing the power button when prompted: no Magisk
V Reboot, hold power button + volume up button, press power button to confirm: Magisk :victory:
Well, that's good enough for me! I am happy :laugh:
Captain Beretta said:
I tested a few reboots, and this is how my A70 behaves:
X Reboot without pressing any buttons: no Magisk
X Reboot, pressing the power button when prompted: no Magisk
V Reboot, hold power button + volume up button, press power button to confirm: Magisk :victory:
Well, that's good enough for me! I am happy :laugh:
Click to expand...
Click to collapse
Yeah that's right my English is not perfect maybe I didn't explained it good enough but that's what I meant! Thank you for trying. That's good enough for me also.
I also installed EdExposed and it's working good with modules that are confirmed to work with Android pie.
Next thing is trying to flash mods with flashify or something because we don't have twrp yet.
There is more good news!
I got EdXposed working following this manual, using the SandHook version: https://magiskroot.net/download-xposed-for-android-pie
It was really easy, just download and flash/install these files:
Links:
Riru core: https://github.com/RikkaApps/Riru/releases
EdXposed Sandhook: https://github.com/ElderDrivers/EdXposed/releases/tag/v0.4.1.2
EdXposed Installer: https://github.com/solohsu/XposedInstaller/releases/tag/Ed_v2.2.4
Don't forget to reboot with the button combination trick mentioned earlier!
this way can flash Treble?
5dprince said:
this way can flash Treble?
Click to expand...
Click to collapse
Not.
@Avicohen21 I want to do this, but now this magisk canari, to patch FW, is not longer available to download...
point me there, please
thanks
ivanox1972 said:
@Avicohen21 I want to do this, but now this magisk canari, to patch FW, is not longer available to download...
point me there, please
thanks
Click to expand...
Click to collapse
Here's the copy of it. View attachment 4768110
@Avicohen21 Actually I tried it on tab s5e- should be same procedure.
But I got fail result on odin flash patched ap...
Is this normal? 1 fail 0 success? or not- must be 1 success?
thanks
ivanox1972 said:
@Avicohen21 I want to do this, but now this magisk canari, to patch FW, is not longer available to download...
point me there, please
thanks
Click to expand...
Click to collapse
It also works with version 7.20 if you can't find an app I'll upload it.
ivanox1972 said:
@Avicohen21 Actually I tried it on tab s5e- should be same procedure.
But I got fail result on odin flash patched ap...
Is this normal? 1 fail 0 success? or not- must be 1 success?
thanks
Click to expand...
Click to collapse
If it failed maybe magisk didn't patched AP correctly try to extract the AP file again from the firmware file and then patch it in magisk again.
I extract with 7zip and got all ok in magisk. Newest 214 build.
But got success 0 fail 1 as result
Can't be ok like this?
@Avicohen21 I almost bricked it. Send me on pm your telegram contact or something to send you some pictures
Title says it all. But for those that want to know a bit more in detail about what's going on, I tried to install this custom ROM: https://forum.xda-developers.com/t/rom-oneui-2-5-twrp-ncx-2-5-for-a71-sm-a715f.4174135/ Clearly I did something wrong (a bit more clarification in that guide would help people not used to rooting an Android device getting through that process easier), so now I want to go to square 1 by installing the stock ROM again. But the thing is, after installing multidisabler through TWRP, the phone is not permanently stuck into a bootloop and now I can't even go into safemode, nor download mode, and I can't enter the recovery mode, the only thing my phone is capable of doing is to restart by itself by holding the volume down and the power buttons at the same time, and now ADB nor Fastboot can't detect my device (the PC does a Samsung device being connected though, so it's not a hardbrick, I guess).
Samsung devices do not use Fastboot. You should restore through Odin instead.
Try the following:
1. Download Odin on your computer, you can get it from here. Extract it into a folder.
2. Download the firmware for your device. Find out your device model first and then look on http://samfw.com, I've downloaded from there a lot in the past, it works great.
3. Extract the firmware, you should get five files: AP, BL, CP, CSC, and HOME_CSC.
4. Make sure your device is powered off, and press power + volume down + bixby. You should be asked to confirm you want to enter download mode, press the volume up button.
5. Plug your device into the computer, then select the files for all the slots. Use CSC, not HOME_CSC for CSC (CSC is for fresh restore, HOME_CSC is for software update).
6. A device should show in the top bar, something like [COM:6]. This means your device is connected. If it isn't there, make sure your device is plugged in and in Download Mode.
7. Click flash. The firmware should start to flash and there should be a progress bar in Download Mode. Once it's finished your device should reboot into the system.
ChasTechProjects said:
Samsung devices do not use Fastboot. You should restore through Odin instead.
Try the following:
1. Download Odin on your computer, you can get it from here. Extract it into a folder.
2. Download the firmware for your device. Find out your device model first and then look on http://samfw.com, I've downloaded from there a lot in the past, it works great.
3. Extract the firmware, you should get five files: AP, BL, CP, CSC, and HOME_CSC.
4. Make sure your device is powered off, and press power + volume down + bixby. You should be asked to confirm you want to enter download mode, press the volume up button.
5. Plug your device into the computer, then select the files for all the slots. Use CSC, not HOME_CSC for CSC (CSC is for fresh restore, HOME_CSC is for software update).
6. A device should show in the top bar, something like [COM:6]. This means your device is connected. If it isn't there, make sure your device is plugged in and in Download Mode.
7. Click flash. The firmware should start to flash and there should be a progress bar in Download Mode. Once it's finished your device should reboot into the system.
Click to expand...
Click to collapse
Well, trying to reflash everything through Odin has been a thing I tried to do, but how am I supposed to shutdown a phone that is stuck at the Samsung logo (is there any combination to shutdown a Samsung during the boot process?)? And even after that, how am I supposed to press "power + volume down + bixby" if both the power and bixby buttons are the same buttons?
racer21 said:
Well, trying to reflash everything through Odin has been a thing I tried to do, but how am I supposed to shutdown a phone that is stuck at the Samsung logo (is there any combination to shutdown a Samsung during the boot process?)? And even after that, how am I supposed to press "power + volume down + bixby" if both the power and bixby buttons are the same buttons?
Click to expand...
Click to collapse
Long press vol+,vol- and power and in the same time plug in in your pc
geekmaster21 said:
Long press vol+,vol- and power and in the same time plug in in your pc
Click to expand...
Click to collapse
I tried entering Download Mode hours ago, but to no avail. Even before flashing mutidisabler through TWRP (and thus, the phone was working), I had to use ADB in order to make my phone be able to enter Recovery Mode, since the combo for recovery and download mode just made my phone make a loud noise and restart my phone onto safe mode.
Ok, here's an update, apparently pressing those buttons, makes the screen have the same, but at least Odin recognizes the drive, but now I'm stuck at this error: "Complete(Write) operation failed."
Something's weird here, I'm 99.9% sure I did activate USB debugging for this phone, although that was just before wiping the entire drive before the phone got stuck in this loop.
Fixed. Many thanks to @hainguyenthao for helping me out ^^
racer21 said:
Title says it all. But for those that want to know a bit more in detail about what's going on, I tried to install this custom ROM: https://forum.xda-developers.com/t/rom-oneui-2-5-twrp-ncx-2-5-for-a71-sm-a715f.4174135/ Clearly I did something wrong (a bit more clarification in that guide would help people not used to rooting an Android device getting through that process easier), so now I want to go to square 1 by installing the stock ROM again. But the thing is, after installing multidisabler through TWRP, the phone is not permanently stuck into a bootloop and now I can't even go into safemode, nor download mode, and I can't enter the recovery mode, the only thing my phone is capable of doing is to restart by itself by holding the volume down and the power buttons at the same time, and now ADB nor Fastboot can't detect my device (the PC does a Samsung device being connected though, so it's not a hardbrick, I guess).
Click to expand...
Click to collapse
I'm sorry to hear that you had trouble installing the ROM and I'm glad you were able to fix it.
I unfortunately can't see a way that I could make the tutorial on how to install the ROM any easier. I'm almost certain I covered all my bases going over the perquisites and how to install the ROM. I also have a Telegram group in that thread so that users can join if they are ever stuck in any of the steps so that either me or other users that have successfully installed the ROM can help people in doubt since I'm not available 100% of the time. If you ever decide to give it a try again, don't be shy, you can always join the group and request for help.