Related
Rom Manager was just updated to version 5.0.2.4 and allows you to flash to CWM 6.0.1.6 recovery. Booting to recovery just gives me the Android with a red flag though. Just a FYI till it gets sorted.
Pressing and holding the pwr button will boot you back to the OS. Not a huge deal as we don't have anything to flash at the moment.
If you need to get back to the stock recovery in the meantime which can be found in this thread
http://forum.xda-developers.com/showthread.php?t=1993331
Edit:
Don't Flash this yet, you'll have to re-install the stock recovery or wait for a fix and could possibly brick your phone if you don't know what you're doing.
Is there like an easy way to root other than manually adb pushing? Flashable zip maybe?
I get the same thing as you, says flash successful then the red flag.
F4M0U569 said:
Is there like an easy way to root other than manually adb pushing? Flashable zip maybe?
Click to expand...
Click to collapse
You can use the temporary "boot" method as opposed to "flash" when using the current CWM recovery which is posted here http://forum.xda-developers.com/showthread.php?t=1993331
Don't flash the recovery yet though, it's obviously not sorted. I used the adb method to root which worked fine. I got excited when I saw the new Rom Manager which allowed me to flash recovery because Koush's G+ messages earlier today.
kchino said:
You can use the temporary "boot" method as opposed to "flash" when using the current CWM recovery which is posted here http://forum.xda-developers.com/showthread.php?t=1993331
Don't flash the recovery yet though, it's obviously not sorted. I used the adb method to root which worked fine. I got excited when I saw the new Rom Manager which allowed me to flash recovery because Koush's G+ messages earlier today.
Click to expand...
Click to collapse
I tried using the adb boot method but it doesn't work for me. After booting the insecure boot and taking me to the Android screen, I tried using the codes listed there but it says no device found.
F4M0U569 said:
I tried using the adb boot method but it doesn't work for me. After booting the insecure boot and taking me to the Android screen, I tried using the codes listed there but it says no device found.
Click to expand...
Click to collapse
i did it last night and it was quite late, but if i remember correctly i had the same problem but just had to reselect USB debugging
Sent from my Nexus 7 using xda app-developers app
If coming from the original JellyBean and have not updated your custom recovery since, you will need to install the recovery provided below. This step only needs to be performed once to support the newer updates.
Recovery Update
Boot into bootloader mode, connect the USB cable, and from a terminal window or command prompt type:
Code:
fastboot flash recovery recovery.img
To root an OTA, the procedure is pretty simple.
Code:
Copy the OTA from the cache folder to the sdcard.
Move the OTA zip somewhere it can be opened and unzip it
Go to system/etc/ to find the file named recovery and delete it
(extension may vary, but it is always named recovery)
Open the META-INF/com/google/android/updater-script
Delete all of step 1 and step 3 so that all that is left is the large middle portion without any steps
That's it. You have made the same files you find here.
Download the desired package below and copy it to your sdcard, along with the SuperSU recovery package.
Boot into recovery, select install from sdcard, and choose the update. Go back and repeat the install for SuperSU.
KitKat Update 98
KitKat Update 99
Lollipop Update 110
XDA:DevDB Information
Nvidia Root-Friendly Updates [No Wipe], ROM for the Nvidia Shield
Contributors
twistedumbrella
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-11-08
Last Updated 2018-07-05
twistedumbrella said:
The new update has a few things that require updating the recovery, but since a recovery is not officially developed, updating the kernel of the existing recovery will do the trick. Flash this first.
Recovery Update
The install requires removing the assert checks since there is an error that the device is a Thor but looking for a Roth (same thing, right?). Install this from the new recovery.
KitKat Update
Immediately after installing the update, install the SuperSU recovery package to restore root and you're all set.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?
NapalmDawn said:
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?
Click to expand...
Click to collapse
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands
twistedumbrella said:
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands
Click to expand...
Click to collapse
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?
NapalmDawn said:
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?
Click to expand...
Click to collapse
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
KitKat Update Without Complete Re-root
hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.
twistedumbrella said:
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.
Click to expand...
Click to collapse
Ahh I gotcha. Well that's good to know. I haven't had a chance to really look at many of the files yet. Do you know if nvidia released the factory recovery packages yet?
EDIT:
Nevermind looks like 72 is out now.
Yeah, they are pretty good about that. It may be nearing the last update for this version, though
hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?
NapalmDawn said:
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?
Click to expand...
Click to collapse
Exactly
twistedumbrella said:
Exactly
Click to expand...
Click to collapse
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?
NapalmDawn said:
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?
Click to expand...
Click to collapse
The OTA will restore the stock recovery. This way updates it to one compatible with KitKat.
KitKat Update Without Complete Re-root
OTA 98 has been added. No recovery update is needed coming from 72. Flash the build and SuperSU and off you go. No data wipe necessary, either.
Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.
Neoistheone2000 said:
Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.
Click to expand...
Click to collapse
Updated
twistedumbrella said:
Updated
Click to expand...
Click to collapse
Thanks, that worked a treat
Yeah, to clarify, in recovery, you must press and hold Shield and Home buttons for a second, then release to bring up the menu. Then use X and Y to navigate, A to select. Don't understand why the bootloader or recovery don't use the D-pad at all. They're weird. Anyway, downloading this now, and will report back in a few minutes. This is just sideloaded via the stock recovery, right? I hope so, that's how I'm doing it right now.
EDIT: Nope. Failed again.
E:footer is wrong
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I think I'll try that new recovery (funny, because I had flashed the one included in the original update archive, still had issues). I shouldn't have to use that one, I was on update 92 already.
EDIT 2: Oh, I'm dumb. Here I thought this was still being done with the STOCK recovery. Didn't realize this would flash in CWM. Awesome. Flashed SuperSU 2.16 while I was at it. Rebooted, and it's at .98, with root access. You ROCK, @twistedumbrella!
Did you do this with update 99 yet? Just came out today.
GuyInDogSuit said:
Did you do this with update 99 yet? Just came out today.
Click to expand...
Click to collapse
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.
twistedumbrella said:
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.
Click to expand...
Click to collapse
Hmmm. It started downloading as soon as I turned mine on. I'm just gonna do the usual process.
Here is what I had to do to get ROOT on Lollipop.
-
Upgrade to Lollipop ( I did it the ODIN method but shouldn't matter if you do OTA)
- ODIN Flash CF-AutoRoot from the first thread. http://forum.xda-developers.com/show...34&postcount=1
- Let Device Reboot
- Go to Download Mode Again
- ODIN flash the latest TWRP. http://twrp.me/devices/samsunggalaxytabs105.html
- Let device reboot.
- Download latest SuperSU here and store it in your device. http://download.chainfire.eu/696/Sup...erSU-v2.46.zip
- Go into Recover by Power+Home+Volume Up.
- Instal the SuperSU zip you downloaded.
You should be good.
Took me a while to get this figured out so just sharing what i found.
If this helped please hit the thanks button.
dadanepal said:
Here is what I had to do to get ROOT on Lollipop.
-
Upgrade to Lollipop ( I did it the ODIN method but shouldn't matter if you do OTA)
- ODIN Flash CF-AutoRoot from the first thread. http://forum.xda-developers.com/show...34&postcount=1
- Let Device Reboot
- Go to Download Mode Again
- ODIN flash the latest TWRP. http://twrp.me/devices/samsunggalaxytabs105.html
- Let device reboot.
- Download latest SuperSU here and store it in your device. http://download.chainfire.eu/696/Sup...erSU-v2.46.zip
- Go into Recover by Power+Home+Volume Up.
- Instal the SuperSU zip you downloaded.
You should be good.
Took me a while to get this figured out so just sharing what i found.
If this helped please hit the thanks button.
Click to expand...
Click to collapse
I can confirm that this process does work. It's the method I went through when I upgraded my Tab S.
Tbh that is a long winded way to achieve something much easier. The Cf-autoroot step was totally unnecessary. It only does what the supersu zip does or twrp does itself.
Just flash TWRP from the first post. It will root your device with the latest binary.
http://forum.xda-developers.com/galaxy-tab-s/development/test-twrp-2-8-60-recovery-mod-t3066372
ashyx said:
Tbh that is a long winded way to achieve something much easier. The Cf-autoroot step was totally unnecessary. It only does what the supersu zip does or twrp does itself.
Just flash TWRP from the first post. It will root your device with the latest binary.
http://forum.xda-developers.com/galaxy-tab-s/development/test-twrp-2-8-60-recovery-mod-t3066372
Click to expand...
Click to collapse
Thanks for the update. Are you going to keep up with every new SU updated binaries and update TWRP every time the binaries are update. That would be great if you are willing to do that. I rather rely on the actual TWRP and SuperSU Developers to give me the zips etc. and flash my self as long winded as that may seem but people can choose.
Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue now.
Regarding cf-autoroot. I don't think people realise there is nothing special about how it roots.
It basically does the same thing that twrp does itself or flashing a super su zip.
Cf-autoroot simply installs a modified stock recovery which runs a script to Install root then flashes back stock recovery.
If someone intends to install a custom recovery anyway then there is no point in running cf-autoroot.
Twrp will do exactly the same thing and so does installing a super su zip.
They all accomplish the same thing using a slightly different method.
The only difference will be that chainfire may keep each cf-autroot updated with the latest binary.
The reason chainfire created it is for people who want to stick with stock recovery instead of custom
ashyx said:
Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue n
So i tried the auto root no luck, what mode do i flash twrp in odin?
Click to expand...
Click to collapse
deno24 said:
ashyx said:
Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue n
So i tried the auto root no luck, what mode do i flash twrp in odin?
Click to expand...
Click to collapse
Mode? Just load it and flash it.
Click to expand...
Click to collapse
ashyx said:
deno24 said:
Mode? Just load it and flash it.
Click to expand...
Click to collapse
yeah in AP mode?
im trying to root this
Click to expand...
Click to collapse
deno24 said:
ashyx said:
yeah in AP mode?
im trying to root this
Click to expand...
Click to collapse
That's the one.
Click to expand...
Click to collapse
ashyx said:
deno24 said:
That's the one.
Click to expand...
Click to collapse
cool so i flash twrp and ill have root? been a cpl oif years since ive done this last root was note2
Click to expand...
Click to collapse
Just flash twrp, boot into it then hit reboot. Twrp will give you the option to root.
If doesn't then you are already rooted and probably just need to update the super su app.
ashyx said:
Just flash twrp, boot into it then hit reboot. Twrp will give you the option to root.
If doesn't then you are already rooted and probably just need to update the super su app.
Click to expand...
Click to collapse
I did that and I can't boot into twrp, samsung recovery is shown. Looks like it can't rewrite the original recovery. Used your version from 30th March with Odin 10.6.
Thanks
d3xtr0 said:
I did that and I can't boot into twrp, samsung recovery is shown. Looks like it can't rewrite the original recovery. Used your version from 30th March with Odin 10.6.
Thanks
Click to expand...
Click to collapse
That's a feature of lollipop. It overwrites with stock recovery. Happens on many devices. You need to boot into recovery immediately after flashing twrp, twrp will then patch it so stock recovery can't replace it.
When flashing uncheck auto reboot in odin. When it finishes flashing hold power + vol down + home. As soon as the screen goes blank hold power +vol up + home to boot into recovery.
Thanks for the information, but now I've flashed your new package root+twrp and it's working great
Thanks again.
Sent from my MI 4W
Whith this method, what is the knox value?
Knox is one ( .. )
Newer thread opened yesterday.
Edit:
http://forum.xda-developers.com/showthread.php?t=3079488
[ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805 [Tab S 10.5 ]
Sent from my MI 4W
Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.
twrp works, but SU binary still wont flash :/
edit - the combination of this APK and TWRP gave me all I need for root + rebooting and keeping root
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Steel01 said:
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Click to expand...
Click to collapse
So you were successful in getting TWRP installed, SuperSU installed and removing KingRoot clean - leaving only SuperSU on the system, surviving a reboot?
Ink Rampant Wolf said:
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
Click to expand...
Click to collapse
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
You might wanna include the instructions as shown here,
http://forum.xda-developers.com/xpe...how-to-root-lollipop-xperia-tablet-z-t3115107
It basically tells you how to install SuperSU and remove the entire KingRoot library after that. It worked on my Z and on my SHIELD as well.
This was essentially what I did:
http://greenrobotgamer.com/shieldzone/root-shield-portable-lollipop-5-1/
Mine seems to be working just fine, after obtaining root and installing SuperSU. I didn't bother with installing TWRP, I just hotboot the recovery. I'm rebooting my SHIELD as we speak, see if there's any issue
EDIT: Scractch that, it's not booting. How do I flash the latest image back in?
JCESAR2 said:
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
Click to expand...
Click to collapse
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Ink Rampant Wolf said:
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
JCESAR2 said:
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
Click to expand...
Click to collapse
You need to unlock your bootloader first.
ok long story short: since i had the shield drivers installed and tha adb drivers installed i did the oem unlock and after a confirmation screen on the shield i did it, then i immediately flashed the twrp image from the same command line. now the shield is stuck in nvidia android boot logo. any suggestions? thanks
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
JCESAR2 said:
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
Click to expand...
Click to collapse
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Ink Rampant Wolf said:
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
Guess I'll have to flash the old firmware then, it's been sitting there forever.
341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
JCESAR2 said:
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
Click to expand...
Click to collapse
I just re-flashed the system using RAM, should be fine now. I'll just have wait for the OTA all over again. UGH.
I wish someone could provide a KitKat version tho.
EDIT: Annnd battery's at 15% so the system won't let me OTA yet.
SuperSU will work fine with my latest TWRP builds posted here. The older 2.8.5.0 builds will not work, neither will any build in the linked thread before yesterday. I used SuperSU 2.49 Beta and it worked as expected.
Side Note: The older builds will have the problem where boot will just hang. That seems to be because the older builds didn't have selinux policies built in, so some things never get set up right and the boot panics.
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Rentom said:
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Click to expand...
Click to collapse
flash any custom kernel to get rid of that message
simms22 said:
flash any custom kernel to get rid of that message
Click to expand...
Click to collapse
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Rentom said:
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Click to expand...
Click to collapse
because google put it there, it is new.
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah I let twrp root it when it asked when I did it two months ago. Was that a bad thing? I thought I read that it was if you were rooting 6.0.1, but I was rooting 6.0 so I decided to see what would happen, and it went smoothly.
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I see. Makes sense. Alright, thanks. I already did flash it back to stock to update to 6.0.1, so I'm not sure why you told me to flash it back to stock and then install su 2.67.
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Mongo23ny said:
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Click to expand...
Click to collapse
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
simms22 said:
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
Click to expand...
Click to collapse
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Mongo23ny said:
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Click to expand...
Click to collapse
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Tried flashing twrp a couple of times, went back to stock recovery and then twrp. No luck. Also, phone will not boot with custom recovery only with stock. Not sure if I tried 3.0.0.0
simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Do I keep system read only in twrp 3.0?
Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
no, do not keep system read only, ever.
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
Thanks for all your help, did a clean install, fastboot flashed 6.01. I had gotten that corrupt phone message when I rebooted again but I took some security update and that got rid of the message. I flashed twrp 3.0.0.0 and SuperSU 2.67 and got root back. No worries, thx again.
Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
If you are using the systemless root method then yes, you do want to keep system read only.
alryder said:
If you are using the systemless root method then yes, you do want to keep system read only.
Click to expand...
Click to collapse
I kept it in read only, installed SuperSU 2.67 in twrp.