Related
I have rooted my S4 with the motochopper and it keeps on telling me to update the Superuser from clockworkmod and i updated thru the plays store and it still asks for an update how can i fix this? and if i install the other superuser by chainfire it doesnt have the SU binary installed.... please help
re: SuperSU
MrDiaz said:
I have rooted my S4 with the motochopper and it keeps on telling me to update the Superuser from clockworkmod and i updated thru the plays store and it still asks for an update how can i fix this? and if i install the other superuser by chainfire it doesnt have the SU binary installed.... please help
Click to expand...
Click to collapse
Your problem is almost fixed, here is what you need: http://batakang.com/ftp/SGH-M919/MDB-SetUIDOff.zip
Flash it using CWM or TWRP recovery and reboot the phone and you will see the magic!
After doing this go to the play store and see if there is an update of SuperSU if there is then install it and reboot the computer.
(do not install superuser).
Good luck!
Misterjunky said:
Your problem is almost fixed, here is what you need: http://batakang.com/ftp/SGH-M919/MDB-SetUIDOff.zip
Flash it using CWM or TWRP recovery and reboot the phone and you will see the magic!
After doing this go to the play store and see if there is an update of SuperSU if there is then install it and reboot the computer.
(do not install superuser).
Good luck!
Click to expand...
Click to collapse
It still says it doesnt have the binary installed but it still grants any rooted applications lol.... ill keep messing around with it maybe i did a mistake when i did it on the motochopper
The latest version of superuser does not play well with twrp... Titanium Backup, CPU Sleeper, etc..still have superuser access... After flashing I just chose ignore but if you select 'fix' it will restore the old version of superuser. To update binary, I flashed Phantom kernel v1 from Infamous S4 thread. That fixed me up.
Your are the BEST news you have gave me how to fix the problem on t-mobile binary problem to root the galaxy s4 .IT DID WORK THANK YOU VERY MUCH the other top dogs that they root their phones dont know about this fix in you tube.. thank u again.
Misterjunky said:
Your problem is almost fixed, here is what you need: http://batakang.com/ftp/SGH-M919/MDB-SetUIDOff.zip
Flash it using CWM or TWRP recovery and reboot the phone and you will see the magic!
After doing this go to the play store and see if there is an update of SuperSU if there is then install it and reboot the computer.
(do not install superuser).
Good luck!
Click to expand...
Click to collapse
Sir, I love you. I searched for hours trying to figure this out.
sent from my jelly bean droid (SGH-M919)
Ive searched the similar thread suggestions and my issue seems to be different...
**BACKSTORY** So I have the sgh-I317...I rooted it a while back and had JellyBEANSTALK 4.2.2 running on it for a while...phone started randomly not waking up from being locked every once in a while so I flashed back to my stock JB 4.1.2 image i had made and flashed the counter so i could take it in to ATT...since flashing back to 4.1.2 I have not had that issue so i am assuming it was something with the ROM
**PRESENT TIME** I decided I wanted to re-root and try CleanROM out...so I got all the necessary stuff I needed (correct drivers and CF Auto Root), followed directions to a T, everything passed, phone rebooted, etc. When i try and use root checker, it just 'searches'...I dont get a 'Not rooted' message or anything...tried installing titanium backup pro root; it installs but when i open it it just says its looking for root access and stays on that screen...ALSO, i do not have SuperSU in my applications but if I go into the Application Manager, SuperSU is there...I also have cwm recovery as well...so its like it partially rooted? Im at a loss right now...anyone have any ideas? Thanks!:good:
jwalck5950 said:
Ive searched the similar thread suggestions and my issue seems to be different...
**BACKSTORY** So I have the sgh-I317...I rooted it a while back and had JellyBEANSTALK 4.2.2 running on it for a while...phone started randomly not waking up from being locked every once in a while so I flashed back to my stock JB 4.1.2 image i had made and flashed the counter so i could take it in to ATT...since flashing back to 4.1.2 I have not had that issue so i am assuming it was something with the ROM
**PRESENT TIME** I decided I wanted to re-root and try CleanROM out...so I got all the necessary stuff I needed (correct drivers and CF Auto Root), followed directions to a T, everything passed, phone rebooted, etc. When i try and use root checker, it just 'searches'...I dont get a 'Not rooted' message or anything...tried installing titanium backup pro root; it installs but when i open it it just says its looking for root access and stays on that screen...ALSO, i do not have SuperSU in my applications but if I go into the Application Manager, SuperSU is there...I also have cwm recovery as well...so its like it partially rooted? Im at a loss right now...anyone have any ideas? Thanks!:good:
Click to expand...
Click to collapse
Download and flash this on cwm.
http://download.chainfire.eu/350/SuperSU/UPDATE-SuperSU-v1.60.zip?retrieve_file=1
jibust said:
Download and flash this on cwm.
Thanks man, but oddly enough, it seems i dont have cwm recovery anymore...looks like its reverted back to the Android system recovery...
Click to expand...
Click to collapse
jwalck5950 said:
jibust said:
Download and flash this on cwm.
Thanks man, but oddly enough, it seems i dont have cwm recovery anymore...looks like its reverted back to the Android system recovery...
Click to expand...
Click to collapse
Download the CWM tar and flash through ODIN, reboot to recovery and flash SuperSU
Click to expand...
Click to collapse
jibust said:
Download the CWM tar and flash through ODIN, reboot to recovery and flash SuperSU
Click to expand...
Click to collapse
Did both...worked like a charm man thanks again!!
jwalck5950 said:
Did both...worked like a charm man thanks again!!
Click to expand...
Click to collapse
Good :thumbup:
Okay be gentle...
After the last update to JSSR15R I lost root and SU, doing the rebbot into recovery (vol down + power button) TWRP launches but when I select to go to recovery via the vol buttons and select it with the power button, all I get is the exclamation point android.
While I'm not a total idiot (debatable of course), is there a way to re-establish root and su without wiping off 15gigs of music and playlists and starting from scratch? Rooting the Nexus 7 (flo) the first time (at least for me) was a fight I eventually won, but for me it was a fight. tia Tutor
Same thing happened to me. I installed TWRP via goomanager. Then, I flashed SU update. Now I'm back rooted and going strong.
Like previous poster mentioned, just reinstall twrp and su.
Your bootloader should already be unlocked. Unlocking the bootloader is the only step that causes you to lose data.
Reinstalling twrp and su will not cause you to lose data, unless you had locked after installing them last time, and now need to unlock again to reinstall.
I reinstalled TWRP via the playstore but while it shows my directory file structure it won't install my copy of Update SuperSU 1.5.1.zip also I went to install goomanager but the descrription says you have to have root prior to installing.
As a sidenote while in TWRP if I go into rebooting the device none of the actions work except when I hit the "Bootloader" option the a error box pops up stating the option isn't available on your device. Tutor
Only way I know of to install TWRP is go to the TWRP web site and download it from there to your PC. You will find flash instructions on the web site.
Sent from my Nexus 7 using xda app-developers app
Download Goo manager from Playstore. Choose Flash Roms, It will tell you that you need a custom recovery to do this and ask if you have one or would like Goo to find one. Choose find one for me and it will download and install TWRP 2.6.3.0. After said process is complete flash SU update. Profit..
Same happened to me, but I reflashed TWRP and root access... Just curious how come that never happened with Clockwork Mod recovery being lost after applying an update to the system on the old N7.
If you don't want to lose root or recovery, it is very simple.
Boot to twrp
Install OTA update.zip
Install SuperSU 1.55 update.zip (Prior to reboot, use 1.55 as 1.65 has issues)
You will maintain root and keep twrp if you do it in this exact order.
sfhub said:
If you don't want to lose root or recovery, it is very simple.
Boot to twrp
Install OTA update.zip
Install SuperSU update.zip (Prior to reboot)
You will maintain root and keep twrp if you do it in this exact order.
Click to expand...
Click to collapse
Can TWRP generally find the latest OTA update.zip on it's own?
Lastb0isct said:
Can TWRP generally find the latest OTA update.zip on it's own?
Click to expand...
Click to collapse
Nope, download the ota manually and place on your virtual sdcard, then boot to twrp and select the file for install
installing through goomanager didn't work for me. It would say it installed but wouldn't really install. I did it using the fastboot method instead and that seemed to work fine.
Well nothing I seemed to do would allow me to re-root the Nexus 7 after the 15R update, I finally went as re-rooted from scratch using the sticky post at the beginning of this subdivision forum for the Nexus. Back up and running in root and su... thx to all those that attempted to help me thru this
CallMeTut said:
Well nothing I seemed to do would allow me to re-root the Nexus 7 after the 15R update, I finally went as re-rooted from scratch using the sticky post at the beginning of this subdivision forum for the Nexus. Back up and running in root and su... thx to all those that attempted to help me thru this
Click to expand...
Click to collapse
I used Wugfresh tool. Everything worked until I flashed the updated SU 1.65. I could never get root. I read earlier that others were using SU 1.5, so I manually went back into TWRP and flashed SU 1.5 and bam, had root! Then SU upgraded itself via the play store to the newer version. Go figure!
jyams said:
I used Wugfresh tool. Everything worked until I flashed the updated SU 1.65. I could never get root. I read earlier that others were using SU 1.5, so I manually went back into TWRP and flashed SU 1.5 and bam, had root! Then SU upgraded itself via the play store to the newer version. Go figure!
Click to expand...
Click to collapse
The update.zip for SU 1.65 is broken. A "placeholder" install script was included that does nothing.
IMO SuperSU 1.55 is the best version to use right now. The install script works, it doesn't mess with a bunch of file permissions for your *other* files in /system to support the new ota survival mode, and it has the fix for the problem that used to break the OTA installs.
The other day I flashed velocity ROM on my flo and it failed on twrp so I flashed clockwork mod and it did the trick but I had forgotten to flash super su so when I pressed reboot it gave me "root lost do you wanna fix sys xbin su?" And of course I clicked yes but after that it told me that the ROM wanted to flash stock recovery and I clicked no so when I booted up I tried using trickster mod and it wouldn't open because I didn't have root so I figured no biggy ill just flash the latest su zip I had and I tried rebooting into cwm but there was no recovery just an android with a red triangle so now I have no root and no recovery which isn't a huge deal but I would really like to fix this. I was thinking of using the wugfresh toolkit I used to first root my flo but I wasent sure if that would work any suggestions?
OsSkates1996 said:
The other day I flashed velocity ROM on my flo and it failed on twrp so I flashed clockwork mod and it did the trick but I had forgotten to flash super su so when I pressed reboot it gave me "root lost do you wanna fix sys xbin su?" And of course I clicked yes but after that it told me that the ROM wanted to flash stock recovery and I clicked no so when I booted up I tried using trickster mod and it wouldn't open because I didn't have root so I figured no biggy ill just flash the latest su zip I had and I tried rebooting into cwm but there was no recovery just an android with a red triangle so now I have no root and no recovery which isn't a huge deal but I would really like to fix this. I was thinking of using the wugfresh toolkit I used to first root my flo but I wasent sure if that would work any suggestions?
Click to expand...
Click to collapse
I don't have any experience using toolkits but I do hear of people using wug's quite a bit. I've only ever used adb/fastboot with the complete sdk installed but a lot of people have problems getting it setup. You can use the toolkit but I would recommend using adb/fastboot because you will get a better working knowledge of what you are actually doing. I installed ADB Installer v1.2 on my brother's laptop and it was ridiculously easy to setup. There are a ton of guides/tutorials out there. Piece of cake!
[GUIDE][30/10/2013]New To Adb And Fastboot Guide
How To: Restore Your 2013 Nexus 7 Back To Stock Using A Full Factory Image And Root It
OsSkates1996 said:
The other day I flashed velocity ROM on my flo and it failed on twrp so I flashed clockwork mod and it did the trick but I had forgotten to flash super su so when I pressed reboot it gave me "root lost do you wanna fix sys xbin su?" And of course I clicked yes but after that it told me that the ROM wanted to flash stock recovery and I clicked no so when I booted up I tried using trickster mod and it wouldn't open because I didn't have root so I figured no biggy ill just flash the latest su zip I had and I tried rebooting into cwm but there was no recovery just an android with a red triangle so now I have no root and no recovery which isn't a huge deal but I would really like to fix this. I was thinking of using the wugfresh toolkit I used to first root my flo but I wasent sure if that would work any suggestions?
Click to expand...
Click to collapse
FWIW, the Android with the red triangle is recovery, stock recovery, just flash a custom recovery again.
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Root works with supersu version 2.62-3. Thanks
sam298 said:
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
Click to expand...
Click to collapse
That wasn't my experience. I took the 6.0.1 update and it failed. So I ran
Code:
fastboot flash system system.img
fastboot flash boot boot.img
using the system and boot images from the 6.0 update. And then I waited for the OTA again. It installed ok.
Using TWRP I installed SuperSU 2.60 for a systemless root of the boot image. Everything is fine.
i can't even get pass installing twrp. every time i flash twrp in fastboot mode it works but it wipes my entire device. booting into twrp shows "NO OS INSTALLED' and even the sd card storage is wiped. the only way to get it to boot is to flash back 6.0.1 full stock rom. any help???
Try nexus root toolkit.
tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
WugFresh did not work for me, after booting into TWRP and looking for the SuperSU and BusyBox they don not show up. Below is a post I have over on WugFresh Forum.
I’m having the same problem as everyone else. I’m using 6.0.1 MMB29K. It goes through the motions but when TWRP launches the /sdcard directory is empty. However, when I reboot and look at the files using an app called File Manager, I see them in /storage/emulated/0/!ReadyToFlash/Root_Files/. However, if I use a app called Root Browser I see a directory called sdcard and in there is !ReadyToFlash/Root_Files/ so they are being copied to the tablet but when you go into TWRP to install them they can’t be found. I tried to use the app Root Browser and make a directory called kiledl, this failed, probably because I do not have root access. Kind of a catch 22 here. I was just going to copy the files in sdcard to my directory and then try again. NO go!!! Anyone else have any ideas? I seems like this is some sort of permissions issue with the files but only from TWRP. I sure hope someone comes up with an answer, WugFresh and ideas?
tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
same result. twrp installed but can't detect my sd card or any files on the device
Download latest SuperSU 2.62-3.
Root via Nexus root toolkit.
Then copy SuperSu to nexus and flash, supersu not from NRT but downloaded latest 2.62-3, busybox and last rar.
Sorry for my English.
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
dlkile said:
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
Click to expand...
Click to collapse
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
aiiee said:
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
aiiee said:
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Correct only when using TWRP. However, I was using WugFresh NRT and it does a temporary install of TWRP then you install the SuperSU and BusyBox files. However, with the wrong version of TWRP you would not see the files in the SDCard folder, it would be empty. However, booting back to Android and using File Explorer the files where there. Using the modified version of TWRP would correct this.
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
r.sorujlall said:
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
Click to expand...
Click to collapse
Yes, here is the link you need to select the LTE or WiFi version depending on you device. I do not have enough post to be able post links, so try removing the "*" from the link below.
forum*.xda-developers*.com/nexus*-7-2013/nexus*-7-2013-qa/mount*-recovery*-t3064562
dlkile said:
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
Click to expand...
Click to collapse
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
aiiee said:
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
Click to expand...
Click to collapse
You most have the same unit as I do. I just got mine a week ago from GroupOn as well.
i bought mine about a week ago off amazon. i had a gift card and had nothing to buy so i decided to get the N7 and give it a try