Related
Hello,
I unfortunately just updated to 2.32.651.2 before deciding to root my phone. Is it still possible to root with this updated version, or should I downgrade. If I need to downgrade, can anyone tell me which software version I need to downgrade to in order to root, and a thread linking to a guide to downgrade?
forum.xda-developers.com/showthread.php?t=847993
this should do it
I think you can root this version, search around... if it possible you will find a post regarding it.
If you plan to downgrade, I would recommend .5 and then root using regaw's method - you should find all the details on the CDMA hero wiki page.
xlectik67 said:
I unfortunately just updated to 2.32.651.2 before deciding to root my phone. Is it still possible to root with this updated version [?]
Click to expand...
Click to collapse
HERE is the link to the post i wrote (in the thread which guided me) to get root in this stock-rom... so, yes, it can be done...
as far as dowgrading, im not sure i would recommend it - but as mentioned earlier, the wiki has a guide which i believe is based on a ...31...5 version you could use...
gl, h.
Root Sprint 2.32.651.2 OTA Permanently (in 10 steps)
Hi All
I have been able to root the Sprint 2.32.651.2 OTA permanently with the old boot-patched method. It is a little tricky and requires some knowledge of the Android SDK and Android Commander (There are several documents on how to install and use these 2 tools. Please search them out and learn.)
None of the other rooting methods seem to hold root after booting on this update. I have done this twice and it retains root permanently.
You must follow these steps to the letter.
First gather the tools needed for this root method
Android SDK (up and running)
Android Commander (androidcommander.com - makes moving and deleting so much easier)
SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682 (this will give you temporary rootand install superuser, It is only temporary. After you do a boot the phone will loose root)
RomManager (download from Market after you have temp root)
Boot-Patched.zip (place this at the root of your SD Card. Flash through recovery. This is what will give you permanent root. File attached)
I take no credit for the tools that are needed. They are freely distributed. If I could remember who they belonged to I would give them props. Props to all the devs for making my Hero more enjoyable!!!
Process:
1: Install Android SDK. Make sure it is up and running and you have knowledge of the tools
2: Install Android Commander. Make sure it is up and running and you have knowledge of the tools
(Plug your phone into your computer with a USB cable)
3: Download and install SuperOneClick on your Windows based computer.
4: Run SuperOneClick.exe from the programs folder and click the ROOT button. (this will give you temorary root and install superuser onto your phone)
(At this point DO Not Reboot!! You will loose root and have to re-run step 4)
5: Download and install RomManger from the Market
6: Open the RomManager App and install the Clockwork Recovery (now you have a custom recovery on the phone. This will allow you to run Boot-Patched.Zip while temporarily rooted.
7: Through Android Commander copy Boot-Patched.zip to the root of your SD Card
8: Once Boot-Patched.zip is copied, boot into recovery either from Android Commander or RomManger
9: From recovery, flash boot-patched.zip like any other ROM. (this will permanently root this Sprint Update)
10: From recovery, boot the phone. re-run Android Commander and look at the bottom left corner of the program window. If it says "root OK" then it worked. If it says "root NO" then start over at step 4.
To test if you have permanent root, through Android Commander, remove a stock app that you do not want on your phone. If it works, you have permanent root. You will not be able to remove apps with temporary root.
I have an understanding of all of these tools. For you noobs out there, just keep learning. Trial and Error that is how its done. Keep asking questions (in the right forums please) someone will answer.
Enjoy
PS: Once rooted your WiFi will be non-functional. The only Kernel I have been able to get to work with this update and fix WiFi is the ZenKernel from 08122010. Serch it out, download and flash. (If you dont, you will be stuck with a phone with no WiFi and a top speed of 585mhz through SetCpu)
ccrosno said:
Hi All
I have been able to root the Sprint 2.32.651.2 OTA permanently with the old boot-patched method. It is a little tricky and requires some knowledge of the Android SDK and Android Commander (There are several documents on how to install and use these 2 tools. Please search them out and learn.)
None of the other rooting methods seem to hold root after booting on this update. I have done this twice and it retains root permanently.
You must follow these steps to the letter.
First gather the tools needed for this root method
Android SDK (up and running)
Android Commander (androidcommander.com - makes moving and deleting so much easier)
SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682 (this will give you temporary rootand install superuser, It is only temporary. After you do a boot the phone will loose root)
RomManager (download from Market after you have temp root)
Boot-Patched.zip (place this at the root of your SD Card. Flash through recovery. This is what will give you permanent root. File attached)
I take no credit for the tools that are needed. They are freely distributed. If I could remember who they belonged to I would give them props. Props to all the devs for making my Hero more enjoyable!!!
Process:
1: Install Android SDK. Make sure it is up and running and you have knowledge of the tools
2: Install Android Commander. Make sure it is up and running and you have knowledge of the tools
(Plug your phone into your computer with a USB cable)
3: Download and install SuperOneClick on your Windows based computer.
4: Run SuperOneClick.exe from the programs folder and click the ROOT button. (this will give you temorary root and install superuser onto your phone)
(At this point DO Not Reboot!! You will loose root and have to re-run step 4)
5: Download and install RomManger from the Market
6: Open the RomManager App and install the Clockwork Recovery (now you have a custom recovery on the phone. This will allow you to run Boot-Patched.Zip while temporarily rooted.
7: Through Android Commander copy Boot-Patched.zip to the root of your SD Card
8: Once Boot-Patched.zip is copied, boot into recovery either from Android Commander or RomManger
9: From recovery, flash boot-patched.zip like any other ROM. (this will permanently root this Sprint Update)
10: From recovery, boot the phone. re-run Android Commander and look at the bottom left corner of the program window. If it says "root OK" then it worked. If it says "root NO" then start over at step 4.
To test if you have permanent root, through Android Commander, remove a stock app that you do not want on your phone. If it works, you have permanent root. You will not be able to remove apps with temporary root.
I have an understanding of all of these tools. For you noobs out there, just keep learning. Trial and Error that is how its done. Keep asking questions (in the right forums please) someone will answer.
Enjoy
PS: Once rooted your WiFi will be non-functional. The only Kernel I have been able to get to work with this update and fix WiFi is the ZenKernel from 08122010. Serch it out, download and flash. (If you dont, you will be stuck with a phone with no WiFi and a top speed of 585mhz through SetCpu)
Click to expand...
Click to collapse
Sorry I forgot to mention that there were a couple times that the phone locked up durring the reboot to recovery stage. I do not know why. I beleive that it was due to forgetting to install the recover before rebooting. If this happens, pull the battery, replace the battery and start over.
Thanks
tailsthecat3 said:
forum.xda-developers.com/showthread.php?t=847993
this should do it
Click to expand...
Click to collapse
my WiFi worked fine after rooting the ota update by following the linked method. ^
Go ahead and root using the method mentioned above, if anything goes wrong... you can always RUU and reroot.
BTW, I have downgraded using .5 RUU and rooted my phone, so based on my experience I can say, it works well. I had initially rooted my .7 and was running CM 6.0 stable, had some issues, got my recovery screwed up, so had to go all the way... ;-).
tailsthecat3 said:
my WiFi worked fine after rooting the ota update by following the linked method. ^
Click to expand...
Click to collapse
Ya I tried that one. Couldn't get it to take. Mine is sort of the non-syntax method.
Note to all users: This thread is now closed. I will no longer be updating GladRoot as there are more reliable and simpler methods for obtaining root on the newer firmwares. Support can still be found through PM for the older firmware versions.Note to all users on non-AT&T/Bell devicesThis is currently untested on anything but AT&T and Bell phones. You can run this on any phone, and at the very worst, it just won't work. There's almost 0 chance you will harm your phone by running this, so feel free to try. Please report back what firmware version you tried it on, and if it worked or not and I'll update the first post here to reflect. I don't have any device but an AT&T Atrix so I can't test any of the other versions myself, I need your help!GladRoot v4.3 (AT&T 1.83 Update Supported - READ DIRECTIONS)
In the interest of cleaning things up and putting all the current information into one place, with links to everything you'll need to get this working.
Basically, there's a ton of misinformation floating around about current root methods. This is your one stop shop for all your root needs. To explain, the SuperOneClick method installs busybox a second time. The Atrix already has busybox installed, so there's no need to install a duplicate. This can cause issues with other mods. GladRoot will take care of everything SuperOneClick did. I've contacted the developer to see if there's a way around this.
Start Here
If you have an AT&T Atrix and want to update to 1.57/1.83 with root, follow the first set of instructions.
If you have a Bell Atrix or an AT&T Atrix on 1.26 or 1.52 and just want to root, go to the second set of instructions.
Please, please, PLEASE, read the whole first post before asking questions. Chances are your question is already covered in the directions.
If you have any features requests or notice any bugs, please PM me, I might miss them in this thread.
To unroot, just run unroot.bat
Note to users seeing "Unable to detect device" error: Disable USB debugging, and turn it back on. Make sure your connection type is set to None. If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
Little bit of additional info here:
This will root your phone. There is no need to run aRoot before this, and you should NOT be running SuperOneClick anymore.
This has options to enable sideloading and the tethering APN. Enabling sideloading will not add an Unknown Sources checkbox, it will just enable it. I don't see any reason for the need to disable this, so unless someone can make a case for the checkbox (that makes sense for users), it will remain this way.
Unlike v1, the scripts are fully automated. You need only click "allow" to superuser when prompted for certain steps.
If you are already on 1.57/1.83 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS.
Installation instructions: 1.26 to 1.57/1.83
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is 1.2.6 and is not running any mods, I recommend a fresh SBF flash of 1.2.6. Download links and installation instructions here
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions (If you're using Windows 7, run as admin by holding down control and double-clicking).
Verify that there are no errors before updating.
Go to Settings -> About phone -> System updates
Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
Run afterupdate.bat (If you're using Windows 7, run as admin by holding down control and double-clicking).
Make sure you allow the superuser request on your phone or it WILL fail.
All done! Enjoy your rooted Atrix on 1.57/1.83!
Screenshots**REMOVED FOR NOW UNTIL I GET A CHANCE TO UPDATE**Installation instructions: 1.26, 1.52 and Bell Atrix
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is the correct version. Go to Settings -> About phone -> Build number and make sure it matches one of the following:
OLYFR_U4_1.2.6
OLYFR_U4_1.5.2
OLYLA_U4_0.37.4
If you need to flash an SBF first, Download links and installation instructions here.
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions.(If you're using Windows 7, run as admin by holding down control and double-clicking).
When you get to the step that asks if you're updating to 1.57, just say no.
Verify that there are no errors.
All done! Enjoy your rooted Atrix!
DISCLAIMER
I am not responsible if this bricks your phone or if it doesn't work properly for you. I've done everything I can to ensure smooth execution.
If you have any issues, feel free to PM me, reply to this thread, or come find me on IRC (I'm Fenrir or fen|works on IRC)Special Thanks
Sogarth for adb wizardry, shawnbuck for the concept and getting the ball moving, designgears for the initial aRoot script method, and everyone on XDA and IRC who helped contribute and test.Changelog
Version 4.3
Cleaned up script a tiny bit
Added textual support for 1.83 (the method hasn't changed, it's always worked)
Version 4.2
Added Uknown Sources checkbox to sideloading, as well as enabling it.
Added unroot script.
Version 4.1
Fixed a few minor aesthetic errors in the script
Version 4
Added a pause after the superuser request so if it fails, users can read the output.
Started mapping out log process for error catching.
Removed abd kill-server from the beginning of the file as I think it might be causing problems on slower machines.
Version 3
Removed option to root, it just roots. This will not harm your phone if you're already rooted.
Added support to root all devices, including Bell Atrix.
Cleaned up and improved script.
Changed name from Root v2 to GladRoot (Which is Root v3)
Version 2
Massive improvements to deployment script
Removed need to manually enter commands
Version 1
Initial Release
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Vigneshd said:
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Click to expand...
Click to collapse
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
So do this version allow sideloading?
awww yeahhh
PixoNova said:
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
Click to expand...
Click to collapse
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
plmiller0905 said:
So do this version allow sideloading?
Click to expand...
Click to collapse
i assume so. i'm able to sideload
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync. I put the new retainroot folder in C:\.
Nothing works.
Have I missed something?
Any ideas?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
open command prompt and type:
Code:
adb devices
What does it return?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
USB debugging on?
USB mode set as None?
Ririal said:
open command prompt and type:
Code:
adb devices
What does it return?
Click to expand...
Click to collapse
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
shawnbuck said:
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
Click to expand...
Click to collapse
So is this a hole that allows us to exploit another hole?
s0dhi said:
USB debugging on?
USB mode set as None?
Click to expand...
Click to collapse
Yes to both.
drjim said:
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
Click to expand...
Click to collapse
I changed directory to C:\ in cmd and typed in adb devices. Its response: List of devices attached.
Only thing I haven't done is flash SBF (whatever that is). But I'm dling it now...along with RSDlite (whatever that is).
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
PixoNova said:
So is this a hole that allows us to exploit another hole?
Click to expand...
Click to collapse
This isn't quite a hole, just a little magic-show type trickery really.
tdamocles said:
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
Click to expand...
Click to collapse
What do you mean second command prompt?
Failed backup?
OK, I'm on stock 1.2.6, said yes to already rooted and yes to side load and no to tether. It starts and says pushing backupsu.sh... then retval = and backup failed to execute properly. What am I doing wrong? I have developer on and usb = none. Can't seem to get it to work...
when i run beforeupdate i get backup failed to execute properly
am i missing something?
Currently Beta:
THIS IS UNTESTED. I don't have my Atrix anymore, so I need volunteers to test this for me. Ideally, whoever can test this will have access to a PC to reflash the SBF. If you are willing to do so, please run the beforedebug and afterdebug versions and PM me the output
Some Notes:
- As this is Ririal's script translated to bash (see here: http://forum.xda-developers.com/showthread.php?t=1016060), this shouldn't work on Bell Atricies
- Since RSDLite is a windows only program, it is not possible to flash the SBF back to 1.2.6 on a Mac as far as I know. In other words if you've upgraded already, you're out of luck until you can find a PC to flash back to 1.2.6
PS: Since the method I used to turn the scripts to executables last time caused some PATH issues, I've decided to leave this as .sh files
Instructions:
1) Download the zip and decompress it to the Desktop
2) Make sure you're Atrix is hooked up w/ ADB debugging enabled
3) open up a terminal (What follows will be instructions to run)
cd ~/Desktop/aRootMacV2
./beforedebug.sh
4) Run the update on your phone( Settings -> About phone -> System updates)
5) Back to the terminal
./afterdebug.sh
6) Make sure to allow the SU request on your phone when prompted
Once this has been tested to make sure it's working correctly I will update this thread with more thorough instructions. In the mean time if you don't have a PC, make sure not to update.
Download: http://www.mediafire.com/?djxt3d8j519yk9m
Thanks for this. Ill try to get a pc so I can downgrade and test this.
Sent from my MB860 using XDA Premium App
I get this when trying to run beforedebug.sh
new-host-5:aRootMacV2 AJ$ /Users/AJ/Desktop/aRootMacV2/beforedebug.sh
-bash: /Users/AJ/Desktop/aRootMacV2/beforedebug.sh: /bin/bash^M: bad interpreter
EvilEvo said:
I get this when trying to run beforedebug.sh
new-host-5:aRootMacV2 AJ$ /Users/AJ/Desktop/aRootMacV2/beforedebug.sh
-bash: /Users/AJ/Desktop/aRootMacV2/beforedebug.sh: /bin/bash^M: bad interpreter
Click to expand...
Click to collapse
the "bad interpreter" message is caused by ^M (Windoze carriage returns) being embedded in the script file. If you do this
Code:
cat beforedebug.sh | tr -d '\r' > beforedebug.sh.new
cp beforedebug.sh.new beforedebug.sh
that should do the trick.
At the risk of jacking phoneixx's thread, I had done something similar for Mac based on Ririal's GladRoot and DesignGears aRoot.
There actually is an SBF flasher for Linux and Mac found on OPTICALDELUSION's blog.
I had originally posted this on AndroidCentral but since XDA is the site of record then I guess it should go here too
(I tried to link to the OPTICALDELUSION blog and AndroidCentral article but the XDA spam filter won't let me post a link to an outside site until I have 8 more posts, lol. I may make some more posts elsewhere and edit this post to include the proper links )
_____________
Hello, all of you frustrated Mac users out there!
This method is tested on my MacBook Pro (10.6.6)
Linux users should be able to use this if they replace the copy of adb that is in the zip file with the appropriate executable from Linux version of the SDK. If you know enough to run Linux then you can do that on your own
Warning -- AT&T Atrix only! No Bell!
So you're on 1.5.7 -- let's root it!
Part A -- Revert software back to 1.26
1. Download this file and unzip it (Deposit Files)
2. Make sure your phone is FULLY CHARGED
3. Turn off your phone
4. Remove your SIM card and SD card if you have one
5. Turn your phone ON and hold the Volume UP button
6. It will say “Starting RSD protocol support” at the top of the boot screen
7. Connect your phone to the computer via USB
8. Run the downgrade.sh script. This will reflash your phone to 1.26 so that we can gain root access.
9. it can take up to 5 minutes to flash depending on your computer speed. My MacBook Pro takes just under 4 minutes. If you get any errors that look something like
>> uploading RDL03: 0.0%usb_bulk_write -5
>> uploading RDL03: failed at 00000000/00300000
!! failed
>> rebooting
usb_bulk_write -104
Don't get nervous! That happens occasionally. Just run the script again.
10. Phone will reboot and it takes longer than usual to come up
11. disconnect USB and power down.
12. Put your SIM and SD cards back in
13. Power up and verify that you are running 1.2.6 in Settings -> About Phone. You'll have to reenter your Motoblur account info.
Part B -- Root it!
14. Enable USB debugging (Settings -> Applications -> Development).
15. Connect your phone and set USB Connection to 'None'.
16. cd to the aRoot directory and run aRoot.sh and follow the on-screen directions
If you see this:
…
Getting temporary root access...
mmap() failed. Operation not permitted
…
then the rooting operation failed. Try running the aRoot.sh script again. If it fails manually run this:
./adb kill-server
If it keeps failing you may not have flashed back to 1.26 successfully. Start again.
17. Verify that there are no errors before updating.
18. Go to Settings -> About phone -> System updates
19. Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
20. The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
21. When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
22. Run afterupdate.sh
23. Make sure you allow the superuser request on your phone or it WILL fail.
24. All done! Enjoy your rooted Atrix on 4.1.57!
thanks to
OpticalDelusion (OPTICALDELUSION)
DesignGears([SCRIPT] aRoot for Atrix 4G [ root - init.d - sideloading - tethering ] - xda-developers)
Ririal ([SCRIPT] GladRoot v4 (Bell 0.37.4, AT&T 1.26/1.52/1.57 Supported) - xda-developers)
Kennethpenn ([GUIDE] Flash SBF to Motorola Atrix 4G - xda-developers)
I was hoping for some help getting my S4 Active rooted.
But first, apologies if this thread is misplaced.
I have reviewed the following threads and followed the instructions therein, but to no avail:
http://forum.xda-developers.com/showthread.php?t=2347793
http://forum.xda-developers.com/showthread.php?t=2576460
http://forum.xda-developers.com/showthread.php?t=2596352
Against my better judgment, I tried various other options like One Click Root, even thought it was not certified for the I537; I also tried Kingo, VRoot and another Chinese root, and still nothing.
Phone:
AT&T
Samsung-SGH-I537
Version: 4.2.2
BaseBand: I537UCUAMF3
Kernel: 3.4.0-784654
From a new phone, I attempted to use activeroot.apk. I get the confirmation message that the phone is rooted, but Root Check, and Root Checker Basic both indicate no root. However, I was able to install SuperSU and update the binaries. I also installed SuperSU, Root Explorer, and Titanium Backup, and they all appeared to be working. Next, I installed XPrivacy.
However, at no time did any of the root checkers confirm root.
Today, SuperSU disappeared from my install list. I re-installed it, but upon attempting to update the binaries, I received an error message indicating that it has no binaries, and no way to install them. Titanium backup now gives me an error message indicating that I don't have root.
I unistalled activeroot, but when I navigated back to geohot's site to click on the "lambda", I got an error indicating that I needed an SD card to download activeroot. The card I was using at the time was a SanDisk 8gb SDHC Class 2 card from an old phone. So I researched and found that older cards, or cards from other devices can sometimes cause difficulties. So my current card is a SanDisk 32gb SDHC Class 10 that I formatted in the phone.
Now when I go to geohot's site on the default browser, I click on the "lambda", receive a notification that the download has commenced, but nothing further - no confirmation message. On Dolphin Browser, I still get the "SD card is required to download ar.apk."
Thanks to anyone who had read this far; and I would certainly appreciate any assistance that any of you are willing to provide.
Thanks so much.
You said you tried One Click Root. Have you tried SRS One Click Root from srsroot,com or did you try oneclickroot,com ? SRS Root worked for me on a cheapo Bauhn tablet - wasn't a device specific root, just used some sort of flaw, so (from my limited understand) the following instructions should apply to you (since I can't post links yet, I c+p'd)
1. Download the free SRS One Click Android Root v4.6 from SRSRoot One Click Root for Android (SuperUser) and install on your PC.
2. Download the free Root Checker by joeykrim from Play Store
3. Connect your device to your PC with the USB cable, wait for any drivers to install.
4. On the device:
a. Make sure Unknown sources is turned on – Settings>Security>Unknown sources
b. Make sure USB Debugging is turned on – Settings>Developer options and turn on at Top Right Corner if grayed out and turn on both USB debugging and Allow mock locations
c. Make sure the USB computer connection is set up – Settings>Storage and click on the 3 dots in the Top Right Corner – Click on USB computer connection and select Mount SD card.
5. Back out to the Home screen
6. Wait until the tablet goes into standby and the screen is black
7. Run Super One Click Root (you need to be connected to the Internet)
8. Select ADB Toolbox
9. Select Reboot Device
10. Wait for Reboot
11. Wait until the tablet goes into standby and the screen is black
12. Select Root Device (All Methods)
13. Follow directions and when you unlock the screen
14. Select Install SuperUser
15. When the root finishes turn off and restart the device and it should be rooted
16. Use the root checker
I hope this works for you. Credits to enviro8 from the androidtablets forum and obviously everyone who developed all that nitty gritty stuff.
Tiskael,
Thanks for your help. I followed your instructions, but I got some confusing results - the rooting program indicates that I have SU Root, but the Root Checker programs all indicate that I do not. Super SU and Root Explorer are still not working.
---= SRS One-Click-Root v4.7 =---
4:30:33 PM - Starting ADB Server..
4:30:38 PM - Manufacturer: samsung
4:30:38 PM - Model: SAMSUNG-SGH-I537
4:30:39 PM - Android Version: 4.2.2
4:30:39 PM - Build ID: JDQ39.I537UCUAMF3
4:30:39 PM - Board ID: MSM8960
4:30:39 PM - Chipset Platform: msm8960
4:30:39 PM - Getting OffSets.. : 0x8003 0x8005 (False)
4:30:40 PM - Checking Root access: True
[x] Device already have SU Root access, Rooting not needed.
My 14 day return period ends this weekend; I am going to do a Reset and start again from scratch. Certainly would appreciate any help if someone out there has had a similar experience.
Dansun said:
My 14 day return period ends this weekend; I am going to do a Reset and start again from scratch. Certainly would appreciate any help if someone out there has had a similar experience.
Click to expand...
Click to collapse
FWIW: This process worked for me:
http://forum.xda-developers.com/showthread.php?p=44165374#post44165374
My apologies for posting a question on what is most likely the wrong forum - but after 15-minutes of searching, I could not find the right forum for a new Galaxy Tab Active 2 question.
This is a question more related to software and may be more generic ?
My wife is the owner of a new Galaxy Tab Active 2 , and she is struggling to have her many Android applications installed not on the 16-GByte internal memory, but instead on a 128 GB microSD card she has in the Tablet. She has found various guides, but they either are not applicable to Active2 (as their menu options don't exist on Active 2) or they simply only work for some apps but not the necessary/important to her applications that she wants to transfer to the microSD card. In particular she would like the application "Line" ( https://play.google.com/store/apps/details?id=jp.naver.line.android&hl=en ) and also "WhatsAPP' (https://play.google.com/store/apps/details?id=com.whatsapp&hl=en) configured such that all their data goes on the microSD card. Unfortunately (especially for Line) she has not been able to do such.
Can anyone point me to the correct forum area ?
Again - my apologies for likely posting in the wrong area.
I own tab active 2 sm-390 too. 16gb is really not enough. We can only wait some professional to root the machine. Once root, we can try 'adaptive storage' or other app like 'App2SD' to save internal storage.
Just want to update you that I solve the storage problem.
1) You need to download the firmwire , extract the 'boot.img' file. Then, copy the file to your tablet.
2) Then, you have to install Magisk Manager and run the manager to patch the 'Boot.img'. In setting, remember to set the output file to odin format.
3) Copy the patched file to computer. In computer, run odin to install the patched file to tablet.
4) The tablet will then be reset. Now, the tablet is already rooted.
5) Then, run Apps2SD, you can move all apps to SD.
I am now have around 50 apps installed.
Please a step by step
Awesome!
You are such a genius to give us this good news
Can you please provide us a step by step guide and also the links to the files so that we can follow.
Thank you so much
How are you getting root.
I have the galaxy tab active 2 / T395 and have tried all the stand alone apks out there that claim they can root any android device; 'KingRoot, KingoRoot, OneClickRoot, z4mod.z4root, Rootmaster and Framaroot'. But do absolutely nothing for the T395 active 2.
However I can confirm that 'mark.mccv' method of rooting DOES WORK for the T395.
I guess the days of using CF-Auto Root & TWRP are over for the newer Nougat 7.1.1
mark.mccv said:
Just want to update you that I solve the storage problem.
1) You need to download the firmwire , extract the 'boot.img' file. Then, copy the file to your tablet.
2) Then, you have to install Magisk Manager and run the manager to patch the 'Boot.img'. In setting, remember to set the output file to odin format.
3) Copy the patched file to computer. In computer, run odin to install the patched file to tablet.
4) The tablet will then be reset. Now, the tablet is already rooted.
5) Then, run Apps2SD, you can move all apps to SD.
I am now have around 50 apps installed.
Click to expand...
Click to collapse
You forgot to mention, when installing the 'patched_boot.img' you need to turn 'OFF' both the FRP & OEM locks. Otherwise, when trying to flash the 'patched_boot.img' through Odin on the PC.
The devices download screen shows 'custom binary boot file' blocked by the FRP & OEM locks......
For anyone stuck on this ROOT process , you turn off the FRP lock by just deleting your Google accounts from your devices settings page.
Remove, turn OFF the OEM lock , by going to 'settings' > 'developers tools' > 'oem unlock'
On flashing the patched_boot.img , you will see a verification screen page after reboot, which forces you to reset, reformat your device. So back up your files beforehand.
Once reset, your device is rooted, ready to install busybox , adaway etc.
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info.
Crap: posetd this is two threads, realized i was typeing in the wrong one, cut and pasted and still hit send. oops
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Also, If you are having any trouble, then you can take a look at this thread (more detailed): https://forum.xda-developers.com/galaxy-tab/help/how-to-root-samsung-galaxy-tab-active-2-t3775664
Last thing, you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)
Did App data remain after rooting
mark.mccv said:
Just want to update you that I solve the storage problem.
1) You need to download the firmwire , extract the 'boot.img' file. Then, copy the file to your tablet.
2) Then, you have to install Magisk Manager and run the manager to patch the 'Boot.img'. In setting, remember to set the output file to odin format.
3) Copy the patched file to computer. In computer, run odin to install the patched file to tablet.
4) The tablet will then be reset. Now, the tablet is already rooted.
5) Then, run Apps2SD, you can move all apps to SD.
I am now have around 50 apps installed.
Click to expand...
Click to collapse
Hi mark.mccv
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.
I just came across a little gem, my uncle Gave me his T397U that he used to use for work, but has since upgraded!!!! I was so stoked until I powered up to realize that’s its full on knox mdm and is running what I’m assuming is the OS from his job, accessing reg samsung os at all is only possible through safe mode at the present moment ...I apologize if I’m in the wrong area, I’m vey New and honestly not even navigating around the boards to efficiently just yet ! Hopefully someone will want to throw me a bone! Thank you all for the amazing plethora of information!!!!