Related
USE THIS SCRIPT AT YOUR OWN RISK
Prerequisites:
1. Unlocked Bootloader
2. CWM Recovery for unlocked bootloader installed
Code:
Changelog 27.7.2011:
- su and superuser updated to latest version
- fixed issue with permissions
- works correctly with Titanium Backup
Changelog 26.7.2011:
- added sqlite3 binary
- su and busybox updated to latest version
How to:
1. Download "root_cwm.zip" (bellow in Attached Files)
2. Copy it to sdcard or sdcard-ext
3. Reboot into CWM recovery
5. Click "install zip from sdcard"
6. Choose zip from sdcard
7. Pick the "root_cwm.zip"
8. Install
9. Reboot
Tested on kennethpenn's [ROM] AT&T 4.5.91 ★ Gingerbread 2.3.4, but should work on any ROM available.
Can you please upload the .zip?
kennethpenn said:
Can you please upload the .zip?
Click to expand...
Click to collapse
its there in attached files...
kamma said:
its there in attached files...
Click to expand...
Click to collapse
Edit: im an idiot.
Awesome
Sent from my MB860 using XDA Premium App
Worked like a charm. Thanks!
goscrewsir said:
Worked like a charm. Thanks!
Click to expand...
Click to collapse
glad to hear...
So is the only difference between these two threads (this one and http://forum.xda-developers.com/showthread.php?t=1140110) that the other is for the HKTW... orrrrr? =) and thanks anyway, I'm about to use your .zip right now
Worked beautifully when preinstall didn't, thank you
wow! this is awesome!
This is great!!!
I used this to obtain root in OTA 4.5.91 but I'm have some problems. Root explorer and terminal can access root, but Titanium Backup, busybox, and SQLite Editor cant get root access. USB debugging is turned on, and same for 3rd party install.
Anyone have any idea what's causing this?
Can you read/write in root explorer?
GuerillaZhou said:
I used this to obtain root in OTA 4.5.91 but I'm have some problems. Root explorer and terminal can access root, but Titanium Backup, busybox, and SQLite Editor cant get root access. USB debugging is turned on, and same for 3rd party install.
Anyone have any idea what's causing this?
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
i got it working, just manually copied su from /preinstall to /system/bin, and sqlite and titanium works now
how do i install CWM before I am rooted?
ekerbuddyeker said:
how do i install CWM before I am rooted?
Click to expand...
Click to collapse
unlock BL and then go to fastboot mode and install CWM
munchy_cool said:
unlock BL and then go to fastboot mode and install CWM
Click to expand...
Click to collapse
can you elaborate. I am in fastboot mode. How do I install CWM?
Hi,
For me, the flashing appears to be successful, but when I boot into recovery I'm getting the stock recovery. I think the issue is with /system/etc/install-recovery.sh, but I have no clue how to remove this file from my phone. I can't change the permissions or the file even with root access. Anyone have any advice?
Thanks!
ekerbuddyeker said:
can you elaborate. I am in fastboot mode. How do I install CWM?
Click to expand...
Click to collapse
Here you go buddy: http://forum.xda-developers.com/showthread.php?t=1154600
kamma said:
USE THIS SCRIPT AT YOUR OWN RISK
Prerequisites:
1. Unlocked Bootloader
2. CWM Recovery for unlocked bootloader installed
How to:
1. Download "root_cwm.zip" (bellow in Attached Files)
2. Copy it to sdcard or sdcard-ext
3. Reboot into CWM recovery
5. Click "install zip from sdcard"
6. Choose zip from sdcard
7. Pick the "root_cwm.zip"
8. Install
9. Reboot
Tested on kennethpenn's [ROM] AT&T 4.5.91 ★ Gingerbread 2.3.4, but should work on any ROM available.
Click to expand...
Click to collapse
Thanks a lot dude...
Easy as pie!
Cheers!
Rayan
YOU HOLD MYSELF AND XDA FREE FROM ANY LIABILITY. WE ARE NOT RESPONSIBLE FOR YOUR DEVICE. FLASH AT YOUR OWN RISK.
This will enable Native Tether for Build 183.46.15. Shout out goes to iKrYpToNite for his work with this.
Prerequisites:
Droid RAZR M Rooted or unlocked on 183.46.15
METHOD 1: TWRP INSTALL
1) Download the package below labeled "183.46.15_tether_twrpinstall".
2) Reboot Into TWRP recovery and navigate to the file for flashing.
3) Reboot
4) Verify tether works
5) Profit.
METHOD 2: MANUAL INSTALL
1) Download the package below labeled "183.46.15_tether_manual".
2) Download root browser by Jrummy from the play store
3) Navigate to System/Priv-App and rename VZWEntitlementservice.apk to VzwEntitlementservice.apk.bak.
4) Navigate to System and rename the build.prop to build.prop.bak
5) Place the package on the root of your sd card and extract the build.prop file within the folder.
6) Navigate to system and Copy and paste the new file.
7) Set permissions for the file to
Owner: Read/Write
Group: Read
Others: Read
This should show (rw-r--r--)
8) Reboot. Verify tether works
9) Profit.
REVERTING
METHOD 1:
If installed in twrp, download the package below labeled 183.46.15_tether_revert. Flash in Twrp, reboot, verify subscription check re-enabled.
METHOD 2:
If manually installed, simply delete the build.prop you installed, remove the .bak extension from the original build.prop, verify permissions, reboot.
If you enjoyed this, consider donating! I do appreciate it.
Topsnake said:
METHOD 1: TWRP INSTALL
1) Download the package below labeled "183.46.15_tether_twrpinstall".
2) Reboot Into TWRP recovery and navigate to the file for flashing.
3) Reboot
4) Verify tether works
5) Profit.
Click to expand...
Click to collapse
I can confirm that tethering does work on the latest 183.46.15 build using this method. I flashed the .zip in TWRP, rebooted, and the Mobile Hotspot is now working. Thank you for working on this for all of us!
ScallywagginIT said:
I can confirm that tethering does work on the latest 183.46.15 build using this method. I flashed the .zip in TWRP, rebooted, and the Mobile Hotspot is now working. Thank you for working on this for all of us!
Click to expand...
Click to collapse
No problem!
Thanks for your time again Topsnake... I'll be flashing .15 when I get home was kinda hoping you would put one out for the update...
We cannot teach people anything; we can only help them discover it within themselves.
Hello
Whats the lines should be added to original build prop? or what needs to be changed?
i m confused
u said u can flash native tether using twrp recovery in 183.46.15 build...
but i read in most forums that 183.46.15 build cant be unlocked nor can install custom recovery.. so how u can flash native tether using twrp..
plz tell me if there is a way to install twrp in 183.46.15 build.. i tried lot to install twrp but nothing working..
rahulbeast said:
u said u can flash native tether using twrp recovery in 183.46.15 build...
but i read in most forums that 183.46.15 build cant be unlocked nor can install custom recovery.. so how u can flash native tether using twrp..
plz tell me if there is a way to install twrp in 183.46.15 build.. i tried lot to install twrp but nothing working..
Click to expand...
Click to collapse
bootloader was unlockable before 183.46.15
if bootloader is unlocked, updating doesnt lock the bootloader
if bootloader is locked you just need root access to
to change the build.prop
XT907 with kernel date July 2014 or after
can now be unlocked with sunshine app
http://theroot.ninja/download.html
xda thread: http://forum.xda-developers.com/showthread.php?t=2792487
free to test compatibility, $25 to unlock
I would root with hydrogen peroxide, even though kingroot or temporary root should work too
Sent from my XT1060 using XDA Labs
---------- Post added at 03:27 PM ---------- Previous post was at 03:26 PM ----------
see method #2
Sent from my XT1060 using XDA Labs
what exactly is edited in the build prop? so I can just make the changes myself without losing my current build prop edits. Thanks!
motolio said:
what exactly is edited in the build prop? so I can just make the changes myself without losing my current build prop edits. Thanks!
Click to expand...
Click to collapse
post #1 method 2
hello a question like I can put transparent bars of notification and navbars, can you teach me?
Hello, everyone!
TL;DR: You're about to perform a systemless root installation on your phone so make sure you have uninstalled Xposed Framework, uninstalled root, the device's bootloader is unlocked and your phone's boot image is in its untouched stock state. Then boot into TWRP and install SuperSU-v.279-SR3 or newer.
UPDATE 2017-01-19:
- Provided missing bootloader information regarding root. Thanks, @Charlita for the heads-up!
- Moved TL;DR section to the top.
UPDATE 2017-01-15:
- SuperSU-v.279-SR3 learned how to use systemless mode as default flashing method for Motos. This is great news as the installation process now is just a matter of flashing the SuperSU installer. The segmentation fault had been fixed on SR2 and this version also includes that fix.
- Included a TL;DR section.
UPDATE 2016-12-25:
- SuperSU-v.279-SR1 contains a regression bug regarding the "segmentation fault". Skip this version for now. I've already contacted Chainfire.
- suhide: as the Chainfire himself stated, the tool is a losing game so I'm not putting any further effort here.
UPDATE 2016-11-03:
- As of SuperSU-v2.78-SR3 boot image patching works out-of-the-box. Just install it and you're done!
- TWRP version 3.x works as expected.
- Unfortunately, SafetyNet checking fails as Google constantly updates the server-side code.
- WIP: Check if Chainfire's suhide are able to help here.
UPDATE 2016-08-08:
- Added a backup reminder.
- Added flashable zip systemless_root_enabler_by_glauberlima.zip.
After a few days playing with it, I finally managed to perform a systemless root install for our beloved Moto X 2014
Benefits:
- Install OTA updates when they arrive;
- SafetyNet checking will pass so Android Pay can be used (not available in Brazil yet).
Requirements (links below) :
- Android 6 Marshmallow
- Bootloader must be unlocked otherwise you won't be able to root your phone;
- Boot partition must be in its original untouched stock state otherwise, SuperSU installer won't be able to patch it;
- System partition must be untouched as well but a simple uninstall of applications that have changed it should be enough. This step is not mandatory but if your system partition remains changed SafetyNet checking will fail;
- Your device must be unrooted. SuperSU has the option "Completly remove root". Use it;
- If you have Xposed Framework installed, uninstall it;
- You'll need ADB and Fastboot in order to flash stock boot.img if applicable;
- TWRP. Version 3.0.2-2 works just fine. If you prefer 2x series, I highly recommend version 2.8.7.1;
- SuperSU-v2.79-SR3 zip installer (or a newer version). DO NOT TRY AN OLDER VERSION. WILL NOT WORK;
Install guide:
- Make a Nandroid backup first using TWRP;
- Uninstall Xposed Framework if applicable;
- Uninstall SuperSU;
- Connect your device to your computer via USB;
- Reboot into bootloader:
Code:
adb reboot-bootloader
- Restore stock boot partition (you can skip this step if you already been on stock boot):
Code:
fastboot flash boot xt1097_boot_stock_with_may_2016_update.img
VERY IMPORTANT: The binary file boot xt1097_boot_stock_with_may_2016_update.img is device dependent. I have extracted stock boot.img from victara May 2016 update full ROM package and put it here. If you are trying on the other variants, make sure you will use the right image.
- Reboot into Recovery (TWRP);
- Flash the attached zip file systemless_root_enabler_by_glauberlima.zip. This will set both variables SYSTEMLESS=true and BINDSYSTEMXBIN=false. Without these variables set, SuperSU will fail to systemless root the device. Feel free if you want to manually enter the commands in the Command Prompt:
Code:
adb shell "echo SYSTEMLESS=true>/data/.supersu"
adb shell "echo BINDSYSTEMXBIN=false>>/data/.supersu"
- Install SuperSU and reboot system. If the first boot fails, just wait - the second will work I promise you!
- As soon as Android UI shows up you should be systemless rooted;
- Confirm SuperSU is installed by recognizing the green icon on your app drawer;
- Open up any root app you have. The world-famous Superuser permission request dialog should pop-up;
- Install SafetyNet Helper, in order to attest your Android, is passing Google's SafetyNet checking: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Now you should be good. Congrats!
Go ahead and get some systemless apps:
- Systemless Xposed Framework
- Systemless Adaway
This procedure should work for the other variants too - all you need is the original boot.img
If you need any help feel free to ask.
Attached you can find the screenshots taken from my XT1097 after the procedure
Related links:
SuperSU-v2.79-SR3:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Latest stable SuperSU:
http://download.chainfire.eu/supersu-stable
Systemless Xposed Framework:
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Systemless AdAway:
http://forum.xda-developers.com/showthread.php?t=2190753
Material Design Xposed Installer:
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Minimal ADB and Fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP for Moto X 2014:
http://forum.xda-developers.com/mot...recovery-twrp-2-8-0-0-touch-recovery-t2911523
Thanks:
@Chainfire
Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk
rtrotsky said:
Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
Since your device already has the untouched stock boot you don't need to flash anything.
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
jbaumert said:
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
Click to expand...
Click to collapse
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
glauberlima said:
Could you provide your recovery.log from TWRP?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip[code]
This will copy contents to the clipboard. Paste it in notepad then save and attach here.[/QUOTE]
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse
vpxf said:
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse
Hi @vpxf
The unmodified boot.img is a requirement for SuperSU as it tries to patch the boot image on-the-fly during the install process (by the time you flash it using TWRP). If the image is not in its original state, SuperSU will fail to install in systemless mode.
Regarding your question about custom ROMs compatibility I don't know if the SafetyNet checking will pass/fail. That's a good test to perform.
glauberlima said:
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
Click to expand...
Click to collapse
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
bertolehm said:
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
Click to expand...
Click to collapse
jbaumert said:
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
Click to expand...
Click to collapse
As stated by @bertolehm I've discussed in the other posts the exactly same issue with the zip installer you have reported @jbaumert. Take a look at them:
http://forum.xda-developers.com/showpost.php?p=67792193&postcount=1193
http://forum.xda-developers.com/showpost.php?p=67805517&postcount=1233
Regarding your device being systemless rooted check with SafetyNet Helper Sample app. If everything turns green you are good
** Duplicated **
Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
oyoyl said:
Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
Click to expand...
Click to collapse
Which variant is your X?
glauberlima said:
Which variant is your X?
Click to expand...
Click to collapse
XT1092
oyoyl said:
XT1092
Click to expand...
Click to collapse
15 minutes... That's definitely too much.
I'm about to update this guide with my new findings so If you don't mind I'd like to suggest you this:
Repeat the steps but this time skip the update to latest version. After the reboot access SuperSU. It should display a message regarding your su needs update. Accept it.
Make sure your nandroid backup is up to date.
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
Hi! Hey, I followed the steps and my MotoX got stuck when rebooting after flashing. I'm trying to enter fastboot with power+Volume down but no luck so far, any idea? I hope you can help me!
oyoyl said:
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks
Click to expand...
Click to collapse
OK. Just leave a reply by the time you have the result of your test.
guilhermoaraujo said:
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
Click to expand...
Click to collapse
One of your installed apps modified system partition. Did you test on a completly stock image?
Fist of I wanna say a big thanks to - Developers of Kingroot and Flashify
Now - I don't know why nobody ever uses this method but it works all the time on almost all phones both new and old if you can gain root using an apk app even if its temp root it works and its fairly easy and fast.
Straight to the point.
1. Install kingroot ( search for it on google download and install )
2. Use the kingroot app to root your device it works - and its good.
3. Download the latest recovery of TWRP image from their site it must contain in the name wls since its a sprint version.
put the recovery on the root folder of your device.
4. Install flashify - from playstore - Grant root access and flash the recovery you downloaded it should take a few seconds then reboot to recovery and vuala ... You now have a fully functional recovery without the hassle of fastboot ( Which i f**king hate and consider a total waste of energy and a drag for the need of a PC and installation of drivers blah blah blah ...)
Now download any custom ROM of your choice and install - i use viper one 9.0.0 - its amazing.
Thank you and bye bye ...
Now if you are have troubles with invalid sim card its simple just download the latest ruu the .exe for format - install htc drivers and double click on the ruu plug your device and then follow the dialogue and install ( that simple too no fastboot :silly: ).
Then follow the he step 1 to 4
1. flash this - https://forum.xda-developers.com/attachment.php?attachmentid=2402764&d=1384892279 - via you twrp and
2. Install this "SIM Unlock Helper" - open press the back press start and grant root access.
3. Scroll down and tap on Sim Lock - it should freeze for 5-10s and then you should see your none sprint sim card.
And now you can flash any ROM without the need to sim unlock again .
That's all , Thank you.
Nice guide!
Method was kindly shown to me by user Mefody in answer to a thread I posted.
Rooting SM-T380/T385 via Magisk Manager APK v.5.5.3 & Magisk 15.2:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet Magisk Manager APK.
4. Put "boot.img" on SDCARD.
5. Run Magisk Manager, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point Magisk Manager to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google registry will be wiped.
11. After wiping & rebooting install Magisk Manager APK again... And YEAH!!! You got root!
Thanks for creating this thread. I used the original thread to root my tab, so seeing this as its own thing will be helpful to a lot of people.
a.brooding.mage said:
Thanks for creating this thread. I used the original thread to root my tab, so seeing this as its own thing will be helpful to a lot of people.
Click to expand...
Click to collapse
Now all we need is TWRP and we'll have Xposed and custom rom support
shahmir_k said:
Now all we need is TWRP and we'll have Xposed and custom rom support
Click to expand...
Click to collapse
For TWRP: https://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560
I will get this tab.
BTW, can it install Samsung Game Tuner?
mingkee said:
I will get this tab.
BTW, can it install Samsung Game Tuner?
Click to expand...
Click to collapse
Yes... Game Tuner installs & wokrs good.
Could you clarify on these two steps?
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
Nerd10 said:
Could you clarify on these two steps?
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
Click to expand...
Click to collapse
You have to open the stock firmware with an archive manager like WinRar or 7zip. Inside you should find an AP-Block folder. Inside of that should be your boot.img file
shahmir_k said:
You have to open the stock firmware with an archive manager like WinRar or 7zip. Inside you should find an AP-Block folder. Inside of that should be your boot.img file
Click to expand...
Click to collapse
Thanks, where can I find the stock firmwares?
Here is another problem
Is OEM unlock in Developer Section required to install patched kernel and TWRP with Odin?
I can't find it even it's updated.
Does anybody know if this rooting method will work with T-585 on Android 7.0 (January 2018 update)? I guess KNOX will be triggered, right?
Yours
WeT-Klb
I say the root is TOTALLY FALSE!!!
I have been waiting for two week and there's no update to enable OEM Unlock option.
I have returned the unit with restocking fee.
mingkee said:
I say the root is TOTALLY FALSE!!!
I have been waiting for two week and there's no update to enable OEM Unlock option.
I have returned the unit with restocking fee.
Click to expand...
Click to collapse
Have you tried this method even without the option in developer settings to OEM Unlock? On my SM-T350, I don't have the option to OEM unlock either. But I can still root and install TWRP anyways.
Delgoth said:
Have you tried this method even without the option in developer settings to OEM Unlock? On my SM-T350, I don't have the option to OEM unlock either. But I can still root and install TWRP anyways.
Click to expand...
Click to collapse
I tried to flash modified kernel or TWRP with Odin and I got error
Only official software can be installed.
Perhaps someone could provide boot.img files and links here?
I for instance found no matching firmwares for mine. The one that had both matching versions numbers, said it was for Cellular US. This is a wifi only model. Confused
Thanks
Barsky said:
Perhaps someone could provide boot.img files and links here?
I for instance found no matching firmwares for mine. The one that had both matching versions numbers, said it was for Cellular US. This is a wifi only model. Confused
Thanks
Click to expand...
Click to collapse
I have that original boot.img and magisk modified one.
There's a 7 days waiting period after you turned it on the first time regardless reboot or not.
I will make a instruction how to root and I will post kernel and modified kernel.
mingkee said:
I have that original boot.img and magisk modified one.
Click to expand...
Click to collapse
I didn't realize it was so effortless to pull the boot.img out. BUt, until I have that oem unlock option in there, doesn't matter.
Come on, 14 days
Finally, mine has successfully rooted with Magisk.
I will post a guide.
Trouble rooting SM-t380
shahmir_k said:
Method was kindly shown to me by user Mefody in answer to a thread I posted.
Rooting SM-T380/T385 via Magisk Manager APK v.5.5.3 & Magisk 15.2:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet Magisk Manager APK.
4. Put "boot.img" on SDCARD.
5. Run Magisk Manager, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point Magisk Manager to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google registry will be wiped.
11. After wiping & rebooting install Magisk Manager APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
When I try to flash the archived boot.tar via Odin it just hangs and sits there. Any help would be much appreciated. Thank You.