Related
First, props to TeamWin, joel.bourquard, theintelligent, and maybe a few others I'm not aware of...
Second, these are Windows instructions. If you have another OS, you can open the batch files and type the commands inside (or paste them) one by one.
Third, keep in mind that the current temp root is NOT a full root even WHEN it is in place... so don't expect too much! This method has also been modified (by others) so that it does not "randomly" reset and it sticks until the next restart. As a result of how that works, however, even fewer apps recognize root with this method but some do!
Most of this is just other people's work: stuff from several different posts repackaged in a way that I found very easy to use. So I don't take credit for most of the contents, although I did modify the batch files to take care of a timing issue that was causing a fail on most machines. In the end, you should be able to use the attached prepare.bat file to prepare your phone once and then you can use root.bat after each reboot to restore temp root. Create a shortcut to root.bat on your desktop and you can just plug your phone in, click the icon, and you're (re)rooted in about 8 seconds.
The instructions are simple but I elaborate below to try to hit all the stumbling blocks. Basically you just run prepare.bat the first time you do this and from that point forward, you only need to run root.bat after every restart.
Here are the specific instructions:
THE FIRST TIME ONLY:
(1) Unzip contents of the attached ZIP to a folder you'll remember on your hard drive.
(2) Plug your phone in via USB and set it to "charge only" with "USB debugging" under "Settings", "Applications", "Development" turned on. It's best to do this after a fresh (full, not fast) boot. Your phone should be in this mode each time you connect it to root it. Trust me, if you've been using your phone for a while, reboot it first, then wait a few minutes for it to stabilize, THEN do this routine... saves a lot of headaches.
(3) Go to the folder where you unzipped the files in (1) and run prepare.bat. I prefer to do it in a DOS box but you should be able to just use Explorer and double click on the prepare.bat file.
(4) The first thing these batch files do is a check to make sure your computer can see the phone. If your phone isn't in the list, Ctrl-C and break out of the batch file. You'll have to correct the problem which will most likely be an issue with the HTC drivers. If your phone is not found, try these x64 drivers... or these if you're running a 32 bit OS. To install these, go to Control Panel and click on your Android device and do "Update Drivers" and browse to the location of the drivers you downloaded.
(5) Assuming your phone is on the list, everything should be ready to go. Press enter and the batch file will proceed and it will root your phone.
AFTER DOING THE ABOVE ONCE, AFTER EACH REBOOT:
(1) Attach phone and double click the root.bat file.
(2) Again, verify that your phone is on the list (proves your PC can see the phone). If so, press enter and the phone will be RErooted.
That's it! Works for me. Keep in mind that temp root is NOT a full root! Many apps will not run (won't see root) but that's just the nature of the current temp root. But some apps do work. Barnacle WiFi does for example: although sometimes it take two "start" presses to get it to connect as the first one sometimes produces errors. People say Titanium Backup and some other apps work: I haven't personally tested them. As temp root is really for dev and testing, test what you want and see if it works.
Hope this helps some of us to get a quick and easy temp root. If any issues are found, I'd be glad to modify this initial post and/or modify the batch files if any errors are found.
Mike
I can't get to the site to download the 64-bit drivers for windows. Anybody has an alternate links? Thanks.
Does this really work? How is this thread not blowing up??
vWvSTATICvWv said:
Does this really work? How is this thread not blowing up??
Click to expand...
Click to collapse
Really! Anyone out there? I expected to come back from lunch to find questions I needed to answer or maybe a suggested modification or two. This has been working for me for over 12 hours now. No restarts. No reverting to non-root. Barnacle Wifi Tether is still working. And the best thing is, if I have to restart the phone for some reason, I connect it to my computer, click, and 8 seconds later it is rooted again and I unplug it and go on my way.
Mike
can you run a wireless tethering app after temp root?
edit: see mikeyxda's post above this
I was hoping to be able to help some people with the Barnacle WiFi Tether app because a lot of people complain that they didn't get it to work and I suspect I got it to work with some combination of settings. Only problem is: I don't know how my Barnacle settings differ from those other people are using so I wanted to compare with others. Short on time right now but later I'll try to post my entire list of Barnacle settings. They work for me.
Edit: Oh Hell... I have a few minutes, here are my settings:
SSID: Evo 3D Tether
BSSID: <blank>
Wireless Encryption: not enabled (open)
Channel: mine is 6, probably doesn't matter
Custom Wifi Ad-hoc: none
Skip wpa_supplicant: NOT checked
Auto Associate: NOT checked
Access Control: NOT checked
New Client Actions: Notify Checked, nothing else checked
Local Mode: NOT checked
DHCP: Didn't mess with these
NAT: Didn't mess with that either
WAN: rmnet0 (whatever that means)
LAN: Blank
Mike
it seems like the link for the 32bit drivers is down also....
i ran batch files as OP directed, they run successfully, but when i go to start barnacle tether it doesn't have root. same for the "wifi tether for root" app. tried full reboots several times, no help.
os10 said:
i ran batch files as OP directed, they run successfully, but when i go to start barnacle tether it doesn't have root. same for the "wifi tether for root" app. tried full reboots several times, no help.
Click to expand...
Click to collapse
Try making sure fast boot is turned off and then power the phone down and power it back up. Then use the root.bat to reroot. Might not work the first time.
For those having trouble with the driver links, try this link. It's kind of a convoluted mess with countdowns, etc. but seems like the files are there. I haven't verified them yet though.
Mike
Gave it a shot, doesn't quite seem to be working for me.
johnsmusicbox said:
Gave it a shot, doesn't quite seem to be working for me.
Click to expand...
Click to collapse
What is it that isn't working: the rooting process itself or Barnacle? I was hoping to give enough feedback in this thread to get things working for the people who say "it doesn't work" because I've been watching other threads and most of these methods seem to be very inconsistent, meaning, they don't work for a lot of people. My intention was to find the kinks and get it working for the vast majority. If you can give me details like what you see during the process, whether any error messages display, and so on, we might be able to get a more reliable temp root.
Mike
Titanium backup is definitely not working with this.
So what's going on with this? Anyone got it to work?
OK, let's try this. This is a "cleaned up" version of a different method posted in another thread. Comes with 2 batch files. Run root-init the first time and then root-redo each time you restart after that. Let's see if this works better.
Mike
Ok...My guess is that people are scared and don't know exactly what they're flashing. Would you mind sharing the source of your find, Mike? If this does indeed work, I can't see people not using this method. HmMm
*EDIT* I found the source is from XHAUSX
*EDIT 2* IT WORKS!!
Howdy folks,
Yesterday, I was the proud owner of a sleek little TCT.Alcatel OneTouch A554C, formally know as a Virgin Mobile Venture running Android version 2.3.5.
It was successfully and surprisingly easy to root by utilizing 2 cool little apps, Ministro and Poot-Debug.
After root, I subsequently downloaded some root tools (eg., Titanium Backup Pro, Superuser Elite, System App Uninstaller).
That was last week.
Yesterday, I got a bit cocky. I needed to clear up some internal memory so I used "System App Uninstaller" to uninstall a few apps. If I remember correctly, the apps were as follows: Google Maps, Google Maps Street View, Calculator, Digital Clock, Setup Wizard, Android Live Wallpaper, Live Wallpaper Picker, Magic Smoke Wallpaper, Music Visualization Wallpaper, and the TouchPal Keyboard French and Spanish Language Packs.
So far so good, right? However, I believe I may have snarfed-up when I uninstalled the Setup Wizard. But I'll get to that in a minute.
Now with Titanium Backup, I moved some apps to the sd card. Included was the stock launcher, Smart Launcher Pro, SPB Shell, AVG Anti-Virus, and Superuser Elite. Then I rebooted through Titanium Backup and I haven't viewed any pornographic material since!
After reboot, the phone got stuck on the final boot animation frame. I panicked, pulled the battery, booted into recovery then rebooted a 2nd time.
This time it booted to the pull-down lock screen. I unlocked and seen:
"Sorry! The application com.android.setup wizard has stopped unexpectedly. Please try again." Along with a "Force Close" option. I forced closed and the screen went black with the exception of the status bar. The phone is still on but otherwise...nada.
When I press the power button, same thing happens: pull-down lock screen, screen goes black. Or sometimes, it will turn on and boot loop.
Major panic time!!! I booted into recovery again and performed a factory reset to no avail.
Another clue to note: I can connect & access the sd card via usb to desktop.
Also, I did have the good sense to backup all apps, system and user, through ES File Explorer and stored them both on sd card and in the cloud via Yandex Disk prior to this bricking fiasco. Now, what do I do with them? I now realize it was possibly a mistake moving all 3 launchers to the sd card. How do I get the stock launcher back to the phone?
Or, should I:
1- Attempt a base rom reinstall or
2- Attempt a custom rom install or
3- Use it solely as a time piece/mass storage device or
4- Throw it very hard and very ******* far away from me!?
I realize this is an obscure little cheap phone but it's the only one I have. Any valid feedback would be greatly appreciated.
You can go to the Play Store on any browser and choose a launcher to install. Or if you have USB Debugging on, you can side load an launcher apk. Or if you install a custom recovery, you can install another rom or sideload an apk there. Or you can flash the original firmware via SP Flash Tool.
Lots of options and none of them need to be throwing it against the wall.
es0tericcha0s said:
You can go to the Play Store on any browser and choose a launcher to install. Or if you have USB Debugging on, you can side load an launcher apk. Or if you install a custom recovery, you can install another rom or sideload an apk there. Or you can flash the original firmware via SP Flash Tool.
Lots of options and none of them need to be throwing it against the wall.
Click to expand...
Click to collapse
Hmmm...Ok, thanks. Dig your username, by the way.
First thing is, install from play store would be possible if I had data service or if I was able to enable wi-fi. I only have calling & texting service on this phone and as for wi-fi, I can't enable it due to the problem of not being able to access the settings menu. All I have when it does boot, and it only fully boots when it is connected to a PC, is the pull-down lockscreen displaying time, date, status bar and the original wallpaper. Pull it down and the screen goes black with status bar still displayed along with time & battery level.
Secondly, USB debugging was enabled prior to all of this but I panicked & performed a factory reset. Don't think it's still on.
And lastly, is installing either a custom recovery, (which, to be frank, I'm just not that savvy) another rom or flashing original firmware even possible without a PC? Because I only have access to a PC without administrative privileges so therefore...no installing exe's without a password. Maybe this program lab will allow me, quite possibly not.
Hell, would I even still have root after a reset/data wipe?
Thanks, anyway, Esoteric Chaos
Off subject: The Joker was an Agent of Chaos. Loved Heath Ledger as The Joker.
Silver Rivers said:
Hmmm...Ok, thanks. Dig your username, by the way.
First thing is, install from play store would be possible if I had data service or if I was able to enable wi-fi. I only have calling & texting service on this phone and as for wi-fi, I can't enable it due to the problem of not being able to access the settings menu. All I have when it does boot, and it only fully boots when it is connected to a PC, is the pull-down lockscreen displaying time, date, status bar and the original wallpaper. Pull it down and the screen goes black with status bar still displayed along with time & battery level.
Secondly, USB debugging was enabled prior to all of this but I panicked & performed a factory reset. Don't think it's still on.
And lastly, is installing either a custom recovery, (which, to be frank, I'm just not that savvy) another rom or flashing original firmware even possible without a PC? Because I only have access to a PC without administrative privileges so therefore...no installing exe's without a password. Maybe this program lab will allow me, quite possibly not.
Hell, would I even still have root after a reset/data wipe?
Thanks, anyway, Esoteric Chaos
Off subject: The Joker was an Agent of Chaos. Loved Heath Ledger as The Joker.
Click to expand...
Click to collapse
You can go to ANY browser - even on the PC and log into your account and hit Install and it will send the command to your phone to install it. Pretty nifty. But you did say you factory reset, so that isn't actually going to work. Sorry.
The rest of the stuff would require a PC, though I don't think admin rights are needed, so there's that...
If you don't have your phone logged into Google or USB Debugging enabled, you're kind of stuck without a PC.
es0tericcha0s said:
You can go to ANY browser - even on the PC and log into your account and hit Install and it will send the command to your phone to install it. Pretty nifty. But you did say you factory reset, so that isn't actually going to work. Sorry.
The rest of the stuff would require a PC, though I don't think admin rights are needed, so there's that...
If you don't have your phone logged into Google or USB Debugging enabled, you're kind of stuck without a PC.
Click to expand...
Click to collapse
Well, on these PCs it certainly does. I thought I was on track yesterday and tried to install a copy of Odin that I found. Can't install without a frigging admin pass.
Someone else just suggested I try a stock rom flash. Might as well, right? Happen to know where I could find a good reliable copy? That also happens to be free?
Not sure why you were trying to use Odin for a non Samsung phone...?
The stock rom flash would only be possible via PC or if you had a custom recovery installed.
Here's what you would need to do for the Virgin Mobile Venture:
Download CWM: http://www.sendspace.com/file/4gt04i
Download adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download rom: http://goo.im/devs/LeslieAnn/Venture/Stock_Venture.zip - Put on SD card.
Drivers: http://pdanet.co/bin/PdaNetA4150.exe (this program is for USB tethering and installs the adb drivers for your phone as well as many others)
The CWM img will need to be in the folder you unzipped for adb/fastboot. You'll need to boot to fastboot mode by powering on with while holding Volume Up.
Open a terminal prompt and change directories to your adb/fastboot folder. Then run this command:
fastboot flash recovery nameofrecovery.img - fill in the nameofrecovery with whatever the CWM file name is.
(if this doesn't work - make sure that your PC is reading the phone correctly by using the command: fastboot devices . If you don't get anything back, make sure you check the Device Manager for errors. If you have them, try reinstalling the drivers and rebooting the PC)
Then pop the battery out and then reboot to recovery via powering on while holding volume down. Once there, you should be able to do a factory reset and then install the stock rom zip. The volume keys should scroll through selections and the Enter key for accept, or Power if that doesn't work. Not really sure about this particular phone.)
Actually, you might just be able to use adb to install a launcher apk once you have CWM installed. Might be a little easier.
launcher apk must be in adb folder then while in CWM:
adb install nameoflauncher.apk
Note: You can rename zips and apks to be easier to type the commands.
es0tericcha0s said:
Not sure why you were trying to use Odin for a non Samsung phone...?
Click to expand...
Click to collapse
Yeah, me either. I was all over the place yesterday grasping at anything. So Odin is only for Samsungs, huh? Guess I can delete the exe file from my sd.
Right then. I'm about to proceed with your advice. Cross your fingers and toes.
Thanks mate!
The CWM img will need to be in the folder you unzipped for adb/fastboot.
Click to expand...
Click to collapse
and
launcher apk must be in adb folder then while in CWM
Click to expand...
Click to collapse
Wait, what? Please excuse my ignorance, but am I missing something. ADB didn't come in a zip. It's an installer. I think you may have to dumb this down a bit more, mate.
Silver Rivers said:
and
Wait, what? Please excuse my ignorance, but am I missing something. ADB didn't come in a zip. It's an installer. I think you may have to dumb this down a bit more, mate.
Click to expand...
Click to collapse
Sorry, I meant in the folder that it extracts the files too.
es0tericcha0s said:
Sorry, I meant in the folder that it extracts the files too.
Click to expand...
Click to collapse
Right, got it.
Silver Rivers said:
Right, got it.
Click to expand...
Click to collapse
If you can't run the exe file, then let me know, and I'll just upload a zip / folder with the necessary files. You do not need admin access to run the adb commands.
es0tericcha0s said:
If you can't run the exe file, then let me know, and I'll just upload a zip / folder with the necessary files. You do not need admin access to run the adb commands.
Click to expand...
Click to collapse
That would be really cool, actually. But check this out:
I talked someone into allowing me to utilize his laptop. I installed ADB, moved the Launcher APK to the folder suggested, ran the commands but the command prompter responded with "waiting for device" and progressed no further. Could it be a driver issue? I was under the impression that if the PC recognizes your device (which it did) then a new driver install was not necessary.
Dude was real cool about it even though I ran his battery down quite significantly and didn't even accomplish anything.
So, if I had the ADB files then I could just copy them to...say the PC desktop and run the command prompter from there? If so, then yes please upload and I'll just try it that route rather than rely on someone's personal PC. Know what i mean?
I do appreciate all of this. I'm getting quite the education here. If you ever get married, let me know and I'll come and dance as my favor to you.:good:
Peace...I'll return tomorrow.
What mode were you in when trying to install? The laptop had the most up to date drivers? You checked the Device Manager to make sure there was no yellow exclamation mark next to the phone? It's not unheard of for the PC to recognize in one mode, but not load the correct drivers in another, as there are different drivers for the phone depending on if it is booted, in recovery, or download mode or whatever they call it for that phone. Just make sure to get the PDAnet drivers installed and reboot. That should do the trick.
Everything else you should need will be in here:
https://dl.dropboxusercontent.com/u/9903887/adbfastboot.zip
es0tericcha0s said:
What mode were you in when trying to install? The laptop had the most up to date drivers? You checked the Device Manager to make sure there was no yellow exclamation mark next to the phone? It's not unheard of for the PC to recognize in one mode, but not load the correct drivers in another, as there are different drivers for the phone depending on if it is booted, in recovery, or download mode or whatever they call it for that phone. Just make sure to get the PDAnet drivers installed and reboot. That should do the trick.
Everything else you should need will be in here:
https://dl.dropboxusercontent.com/u/9903887/adbfastboot.zip
Click to expand...
Click to collapse
I was in Recovery and I was also attempting to install the just the Launcher versus the entire ROM. And I was also feeling a tad bit rushed, cause dude was right there informing me of his battery status. "Well, it's down to 30%." Then 2 mins later.."Ok, looks like it just fell to 25%."
Haha...so yeah, with him pressuring me, I spaced on checking the device manager. This desktop that I'm on today seems to be cool. Just checked the manager & it informs me that my device is 'working properly'.
Off to give it another bloody joust, mate. Wish me luck...
Can you fully explain how to do this
es0tericcha0s said:
Not sure why you were trying to use Odin for a non Samsung phone...?
The stock rom flash would only be possible via PC or if you had a custom recovery installed.
Here's what you would need to do for the Virgin Mobile Venture:
Download CWM: http://www.sendspace.com/file/4gt04i
Download adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download rom: http://goo.im/devs/LeslieAnn/Venture/Stock_Venture.zip - Put on SD card.
Drivers: http://pdanet.co/bin/PdaNetA4150.exe (this program is for USB tethering and installs the adb drivers for your phone as well as many others)
The CWM img will need to be in the folder you unzipped for adb/fastboot. You'll need to boot to fastboot mode by powering on with while holding Volume Up.
Open a terminal prompt and change directories to your adb/fastboot folder. Then run this command:
fastboot flash recovery nameofrecovery.img - fill in the nameofrecovery with whatever the CWM file name is.
(if this doesn't work - make sure that your PC is reading the phone correctly by using the command: fastboot devices . If you don't get anything back, make sure you check the Device Manager for errors. If you have them, try reinstalling the drivers and rebooting the PC)
Then pop the battery out and then reboot to recovery via powering on while holding volume down. Once there, you should be able to do a factory reset and then install the stock rom zip. The volume keys should scroll through selections and the Enter key for accept, or Power if that doesn't work. Not really sure about this particular phone.)
Actually, you might just be able to use adb to install a launcher apk once you have CWM installed. Might be a little easier.
launcher apk must be in adb folder then while in CWM:
adb install nameoflauncher.apk
Note: You can rename zips and apks to be easier to type the commands.
Click to expand...
Click to collapse
I have a old ass iMac desktop that has not been used in 5plus years at all and I'm a mother of 3 with no clue how to do any of this if you can dumb it down for me that would be very help full as well I have no clue where to download any of the needed files please help. My email is [email protected]
Thank you
Hello All! I'm sorry, I'm very new to this. Can someone please point me in the direction of instructions that I need to follow in order to root my son's Star Wars Nabi? I'm not sure if it's a nabi 2 or not.. I can't find that anywhere. We just bought it for Christmas. The internal storage is used up and the games won't move to the SD card - so, I figured my only option was to root it. There are so many pages out there with root instructions and I'm not sure which ones to use. Any help would be greatly appreciated.
MrsPurchase15 said:
Hello All! I'm sorry, I'm very new to this. Can someone please point me in the direction of instructions that I need to follow in order to root my son's Star Wars Nabi? I'm not sure if it's a nabi 2 or not.. I can't find that anywhere. We just bought it for Christmas. The internal storage is used up and the games won't move to the SD card - so, I figured my only option was to root it. There are so many pages out there with root instructions and I'm not sure which ones to use. Any help would be greatly appreciated.
Click to expand...
Click to collapse
What is the name of the device in the "about tablet" tab in settings?
It's probably closely related to the nabi2S of i were to guess. You can either try a root method like Kingo root or a TWRP method. Since you are the first person I have seen here with a Star Wars I don't have all the answers.
-If you use Kingo there is no backup to help you if something goes wrong.
-If you use TWRP method there may not even be a version of TWRP that will work, and initially you will not want to install TWRP but run it from ram. So the commands will be a bit different then what you see on the forums. With that method though you will have a backup.
aicjofs said:
What is the name of the device in the "about tablet" tab in settings?
It's probably closely related to the nabi2S of i were to guess. You can either try a root method like Kingo root or a TWRP method. Since you are the first person I have seen here with a Star Wars I don't have all the answers.
-If you use Kingo there is no backup to help you if something goes wrong.
-If you use TWRP method there may not even be a version of TWRP that will work, and initially you will not want to install TWRP but run it from ram. So the commands will be a bit different then what you see on the forums. With that method though you will have a backup.
Click to expand...
Click to collapse
It doesn't have a name :/ It has a model number (SNB02-NV7A), an edition number (SNB02-NV7A-US-SW), android version (4.4.2), a kernel version (3.1.10) and then a build and hard ware number.
I appreciate the advice though. Thank you!
MrsPurchase15 said:
I appreciate the advice though. Thank you!
Click to expand...
Click to collapse
SNB02-NV7A is the model number for the NABI2S. It's likely the Nabi2S TWRP will work for the tablet. To use it though you will likely have to unlock the bootloader and that will erase all your personal data on the tablet. It's the safer method since you will have a backup of your tablet, but will require you to get your hands dirty.
You can read through this http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 and see if it's something you want to try.
Using the above linked thread as the basic outline, in general you would:
-Setup adb/fastboot and the windows driver.
-Unlock the bootloader(wiping all personal data on tablet)
-"fastboot boot" NOT "fastboot flash" the Nabi2S TWRP recovery to the tablet RAM.
- backup the recovery, boot, system, and addon(preload) partitions. Then you can always recovery the tablet if something goes wrong, and help others that need to recover their tablet.
-Download SuperSU and flash from TWRP to obtain root.
I can help with more detailed instructions but if it's something that seems uncomfortable to try then I don't want to type it all out. Again a kingo root or other root method will likely give you root, I personally like having a clean backup before beginning and there is none in existence yet.
Thank you so much! I am absolutely willing to try it. I can't do much worse to it then the state it's already in.
MrsPurchase15 said:
Thank you so much! I am absolutely willing to try it. I can't do much worse to it then the state it's already in.
Click to expand...
Click to collapse
Again the Nabi general information thread is going to be the biggest help in understanding what needs to be done. That information is here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 The procedure below isn't as long as it looks I tried to add some troubleshooting stuff along the way.
Best to have a mircoSD card for this well at least 4GB. Start with the microSD in your computer if possible.
1) First you will need to grab all the files you need:
-Drivers: Refer to drivers section #4 in the General Info Thread. Your choice if you want to try PDAnet, NabiLab, or Universal Naked Drivers. The NabiLab drivers are self installing and work pretty good in a lot of situations but not always. Download which ever one you choose to your computer. I'm going to talk about Nabilab and Universal as first resorts, we will revisit PNAnet if you are having driver issues.
-ADB and Fastboot tools. Here it's best to refer to section #6 in the General Thread. Specifically:
Download and install this package(pay attention to where you install this as you will likely need to put files in there later): http://forum.xda-developers.com/showthread.php?t=2317790
From your start menu select "Minimal ADB and Fastboot" this should open a command prompt where you can type commands
If you didn't pay attention or forgot where you installed the files, at the command prompt that opens type "explorer ." The period is important, explorer <space bar> and a period. So type what is between the quotes.
-TWRP for the NABI2S. Get that file here: TWRP for Nabi2S
After this step you should have downloaded 3 files and the ADB/fastboot files you should have installed. That leaves the remaining 2 files. One should be NABI2S_TWRP271.img, copy that file to the folder where you installed ADB/fastboot(remember you can find that folder by selecting Minimal ADb and Fastboot from your start menu and typing "explorer ." as explained above.) The remaining file is the which ever driver package you picked. If it's universal naked extract the zip file to a place you know. If it's Nabilab drivers go ahead and install them. PDAnet we will try later if these 2 don't work.
2) Boot the Nabi to fastboot with the USB cable plugged in to your computer. Also open device manager on your computer so you can see when the interface comes up. I don't have a Nabi2S so this may be not exactly right. Start with the tablet off. Press and hold the power button AND the vol up buttons at the same time. At some point you should boot up and have a small text menu in the top corner of the screen.(If that doesn't work try power and vol down buttons). One of the menu items will be fastboot protocol. You will want to highlight that text using the volume keys, and then select it using the volume keys.(again I an not sure which is which. Vol - might change which is highlighted, and vol + will select that line, or vice versa, remember which does does what as you will need it later on). Keep trying combinations or timings if it's not working. When it's right your computer will acknowledge a new device plugged in and the device manager screen should show a fastboot or unknown interface.
3) Getting the drivers working. If you chose the Nabilab drivers they should automatically install, and in device manager you should see and item called Android device, and when expanding that entry some bootloader or fastboot interface(When you see this you should be done with this step). The tablet will also switch the text on the screen to say something like "continue", "bootlader", blah, blah. If you went with universal naked drivers this is where you would locate the unknown or fastboot device with the yellow exclamation mark and manually install the driver by pointing them to the folder you extracted(There could be driver signing issues depending on which version of windows you are using. You will have to google "disable windows driver signature enforcement", but basically you will reboot the computer disabling driver signature enforcement. Hopefully if you picked the Nabilab drivers and they work on your computer this step will be pretty painless and not as long as it looks.
4) Unlocking the bootloader. If you have the command window open now great, if not from your start menu select "Minimal ADB and Fastboot" this should open a command prompt. REMEMBER this step will erase all you data on the tablet, game saves, pictures, etc.
Get ready to acknowledge some text on the tablet itself as you have to be pretty quick using the volume keys to highlight and select(Same function as what you noted in step 2). At the command prompt type:
Code:
fastboot oem unlock
OR
Code:
fastboot -i 0x0489 oem unlock
On the tablet some text will pop up asking yes or no do you really want to unlock the bootloader? The selection is made with the volume keys. You should see some confirmation of erasing tablet and completed.
If this step isn't working when you type the command i.e. "waiting for device" the drivers probably still aren't installed correctly. If something failed in this step you may be forced to reboot the tablet and get back in fastboot mode(step2)
5) Install TWRP. With tablet in fastboot mode. Type at the command prompt:
Code:
fastboot boot NABI2S_TWRP271.img
or
Code:
fastboot -i 0x0489 boot NABI2S_TWRP271.img
If you are getting file not found errors the NABI2S TWRP file isn't in the folder. If all goes right the tablet will boot to TWRP. This is where we may have problems as I'm not sure if the NABI2S TWRP can boot the Star Wars Nabi. If it's not booting then we are pretty much done at this point...
6) Getting SuperSU(root). If the tablet booted TWRP. Download this UPDATE-SuperSU-v2.46.zip. Copy that file to your microSD you have inserted in the computer. When that is done safely eject the card from the computer and put it in the tablet.
7) In TWRP select the "mount" tab and check MicroSD(external storage) and the check box should become checked.
8) Make a backup. Select the "backup" tab in TWRP. You will have the options to backup "recovery" "boot" "system" and "preload(or addon)" select all 4 of those. Then select the backup location as MicroSD(external storage). Swipe to backup.
9) Only if step 8 worked install root. Select the TWRP "install" tab. Back out to the highest level, and find external_storage. The UPDATE SUperSU zip should be there. Select it and swipe to install.
10) Only if the step 8 and 9 worked go to the "reboot" tab and reboot. If they didn't work. Press and hold the power key until the tablet shuts off, and we can troubleshoot. If you rebooted the tablet will take a long time to boot initially since you wiped the tablet and it will have to rebuild data. You can then reset up the tablet.
11) Get superSU from Play Store and verify root.
12) If all this work your backup will likely be a benefit to future users so sharing it might be something to consider.
Well.. I followed everything above and it all appeared to work perfectly - however, I still can't access the microSD card to store games. Any ideas?
MrsPurchase15 said:
Well.. I followed everything above and it all appeared to work perfectly - however, I still can't access the microSD card to store games. Any ideas?
Click to expand...
Click to collapse
Are you using an app to do this(like link2sd)? Or just hoping root alone would allow you to do this?
I was hoping the root would allow me but I take it that's wrong, lol.
MrsPurchase15 said:
I was hoping the root would allow me but I take it that's wrong, lol.
Click to expand...
Click to collapse
Haha. Understood. You do need root to do it, but root is needed for the apps that can make it possible. My kids never had the problem when they had their old Nabi2's so I'm not as much help on the "how to" portion but I understand how the apps work. Read through this thread to gain some understanding of what it takes now that you have root. http://forum.xda-developers.com/showthread.php?t=2086338
There is another way also where you stop using internal storage altogether and use an external by editing the ramdisk but it has some limitations as well.
This was awesome i have the same star wars edition and everything works well i even made a backup which i can post and i used the 3.0.1.3 kernel backup to restore the tablet and it still worked
**does not yet work for 7.1.1**
Using a PC to root seems like moving backwards compaired to a 'one click' apk. but we're already at the PC to flash eng_boot, plus this new method is so much faster...so here we go
Features:
SuperSU 2.82
Init.d
Wifi fix
Flashlight fix
Issues:
For the wifi fix I just copied an edited J320a build.prop
So J320AZ users will see J320A in about device, and will have to reassign notification sounds. (Hope to fix it in the future)
Needed Files:
Odin
Root_J320A.zip
Procedure:
1. Unzip both files.
2. Run Odin click the 'AP' button.
3. Navigate to Root_J320A/bin and select sm-j320a_Engroot_601PJ2.tar and press "Start" (make sure NOT to check re-partition)
4. After it completes sucessfully, leave the phone hooked to the pc... and then wait, wait a good 2 or 3 minutes after its booted.
5. Once 2 or 3 minutes has gone by you can navigate to the Root_J320A folder.
6. There you'll see root.bat, double click that let it do its thing.
6a. If at any time during the script you see "adb out of date. killing..." hit the x to close the window and restart the script.
*This may work on J320AG models but make sure you check oem unlock from dev settings first... and let us know how it goes
Enjoy
- D
Credits:
@ashyx - eng_boot
@Sh$llNinjA - eng_root
@sjowns - flashlight fix
@Chainfire - SuperSU
@Ryuinferno - init.d script
Excellent! This works perfectly! Thank you so much for posting this.
J320A PC9 worked perfectly!
March security patch
Hi man, this method support the march security patch, or are still in january security patch
I tested on AQD2 so it'll work on AQC1 too.
I assume it'll work for all 6.0 updates we get.
I tested on AQD2 so it'll work on AQC1 too.
I assume it'll work for all 6.0 updates we get.
This works perfectly. Thank you!
I suggest you put 'root' in the tile, otherwise google cannot find it.
I googled 'j320a root', google only links to ashyx's post which doesn't... well maybe only mine phone.
I am new to this root bit.
Possibly I have done something wrong. I read your instructions carefully and quit didn't understand where the unzipped files should go. Do any of these have to be placed in the phone's directory?
Failed on my AT&T SM-J320A
I wonder if it has anything to do with the new update pushed out recently
@JeffF73
Run Odin and Click ap.
Navigate to the directory where you unzipped root_j320a.zip.
In that folder you'll see a bin folder, inside that is sm-j320a_Engroot_601PJ2.tar, which needs flashed to the phone.
Once that's complete, let it boot and wait.
Then run root.bat
DamienMc said:
@JeffF73
Run Odin and Click ap.
Navigate to the directory where you unzipped root_j320a.zip.
In that folder you'll see a bin folder, inside that is sm-j320a_Engroot_601PJ2.tar, which needs flashed to the phone.
Once that's complete, let it boot and wait.
Then run root.bat
Click to expand...
Click to collapse
Hello DamienMc Thank you for your reply and help. I figured it out. I had to put my phone in "Download Mode" by holding down Volume Down, Home Button and Power button while booting. Then I was able to use Odin without failing. This solved all my problems thank you
Is it safe to flash this after doing this?
https://mega.nz/#!D8hSzLaa!pDugFwQ0NyGBLy36j1643bI3e4f9xog7US8UTTkZ8SU
sonic0504 said:
Is it safe to flash this after doing this?
https://mega.nz/#!D8hSzLaa!pDugFwQ0NyGBLy36j1643bI3e4f9xog7US8UTTkZ8SU
Click to expand...
Click to collapse
Yes, that has selinux set to permissive as well, although there's no real difference. The build.prop differences are noticable tho...I plan on doing an update to this, just have to figure out how to tell if it's A or AZ from adb
Ragheb Alama said:
Hi man, this method support the march security patch, or are still in january security patch
Click to expand...
Click to collapse
Yes, it works for QC1. However, you may need to replace build.prop in /bin from QC1 with WiFi fix before root.
I did notice that after root, the contents of /Android/data folders in both internal storage and external sd card are hidden from PC. Before root, both are visible from PC. Any thoughts about what cause the changes?
Will this work on July security patch?
DamienMc said:
Yes, that has selinux set to permissive as well, although there's no real difference. The build.prop differences are "noticeable" tho...I plan on doing an update to this, just have to figure out how to tell if it's A or AZ from adb
Click to expand...
Click to collapse
Thanks, I just needed to install this to use adb to uninstall an update I did to System UI because it would continuously crash.
SBCarr said:
Yes, it works for QC1. However, you may need to replace build.prop in /bin from QC1 with WiFi fix before root.
I did notice that after root, the contents of /Android/data folders in both internal storage and external sd card are hidden from PC. Before root, both are visible from PC. Any thoughts about what cause the changes?
Will this work on July security patch?
Click to expand...
Click to collapse
Probably the eng_boot we use, it breaks the flashlight and wifi passwords too... it does work on j320a July update, so I assume it'll work on j320az update too
@DamienMc Dude, thanks for ur post, but i tried 2 times and fail, i got stuck at logo, i had to reflash to stock but now my build.prop is gone or corrupted, my phone says model unknow, i cant even use hidden menus like *#06, etc, i need the original file to fix it please. model SM-J320A RUNING QC1
ScSoluciones said:
@DamienMc Dude, thanks for ur post, but i tried 2 times and fail, i got stuck at logo, i had to reflash to stock but now my build.prop is gone or corrupted, my phone says model unknow, i cant even use hidden menus like *#06, etc, i need the original file to fix it please. model SM-J320A RUNING QC1
Click to expand...
Click to collapse
Reflash CSC as well, that'll wipe your device but fix your problem.
Are you sure you waited long enough after the phone booted before rooting?
If at any time during the script you see it say "adb server out of date. Killing..." something is wrong. You can x the command prompt and do root.bat again.
DamienMc said:
Using a PC to root seems like moving backwards compaired to a 'one click' apk. but we're already at the PC to flash eng_boot, plus this new method is so much faster...so here we go
Features:
SuperSU 2.82
Init.d
Wifi fix
Flashlight fix
Issues:
For the wifi fix I just copied an edited J320a build.prop
So J320AZ users will see J320A in about device, and will have to reassign notification sounds. (Hope to fix it in the future)
Needed Files:
Odin
Root_J320A.zip
Procedure:
1. Unzip both files.
2. Run Odin click the 'AP' button.
3. Navigate to Root_J320A/bin and select sm-j320a_Engroot_601PJ2.tar and press "Start" (make sure NOT to check re-partition)
4. After it completes sucessfully, leave the phone hooked to the pc... and then wait, wait a good 2 or 3 minutes after its booted.
5. Once 2 or 3 minutes has gone by you can navigate to the Root_J320A folder.
6. There you'll see root.bat, double click that let it do its thing.
6a. If at any time during the script you see "adb out of date. killing..." hit the x to close the window and restart the script.
*This may work on J320AG models but make sure you check oem unlock from dev settings first... and let us know how it goes
Enjoy
- D
Credits:
@ashyx - eng_boot
@Sh$llNinjA - eng_root
@sjowns - flashlight fix
@Chainfire - SuperSU
@Ryuinferno - init.d script
Click to expand...
Click to collapse
This was the first time i ever tried to root my phone and i followed the instructions located here:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
Well my wifi wouldnt save any passwords , flashlight was broken and my ATT J320A would always want to boot in to recovery mode. I thought i was screwed!!!! Then i seen one link in the thread to this thread where Kingroot was not needed.
I opened Odin and gave a shot and then ran Root.bat file, and the device rebooted wifi and flashlight were fixed and best of all my J3 was now rooted!!!!!
Still working on getting rid of that annoying pop up but all is good, thanks so much for this root and fix from the other thread.
james2ya said:
This was the first time i ever tried to root my phone and i followed the instructions located here:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
Well my wifi wouldnt save any passwords , flashlight was broken and my ATT J320A would always want to boot in to recovery mode. I thought i was screwed!!!! Then i seen one link in the thread to this thread where Kingroot was not needed.
I opened Odin and gave a shot and then ran Root.bat file, and the device rebooted wifi and flashlight were fixed and best of all my J3 was now rooted!!!!!
Still working on getting rid of that annoying pop up but all is good, thanks so much for this root and fix from the other thread.
Click to expand...
Click to collapse
@james2ya If you are talking about the pop that either says something in the order of "Unathorized activities where made" go to the play store, download and install SecurityLogAgent Fix, Open it up and click "Disable Securitylogagent" then restart phone when it asks. This should help get rid of that popup.
works great for me! now i just need a custom rom. is it possible to install trwp on j320a?
This guide is based on the original PewPewK post.
Which, in turn, was inspired by TopJohnWu's 'Samsung (System-as-root)' Magisk Installation Guide
It is an extended walk through aimed at ALL users, meant specifically for the SM-T720 (Tab S5e) BUT specifically meant to:
UNLOCK THE BOOTLOADER
INTRODUCE ROOT
RESTORE STOCK/RELOCK THE BOOTLOADER
Because of the community support, the options available to you have become numerous!
So if you're looking to squeeze EVERY inch out of your tablet, search the thread for suggestions or see the links below:
Go HERE if you are interested in custom recovery (e.g., TWRP).
Go HERE if you are interested in custom ROMs or kernels.
ROOT WARNING
Introducing root and further tampering may lead to unfavorable performance and/or shortened device lifespan.
In extreme circumstances, it may render your device OR specific hardware components unstable or non-functioning.
By following this guide, you ACKNOWLEDGE these risks and release AHE_XDA, XDA and its CONTRIBUTORS of ANY and ALL responsibility.
WARRANTY WARNING
In many states, countries, provinces and territories, introducing root voids device warranty (manufacturer's and/or third-party). Please consult your regional Samsung office, place of purchase or third-party warranty company to determine if these terms are applicable to you.
ALTERNATIVES TO ROOT
If you are looking to maintain warranty and continue access to Samsung-specific features, consider disabling or uninstalling unwanted applications via the Android Debugging Bridge (ADB).
TiTiB, a genius in his own right, has a thread dedicated to the Tab S5e and bloat removal without the cost of warranty.
Visit it HERE and click 'Thanks!' if it helped.
Known Issues (January 31, 2020)
KNOWN ISSUES (January 31, 2020)
Where's Recovery?
Explanation: TWRP (custom recovery) is NOW available. Please visit TeamWin for instructions.
Workaround: Resolved as of August 6, 2019.
Magisk shows as 'Not Installed.'
Explanation: Magisk, due to the changes to the recovery partition in Android Pie & above, will not boot automatically. It requires user intervention.
Workaround: To enable root access, be prepared to hold 'Volume Up' and the 'Power' keys on EVERY BOOT or REBOOT.
WiFi stopped working after installing 'magisk_patched.tar' with Odin.
Explanation: Cause unknown as of January 31, 2020.
Workaround: In some cases, after introducing root ('magisk_patched.tar'), WiFi may stop working. If this happens, do the following:
From the app drawer, go to Settings > Connections > Wi-Fi.
Highlight and select your WiFi network.
Long press the network name and select "Forget Network".
Wait 3 to 5 seconds.
Press and click on the network in which you asked Android to forget.
Re-enter your password.
If entered correctly, WiFi will resume connectivity.
"Your phone is locked because the payment service was uninstalled."
OR
Only official released binaries are allowed to be flashed (vbmeta).
Explanation: To protect against various threats (e.g., compromised data, theft or root), Samsung, as of December 2017, introduced a series of low-level initiatives to LOCK the device should ANY part of Knox be compromised. These initiatives are frequently referred to as 'KG' (KnoxGuard) or 'RMM' (Remote Monitoring and Management).
Further details can be found HERE.
Workaround: A workaround now exists, thanks to @ianmacd, but requires TWRP to be installed followed by the Samsung multi-disabler file.
If you do NOT intend to install TWRP, precautions MUST be taken not to freeze, disable or remove the following files:
'Payment Services' (com.samsung.android.kgclient)
'KnoxGuard' (knoxguard.apk)
In most circumstances, the issue will present itself immediately after the application(s) is frozen, disabled or removed. In rare circumstances, only after a device restart.
PRO-TIP: Do NOT reboot unless absolutely necessary; opt to power down the device.
Should you encounter EITHER error, you will need to boot into 'Download Mode', revert to original factory settings and verify your Google account to avoid an FRP LOCK.
To enter 'Download Mode' and recover from the error:
Connect a USB cable to your Laptop/PC.
With power-off on the device, hold down BOTH 'Volume Up' and 'Volume Down'.
Connect the USB cable to the device, while holding down both volume keys, and press 'Power'.
If done correctly, the device will boot to 'Download Mode'.
My Streaming Service won't log me in, no longer provides HD viewing or doesn't allow offline downloads.
Explanation: Widevine is a digital rights management platform used by major streaming companies to prevent piracy.
Low-level details can be found HERE.
Workaround:
Resolved by @ianmacd and his 'liboemcrypto disabler' via Magisk Manager and/or Custom Recovery (e.g, TWRP) as of April 4, 2018.
NOTE: If you installed TWRP and flashed the Samsung multi-disabler file, this issue is resolved of as December 13, 2019.
If you do NOT intend to install TWRP, log-out and uninstall your streaming application(s). With root introduced and magisk enabled, download 'liboemcrypto' from 'Modules' within Magisk Manager. You will be asked to restart after installing the module. Do this and re-enable Magisk on boot. Sideload your streaming application(s) from a source OUTSIDE the Playstore. Log in and resume streaming.
Items are ADDED and UPDATED as they are discovered, solved or a workaround is introduced. Please message me directly if something is missing.
Requirements & Instructions
HARDWARE & SOFTWARE REQUIREMENTS
Windows Laptop/PC with more than 25GB of available storage space
SM-T720 Tablet (Galaxy Tab S5e)
Samsung USB Type-C Cable (as found in the original packaging)
WIFI connection (and if necessary, login details)
SECTION ONE - LOG-OUT & BACK-UP YOUR DATA
Log out of your Samsung and Google account(s).
Back-up ANY and ALL data as following this guide will result in COMPLETE data loss.
SECTION TWO - DOWNLOAD THE RIGHT UTILITIES
In order to root, you require several utilities.
They are as followed:
Samsung USB Drivers - Provides connectivity between Laptop/PC and your device.
7-Zip - An open-source file archiver.
Odin 3.13.1 - Used to flash original or custom Samsung firmware.
Frija - Downloads the latest available Samsung firmware.
Magisk Manager (APK) - Helps obtain/manage and extend root options. Download the latest .APK (Application Package).
Click on the UNDERLINED NAME of the above utilities to download them to your local Laptop/PC.
PRO-TIP: Create sub-directories, like pictured below, and organize your downloads accordingly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PRO-TIP: Consider a donation to Frija, Magisk or your favorite developers as a token of goodwill and to help ensure future development efforts.
SECTION THREE - DOWNLOAD THE RIGHT FIRMWARE
In order to root or, at a later time, return to original factory settings; you MUST have a local copy of firmware.
This requires knowing our CSC; a three letter code that Samsung devices use to comply with local telecommunication standards and determine device-specific features or updates.
To locate your CSC, perform the following:
On your device, go to 'Settings'
From 'Settings', scroll down to 'About Tablet'.
Press on 'About Tablet' followed by a press on 'Software Information'
Scroll downwards until you see 'Service Provider SW Ver.'
There are three lines.
The third line will read similar to the following:
TUR//
Those three characters (e.g., TUR) represent the CSC code for your region.
PRO-TIP: Your CSC may OR may not be the same as the example; that's expected and perfectly normal.
Open Frija, which you downloaded under 'Section One', and input your model and CSC.
Make sure 'Auto' is selected and click on 'Check Update'.
If the right values are inputted, Frija will look similar to the following:
Click on 'Download' and select a location on your Laptop/PC.
When the download is complete, Frija will verify and decrypt the firmware.
Once finished, Frija will look similar to this example:
PRO-TIP: If you can't get Frija to open or download, right click and select 'Run as administrator'.
SECTION FOUR - UNLOCK THE BOOTLOADER
THIS STEP WILL REMOVE ALL DATA FROM YOUR DEVICE. PLEASE REFER TO 'SECTION ONE' FOR MORE DETAILS.
Power off the device.
Power on your Laptop/PC and login into your Windows account.
Connect the USB cable to your Laptop/PC but NOT to your device.
On the device, hold the 'Volume Up' and 'Volume Down' keys at the SAME time.
Connect the USB Cable from your Laptop/PC to the device.
You MUST hold BOTH keys during AND after inserting the USB Cable to receive the following warning:
PRO-TIP: In SOME cases, you may also need to hold 'POWER' as well.
To continue towards unlocking your bootloader, hold the 'Volume Up' key for approximately 4 to 5 seconds (or until the screen goes black).
After 4 to 5 seconds have passed (or if the screen went black), release the 'Volume Up' key and you will be presented with one last warning:
Press and click on the 'Volume Up' key to finalize your decision.
The device will factory reset and from now on, until the bootloader is re-locked, you will receive this warning:
Leave the device to reinitialize. This will take approximately three minutes. The device will erase itself and you will notice several reboots. Afterwards the only activity you'll see is a pulsing 'SAMSUNG' logo. Eventually you will be presented with the 'Let's Go!' set-up screen. Set the device aside for now.
SECTION FIVE - INSTALLING 7-ZIP
If you correctly followed the first FOUR sections, you now have the required utilities, firmware and an unlocked bootloader.
In order to proceed, you MUST install 7-Zip to extract and manipulate key files required for root.
If you have prior experience with 7-Zip or an alternate compression manager, SKIP this step and proceed to 'SECTION SIX'.
It IS enough to double-click the EXECUTABLE and install it; you need NOT configure anything.
However, for a visual reference, follow this LINK to see 7-Zip in use.
Alternately, for technical support and assistance SPECIFIC to 7-Zip, use this LINK. Search thoroughly before posting.
SECTION SIX - EXTRACTING FIRMWARE
Like the CSC code, mentioned in 'SECTION THREE', the name of your download will differ slightly but 'SM-T720' and 'AP_T720' will be in the file name:
Using 7-Zip, you must extract the following file:
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
From the following ZIP container:
SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
Right click on your ZIP container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.
7-Zip will begin to decompress the necessary files and will result in the following output:
Delete ALL files except for the following:
SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
Rename the extension of 'AP_T720XX.....tar.md5' to 'AP_T720XX.....tar' and ignore the warning provided by Windows.
When finished, your folder contents will look similar to this:
The AP file is required for root.
PRO-TIP: Keep the ZIP container should you ever want to revert back to original factory settings. If not, delete it and download again later using Frija.
SECTION SEVEN - ENABLE WIFI, TRANSFER FILES & INSTALL MAGISK MANAGER
In 'SECTION FOUR', the device was left to reinitialize.
This means you have a device that requires set-up:
Do NOT log into your Samsung or Google account. The ONLY thing required is WIFI:
PRO-TIP: WIFI and Magisk work together to help achieve root access, provide updates and for module repository access.
Once you've arrived at the home screen, you need to enable 'Developer Options' to ensure the bootloader is unlocked.
To verify your bootloader is unlocked, perform the following:
On your device, go to 'Settings'.
From 'Settings', scroll down to 'About Tablet'.
Press on 'Software Information'.
Scroll downwards until you see 'Build Number'.
Tap 'Build Number' seven times to enable 'Developer Options'.
Press the back button on the navigation bar to return to 'Settings'.
Underneath 'About Tablet', you will now see 'Developer Options'.
Open this and locate 'OEM Unlocking'.
If you've followed the outlined steps, your screen should match this example:
PRO-TIP: If your screen does NOT match the example, it is possible you are NOT connected to WIFI or you did NOT successfully unlock the bootloader. If all these conditions are true, restart the device and check again. If the issue persists, create a NEW response in the thread.
Now connect the device to your Laptop/PC and, when prompted, 'Allow access to tablet data'.
Using Windows Explorer, copy the following files to the 'Download' folder of your device:
MagiskManager-v7.3.2.apk
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
Due to the size of the AP file, this may take several minutes on a low-end Laptop/PC.
Once the copy is complete, go to your device and double press on 'MagiskManager-v7.3.2.apk' to initiate the install process.
PRO-TIP: Due to changes introduced in Android Oreo, you MUST allow permission to install applications (APKs) not obtained from the PlayStore.
Click on 'Settings' to open the 'Install unknown apps' screen and toggle 'Allow from this source' on.
Press the back button on the navigation bar to allow the installation:
SECTION EIGHT - PATCH YOUR AP FILE
Open your app tray by swiping up and open Magisk Manager.
You will see a RED QUESTION MARK and the following error:
'Magisk is not installed.'
Click on 'Install' and, when prompted by Magisk, select 'Install' again:
Magisk will provide another prompt:
Choose 'Select and Patch a File' to proceed.
Magisk will now prompt for device access:
Click on 'Allow' and the internal Device File Explorer will open to the 'Recent' tab:
Click on the top app bar and select 'Downloads' to find your AP file:
And then:
Once inside the 'Downloads' folder, select your AP file to begin the flash process.
Once the flash process is complete, the status on the top title bar will change from 'Flashing' to 'Done!':
SECTION NINE - RETRIEVAL & DISSECTION
With our AP file patched by Magisk, you must now locate and transfer it back to our Laptop/PC.
If you have not already done so, reconnect the device to your Laptop/PC:
Open Windows Explorer, double-click on 'Tab S5e', double-click again on 'Tablet' and open the 'Downloads' folder:
Under 'Downloads', you will see THREE files:
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
magisk_patched.tar
magisk_install_log_2019-07-10T225845Z
PRO-TIP: 'magisk_install_log' is an output of the AP file patching process. If you encountered ANY errors, keep a copy and raise a question in the thread.
Delete 'AP_T720XX.....tar' and copy 'magisk_patched.tar' back to your Laptop/PC; preferably to the 'FIRMWARE' sub-directory suggested in 'SECTION TWO'.
Due to the size of the 'magisk_patched.tar' file, this may take several minutes on a low-end Laptop/PC.
Once the transfer is complete, let's make room in our 'FIRMWARE' folder by deleting the 'AP_T720XX.....tar' file.
This should leave you with TWO files:
SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
magisk_patched.tar
Move OR delete the 'SM-T720.....fac.zip' container so you can focus exclusively on 'magisk_patched.tar'.
With NO files left except for 'magisk_patched.tar', you must now use 7-Zip again to extract its contents.
PRO-TIP: Refer to 'SECTION FIVE' if you need a refresher on 7-Zip.
Right-click on the 'magisk_patched.tar' container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.
Once all files are extracted, your output will look similar to, if NOT exactly like, this:
Now DELETE these files:
dtbo.img.lz4
magisk_patched.tar
modem.bin.lz4
persist.img.ext4.lz4
system.img.ext4.lz4
userdata.img.ext4.lz4
vendor.img.ext4.lz4
In order to have the following:
meta-data [FOLDER]
boot.img
recovery.img
vbmeta.img
If done correctly, your folder output will look like this:
SECTION TEN - CREATE YOUR TAR
In 'SECTION NINE', you organized the following list of files/folder:
meta-data [FOLDER]
boot.img
recovery.img
vbmeta.img
Using Windows Explorer, navigate to your 'Firmware' folder (or whatever location you used).
Now, using 7-Zip, you need to compress these files into a TAR container.
This means you must select ALL files.
This can be achieved by using CRTL + A on your keyboard or simply by highlighting them all with a left-click:
Right-click on the selected files, navigate to '7-Zip' and, from the sub-menu, select 'Add to archive...':
If done correctly, the following screen will present itself:
Only THREE things MUST be done to complete our TAR:
Change the filename to 'magisk_patched' WITHOUT quotations
Change the 'Archive format' to 'TAR'
Click on 'OK' to confirm your decisions and begin compression:
PRO-TIP: If, for ANY reason, you don't want to keep these files, you can select 'Delete files after compression' before clicking on 'OK'.
With this step complete, you are left with the following output:
SECTION ELEVEN - DOWNLOAD MODE
Using the 'Power' key on your device , select 'Power off':
Disconnect the USB cable or the device will switch to 'Charging Mode':
On your device, hold 'Volume Up' and 'Power' together until the 'Android Recovery' screen appears:
'VOLUME UP' will navigate upwards, 'VOLUME DOWN' will navigate downwards, and 'POWER' will highlight and confirm your choice.
PRO-TIP: You may have to press 'POWER' twice.
Highlight and select 'Reboot to bootloader' to properly put your device into 'Download Mode':
Reconnect the device back to your Laptop/PC.
SECTION TWELVE - ODIN PREPARATION AND FLASH
Now, because recovery is unavailable, you must use Odin to flash your TAR file to introduce root.
In 'SECTION TWO', you downloaded Odin and created a folder for it.
You must now go to that folder, or whatever folder you opted to use, and decompress Odin.
Right-click on the 'Odin3_v3.13.1.zip' container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.
This will create a sub-directory called 'Odin3_v3.13.1'.
Double-click and you will be presented with the following output:
Double-click on 'Odin3 v3.13.1.exe' to launch the application.
You will receive a prompt written in both English and Korean. Click 'OK' to close the warning.
With Odin open, locate and click on the second tab called 'Options' and uncheck 'Auto Reboot':
When you click on the 'AP' button, Windows File Explorer will automatically launch.
As per 'SECTION NINE', and using Windows File Explorer, navigate to the location you created and saved 'magisk_patched.tar'.
Double-click 'magisk_patched.tar' (or alternatively, highlight the file and select 'Open') to have it load into the AP slot:
With all these steps completed and your device connected, STOP and read below:
A green navigation bar on Odin, and a white bar on you device, will appear.
This indicates that key files are being written to your device.
Irregardless of how quick or slow the progress bar is, DO NOT disconnect the device.
The device, no matter if the flash was successful or not, will do NOTHING because you unchecked 'Auto Reboot'.
Wait for 'PASS!' to appear in Odin before you disconnect your device.
If everything was done correctly, Odin will look like this:
Your device, on the other hand, will have the following bar across its screen:
Now disconnect the device, STOP and read below until you feel comfortable enough to execute the instructions:
Hold 'Volume Down' and 'Power' until the screen goes black (also known as a 'Soft Reset').
The moment the screen goes black, continue to hold down 'Power' but QUICKLY switch so now only 'Volume Up' is being held.
Do this until you enter 'Android Recovery'.
As outlined in 'SECTION ELEVEN', use the 'Volume Keys' & 'Power' to navigate the menu.
First select 'Wipe Data/Factory Reset' and, upon completion, choose 'Reboot System Now'.
Your device will reboot several times. This is expected behavior.
If everything was done correctly, your device will reinitialize and require set-up again:
SECTION THIRTEEN - ROOT VERIFICATION
Like 'SECTION SEVEN', you need WIFI to complete set-up but mustn't log into ANY accounts.
Also, like 'SECTION SEVEN', you will need to install Magisk Manager again.
Once the first two steps are complete, power-off the device:
With the device powered off AND disconnected, hold down 'Volume Up' and 'Power' until you see the following warning:
WARNING: From now on, on EVERY BOOT or REBOOT, you MUST do this if you want Magisk enabled.
Release all keys and allow the device to boot.
Once Android is loaded, launch Magisk from your app drawer.
If you are prompted to update, do so but select 'Direct Install (Recommended)' and remember the key sequence on reboot:
Magisk Manager, if set-up properly AND with root enabled, will look like this:
Magisk Manager, if NOT set-up properly OR with root disabled, will look like this:
PRO-TIP: To further validate root, you can use an application like 'Root Checker' to verify:
You may now log into your accounts and finish configuring the device.
Recognition & Sharing Policy
RECOGNITION
This guide, and the required methods and software, would NOT be possible with the efforts of the following individuals:
@topjohnwu
@ianmacd
@LuK1337
@invmini
@CrazyApe
@eragon5779
@PewPewK
A sincere thank you for your time, hard work and, most importantly, determination to explore.
Praise and tribute is also extended to @TiTiB for his editorial skills, testing and much needed feedback.
SHARING POLICY
Do NOT reuse any part of this guide without first asking.
Do NOT reuse any part of this guide without giving credit to those in the 'RECOGNITION' header.
ALL photographs, not screenshots, are the property of myself (AHE_XDA). I spent considerable time capturing and editing each posted photograph. Therefore photographs may NOT be downloaded, copied, reproduced or used anyway without consent.
If there's something you like (styling/format/text/photographs) and want to use, ask.
Return To Stock Instructions
To return to stock and/or relock the bootloader, these are the best instructions available:
https://forum.xda-developers.com/showpost.php?p=79698366&postcount=44
They are originally intended for the Galaxy S10 series but work perfectly for the Tab S5e (SM-T720).
Full credit to @robbo1947.
Very nice how-to!!!
Would've made my first attempts much easier
I made it through the old way, getting all bits and pieces from through the other thread, this saves new comers hours of reading through all info available and getting it done at once.
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
Side note I never used the key combo on rebooting for magisk updates or other stuff, always had root enabled afterwards.
You've done one helluva job @AHE_XDA!! I can't even imagine how long it took to put all of this together. It leaves nothing to be desired. Honestly, I've never seen such a comprehensive guide on xda before. Here's some $$$$$$$$$$ in thanks.
BTW, I'm fully up and running with Magisk and am currently freezing away many apps.
CAUTION: Be very careful when freezing anything Samsung 'billing' related.
I got a bit carried away freezing Samsung stuff and locked it up tighter than a drum.
FYI, before rooting I was disabling every Samsung app I could (including com.sec.android.app.billing) and had no problems. Root really *is* powerful.?
Anyways, if you get in to a predicament like mine and see these screens there is still hope.
Power off> Hold both VOL> Plug in PC-connected USB cable> Press PWR
Might take a few tries, but eventually you should get to DOWNLOAD screen.
Pics are in reverse order. You would see the one on the right first.
@TiTiB
I was able to reproduce your error.
I updated the 'Known Issues' to reflect this.
It is either 'Payment Services' (com.samsung.android.kgclient)' or 'KnoxGuard' (knoxguard.apk) that caused the error.
I can disable, freeze or delete 'Samsung Billing' (com.sec.android.app.billing) without issue.
Thank you for this info! It really helps in my continuing persuit to get rid of as much Samsung stuff as possible, while still retaining OneUI functionality. It gets a bit unnerving freezing stuff when you're several days in to setting up stuff. I'm going slower this time.
@AHE_XDA first of all thanks for this manual, I had never seen more comprehensive here!
Second, I had one attempt to root t725, it was 2 months ago. I done all steps, made patched AP, glashed successfully (only ap, not other 3 files). After reboot I got exactly same messages as described in upper post! Not debloat, but straight from boot with root.
I afraid, gone to download mode and flashing stock. Got it back.
Never tried again.
Have you idea what was wrong?
I want to do again, but afraid a little...
Thanks
ivanox1972 said:
@AHE_XDA first of all thanks for this manual, I had never seen more comprehensive here!
Second, I had one attempt to root t725, it was 2 months ago. I done all steps, made patched AP, glashed successfully (only ap, not other 3 files). After reboot I got exactly same messages as described in upper post! Not debloat, but straight from boot with root.
I afraid, gone to download mode and flashing stock. Got it back.
Never tried again.
Have you idea what was wrong?
I want to do again, but afraid a little...
Thanks
Click to expand...
Click to collapse
After you flash the AP file with Magisk, you don't want to re-install the entire binary with Odin.
You need to dissect its contents, re-compress it and THEN install with Odin.
Take a look at 'Section Ten' on the first page to see what I'm talking about.
Any questions, place them on thread or PM me.
AHE_XDA said:
@TiTiB
I was able to reproduce your error.
I updated the 'Known Issues' to reflect this.
It is either 'Payment Services' (com.samsung.android.kgclient)' or 'KnoxGuard' (knoxguard.apk) that caused the error.
I can disable, freeze or delete 'Samsung Billing' (com.sec.android.app.billing) without issue.
Click to expand...
Click to collapse
Check this-wtf?
TiTiB said:
Check this-wtf?
Click to expand...
Click to collapse
Yes, there is a dependency between the two. With App Inpector, you don't see 'KnoxGuard' explicitly listed but if you use something like 'Root Explorer', you'll find it.
Until we get recovery, like the other Samsung devices on Pie, we simply can't touch these files.
AHE_XDA said:
Yes, there is a dependency between the two. With App Inpector, you don't see 'KnoxGuard' explicitly listed but if you use something like 'Root Explorer', you'll find it.
Until we get recovery, like the other Samsung devices on Pie, we simply can't touch these files.
Click to expand...
Click to collapse
I use MiXplorer and have seen those while 'xploring'. Before rooting, when I was using PackageDisabler, kgclient was one of the disabled packages....uh, so my point is WTF?
@TiTiB
So to make sure we understand each other; you could disable/uninstall it through ADB but a removal of the apk froze the device (along with the error)?
Bixby Is Coming - July Update
In the next build of software for the Tab S5e (July), Bixby will be introduced and fully integrated into the system.
This means nothing for root but means you'll have more to uninstall/disable.
If you don't want or need Bixby, stay on ANY release prior to July.
AHE_XDA said:
@TiTiB
So to make sure we understand each other; you could disable/uninstall it through ADB but a removal of the apk froze the device (along with the error)?
Click to expand...
Click to collapse
I disabled kgclient using Disabler Pro app with no ill effects (before rooting). It's in my 'disabledpackages133-OK.xml', so I assume it was disabled. Perhaps the Disabler app handled it differently or something, idk.
After I rooted, while I was freezing Samsung apps using '3C Toolbox Pro', and I'm *almost* 100% certain Payment Services/kgclient was among them, the tablet locked up. AFAIK, these two actions, using these two apps is effectively the same thing, therefore the 'wtf' statement.
I am curious enough that I'm going to prepare for disaster, then mess around with this package—first, disabling it with the 'CCSWE App Manager (SAMSUNG)' app, then manipulating the package's contents (expecting disaster), then freezing it with 3C Toolbox—I MUST HAVE THE ANSWER!! (TiTiB *does* stand for Tweak it Til it Breaks, after all) ?
It wiil be an hour or two, and, of course, I'll post my results here.
@TiTiB
Whenever you disable or remove a system app without root; the application still exists on the device.
It's never truly gone.
It's only been removed from your profile; usually referred to as user 0 (current user).
A factory reset will bring that application right back.
Introduce root and now, because you have administration access over the entire device, remove the application and it's gone for good (or at least until you flash stock firmware).
Alter them at a root level, freeze/remove/disable, it's likely you're going to see the same error as before.
TiTiB said:
I disabled kgclient using Disabler Pro app with no ill effects (before rooting). It's in my 'disabledpackages133-OK.xml', so I assume it was disabled. Perhaps the Disabler app handled it differently or something, idk.
After I rooted, while I was freezing Samsung apps using '3C Toolbox Pro', and I'm *almost* 100% certain Payment Services/kgclient was among them, the tablet locked up. AFAIK, these two actions, using these two apps is effectively the same thing, therefore the 'wtf' statement.
I am curious enough that I'm going to prepare for disaster, then mess around with this package—first, disabling it with the 'CCSWE App Manager (SAMSUNG)' app, then manipulating the package's contents (expecting disaster), then freezing it with 3C Toolbox—I MUST HAVE THE ANSWER!! (TiTiB *does* stand for Tweak it Til it Breaks, after all)
It wiil be an hour or two, and, of course, I'll post my results here.
Click to expand...
Click to collapse
Sho'nuff, stay away from Samsung Payment/kgclient if rooted.