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.
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.
Hi,
I am trying to root my SGS2 and I haven't rooted a phone before. I am using CF-Root and have followed the instructions on:
http://forum.xda-developers.com/showthread.php?t=1103399
That all seemed to work and when I boot my phone I get the yellow triangle, etc. But, according to Root Checker my phone isn't rooted and if I try to run an app that requires root then it doesn't work.
Do I need to do anything other than flashing the CF-Root tar in Odin to root the phone?
I used the following kernel (my phone was previously using LPC so I assume this is correct):
CF-Root-SGS2_BU_VOD_LPC-v5.4-CWM5.zip
I have searched and can't find any answers so hopefully someone here can help.
Thanks,
Jon
flash the same again an this time ull b rooted
as rock23 said reflashing should solve that issue. If you are missing the SU specifically. Then you can install it from the market.
Thanks for the quick replies. I flashed again but it's still not working. Just in case it helps, I flashed a third time but still no luck. Odin seems to run properly and reports success. But Root Checker says:
Superuser: Not found
Busybox: Not found
Su location: Not found
Sudo location: Not found
And if I ran an app that needs root then I am not prompted to allow it, etc, and the app doesn't work. Any suggestions for what I should try?
Install su frm market and update it if not.c an post
Sent from my GT-I9100 using xda premium
Sorry, I might be misunderstanding this, but I can't find su on the market. There are apps like superuser, etc, but I can't find anything that delivers su. Shouldn't that have come with CF-Root or do I install it from somewhere else?
dorsetjon said:
Sorry, I might be misunderstanding this, but I can't find su on the market. There are apps like superuser, etc, but I can't find anything that delivers su. Shouldn't that have come with CF-Root or do I install it from somewhere else?
Click to expand...
Click to collapse
Install super user from here
https://play.google.com/store/apps/details?id=com.noshufou.android.su&feature=search_result
Thanks. I have now installed super user but 'su' is still missing.
In super user preferences it says "Su binary vnull" so I tapped that to get an update. Super user says "New version of su binary found" and I click "Update" but that fails with the error "Failed to find currently installed su binary".
I can't see how I get this su binary.
Flash a different CF root firmware .
Ignore root checker .
Reboot and you should have CWM apk open that and if it works check recovery works .
jje
Thanks, I think I'll have to try a different CF Root kernel because the one that's meant to be for my Kernel definitely isn't installing some of the things that I think it should.
dorsetjon said:
Thanks, I think I'll have to try a different CF Root kernel because the one that's meant to be for my Kernel definitely isn't installing some of the things that I think it should.
Click to expand...
Click to collapse
I dont thik you have to flash different again,
have you opened atleast once the Supe SU application, there is a binary updatin, at your first opening, may be alright after that and a reboot.
I am currently using LPC cf-root on my LP8 rom without any treble....
The weird thing is that I couldn't even find SuperSU on the phone after flashing with CF-Root...I definitely had an insecure kernel but the other things needed for root didn't seem to be there (or at least didn't work). I gave up with CF-Root and tried the root method described on the following link and that worked first time (although wifi then broke until I changed to a static IP):
http://forum.xda-developers.com/showthread.php?t=1501719
dorsetjon said:
Thanks. I have now installed super user but 'su' is still missing.
In super user preferences it says "Su binary vnull" so I tapped that to get an update. Super user says "New version of su binary found" and I click "Update" but that fails with the error "Failed to find currently installed su binary".
I can't see how I get this su binary.
Click to expand...
Click to collapse
I had this problem. No superuser installed after flashing. Couldn't update su binary with superuser. Here is how do you solve this issue:
1) install superuser from market
2) flash manually su binary with cwm http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
3) open superuser go through prefences and check updates if any.
Sent from my GT-I9100 using Tapatalk 2
OK, can anyone tell me what stage I'm at here?
I have - Stock OTA ICS, Hboot 1.53.0007, Software no 3.28.401.1, Kernel 3.0.16-ge733189
on a UK (GSM presumably) Evo 3d.
Unlocked via HTC's unlocking guide - successful, showing Unlocked at boot screen.
S-ON still showing...
Have recovery - Revolutionary CWM v4.0.1.4
Somewhere along the line, Superuser got installed.
But any app that needs root tells me I'm not rooted, for example System Tuner, everything needing root is greyed out.
Superuser shows nothing in the Apps list, or the log, and has never prompted for an app to be added. The "Temp unroot" and "OTA survival" buttons return errors.
I can browse root using ES File Explorer, but I didn't notice if I could do that before...
I feel I must be close here, but what do I need to do?
Thanks
Get the app root checker it"ll tell ya
Hit the thanks button
e3d4eva said:
Get the app root checker it"ll tell ya
Hit the thanks button
Click to expand...
Click to collapse
I found two apps called Root Checker, and they both say I'm not.
The second one told me "BusyBox" and "Sudo" were not found.
Any ideas where I should go from here?
Thanks
lurkist said:
I found two apps called Root Checker, and they both say I'm not.
The second one told me "BusyBox" and "Sudo" were not found.
Any ideas where I should go from here?
Thanks
Click to expand...
Click to collapse
Superuser is installed per your op. On the info page, click tap to update and have it try to install an updated su binary. No promises, but that's worked for me in the past.
Sent from my ICS 3VO with Tapatalk 2
coal686 said:
Superuser is installed per your op. On the info page, click tap to update and have it try to install an updated su binary. No promises, but that's worked for me in the past.
Sent from my ICS 3VO with Tapatalk 2
Click to expand...
Click to collapse
Didn't even realise that was clickable!
Anyhow, Installed version showed red, tapped update.
Fixing database - okay
Unpacking sutools - okay
Checking current install path - /system/bin/su
Downloading new bianry - okay
Gaining root access - FAIL!
Try again? Yes, several times but same thing.
Just realised my HBOOT version may not be supported by Revolutionary. Can I unflash this? And flash something that does support 1.53.0007?
I realise now from other threads that what I'm trying to do is essentially impossible at this point (root while keeping stock ICS and HBOOT).
/give_up.
HAHAAA!! Rooted! Just re-installed Superuser, works now. Wooh! Knew I was close!
Noone knew how close you were boom
Sent from my PG86100 using xda premium
I'm trying to install BusyBox on my HTC Droid DNA. I rooted the phone using the Jcase method.
I'm choosing the "normal install" method for Busybox and it keeps saying unsuccessful.
Question: Is it safe to try the "smart install" method? Has anyone else installed Busybox successfully?
What I'm trying to do: Just be able to do Linux stuff like edit files, etc. I'm told I need this software.
Thanks.
Joe
Ok, I think it worked. I booted into recovery, then used a .zip file that also contains SuperUser SU from a forum posting on rooting the DNA. I am almost 100% sure this was the file (I forgot to remember the link, but this was in my history):
http://www.mediafire.com/?es35lyioe8hxbxh
commandlinekid said:
I'm trying to install BusyBox on my HTC Droid DNA. I rooted the phone using the Jcase method.
I'm choosing the "normal install" method for Busybox and it keeps saying unsuccessful.
Question: Is it safe to try the "smart install" method? Has anyone else installed Busybox successfully?
What I'm trying to do: Just be able to do Linux stuff like edit files, etc. I'm told I need this software.
Thanks.
Joe
Click to expand...
Click to collapse
Did you get this officially fixed then?
Sent from my HTC DNA.
Technically, yes. It is installed.
wget isn't working, and I need to play with it, but yes, Busybox is on now.
BigRed35m said:
Did you get this officially fixed then?
Sent from my HTC DNA.
Click to expand...
Click to collapse
commandlinekid said:
Ok, I think it worked. I booted into recovery, then used a .zip file that also contains SuperUser SU from a forum posting on rooting the DNA. I am almost 100% sure this was the file (I forgot to remember the link, but this was in my history)
Click to expand...
Click to collapse
Do you still have the zip that you downloaded?
That link is broken, says that the file was deleted.
I'm running into the same problem, with either crashing my phone or saying that it failed.
You need a kernel that allows write to system.
D
.
Sent from somewhere irrelevant.
dsb9938 said:
You need a kernel that allows write to system.
Click to expand...
Click to collapse
I dunno... I kinda like the stock kernel.
Do I really need to change kernels in order to install BusyBox through recovery mode?
I'm sure there are other kernels that are a lot better than stock, but I'm not super adventurous. Just rooting was a lot, but I really wanted to have more functionality in Tasker and Titanium Backup. Once I get BusyBox I think I'm done for a while.
andyd273 said:
I dunno... I kinda like the stock kernel.
Do I really need to change kernels in order to install BusyBox through recovery mode?
I'm sure there are other kernels that are a lot better than stock, but I'm not super adventurous. Just rooting was a lot, but I really wanted to have more functionality in Tasker and Titanium Backup. Once I get BusyBox I think I'm done for a while.
Click to expand...
Click to collapse
There is stock with system write. You can do whatever you want in recovery, but installing it normally, or updating it, or updating su will not work.
D
.
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