Rooting Samsung Tab E (SM-T377W) on 7.1.1 - Android Q&A, Help & Troubleshooting

Hi all,
First time poster and honestly, a complete noob re: rooting. I tried once before with a BLU device I had, but had driver issues and just gave up.
Anyway, looking to remove a bunch of bloat from my Tab E that I barely use....... just fired it up today for the first time in months and saw an update to 7.1.1
All of my Google searching links me to this:
https://forum.xda-developers.com/android/development/recovery-official-twrp-gteslte-galaxy-t3419219
My concerns/problems are ....
1. Do I just pick the latest '.tar' file?
2. At no point does the guide actually say when to connect the device to the computer
3. I should be able to maintain my LTE connection after rooting, I assume?
4. I can't seem to get into "download mode", I got into "safe mode" somehow by mistake, but when following the suggestions here:
http://techbeasts.com/how-to-boot-samsung-galaxy-devices-in-download-recovery-mode/
To access "download mode", I get some life.... followed by an increasingly green circle. Get's to 66% with a flashing white circle, and then nothing happens.
5. Even if I could get into "download mode", it says to Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery. but Odin doesn't appear to be overly user-friendly as far as knowing when the end of the flash would be? Haven't got that far though, so mere speculation on my part.
I'm really lost at this point.... can anybody give me any pointers?
****EDIT*** So, I went ahead and tried again - turns out I was able to get it all done...... problem was the instructions didn't quite relate the my Tab E? Power+Vol Down+Home was needed to get into download mode, and Power+VolUp+Home was needed for Recovery.
Funny though, after confirming TWRP and following the reboot promps, device still didn't appear to be rooted. Tried again and "Root Checker" says it's not..... but NOBloat is not prompting me I'm not rooted, when previously it stated the device wasn't rooted? AND, I have SuperSU installed?

Easily done if you follow the rooting guide for the 6.0.1 ... anyway, here's how.
Download Odin (version 10.12.x) and then download TWRP into the same folder:
https://dl.twrp.me/gteslte/twrp-3.2.0-0-gteslte.img.tar.html
Now donwload Super User: https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip?retrieve_file=1
Run Odin (preferred in Admin mode) and load : twrp-3.2.0-0-gteslte.img.tar into the AP.
Put your Tablet into Download mode (Vol Down + Home + Power and then Vol Up), connect to your PC and Hit Start on Odin.
Wait for it to fully reboot and Power it Off, now reboot into Recovery mode (Vol Up + Home + Power), once in TWRP, copy Super User file into the Download folder of your Tablet, select Install from TWRP and install Super User. Reboot and enjoy Root

Using updated Odin (3.13.1) to root Tab E SM-T377W
As this post is somewhat dated, would the most recent Odin version (3.13.1) be appropriate?
I have the same Tab E (SM-T377W) running 7.1.1.
Thank you in advance for your help.
Reid.

Any suggestions how to root 7.1.1 ?

rooting 7.1.1
msaithan said:
Any suggestions how to root 7.1.1 ?
Click to expand...
Click to collapse
Root is possible. On firmware version: T377WVLU2BQI6, I just flashed this
TWRP-3.2.3-0-gteslte.img.tar (PM if you need a link. I uploaded it on my drive)
Then flashed magisk through TWRP yesterday.
Couple of notes though. Once you fllash TWRP with Odin, even with auto reboot ticked off, the device WILL STILL reboot. Once this happens, if you're not holding pwr, vol+, & home buttons, the custom recovery will be replaced back to stock. And as always, ensure drivers installed and debugging and OEM unlock is on.
---------- Post added at 04:25 AM ---------- Previous post was at 04:17 AM ----------
webREID said:
As this post is somewhat dated, would the most recent Odin version (3.13.1) be appropriate?
I have the same Tab E (SM-T377W) running 7.1.1.
Thank you in advance for your help.
Reid.
Click to expand...
Click to collapse
Usually when I flash, I found it's best to use which version of Odin was released at the time the device was. For instance, if I wanted to flash an S7, I'd probably use Odin 3.10. This is only AFTER I've tried my go to Odin version - Prince Comsey. I find it works 90% of the time though. This of course excludes any devices running stock Oreo or Pie. Where it's mandatory to have the latest version of Odin.

Android_GMS_Solutions said:
Root is possible. On firmware version: T377WVLU2BQI6, I just flashed this
TWRP-3.2.3-0-gteslte.img.tar (PM if you need a link. I uploaded it on my drive)
Then flashed magisk through TWRP yesterday.
Couple of notes though. Once you fllash TWRP with Odin, even with auto reboot ticked off, the device WILL STILL reboot. Once this happens, if you're not holding pwr, vol+, & home buttons, the custom recovery will be replaced back to stock. And as always, ensure drivers installed and debugging and OEM unlock is on.
Click to expand...
Click to collapse
Whenever i flash TWRP i get the message that FRP is locked (green color) and odin never pass, i have tried many times to install TWRP but its locked

Which firmware version do you have on the tablet?? Like, is there a 3 or 2 prior to the B?? I think it's the forth from the end

For example: T377WVLU '2' BQI6 or do you have the 3rd Bootloader?

Sassiest said:
Which firmware version do you have on the tablet?? Like, is there a 3 or 2 prior to the B?? I think it's the forth from the end
Click to expand...
Click to collapse
Firmware SM-T377W T377WVLU3BRG4 [7.1.1]

halp
I've been trying to use this thread and several others as a guide to root my galaxy tab E version sm-t377wVLU3BRG4 running android 7.1.1. I've been trying to root the tablet for 3 days including one click rooting applications both on and off pc.
I can't even get TWRP installed, I've tried using odin to flash it but when it reboots and I'm supposed hold volume up and home to boot into recovery mode it just keeps booting. I don't understand if I'm doing something wrong. Also half the guides I've read have had most of the files removed so I've just googled another guide

@Helium Iz Ninja
Probably your attempt flashing TWRP miserably failed for whatever reason.
BTW: How to install TWRP using ODIN is explained here.
If you have phone's Stock ROM at your fingertips, then re-flash this to bring back phone to its original state.

Related

Did I just brick my phone?

So, I was off attempting to root my phone with CF-Auto-Root. I have an S6 Edge from T-mobile, and so I selected the one for the SM-G925T, which was my phone's model number. On using Odin, following all the steps from the youtube video titled "How to Root Galaxy S6 or S6 Edge!" by Max Lee at High on Android (Sorry I can't post a link, I'm too new) Anyway, once I got to the part where I was rooting, upon restart, my phone seems to be locked in the startup screen. In the upper right corner in red, it says "Recovery is not seandroid enforcing" other than that, the screen is black with some white text that says "Samsung / Galaxy / S6 Edge / Powered By / Android" With each "/" representing a line break.
When I hold down the power button, nothing happens. Did I just ruin this phone, or is there something I can do to fix it? (I fear I may have unplugged it too early... I waited ~5 minutes before I figured it was totally frozen and that I would need to do something. Hopefully that didn't ruin the root...)
Thanks for any help!
Disclaimer, I'm no expert.
First, take a couple of deep breaths, your phone is not lost to the world.
Sounds like your stock firmware is kicking up a fuss about being booted from a non-samsung recovery.
There are several threads about this particular error already, but the general gist seems to be to get your phone back into Download Mode (power button + volume down + menu button) and flash your stock firmware back in.
That will probably remove root and clear your data though.
Do a Google for "Recovery seandroid enforcing s6" if you havn't already
Sent from my SM-G925I using Tapatalk
This is quite normal. The same thing happened to me.
If you've got as far as flashing TWRP via Odin then it should just be a matter of booting into recovery. As you're in a place where your phone will keep trying to boot even if you power off, it's just a matter of timing.
To shut the phone down you need to hold Power and Vol Down for about 10 seconds. What you'll find though is the phone will boot up again straight away and show you the annoying Seandroid screen so what you need to do is power off the phone then as soon as the screen goes black hit Vol Up, Home and Power. Keep holding them and instead of booting to Seandroid it should boot to TWRP. If you get Seandroid just try again. You need to get those buttons pressed as soon as the phone starts to boot-cycle though.
Once you're in TWRP you can install root, and then install the kernel which will allow the phone to boot normally again.
Good luck!
Mischala said:
Disclaimer, I'm no expert.
First, take a couple of deep breaths, your phone is not lost to the world.
Sounds like your stock firmware is kicking up a fuss about being booted from a non-samsung recovery.
There are several threads about this particular error already, but the general gist seems to be to get your phone back into Download Mode (power button + volume down + menu button) and flash your stock firmware back in.
That will probably remove root and clear your data though.
Do a Google for "Recovery seandroid enforcing s6" if you havn't already
Sent from my SM-G925I using Tapatalk
Click to expand...
Click to collapse
Yeah, I was just googling around to see if anyone had more luck. I'm currently downloading 5.1.1 (I didn't know that Samsung changed the bootloader, so I'll have to wait for that root to come out. Oh well...) Hopefully it goes well I'll update with results once it's done downloading!
The s6 is weird. This is the first Samsung phone that when using cf-auto root it soft-bricks my phone. You have to flash recovery through odin, then root through recovery for it to work. Dont forget the no sleep fix while you're there.
Here are the steps and links:
1. Download ODIN v 3.10.6 from http://forum.xda-developers.com/show....php?t=2711451 and extract it to a folder.
2. Download TWRP v2 by eousphoros (Odin Flashable Version) from https://mega.co.nz/#!aQhTnQRR!k-M-j9...swZO3CWYi0mMtI
3. Download the latest SuperSu Beta from http://forum.xda-developers.com/apps...v2-05-t2868133 and transfer it to your internal storage on the phone.
4. Download Deep-Sleep flashable fix from http://forum.xda-developers.com/show...7&postcount=56 and transfer it ot your internal storage on the phone.
5. Put your phone into Download Mode. Power Off, then hold Power+Home+VolDown. At the warning press VolUp to continue.
6. Connect your phone to your computer via the USB cable.
7. Launch ODIN.
8. You will see the text Added! in the status panel (left side).
9. Checkmark the box beside AP and then click on AP.
10. Browse to the TWRP tar.md5 file you downloaded earlier and select it.
11. Wait a few seconds for MD5 check to finish successfully.
12. Press Start. You will see the progress bar at the top and when it's complete status window will have message "All Threads Complete (Succeed 1, Failed 0)".
13. Boot into TWRP (Button combination Power+Home+VolUp) and then flash/sideload SuperSu beta zip and then the deep sleep fix zip that you have on internal storage.
14. Reboot to system. Congratulations, your phone is now rooted.
Click to expand...
Click to collapse
H00pyFr00d said:
This is quite normal. The same thing happened to me.
If you've got as far as flashing TWRP via Odin then it should just be a matter of booting into recovery. As you're in a place where your phone will keep trying to boot even if you power off, it's just a matter of timing.
To shut the phone down you need to hold Power and Vol Down for about 10 seconds. What you'll find though is the phone will boot up again straight away and show you the annoying Seandroid screen so what you need to do is power off the phone then as soon as the screen goes black hit Vol Up, Home and Power. Keep holding them and instead of booting to Seandroid it should boot to TWRP. If you get Seandroid just try again. You need to get those buttons pressed as soon as the phone starts to boot-cycle though.
Once you're in TWRP you can install root, and then install the kernel which will allow the phone to boot normally again.
Good luck!
Click to expand...
Click to collapse
I'm confused... When I use the Vol Down + home + power button, it boots into the normal (as far as I can tell) samsung bootloader thing (at least, the one from 5.1.1) So I don't think I have TWRP installed even. Anyway, it shows up in Odin, so how do I start loading everything? In the Files [Download] section in Odin, I see boxes that say BL, AP, CP, and CSC. Which of those do I select to load up the full backup that I got? (It's about 4GB of data with an .iso, if that makes a difference)
Edit: Basically, I have no MD5 files in the download. (I got it off high off android)
KaminKevCrew said:
I'm confused... When I use the Vol Down + home + power button, it boots into the normal (as far as I can tell) samsung bootloader thing (at least, the one from 5.1.1) So I don't think I have TWRP installed even. Anyway, it shows up in Odin, so how do I start loading everything? In the Files [Download] section in Odin, I see boxes that say BL, AP, CP, and CSC. Which of those do I select to load up the full backup that I got? (It's about 4GB of data with an .iso, if that makes a difference)
Edit: Basically, I have no MD5 files in the download. (I got it off high off android)
Click to expand...
Click to collapse
You will not be able to flash anything in odin if youre not in download mode. If you have trouble getting in download mode, you're doing it wrong. Turn off phone, then press Vol down + power + home and dont release any of those until you see something unusual, such as an android robot. While using odin, NEVER EVER load anything in any other option than AP. As far as backup goes, I don't know what backup you made but you don't restore it though odin thats for sure, you will hardbrick your phone.
polish_pat said:
You will not be able to flash anything in odin if youre not in download mode. If you have trouble getting in download mode, you're doing it wrong. Turn off phone, then press Vol down + power + home and dont release any of those until you see something unusual, such as an android robot. While using odin, NEVER EVER load anything in any other option than AP. As far as backup goes, I don't know what backup you made but you don't restore it though odin thats for sure, you will hardbrick your phone.
Click to expand...
Click to collapse
I can get into the stock Samsung download mode (light blue screen, it says downloading on it..) On the links posted in post number five, none of them worked for me... The thing is, I was trying to load TWRP while my phone was updated to 5.1.1 if that makes any difference... Anyway, it appears that the stock download mode is working, so what do I do now? (From what I've read, I can't really put TWRP on it??)
Alright, I got it working! (Hopefully this will help others get redirected to the right thread, since it took me a while to find this!) Depending on whether or not I am allowed to post links at this point, I may need to post repeatedly here, and I apologize for that, but it's all with the best intents in mind!!!
Anyway, if you do what I did, which is this:
No backup, attempt to root GS6 Edge (SM-G925T from T-mobile) with the 5.0.2 CF auto root, while your phone has already been updated to 5.1.1. It puts you in a boot loop, which really isn't fun, because it doesn't appear that you can fix it... Anyway, I went to the thread, which you can find here: http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002 . Anyway, what you need to do is boot into download mode (which you can still do when you are in the boot loop, just hold the volume down + home + power buttons until the device boots into the downloader screen. At that point, you use Odin, and install the file called "OF6 Stock Recovery". That should fix it! Anyway, go to the thread above, it helped me a TON!!!
This isn't really rocket science. Yes, there are different root options for 5.0.1 and 5.1.1 but this is clear in the OP when you decide which root to use.
The only things you need to consider are, if you flash a custom recovery (not the 'download mode' that you use for Odin) then the stock rom won't boot. It's not bricked but you just need a custom kernel. Therefore the steps are:
Download and copy the custom kernel and root to the phone
Boot into Download mode -Vol down, home, power - and flash recovery (TWRP etc) via Odin
Boot into TWRP custom recovery - Vol up, home, power - and flash kernel and root
Reboot
Profit
It really is just a matter of reading the steps carefully and doing exactly what they tell you.

ZU not responding to anything after installing recovery

Ok guys so I have a Sony Xperia Z Ultra and I decided to install Marshmallow 6.0 on it (which wasn't released for my phone). I downloaded the boot, cache, system and userdata imgs of Marshmallow 6.0 and installed them using fastboot, then I was supposed to boot in recovery mode and wipe the caches and do a reset, before installing the G-apps zip file and completing the entire process. So I tried to start recovery mode which I had previously installed already and it failed, starting in safe mode instead. Then I re-installed the recovery using a batch file in a directory downloaded from NUT's XDA Developers download site, which failed on the first try. So I tried again and it was installed, meaning my phone will automatically reboot into recovery right after it was done. My phone rebooted but my screen remained black and nothing happened. I tried holding down the power button and it vibrated but nothing happened again. I tried holding down the power and volume down button for 30sec and more, tried it with the volume up button too and it didn't work. I tried connecting my phone to the pc but it won't recognize it (of course) and I tried holding the volume up button upon connecting to enter fastboot but that failed as well. Now it's stuck like this and I'm hoping its battery drains out and it powers off. Help.
Update: I went to sleep and now that I've woken up, the screen is still going with the low battery red light. I don't know for how long it will continue, but the problem remains.
Update: Now my pc recognizes it but all adb commands have no effect.
Jissatsu said:
Ok guys so I have a Sony Xperia Z Ultra and I decided to install Marshmallow 6.0 on it (which wasn't released for my phone). I downloaded the boot, cache, system and userdata imgs of Marshmallow 6.0 and installed them using fastboot, then I was supposed to boot in recovery mode and wipe the caches and do a reset, before installing the G-apps zip file and completing the entire process. So I tried to start recovery mode which I had previously installed already and it failed, starting in safe mode instead. Then I re-installed the recovery using a batch file in a directory downloaded from NUT's XDA Developers download site, which failed on the first try. So I tried again and it was installed, meaning my phone will automatically reboot into recovery right after it was done. My phone rebooted but my screen remained black and nothing happened. I tried holding down the power button and it vibrated but nothing happened again. I tried holding down the power and volume down button for 30sec and more, tried it with the volume up button too and it didn't work. I tried connecting my phone to the pc but it won't recognize it (of course) and I tried holding the volume up button upon connecting to enter fastboot but that failed as well. Now it's stuck like this and I'm hoping its battery drains out and it powers off. Help.
Update: I went to sleep and now that I've woken up, the screen is still going with the low battery red light. I don't know for how long it will continue, but the problem remains.
Update: Now my pc recognizes it but all adb commands have no effect.
Click to expand...
Click to collapse
you should give some info... like what rom youre using. also use twrp 3.x with mm
you cant expect help without telling the error messages you get...
you can always power off your phone with holding vol down + power for 30sec
MusterMaxMueller said:
you should give some info... like what rom youre using. also use twrp 3.x with mm
you cant expect help without telling the error messages you get...
you can always power off your phone with holding vol down + power for 30sec
Click to expand...
Click to collapse
YEAH ok here's my issue. NO MATTER WHAT recovery I install (through the app or fastboot) IT DOES NOT WORK. Any earlier version of TWRP, it will boot into, but the screen is unresponsive, while the latest version of TWRP simply acts like it isn't there as the phone never boots into recovery, this has been happening on MM and now it's happening on my latest stock. After the failed MM attempts I've downloaded the latest C6833 stock and everything is fine, but I'd like to be able to install custom roms like everyone else. It took me a day or two to learn how to actually do that, but I still have no idea why NO recovery works for me. My device is rooted, bootloader unlocked, all that crap. I tried many kernel links on your site, especially that main one that the mod posted, but the links are dead. Help.
Jissatsu said:
YEAH ok here's my issue. NO MATTER WHAT recovery I install (through the app or fastboot) IT DOES NOT WORK. Any earlier version of TWRP, it will boot into, but the screen is unresponsive, while the latest version of TWRP simply acts like it isn't there as the phone never boots into recovery, this has been happening on MM and now it's happening on my latest stock. After the failed MM attempts I've downloaded the latest C6833 stock and everything is fine, but I'd like to be able to install custom roms like everyone else. It took me a day or two to learn how to actually do that, but I still have no idea why NO recovery works for me. My device is rooted, bootloader unlocked, all that crap. I tried many kernel links on your site, especially that main one that the mod posted, but the links are dead. Help.
Click to expand...
Click to collapse
there is other way to enter twrp 3.0.2 with new bootloader, power + vol down (instead of up!)
read op of twrp thread and follow instructions carefully and it'll work. also for the twrp i build you must be on a rom which uses sony aosp device tree (like aicp). otherwise i wont guarantee that it will work.
MusterMaxMueller said:
there is other way to enter twrp 3.0.2 with new bootloader, power + vol down (instead of up!)
read op of twrp thread and follow instructions carefully and it'll work. also for the twrp i build you must be on a rom which uses sony aosp device tree (like aicp). otherwise i wont guarantee that it will work.
Click to expand...
Click to collapse
I tried holding the button down like you said, tried rebooting to recovery from TWRP manager itself, with root access granted of course. Nothing. Can you link the post or something? However I don't think anything in it will fix my issue.
Sounds like you flashed a recovery for another model. I had this issue with a ROM awhile back.
Didn't read the walls of text.
I recommend using you flashtool and flashing a stock ftf. Re-root, recovery and flash again.
---------- Post added at 06:16 AM ---------- Previous post was at 06:11 AM ----------
Edit. Read somethings. There are plenty of ROMs on xda do not flash the old way which is part by part. Flash the most recent Sony firmware, and you should be able to flash MM ROMs.
I have copy's of the recovery if needed.
I did flash the latest FTF using the flash tool, but I need a working recovery in order to install the gapps and still no recovery works on my device.
check here
http://forum.xda-developers.com/xpe...2-0-togari-t3452968/post68481255#post68481255

Successfully Rooted Samsung SM-J120W Android 6.0.1 Wind Mobile Canada

Here are the steps to follow that worked for me to obtain Root on my Samsung SM-J120W Android 6.0.1 which I bought outright from Wind Mobile Canada. This method seems to work for other providers as well, but has not been tested by me. However, others in this thread have since rooted with Chatr (Rogers) and Koodo (Telus). This is great news!
Proceed at your OWN RISK. If you are successful, or successful rooting the SM-J120W that is with a provider other than Wind Mobile Canada, please post it here so others know!
In preparation for this process I performed a Software Update within Android, prior to rooting to ensure that I had the most up to date Android version available. From previous experience, I would suggest that you do not perform a Software update after rooting as it may remove root.
With respect to compatibility, on my phone under Settings > About device > Software info, the Baseband version of my phone, after ensuring the most recent update, was J120WVLU2AQA1 with Build number MMB29K.J120WVLU2AQA1 and Android security patch level January 1, 2017. These versions should match before you continue. To perform an OTA Software Update, on your phone Enable Wi-Fi then navigate to Settings > About Device > Download updates manually, then follow the instructions.
I used a Windows PC to interface with my Android. I have included a link below to a zip of all the files you will need in my Google Drive.
You should have some experience with Android recovery environments / flashing prior to proceeding at your OWN RISK. I will not be held liable for any damages related to this method.
Having said that, let's begin!
1. Download this zip archive from my Google Drive to your PC https://drive.google.com/open?id=0B1iPMyk4G2_-a0ZENXVETjNPT1E.
2. Extract Samsung SM-J120W Rooting Files.zip to your PC, then follow the instructions below on file usage for the files extracted from within.
3. Copy SR1-SuperSU-v2.78-SR1-20160915123031.zip from your PC to your phones internal storage.
4. Install Samsung USB Drivers SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.61.0.exe on your PC.
5. Extract Odin_3.12.3.zip to your PC.
6. On your phone, Open Settings > Developer options > Enable OEM unlock and Enable USB debugging.
* If under Settings there is no Developer options menu, tap About device > Software info > then tap Build number 7 times which will enable Developer options in the Settings menu.
* I was asked for a PIN for OEM unlock, it was my lock screen PIN.
7. Power off your phone. Remove the back cover from your phone. Connect your phone to your PC with a USB data cable. Power on your phone in Download Mode. (Press and hold Vol Down + Home + Power until you are presented with a warning regarding a custom OS). Press Vol Up to continue. You should now see ODIN MODE in red text at the top of the screen and a "Downloading... Do no turn off target" message.
8. On your PC, run Odin by opening Odin3_v3.12.3.exe. Under ID:COM the background should have turned blue. Under Log it should say Added!! Under Options, uncheck Auto Reboot and check F. Reset Time if it is not already checked. Click AP and select the twrp-3.0.2-0-b2-j1xlte.tar.md5 file in the Open dialog. Click Start.
9. Once Odin indicates PASS! in green at the top, flashing is complete. Now remove the battery from your phone. Unplug the USB data cable from your phone. Your phone will now be completely off. Click Exit to close the Odin program.
10. Replace the battery and back cover. Power on your phone in Recovery Mode. (Press and hold Vol Up + Home + Power until you see the blue TEAMWIN logo splash screen).
11. Now that you're in the TWRP Recovery environment, it should say Unmodified System Partition at the top. Tap Never show this screen during boot again, then Swipe at the bottom to Allow Modifications.
12. Tap Install, browse to & select the SR1-SuperSU-v2.78-SR1-20160915123031.zip file you copied to the Internal Storage in Step 3. Tap Reboot after installation is complete, then Swipe at the bottom to confirm Flash.
13. Your phone should boot normally into Android with SuperSU installed in your apps. Configure SuperSU to your liking and test for root by installing a Root Checker app if you wish.
* First boot after rooting may take a few minutes. It can also boot loop a few times. When I performed this on my phone, it did take a little while longer to boot than usual, but I didn't experience any boot loops and all went well.
* I have noticed that some "older" apps that require root, complain I am not rooted. For example, in the past on other phones, with earlier Android Versions, I have used ROM Toolbox Pro to overclock my CPU when rooted; and it no longer works with Android 6 MM. I suspect that the behaviour of Rooted Android 6 MM is a bit different than previous builds. I now use Kernel Adiutor (ROOT) and that works fine for overclocking and doesn't complain about not being rooted. Other newer apps that require root like Root Explorer, AdAway, Busybox Installer, Trimmer (fstrim) all work great!
Please share your experience or comments and suggestions related to this guide!
Updated Sep 13 2017 - Thank you to everyone for your feedback and suggestions.
Please provide a link
Hi, please provide a link of the file twrp-3.0.2-0-b2-j1xlte.tar.tar, I can't find it in google, thank you
https://drive.google.com/open?id=0B1iPMyk4G2_-a0ZENXVETjNPT1E
I rooted it successfully, thank you!
However, I am now having some issues installing xposed framework, have you tried install xposed framework in this phone model?
I installed this custom version of Xposed: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 because with the original one, the phone doesn't startup (it stays in the samsung screen).
That custom xposed version was installed good, and phone started up good, but when I install and activate an xposed module and reboot the phone, I get the same problem, phone stays in the samsung screen.
I hope it's possible to use xposed framework in this phone model, I will open a thread soon about this issue, thanks for the help!
lilandroid said:
I rooted it successfully, thank you!
However, I am now having some issues installing xposed framework, have you tried install xposed framework in this phone model?
I installed this custom version of Xposed: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 because with the original one, the phone doesn't startup (it stays in the samsung screen).
That custom xposed version was installed good, and phone started up good, but when I install and activate an xposed module and reboot the phone, I get the same problem, phone stays in the samsung screen.
I hope it's possible to use xposed framework in this phone model, I will open a thread soon about this issue, thanks for the help!
Click to expand...
Click to collapse
No problem, your welcome. I have not tried to install xposed yet. I don't have a use for it right now. If I attempt and am successful, I will let you know!
lilandroid said:
I rooted it successfully, thank you!
However, I am now having some issues installing xposed framework, have you tried install xposed framework in this phone model?
I installed this custom version of Xposed: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 because with the original one, the phone doesn't startup (it stays in the samsung screen).
That custom xposed version was installed good, and phone started up good, but when I install and activate an xposed module and reboot the phone, I get the same problem, phone stays in the samsung screen.
I hope it's possible to use xposed framework in this phone model, I will open a thread soon about this issue, thanks for the help!
Click to expand...
Click to collapse
I got it working on mine just now. I followed the procedure at this site: https://devs-lab.com/download-install-xposed-for-samsung-devices.html.
I was following that tutorial method, I retried just a few minutes ago with a different approach, and it worked, I will share it here maybe someone finds it useful:
I got rid of everything (root and xposed) with a firmware and odin.
Then I installed supersu and xposed at one time in twrp, then I installed xposed apk, I activated a different module this time, then I turned off instead of rebooting. I waited a few mins and then I turned my phone on and it worked!
I don't know what exactly was the problem, but most likely it was just a module issue.
As always, thanks for the help!
Just posting to confirm that OP's instructions worked flawlessly for me. I had already soft bricked it once using another method, recovered from that, and then found this thread. Thanks a bunch for the tutorial!
4o4 said:
Just posting to confirm that OP's instructions worked flawlessly for me. I had already soft bricked it once using another method, recovered from that, and then found this thread. Thanks a bunch for the tutorial!
Click to expand...
Click to collapse
Awesome! Thanks for the reply
Not working for me, Everything goes great right up to reboot after flashing TWRP. Reboots from Odin into system I wait for complete boot, Power off reboot with Power Volume up and home.
10. Power on your phone in Recovery Mode. (Press and hold Vol Up + Home + Power until you see the blue TEAMWIN logo splash screen).
Click to expand...
Click to collapse
It boots to Andriod Robot saying installing update, Which fails, I try to get it to boot into bootloader via the menu after the install fails but reboots directly to system. Any ideas?
Unit is from Chatr not wind.
is it better, more wise to download the latest version of Supersu from the google play store and use that one, as I notice the one in the zip has a 2008 date
At Step 10 when I try to reboot the phone into recovery mode I don't get the Teamwin splash screen, it just says "Installing System Update" then "No Command" and goes straight to the normal recovery mode. Am I doing something wrong?
---------- Post added at 06:40 AM ---------- Previous post was at 06:03 AM ----------
fubar121 said:
Not working for me, Everything goes great right up to reboot after flashing TWRP. Reboots from Odin into system I wait for complete boot, Power off reboot with Power Volume up and home.
It boots to Andriod Robot saying installing update, Which fails, I try to get it to boot into bootloader via the menu after the install fails but reboots directly to system. Any ideas?
Unit is from Chatr not wind.
Click to expand...
Click to collapse
Exact same happnened to me, did you get it to work after?
Kevinthemew said:
At Step 10 when I try to reboot the phone into recovery mode I don't get the Teamwin splash screen, it just says "Installing System Update" then "No Command" and goes straight to the normal recovery mode. Am I doing something wrong?
---------- Post added at 06:40 AM ---------- Previous post was at 06:03 AM ----------
Exact same happnened to me, did you get it to work after?
Click to expand...
Click to collapse
No sir I did not I will let you know if I can get it to work. Please do the same for me.
fubar121 said:
Not working for me, Everything goes great right up to reboot after flashing TWRP. Reboots from Odin into system I wait for complete boot, Power off reboot with Power Volume up and home.
It boots to Andriod Robot saying installing update, Which fails, I try to get it to boot into bootloader via the menu after the install fails but reboots directly to system. Any ideas?
Unit is from Chatr not wind.
Click to expand...
Click to collapse
Did you Enable OEM unlock in Developer Options? Sounds like the FRP lock is active.
adamwestca said:
Did you Enable OEM unlock in Developer Options? Sounds like the FRP lock is active.
Click to expand...
Click to collapse
If you do get it to work after Enabling OEM Unlock, please let us know as your with Chatr, would be beneficial information knowing that another provider works also other than Wind (Freedom Mobile).
Thanks and Good Luck!
VonLigenstein said:
is it better, more wise to download the latest version of Supersu from the google play store and use that one, as I notice the one in the zip has a 2008 date
Click to expand...
Click to collapse
I would agree to update SuperSU from the Play Store after install. The version I included in the zip is 2.78 SR1, dated Sep 15 2016. Due to the complexity of the process, I have not tested an updated version, therfore have not included it in the guide.
4o4 said:
Just posting to confirm that OP's instructions worked flawlessly for me. I had already soft bricked it once using another method, recovered from that, and then found this thread. Thanks a bunch for the tutorial!
Click to expand...
Click to collapse
Your welcome, glad to help
Just wanted to say this worked for me, except I was having trouble booting into the Teamwin screen.
What I did was skip the end of step 9 where it says to let your phone reboot fully, instead I pulled the battery and the usb cord and forced it off, then went straight into recovery mode, never letting the phone reboot properly. Was able to get to the Teamwin screen just fine after. Everything else worked like a charm.
(Bought phone at Costco in Canada for use on Koodo.)
Mr Minister
[email protected] said:
Just wanted to say this worked for me, except I was having trouble booting into the Teamwin screen.
What I did was skip the end of step 9 where it says to let your phone reboot fully, instead I pulled the battery and the usb cord and forced it off, then went straight into recovery mode, never letting the phone reboot properly. Was able to get to the Teamwin screen just fine after. Everything else worked like a charm.
(Bought phone at Costco in Canada for use on Koodo.)
Click to expand...
Click to collapse
Yeeesss!!! That worked for me as well!
I've got my SM-J120W at Costco and I'm with Chatr
Yeeesss!!! That worked for me with pulling the battery at end of step 9 before reboot

J3 Hard Brick

**Please move to correct forum if not allowed*
Samsung J3 - J337P > Windows 10
Will not boot into download mode, Will not boot into recovery.
Power on > SAMSUNG J3 screen > No boot. Screen just flashes. No logo after the initial J3 screen.
Have tried every button combination / plugging USB in trick I can think of in an attempt to get to download mode.
Phone immediately attempts to boot when plugged in through USB. Im sure its just trying to display the charging screen but it doesn't even do that.
Samsung drivers are installed but do not see any USB recognition in Device Manager.
Any ideas for this newly acquired paper weight?
did you try adb or fastboot? just because its not showing in windows doesn't mean its not being seen...
i finally got it to boot into download mode by holding VOL down and the home key while plugging the usb in. flashed to stock rom with odin. not rooted but also not useless now.
I am having similar problems although self-induced. I had messed up my J3 Achieve so that it wouldn't boot. So, I tried reloading the stock firmware but had problems. I ended up loading the combination firmware factory binary. But, now I cannot get it into Download Mode to use ODIN for another firmware update. It keeps going in to the Unknown Power or Upload Mode. ODIN sees the phone in that mode but won't connect to load files.
The Factory Binary has a place to do DownloadMode, but it says Enter Password. So, I have no idea what the password would be and coannot find any documentation on the service firmware (assuming they use this at the factory to test). I can get to recovery, which will let me load from SD or ADB. I have barely used ADB and couldn't get it to connect. So, I need some guidance. Hopefully I didn't totally brick it, although I only paid about $60 for it and can get most of that back for parts.
Ideas?
OK, I got the stock ROM reloaded - finally. Now, however, I'm back to the problem that started all of these problems in the first place. When I flash TWRP, the phone won't boot. It shows the initial screen and then goes into a mode where it is either black or dark gray (momentary flashes like it's trying to do something). I've verified my version of TWRP (released in October). Any ideas how to flash this one correctly?
BrianN_Cols_OH said:
I am having similar problems although self-induced. I had messed up my J3 Achieve so that it wouldn't boot. So, I tried reloading the stock firmware but had problems. I ended up loading the combination firmware factory binary. But, now I cannot get it into Download Mode to use ODIN for another firmware update. It keeps going in to the Unknown Power or Upload Mode. ODIN sees the phone in that mode but won't connect to load files.
The Factory Binary has a place to do DownloadMode, but it says Enter Password. So, I have no idea what the password would be and coannot find any documentation on the service firmware (assuming they use this at the factory to test). I can get to recovery, which will let me load from SD or ADB. I have barely used ADB and couldn't get it to connect. So, I need some guidance. Hopefully I didn't totally brick it, although I only paid about $60 for it and can get most of that back for parts.
Ideas?
Click to expand...
Click to collapse
I know you've fixed this but the way to get it to download mode when you get the upload screen is by holding down vol - , power and home button. Once the screen goes blank continue to hold down the home button and let off either the vol- and hold the home button, or hold vol - still and home button. It will then boot into download mode.
---------- Post added at 12:44 PM ---------- Previous post was at 12:41 PM ----------
BrianN_Cols_OH said:
OK, I got the stock ROM reloaded - finally. Now, however, I'm back to the problem that started all of these problems in the first place. When I flash TWRP, the phone won't boot. It shows the initial screen and then goes into a mode where it is either black or dark gray (momentary flashes like it's trying to do something). I've verified my version of TWRP (released in October). Any ideas how to flash this one correctly?
Click to expand...
Click to collapse
That TWRP build doesn't work. I have created a build that works only functions arent working properly so i just need to edit some things then I will upload it here.

Tab S6 stuck in bootloop, can't get to recovery mode

My Tab S6 tried to auto-install an update yesterday (it is rarely connected to Wifi/internet). It then rebooted. Since then, it's been stuck in a boot loop.
It will display the "Samsung Galaxy Tab S6 | Secured By Knox" logo screen for a few seconds, then switch to the blue "Installing System Update" screen (with the android logo). Installing System Update gets to 28% and stops. Then the rotating icon on the android freezes. Then the device reboots and starts all over again.
Edit: the tablet is 100% stock. It's not been rooted or had any custom ROMs loaded.
I have tried getting to recovery mode, by holding power+volup while it boots. This doesn't seem to change the behavior at all. Any advice is much appreciated.
Fedge7 said:
My Tab S6 tried to auto-install an update yesterday (it is rarely connected to Wifi/internet). It then rebooted. Since then, it's been stuck in a boot loop.
It will display the "Samsung Galaxy Tab S6 | Secured By Knox" logo screen for a few seconds, then switch to the blue "Installing System Update" screen (with the android logo). Installing System Update gets to 28% and stops. Then the rotating icon on the android freezes. Then the device reboots and starts all over again.
Edit: the tablet is 100% stock. It's not been rooted or had any custom ROMs loaded.
I have tried getting to recovery mode, by holding power+volup while it boots. This doesn't seem to change the behavior at all. Any advice is much appreciated.
Click to expand...
Click to collapse
can you shut it down? try volume down and power button ? if it don't shut down, do this soon as it reboots, hold volume up and down and plug in usb cable to desktop/laptop usb port! it will boot into download mode!
N1NJATH3ORY said:
can you shut it down? try volume down and power button ? if it don't shut down, do this soon as it reboots, hold volume up and down and plug in usb cable to desktop/laptop usb port! it will boot into download mode!
Click to expand...
Click to collapse
I can't actually shut it down. If I start holding power+voldown right after it boots, the tablet does reboot before getting stuck at 28%. But it reboots--it doesn't power off.
I tried download mode and that actually seemed to work! Specifically, I left the tablet overnight in the reboot loop until the battery drained. Just now, I held down volup+voldown and plugged it into my laptop. I got the green "Warning/Custom OS" screen and then pressed volup to continue. The tablet rebooted pretty quickly after that (I'm guessing due to low battery) so I didn't get a good look at the download mode options.
Once I'm in download mode, can I factory reset the tablet? I don't need to preserve any data/apps/settings.
Fedge7 said:
I can't actually shut it down. If I start holding power+voldown right after it boots, the tablet does reboot before getting stuck at 28%. But it reboots--it doesn't power off.
I tried download mode and that actually seemed to work! Specifically, I left the tablet overnight in the reboot loop until the battery drained. Just now, I held down volup+voldown and plugged it into my laptop. I got the green "Warning/Custom OS" screen and then pressed volup to continue. The tablet rebooted pretty quickly after that (I'm guessing due to low battery) so I didn't get a good look at the download mode options.
Once I'm in download mode, can I factory reset the tablet? I don't need to preserve any data/apps/settings.
Click to expand...
Click to collapse
You cannot reset the tablet from Download mode afaik- You need to enter Recovery Mode to do that.
You can however, flash stock from Download mode using Odin (3.13.3 is best). If you're not confident with doing that, your best option is Factory Reset in Recovery Mode. Hold Volume Up and Power when the Tablet is booting, let go when you see the Samsung logo. The timing can be tricky, but you should be able to do it. Also, you can force a reboot with Volume Down and Power.
Alternatively, if factory reset doesn't work, since you're completely stock, you will still be covered under warrenty.
bartleby999 said:
your best option is Factory Reset in Recovery Mode. Hold Volume Up and Power when the Tablet is booting, let go when you see the Samsung logo.
Click to expand...
Click to collapse
Thanks for the suggestion. I have tried this many many times. I've tried letting go of the buttons at different times. I've tried holding volup while letting go of power. I've tried this a ton of different ways, and no matter what, the tablet always shows the "Installing system update" screen. Some googling has led me to believe that sometimes, when performing a factory reset, the "Installing system update" screen shows up right before the normal recovery screen. Is it possible that the tablet is trying to get to recovery mode, but can't get past this first step?
Fedge7 said:
Is it possible that the tablet is trying to get to recovery mode, but can't get past this first step?
Click to expand...
Click to collapse
Honestly, I don't know - I'm not an expert but I guess it's possible that the update failed and corrupted both System and Recovery.
You'll be covered under warrenty, so maybe just return the Tablet from where you purchased or direct to Samsung, could take a while given the current situation though I guess. If you have a PC, then I think the best option would be to just flash stock yourself, since that's probably all Samsung will do. Even if that doesn't work you'd still be covered under warrenty, as far as I'm aware attempting to flash stock doesn't trip Knox.
Here is solution to unbrick your device!!!
Fedge7 said:
My Tab S6 tried to auto-install an update yesterday (it is rarely connected to Wifi/internet). It then rebooted. Since then, it's been stuck in a boot loop.
...
Edit: the tablet is 100% stock. It's not been rooted or had any custom ROMs loaded.
I have tried getting to recovery mode, by holding power+volup while it boots. This doesn't seem to change the behavior at all. Any advice is much appreciated.
Click to expand...
Click to collapse
Despair not...I have just come from resolving this exact situation not 30 minutes ago. I'd been trying to flash (using Odin as I decided to stay on Stock and not root this device, for a change) the latest OneUI2.1 releases for my device (SM-T865 - LTE version) and boom in the middle of the Odin update, the flash just failed...I then couldn't reboot and get into neither Recovery, nor Download Mode because it appears my bootloader and recovery both got corrupted.
Here's what you need....
1. Odin app for PC (am on Windows)
2. Your device's Stock firmware (sammobile firmware archive)
3. You will need someone to help you boot the device directly into Download mode (and this is the tricky part because for most of us we are used to get into Bootloader by using the key combination (from Powered Off device) Vol+ and Power On at the same time to get into stock recovery and then scrolling down to option 2 in this menu, "Reboot to Bootloader". Well now you are going to boot directly into Bootloader mode. Here's how you do it...
4. Get your friend to line up the USB-C cable into the port of the device, but DO NOT press it in...yet
5. Press Power off and Vol- buttons at the same time to turn off the device
6. And now you have to to be super fast: if device starts to turn on on its own, YOU press and hold Vol+ and Vol- both at the same time while YOUR FRIEND pushes the USB cable fully into the port - you should now have booted directly into Download mode. (if not repeat this, and remember to be super fast and sync with your friend pushing in the USB cable)...
7. When you get into Download mode, then you are home and dry...
8. Select ONLY the Bootloader file (BL...XX...) in Odin, make sure only "reset time" and "reboot" are ticked, and flash
9. When device reboots, press Vol+ and Power combo to get back into Bootloader mode again...but I think device will reboot into Download mode on its own
10. Now select all the files from your Stock file into the various tabs (BL, CP, CSC, AP...) do not select HOME_CSC as we want to flush this device clean...
11. Flash, and voila...success - you will have lost all your data but rather that than losing the device...
12. Feedback here and let us know if this works? For reference for others in the future...
FYI, I got in this situation, and the previous post did work for me, just takes good timing! Thanks!!!!
Same issue today for me. My tablet showed different screen with green and red text, it allowed me to delete app data, then booted into safe mode, then i had to do factory reset and now i am screwed, as it is refusing to restore any apps and their settings. I will try to flash it back to Android 9, maybe then it will do the restore. I forgot to do any manual backup to SD or so.
Edit: the device upgraded to 10, but reset itself after about 10 minutes of use.
Edit2: i found what caused it. It is caused by Nova Launcher, if i try to set wallpaper.
Just found a news article that there is a RGB/sRGB problem with wallpapers. It might be the problem i had.
I am adding a screenshot of the result.
Yeah, I had that kind of reboot loop from a wallpaper that I downloaded
Moe5508 said:
Here is solution to unbrick your device!!!
Despair not...I have just come from resolving this exact situation not 30 minutes ago. I'd been trying to flash (using Odin as I decided to stay on Stock and not root this device, for a change) the latest OneUI2.1 releases for my device (SM-T865 - LTE version) and boom in the middle of the Odin update, the flash just failed...I then couldn't reboot and get into neither Recovery, nor Download Mode because it appears my bootloader and recovery both got corrupted.
Here's what you need....
1. Odin app for PC (am on Windows)
2. Your device's Stock firmware (sammobile firmware archive)
3. You will need someone to help you boot the device directly into Download mode (and this is the tricky part because for most of us we are used to get into Bootloader by using the key combination (from Powered Off device) Vol+ and Power On at the same time to get into stock recovery and then scrolling down to option 2 in this menu, "Reboot to Bootloader". Well now you are going to boot directly into Bootloader mode. Here's how you do it...
4. Get your friend to line up the USB-C cable into the port of the device, but DO NOT press it in...yet
5. Press Power off and Vol- buttons at the same time to turn off the device
6. And now you have to to be super fast: if device starts to turn on on its own, YOU press and hold Vol+ and Vol- both at the same time while YOUR FRIEND pushes the USB cable fully into the port - you should now have booted directly into Download mode. (if not repeat this, and remember to be super fast and sync with your friend pushing in the USB cable)...
7. When you get into Download mode, then you are home and dry...
8. Select ONLY the Bootloader file (BL...XX...) in Odin, make sure only "reset time" and "reboot" are ticked, and flash
9. When device reboots, press Vol+ and Power combo to get back into Bootloader mode again...but I think device will reboot into Download mode on its own
10. Now select all the files from your Stock file into the various tabs (BL, CP, CSC, AP...) do not select HOME_CSC as we want to flush this device clean...
11. Flash, and voila...success - you will have lost all your data but rather that than losing the device...
12. Feedback here and let us know if this works? For reference for others in the future...
Click to expand...
Click to collapse
Bravo!!
Works for me.
Many thanks
I can get into download mode. But it kicks me out within a few seconds. Any help please
Moe5508 said:
Here is solution to unbrick your device!!!
Despair not...I have just come from resolving this exact situation not 30 minutes ago. I'd been trying to flash (using Odin as I decided to stay on Stock and not root this device, for a change) the latest OneUI2.1 releases for my device (SM-T865 - LTE version) and boom in the middle of the Odin update, the flash just failed...I then couldn't reboot and get into neither Recovery, nor Download Mode because it appears my bootloader and recovery both got corrupted.
Here's what you need....
1. Odin app for PC (am on Windows)
2. Your device's Stock firmware (sammobile firmware archive)
3. You will need someone to help you boot the device directly into Download mode (and this is the tricky part because for most of us we are used to get into Bootloader by using the key combination (from Powered Off device) Vol+ and Power On at the same time to get into stock recovery and then scrolling down to option 2 in this menu, "Reboot to Bootloader". Well now you are going to boot directly into Bootloader mode. Here's how you do it...
4. Get your friend to line up the USB-C cable into the port of the device, but DO NOT press it in...yet
5. Press Power off and Vol- buttons at the same time to turn off the device
6. And now you have to to be super fast: if device starts to turn on on its own, YOU press and hold Vol+ and Vol- both at the same time while YOUR FRIEND pushes the USB cable fully into the port - you should now have booted directly into Download mode. (if not repeat this, and remember to be super fast and sync with your friend pushing in the USB cable)...
7. When you get into Download mode, then you are home and dry...
8. Select ONLY the Bootloader file (BL...XX...) in Odin, make sure only "reset time" and "reboot" are ticked, and flash
9. When device reboots, press Vol+ and Power combo to get back into Bootloader mode again...but I think device will reboot into Download mode on its own
10. Now select all the files from your Stock file into the various tabs (BL, CP, CSC, AP...) do not select HOME_CSC as we want to flush this device clean...
11. Flash, and voila...success - you will have lost all your data but rather that than losing the device...
12. Feedback here and let us know if this works? For reference for others in the future...
Click to expand...
Click to collapse
Hi,
Really need your help, after I updated my firmware using Odin, updated BL, AP, CP, CSC, my tab cannot boot up stuck in logo. Doing the Power + volume up leads me to different screen now. I cannot access recovery mode or download page anymore,
What must I do? Pleasssee help. Added the pic, after doing hard reset (power + vol up)
I cannot connect back to Odin also. Always setup connection failed.
Please help. Really messed up big time
Just a thought... Can this be restored from service center?
Thank you in advance.
I have the same problem with a Tab S6 Lite, it is in bootloop and does not let me enter the recovery mode, I can go into download mode and I flashed the latest original firmware Android11, Android10 etc., . I tried them all but always goes in bootloop, and also the bootloop occurs only if I connect the usb cable to the PC, without any sign of life. Do I still have hopes or have I compromised the motherboard?
The reason for all this is because I had followed a guide to give root permissions with magisk, I did everything right, only that the guide was with Android10, while I had Android11 and I was deceived by the fact that in the title of the guide there was written "guide 2021"
, so I did not check the compatibility of operating systems, I was a fool, I know, I hope so much that I did nothing irretrievable, it's my son's tablet!
Genpis said:
I have the same problem with a Tab S6 Lite, it is in bootloop and does not let me enter the recovery mode, I can go into download mode and I flashed the latest original firmware Android11, Android10 etc., . I tried them all but always goes in bootloop, and also the bootloop occurs only if I connect the usb cable to the PC, without any sign of life. Do I still have hopes or have I compromised the motherboard?
The reason for all this is because I had followed a guide to give root permissions with magisk, I did everything right, only that the guide was with Android10, while I had Android11 and I was deceived by the fact that in the title of the guide there was written "guide 2021"
, so I did not check the compatibility of operating systems, I was a fool, I know, I hope so much that I did nothing irretrievable, it's my son's tablet!
Click to expand...
Click to collapse
Did you use HOME CSC or the non HOME CSC when flashing?
Genpis said:
I have the same problem with a Tab S6 Lite, it is in bootloop and does not let me enter the recovery mode, I can go into download mode and I flashed the latest original firmware Android11, Android10 etc., . I tried them all but always goes in bootloop, and also the bootloop occurs only if I connect the usb cable to the PC, without any sign of life. Do I still have hopes or have I compromised the motherboard?
The reason for all this is because I had followed a guide to give root permissions with magisk, I did everything right, only that the guide was with Android10, while I had Android11 and I was deceived by the fact that in the title of the guide there was written "guide 2021"
, so I did not check the compatibility of operating systems, I was a fool, I know, I hope so much that I did nothing irretrievable, it's my son's tablet!
Click to expand...
Click to collapse
Try to install a castom rooted rom which has pre installed also Twrp.
[MAGISK Rom / Firmware base convertor) 420rom-T860/5 - V13.3- CUE1 - ANDROID 10 - OneUI 3.1 - Sec Patch 05/2021 - Released 06/07/2021
WELCOME TO 420 ROM - MAGISK ROM FOR SAMSUNG GALAXY TAB S6 WiFi/4G (T860/5)! 420rom Telegram-Group: Please bear in mind that things will be added as and when my learning and time permits (being a dad with a family and having ADHD myself means...
forum.xda-developers.com
Download the android 11 last rooted rom from there. You install it with odin as as a normal original rom.
Disable in odin auto reboot. After rom install, restart manually and press the correct buttons immediately to boot in Twrp and not to system. Format (not wipe) data from there and reboot to system. If you are lucky it will work..
(I hope you unlocked bootloader before try to root. If you haven't unlocked bootloader this won't work also).
Moe5508 said:
Here is solution to unbrick your device!!!
Despair not...I have just come from resolving this exact situation not 30 minutes ago. I'd been trying to flash (using Odin as I decided to stay on Stock and not root this device, for a change) the latest OneUI2.1 releases for my device (SM-T865 - LTE version) and boom in the middle of the Odin update, the flash just failed...I then couldn't reboot and get into neither Recovery, nor Download Mode because it appears my bootloader and recovery both got corrupted.
Here's what you need....
1. Odin app for PC (am on Windows)
2. Your device's Stock firmware (sammobile firmware archive)
3. You will need someone to help you boot the device directly into Download mode (and this is the tricky part because for most of us we are used to get into Bootloader by using the key combination (from Powered Off device) Vol+ and Power On at the same time to get into stock recovery and then scrolling down to option 2 in this menu, "Reboot to Bootloader". Well now you are going to boot directly into Bootloader mode. Here's how you do it...
4. Get your friend to line up the USB-C cable into the port of the device, but DO NOT press it in...yet
5. Press Power off and Vol- buttons at the same time to turn off the device
6. And now you have to to be super fast: if device starts to turn on on its own, YOU press and hold Vol+ and Vol- both at the same time while YOUR FRIEND pushes the USB cable fully into the port - you should now have booted directly into Download mode. (if not repeat this, and remember to be super fast and sync with your friend pushing in the USB cable)...
7. When you get into Download mode, then you are home and dry...
8. Select ONLY the Bootloader file (BL...XX...) in Odin, make sure only "reset time" and "reboot" are ticked, and flash
9. When device reboots, press Vol+ and Power combo to get back into Bootloader mode again...but I think device will reboot into Download mode on its own
10. Now select all the files from your Stock file into the various tabs (BL, CP, CSC, AP...) do not select HOME_CSC as we want to flush this device clean...
11. Flash, and voila...success - you will have lost all your data but rather that than losing the device...
12. Feedback here and let us know if this works? For reference for others in the future...
Click to expand...
Click to collapse
Why flashing only the bootloader first? At the moment I'm trying to recover my s20 fe from a bootloop without losing my data
sosimple said:
Try to install a castom rooted rom which has pre installed also Twrp.
[MAGISK Rom / Firmware base convertor) 420rom-T860/5 - V13.3- CUE1 - ANDROID 10 - OneUI 3.1 - Sec Patch 05/2021 - Released 06/07/2021
WELCOME TO 420 ROM - MAGISK ROM FOR SAMSUNG GALAXY TAB S6 WiFi/4G (T860/5)! 420rom Telegram-Group: Please bear in mind that things will be added as and when my learning and time permits (being a dad with a family and having ADHD myself means...
forum.xda-developers.com
Download the android 11 last rooted rom from there. You install it with odin as as a normal original rom.
Disable in odin auto reboot. After rom install, restart manually and press the correct buttons immediately to boot in Twrp and not to system. Format (not wipe) data from there and reboot to system. If you are lucky it will work..
(I hope you unlocked bootloader before try to root. If you haven't unlocked bootloader this won't work also).
Click to expand...
Click to collapse
Any tips in recovering my stock s20 fe from a bootloop without losing data? already tried Odin but without success the first try
jointer said:
Same issue today for me. My tablet showed different screen with green and red text, it allowed me to delete app data, then booted into safe mode, then i had to do factory reset and now i am screwed, as it is refusing to restore any apps and their settings. I will try to flash it back to Android 9, maybe then it will do the restore. I forgot to do any manual backup to SD or so.
Edit: the device upgraded to 10, but reset itself after about 10 minutes of use.
Edit2: i found what caused it. It is caused by Nova Launcher, if i try to set wallpaper.
Click to expand...
Click to collapse
did you managed to not lose your data?
jrdef said:
Any tips in recovering my stock s20 fe from a bootloop without losing data? already tried Odin but without success the first try
Click to expand...
Click to collapse
Wiping cache partition in Recovery and reflashing the firmware are basically your only 2 options
jrdef said:
Any tips in recovering my stock s20 fe from a bootloop without losing data? already tried Odin but without success the first try
Click to expand...
Click to collapse
Flash in odin the same rom you had. There are 2 csc files in rom, which you use 1 in odin one. Try use the "home csc". Home csc keep KEEPS your data. If you're lucky it may work. (It would work in keeping your data 100% if your rom was ok. Because it isn't you have some changes to work.).
You must try with same rom or newer.
CSC – If you flash the CSC file, it’ll perform a factory reset of your Galaxy device and wipe all data while installing a new firmware to bring your device to the same state as it was when you purchased it. Go with CSC if you want a clean installation.
HOME_CSC – On the other hand, if you want to keep your Samsung phone’s data and settings even flashing the stock firmware, you can select the HOME_CSC file.

Categories

Resources