Related
Ok so I am having a strange issue here. I tried to root my buddy's incredible using the newest version of unrevoked. It went through successfully but I noticed when going into the bootloader that it still states S-ON. Also, when I click on Recovery, it takes me to a black screen with white lines on the side. I have tried flashing the recovery multiple times by using the PB31IMG.zip method to no avail. I am guessing at this time the root did not take. So when I try to use Unrevoked again it tells me that root is unsuccessful, my software may be too new (or something to that affect. I have tried it 3 more times, no dice. Just for ****s, I downloaded terminal and it works, I can get superuser access. I tried flashing a recovery at that point with the flash_image method and that doesnt work either, it says image not found or something like that. I dont know if it rooted and didnt turn S-OFF, or if it isn't rooted at all. I tried downloading and just going back to an unrooted stock rom and it said that the software version is older and failed. I have been at it for hours. Please someone help. Thanks in advance.
Hello list,
I have been trying to root my Nexus S with the 2.3.3 update but I've been unsuccessful. I have tried "Allgamer's" GRH78 and a couple of others on youtube but I think the problem is my laptop (windows 7 32-bit) wont recognize the phone. Is there something I'm missing? Has anyone rooted their 2.3.3 phone, and if so can you send a link or PM me so I can figure this out? I eventually want to flash the Cyanogenmod 7 so any help at all would be greatly appreciated.
When I had my HD2 I installed HSPL and flashed all types of ROM's without issue. My Nexus S is acting like my ex......
Thanks,
Rich
Madmax0609 said:
Hello list,
I have been trying to root my Nexus S with the 2.3.3 update but I've been unsuccessful. I have tried "Allgamer's" GRH78 and a couple of others on youtube but I think the problem is my laptop (windows 7 32-bit) wont recognize the phone. Is there something I'm missing? Has anyone rooted their 2.3.3 phone, and if so can you send a link or PM me so I can figure this out? I eventually want to flash the Cyanogenmod 7 so any help at all would be greatly appreciated.
When I had my HD2 I installed HSPL and flashed all types of ROM's without issue. My Nexus S is acting like my ex......
Thanks,
Rich
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=875875
Will that work with 2.3.3? And what the hell am I doing wrong that I cant get my laptop to recognize my phone???
Madmax0609 said:
Will that work with 2.3.3? And what the hell am I doing wrong that I cant get my laptop to recognize my phone???
Click to expand...
Click to collapse
Well, you can try to install this driver: http://mazodude.comze.com/files/drivers.rar
That link takes me to a blank page....??? Have you rooted your Nexus and was it at 2.3.3 when you started?
Thanks, and sorry for all the questions.....I'm just trying to get this resolved.
Madmax0609 said:
That link takes me to a blank page....??? Have you rooted your Nexus and was it at 2.3.3 when you started?
Thanks, and sorry for all the questions.....I'm just trying to get this resolved.
Click to expand...
Click to collapse
Did you install the Android SDK? If so, I apologize as I'm not familiar with the shortcut commands for windows but you should try this:
Code:
*File path to your android sdk/tools folder*\fastboot devices
If you get a result like
Code:
################# fastboot
then your phone is being recognized, if not other troubleshooting stepsmight have to be taken.
Havent tried that yet. I will give it a shot.
Thanks!
was having the same issue with fastboot, use these drivers from pda.net
http://www.junefabrics.com/android/download.php
Having the same problem. I've tried PDAnet and am currently updating (again) SDK, but I can't get the fastboot or adb to recognize the device, no matter how hard I try. For what it's worth, my bootloader was unlocked when I upgraded to 2.3.3 (via Clockword Mod), and the unlock status seems to have been preserved. It still says "unlocked," and boots with the open padlock.
Sorry for the double post, but I posted as I was working on it. What worked for me: I had a 2.3.3 stock image booted from Clockwork. I didn't have root permissions with the stock.
The new stock (is it technically a ROM, or is a ROM just Cyanogen, Bionix, etc., like awesome developers create?) preserved the unlocked bootloader (which I've not re-locked, because I never cared about the padlock boot), but not the root. So I was left with a stock 2.3.3 with an unlocked bootloader.
I tried everything to get my phone recognized via USB under the SDK/adb, but couldn't. I adbed and fastbooted devices, uninstalled and reinstalled PDAnet, even deleted and then redownloaded and reinstalled java, SDK, *and* drivers. To no avail.
The first time I rooted, though, I used the one-click method in the MoDaCo forums, by . . . Paul(?). I think that's his name. It's a simple zip file. So I unzipped to my desktop. Which gave me a folder with the GRI40 Nexus S superboot. I disconnected my phone, shut it off, then held the volume up and power keys until it booted into the fastboot bit. Once it was in fastboot (with the green Android and the orange text up top and the blue text options along the side), I reconnected the USB, then just double-clicked the .bat file in the superboot folder.
That gave me root. I verified via rootchecker, and the moment I confirmed root, I went to Clockwork, reflashed Clockwork Mod Recovery, and did a complete back-up. That's where I am now. Not sure where I'm going from here, but I have 2.3.3 GRI40 root with baseband i9020xxb1, and that's how I did it.
willentrekin said:
Sorry for the double post, but I posted as I was working on it. What worked for me: I had a 2.3.3 stock image booted from Clockwork. I didn't have root permissions with the stock.
The new stock (is it technically a ROM, or is a ROM just Cyanogen, Bionix, etc., like awesome developers create?) preserved the unlocked bootloader (which I've not re-locked, because I never cared about the padlock boot), but not the root. So I was left with a stock 2.3.3 with an unlocked bootloader.
I tried everything to get my phone recognized via USB under the SDK/adb, but couldn't. I adbed and fastbooted devices, uninstalled and reinstalled PDAnet, even deleted and then redownloaded and reinstalled java, SDK, *and* drivers. To no avail.
The first time I rooted, though, I used the one-click method in the MoDaCo forums, by . . . Paul(?). I think that's his name. It's a simple zip file. So I unzipped to my desktop. Which gave me a folder with the GRI40 Nexus S superboot. I disconnected my phone, shut it off, then held the volume up and power keys until it booted into the fastboot bit. Once it was in fastboot (with the green Android and the orange text up top and the blue text options along the side), I reconnected the USB, then just double-clicked the .bat file in the superboot folder.
That gave me root. I verified via rootchecker, and the moment I confirmed root, I went to Clockwork, reflashed Clockwork Mod Recovery, and did a complete back-up. That's where I am now. Not sure where I'm going from here, but I have 2.3.3 GRI40 root with baseband i9020xxb1, and that's how I did it.
Click to expand...
Click to collapse
Are you on a PC or a mac?
PC
Loaded up Cyanogen. Seems okay. Tried adding the Honity kernel, but that seems to bugger everything up.
willentrekin said:
PC
Loaded up Cyanogen. Seems okay. Tried adding the Honity kernel, but that seems to bugger everything up.
Click to expand...
Click to collapse
Cyanogen is nice as it adds some features but if you've been living without them you might never notice having them lol. More people need to buy macs <.< I can help anyone get root on a mac >.>
I'm noticing that. It seems like kernels are what introduce problems for me; I've run Bionix and Cyanogen without issue, but as soon as I load up a kernel, I start getting force closes in any app that requires superuser permissions. I've discovered that managing the apps to clear their data/caches can help, but I'd like to find a more stable set up.
willentrekin said:
I'm noticing that. It seems like kernels are what introduce problems for me; I've run Bionix and Cyanogen without issue, but as soon as I load up a kernel, I start getting force closes in any app that requires superuser permissions. I've discovered that managing the apps to clear their data/caches can help, but I'd like to find a more stable set up.
Click to expand...
Click to collapse
When you flash the kernel run fix permissions before you reboot. For me cfs kernels.
I downloaded and installed the Incredible S Beta rom that is listed somewhere on this site for the Incredible. My issue is I want to revert to another ROM, HOWEVER, now my Superuser keeps force closing and will not allow ROM Manger to flash. I try to reboot in HBoot and ONLY get the start-up screen when doing Vol- and Power. Any suggestions on how to get into Hboot or another way to flash a different ROM when SuperUser will NOT allow permissions or Rom Manger wont reboot into Recovery (because superuser forecloses and wont let me flash Rom Manager
BTW-The Incredible S Rom works great...just NO pic/video (As it states in the description.)
Editing to take away some of the clutter (my clutter)
I am not sure what happened. As stated above once the ROM (which is great!) was installed, Rom Manager was no longer granted superuser access (was trying to reboot into recovery via Rom Manager). It wiped the Recovery Version from the phone and would not let me flash a new recovery. Everything else seemed to work fine (superuser permissions, ie. SetPC, etc.)
I tried plugging the phone in and reflashing Unrevoked directly to the phone. Unrevoked stated the root access was denied and asked if I had a "newer firmware".
I also tried uninstalling superuser (to only reinstall and see if it fixed the issue), however, Superuser was included in the ROM and would not let me uninstall.
The only way I was able to get back into Recovery was to re-run Unrevoked Flash and UNPLUG the phone when Unrevoked managed (somehow) to get the phone into bootloader. From there Clockwork ran fine.
Installed a different ROM and all is good.
The only thing I can think of is: In some post regarding the Incredible S being not branded to a certain carrier. When the ROM was installed, it showed "EVDO" in the notification bar (which leads me to believe it is for Sprint), I am not sure how THAT would affect anything being on a Verizon phone...again..only thing I can think of.
Just reboot the phone directly into recovery.
evilkorn said:
Just reboot the phone directly into recovery.
Click to expand...
Click to collapse
It wont let me. I dont think...I tried the Vol-+power...nothing..just reboots. Tried booting into recovery via Rom Manager, but since superuser no longer is granting persmission it wont even do that...is there another way to flash a different ROM?
I just tried reflashing Unrevoked directly to it...it failed to access boot, something about the firmware being too new...???
I dont know anything about your device but maybe your root is broken? Re root and re install superuser goodluck.
Sent from my X10a using XDA App
shahkam said:
I dont know anything about your device but maybe your root is broken? Re root and re install superuser goodluck.
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Oh, HTC Incredible.
I went into Rom Manager (and against ALL I have read) am trying to instal and reboot using Rom Manager...instead of going into recovery mode...phone is just sitting here "thinking" right now...nothing YET about being denied root access...fingers crossed...
OK, not sure this was SMART...Hooked phone back up to PC, ran Unrevoked flash kit again...unplugged phone once it came up in recovery...have access NOW to CLockwork...wiped data..installing different ROM as I type...hopefully this will work..
YAY...close call...sorry to waste everyones time..lol. So..If your installing the INcredible S Rom onto your incrediable..I have learned two things...1.) Unrevoked failed to push recovery due to the firmware...2.) you may lose superuser ability....
You would get more help if your thread title would actually be helpful.
Include your phone model, the rom you tried, and what happened (SuperUses FCs[forcecloses]).
Caps, lots of exclamation marks and a title like ZOMFG I NEED HELP, usually deters skilled people from threads like this.
Dark3n said:
You would get more help if your thread title would actually be helpful.
Include your phone model, the rom you tried, and what happened (SuperUses FCs[forcecloses]).
Caps, lots of exclamation marks and a title like ZOMFG I NEED HELP, usually deters skilled people from threads like this.
Click to expand...
Click to collapse
Good point...just paniked. Someone can close this or change title.
You can do it yourself through the edit button. Make it accurate so people who have the same problem and search for it will find your thread and your solution.
I need to root. After bricking and using odin to get back to stock, my phone wont root again. why, you ask? well, because the phone will not connect to the computer via adb interface. I have usb debugging on, I connect my phone, it installs to the computer, but adb wont work for me. neither will super one click. is there a way to root without using a computer? maybe through terminal emulator? or an app that will work? I know z4 wont work i tried it. someone please give me some advice here. im on xp, i have tried different drivers, tried rebooting the phone, nothing works. please help.
sidekick_fanatic said:
I bricked my sk4g due to bad rom flash. I wanted to try one click unbrick, but couldnt get it to work on my computer. So my only other option was to odin it back to stock. before bricking, i had rooted it with superoneclick. i immediately tried superoneclick after odin. several different things would happen. one, it would go through the whole process and say i was rooted, but root checker pro would say i didnt have root. two, superoneclick would tell me my device was unreadable. i would ignore it and it would go through, but still not rooted. three, superoneclick would hang after killing the adb server. I then attempted to root manually. I downloaded rageagainstthecage and atempted to push it through a command prompt. I have sdk installed and all the other necessary things for a manual root. but when i typed adb devices in command prompt, the list came up empty. i deleted all the drivers, plugged the phone back in, and let the drivers reinstall several times, but my device still will not connect to the adb interface. the drivers are installing, and the usb is connecting through storage mode and firmware update mode, but not through adb no matter what i do. i am on windows xp and i do not have another computer to use. someone please tell me how to root another way or possibly flash a rooted rom through odin. thank you.
Click to expand...
Click to collapse
Try this and post results:
ODIN
Get KD1 or KG2 Firmware
Then visit..
-x]Trunks[x- said:
HERE and HERE
Click to expand...
Click to collapse
And now you should successfully rooted on stock firmware
some of those pages I have already been to. the stock rom you linked is the rom I used to odin my phone. some of those pages were confusing to me, and as far as cwm recovery goes, need root to change recovery binary. before bricking, I had root and cwm. what i need (sorry to sound like such a noob) is a step by step in this thread. please dont post links to me unless they apply to my particular situation. superoneclick, odin, cwm, these are all things i already know how to do. my question is how can i root if my phone wont connect to my pc through adb?
also, odin still recognizes my phone. i can still brick my phone and odin it all day long if i want to. I used the tutorial in one of the links you posted and downloaded the odexed stock rom and followed the tutorial exactly. the phone works, but i cant root it. there has to be someone who can help me figure this out.
bumping this thread hoping someone out there has some useful info for me. thanks
Did you turn on USB debugging?
settings->applications->development->USB Debugging
yes I did. adb is not connecting.
basically what I need is a way to flash a rooted rom through odin or another way to root without using adb. possibly without connecting to the computer, like through terminal emulator or something?
what if I added superuser, busybox, and su to my stock odin rom that I have and just odin again? would that give me root?
what if I added superuser, busybox, and su to my stock odin rom that I have and just odin again? would that give me root?
You can root the phone fine do it after the odin
Sent from my SGH-T839 using XDA App
I think I should start a new thread so I can be a little more concise. I can see that at least one person here completely does not understand what I am talking about.
No just edit the og post
PM FOR PSN NEED THE RUN PSN
xtrem88, do you understand what I am saying? I bricked my phone and had to use odin to get it back to stock. now my phone will not root. superoneclick runs, but for some reason doesnt configure root properly. i end up with superuser installed, but no root. when i try to root through command prompt, i type in adb devices and the list comes back empty. what I think I want to do at this point is odin a rooted rom.
Ohhh ok now i get it you got to. Odin it again and do not connect storage
PM FOR PSN NEED THE RUN PSN
I am updating the firmware through kies mini right now, since the firmware i odin'd wasnt the latest. I just unmounted and removed the sd card. are you saying that was the problem before?
Yeah dont use the sd card
PM FOR PSN NEED THE RUN PSN
I got it rooted. Im on KD1 firmware, but at least I am rooted. I feel like a simpleton, though. Wait till I tell you what the problem was. I was using superoneclick the whole time, and it wasnt working. I re-read the tutorial for the umpteenth time to see if I had missed anything, and it finally dawned on me that each time root had failed, I hadnt rebooted my device after running superoneclick. I just ran superoneclick, it did its thing, I disconnected and rebooted, and voila, I have root. I verified root by going to superuser and updating the su binary. thats how i knew it failed before. each time i would try to update su, it would say obtaining root access and it would fail. this time when it said obtaining root access, superuser asked for permission and i knew I had root. I am so ticked at myself for spending so much time doing it wrong, but so happy that I finally did it right lol. the whole time I thought odin was causing the problem, but im glad to know it wasnt. now i know if i brick my phone again, i can just odin and root and the phone will be back to running and rooted in like 10 minutes.
Lmao
PM FOR PSN NEED THE RUN PSN
sidekick_fanatic said:
I got it rooted. Im on KD1 firmware, but at least I am rooted. I feel like a simpleton, though. Wait till I tell you what the problem was. I was using superoneclick the whole time, and it wasnt working. I re-read the tutorial for the umpteenth time to see if I had missed anything, and it finally dawned on me that each time root had failed, I hadnt rebooted my device after running superoneclick. I just ran superoneclick, it did its thing, I disconnected and rebooted, and voila, I have root. I verified root by going to superuser and updating the su binary. thats how i knew it failed before. each time i would try to update su, it would say obtaining root access and it would fail. this time when it said obtaining root access, superuser asked for permission and i knew I had root. I am so ticked at myself for spending so much time doing it wrong, but so happy that I finally did it right lol. the whole time I thought odin was causing the problem, but im glad to know it wasnt. now i know if i brick my phone again, i can just odin and root and the phone will be back to running and rooted in like 10 minutes.
Click to expand...
Click to collapse
Soo.....this entire time the process I posted didn't work due to a simple reboot after superoneclick....*crickets*....
LMAO!!!! Glad you got your problem solved
Sent from my SGH-T839 using XDA Premium App
http://forum.xda-developers.com/showthread.php?t=2699089&page=40
I tried using that method to root my phone, but Super SU just won't install binaries. First time around it just wouldn't work, after a few tries I unrooted my device and started over. I got the same message, "Unable to install, reboot"
Then after that it said something like "If you upgraded to 4.3 then reroot" Something like that. Which is weird because I have 4.4.2.
What's going on? I tried Superuser but when I tried installing the binaries it crashed when it was doing a software update twice so I had to hold down on volume up and the power button to reboot it on both occasions.
Also, how do I do an ADB Reboot? What's the easiest method? I tried doing that on my PC but it keeps saying device not detected Maybe I'm not setting up the program for that right? Yes, Developer Options and USB Debugging are enabled.
Yes my M8 is from Verizon. Is there another method for one-click rooting?
Anyone?
CannedBullets said:
http://forum.xda-developers.com/showthread.php?t=2699089&page=40
I tried using that method to root my phone, but Super SU just won't install binaries. First time around it just wouldn't work, after a few tries I unrooted my device and started over. I got the same message, "Unable to install, reboot"
Then after that it said something like "If you upgraded to 4.3 then reroot" Something like that. Which is weird because I have 4.4.2.
What's going on? I tried Superuser but when I tried installing the binaries it crashed when it was doing a software update twice so I had to hold down on volume up and the power button to reboot it on both occasions.
Also, how do I do an ADB Reboot? What's the easiest method? I tried doing that on my PC but it keeps saying device not detected Maybe I'm not setting up the program for that right? Yes, Developer Options and USB Debugging are enabled.
Yes my M8 is from Verizon. Is there another method for one-click rooting?
Click to expand...
Click to collapse
Probably the last thing you wanna do but if it wont work have you considered a factory reset? Usually solves most issues & are you S-OFF? Asking the S-OFF question because if you are you can flash a custom recovery and just flash the binaries. 0% failure rate with that as far as I know. About the ADB Reboot question, did you install the HTC Sync Manager so it would install the proper drivers and then removed the Sync program (not drivers)?
S1L3nTShaDoWz said:
Probably the last thing you wanna do but if it wont work have you considered a factory reset? Usually solves most issues & are you S-OFF? Asking the S-OFF question because if you are you can flash a custom recovery and just flash the binaries. 0% failure rate with that as far as I know. About the ADB Reboot question, did you install the HTC Sync Manager so it would install the proper drivers and then removed the Sync program (not drivers)?
Click to expand...
Click to collapse
I have not considered a factory reset. Also, what's S-OFF? I'm not sure what that is. Also do you mean the HTC Transfer Tool? I don't have that.
CannedBullets said:
I have not considered a factory reset. Also, what's S-OFF? I'm not sure what that is. Also do you mean the HTC Transfer Tool? I don't have that.
Click to expand...
Click to collapse
I don't really know how to explain what "S" is other than its security/signature verification(not sure on signature verification), when your phone is S-ON you can't flash any non verified rom or write to protected areas of your phone such as /system which is required for root, etc and I know it does more than that but I'm not 100% educated as to what it means yet though so can't give you a 100% accurate or complete explanation.
Now based off of what I just said and a little research i'm quite sure you actually require it for a permanent root solution such as SuperSU but could be wrong.
Anyways if you're interested in doing it go here: http://forum.xda-developers.com/showthread.php?t=2708628 and follow the instructions carefully. This also unlocks your bootloader which means you can install custom roms, kernels, flash scripts, apps, SuperSU for PERMANENT root, etc. In order to do these things you'll need to flash a custom recovery such as TWRP or CWM (Team Win Recovery Project & Clockwork Mod/Philz Touch). Afterwards it's quite simple from there on out, just be careful and research before you do anything I've suggested/stated. Also on the Sync Manager thing, what you need to do is install it from here http://www.htc.com/us/support/software/htc-sync-manager.aspx and then let it install the phone drivers for your M8 on your computer and then you need to uninstall it "HTC Sync Manager" from your computer in order to do the S-OFF process.
Please do be careful and get a good understanding before you do this though, re-read things a few times and make sure you're well aware of what it means and how to do it properly.
S1L3nTShaDoWz said:
Probably the last thing you wanna do but if it wont work have you considered a factory reset? Usually solves most issues & are you S-OFF? Asking the S-OFF question because if you are you can flash a custom recovery and just flash the binaries. 0% failure rate with that as far as I know. About the ADB Reboot question, did you install the HTC Sync Manager so it would install the proper drivers and then removed the Sync program (not drivers)?
Click to expand...
Click to collapse
S1L3nTShaDoWz said:
I don't really know how to explain what "S" is other than its security/signature verification(not sure on signature verification), when your phone is S-ON you can't flash any non verified rom or write to protected areas of your phone such as /system which is required for root, etc and I know it does more than that but I'm not 100% educated as to what it means yet though so can't give you a 100% accurate or complete explanation.
Now based off of what I just said and a little research i'm quite sure you actually require it for a permanent root solution such as SuperSU but could be wrong.
Anyways if you're interested in doing it go here: http://forum.xda-developers.com/showthread.php?t=2708628 and follow the instructions carefully. This also unlocks your bootloader which means you can install custom roms, kernels, flash scripts, apps, SuperSU for PERMANENT root, etc. In order to do these things you'll need to flash a custom recovery such as TWRP or CWM (Team Win Recovery Project & Clockwork Mod/Philz Touch). Afterwards it's quite simple from there on out, just be careful and research before you do anything I've suggested/stated. Also on the Sync Manager thing, what you need to do is install it from here http://www.htc.com/us/support/software/htc-sync-manager.aspx and then let it install the phone drivers for your M8 on your computer and then you need to uninstall it "HTC Sync Manager" from your computer in order to do the S-OFF process.
Please do be careful and get a good understanding before you do this though, re-read things a few times and make sure you're well aware of what it means and how to do it properly.
Click to expand...
Click to collapse
Yeah I'll have to look into that. I'm not sure if I'll ever flash a custom ROM though on my M8, Sense 6 is good as it is, I need to get Cyanogenmod on my Razr Maxx, Motoblur on it is just slow ever since they updated it to 4.1.2.
CannedBullets said:
Yeah I'll have to look into that. I'm not sure if I'll ever flash a custom ROM though on my M8, Sense 6 is good as it is, I need to get Cyanogenmod on my Razr Maxx, Motoblur on it is just slow ever since they updated it to 4.1.2.
Click to expand...
Click to collapse
Most of the ROM's for the M8 are Sense based anyways so you won't have a problem if you want Sense.
S1L3nTShaDoWz said:
Most of the ROM's for the M8 are Sense based anyways so you won't have a problem if you want Sense.
Click to expand...
Click to collapse
I just had a strange morning. What's new right? This morning I saw that my Titanium Back had a superuser fail. I had no problems yesterday. I used SuperSU to root and checked to see if Titanium Back was granted rights and it was. Still no luck running it. So Titanium suggested I load Superuser which I was not running. I installed it and it said it could not update the binary. That's weird so I read this post and reflashed SuperSU and yep Titanium backup was denied in the grant list. I granted it and everything is OK now. I posted here because I saw an unusual program in the grant list in SuperSU. It is com.koushikdutta.superuser. I don't know what that is but I bet that was the culprit. It did not show before I updated so it was hidden. Anybody know where this came from?
Weaksauce will not install binaries that's why it needs to reroot your phone every time you reboot. If you want your root to stick you need to be S-OFF. Since you are on 4.2.2 you could try Firewater to gain S-OFF. (Only works for some M8'S on 4.2.2)
http://firewater-soff.com/instructions/
If firewater does not work then you need to use Sunshine which I believe it cost $25. (Will not work on 4.4.4!)
http://forum.xda-developers.com/showthread.php?t=2792487
Not sure if you have adb/fastboot set up on your computer but if not...Google! I know there are instructions on how to set that up because I had to Google it. I think that may be the hardest part of all of this, if you can follow instructions WORD FOR WORD after setting that up I don't see how you can mess up. If you do find yourself stuck well we are here
SOLUTION
CannedBullets said:
http://forum.xda-developers.com/showthread.php?t=2699089&page=40
I tried using that method to root my phone, but Super SU just won't install binaries. First time around it just wouldn't work, after a few tries I unrooted my device and started over. I got the same message, "Unable to install, reboot"
Then after that it said something like "If you upgraded to 4.3 then reroot" Something like that. Which is weird because I have 4.4.2.
What's going on? I tried Superuser but when I tried installing the binaries it crashed when it was doing a software update twice so I had to hold down on volume up and the power button to reboot it on both occasions.
Also, how do I do an ADB Reboot? What's the easiest method? I tried doing that on my PC but it keeps saying device not detected Maybe I'm not setting up the program for that right? Yes, Developer Options and USB Debugging are enabled.
Yes my M8 is from Verizon. Is there another method for one-click rooting?
Click to expand...
Click to collapse
**SOLUTION**
Download the SuperSU ZIP from the link below;
http://download.chainfire.eu/supersu
Reboot your device into your custom recovery of choice, install the ZIP (which should be in your download folder on "sdcard" by default), reboot.
It should now work with no issues!
KnightAlex said:
**SOLUTION**
Download the SuperSU ZIP from the link below;
download.chainfire.eu/supersu
Reboot your device into your custom recovery of choice, install the ZIP (which should be in your download folder on "sdcard" by default), reboot.
It should now work with no issues!
Click to expand...
Click to collapse
I installed CM13 on my Moto G 1st Gen also GApps, I also had TWRP working. So my next step was to install SuperSU (UPDATE-SuperSU-v2.46.zip) with TWRP, after it says it was succesfull, i wanted to reboot the system, it is stuck in the Cyanogenmod Bootanimation and won't boot into the system. And It also stuck in the TWRP loading screen when i want to load into recovery!
What can I do? I have still files on the phone which I want to preserve!
Umm. This is a HTC one m8 forum?