Related
Get your lollipop here. Below is the full OTA from 4.4.4/KTU84P/N910AUCU1ANIE to 5.0.1/LRX22C/N910AUCU1COC4.
I have also include an flashable update.zip with the ota. Please read info below.
OTA/cfg only:
https://mega.co.nz/#!mZB3QBZR!tsWqPGQynF_AgWxsO8xZJy5u4pqfb8HKv5jV_SonVI8
For now this zip is useless until have root. It's here to be available when we are able to use it.
Update.zip: Custom recovery only: {{{{WARNING UNTESTED}}}} Although it's most likely perfect it's untested. See update.zip info below.
https://mega.co.nz/#!jQwxkaIb!UBrf26IRhdSgGnk935qE4GejP-wZG7HR4uZOIb5V3cA
OC4 odin Tar newest:
COMING SOON Waiting for Kies to update version
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Update.zip INFO
In the past pre-rooting the zips was causing WiFi in to fork,so the zip is not rooted.
The update.zip and the actual cfg are almost identical with a few exceptions. They update identically using the same method.
Both use a series of update patches to inject new code in existing apk's some do get fully replaced but very few. So for this reason rooting using them needs to be done in a specific manner. You can thank Samsung/KNOX and SELinux for that.
How to upgrade with update.zip and keep root
It's best to be 100%stock before updating.
Remove SU app from system,do not remove the>>>>>>binary<<<<<<
Boot recovery,flash update zip,reboot
Install SU zip after rom fully boots and profit.
You...are...awesome!!!
Update.zip added.
what is this? I thought we only have a temp root
darkbots said:
Update.zip added.
Click to expand...
Click to collapse
Hi bro! I changed the name of .cfg and on recovery stock says failed to verify signature...
Deleted
darkbots said:
Get your lollipop here. Below is the full ota from 4.4.4/KTU84P/N910AUCU1ANIE to 5.0.1/LRX22C/N910AUCU1COC4.
I have also include an flashable update.zip with the ota. Please read info below.
OTA/cfg only:
https://mega.co.nz/#!mZB3QBZR!tsWqPGQynF_AgWxsO8xZJy5u4pqfb8HKv5jV_SonVI8
Update.zip: Custom recovery only: {{{{WARNING UNTESTED}}}} Although it's most likely perfect it's untested. See update.zip info below.
https://mega.co.nz/#!jQwxkaIb!UBrf26IRhdSgGnk935qE4GejP-wZG7HR4uZOIb5V3cA
OC4 odin Tar newest:
COMING SOON Waiting for Kies to update version
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Update.zip INFO
In the past pre-rooting the zips was causing WiFi in to fork,so the zip is not rooted.
The update.zip and the actual cfg are almost identical with a few exceptions. They update identically using the same method.
Both use a series of update patches to inject new code in existing apk's some do get fully replaced but very few. So for this reason rooting using them needs to be done in a specific manner. You can thank Samsung/KNOX and SELinux for that.
How to upgrade with update.zip and keep root
It's best to be 100%stock before updating.
Remove SU app from system,do not remove the>>>>>>binary<<<<<<
Boot recovery,flash update zip,reboot
Install SU zip after rom fully boots and profit.
Click to expand...
Click to collapse
Now obviously anyone on these forums knows the deal here, if it's flashable it's risky, but this raises some flags that need addressed.
This is for the AT&T yes? If I'm not mistaken, this device has a locked bootloader, so then it goes without saying that your custom recovery flash only is untested. So is the expectation that users here are supposed to test it?
This is only the stock update put in a zip, then I cleaned some of the updater. This way if your on stock kitkat with custom recovery you can take the ota. There's zero risk here other than what Samsung messed up. I assumed it would be obvious we can use them yet because of not having root. I've done this a lot for several devices it's crazy easy to do,and you only need to change its zip and clean the updater.
rondoo said:
Hi bro! I changed the name of .cfg and on recovery stock says failed to verify signature...
Click to expand...
Click to collapse
You can't change the name extention or open the cfg .Put it on a sd, use stock recovery sd install option.
darkbots said:
You can't change the name extention or open the cfg .Put it on a sd, use stock recovery sd install option.
Click to expand...
Click to collapse
Did it and...
failed to verify whole-file signature
signature verification failed
download again you have a corrupted file
having same problem here.
failed to verify whole-file signature
signature verification failed.
I just bought note 4. This is AT&T model firmware version N910AUCU1BNK3. This is unlocked phone. I am using this phone in Pakistan. Currently it is with Kitkat. Once I am trying to update to lollipop through OTA it shows its is lastest firmware but I know Lollipop already released. Please help me how to update my phone ? I want my phone keep unlock as I am using in Pakistan.
waqas.ahmad said:
I just bought note 4. This is AT&T model firmware version N910AUCU1BNK3. This is unlocked phone. I am using this phone in Pakistan. Currently it is with Kitkat. Once I am trying to update to lollipop through OTA it shows its is lastest firmware but I know Lollipop already released. Please help me how to update my phone ? I want my phone keep unlock as I am using in Pakistan.
Click to expand...
Click to collapse
you can not update at&t version outside of US. I struggled a lot and finally gave up and installed lollipop (5.0.1) manually using files shared by the guys from here.
annttiigs said:
you can not update at&t version outside of US. I struggled a lot and finally gave up and installed lollipop (5.0.1) manually using files shared by the guys from here.
Click to expand...
Click to collapse
If I update manually, will my phone SIM Locked? Currently it is unlocked.
What about Knox? will is break?
Can you share me the firmware link which I exactly download and install in my phone?
waqas.ahmad said:
If I update manually, will my phone SIM Locked? Currently it is unlocked.
What about Knox? will is break?
Can you share me the firmware link which I exactly download and install in my phone?
Click to expand...
Click to collapse
I have used this one and and no issue:
http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
but all is on your own risk.
annttiigs said:
I have used this one and and no issue:
http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
but all is on your own risk.
Click to expand...
Click to collapse
I have downloaded the firmware from the link you sent me.
You tried to install it on unlocked phone ? Firmware Version N910AUCU1BNK3?
Do I need to load all files or just AP is ok ?
waqas.ahmad said:
I have downloaded the firmware from the link you sent me.
You tried to install it on unlocked phone ? Firmware Version N910AUCU1BNK3?
Do I need to load all files or just AP is ok ?
Click to expand...
Click to collapse
Plase follow the discussion there. Those all were my questions as well. You need to put each file in its location in Odin means you will use all files. My phone was unlocked and I dont remember my fw version. Please read the discussion there.
hi this link for CFG is dead , can you reup link ?>
+1 Please re-upload
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've looked around and can't find my exact issue, so I'm hoping I can get some help if I make a new post!
I unlocked my bootloader through HTC, rooted my device, and then was trying to install Cyanogenmod 13 on it. I have TWRP 3.0.0-0 since the latest one didn't work. It kept giving me errors, and too late, I figured out it was because I still had Android 5.1 on it. I found this out however after I deleted everything except TWRP from the phone. Now that's the only folder that shows up if I plug it into my computer. I do have an SD card, and the files on there seem to be safe. I'm also using a Mac. I presume I need to reflash the stock OS on it, am I correct? If so, how?? I found the RUU file on HTC's website, but I'm not sure how to manually flash it onto the phone, and the files are all .exe, which of course don't run on Mac. I do have the free trial of Crossover, is that compatible?
EDIT: I'm on the AT&T US version if that matters.
I hope this all makes sense haha. Thanks for any help!
You can download cm13 and put it on your SD-Card and flash it from there in TWRP. Or you can use adb and Sideload to flash it. I dont see a reason why you have to go back to Stock before
The latest version of Twrp can flash Zip of Rom bigger as 2 Go but need a new script for the flash , so you have to use older version as 3.0.0. or below to flash rom' s zip with older script.
As Adromir write , no need to be back stock...
He any way needs Android 6 Firmware for CM13 to run properly. As he's on 5.1.1 Firmware, and - just guessing - S-ON, he hast to flash an RUU to Upgrade to Android 6 first.
Send by the swarm intelligence of my coffee machine ?.
Are there detailed instructions somewhere on how to manually flash the RUU file? Can I do it on a Mac with or without Crossover? I could use my spouse's PC, but I'd prefer not to. (I'm still a n00b at all this, haha.)
And yes, S-ON appears in the bootloader.
When I was trying to install CM13, I kept getting a "No MD5 file found", and I found an MD5 hash on the CM wiki, but I have no idea what to do with it.
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.
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.