Related
I have recently rooted my phone i think gone through all the steps on galaxys4root.com. When I was done I tried to update su binary and it said installation failed.then tried to go on titanium backup and it said rom is not rooted .ok i got su app to update but it now saying there is no su binary installed and super su cannot install it . This is a problem But the phone says it is rooted so do I need to re root the phone
Thanks for any help
willdoe said:
I have recently rooted my phone i think gone through all the steps on galaxys4root.com. When I was done I tried to update su binary and it said installation failed.then tried to go on titanium backup and it said rom is not rooted .ok i got su app to update but it now saying there is no su binary installed and super su cannot install it . This is a problem But the phone says it is rooted so do I need to re root the phone
Thanks for any help
Click to expand...
Click to collapse
I think the steps on galaxys4root.com may be outdated or used properly on an older version of Android. Try CF Auto-Root: http://forum.xda-developers.com/showthread.php?t=2294005
Vigz said:
I think the steps on galaxys4root.com may be outdated or used properly on an older version of Android. Try CF Auto-Root: http://forum.xda-developers.com/showthread.php?t=2294005
Click to expand...
Click to collapse
do i have to unroot the phone first or anything i should do before cf auto root right now i have cwm recovery and super su down loaded on it
willdoe said:
do i have to unroot the phone first or anything i should do before cf auto root right now i have cwm recovery and super su down loaded on it
Click to expand...
Click to collapse
No. However, CF Auto-Root will flash stock recovery. If you want to install custom ROMs, simply re-flash CWM Recovery.
willdoe said:
do i have to unroot the phone first or anything i should do before cf auto root right now i have cwm recovery and super su down loaded on it
Click to expand...
Click to collapse
ok thanks a bunch one more question what steps should i follow to re-flash cwm recovery
willdoe said:
ok thanks a bunch one more question what steps should i follow to re-flash cwm recovery
Click to expand...
Click to collapse
I am guessing here but please correct me if i am wrong cf auto root gives me root then i should follow galaxy s4root.com instrutions on how to install cwm recovery
willdoe said:
I am guessing here but please correct me if i am wrong cf auto root gives me root then i should follow galaxy s4root.com instrutions on how to install cwm recovery
Click to expand...
Click to collapse
Once you are rooted you have to choose which recovery you want. Twrp is the most compatible with most Roms out there. To get cwm you need to install ROM manager from the market. The option to flash recovery will be inside. If you want twrp download goo manager and the option to flash will also be in the app. Good luck!
Sent from my SGH-M919 using xda app-developers app
mrzhadow said:
Once you are rooted you have to choose which recovery you want. Twrp is the most compatible with most Roms out there. To get cwm you need to install ROM manager from the market. The option to flash recovery will be inside. If you want twrp download goo manager and the option to flash will also be in the app. Good luck!
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You can also get either TWRP or CWM as a Tar file that can be flashed in Odin.
You can also download the .img files and flash either with Flashify.
There are a lot of ways to flash recoveries. Each with specific advantages for specific situations.
Ok thanks a bunch to all of ya in my situation I am just trying to get root on my phone it is a t-mobile S4 its running 4.2.2 it seemed easy enough on galaxyS4root.com I think I guessed wrong so I will definitely try cf auto root though I am not done trying yet so again thanks for your time
willdoe said:
Ok thanks a bunch to all of ya in my situation I am just trying to get root on my phone it is a t-mobile S4 its running 4.2.2 it seemed easy enough on galaxyS4root.com I think I guessed wrong so I will definitely try cf auto root though I am not done trying yet so again thanks for your time
Click to expand...
Click to collapse
That website you tried seems to have borked you all up. Cut your losses with methods from there and start over with the CF Auto Root method. it will work perfectly in 30 seconds.
Ya I was pretty aggravated lastnight but got up this morning used cf autoroot and so far so good super su has binary installed titanum back has root its going good so far thanks again for yalls help
Recently I got a nexus 7 2013 5.1.1 LMY48I which I tried to root with NRT. Long story short like many other people I cant get TWRP to mount the files it needs(I get to the automated step that is suppose to open TWRP and install some files from a ZIP archive and it hangs up). First off I have a USB OTG cable coming within a couple days. I have looked for the past couple hours for a solution and keep coming up empty. Basically I have two questions, 1. what files do I need to have transferred so that I can get my Root permissions installed properly and 2. should I wait for the USB OTG calbe or should I try to use abs push
I'm in the same boat, really would like to get this thing rooted. I have been all over the WugFresh Forum, as well as Android Central and this one too of course. I have not found an answer to this problem yet. If I come across one I will post here, please do the same.
Dude. this is infuriating. Apparently the alst batch that was made, they changed the mmc chip. These all went out on Groupon and stuff on sale.
https://www.reddit.com/r/AndroidQue...e_to_mount_partitions_after_flashing_twrp_on/
The only recovery that I got to work was the TWRP for Multirom because they actually addressed the issue. The bug has been brought up on the TWRP flo github they just have yet to fix it.
This is infuriating
gorilla p said:
Dude. this is infuriating. Apparently the alst batch that was made, they changed the mmc chip. These all went out on Groupon and stuff on sale.
The only recovery that I got to work was the TWRP for Multirom because they actually addressed the issue. The bug has been brought up on the TWRP flo github they just have yet to fix it.
This is infuriating
Click to expand...
Click to collapse
So what version of Android are you running now. I am on 6.0.1 and want to root it. Did you apply this to to Lollipop or Marshmallow? Thanks for the info.
UPDATE: This worked for me I am now on MM 6.0.1 and rooted. Thank you for the find.
Yea we already have a thread for this..
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
sgtfoo said:
Yea we already have a thread for this..
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
Click to expand...
Click to collapse
Thank you I was able to downgrade and root my device using that method. Now I just need to figure out how to flash to purenexus or just upgrade my device to 6.+ and root it.
AngryPotato said:
Thank you I was able to downgrade and root my device using that method. Now I just need to figure out how to flash to purenexus or just upgrade my device to 6.+ and root it.
Click to expand...
Click to collapse
You can root 6.0.1 using the beta SU from Chainfire. I am running the new one from Groupon using the multirom TWRP and I flashed SU 2.65 and it worked perfectly.
diggitydogg said:
You can root 6.0.1 using the beta SU from Chainfire. I am running the new one from Groupon using the multirom TWRP and I flashed SU 2.65 and it worked perfectly.
Click to expand...
Click to collapse
so update to 6.0.1 stock then root or flash a rooted rom?
AngryPotato said:
so update to 6.0.1 stock then root or flash a rooted rom?
Click to expand...
Click to collapse
I did a clean flash of stock 6.0.1. Then flashed the multirom version of TWRP since I have one of the newer chipsets of the Nexus 7. Then I flashed the beta SU. All was good. The issue I am having now is that I can't get the restore from within TWRP to work. I backup fine, but when I restore it gets partway through the system part and then just says Failed. Not really sure what the deal is there. I am guessing it has to do with this multirom version of TWRP, but I'm not really sure...
Running N910PVPU4DPC1 [http://forum.xda-developers.com/note-4-sprint/development/rom-t3352832]
It's been running fine for the past month or so, then yesterday, I went to run Titanium Backup, and it said my phone no longer had root access.
---------------------------------------------
SuperSU
There is no SU binary installed, and SuperSU cannot install it. There is a problem!
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!
---------------------------------------------
I've tried to re-root via CF-Auto-Root, it'll complete without error, but still no root access.
Anyway I can get root back without blowing out and starting from scratch?
If you have recovery just flash SuperSU itself.
SaintZ93 said:
If you have recovery just flash SuperSU itself.
Click to expand...
Click to collapse
Thanks for your reply SaintZ93.
Just tried that via https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Uninstalled my previous version of SuperSU, booted to TWRP 3.0.2-0, no errors on install, fire up SuperSU, I get the same error message as before.
I was really hoping to get SU back with out having to go and reinstall everything. Doesn't look like it's going to work out that way.
Actually I just noticed the same thing, its quite weird, I lost root also. I had root working fine with PD1 now its gone.
I believe a security update was pushed, well at I know one was on my Sprint Note 4, and I think it auto installed that's what made me lost root.
I simply flashed supersu from TWRP and I had root again.
Don't know if this would help, but I turned off firmware updates on my phone and haven't had an issue for the last 3 days.
I think the update was pushed out on Tuesday or Wednesday because I noticed I didn't have root on Thursday.
krakerx said:
Running N910PVPU4DPC1 [http://forum.xda-developers.com/note-4-sprint/development/rom-t3352832]
It's been running fine for the past month or so, then yesterday, I went to run Titanium Backup, and it said my phone no longer had root access.
---------------------------------------------
SuperSU
There is no SU binary installed, and SuperSU cannot install it. There is a problem!
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!
---------------------------------------------
I've tried to re-root via CF-Auto-Root, it'll complete without error, but still no root access.
Anyway I can get root back without blowing out and starting from scratch?
Click to expand...
Click to collapse
I believe that the SuperSu that comes with that ROM is systemless, which you would need to flash SuperSu 2.68
I am in the same boat.
ianmb said:
I believe that the SuperSu that comes with that ROM is systemless, which you would need to flash SuperSu 2.68
Click to expand...
Click to collapse
That worked like a f'n charm!
I uninstalled SuperSU, downloaded SuperSU 2.68 [https://download.chainfire.eu/924/SuperSU], installed via TWRP, and verified!
Thanks for all the help!
krakerx said:
That worked like a f'n charm!
I uninstalled SuperSU, downloaded SuperSU 2.68 [https://download.chainfire.eu/924/SuperSU], installed via TWRP, and verified!
Thanks for all the help!
Click to expand...
Click to collapse
Glad it worked for you
can I stall SUPERSU 2.68 with stock recovery? how?
I extracted the 2.68 zip but can I install without a custom recovery?
krakerx said:
That worked like a f'n charm!
I uninstalled SuperSU, downloaded SuperSU 2.68 [https://download.chainfire.eu/924/SuperSU], installed via TWRP, and verified!
Thanks for all the help!
Click to expand...
Click to collapse
Same issue of lost root. Worked great so far. Thanks for the info.
Sent from my SM-N910P using Tapatalk
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
No, i downloaded normal su (SuperSU) and then flashed it through TWRP. I don't know which su you are using, but there are loads of us who have installed SuperSU without an issue.
nemexs said:
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
Click to expand...
Click to collapse
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
PS: regular supersu is both systemless and "normal" root it makes a decision during installation determining whether your device can support normal root and if not then it does a systemless boot.img patch.
StykerB said:
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
Click to expand...
Click to collapse
You beat me to pointing him to it. If I can add, there's a dedicated SuperSU thread to seek help if SuperSU causes an issue:
http://forum.xda-developers.com/showthread.php?t=1538053
Highly unlikely but just in case. If you are not sure, there are sufficient number of toolkits out there that can simplify the job for you.
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
nemexs said:
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
Click to expand...
Click to collapse
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
tropicanapure said:
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
Click to expand...
Click to collapse
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
nemexs said:
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
Click to expand...
Click to collapse
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
tropicanapure said:
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
Click to expand...
Click to collapse
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
nemexs said:
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
Click to expand...
Click to collapse
Assuming your bootloader is already unlocked beforehand, the straight answer to your question is yes, that's how most of us do it.
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
otonieru said:
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
Click to expand...
Click to collapse
doesn't work for me.
Hey - followed this guide (https://matthewtraughber.github.io/pixel_manual-update_guide/) to update my rooted XL to NMF26O, lost root along the process. Flashing the SR5 supersu.zip didn't give me any errors in TWRP, but supersu isn't installed on boot. If I go into the Play Store and install it manually, I get an error about the SU binary not being installed. Any suggestions?
cantsingh said:
Hey - followed this guide (https://matthewtraughber.github.io/pixel_manual-update_guide/) to update my rooted XL to NMF26O, lost root along the process. Flashing the SR5 supersu.zip didn't give me any errors in TWRP, but supersu isn't installed on boot. If I go into the Play Store and install it manually, I get an error about the SU binary not being installed. Any suggestions?
Click to expand...
Click to collapse
That update permanently block root for your device
cwalker0906 said:
That update permanently block root for your device
Click to expand...
Click to collapse
Even if I have an unlocked bootloader already?
cantsingh said:
Even if I have an unlocked bootloader already?
Click to expand...
Click to collapse
No I'm messing with you, many people have had this problem. Easy fix, read last few pages of root thread
cwalker0906 said:
No I'm messing with you, many people have had this problem. Easy fix, read last few pages of root thread
Click to expand...
Click to collapse
Lol you terrified me. What's the fix? I'm looking for the root thread right now..
cantsingh said:
Lol you terrified me. What's the fix? I'm looking for the root thread right now..
Click to expand...
Click to collapse
Fastboot boot twrp alpha 2, flash the su zip, and reboot
cwalker0906 said:
Fastboot boot twrp alpha 2, flash the su zip, and reboot
Click to expand...
Click to collapse
Got it. Thanks, buddy. I'll post back here to confirm.
Confirmed. If you lost root when updating to NMF26O (or after installing TWRP RC1), then hot-boot TWRP Alpha 2 (fastboot boot twrp-alpha-2.img), flash supersu and reboot. Thanks!
confirmed - worked for me!
cantsingh said:
Got it. Thanks, buddy. I'll post back here to confirm.
Click to expand...
Click to collapse
Confirmed, this saved my life
I had a Pixel XL that had 7.1 on it and rooted it successfully. Not sure when but my phone got updated to 7.1.1 I was careful not to take the update, maybe I inadvertently clicked it (I don't think so) but I think it got forced on me. So I ended up with 7.1.1. Tried using my hotspot which worked before and it didn't. Fortunately my device boot loader was still unlocked, but previous root technique using twrp-3.0.2-0-RC1-fastboot-marlin.img didn't work (seems like it does but after reboot, no joy). Figured if I flashed stock 7.1 image that would do the trick - no joy.
Found this post
Followed suggestion above and used twrp-3.0.2-0-alpha2-fastboot-marlin.img and used same SR5-SuperSU-v2.78 - reboot worked great. FYI, I downloaded the stock 7.1.1 (marlin-nof26v-factory-1dce14a1.zip) and rooting works with that.
Note: turn off "Automatic System Updates" (obviously that was probably the originally culprit) under developer options.
miker2069 said:
Confirmed, this saved my life
I had a Pixel XL that had 7.1 on it and rooted it successfully. Not sure when but my phone got updated to 7.1.1 I was careful not to take the update, maybe I inadvertently clicked it (I don't think so) but I think it got forced on me. So I ended up with 7.1.1. Tried using my hotspot which worked before and it didn't. Fortunately my device boot loader was still unlocked, but previous root technique using twrp-3.0.2-0-RC1-fastboot-marlin.img didn't work (seems like it does but after reboot, no joy). Figured if I flashed stock 7.1 image that would do the trick - no joy.
Found this post
Followed suggestion above and used twrp-3.0.2-0-alpha2-fastboot-marlin.img and used same SR5-SuperSU-v2.78 - reboot worked great. FYI, I downloaded the stock 7.1.1 (marlin-nof26v-factory-1dce14a1.zip) and rooting works with that.
Note: turn off "Automatic System Updates" (obviously that was probably the originally culprit) under developer options.
Click to expand...
Click to collapse
You fastboot twrp rc1 but then flash the twrp rc1 zip and then it should be fine and then flash SuperSU 2.79 sr3.