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
WARNING! ONLY USE THIS ON THE GT-I9192 MODEL!
Hello all S4 Mini owners!
I'm happy to finally release ClockworkMod recovery and an insecure kernel for the GT-I9192. With these two installed on your device, obtaining root is easy.
Attached to this post is the necessary files needed for this task. Download the following files:
Odin_v3.09.zip (if you don't have it already)
recovery-clockwork-6.0.5.1-serranodsdd.tar.zip
S4Mini_RootKit_v2.zip (contains SuperSU v1.89 and BusyBox v1.21.1)
Extract recovery-clockwork-6.0.5.1-serranodsdd.tar.zip file to your computer.
The procedure is as:
Copy the "S4Mini_RootKit_v2.zip" to your device SD card.
Turn off the phone.
Press and hold home, volume down and power. Download screen should appear.
Connect USB cable, and press volume up.
Start Odin, uncheck "F. Reset Time", and then click AP button.
Select "recovery-clockwork-6.0.5.1-serranodsdd.tar.md5" file that you previously extracted, and press Start button. The phone will reboot when finished.
After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode.
Select the option to install the ZIP file you have previously copied to your device and begin flashing it.
After flashing using CWM, reboot into system and enjoy your rooted device.
To get rid of the the warnings about applications doing not permitted actions, delete the following files from system/app, or let SuperSU fix it for you.
KNOXAgent.apk
KNOXStore.apk
ContainerAgent.apk
Link to a test build of CM 10.2 coming in a bit. Support for multi SIM support was merged into CM earlier, so I thought I'd put out a test build to let you guys test if it's working or not.
CM 10.2 test build: http://goo.im/devs/arco/serranodsub/cm-10.2-20131022-UNOFFICIAL-serranodsub.zip
You need to flash it with the recovery I posted in first post.
arco68 said:
CM 10.2 test build: http://goo.im/devs/arco/serranodsub/cm-10.2-20131022-UNOFFICIAL-serranodsub.zip
You need to flash it with the recovery I posted in first post.
Click to expand...
Click to collapse
Unfortunately, System UI has stopped.
Sim card also not found.
Difference with other rooting methods....???
arco68 said:
WARNING! ONLY USE THIS ON THE GT-I9192 MODEL!
Hello all S4 Mini owners!
I'm happy to finally release ClockworkMod recovery and an insecure kernel for the GT-I9192. With these two installed on your device, obtaining root is easy.
Attached to this post is the necessary files needed for this task. Download the following files:
Odin_v3.09.zip (if you don't have it already)
recovery-clockwork-6.0.4.4-serranodsub.tar.zip
S4Mini_RootKit_v1.zip (contains SuperSU v1.65 and BusyBox v1.21.1)
Extract recovery-clockwork-6.0.4.4-serranodsub.tar.zip file to your computer.
The procedure is as:
Copy the "S4Mini_RootKit_v1.zip" to your device SD card.
Turn off the phone.
Press and hold home, volume down and power. Download screen should appear.
Connect USB cable, and press volume up.
Start Odin, uncheck "F. Reset Time", and then click AP button.
Select "recovery-clockwork-6.0.4.4-serranodsub.tar.md5" file that you previously extracted, and press Start button. The phone will reboot when finished.
After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode.
Select the option to install the ZIP file you have previously copied to your device and begin flashing it.
After flashing using CWM, reboot into system and enjoy your rooted device.
To get rid of the the warnings about applications doing not permitted actions, delete the following files from system/app
KNOXAgent.apk
KNOXStore.apk
ContainerAgent.apk
Click to expand...
Click to collapse
Hi...
Appreciate your effort....!!
Could you please tell what is its difference from other rooting methods currently available in xda..??
Does it have BLN support...??
Awaiting your reply....
Thanx in advance.....
---------- Post added at 07:40 PM ---------- Previous post was at 07:10 PM ----------
Eagerly waiting for the working CM 10.2 Rom....!!
Please fix the errors and upload it s early as possible....!!
arco68 said:
CM 10.2 test build: http://goo.im/devs/arco/serranodsub/cm-10.2-20131022-UNOFFICIAL-serranodsub.zip
You need to flash it with the recovery I posted in first post.
Click to expand...
Click to collapse
Thank you, indeed, for all your efforts for i9192! Waiting for this fixed build, I'll test it as soon as you post it here.
I'll try this next week at home
Is this kernel for all regions?
Sent from my GT-I9192 using Tapatalk
Can you try adding the following to build.prop?
ro.telephony.ril.v3=qcomdsds
arco68 said:
Can you try adding the following to build.prop?
ro.telephony.ril.v3=qcomdsds
Click to expand...
Click to collapse
is it change samething?
Alexannino said:
is it change samething?
Click to expand...
Click to collapse
To see if it fixes the sim card not found issue. If not then I don't know what's wrong, as I don't have this phone myself so I can test. Could be that the multi sim stuff in 4.3 isn't compatible with the current drivers available for this phone, and in that case it won't be possible to have a working CM for it.
arco68 said:
Can you try adding the following to build.prop?
ro.telephony.ril.v3=qcomdsds
Click to expand...
Click to collapse
Could you rebuild ROM or create separate flashable zip for correct build.prop, please? Your recovery is incompatible with AROMA filemanager, cannot apply corrections after flashing ROM
Sent from my GT-I9195 using XDA Premium 4 mobile app
---------- Post added at 09:58 PM ---------- Previous post was at 09:53 PM ----------
Arco, the reason we cannot change props file from ROM itself is that device is stuck on welcome screen with SystemUI crash messages.
Sent from my Galaxy S4 Mini GT-I9192
Upd: Editing build.prop did not fix neither no sim/network message, nor systemui force close
Maybe there is something deeper than just drivers? Framework for them, for example? When running I9192 with I9195 ROM, systemui does not perform fc.
Weird. Try removing the following from build.prop. It should work in single sim card mode then.
Code:
# System prop to enable DSDS
persist.dsds.enabled=true
persist.multisim.config=dsds
# System prop for DSDS model *no binding subscription for QMI_WDS* message
persist.radio.dont_use_dsd=true
Is sim card and network working with the 9195 rom?
arco68 said:
Weird. Try removing the following from build.prop. It should work in single sim card mode then.
Code:
# System prop to enable DSDS
persist.dsds.enabled=true
persist.multisim.config=dsds
# System prop for DSDS model *no binding subscription for QMI_WDS* message
persist.radio.dont_use_dsd=true
Is sim card and network working with the 9195 rom?
Click to expand...
Click to collapse
I have to use my I9192 as primiary device on this weekend, so I will test it out after 27th.
Nope, no network (but no empty sim slot message) on official cm roms from I9190 and I9195.
Sent from my Galaxy S4 Mini GT-I9192
arco68 said:
WARNING! ONLY USE THIS ON THE GT-I9192 MODEL!
Hello all S4 Mini owners!
I'm happy to finally release ClockworkMod recovery and an insecure kernel for the GT-I9192. With these two installed on your device, obtaining root is easy.
Attached to this post is the necessary files needed for this task. Download the following files:
Odin_v3.09.zip (if you don't have it already)
recovery-clockwork-6.0.4.4-serranodsub.tar.zip
S4Mini_RootKit_v1.zip (contains SuperSU v1.65 and BusyBox v1.21.1)
Extract recovery-clockwork-6.0.4.4-serranodsub.tar.zip file to your computer.
The procedure is as:
Copy the "S4Mini_RootKit_v1.zip" to your device SD card.
Turn off the phone.
Press and hold home, volume down and power. Download screen should appear.
Connect USB cable, and press volume up.
Start Odin, uncheck "F. Reset Time", and then click AP button.
Select "recovery-clockwork-6.0.4.4-serranodsub.tar.md5" file that you previously extracted, and press Start button. The phone will reboot when finished.
After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode.
Select the option to install the ZIP file you have previously copied to your device and begin flashing it.
After flashing using CWM, reboot into system and enjoy your rooted device.
To get rid of the the warnings about applications doing not permitted actions, delete the following files from system/app
KNOXAgent.apk
KNOXStore.apk
ContainerAgent.apk
Click to expand...
Click to collapse
I am running I9192UBUAMH2.
I was able to flash the recovery you posted, however I can't enter on it with VOL UP+HOME+PWR. Simply got a blank screen and after some seconds the phone reboots normally...
Ops, my bad. I got it working...
Thanks!
Arco, i've tried to delete persist.dsds.enabled etc. strings, systemui works now, but no network. What exactly did you modify in this CM build? Any information helps
Sent from my Galaxy S4 Mini GT-I9192
Corias said:
Arco, i've tried to delete persist.dsds.enabled etc. strings, systemui works now, but no network. What exactly did you modify in this CM build? Any information helps
Sent from my Galaxy S4 Mini GT-I9192
Click to expand...
Click to collapse
Take a look here:
https://github.com/arco/android_device_samsung_serranodsub
https://github.com/arco/android_vendor_samsung_serranodsub
That should be all you need to build for the I9192. I'm not sure why network isn't working on this device, but it might be because the multi-sim for 4.3 that CM integrated doesn't work properly with the 4.2 libs from stock rom.
touch version
Hi,
is possible to realize the touch version of this recovery?
thanks
My co-worker...just got the samsung s 4 mini dous about a week ago (model number GT-I9192). I want to help her root...but her baseband and build number both end with "XXXUAMH2" and doesnt match the number shown on the first post of this thread. She has checked to see if there was a system update, but the phone says its up to date. Can her phone still be rooted using the file on this thread or do she need a new set of files? I have searched the form for rooting information for her phone...but all I see is info for the other models Ex. I9190 and I9195 etc....
Perhaps someone can point us in the right direction. any help would be appreciated. Thanks!
Yes you can root with this method but I suggest to flash stock kernel again after root
Sent from my GT-I9192 using Tapatalk
fburgos said:
Yes you can root with this method but I suggest to flash stock kernel again after root
Sent from my GT-I9192 using Tapatalk
Click to expand...
Click to collapse
Ok great...two things...
First: Where is the stock kernel link?
Second: Why would I need to flash it after?
Koodo Mobile: http://downloadmirror.co/android/tq/G900W8VLU1COI4_G900W8OYA1COI4_KDO.zip
SaskTel: http://downloadmirror.co/android/tr/G900W8VLU1COI4_G900W8OYA1COI4_BWA.zip
Virgin Mobile: http://downloadmirror.co/android/ts/G900W8VLU1COI4_G900W8OYA1COI4_VMC.zip
Bell Mobil: http://downloadmirror.co/android/tt/G900W8VLU1COI4_G900W8OYA1COI4_BMC.zip
Rogers: http://downloadmirror.co/android/tu/G900W8VLU1COI4_G900W8OYA1COI4_RWC.zip
Telus: http://downloadmirror.co/android/tv/G900W8VLU1COI4_G900W8OYA1COI4_TLS.zip
Fido Mobile: http://downloadmirror.co/android/tw/G900W8VLU1COI4_G900W8OYA1COI4_FMC.zip
Source: http://www.theandroidsoul.com/downl...1-update-g900w8vlu1coi4-with-root-info-85381/
Nice, which I've would I download for Wind Mobile?
If Flash fire shows protected on some partitions does that mean I have to use Odin on PC?
Spacemonkie4207 said:
Nice, which I've would I download for Wind Mobile?
Click to expand...
Click to collapse
The Wind Mobile firmware is always released under its parent company's name, Globalive, which is not listed here. It's CSC is GLO if you can find it elsewhere. But it really doesn't matter at all. The last few releases that were labelled Globalive were literally just the Bell version renamed. You can use any of the firmware versions above if you want. I used the Telus one a couple of times, just because I have a grudge against Bell and Rogers. But it makes absolutely no difference.
hexavoodoomal said:
The Wind Mobile firmware is always released under its parent company's name, Globalive, which is not listed here. It's CSC is GLO if you can find it elsewhere. But it really doesn't matter at all. The last few releases that were labelled Globalive were literally just the Bell version renamed. You can use any of the firmware versions above if you want. I used the Telus one a couple of times, just because I have a grudge against Bell and Rogers. But it makes absolutely no difference.
Click to expand...
Click to collapse
Where can I find the proper apn settings?
Zehlek said:
If Flash fire shows protected on some partitions does that mean I have to use Odin on PC?
Click to expand...
Click to collapse
use odin in pc
Spacemonkie4207 said:
Where can I find the proper apn settings?
Click to expand...
Click to collapse
Google it.
Whats new ?
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
brayhanrd said:
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
Click to expand...
Click to collapse
I have 900M so i cant install, maybe anyone can post anything, but 99% sure didnt have themes
Enviado de meu SM-G900F usando Tapatalk
brayhanrd said:
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
Click to expand...
Click to collapse
I think it is more under the hood updates
Sent from my SM-G900W8 using Tapatalk
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results.
Any suggestions?
Thanks.
daroco said:
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
Only with custom kernel
Enviado de meu SM-G900F usando Tapatalk
Thanks bro! I thought about it but I didn't think it mattered. I'll give it a go.
No dice as of yet, custom kernels are not booting either, good thing I had the sense to do a bacup first
☺
daroco said:
Thanks bro! I thought about it but I didn't think it mattered. I'll give it a go.
No dice as of yet, custom kernels are not booting either, good thing I had the sense to do a bacup first
Click to expand...
Click to collapse
The way I usually root is to flash CF-Auto-Root-kltecan-kltevl-smg900w8.tar using odin. Can you try that?
I haven't updated yet until I'm sure root is there as I gave the phone to my wife.
thanks
Still bootloops when I flashed CF-Autoroot. it also installed the original recovery from another BL version. I reflashed TWRP and cleared cache and dalvik (not that I expected it to do much) but still the same. restored a nandroid and I had all kinds of apps FC. End result was to factory reset the phone to be in a stable condition. If this was a car I could get this damn thing running right! I should have learned more about programming while I was in school...... 2 kids and a mortgage I have no time for it now.
[HOWTO] Root your 5.1.1 G900W8VLU1COI4 firmware
daroco said:
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results. [...]
Click to expand...
Click to collapse
mauriicio21 said:
Only with custom kernel
Click to expand...
Click to collapse
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
-------------------------------------------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions list from your 5.1.1 firmware (in all Snapdragon S5 variants contexts/permissions are the same). I require it as I would like to be well prepared with my custom ROMs for G900F/FD. I believe that Android 5.1.1 for G900F/FD is just a matter of a few days...
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rooted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
_alexndr said:
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions/symlinks list from your 5.1.1 firmware. I require it to be well prepared with my custom firmware for G900F. I believe that Android 5.1.1 for G900F is just a matter of a few days.
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rotted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
Click to expand...
Click to collapse
Do you Know how can i get spanish on this Vertion plz. ? @_alexndr
_alexndr said:
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions list from your 5.1.1 firmware (in all Snapdragon S5 variants contexts/permissions are the same). I require it as I would like to be well prepared with my custom ROMs for G900F/FD. I believe that Android 5.1.1 for G900F/FD is just a matter of a few days...
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rotted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
Click to expand...
Click to collapse
Hope this helps, thanks for your help.
Here you go!
Just confirmed the camera can shoot in RAW format
Special thanks to @funkyboy1281, @lentm, @macboy3000 for helping getting this work. As far as I can tell, this is the easiest and most straight forward instruction set for getting Android Pay to work on the latest version of Pure Nexus, Chroma, or OMNI Rom
Clean Flashing
Download the appropriate Rom.
Pure Nexus DiscussionChroma DiscussionOMNI (no link available, sorry)
Download Pure Nexus Dynamic Gapps 2-3-16 (Very important, you cannot use 15-3-16 or later). Yes, even if you use Chroma or OMNI, these Gapps should work for you. Link
Download the unSU script for completely unrooting before installing systemless root. Link
Download SuperSU 2.68 (or higher) Link || Discussion
Advance wipe in recovery all but internal storage
Install the ROM, gapps, and unSU
Optional: Install custom kernel
In TWRP, under advanced, go to terminal and type the following:
Code:
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Note: You may also do this using ADB in recovery (adb shell, and then enter the same commands. This is much easier in my opinion, and is the method I used.
Flash 2.68 beta in TWRP
Fully reboot, go through initial device setup
Verify in SuperSU that you cannot install SU to the system. This will verify that we are using the systemless root option
Download SafetyNet Helper and make sure it passes
Install Android Pay and profit!
Dirty Flashing
Verify that SafetyNet still passes in Android.
Verify in Android that /data/.supersu is still present and contains the appropriate options (see clean flashing). You may also verify in recovery by going to terminal commands and entering in:
Code:
cat /data/.supersu
Install the updated ROM (do not reinstall gapps unless your ROM builder specifically tells you to do so. Pure nexus does not require a reflash)
Optional: Install unSU. This was not necessary on PureNexus, but I cannot be sure for other roms. It shouldn't hurt anything to flash.
Optional: Install custom kernel
Install SuperSu 2.68 (or higher)
Check SafetyNet Helper and make sure it still passes
FAQ
Q. Can I still install and use AdAway?
A. Yes. You must first install something in recovery before installing AdAway. See the discussion Thread. You should be installing v3.1 of the app after you install the recovery zip.
Q. Can I still use V4A?
A. Yes. I do not use this however, but it has been reported that nothing special needs to be done.
Q. Can I change the screen density?
A. We have not found a way to do this without tripping Safety Net
..
@skaforey thanks for this thread! Might want to note in the OP that Wiping Data erases the internal storage. Some people may not know that.
MrBrady said:
@skaforey thanks for this thread! Might want to note in the OP that Wiping Data erases the internal storage. Some people may not know that.
Click to expand...
Click to collapse
Noted, thank you! Still hoping some of the lucky folks that have it working can help us out here.
Has anyone found a way to adjust the screen density while keeping Android Pay functional?
MrBrady said:
Has anyone found a way to adjust the screen density while keeping Android Pay functional?
Click to expand...
Click to collapse
You (should) be able to change the density through adb using
Code:
adb shell wm density DPI
with dpi being what you want, or if you have root you can do that from a terminal emulator, just remove the adb shell part.
I tried the 2nd method without formating data in different combos to no avail, still hesitant to wipe my internal sdcard, it shouldn't be that hard man, will follow this thread
anyone know other aosp ROMs that have AP working outside of pure nexus?
Sent from my Nexus 6 using Tapatalk
Following the steps in the top most instructions in the OP...
1) Pure Nexus 3/8 does not have root out of the box, so the Unroot step was not needed.
2) TWRP did not show any files/folders in the /su directory, so the Terminal command didn't work. I booted up the device and did it through the Terminal there instead and then rebooted.
After that, loaded up Android Pay and it says "Android Pay can't be used".
Running SafetyNet reports....
SafteyNet request: success
Response validation: success
CTS profile match: false
Tried different methods, not working for me.
1. Download Pure Nexus 1/03/16 or newer (Layers), the latest PN GApps, UnSU, the latest SuperSU.
2. Backup any important data.
3. Boot into TWRP and wipe everything including internal storage
4. Format data.
5. reboot TWRP with USB-OTG that has fines necessary.
6. Flash Pure Nexus.
7. Flash GApps.
8. Flash UnSU.
9. In terminal I saw I still had a folder /supersu so I deleted that.
reboot. Setup phone with google account. Did not have it restore apps, but did have it restore basic setup from google.
Install Safetynet helper
Still fail CTS Profile Match
Don't know what the people are doing different, but not working for me.
Are you using the PN-Gapps or others?
The updated-unsu is what date?
Thanks!
The only way I have gotten AP to work is from a stock image based ROM. It doesn't seem to work with AOSP ROMs like Pure Nexus.
For example, I am currently running Tupac's debloated stock ROM with Cataclysm MOD, Viper4Android and AdAway ad blocking. Android Pay works fine, as long as you follow the SU steps listed in the OP of this thread.
What I did to get AP to work was removing these lines from updater-script located in META-INF > com > google > android
Code:
ui_print("Flashing SuperSU..");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
ui_print(" ");
and removed the supersu folder inside the zip file. I then installed my custom kernel and systemless supersu. After that, I set the permissions for bin folder inside su to 751 using a root explorer and deleted xbin_bind.
@macboy3000 what kernel and what version of SuperSU did you use, ? I tried your method, ROM booted fine but safetynet test failed...
this is how I did it
unzip ROM
edit code out
delete supersu folder
zip ROM
advance wipe everything but internal
flash ROM
flash pn gapps
flash elemental kernel
flash supersu
boot into android, delete xbin_bind
reboot system
permissions on bin folder were already 751, so didn't need to change
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
@macboy3000 what kernel and what version of SuperSU did you use, ? I tried your method, ROM booted fine but safetynet test failed...
this is how I did it
unzip ROM
edit code out
delete supersu folder
zip ROM
advance wipe everything but internal
flash ROM
flash pn gapps
flash elemental kernel
flash supersu
boot into android, delete xbin_bind
reboot system
permissions on bin folder were already 751, so didn't need to change
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Weird...I'm using SuperSU 2.67 and I'm also using Elemental kernel.
macboy3000 said:
Weird...I'm using SuperSU 2.67 and I'm also using Elemental kernel.
Click to expand...
Click to collapse
Did you format data? I'll give it a shot with 2.67, I used 2.68
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
Did you format data? I'll give it a shot with 2.67, I used 2.68
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I formatted everything except internal storage before installing.
macboy3000 said:
What I did to get AP to work was removing these lines from updater-script located in META-INF > com > google > android
Code:
ui_print("Flashing SuperSU..");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
ui_print(" ");
and removed the supersu folder inside the zip file. I then installed my custom kernel and systemless supersu. After that, I set the permissions for bin folder inside su to 751 using a root explorer and deleted xbin_bind.
Click to expand...
Click to collapse
Well I tried this and still no luck
I even tried flashing the modified ROM, gapps, and never flashing SuperSU at all (so my rom wasn't rooted at all), and SafetyNet still gives me a red screen. I really wish I knew what was triggering this for some and how others can make it work.
I tried again using 2.57 SuperSU and Elemental X and still fails. Would someone that got it working be able to post a more detailed log of exactly what steps you're using and exactly what files you're flashing.
MrBrady said:
The only way I have gotten AP to work is from a stock image based ROM. It doesn't seem to work with AOSP ROMs like Pure Nexus.
For example, I am currently running Tupac's debloated stock ROM with Cataclysm MOD, Viper4Android and AdAway ad blocking. Android Pay works fine, as long as you follow the SU steps listed in the OP of this thread.
Click to expand...
Click to collapse
This has been my experience as well !
jcrompton said:
This has been my experience as well !
Click to expand...
Click to collapse
Got Android Pay working with Tupac's debloated stock ROM too! Thanks!
Is it possible to change DPI and keep Android Pay working?
lentm said:
Got Android Pay working with Tupac's debloated stock ROM too! Thanks!
Is it possible to change DPI and keep Android Pay working?
Click to expand...
Click to collapse
Not that I have found, unfortunately. Even via just ADB commands.
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.