Related
Ive noticed many people with older TWRP versions having problems with the updater script when installing 4.4 roms you need to be on the latest version of twrp (CWM may also need to be on a recent version). This tutorial will cover TWRP. Goo manager will not work for installing the latest TWRP recovery version on grouper. The following will give you the basics on how to use fastboot to flash a recovery.img (In this case twrp)
Things you will need:
A PC
Android SDK http://developer.android.com/sdk/index.html
TWRP recovery.img for grouper http://techerrata.com/browse/twrp2/grouper
A basic understanding of terminal/command prompt
You will need a PC and the android SDK (SDK http://developer.android.com/sdk/index.html) for fastboot to push the recovery file. TWRP can be found here (http://techerrata.com/browse/twrp2/grouper) you need the 2.6.3.0 version. Extract your android sdk and move your twrp image file (openrecovery-twrp-2.6.3.0-grouper.img) to the platform-tools folder in the sdk (This is where fastboot/adb are). For simplicity's sake rename your twrp file to recovery.img Enter command prompt or terminal depending on what OS you are using (windows/linux) and navigate to to your platform-tools folder in the SDK folder (where you should have moved your recovery.img) using the cd command. (plug device in) Once there check to see if you device is connected and seen with the adb devices command hopefully you will see a wonky alpha numeric code with "device" after it. If you dont you need to enter developer setting to enable adb. You do that by going into settings/about tablet and tapping build number 7 times. That should give you a developer options in settings check to make sure USB debugging is enabled. If all is well reboot your device into the boot loader with the adb reboot bootloader command once your device is at the bootloader check fastboot with fastboot devices you should see another wonky output with "fastboot" after it. The final command to push your new twrp image will be fastboot flash recovery recovery.img You should see some output saying how long it took to push the file it should not take that long. That should cover it! Now you should be good to go with the 4.4 rom's floating around.
There are many tutorials online explaining this process I just thought customizing it to the grouper would help those less comfortable with adb/fastboot. It's always a good idea to know how to use these tools you never know when you might need to use them. Anyone with question's feel free to ask.
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That will work. But knowing your way around adb/fastboot can't hurt. There won't always be a GUI to do everything for you.
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't know of flashify, awesome. Thx, really fast and easy method. Best thing is I didn't even need my pc for it
Thanks for the tutorial but surely this belongs in q&a, help etc not android development ;p
Sent from my Nexus 4 using XDA Premium 4 mobile app
Actually it's suited to the General section (guides and all). I appreciate you advising the fastboot method (I use it too), but it can b a pain for people who don't have their devices configured (configuring it can be a pain sometimes too). Flashify, as one member said, is a great alternative. BUT you *may* brick your device if you flash something to the wrong block device (possibility of that happening to an expert user: 0.0001%; possibility of that happening to a new user: 1%). Just my two cents.
I agree guys this should be in general. I've never posted anything but a build and didn't even think about it. Do I need to get a mod to move it? As for flashify sounds like a great tool. I've never had the pleasure of using it but if it works and people are comfortable with it more power to it. Personally fastboot is what I'm comfortable with it might seem a little in depth but really its quite simple especially if you use adb for logcats and are setup.
OP No worries, moved and thank you.
To flash 4.4 ROMs one could follow this tutorial, or one could simply flash this .zip of the latest version of CWM:
http://forum.xda-developers.com/showpost.php?p=46053223
So, i've bricked it already.
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
ziffius said:
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
Click to expand...
Click to collapse
I'm sure this is not what you want to hear but if all else fails push the factory.IMG you will be starting from square one. You can try pulling your backups off but might as well start over for 4.4
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much for this recommendation. Really nice. Simple and took out all the nervousness of using the computer to push these files etc.
REally truly best for flashaholics.
question
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??
Ergina95 said:
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??
Click to expand...
Click to collapse
Did you ever try just flashing it and if so, did it work?
for some reason i cannot download the twrp ..it stuck at 99%
tried 2 version of twrp..hurm
Mookie2014 said:
Did you ever try just flashing it and if so, did it work?
Click to expand...
Click to collapse
yeap! did it! worked perfectly :good: just flash zip updates through the recovery
Hello guys,
I recieved the 5.0 OTA update for Moto G 2nd Gen(India) but update failing on rooted phone with TeamWin recovery. Any suggestion?
Thanks
Flash stock recovery...
Unroot your phone....
Flash stock Kitket ...
Then lock your boot loader... And try to update
Sent from my XT1068/69 using XDA Premium 4 mobile app
amritmalviya said:
Flash stock recovery...
Unroot your phone....
Flash stock Kitket ...
Then lock your boot loader... And try to update
Sent from my XT1068/69 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think locking the bootloader is not necessary.Stock recovery is the most important part.
Thanks bro, that's what I thought was the problem(recovery mostly). Will back up my data and give it try.
Sent from my XT1068 using XDA Free mobile app
Hey guys, I have a very similar problem.
I have a Moto G2, I unlocked the boot loader, installed TWRP and rooted it.
Today I received the Lollipop update OTA. The update seems to have downloaded fine, but at the moment of installation, the phone enters TWRP and does nothing. If I boot the phone, it boots normally but after a few seconds, the phone restarts itself.
Did this 4 or 5 times and finally came up with the message the update failed.
Do I also need to flash stock? Any other way this may be done?
Right now the update is downloading again but I'm not updating just yet.
vargas7 said:
Hey guys, I have a very similar problem.
I have a Moto G2, I unlocked the boot loader, installed TWRP and rooted it.
Today I received the Lollipop update OTA. The update seems to have downloaded fine, but at the moment of installation, the phone enters TWRP and does nothing. If I boot the phone, it boots normally but after a few seconds, the phone restarts itself.
Did this 4 or 5 times and finally came up with the message the update failed.
Do I also need to flash stock? Any other way this may be done?
Right now the update is downloading again but I'm not updating just yet.
Click to expand...
Click to collapse
Try flashing the stock recovery.For the constant rebooting issue, try wiping your cache and dalvik cache.
mobile_maniac said:
Try flashing the stock recovery.For the constant rebooting issue, try wiping your cache and dalvik cache.
Click to expand...
Click to collapse
Is there a tutorial to do this? Can it be done without re-loading the whole rom?
Just for the recovery: Choose a link for your firmware here on XDA (for example: http://forum.xda-developers.com/moto-g-2014/development/windows-tool-moto-g-2014-xt1068-dual-t2983295 ) ,extract the recovery.img out of it and flash it. Also use the fullunroot-function of superSU. It´s important to remove any changes made to stockfirmware like removing sytemapps or xposed things.
If that doesn´t work you´ll have to flash whole stock firmware like in this thread: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
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 accidentally confirmed installation of SuperSU while trying to exit TWRP (I wish TWRP had an option to disable it) ;[
How do I uninstall it? As I'm unable to boot into my phone anymore((
a1exus said:
I by accidented confirmed to install SuperSU while trying to exit TWRP (I wish TWRP had an option to disable it) ;[
How do I uninstall it? As I'm unable to boot into my phone anymore((
Click to expand...
Click to collapse
hi a1exus
i've the same problem, uninstall supersu from its settings panel doesnt work at all... after the required reboot supersu is still there and installed as an system app.
im using a htc one m7. i need to remove supersu to install the OTA update.
any ideas on how to remove supersu?
kind regards
red1337
red1337 said:
hi a1exus
i've the same problem, uninstall supersu from its settings panel doesnt work at all... after the required reboot supersu is still there and installed as an system app.
im using a htc one m7. i need to remove supersu to install the OTA update.
any ideas on how to remove supersu?
kind regards
red1337
Click to expand...
Click to collapse
flash system.img
Sent from my Nexus 9 using Tapatalk
Try to install this zip through TWRP.
http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
@a1exus
thanks for your help.
Unfortunately I didn't made any backup befor rooting. But now I made a nandroid backup after updating to the newest version and before rooting
@Srandista
next time I'll definately try that script. I couldn't find that unSU script when I searched the interwebs. Thanks also for your help!
Kind regards
red1337
red1337 said:
@a1exus
thanks for your help.
Unfortunately I didn't made any backup befor rooting. But now I made a nandroid backup after updating to the newest version and before rooting
Click to expand...
Click to collapse
you can always flash stock image..
Sent from my Nexus 6P using Tapatalk
Srandista said:
Try to install this zip through TWRP.
http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
Click to expand...
Click to collapse
I have to thank you, I was stuck on de boot logo, because i had the same problem that he says, and that file solved it.
I have a Moto X Play 6.0
Madvinv said:
I have to thank you, I was stuck on de boot logo, because i had the same problem that he says, and that file solved it.
I have a Moto X Play 6.0
Click to expand...
Click to collapse
Thanks for this. I had CM13 installed on my Redmi 2 and I flashed SUperSU ZIP through TWRP leading to booting error. Through the link shared by you and downloading file provided by @osm0sis I was able to get out of booting issue.
But problem is that now am stuck with no root access. Any idea how to renable it? I have CM13 and in developer options it is on.
Pls guide.
same issue and worst
hi
I was doing standard procedure to root LG4. Everything went ok until I uploaded the UPDATE-SUPERSU-v2.46.zip
Now, LG G4 don't boot anymore...
Until now I was able to boot into TRWP system doing adb commands but now since LG G4 stucks in boot my windows don't recognize the phone.
Am I totally screw?
Do you have any idea?
rubendob said:
hi
I was doing standard procedure to root LG4. Everything went ok until I uploaded the UPDATE-SUPERSU-v2.46.zip
Now, LG G4 don't boot anymore...
Until now I was able to boot into TRWP system doing adb commands but now since LG G4 stucks in boot my windows don't recognize the phone.
Am I totally screw?
Do you have any idea?
Click to expand...
Click to collapse
Does your LG G4 haven't got a key press combination to go to bootloader menu ?
Oooh wait first hit on Google search.
How to Boot into Fastboot Mode on LG G4 with the help of its Hardware Buttons:
First of all, turn off the smartphone.
Then, press and hold the Power and Volume Up keys at the same time for about 6 or 7 seconds.
Plug in the USB cable for your smartphone and connect it to your PC.
Release the keys only when the download mode is being displayed.
Same problem here! Nog able to het Root acces.(su binary not installed), so says Supersu. Probally because cm and Supersu Have a conflict. So how to delete the 'System' Supersu app?
benjg_ said:
Same problem here! Nog able to het Root acces.(su binary not installed), so says Supersu. Probally because cm and Supersu Have a conflict. So how to delete the 'System' Supersu app?
Click to expand...
Click to collapse
You have to use the clean up option in the app or remove the app manually through terminal or adb shell
Sent from my Nexus 5 using XDA-Developers mobile app
i had same problem before, I upload and install super Su in LG G4, turns into soft brick. I was only able to restore all android with kdz file via LGUP.
a1exus said:
flash system.img
Click to expand...
Click to collapse
how ican flash just system.img if ican using Odin3 v3.10
grep_i said:
You have to use the clean up option in the app or remove the app manually through terminal or adb shell
Sent from my Nexus 5 using XDA-Developers mobile app
Click to expand...
Click to collapse
How can I remove the app manually? When I open SuperSU, it won't let me open it because SuperSU says something like "cannot install SuperSU" and quits.
Vegerot said:
How can I remove the app manually? When I open SuperSU, it won't let me open it because SuperSU says something like "cannot install SuperSU" and quits.
Click to expand...
Click to collapse
If you mean the app you can simply remove it by long pressing the icon.
When i install super su from twrp it does not install, but super su icon see on my phone, so that i try to un install but it does not open a pop up menu showing on the screen that is super su is not install and su binary need , so how to remove super su for my mobile
Deleted
Srandista said:
Try to install this zip through TWRP.
http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
Click to expand...
Click to collapse
It worked. Thank you so much.:good:
Use Magisk Uninstaller
just flash the Magisk Uninstaller zip through recovery and done....
http://forum.xda-developers.com/attachment.php?attachmentid=3893658&d=1475527472
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.