I'm trying to install the new OTA that was just released while keeping Xposed, Root, and TWRP and coming up with a process for the future to apply each OTA going forward without dealing with the mess I'm dealing with now. Any and all help is appreciated . I'm very strong and comfortable with using fastboot commands and flashing and just need someone to help me wrap my head around the process of doing this and step by step instructions of achieving my goal. So currently I have downloaded the new OTA_PERFUME_WL_M60_SENSE80GP_VZW_NA_Gen_Unlock_1.80.617.1_R-1.53.617.5_release_480240aw6u8xea6328m583.zip file. I have the latest TWRP installed on my phone, I have the latest Systemless Root zip (BETA-SuperSU-v2.74-2-forceencrypt.zip), as well as the latest Systemless Xposed zip (Xposed-v85.6-sdk23-systemless.zip). I have also downloaded the TWRP clean system Backup 1.53.617.5_twrp.zip. My phone is a T-Mobile HTC 10 that I've converted into a US Unlocked model by S-Offing it, changing the CID to the super CID (11111111), and installed the 1.53.617.5 RUU. I tried doing different steps on different guides here and now my phone is all sorts of messed up. Root isn't working 100% (es file explorer fails when trying to toggle on root explorer, but fx explorer works fine), and Xposed is broken (modules don't work, Xposed app saying no framework found even though I've flashed it). Can someone help me with what I should do to be able to install the OTA, root, have Xposed, and keep TWRP so that way in the future, I can apply and OTA and keep the rest?
Thanks!
wschamps42 said:
I'm trying to install the new OTA that was just released while keeping Xposed, Root, and TWRP and coming up with a process for the future to apply each OTA going forward without dealing with the mess I'm dealing with now. Any and all help is appreciated . I'm very strong and comfortable with using fastboot commands and flashing and just need someone to help me wrap my head around the process of doing this and step by step instructions of achieving my goal. So currently I have downloaded the new OTA_PERFUME_WL_M60_SENSE80GP_VZW_NA_Gen_Unlock_1.80.617.1_R-1.53.617.5_release_480240aw6u8xea6328m583.zip file. I have the latest TWRP installed on my phone, I have the latest Systemless Root zip (BETA-SuperSU-v2.74-2-forceencrypt.zip), as well as the latest Systemless Xposed zip (Xposed-v85.6-sdk23-systemless.zip). I have also downloaded the TWRP clean system Backup 1.53.617.5_twrp.zip. My phone is a T-Mobile HTC 10 that I've converted into a US Unlocked model by S-Offing it, changing the CID to the super CID (11111111), and installed the 1.53.617.5 RUU. I tried doing different steps on different guides here and now my phone is all sorts of messed up. Root isn't working 100% (es file explorer fails when trying to toggle on root explorer, but fx explorer works fine), and Xposed is broken (modules don't work, Xposed app saying no framework found even though I've flashed it). Can someone help me with what I should do to be able to install the OTA, root, have Xposed, and keep TWRP so that way in the future, I can apply and OTA and keep the rest?
Thanks!
Click to expand...
Click to collapse
I am also just starting this procedure... Just bought my 10 today, and I am starting slowly.. All I know is that if you dont change anything in /system directory and have stock recovery, OTAs perform fine.
So my plan is unlock bootloader, flash TWRP, root, flash ElementalX, install xposed and after that flash stock firmware. Both SuperSU AND Xposed should be systemless. I know that AdAway can also be systemless, but I have to figure out everything beucase I just charged and turn on the phone
Download Xposed for Material Design... I had the same issue with the "framework not found" error.
civicdelslow said:
Download Xposed for Material Design... I had the same issue with the "framework not found" error.
Click to expand...
Click to collapse
Yeah I've downloaded the latest. Now I have an Xposed is installed but not active error :-/
The last version (85.6) doesn't work that well. It's better to install version 85.5 which works fine.
Related
I installed a stock recovery to update to 4.4.4 OTA. I then installed TWRP(openrecovery-twrp-2.8.1.0-m8) through fastboot and attempted to install the super SU zip 2.00.
The file seemed to install properly as it gave me no errors, but I did not have root access when booting into the phone. I then tried CWM recovery (recovery-clockwork-6.0.4.8-m8). CWM installed the super SU 2.00 zip without any errors as well, but warned me before reboot that my root access was not found, I selected the option that "fixes" that, but still I am without root.
I like the 4.4.4 features but I don't want to be without root, please help me guys.
Let me know if you guys figure anything out for the stock rom. I just jumped on the latest cyanogenmod nighty till I figure this out.
Do you have s-off?
You should definitely get s-off as it makes everything so much easier.
But in the meantime, I would download the sunshine.apk and run it. It will reboot your phone and ask you to confirm and enter PayPal info. I believe your phone at this point has a soft root. If you now run superSU and allow it to install the binary, you should have root.
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Flashing Custom Recovery
I downloaded official TWRP recovery from teamw.in and decided to go the hard way and install the recovery doing dd fom command line (ConnectBot) - I was hoping this will help me to keep the warranty. Worked just fine, but tripped Knox bit nevertheless. NB: avoid extra hassles and just use Odin to install recovery.
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable. The fix is very simple:
1. Install Xposed Installer and ES File Explorer.
2. Open Xposed Installer, go to Framework menu, select "Recovery (write zip to SD card, flash manually)" Installation mode, press "Install/Update".
3. Open ES File, navigate to /sdcard/Andriod/data/de.robv.android.xposed.installer/files. There are two files there: Xposed-Installer-Recovery.zip and Xposed-Disabler-Recovery.zip
4. Now comes the fun part: in both archives you need to modify META-INF/com/google/android/update-binary: comment or delete all "chmod", "chown" and "restorecon" commands and replace "cp XXX/app_process[.orig] XXX/app_process" with "cat XXX/app_process[.orig] > XXX/app_process". This will keep both permissions and security context of the file. Unpack, edit, repack.
5. Reboot into recovery, install Xposed-Installer-Recovery.zip, enjoy.
I will send patch to Xposed maintainer later this week. But we have not seen new releases of Xposed fo KK for over a year now, so I am not sure it will get released any time soon.
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Alte.78 said:
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Click to expand...
Click to collapse
If you want you can PM me or join Freenode IRC and PM droidlambda. I've already started making CyanogenMod for the device, although I haven't come that far yet (even though the TWRP recovery you installed was ported by me). I could give you some advice (of my experiences with this phone and porting) and my basic config (which builds recovery successfully) if you want.
Does it have to go through all that trouble for Xposed? Or only if you want to install it via recovery (not classic / APK)?
Because recovery will trigger Knox (bye warranty).
Anyone installed Xposed the classic way on i9195i?
Alte.78 said:
Getting Root
For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu.
Click to expand...
Click to collapse
If we install TWRP, can't we just flash SuperSU zip from recovery to avoid the KingRoot removal hassle?
Alte.78 said:
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable.
Click to expand...
Click to collapse
Was this boot loop after classical (write to /system), or recovery install?
I installed Xposed classical on i9195 (not i) KK (it also has selinux enforcing) without problems. Is there a difference that I'm not aware of?
Thanks.
Alte.78 said:
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Flashing Custom Recovery
I downloaded official TWRP recovery from teamw.in and decided to go the hard way and install the recovery doing dd fom command line (ConnectBot) - I was hoping this will help me to keep the warranty. Worked just fine, but tripped Knox bit nevertheless. NB: avoid extra hassles and just use Odin to install recovery.
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable. The fix is very simple:
1. Install Xposed Installer and ES File Explorer.
2. Open Xposed Installer, go to Framework menu, select "Recovery (write zip to SD card, flash manually)" Installation mode, press "Install/Update".
3. Open ES File, navigate to /sdcard/Andriod/data/de.robv.android.xposed.installer/files. There are two files there: Xposed-Installer-Recovery.zip and Xposed-Disabler-Recovery.zip
4. Now comes the fun part: in both archives you need to modify META-INF/com/google/android/update-binary: comment or delete all "chmod", "chown" and "restorecon" commands and replace "cp XXX/app_process[.orig] XXX/app_process" with "cat XXX/app_process[.orig] > XXX/app_process". This will keep both permissions and security context of the file. Unpack, edit, repack.
5. Reboot into recovery, install Xposed-Installer-Recovery.zip, enjoy.
I will send patch to Xposed maintainer later this week. But we have not seen new releases of Xposed fo KK for over a year now, so I am not sure it will get released any time soon.
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Click to expand...
Click to collapse
Thanks for the Xposed trick!
I managed to root according to your instructions (King root the supersu me), then install xposed through flashfire.
No need to flash custom recovery!
So knox is still 0x0!!
Great!
nick_white said:
Does it have to go through all that trouble for Xposed? Or only if you want to install it via recovery (not classic / APK)?
Because recovery will trigger Knox (bye warranty).
Anyone installed Xposed the classic way on i9195i?
Click to expand...
Click to collapse
Yes you have. Normal install (Write to /system) will send your phone into bootloop and you will have to re-flash your rom. I've tried that.
Karboush said:
Thanks for the Xposed trick!
I managed to root according to your instructions (King root the supersu me), then install xposed through flashfire.
No need to flash custom recovery!
So knox is still 0x0!!
Click to expand...
Click to collapse
Thats absolutely cool! I want to have custom recovery anyway, but your discovery will surely help a lot of people. :good:
nick_white said:
Was this boot loop after classical (write to /system), or recovery install?
I installed Xposed classical on i9195 (not i) KK (it also has selinux enforcing) without problems. Is there a difference that I'm not aware of?.
Click to expand...
Click to collapse
For me it failed both ways wiping out security context of app_process. Maybe your better luck has something to do with a different rom or Xposed version you are using?
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Could you point me as to where did you find the firmware for the phone. I'm tempted to try rooting it. Is xposed necessary for the root to take full effect or no ? Cause it sounds a bit tricky and risky.
CostasV23 said:
Could you point me as to where did you find the firmware for the phone.
Click to expand...
Click to collapse
Try this link: http://www.sammobile.com/firmwares/database/GT-I9195I/
soo
Alte.78 said:
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Click to expand...
Click to collapse
So my phone has the AOD1 firmware can i root it like AOD2? Im in greece
Alte.78 said:
For me it failed both ways wiping out security context of app_process. Maybe your better luck has something to do with a different rom or Xposed version you are using?
Click to expand...
Click to collapse
Can you tell me if these will work for sure I have the aob1 firmware
Ok, so I have mine updated to I9195IXXU1AOG1. How do I get SuperSU on it without changing Knox to 0x1?
Which version of Xposed is everyone using? On the S4 Mini Plus?
xposed?
Is xposed necessary for the rooting process? or can i just skip it to avoid all the fuzz?
Alte.78 said:
Yes you have. Normal install (Write to /system) will send your phone into bootloop and you will have to re-flash your rom. I've tried that.
Click to expand...
Click to collapse
I upgraded my firmware to:
PDA: I9195IXXU1APA1
CSC: I9195IPHN1APA1
which is also (one of) the latest version, and has the Stagefright vulnerabilities fixed.
Then rooted with latest KingRoot (4.80) + Super Sume Pro.
Then installed Xposed 2.6.1 (stable) and installed "classical" (write to /system). It worked, no bootloops. Maybe you tried a different Xposed version?
Hi! anyone have a baseband I9195LUBUCNJ2?
Synomenon said:
Which version of Xposed is everyone using? On the S4 Mini Plus?
Click to expand...
Click to collapse
Im using the app_process 58 and
xposedBridge.jar 54 which i think is the latest stable edition as of 13/07/2016
Xposed installer version 2.61 with auto flash in recovery method no problems 5 months that i have it
Full debloat stock ROM on Samsung S4 mini Plus (GT-i9195i)
For more than a year, after I upgraded my firmware to:
PDA: I9195IXXU1APF1
CSC: I9195IYUX1APG1
which was the latest version from https://www.sammobile.com/firmwares/database/GT-I9195I/
I am using a debloat version of Galaxy S4 mini Plus (serranoveltexx). Inspired by @btnetro I made a script and tested a full debloat stock ROM on Samsung S4 mini Plus (GT-i9195i). All this time my device has worked very well and even now I am very pleased with him. For those who want to keep stock OS like me, I decided to share with you this flashable zip.
First flash via Odin, a custom recovery on your device( installation instructions here: https://forum.xda-developers.com/galaxy-s4-mini/development/recovery-cwm-twrp-philz-t3182207 ), restart your device and copy attached files in the root of your ext. SD card. Reboot your device in recovery mode and flash “Full_debloat_i9195i.zip”. For those who want to keep weather widget flash this file “weather2014_A3.zip” too (first debloat). Wipe /cache and reboot your device.
OK, i've a weird issue.
I tried all the available recoveries (Philz touch 6.59.0, twrp 2.8.4.0 & 2.8.7.1 etc, and all flashed with odin method) but none of them recognize my external SD.
I tried other sd cards as well, known to be good as they're used in other phones, but end up with th same.
Funny part is that inside os (stock KK 4.4.4) i can see all the files in SD card...
Any suggestion?
I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
How I Did it...
From a site with this in the title:
can_i_manually_flash_601_also_does_ota_work_with
Systemless root doesn't break ota, non-stock recovery breaks OTA.
Unlock bootloader, flash 6.0.1, flash TWRP, flash systemless root...
I did this:
Went back to stock recovery, by flashing via ADB, rebooted downloaded and attempted to install OTA on phone. Process started, rebooted, proceeded and then failed with error . Rebooted, got Factory image.
Extracted and ran flash-all.bat ONLY AFTER Removing the -w from this line:
fastboot -w update image-bullhead-mmb29k.zip
Got latest SuperSU v2.61 zip with auto boot patcher:
See androiding.how/android-6-0-1-root
Copied this to Memory on phone.
Flashed/Installed TWRP Recovery using ADB.
Booted into TWRP Recovery and installed SuperSU.
So now I'm running systemless rooted 6.01 on a Nexus 5X with mmb29k and every thing is working.
I think even though I rooted systemless 6.0, the modified Boot Image was still not letting OTA work.
We shall have to wait and see on the next OTA. Maybe just going back to stock recovery will be all that's needed.
There are some ADB commands that allow you to temporarily select a recovery image, but I'm not sure how that works.
Good Luck!
teapea said:
I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
Click to expand...
Click to collapse
Hello,
at the moment I have a HTC 10 with normal root and xposed.
But I would like to have the option of installing OTA updates and I have some question:
- Is there any advantage between system and systemless root except OTA/Android Pay? Or is it still better to use system root?
- Can I still flash a custom kernel and other mods in TWRP?
- What do I need for systemless root and systemless xposed?
- Are there any disadvantages?
And it would be awesome if someone could give me a full guide how to do this.
I would start with flashing a RUU, but what should I do after that?
Thanks in advance!
I can't say anything about systemless Xposed, but I've been wondering about it. Main thing I want to know is if it will play nice with Android Pay. Right now, I'd rather have Android Pay than Xposed, but I'd like both.
As for systemless root, yes, you can still flash custom kernels thru TWRP. I'm running @flar2's Elemental X and have run them both successfully on LeeDroid and Venom. Some mods may have to have some special prep if they're not baked into a rom, such as AdAway, to work properly with systemless root.
The disadvantages to systemless root, to this point have been you can't run Xposed on it (not sure how it works now), and root is broken on some poorly coded apps, like ES File Explorer.
The easiest way to install systemless root now is just to install a rom. Put TWRP on and pick a rom. Both LeeDroid and Viper have options for systemless root. You're up and working out of the box with nothing special to do.
Superguy said:
I can't say anything about systemless Xposed, but I've been wondering about it. Main thing I want to know is if it will play nice with Android Pay. Right now, I'd rather have Android Pay than Xposed, but I'd like both.
As for systemless root, yes, you can still flash custom kernels thru TWRP. I'm running @flar2's Elemental X and have run them both successfully on LeeDroid and Venom. Some mods may have to have some special prep if they're not baked into a rom, such as AdAway, to work properly with systemless root.
The disadvantages to systemless root, to this point have been you can't run Xposed on it (not sure how it works now), and root is broken on some poorly coded apps, like ES File Explorer.
The easiest way to install systemless root now is just to install a rom. Put TWRP on and pick a rom. Both LeeDroid and Viper have options for systemless root. You're up and working out of the box with nothing special to do.
Click to expand...
Click to collapse
Have a look at this: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
That's the reason why I'm asking - OTA is working, but Android Pay not (for me it doesn't matter. I never used android pay).
But I want to stay on Stock ROM, no Custom ROMs. I just want the ability to download and install OTA updates.
Edit: Well, I see that I still need stock recovery for OTA updates. It doesn't make sense to install systemless root, because I have stock system-image backup and stock recovery.
Is there any advantage between system and systemless root except OTA/Android Pay? Or is it still better to use system root?
Maik268 said:
Have a look at this: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
That's the reason why I'm asking - OTA is working, but Android Pay not (for me it doesn't matter. I never used android pay).
But I want to stay on Stock ROM, no Custom ROMs. I just want the ability to download and install OTA updates.
Edit: Well, I see that I still need stock recovery for OTA updates. It doesn't make sense to install systemless root, because I have stock system-image backup and stock recovery.
Is there any advantage between system and systemless root except OTA/Android Pay? Or is it still better to use system root?
Click to expand...
Click to collapse
I am in the same position, just got the phone and want to install systemless root, systemless xposed and systemless Adaway... Mainly the reason I want this is because I dont want to s-off (you cant flash newer firmwares that come with updates) or I dont want to restore system and performing update after that... I just want stock rom with elementalx and those xposed goodies I want it so that when I get a notification about update, I dont need to backup anything, flash anything, just install update regularly like all normal people BUT still after update have root and xposed
I think its possible, but I have to do a little research before I get on with it.. Now first step is unlock bootloader
CrazyCypher said:
I am in the same position, just got the phone and want to install systemless root, systemless xposed and systemless Adaway... Mainly the reason I want this is because I dont want to s-off (you cant flash newer firmwares that come with updates) or I dont want to restore system and performing update after that... I just want stock rom with elementalx and those xposed goodies I want it so that when I get a notification about update, I dont need to backup anything, flash anything, just install update regularly like all normal people BUT still after update have root and xposed
I think its possible, but I have to do a little research before I get on with it.. Now first step is unlock bootloader
Click to expand...
Click to collapse
Even with systemless root you have to restore stock recovery to use OTA updates
Well, I have a look at this next weekend when I have some more time.
Or I just try a custom ROM... :laugh:
Maik268 said:
Even with systemless root you have to restore stock recovery to use OTA updates
Well, I have a look at this next weekend when I have some more time.
Or I just try a custom ROM... :laugh:
Click to expand...
Click to collapse
Yes but the amazing thing is that after you flash everything you want, you can immediately restore stock recovery and have stock recovery all the time after you have everything systemless
Then if you want to flash something you flash TWRP.. otherwise you just leave re-flashed stock recovery
CrazyCypher said:
Yes but the amazing thing is that after you flash everything you want, you can immediately restore stock recovery and have stock recovery all the time after you have everything systemless
Then if you want to flash something you flash TWRP.. otherwise you just leave re-flashed stock recovery
Click to expand...
Click to collapse
Hello, I will receive my HTC 10 on Friday, and I all I want is to root and install Xposed Framework (A kernel would be nice too, but it's not a must) but I do want to receive OTA's and not having to flash the Rom each time that I want to update...
So if I root my phone Systemless, will I be able to Install Xposed (and a kernel) so when I receive an OTA, I just flash the stock kernel and install the update, then flash twrp again, without losing root or my data?
If so, how do I systemless root?
Thanks! :good:
Was rooted in past on Lollipop. Tried to upgrade to Marshmallow using the 3.38.502.12 file in this thread:
http://forum.xda-developers.com/att...ficial-att-3-38-502-12-rom-7-01-2016-t3409354
Somehow got completely bricked, but I found the full RUU exe file for AT&T using Google which rebuilt everything, with full (ugh) bloat. Anyway I'm now back up & running with Marshmallow 6.0 and latest TWRP 3.0.2-0 is successfully flashed. The weird thing is that it does NOT give me the option to root & install SuperSu. I did make sure the "mount system read only" option was unchecked. I also tried installing SuperSU from the app store, but it reports required binary is missing. Is there any way to force TWRP to do it's root thing? It apparently thinks the phone is already done when it's not.
Hope all this mumbo jumbo makes sense. Thanks!
~Vol
Vol4Ever said:
Was rooted in past on Lollipop. Tried to upgrade to Marshmallow using the 3.38.502.12 file in this thread:
http://forum.xda-developers.com/att...ficial-att-3-38-502-12-rom-7-01-2016-t3409354
Somehow got completely bricked, but I found the full RUU exe file for AT&T using Google which rebuilt everything, with full (ugh) bloat. Anyway I'm now back up & running with Marshmallow 6.0 and latest TWRP 3.0.2-0 is successfully flashed. The weird thing is that it does NOT give me the option to root & install SuperSu. I did make sure the "mount system read only" option was unchecked. I also tried installing SuperSU from the app store, but it reports required binary is missing. Is there any way to force TWRP to do it's root thing? It apparently thinks the phone is already done when it's not.
Hope all this mumbo jumbo makes sense. Thanks!
~Vol
Click to expand...
Click to collapse
You're doing better then me. From what I've read it looks like you need the supersu.zip, but I think you know that. If you haven't try to install the supersu.zip maybe you'll be able to do it without bootloop (I need to make my post). A new version came out 9.15.2016.
Just flash SuperSu 2.64 or 2.65 using TWRP and that's it. Look for the link using google. Ohter versions cause bootloop.