Database Info

[Q] root without flashing?

I've looked at a few threads but they seem to involve flashing before rooting...
Is there a way to root without flashing? if so... how?
Thanks

You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.

unremarked said:
You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.
Click to expand...
Click to collapse
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???

sinatosk said:
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???
Click to expand...
Click to collapse
The bootloader is built into the phone, there's nothing to flash for that.
Think of it as a pre-recovery. Fastboot is a feature in the Android SDK which works with the bootloader to flash things such as recovery, or boot.imgs prior to actually having a custom recovery/root. However, it does require the bootloader to be unlocked which is where the fastboot oem unlock command comes in. Once you have a custom recovery on your phone, you flash things like normal.
From the stickied FAQ:
unremarked said:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot (aka the bootloader) mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
Click to expand...
Click to collapse
The first step helps you set up the SDK and drivers. The second step will tell you how to root, install recovery, and flash Superuser.

Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?

xspyda said:
Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?
Click to expand...
Click to collapse
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.

Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.

unremarked said:
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.
Click to expand...
Click to collapse
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...

xspyda said:
Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.
Click to expand...
Click to collapse
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
sinatosk said:
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...
Click to expand...
Click to collapse
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).

unremarked said:
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).
Click to expand...
Click to collapse
well yeah I know about ADB... just nothing about rooting

Hmm the phone shipped with 2.3 and I have yet to update but as 2.3.1 is an official update I can't see that being reason not to accept a return.

[Q] Very new to this, where to start?

Hello. As you can see, I'm a new member here and I'm also a new Android user; I bought my Nexus S (GT-i9020A) last week.
After a few days, I started thinking about jailbreaking my phone(rooting in Android's case) but I'm not really sure where to start, what rooting/flashing/ROM/etc means so I am just dumbfounded.
I want to customize my phone, make it look cool, etc.
Help would be greatly appreciated, thanks a lot in advance

1. Root = Unlock to change operating system
2. Install Recovery = Tool to install alternate operating system (ROM)
=> http://forum.xda-developers.com/showthread.php?t=931865
3. Install ROM = Modify the operating system
Then you can change kernel (link betwen operating system and the processor) or radio (link betwen operating system and radio communication).
Consult this : http://forum.xda-developers.com/showthread.php?t=1067813

anremi said:
1. Root = Unlock to change operating system
2. Install Recovery = Tool to install alternate operating system (ROM)
=> http://forum.xda-developers.com/showthread.php?t=931865
3. Install ROM = Modify the operating system
Then you can change kernel (link betwen operating system and the processor) or radio (link betwen operating system and radio communication).
Consult this : http://forum.xda-developers.com/showthread.php?t=1067813
Click to expand...
Click to collapse
Just to add a bit more info, rooting allows you full system access to your phone, where as stock prevents you from accessing certain areas. Some Apps that need to work with the phone on a low level need this root access.
A ROM is not really an operating system, its just the UI that sits on top of it, so different ROMS are custimized etc, lots to choose to your taste.
The recovery allows you to flash these ROM's , but it also allows you to backup your phone, access your storage etc in the case you can not boot.

'one more thing', root =! jailbreak, for god sake! android is 'jailbreaked' by default! =o)

bringonblink said:
Just to add a bit more info, rooting allows you full system access to your phone, where as stock prevents you from accessing certain areas. Some Apps that need to work with the phone on a low level need this root access.
A ROM is not really an operating system, its just the UI that sits on top of it, so different ROMS are custimized etc, lots to choose to your taste.
The recovery allows you to flash these ROM's , but it also allows you to backup your phone, access your storage etc in the case you can not boot.
Click to expand...
Click to collapse
Okay, that explained a lot. But what about the version of my phone? Most guides I see are for 2.3.3 but my phone is 2.3.4?

3doncrack said:
Okay, that explained a lot. But what about the version of my phone? Most guides I see are for 2.3.3 but my phone is 2.3.4?
Click to expand...
Click to collapse
The rooting process is the same for 2.3.3 & 2.3.4.

Maximilian Mary said:
The rooting process is the same for 2.3.3 & 2.3.4.
Click to expand...
Click to collapse
okay. Does phone model matter? Like i9020A or i9020T etc.?

3doncrack said:
okay. Does phone model matter? Like i9020A or i9020T etc.?
Click to expand...
Click to collapse
It should be the same for all the GSM models. Using an NS4G (D720) guide will not work.
(If you start flashing full roms, then you might want to use one specific to your exact model.)

Maximilian Mary said:
It should be the same for all the GSM models. Using an NS4G (D720) guide will not work.
(If you start flashing full roms, then you might want to use one specific to your exact model.)
Click to expand...
Click to collapse
It's not,
9020 rooting is different as 9023/9020A are different. They're similar but there is a minor difference.
And rooting != flashing.
Rooting permits you administrative access to change anything within Android (/system). HOWEVER, it doesn't give you permission to change the recovery. Changing the recovery isn't rooting. Rooting is step one of it but it is not the ability to flash a custom recovery.
The "rooting" process is for ANY android OS. Android OS will not be changing how the bootloader functions unless a new version of the bootloader is changed but it shouldn't significantly change.

zephiK said:
It's not,
9020 rooting is different as 9023/9020A are different. They're similar but there is a minor difference.
Click to expand...
Click to collapse
Pray tell what this difference is.
And rooting != flashing.
Rooting permits you administrative access to change anything within Android (/system). HOWEVER, it doesn't give you permission to change the recovery. Changing the recovery isn't rooting. Rooting is step one of it but it is not the ability to flash a custom recovery.
Click to expand...
Click to collapse
I thought it was the other way around: flashing a custom recovery is step one (well, two) of rooting.
The "rooting" process is for ANY android OS. Android OS will not be changing how the bootloader functions unless a new version of the bootloader is changed but it shouldn't significantly change.
Click to expand...
Click to collapse
Are you saying that the rooting process for the Nexus S will work for any android phone (for example the Hero or the Droid Charge)? Really?

Maximilian Mary said:
Pray tell what this difference is.
I thought it was the other way around: flashing a custom recovery is step one (well, two) of rooting.
Are you saying that the rooting process for the Nexus S will work for any android phone (for example the Hero or the Droid Charge)? Really?
Click to expand...
Click to collapse
For one, when the I9020A was announced, they were using the 9020T method to root and it didn't work. Hence there are two separate threads for rooting respective to that particular phone.
That's why one of the guides say,
[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)
Second: It depends. Some phones you can root with using the stock recovery. For example, the Galaxy S. You just download su.zip, rename it to update.zip go into stock recovery. Reinstall updates and BAM! you're rooted, you then proceed to get ROM manager and download Clockwork Recovery from there.
Edit: For example if you wanted to, you could totally unlock the bootloader and rename su.zip to update.zip and flash that in the stock recovery. It'll do nothing but add superuser.apk into /system/app. Because when I rooted my Nexus S. I didn't flash Clockwork Recovery yet, I wanted to make sure my phone didn't have any defects before changing it (this was before Google added a script to flash the stock recovery). Most guides make you flash Clockwork Recovery first, but in reality, it doesn't matter the order. But if you're a novice user, I'd just follow the guide.
It should be the same for all the GSM models. Using an NS4G (D720) guide will not work.
(If you start flashing full roms, then you might want to use one specific to your exact model.)
Click to expand...
Click to collapse
Third: No, by using common sense and process of elimination. I was clearly talking about the Nexus S due to its ability to unlock and lock the bootloader.
Also, you said "GSM models" and referred a "NS[4G]" and you said charge and hero.. so, you're kind of contradicting yourself here.
Again, process of elimination.
Thanks for trying to push my buttons though, didn't really work. Having said, not to say anything else. I have 2400+ posts, you figure I would know what I'm talking about. Nice try

zephiK said:
For one, when the I9020A was announced, they were using the 9020T method to root and it didn't work. Hence there are two separate threads for rooting respective to that particular phone.
That's why one of the guides say,
[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)
Click to expand...
Click to collapse
I could only find two differences between these guides. One is a patch for the 9023 drivers. I'm assuming Google has fixed this by now. (Can anyone confirm this?)
The other difference is the recoveries they use. Thanks to j_r0dd, you no longer need a separate recovery for the 9023.
Perhaps I should have said "Any up to date GSM Nexus S guide should work."
.
Second: It depends. Some phones you can root with using the stock recovery. For example, the Galaxy S. You just download su.zip, rename it to update.zip go into stock recovery. Reinstall updates and BAM! you're rooted, you then proceed to get ROM manager and download Clockwork Recovery from there.
Edit: For example if you wanted to, you could totally unlock the bootloader and rename su.zip to update.zip and flash that in the stock recovery. It'll do nothing but add superuser.apk into /system/app. Because when I rooted my Nexus S. I didn't flash Clockwork Recovery yet, I wanted to make sure my phone didn't have any defects before changing it (this was before Google added a script to flash the stock recovery). Most guides make you flash Clockwork Recovery first, but in reality, it doesn't matter the order. But if you're a novice user, I'd just follow the guide.
Click to expand...
Click to collapse
That is freaking cool. I'm going to unroot and try it. Do you need to do anything special in recovery, or just put the zip in the right place?
Third: No, by using common sense and process of elimination. I was clearly talking about the Nexus S due to its ability to unlock and lock the bootloader.
Also, you said "GSM models" and referred a "NS[4G]" and you said charge and hero.. so, you're kind of contradicting yourself here.
Again, process of elimination.
Thanks for trying to push my buttons though, didn't really work. Having said, not to say anything else. I have 2400+ posts, you figure I would know what I'm talking about. Nice try
Click to expand...
Click to collapse
The xda app doesn't show post counts. I figured thumping you in the chest would cover all the bases.

Super SU binaries not installing.

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?

[Q] Rooting HTC one M8

is it safe to root your htc one m8? Im not scared about the actual process but once it is rooted can it just randomly brick when opening an app? how does that work?

Black_magic100 said:
is it safe to root your htc one m8? Im not scared about the actual process but once it is rooted can it just randomly brick when opening an app? how does that work?
Click to expand...
Click to collapse
Never heard about random bricks of rooted phones. Often heard about cases of users bricking their phones, bacause they did not know what to do. E.g. deleting or changing important system files and and beeing curious why their phone won't boot anymore.
Way to gain permanent root:
1. Unlock your bootloader via HTCdev.com
2. Flash a custom recovery e.g. TWRP via fastboot commandline
.3 Flash SuperSU via TWRP

LS.xD said:
Never heard about random bricks of rooted phones. Often heard about cases of users bricking their phones, bacause they did not know what to do. E.g. deleting or changing important system files and and beeing curious why their phone won't boot anymore.
Way to gain permanent root:
1. Unlock your bootloader via HTCdev.com
2. Flash a custom recovery e.g. TWRP via fastboot commandline
.3 Flash SuperSU via TWRP
Click to expand...
Click to collapse
I just typed in "how to root htc one m8" and clicked the first video that popped up on youtube. Would you say this is safe to do? Also is the only way to brick your device yo **** with the system files like you said or is it possible to download a sketchy app and **** it up that way?

Black_magic100 said:
I just typed in "how to root htc one m8" and clicked the first video that popped up on youtube. Would you say this is safe to do? Also is the only way to brick your device yo **** with the system files like you said or is it possible to download a sketchy app and **** it up that way?
Click to expand...
Click to collapse
You should not follow any Youtube tutorials while havieng no clue what happens to your phone. XDA-developers is a really awesome forum, so just spend some time here reading and understand how root privileges will affect your phone.
BTW m8 has a own section --> [URL="http://forum.xda-developers.com/htc-one-m8"]CLICK ME[/URL]
Try to get informations and instructions here as they're mostly up-to-date and confirmed by other members.
I really can't recommend any YouTube tutorials.

Bootloop from root app permissions

Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?

val3nteen said:
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
Click to expand...
Click to collapse
Start here, http://forum.xda-developers.com/showthread.php?p=53439068. I'd return to stock and start all over, it will wipe your device, see the return to stock thread linked there. Then don't be lazy and read some more in the thread I linked you to. The n5 is one of the easiest devices to work with and you don't need kingroot, tool kits and junk like that
Sent from my Nexus 5 using XDA Free mobile app

You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image

deelan_chan said:
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
Click to expand...
Click to collapse
Thanks, but that is not possible, as I have not enabled USB debugging before bootloop. I need to unlock the bootloader (wipe) to install TWRP and backup data.

Can you get into fastboot mode? You can flash twrp from there no USB debugging needed
Sent from my Nexus 5 using Tapatalk

Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.

wangdaning said:
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
Click to expand...
Click to collapse
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.

val3nteen said:
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
Click to expand...
Click to collapse
But it is so fun to use fastboot. I remember almost dunking my wife's G2 until I got it to fastboot. Pain in the butt, but the command prompt does not lie