Q&A for Root
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Root. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Nexus 9 root
I'm a newbie so can't post in Chainfire's root thread; but thought I'd post an issue with rooting my N9 in case it helps anyone.
When trying to boot inject.img, it returned "FAILED (data transfer failure (Unkown error))". Tried multiple times, rebooted, etc. Confirmed connection by fastboot devices command.
Not sure exactly what caused it to work, but I rebooted my PC, tried it, it failed, so I unplugged USB connector, plugged it back in to a different port on PC, and SUCCESS! (Maybe just bad USB connection??)
Hopefully this helps someone out there.
Cheers,
Is autoroot working in 25L, the New update?
thebrainkafka said:
Is autoroot working in 25L, the New update?
Click to expand...
Click to collapse
The new update is Q. Some have gotten auto root to work, others have not. You can do the manual root method and flash the elemental x kernel. That was updated with the latest commits.
Sent from my Nexus 9 using Tapatalk
Flash LRX21Q manually. You will need to unzip the package and fastboot flash all img files manually (see this thread: http://forum.xda-developers.com/nexus-9/help/factory-image-flash-t2929019). After that Auto CF will work.
Sent from my Nexus 9 using XDA Free mobile app
I have learnt so many things from your artic,thank you.
---------------------------------------------------------------------------------
I don't know how you guys got it working. I'm on the latest factory image. I ran CF auto root just fine, but then I rebooted and went to flash the SuperSu update to 2.25 via TWRP, and apps just freeze when I try to grant them root now. SuperSu itself will open and I can configure it, but it never comes up when I should be getting an access prompt from using an app requesting root. The app and SuperSu just seem to freeze.
I'm on the latest TWRP as well. I had some issues and went into fastboot and rewrote the system image from the factory image and my device booted again, but updating SuperSu via TWRP says it works but I still get freezing on every app I attempt to grant root. So basically I cannot use root at all.
Moved the above here from Chainfire's root thread. I don't have a clue what's causing the freezing.
EDIT: It gets odder. It's as if the prompts are the problem. I changed SuperSu to grant by default and an app worked. But if I set it to prompt, nothing comes up. Logs only appear when I set it to allow by default.
MikeRL100 said:
I don't know how you guys got it working. I'm on the latest factory image. I ran CF auto root just fine, but then I rebooted and went to flash the SuperSu update to 2.25 via TWRP, and apps just freeze when I try to grant them root now. SuperSu itself will open and I can configure it, but it never comes up when I should be getting an access prompt from using an app requesting root. The app and SuperSu just seem to freeze.
I'm on the latest TWRP as well. I had some issues and went into fastboot and rewrote the system image from the factory image and my device booted again, but updating SuperSu via TWRP says it works but I still get freezing on every app I attempt to grant root. So basically I cannot use root at all.
Moved the above here from Chainfire's root thread. I don't have a clue what's causing the freezing.
EDIT: It gets odder. It's as if the prompts are the problem. I changed SuperSu to grant by default and an app worked. But if I set it to prompt, nothing comes up. Logs only appear when I set it to allow by default.
Click to expand...
Click to collapse
I lost root somehow. Probably kernel. I just reflashed stock recovery and R boot image, ran CFAR again, flashed TWRP and then 2.25. All good now.
Maybe I need to do a complete wipe. Or perhaps I could wait - if anybody knows what I should do. I would log it, but how do I get logs without root? Chainfire may be interested.
MikeRL100 said:
Maybe I need to do a complete wipe. Or perhaps I could wait - if anybody knows what I should do. I would log it, but how do I get logs without root? Chainfire may be interested.
Click to expand...
Click to collapse
I just wiped recovery, boot and reflashed those stock images. Ran CFAR. Flashed TWRP. Flashed 2.25 in TWRP. All good now.
prdog1 said:
I lost root somehow. Probably kernel. I just reflashed stock recovery and R boot image, ran CFAR again, flashed TWRP and then 2.25. All good now.
Click to expand...
Click to collapse
There's a few lines in init.rc that need to be changed to get root working if flashing a factory google boot.img. Kernel itself doesn't just the kernel zimage won't break root, but flashing a boot.IMG will unless you make a small edit to the ramdisk.
For those having problems after flashing 2.25 go into SU settings aand uncheck and recheck the Enable SU checkbox. Worked for me. Working as should now.
Yes I mentioned that in a thread earlier. Must have not been the only one with the problem.
Latest beta 2.27
I'd wait before rooting, seems Chainfire may be able to root without the kernel patches soon: https://plus.google.com/u/0/+Chainfire/posts/K7n4e1q5SMD
Diesel779 said:
I'd wait before rooting, seems Chainfire may be able to root without the kernel patches soon: https://plus.google.com/u/0/+Chainfire/posts/K7n4e1q5SMD
Click to expand...
Click to collapse
Seems to be working. Reports are good.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
prdog1 said:
Seems to be working. Reports are good.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Things are moving along quickly I'm going to hold off from rooting for a few days maybe longer. Give Flar2 time to do some more work on his kernel too.
SU 2.27
I was on R unlocked and rooted w/CFAR using su 2.25 and TWRP 2.8.2.1. Here is what i did - uninstalled/deleted SU, fastboot erased recovery and boot, fastboot flashed stock R boot and recovery. Rebooted all was ok NO ROOT. Then -> fastboot erase recovery -> fastboot flash TWRP -> flashed SU 2.27 w/TWRP -> wipe dalvik/cache -> reboot -> BAAAM ROOT. Thank you Chainfilre!!!!!!
After root dont get updates
After root my tablet nexus 9, I don't get updates. The device detect that there is a update, download it, try to install and then say error!!!
I have did the CF-auto root flasheable. Do you have any solution for that???
Algruista said:
After root my tablet nexus 9, I don't get updates. The device detect that there is a update, download it, try to install and then say error!!!
I have did the CF-auto root flasheable. Do you have any solution for that???
Click to expand...
Click to collapse
Read this forum http://forum.xda-developers.com/nexus-9/orig-development/root-t2929118
or try this one http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
Related
alright, how bad did I screw up here? Got the OTA notification last night, read nothing but good things and most keeping root through the process. I missed an important detail of using the OTA rootkeeper. So I'm currently on the latest update and lost root. I've tried one click 1.1 to no avail so far. I am unlocked and was rooted prior, but never got around to installing a recovery (hadn't found a ROM I was quite happy with enough to lose all my data just yet)
So.. all that said, is there a root option for the latest OTA yet?
racingtiger03 said:
alright, how bad did I screw up here? Got the OTA notification last night, read nothing but good things and most keeping root through the process. I missed an important detail of using the OTA rootkeeper. So I'm currently on the latest update and lost root. I've tried one click 1.1 to no avail so far. I am unlocked and was rooted prior, but never got around to installing a recovery (hadn't found a ROM I was quite happy with enough to lose all my data just yet)
So.. all that said, is there a root option for the latest OTA yet?
Click to expand...
Click to collapse
Yes, all you need to do is flash Amon Ra through fastboot and reboot to recovery .. under the developer menu option on Amon Ra you have the option to install SU and superuser . Just run that and reboot you would have to unlock of course to install Amon Ra
Looks like I'm installing AmonRa today. Thanks!!!! I'm from a moto world where CWM and SPR are all we had.. the feature to install SU binary from recovery is new to me haha
racingtiger03 said:
Looks like I'm installing AmonRa today. Thanks!!!! I'm from a moto world where CWM and SPR are all we had.. the feature to install SU binary from recovery is new to me haha
Click to expand...
Click to collapse
Yes, I came from the OG droid so its quite a world of difference in the process to install stuff due to being S-on.
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
das0527 said:
Idiot check - can someone verify the command for flashing the Amon Ra recovery through fastboot? I've already got the command prompt open and cd to the proper directory.
Click to expand...
Click to collapse
Fastboot flash recovery nameofrecovery.img
for amon ra it was like amon-ra-3.13.gnm.img or something its the name of the file you downloaded just don't forget to add the .img at the end.
no luck. Got amon ra and ran the command to install su and superuser.. still no root access afterwards =/
racingtiger03 said:
no luck. Got amon ra and ran the command to install su and superuser.. still no root access afterwards =/
Click to expand...
Click to collapse
Odd, do you have the superuser app in your app drawer ? Otherwise , I heard to download it from the market and it will work .
I did it this way and I read about it from others that did it this was as well.
I need some help, please - I may have made a very bad assumption here...
I just got my Rezound today (upgrading from a Thunderbolt). I saw the stickied thread about how (relatively) easy it was to perm-root the phone after the bootloader was unlocked, and I assumed that this all still applied after getting the OTA update (not realizing that the OTA update was JUST released - my assumption was that it was older and already dealt with).
So I got the OTA first thing after activating the phone, THEN unlocked the bootloader, THEN tried to root via One Click - I tried both OneClickRoot_1.1 and Super OneClick 2.3.3.0, but it doesn't seem to be working.
I'm getting "Permission denied" errors on mounts and "read-only file system" errors for CHMods and file copies during the Zerg Rush process. It says "Congrats you are now perm rooted", but it doesn't seem to be true - I was able to install SuperUser from the market, but the BusyBox installer says it can't find the su binaries, so I'm not convinced SuperUser is actually working.
Considering that I never had root access to the phone prior to installing the OTA, is there anything I do besides waiting for one or more of the root tools to be updated to deal with the new OTA?
mjh68 said:
Odd, do you have the superuser app in your app drawer ? Otherwise , I heard to download it from the market and it will work .
I did it this way and I read about it from others that did it this was as well.
Click to expand...
Click to collapse
yeah, I have superuser installed. Nothing is getting SU access and as the above guy posted, all of the zergrush methods are completely failing. there is a rooted stock OTA ROM.. seriously debating that route now... =/
racingtiger03 said:
yeah, I have superuser installed. Nothing is getting SU access and as the above guy posted, all of the zergrush methods are completely failing. there is a rooted stock OTA ROM.. seriously debating that route now... =/
Click to expand...
Click to collapse
I would try the rooted stock rom, but just not sure why it didn't work for you . I did all the steps you did and I was rerooted afterwards. Are you getting the pop up for superuser when an app asks for permission ? Sorry, was trying to be helpful
got it.. had to attempt the SU install twice.. also reboot DIRECTLY from recovery, do NOT reboot back to bootloader. I think that's what killed it for me. And yes in the end I did have to install the superuser app from the market to get it working again.
racingtiger03 said:
got it.. had to attempt the SU install twice.. also reboot DIRECTLY from recovery, do NOT reboot back to bootloader. I think that's what killed it for me. And yes in the end I did have to install the superuser app from the market to get it working again.
Click to expand...
Click to collapse
Great ! I couldn't remember how I rebooted ! Sorry for making you do it so many times .
haha.. if you knew how many times I attempted one click two attempts at the SU from amon ra is nothing lmao. Thanks for the tip! Just glad to have root back LOL
mjh68 said:
I would try the rooted stock rom, but just not sure why it didn't work for you . I did all the steps you did and I was rerooted afterwards. Are you getting the pop up for superuser when an app asks for permission ? Sorry, was trying to be helpful
Click to expand...
Click to collapse
I'm having a serious issue here - for unknown reasons (I have NOT installed any ROMS or ANY non-OTA updates whatsoever), my Rezound is no longer able to connect to Verizon's network, for data or voice (it just says "no service"; WiFi works fine). As I said in my previous post on the previous page, I just got the phone today, and was trying to use OneClick to root my phone, but it isn't working because of the OTA update, and at some point I think the radio got screwed up.
So my intended remedy was to download the rooted stock rom and install that, but, naturally, it doesn't pass signature verification on the stock recovery. So I tried to follow another set of instructions to get AmonRa recovery installed, but the bootloader keeps rejecting the PH98IMG.zip file, telling me (depending on which one I try to use) that there's "no image or wrong image" or "Main Version is older! Update Fail!". Furthermore, I tried to extract the PH98IMG.zip file from the rooted stock rom file that I downloaded from the link on this site, but that zip file is corrupted (it won't open on my PC, even after I re-downloaded the rom).
Can someone help me figure out how to get AmonRa installed? From there, I can hopefully get the rooted stock rom installed. OR, at the very least, help me run a radio update so the phone will at least work until an easier root method becomes available?
Thanks.
beleynn said:
Can someone help me figure out how to get AmonRa installed? From there, I can hopefully get the rooted stock rom installed. OR, at the very least, help me run a radio update so the phone will at least work until an easier root method becomes available?
Thanks.
Click to expand...
Click to collapse
Did you try flashing in fastboot? Download Amon Ra v3.13 and then use this command in fastboot:
Fastboot flash recovery nameofrecovery.img
Make sure fastboot is off, usb debugging is on
Link to most current Amon recovery....
http://205.196.123.46/507ebb4s3cqg/c...r-3.13-gnm.img
Use this tool below to flash, easiest to use....... instructions in thread...
http://www.scottsroms.com/downloads.php?do=file&id=57
Viper32 said:
Make sure fastboot is off, usb debugging is on
Link to most current Amon recovery....
Use this tool below to flash, easiest to use....... instructions in thread...
Click to expand...
Click to collapse
Perfect. Thank you.
---------- Post added at 05:27 AM ---------- Previous post was at 04:49 AM ----------
I got the rooted ota rom installed easily, and better yet, the root worked perfectly. The problem is, I still can't connect to any wireless networks (aside from wifi).
I used the tool linked in the previous response to flash a boot.img I got out of this thread (specifically, the stock 2.01.605.11 w/ 1/26 OTA), but still nothing.
Any thoughts?
Is your battery cover on?
Sent from my Asus Transformer, using Tapatalk. Forgive my misspellings.
RED ZMAN said:
Is your battery cover on?
Sent from my Asus Transformer, using Tapatalk. Forgive my misspellings.
Click to expand...
Click to collapse
It is now. I discovered that wonderful "feature" about 30 seconds before your reply showed up. Works perfectly, of course, though I'd been going nuts for *checks* 6 hours.
How I regained root:
Okay, with Scott's CleanFLASH, I flashed
con247 said:
amonra
Click to expand...
Click to collapse
, then used the Development section or whatever in the Recovery to install superuser. I then rebooted twice, used CleanFLASH again to flash the
andybones said:
stock recovery
Click to expand...
Click to collapse
back. After reboot, I installed superuser from market, then updated the binary.
Titanium Backup now works and I can confirm regaining root after the OTA update. To protect myself from this in the future, I have installed OTA RootKeeper. OTA RootKeeper has been confirmed to backup superuser and is a simple way of restoring superuser after an OTA.
I did not have to backup anything on the internal sdcard, as I did not lose any data through this process, but it never hurts to do it, just in case. I am running the stock Rom, and unlocked through HTC-dev.
Thanks to con247 and andybones for pointing me in the right direction.
I am not responsible for any issues with your phone, so proceed at your own risk.
I have the HTC Rezound with the recently released O.T.A. ICS from Verizon. My objective is to root the phone and kill all of the B.S. bloatware that Verizon feels they must add to the phone. I have posted before to ask how to do this and everyone says root the phone and kill the apk files or alternatively Root the phone and download Rom Toolbox then kill it from there. I have gone through and followed the "[GUIDE] Super-noob guide to unlocking, rooting, and flashing Ziggys kernel" to the 'T' up until its time to load the Kernel. I do not want to change the Kernel so my qquestion is:
If i have gone through the process of rooting my phone it should be rooted at this point. However when I run Root Check Basic it tells me "Sorry this device does not have proper root access." I do not understand why. In order to get full root access am i going to have to continue with installing the Kernel.
Is there anybody who could help me. I am missing.
bobcsc said:
I have the HTC Rezound with the recently released O.T.A. ICS from Verizon. My objective is to root the phone and kill all of the B.S. bloatware that Verizon feels they must add to the phone. I have posted before to ask how to do this and everyone says root the phone and kill the apk files or alternatively Root the phone and download Rom Toolbox then kill it from there. I have gone through and followed the "[GUIDE] Super-noob guide to unlocking, rooting, and flashing Ziggys kernel" to the 'T' up until its time to load the Kernel. I do not want to change the Kernel so my qquestion is:
If i have gone through the process of rooting my phone it should be rooted at this point. However when I run Root Check Basic it tells me "Sorry this device does not have proper root access." I do not understand why. In order to get full root access am i going to have to continue with installing the Kernel.
Is there anybody who could help me. I am missing.
Click to expand...
Click to collapse
First, wrong section. But to help out... Do you have recovery? If you do just download the newest supersu zip file and flash it in recovery.. google search for it. Good luck. I hope you don't get flamed too much
Sent from my ADR6425LVW using Tapatalk 2
bobcsc said:
I have the HTC Rezound with the recently released O.T.A. ICS from Verizon. My objective is to root the phone and kill all of the B.S. bloatware that Verizon feels they must add to the phone. I have posted before to ask how to do this and everyone says root the phone and kill the apk files or alternatively Root the phone and download Rom Toolbox then kill it from there. I have gone through and followed the "[GUIDE] Super-noob guide to unlocking, rooting, and flashing Ziggys kernel" to the 'T' up until its time to load the Kernel. I do not want to change the Kernel so my qquestion is:
If i have gone through the process of rooting my phone it should be rooted at this point. However when I run Root Check Basic it tells me "Sorry this device does not have proper root access." I do not understand why. In order to get full root access am i going to have to continue with installing the Kernel.
Is there anybody who could help me. I am missing.
Click to expand...
Click to collapse
1. Wrong section. Please post things like this in the general or q&a sections, not flaming, just telling you for future references.
2. If your device has an unlocked bootloader, flash amon ra recovery or twrp and go to the dev menu and it will say something like give Su permissions or root or whatever, just click that.
3. Profit.
4. You're welcome.
To root you should download the latest version of SuperSU zip file, and flash it with anon RA recovery.
http://download.chainfire.eu/204/SuperSU/
HowardZ said:
To root you should download the latest version of SuperSU zip file, and flash it with anon RA recovery.
http://download.chainfire.eu/204/SuperSU/
Click to expand...
Click to collapse
Thanks for linking that. I was to lazy didn't want to do everything for him
Sent from my ADR6425LVW using Tapatalk 2
Sorry
I didn't mean to post in the wrong section. If a moderator wants to move this post it will not hurt my feelings. Thank you all for the advice i will try them out tomorrow and report back to this thread. If anybody else has anything to add i would love to see it.
Thank you
This is a great community.
You do not need to root your phone to get rid of the bloatware, you can keep your phone stock unrooted and debloat it yourself and not have to worry about flashing anything. To disable go to menu>apps and after clicking an app you see the choice of disabling.
SuperSU not working
I don't know why i cant get this to work. I have flashed the amon recovery to my phone. Followed these steps:
1)Flash AmonRa Recovery.
2) Boot into AmonRa Recovery.
3) Scroll to and enter the Developer menu.
4) Scroll to install Su. DO NOT INSTALL THE ENG (Unguarded) one. Use the other one.
5) Confirm this, when it is finished, go ahead and reboot. You should be rooted.
Downloaded the SuperSU from google play and select install. after a few minutes it comes back and says the SU binert needs updated, I select continue. then after about a minute it says installation failed.
What am i missing? I have followed everything to e "t" I don't get it
More help please.
richii0207 said:
You do not need to root your phone to get rid of the bloatware, you can keep your phone stock unrooted and debloat it yourself and not have to worry about flashing anything. To disable go to menu>apps and after clicking an app you see the choice of disabling.
Click to expand...
Click to collapse
Do this if that's the only reason you want root
Sent from my ADR6425LVW using xda app-developers app
bobcsc said:
I don't know why i cant get this to work. I have flashed the amon recovery to my phone. Followed these steps:
1)Flash AmonRa Recovery.
2) Boot into AmonRa Recovery.
3) Scroll to and enter the Developer menu.
4) Scroll to install Su. DO NOT INSTALL THE ENG (Unguarded) one. Use the other one.
5) Confirm this, when it is finished, go ahead and reboot. You should be rooted.
Downloaded the SuperSU from google play and select install. after a few minutes it comes back and says the SU binert needs updated, I select continue. then after about a minute it says installation failed.
What am i missing? I have followed everything to e "t" I don't get it
More help please.
Click to expand...
Click to collapse
Ics broke the ability of amon ra to install su. You need to download the flashable zip and flash it in recovery
Sent from my ADR6425LVW using Tapatalk 2
Bradsinram- I may in the future may want to increase my skills and get a little deeper into the roming. i just want to start here if possible. I have also do this and when you restart the phone it all seems to be back on and updating.
pwned3- I have downloaded the flashable zip. Now do i flash this to the recovery in place of the amon. or is this flashed with the amon .img
Also do i use the same method as above to flash it or is there an easier way.
THanks
bobcsc said:
Bradsinram- I may in the future may want to increase my skills and get a little deeper into the roming. i just want to start here if possible. I have also do this and when you restart the phone it all seems to be back on and updating.
pwned3- I have downloaded the flashable zip. Now do i flash this to the recovery in place of the amon. or is this flashed with the amon .img
Also do i use the same method as above to flash it or is there an easier way.
THanks
Click to expand...
Click to collapse
Flash in recovery. If you have already flashed a custom recovery(amon ra) then pull your battery, hold out for 3 seconds, insert battery, hold vol down and power at same time til bootloader boots, select recovery, select flash zip menu, select sdcard(assuming you placed flashed zip on external sdcard), select file, press power to confirm, reboot when done. Now you should be rooted.
Sent from my ADR6425LVW using Xparent SkyBlue Tapatalk 2
Thank you Thank you Thank you
pwned3 said:
Ics broke the ability of amon ra to install su. You need to download the flashable zip and flash it in recovery
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I finally got it thank you guys for being patient with me.
pwned3
zzdave_stud
Howard z
bradsinram
keolawills
All of you rock i will go through and hit thank you to each of you.
this thread also helped me access root.
thank you guys. really.
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
xDexter said:
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
Click to expand...
Click to collapse
Ive been using ViperDNA which comes with what seems like a custom SuperUser type of all in it.
But when I origionally rooted my phone, i seem to remember having an issue with SuperSU, and the first time i rooted i said screw it and just installed Superuser without any problems. The second time i rooted, i Installed SuperSU, then had to download Superuser form the Android Market, to update the binary, which updated it for SuperSU, and that solved my problem.
When you try to open an app that needs to use root access, do you get the notification asking for permission?
perhaps the "other" superSU/busybox package that you used didn't properly do what it needed to do?
I see the link on that tutorial is broken, fortunately i have the file that i originally downloaded form that very same tutorial saved to my hard drive, and now uploaded to DropBox if you would like to download it and try flashing this zip while in recovery to see if it gives you a proper root.
I would recommend downloading the above file, and flashing that to see if it helps. I'll try to remember to check back here to see if you posted anything in reply, but let me know if it doesn't work. Ill try to help as much as I can
BigRed35m said:
I would recommend downloading the above file, and flashing that to see if it helps. I'll try to remember to check back here to see if you posted anything in reply, but let me know if it doesn't work. Ill try to help as much as I can
Click to expand...
Click to collapse
I installed your package, and get the same errors before in SuperSU. It wants to upgrade but then force restarts whilst trying.
I then tried the Superuser app by Chainsdd, and I make a little progress?
First, when I try to upgrade, it asks for root from SuperSU and Superuser. Since SuperSU came with the busybox package, I can't uninstall it.
When I first go to the updater, it shows me this: (See attachment 1, I can't do links :S)
After I upgrade it, I am left with this screen: (see attachment 2)
It looks like it reverts back to su v .98 from 1.02?
Either way, as soon as I hit lets do it again, the phone restarts. Did I screw up the unlock/root somehow? In the top left of my fastboot screen it shows ***TAMPERED*** and ***UNLOCKED***
I am using CWM 6.0.2.1
BigRed35m said:
When you try to open an app that needs to use root access, do you get the notification asking for permission?
Click to expand...
Click to collapse
If I do it right when I reboot my phone it usually asks correctly
Thanks again for the help so far!
xDexter said:
I installed your package, and get the same errors before in SuperSU. It wants to upgrade but then force restarts whilst trying.
I then tried the Superuser app by Chainsdd, and I make a little progress?
First, when I try to upgrade, it asks for root from SuperSU and Superuser. Since SuperSU came with the busybox package, I can't uninstall it.
When I first go to the updater, it shows me this: (See attachment 1, I can't do links :S)
After I upgrade it, I am left with this screen: (see attachment 2)
It looks like it reverts back to su v .98 from 1.02?
Either way, as soon as I hit lets do it again, the phone restarts. Did I screw up the unlock/root somehow? In the top left of my fastboot screen it shows ***TAMPERED*** and ***UNLOCKED***
I am using CWM 6.0.2.1
If I do it right when I reboot my phone it usually asks correctly
Thanks again for the help so far!
Click to expand...
Click to collapse
It's difficult for me to troubleshoot when i haven't had to fix this problem since december haha.
The tampered, and unlocked is standard that is what it shows for everyone who unlocked the boot-loader.
So let me get this straight,
Do me a favor, un-install Superuser, download RootChecker from the market by JoeyKrim, And run it, what does it say?
->When you run it, did it ask for permission from SuperSU?
With just the SuperSU installed, if you run a program that requires root permission (For example, RootChecker), Nothing shows up asking if you want to Allow/Deny?
->When you open SuperSU to update the binary, it fails to update and restarts the APP?
With the SuperSU/BusyBox package flashed, when you install Superuser from the android market and try to update the binary, it *appears* to revert back to an older version of the binary?
-> After updating the binary through Superuser (despite the appparent reversion), if you un-install Superuser, and try to run RootChecker, does it work?
Sorry, i know it is a lot and i'm not much help, i'm troubleshooting blindly and from a distance haha.
xDexter said:
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
Click to expand...
Click to collapse
you need to install a kernel with /system writing enabled. Such as lk's or cubed
htc has a line wrong in their code and it makes it so that /system cant be edited while booted into android, only while in recovery. Installing a kernel that fixed this bug will let you use supersu from the play store and other apps such as adfree which need to edit system files to function
Bigandrewgold said:
you need to install a kernel with /system writing enabled. Such as lk's or cubed
htc has a line wrong in their code and it makes it so that /system cant be edited while booted into android, only while in recovery. Installing a kernel that fixed this bug will let you use supersu from the play store and other apps such as adfree which need to edit system files to function
Click to expand...
Click to collapse
Yeah this is what I figured out too.
Sent from my HTC6435LVW using XDA Premium HD app
Even with a writeable kernel SuperSu gives a hiccup at first. Download SuperUser, update the binary of SuperSu, then uninstall SuperUser. SuperSu will be fine after that.
orangechoochoo said:
Even with a writeable kernel SuperSu gives a hiccup at first. Download SuperUser, update the binary of SuperSu, then uninstall SuperUser. SuperSu will be fine after that.
Click to expand...
Click to collapse
I never had an issue with supersu
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
I never had an issue with supersu
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Quite a few of us running a version of Supercharged Hatka had problems when they switched to SuperSu,but now they switched back to SuperUser and the problem hasn't reared its head.
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices and has clocked over 16 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
- Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Are you having fastboot driver issues? You can find fastboot drivers in many places, but the easiest way is probably just installing the Android SDK.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
Download
flo (Nexus 2013 Wi-Fi): CF-Auto-Root-flo-razor-nexus7.zip
deb (Nexus 2013 LTE): CF-Auto-Root-deb-razorg-nexus7.zip
Very happy to see you here too. Thx for your work.
Sent from my Nexus 7 using xda premium
Chainfire said:
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
Click to expand...
Click to collapse
For Flo, bootloader is volume down and power.
Newbie question - Once rooted with this method will I still get OTA updates? If so will it retain root?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Yes, you will get OTA
BTW, you will get OTA's also with custom recovery like CWM, but you cannot install it via custom recovery. For that you need Stock recovery
User_99 said:
Yes, you will get OTA
BTW, you will get OTA's also with custom recovery like CWM, but you cannot install it via custom recovery. For that you need Stock recovery
Click to expand...
Click to collapse
Thats not true... I got the 4.3.1 update for my deb and had root+twrp. After hit install it boot to twrp and installs the ota after boot up root is still there. No Problems here
Great that it works fine for you!
But that will work not for all customers. Some reported that after they recived and downloaded the OTA they got an error while installation in custom recovery.
I rooted my Nexus 7c LTE..
now i can see an unlock logo in startup... anywhere i can remove it?
thanks!
No, that's normal for unlocked bootloader. Only not shown when you close the bootloader again.
Thank you!
any idea how to close the bootloader?
http://www.wugfresh.com/nrt/
Nexus Toolkit - easy way to lock the bootloader. But, for Root, you need an Unlock Bootloader...
decide...
THANKS!!!
is the auto-root still working on new kit-kat update?
ritz_cal78 said:
is the auto-root still working on new kit-kat update?
Click to expand...
Click to collapse
Nope. Already tired twice.
so if i want to install TWRP recovery, i have to flash it after i install CF-auto root?
how do i get to the steps u mentioned using mac?
xdviper said:
Nope. Already tired twice.
Click to expand...
Click to collapse
It worked perfectly for me first try. I should say that I had just rooted my Nexus 7 LTE with Chainfire's method before I updated my N7 OTA. After the update, root was lost. I simply went through the steps again and re-rooted it. I should also state that I did not lose any of my data on during the 2nd root.
I'm going to donate to Chainfire.
same here, only difference,
I came from a factory image fash. Auto root worked
Send from the N7²
Will this work a stock n7 2 running KK?
xbs said:
Will this work a stock n7 2 running KK?
Click to expand...
Click to collapse
Worked OK for me.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Below you will find my procedure to root the SM-J727P Galaxy J7 Perx / MSM8953
This procedure has only been tested on J727PVPU1AQB9 firmware. It may work for future releases or it may not.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.
This took some doing and was a tough nut to crack. I don't own this device and much thanks goes to those that stuck with it in the testing phase, without whom it would not have even been possible. Credits below.
To see how we got here and before asking any questions click this link: https://forum.xda-developers.com/galaxy-j7/help/root-sm-j727p-galaxy-j7-perx-galaxy-j7-t3598117
DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Instructions:
◘ 1. Download the files below:
J727P-SuperSU-v2.79-SR3_rooted_boot_AQB9
ODIN 3.12
SAMSUNG_USB_Driver_for_Mobile_Phones
◘ 2. Install the USB driver and ODIN to Windows.
◘ 3. Boot your device to RECOVERY mode then select FACTORY RESET. THIS WILL WIPE YOUR DEVICE AND YOU WILL LOSE ALL DATA. (This procedure is required to remove encryption or your device won't boot)
◘ 4. From RECOVERY, IMMEDIATELY Boot your device to DOWNLOAD mode then connect your USB cable. (DO NOT LET YOUR DEVICE REBOOT NORMALLY OR YOUR DEVICE WILL RE-ENCRYPT)
◘ 5. Run ODIN and place the J727P_SuperSU-v2.79-SR3_rooted_boot_AQB9.tar file as is in the AP slot. Don't change any options and hit START.
◘ 6. Wait for the device to flash and reboot.
◘ 7. Install the SuperSU apk from Play store and you should be rooted.
◘ 8. Have fun!
Credits: ME, @Borams @Project89Odin @Chainfire and special thanks to @RS.85243
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU
I got the encryption error on reboot. I then did the reset it required and rebooted. I installed supersu just to see what it would say. It says root not properly installed in root checker, so I guess that means its there but I guess its a binary issue? Is there something that I didnt do correctly or a step I missed?
scbcskin said:
I got the encryption error on reboot. I then did the reset it required and rebooted. I installed supersu just to see what it would say. It says root not properly installed in root checker, so I guess that means its there but I guess its a binary issue? Is there something that I didnt do correctly or a step I missed?
Click to expand...
Click to collapse
Whoops glad you pointed that out, forgot to include that step!
I factory reset, booted directly to download mode, flashed tar, phone rebooted. I installed Supersu but still not rooted.
scbcskin said:
I factory reset, booted directly to download mode, flashed tar, phone rebooted. I installed Supersu but still not rooted.
Click to expand...
Click to collapse
When you open the SuperSU app does it complain about no binary installed?
ashyx said:
When you open the SuperSU app does it complain about no binary installed?
Click to expand...
Click to collapse
It sure does!!
scbcskin said:
It sure does!!
Click to expand...
Click to collapse
Strange, it works perfectly on Marshmallow. Looks like we're going back to the old method of manually pushing su.img to data!
Will update shortly.
Have you tried rebooting again to see if works after that?
Just did a reboot and same deal.
scbcskin said:
Just did a reboot and same deal.
Click to expand...
Click to collapse
I think I've just found the issue. Try this version instead, no need to format, just install with ODIN.
https://www.androidfilehost.com/?fid=961840155545567256
.
If you grant root permission before opening supersu apk but after downloading it, it does not ask to update binary with first op build
Project89Odin said:
If you grant root permission before opening supersu apk but after downloading it, it does not ask to update binary with first op build
Click to expand...
Click to collapse
Say again. Can you explain in more details, not sure I understand?
After process in op, after downloading supersu do not open it, download something that requires root and grant it. It will grant without ever opening supersu. I granted flashfire and flashed sr3 just to make sure. After reboot i opened the supersu app and it asks for no update. Although disabling knox did not work for me.
Project89Odin said:
After process in op, after downloading supersu do not open it, download something that requires root and grant it. It will grant without ever opening supersu. I granted flashfire and flashed sr3 just to make sure. After reboot i opened the supersu app and it asks for no update. Although disabling knox did not work for me.
Click to expand...
Click to collapse
OK I see. Can you do me a favour and test the updated version?
First delete su.img from /data or just unroot from SuperSU settings then reboot to download mode and install the new version. Your device should auto re-root.
https://www.androidfilehost.com/?fid=961840155545567256
ashyx said:
I think I've just found the issue. Try this version instead, no need to format, just install with ODIN.
https://www.androidfilehost.com/?fid=961840155545567256
.
Click to expand...
Click to collapse
Root has been achieved my friend. At first a flashed it and when it booted I got the encryption error. I just pulled the battery and then tried to boot into recovery. Instead of going in recovery it booted like normal. I installed Supersu and it got stuck attempting to disable Knox. Well after about 2 minutes or so of watching that I just went to root checker and there it was. I think I can speak for everyone when I say job well done!!!:good:
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Quick question, must you have custom recovery in order to install Xposed or is it just a suggestion?
After deleting su in /data andfull unroot, flashed newer build and supersu reports no binary, not even one to update, no root
scbcskin said:
Root has been achieved my friend. At first a flashed it and when it booted I got the encryption error. I just pulled the battery and then tried to boot into recovery. Instead of going in recovery it booted like normal. I installed Supersu and it got stuck attempting to disable Knox. Well after about 2 minutes or so of watching that I just went to root checker and there it was. I think I can speak for everyone when I say job well done!!!:good:
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Quick question, must you have custom recovery in order to install Xposed or is it just a suggestion?
Click to expand...
Click to collapse
Thanks for confirming. OP updated.
You can use Flashfire to install Xposed.
ashyx thank you for your efforts. Thanks to everyone else that helped as well. Guess what I just ordered. Can't wait to get my new phone and root, install viper4android. Both are a must for me and I never own a phone I can't have both on.
scbcskin said:
Just did a reboot and same deal.
Click to expand...
Click to collapse
When the reboot is repeated,
please flash the original firmware to odin
and try again from the beginning.
from CIAO7
after unrooting, repeating format is required to reroot. Works flawless. Thankyou again. Looking forward to a fully functional twrp now!!
Project89Odin said:
Thankyou again. Looking forward to a fully functional twrp now!!
Click to expand...
Click to collapse
It's next on my hit list. Just need to figure out why the source built kernel doesn't boot.
Now that root is achieved there's more chance of finding out what's going on, so I'll be calling on you guys again at some point for logs.